►
From YouTube: Argo Contributor Experience Office Hour 5th Aug 2021
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
And
yeah
so
hi
everyone
one
more
time.
I
I
won't
share
it
again
because
we
just
have
one
topic.
Basically,
I
think
both
me
and
harry.
We
wanted
to
discuss
the
planning
of
2.2
release
because
2.1
is
going
really
well.
I
think
we
we
fixed
like
pretty
much
all
known
bugs
so
far
and
I
guess
we're
just
waiting
for
more
bugs
for
few
more
days
and
2.1
will
be
released
and
we
need
to
get
ready
for
for
the
next
one
storm,
and
I
don't
know
how
do
you
want
to
yeah
sure.
B
Yeah
thanks
alex
yeah.
I
think
the
one
thing
that
we
want
to
discuss
is,
as
we
have
released,
2.1
for
2.2,
proposing
me
and
alex
are
proposing
for
a
milestone
meeting
where,
from
all
the
community
members,
you
can
bring
up
the
what
are
the
next
topics
or
the
next
features
to
go
or
the
box
to
go
in
2.3.
B
So
the
request
to
everyone
is
to
come
up
with
the
priority
terms
for
the
next
milestone
and
please
come
up
with,
must
go
items
go
to
go
and
stretch
kind
of
three
categories.
I
will
actually
update
in
the
sheet.
Also,
if
we
can
come
up
with
those
three,
then
we
can
use
the
meeting
rather
than
rather
than
adding
those
items
we
can
discuss
on
filling
up
the
2.2.2
milestone.
So
that's
the
request
to
everyone
in
the
community
any
questions
there
or
any
suggestions.
A
A
C
Yeah,
I
think
this
makes
sense
in
general,
we
need
to
ensure
that
for
all
the
contributors
here
we
represent
different
stakeholders
in
some
way
or
the
other,
so
we
should
effectively
ensure
we
poll
the
group
and
say
hey,
which
are
the
must-have
items
that
you
think
should
be
there
in
the
next
release.
That's
probably
this
group
and
then
in
one
of
the
community
meetings.
Also,
we
need
to
do
the
same
that
hey.
We
are
aware
that
many
of
you
have
been
looking
for
features
that
have
been
postponed
forever.
We
are
planning
for
2.2.
C
Let
us
know
if
some
of
those
things
are
still
important
to
you
and
ensure
that
they
are
surfaced
in
our
planning
and
of
course
we
have
to
take
a
call
in
the
end,
because
the
contributors
are
the
ones
who
are
probably
going
to
contribute
under
somebody
volunteers
for
it
and
then
potentially
figure
out.
What
can
we
realistically
accomplish
and
convey
that
to
folks?
Let's
say
somebody
says
they
really
want
this
and
say:
hey,
there's
no
way
we
can
get
to
it.
C
So
I
think,
that's
that
that's
the
first
thing
that
we
should
a
must-haves
and
then
everything
else
is
probably
easier
to
get
in
once
the
must-haves
are
agreed
upon
right
and-
and
I
think
that
way
like
from
a
red
hat
side,
we
can
also
plan
that
okay,
these
are
the
bunch
of
things
and
the
must-haves
from
our
side
may
not
be
the
only
ones
we
are
working
on.
C
B
That's
exactly
so,
I
think
means
once
we
have
a
must-have
must-haves
from
everyone.
It's
not
like
all
muslims
will
go
in
again.
You
need
to
plan
based
on
because
we
need
to
have
enough
content.
B
B
I
think
we
can
use
the
milestone
meeting
to
short
out
that
once
we
have
that
data,
so
the
request
is
to
come
up
with
that
kind
of
data
that
we
create
from
everyone
and
again
like,
as
you
said,
right
you
can,
we
should
discuss
in
the
community
meeting
as
well.
I
think
this
time
I
think
it's
on
friday.
We
can
bring
it
up
at
least
just
to
see
like
if
community
members,
what
are
the
items
that
they
think
that
they
want
to
have
in
the
next
milestone.
A
D
Or
maybe
next
friday
you
mean.
C
I
I
would
say
we
should
repurpose,
probably
one
of
these
meetings
for
a
detailed
discussion,
because
some
of
those
will
be
a
little
too
detailed
once
we
reach
a
you
know
fair
amount
of
consensus
about
what
will
actually
go
in.
We
can
probably
then
have
that
you
know
final
round
of
discussions
on
one
of
the
friday
meetings,
given
the
fact
that
the
initial
discussion
might
be
a
little
chaotic
and
then
once
the
cure
settles
down
a
little,
we
should
take
it
to
the
friday
meeting.
A
Okay
and
basically
I
agree
that
it
might
be,
I
feel
like
we
should
just
do
it
homework
and
get
you
show
up
to
that
meeting
with
some
list
already
prepared,
I'm
ready
to
work
on
that
list
during
next
week.
For
you
know
for
the
next
thursday
and
I'm
basically
looking
at,
I
guess
jonathan
william,
do
you
guys
do
have
time
to
prepare
something
for
the
next
meeting
to
basically
a
list
of
things
that
you
hoping
to
work
during
next
month
soon.
C
Yeah,
I
I
I
think,
let's
target
next
week
anyway,
which
means,
let's,
let's
at
least
get
things
started,
so
I
think
from
right
outside.
If
we
can
get
something
done,
that
would
be
awesome,
we'll
probably
target
it
for
sure.
We've
been
doing
some
planning
on
our
end
as
well.
So
I
think
let's
have
the
first
milestone
planning
meeting
on
thursday.
If
we
see
that
we've
reached
enough
consensus
about
what
should
go
in
and
it
doesn't
have
to
be
hundred
percent,
even
80
percent
is
fine.
C
Then
we
can
probably
do
more
of
like
an
announcement
thing
that
these
are
the
things
that
we
are
planning
to
work
on
in
the
friday
meeting.
And
then
you
know,
because
I,
because
else
the
friday
meeting
will
be
like
100
argo
city.
We
should
have
some.
You
know
time
provided
for
the
other
projects
as
well.
B
I
have
actually
one
more
yeah.
Okay,
do
we
have
this
member
edition
meeting
as
well
like
so
we
have
new
members
from
outside,
also
andrea
and
myself,
and
if
anyone
else
from
the
community
that
needs
to
be
added,
do
you
have
that
quarterly
membership
meeting
as
well?
So
you
can,
can
you
say
it
again?
What
can
you
mention
the
memory
edition
meeting?
I
remember
like
there's
a
sheet
that
we
maintained
the
members.
A
I
mean
yes,
we
have
meeting
for
yeah,
it
happens
every
friday.
If
there's
a
meeting
that
you're
talking
about.
A
Okay-
and
I
I
just
had
one
more
topic-
I
didn't
know:
if
we're
going
to
have
time
today
that
looks
like
we
have,
so
we
wanted
to
do
featured
aging
and
looks
like
it's
really
hard
to
fit
it
into
one
of
these
meetings,
because
we
usually
run
out
of
time
except
today,
and
we
kind
of
stopped
doing
that
because
it
was
impossible
to
do
during
that
meeting,
and
I
guess
we
can.
A
We
just
discuss
the
process
of,
looks
like
we
must
take
it
offline
and
do
it
the
same
way
with
their
bugs
yeah
and
but
features
are
different
from
bugs,
because
basically
we
want
to
salutate
more
opinions
like
it's
easy
to
answer
bugs,
because
if
you
know
the
answer
you
just
answer,
it
features
are
opinionated
and
I'm
kind
of
trying
to
need
looking
for
suggestions,
how
we
can
do
that
process
offline.
But
at
the
same
time
you
know
include
everyone
yeah
possibility.
A
We
just
we
can
agree
to
just
use
common
sense
and
kind
of
try
to
have
a
rotation,
and
then
someone
would
try
to
try
us
simple
features.
Basically,
just
make
sure
we
don't
have
duplicates
and
accept
features
that
obviously
have
to
be
exact
but
reject
everything
which
have
to
be
rejected
and
come
up
with
the
list
of
issues
that
need
discussion
and
bring
it
up
during
that
meeting,
and
we
can
discuss
this.
A
C
I
think
that
sounds
good.
We
probably
need
somebody
to
volunteer
to
go
in
and
try
it
issues
and
it
shouldn't
always
be
you
alex
and
other
folks.
That's
what
my
suggestion
would
be.
The
initial
triaging
is
more
about
hey.
This
is
a
bug
for
sure
and
let's
label
that
as
a
bug
or
hey,
this
looks
like
a
feature
and
definitely
not
a
bug,
but
then
this
needs
more
discussion.
C
I
think
that
that
traging
is
something
that
we
need
to
volunteer
every
couple
of
weeks.
I
think
I
did
mention
this
once,
but
did
we
ever
get
to
it?
I'm
not
sure.
So
we
probably
should
look
at
just
like.
We
have
github
discussions
moderator.
We
should
have
a
triager
role,
which
a
lot
of
software
which
which
a
lot
of
open
source
projects,
have
where
somebody
would
volunteer
every
couple
of
weeks
to
be
the
treasurer,
which
means
new
issues
coming
in
new
feed
and
just
put
them
in
the
right
buckets.
C
B
Yeah
correct
primary
image:
tracer
roles
can
be
primary
secondary
where
one
can
be
experienced.
Another
can
be
a
new
person
where
he
can
also
learn
like
probably
even
like
the
primary
or
someone
is
not
available.
The
other
can
at
least
available
during
the
that
time.
So
probably
two
at
a
time
might
be
better.
I
think
the
price
cases
I
agree.
B
A
C
Yeah,
I
think,
and
and
and
the
minimum
like
at
least
between
one,
at
least
between
one
one
of
those
traders,
the
minimum
requirement
is,
they
should
be
able
to
add,
remove
labels.
I
think
pretty
much
that-
and
I
think
we
do
have
a
bunch
of
folks
who
can
add,
remove
labels
right
now
on
the
cd
project,
at
least
so
it
should
be
a
lot
easier
now.
A
C
A
A
C
Do
you
want
to,
you
know,
ask
for
a
volunteer
for
the
next
two
weeks
or
do
you
want
that
started
in
a
couple
of
weeks
or
do
you
want
to
start
with
yourself
first,
but
you
do
you
do
it
anyway?
So
there's
not
nothing
much
to
start
with
you
alex.
B
We
actually
should
start
from
next
week.
I
think
I
should
discuss
about
next
week
tries
as
well
as
we
have
the
discussion
so.
A
B
At
least
we
should
start,
we
should
come
up
with
two
members
for
starting
from
next
two
weeks.
Meanwhile,
we
can
iron
out
all.
C
A
No,
no,
I
wasn't
thinking
yeah
I've
and
I
think
a
game
is
dead,
so
we're
saying
we
find
two
today
right
now,
right
and
okay.
It
could
be
me
here.
I
could
start
first
and
maybe
john,
do
you
want
to
join
me?
Ian
is
not
here.
C
Yeah
I
mean
I'm,
I'm
I'm
a
little
more
inclined
to
have
folks
like
since
you,
since
you
are
doing
it,
I'm
a
little
more
inclined
to
do
to
have
somebody
who's,
not
jonathan
or
me
or
jan,
just
so
that
you
know
you
have
a
good
knowledge
transfer
potentially,
so
I'm
a
little
more
inclined
to
have
one
of
the
newer
folks
join.
You
does
that
make
sense.
Just.
C
Yeah,
so
any
volunteers
here
in
the
list-
who's
not
let's
say
jonathan.
E
C
C
C
If
you
need
an
example
of
you
know
what
this
work
looks
like,
you
might
want
to
look
at
the
helm
project
they
the
way
they
do.
It
is,
and
I've
myself
been
in
that
role
a
number
of
times
where
being
a
maintainer
is
important
link
some
in
some
fashion,
because
you
need
to
add
remove
labels,
but
even
if
you're,
not
a
maintainer,
you
can
always
be
a
secondary
charger,
and
I
think
you
know
in
this
case
we
have
a
great
example
pasha,
where
you
probably
like
whether
or
not
you're
a
maintainer.
C
One
of
the
things
that
you
would
have
to
do
in
this
role
is
sometimes
have
a
conversation
with
somebody
who
has
opened
an
issue,
ask
more
details
and
then
maybe,
after
a
conversation,
threat
of
five
or
six
messages,
you
understand
it's
a
bug
or
that
it's
a
feature
request.
So
having
that
two-person
thing
is
a
great
idea.
You,
you
may
not
always
be
able
to
see
an
issue
and
understand
if
it's
a
bug
or
a
feature.
F
D
Yeah
correct
yeah
awesome.
Thank
you
back
to
you
alex
okay
and
if
there.
G
Sorry
yeah
just
the
last
topic
I
would
just
add
it
would
be
good
to
include
a
after
you've
gone
through
it
for
say
a
couple
weeks
to
just
write
up
a
quick
description
of
what
is
expected
from
future
folks
that
are
doing
this.
Just
it's
obvious
the
process
that
they
need
to
follow
in
order
to
do
it
themselves.
G
G
Yeah
and
so
yeah,
the
other
thing
I
want
to
bring
up
is
that
you
briefly
talked
about
how
argo
cd
v
2.1
is
going.
Do
you
want
to
give
a
brief
update
on
that.
A
A
A
Eta
is,
I
think,
it's
going
awesome.
We
basically
we
didn't,
we
get
no
blocking
bugs,
they
were
blocking
bugs,
but
the
the
fixes
were
trivial.
Basically,
we
cut.
We
like
messed
up
some
environment
variables,
first
thing,
but
in
general
I
think
we
fixed
already
like
25
bucks
and
yeah,
and
I
it's
a
sign
that
maybe
we
created
release
branch
too
early,
but
it's
okay.
A
It
was
really
easy
to
seems
like
we
stayed
focused
on
bug
fixing
and
it
was
extremely
easy
to
cherry
pick,
all
the
bugs
and
right
now
I
personally,
it's
not
even
a
bug.
I
just
had
a
neat
like
I
just
wanted
to
polish
ui
a
little
bit,
but
it
sounds
like
we
can
release
it
like
even
now.
Basically,
there
are
no
known
bad
issues
in
the
release
and
that's
why
yeah,
I'm
really
hoping
just
for
your
information
like
internally,
with
deploying
argo
cd
already
to
our
cluster
set
into
it.
A
G
Yeah,
so
for
application
set
controller,
we're
hoping
to
release
alongside
our
go
cd,
2.1,
so
yeah.
It
would
be
great.
If
you
give
me
a
heads
up.
G
You
know
as
soon
as
you're
you
have.
You
know
like
a
general
idea
when
you
plan
to
release
once
you
do
release.
Basically,
what
I'll
be
doing
is
picking
up
that
final
argur
cd
driver
making
sure
that
it
still
works
with
the
the
application
set
0.20
release
candidate
and
then
putting
out
the
0.2
release
alongside
it
but
yeah.
G
Basically,
I
need
to
wait
until
the
argo
cd
release
is
out,
because
I
need
to
make
sure
that
because,
because
some
degree
we're
dependent
on
argo
cd
dependent
on
the
behavior,
and
I
need
to
make
sure
that
there
haven't
been
any
last
minute
regressions
that
would
affect
application
set
functionality.
So
yeah
yeah
sounds
good.
Sounds
like
it'll,
be
like
very
close,
which
is
great.
G
A
Yeah
definitely
I
will
so
it's
sun
day
next
week
and
today
only
I
think
we'll
know
I
will
know
for
sure
around
next
tuesday,
when
we
deploy
yeah
so
sounds.
G
Good
and
yeah
on
the
application
side
of
things
just
to
give
folks
a
status
update
you
if
you're
on
the
application
set
status,
slack
channel,
you
probably
see
messages
from
me
about
various
release,
candidates
and
status,
but
yeah
things
are
going
great
there
as
well.
I
think
we've
had
a
release
candidate
out
for
testing
for
folks
on
the
channel
since
at
least
mid-july
and
got
some
great
bugs
there.
Those
have
all
been
fixed
folks
continue
to
test,
but
so
far
so
good
and
yeah.
G
I
think
at
this
point
ready
to
release
as
soon
as
argo
cd
is
release,
notes
are
written,
contributor
list
is
compiled
and
I've
got
the
blog
post.
I
just
need
to
submit
that
to
y'all
for
review
for
the
the
medium
publication,
but
yeah.
That's
it
for
me
for
application
sets.
A
Thank
you
all
right,
and
I
I
want
it
just
so
I
don't
forget
it
again.
We
need
to
change.
A
We
need
to
update
the
moderators
for
for
next
week
and
before
we
go,
I
wanted
to
ask
basha
and
john:
how
did
it
go
last
week
I
I
got
some
feedback
from
kosher
that
it
was
not
easy
to
do
it.
Even
you
know,
answer
discussions
unless
you
have
good
knowledge
of
a
project.
H
Yeah
I
found
the
same
thing.
I
did.
H
Few
of
them
I
didn't
answer
nearly
as
many
as
I
was
open
to,
but
because
I
I
had
some
time
often
because
I
was
busy
with
other
stuff
and
also
because,
like
precious,
my
question
was
saying:
it's
it's
not
as
easy
as
if
you're
not
familiar
with
the
project,
but
I
did
manage
to
answer
a
few
of
them.
E
C
C
And
I
think
this
is
fine.
You
know
it
is
expected
that
not
everyone
would
be
in
a
position
to
answer
every
question
like
an
expert
and
that's
fine,
but
john
and
bashar,
were
you
able
to
reach
out
to
some
of
the
other
experts
in
the
group
who
would
have
been
able
to
help
you
out?
I
mean
that's.
Definitely
an
option
like
if
you
see
a
question,
that's
going
in
a
direction
that
is
not
making
sense.
It's
definitely,
okay
to
ping,
one
of
one
of
the
more
popular
members
with
these
areas.
C
E
C
I
guess
contributors,
no,
I
I
think
in
general
we
did
discuss
about
having
a
group,
but
then
we
didn't
want
to
make
it
an
exclusive
member
group.
That's
why
we
said:
let's
not
have
a
group.
Rather
it's
fine,
if
you
reach
out
to
alex
and
alex,
can
always
put
you
in
touch
with
other
people,
and
I
think
that
should
be
fine,
but.
A
Okay,
is
it
is
that
the
problem
that
we
just
you
know,
don't
know
each
other
yet
and
like
one
way
to
fix
it
yeah
we
can
simply
select
links
to
next
to
moderator
names
and
basically,
you
would
know
at
least.
C
Right,
I
think
that's
a
great
idea
and
and
to
be
clear,
I
think,
john
pasha
and
who
and
whoever
picks
this
up
next,
just
because
you're
a
moderator
does
not
mean
you
have
all
the
answers:
you're,
the
one
who's
taking
the
initiative
to
find
the
answer.
So
it's
totally
fine
to
feel
absolutely
dumb.
When
you
see
a
question-
and
that
happens
to
me
all
the
time,
but
then
it's
just
that
you're
taking
the
initiative
to
go
talk
on
somebody
and
say:
hey
somebody's
looking
for
this
answer.