►
From YouTube: Argo Contributor Experience Office Hour 4th Feb 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
Okay,
so
yeah
good
morning,
everyone
again
today's
our
contributor
experience
meeting
yeah,
I'm
looking
at
a
list
of
participants
trying
to
see
if
there
are
any
new
attendees.
I
think
we've
met
with
everyone
before
so
no
need
to
do
introductions
all
right
and
I'm
going
to
share
agenda
which
is
really
short
today
there
is,
we
didn't
get
any
new
topics
and
we
discussed
everything
from
last
time.
I
think
we'll
have
to
you
know,
come
up
with
a
list
of
things.
We
want
to
decide
on
a
fly
and.
B
B
Sure,
I
think
one
topic
I
wanted
to
add
is
we
need
to
so
so
I
think
I
was
speaking
to
serena
while
ago
and
I
wanted
to
ensure
that
we
don't
lose
out
on
the
ux
health
that
we
could
potentially
get.
B
So
we
should
go
ahead
and
designate
one
of
these
meetings
as
a
ux
centric
meeting,
so
that
we
can
ensure
the
ux
folks
are
in
there
and
we
have
all
the
ux
and
ui
concerns
brought
in
that
meeting,
specifically
at
least
so.
If
we
can
just
choose
probably
let's
meeting
as
the
ux
meeting
and
then
every
third
meeting
from
there
to
be
the
ux
meeting.
That
would
be
great.
A
B
Just
to
get
the
you
know,
ball
rolling
to
have
one
meeting
and
then
every
every
third
or
fourth
meeting
from
there.
We
could
actually
find
out
the
right
kids,
but
then,
like
once
a
month,
we
could
have
like,
like
today's
feb.
Fourth,
so
feb
11th
could
be
the
next
one
and
exactly
a
month
from
there
could
be
the
next
one
again.
So.
A
B
A
B
Think
to
add
to
that
again-
and
this
is
to
ensure
that
you
know
we
don't
take
too
much
responsibilities
on
our
shoulders
and
we
divide
them
properly.
We
should
have
a
volunteer
from
this
group
to
say:
hey,
I'm
going
to
find
out
all
the
different
ui
ux
issues
or
work.
B
That's
happening
contact,
the
corresponding
people,
and
let
them
know
that
we
have
this
meeting
so
that
you
know
folks
actually
show
up
on
this
meeting
with
the
ui
ux
concerns
next
somebody
to
drive
that
meeting
would
be
nice
and,
and
that
doesn't
have
to
be
me
or
you,
somebody
from
the
group
like
every
once
a
month
that
person
should
be
in
charge
of
moderating
that
meeting
by
getting
all
the
concerns
in
one
place
and
the
people
in
one
place.
B
So
I
could
propose
regina.
Do
you
want
to
go
ahead
and
organize
the
next
one.
B
Awesome:
yeah,
okay,
yeah.
I
think
I'm
good
with
that.
I
think,
as
a
first
item
I
can
just
document
it
on
the
sheet
once
that's
done,
the
the
second
one
would
be,
I
think,
alex
we
did
discuss
this
as
well.
A
while
ago
is
if
we
could
come
up
with
a
structure
to
do
grooming
and
planning
also
with
the
whole
group,
just
so
that
for
every
milestone
you
know
you
could
take
into
account
the
non-intuit
help.
Also
that.
B
In
there
for
the
mind
stone,
given
the
fact
that
now
we
have
enough
developers
who
are
pretty
ramped
up
on
this.
So
I
think
I'll
I'll
leave
that
to
you
when
you
want
to
schedule
that
and
how
you
want
to
schedule
that
in
what
cadence.
A
A
Thank
you
cool
and
I
I
wanted.
If
that's
everything
do
or
do
you
want
to
discuss
something
else.
A
Okay,
so-
and
I
I
wanted
to
can
just
talk
about
milestone-
we
didn't
have
hard
deadline,
but
I
think
we
kind
of
we
were
trying
to
deliver
next
time.
Gucci
demand
stone
by
one
by
end
of
february,
and
it
was
different
because
I
feel
like
the
most
number
of
contributions
are
happening
outside
of
fargo
city
in
labs
projects,
in
application,
setting
notifications
and
in
image
updater
and
work
there.
I
feel
like
getting
to
the
end.
A
A
You
know,
try
to
limit
the
amount
of
new
features
which
we
basically
try
to
delay
and
don't
commit
for
a
big
new
features
for
1.9
unless
we
plan
it
for
1.9
and
yeah,
and
basically,
I
think
intuit
team
is
now
trying
to
close
all
the
issues
which
we
could
not
complete
in
1.8.
So
the
god
moves
into
1.9
and
it
based
on
how
quickly
we're
going,
I
feel
like
we
will
be
done
with
1.9
in
one
or
two
weeks
and
then
we
can
spend
another
two
weeks.
A
B
Yeah,
I
think
that
that
sounds
okay
to
me
from
what
I
hear
yeah,
I
think
in
in
general,
we
do
have
a
lot
of
contributions
happening
in
non-argo
cd
projects
like
non-core,
argo,
cd
projects,
and
I
think
that's
that's
why
it
it's
a
little
tricky
to
estimate
the
availability
of
people
for
argus
issues
itself,
but
I
think
that
should
get
better
gradually.
B
A
It
seems
to
be
very
well
to
me
because
we
yeah
we've
done
a
lot
already
and
I'm
like
we
did
more
than
expected
when
we
were
planning
it.
It
sounded
too
ambitious
to
get
these
three
projects
in
a
good
state
and
seems
like
we
are
already
pretty
far
yeah
and
the
kind
of
typically
every
release.
We
have
this
issue
where
release
is
almost
there
and
then
we
can
meet
to
build
something
which
may
be
a
very
big
feature
or
maybe
not,
and
it
appears
to
be
big
and
example
could
be.
A
For
example,
we
introduced
class
referencing
cluster
by
name
which
sounds
like
a
small
feature,
because
it
fit
into
one
sentence,
and
it's
not
right,
because
it
was
touching
too
many
places.
So
it
was,
I
mean
it's
good,
we
did
it,
but
it
was.
You
know,
a
big
effort
to
get
it.
A
Basically,
I
think
we
had
to
delay
release,
maybe
by
a
week
to
fix
all
the
bugs
and
I'm
kind
of
asking
to
try
to
from
now
on,
like
from
this
point
of
time,
we
maybe
should
focus
more
on
fixing
bugs
because
we
already
have
a
lot
and
and
then,
if
we
just
fix
bugs
for
the
next
couple
weeks
and
then
we'll
have
enough
time
to
to
test
what
we've
built,
because
most
likely
there
will
be
bugs
in
updater.
If
we
try
to,
you
know,
get
feedback
from
users,
they
will
come
back
with.
A
A
Great
and
the
other
topic,
I
had
not
sure
if
it's
appropriate
for
that
meeting,
but
I
have
a
feeling
that
it's
time
to
you
know
talk
about.
A
How
do
we
call
it?
You
know,
promote
users,
promote
contributors
to
the
next
role,
I'm
pretty
sure.
Now
we
have
reviewers
who
supposed
to
be
approvers
and
members
who
should
become
reviewers,
and
we
have
contributors
who
should
became
members
and
trobeki,
usually
the
best
person
who
knows
how
to
drive
that
process
and
like
can
you
please
suggest.
B
Yeah,
I
think
in
general
my
suggestion
would
be.
I
think
you
did
the
hard
work
already,
which
is
to
figure
out
who
would
be
recognized
as
reviewers
based
on
their
contributions.
I
think
again
the
next
steps
would
be.
Of
course
the
ball
would
be
your
code
alex,
which
is,
I
think
I
let
the
project
leads,
go
ahead
and
nominate.
Folks,
you
think,
should
be
elevated
to
maintainers.
B
If
that's
what
you
were
thinking
and
I
think
it
should
be
a
simple
pr
and
at
the
same
time
I
would
allow-
I
mean
I
think
we
should
let
others
also
nominate,
but
I
think
the
process
which
I
would
like
to
put
in
place
is
that
you
know
speak
to
alex
or
any
other
maintainers
and
nominate
that
you
think
somebody
would
be
good
and
let
the
maintainers
go
ahead
and
do
it.
A
And
do
you
think
it's
okay
to
do
the
whole
process
of
learning
I'm
kind
of
trying
to
avoid
yeah?
I
think
because
it's
pretty
hard
to
you
know
no,
no.
B
Totally,
I
think
this
should
not
be
a
meeting.
This
has
to
be
offline
for
multiple
reasons,
especially
because
a
lot
of
people
are
more
comfortable
having
these
conversations
over
text
or
instead
of
having
them
verbally,
especially
because,
let's
say
as
a
simple
example,
I
in
from
the
community,
come
and
reach
out
to
you
and
say:
hey.
I
want
this
person
to
be.
I
think
this
person
is
a
good
maintainer
could
be
a
maintainer,
and
let's
say
you
say
no
like
having
that
conversation
verbally
is
a
lot
harder
than
having
that
over.
Let's
say.
B
Comfort
level
is
probably
higher
if
somebody
does
it
offline,
so
I
totally
agree.
So
I
think
one
thing
we
should
do
here
as
a
team
is
come
up
with
a
date
which
means
that,
let's
keep
nominations
open
for
you
know
so
and
so
days
that
that
is
beyond
the
ones
which
I
think,
let's
say,
alex
and
jesse.
B
A
A
All
right
this
is
it.
I
discussed
everything
I
wanted
to
discuss
in
that
meeting
and
folks,
please
I'm
pretty
sure
you
had
questions
we
can
use
it.
You
know
to
answer.
We
could
use
that
meeting
to
answer
your
questions.
C
But
by
the
way
I
started
asking
so
we've
gotten
to
roll
out
people
who
want
to
contribute
like
new
integrations
to
the
like
ambassador
integration
and
like
citrix,
ingress
controller
integration,
and
I
started
asking
folks
to
kind
of
prepare
like
how
a
spec
change
and
how
this
would
work
and
integrate
with
the
their
respective
controller
and
and
present
that
in
these
meetings,
because
I
thought
it
would
be
a
good
time
to
like
understand
like
how
those
things
work
and
and
how
the
design
would
be.
C
So
if
there
are
other
kind
of
cd
contribution
stuff
that
you
want
to
understand-
or
you
know-
maybe
a
pr
is
kind
of
languishing
and-
and
you
know
it
could
do
better
with
a
one-on-one
kind
of
interaction.
Where
you
can
ask
more
questions,
I
I
thought
this
meeting
was
suitable
for
that.
C
B
C
B
C
I've
asked
them
to
put
forward
either
in
a
github
issue
or
a
google
doc,
just
like
the
changes
or
that
how
it
would
how
it'll
work,
maybe
like
a
design.
I
don't
want
them
to
go
overboard
with
it
yeah,
but
there's
just
some
kind
of
document
explaining
how
it
would
work
and
then
present
it
here
just
so,
we
can
agree
on
on
the
design
before
they
get
too
far
in
the
implementation.
C
Yeah,
so
if
there's,
if
there
are
other
argo
cd
stuff
and-
and
you
know,
if
a
pr
maybe
our
go
cdpr
is
getting
too
involved,
then
I
would
invite
the
contributor
to
come
to
this
meeting
to
kind
of
talk
to
it.
I
think
that
might
you
might.
B
Yes,
I
think
yeah,
I
think
in
general.
The
wider
community
meeting
is
helpful
for
all
talking
about
a
new
feature
that
the
users
will
be
interested
in.
But
then,
if
that
leads
to
changes
in
design
in
a
fashion
that
it
needs
more
deep,
deeper
vetting
right.
C
Okay,
yeah.
I
just
wanted
to
to
remind
people
that
this
is
a
venue
for
that,
because
that's
what
I've
been
doing
for
some
of
the
rollouts
of
which
I
because
I
don't
have
any
you
know
background
on
how
the
ingresses
work
and
when
I
would
like
to
learn
about
how
those
work
and
then
to
validate
the
proposal
or
like
I
can
offer
my
insights
on
how
to
adjust
the
spec
to
accommodate
their
needs.
B
Okay,
I
think
the
last
topic
would
be
alex.
You
were
the
github
discussions,
moderator
any.
D
D
A
Thank
you
for
reminding
it
was
actually
not
busy
at
all.
I
think
I
got
maybe
I
answered.
Maybe
four
questions
give
me
one.
Second,.
A
Yeah,
so
I
had
to
answer
maybe
four
questions
and
I
noticed
that
finally
github
fixed
the
bug
and
now
it's
possible
again
to
convert
issues
back
to
discussions,
and
I
think
we
should
do
that
aggressively
because
there
are,
I
mean,
not
aggressively.
There
are
a
lot
of
issues
that
have
been
sure
yeah
to
be
discussions.
We
could
not
do
it
before
so
next
week.
There
will
be
more
questions,
but
yeah
it
was.
You
know.
Four
questions
is
not
a
big
deal.
It
was
easy
to
answer
it,
but.
B
Right,
I
think
right,
I
I,
I
think,
that's
also
test
too
many
of
the
fact
that
we
probably
need
to
make
this
mode
of
q
a
more
pop,
more
popular,
because
I
think
a
lot
of
folks,
I
think
the
slack
channel
is
the
slack
channel
is
super
chatty
right
and
I
think
the
way
I
see
it
is
we
all
spend
time.
You
know
answering
those
questions,
but
they
go
away.
They
are
not
searchable
at
all.
B
B
That
would
be
awesome,
so
I
would
say
whoever
picks
up
the
torch
for
the
next
one,
should
try
that
or
encourage
that
or
kind
of
like
answer
the
question
and
say
hey
by
the
way.
We
also
encourage
people
to
open
up
questions
on
github
discussions
that
way
they
remain
documented
and,
having
said
that,
I
think
whoever
is
the
next
github
discussions.
Moderator
should
also
probably
go
through
the
github
issues
and
if
somebody
has
a
question
there,
which
is
which
should
be
in
q,
a
which
should
be
in
the
github
discussions.
B
A
Right
now
we
have
a
kind
of
a
personal
duty,
who's
supposed
to
review
issues,
and
I
think
we
should
one
of
maintainers
do
it
and
that
same
person
should
convert
issues
to
discussions,
and
I
think
we
have
not
done
it
before,
because
the
feature
was
disabled.
It
was
impossible
and
I
noticed
it
was
enabled
literally
like
two
days
ago,
yeah
and
that's
why
it
heads
up
to
the
next
person.
I
think
you
will
get
converted
issues
in
discussions.
A
B
D
Thank
you,
and
also
thank
you
to
the
redhead
colleagues,
for
the
warm
welcome
that
was
given
to
me.
I'm
very
humbled.
D
Yeah,
but
coming
back
to
alex,
so
I
volunteered
last
time
for
the
upcoming
week.
So
this
is
my
word
and
I'll
do
it.
So
it's
up
to
you
totally
understandable
if
you
cannot,
because
personally,
no.
D
It's
I
think,
it's
it's
it's
fine,
so
I
I
hope
the
effort
will
be
yeah,
not
not
that
high
I'll
try.
It.
B
Yeah,
I
I
think,
jan
while
I
love
the
fact
that
you
are
offering
to
do
it,
but
you
do
it
anyway,
irrespective
whether
you
take
up
the
role
of
the
moderator
and
you're
one
of
the
most
active
people
on
slack.
I
think
one
of
I
think
one
of
the
things
that
I'd
like
you
to
do
yarn,
since
you
know
you're
doing
it
for
the
upcoming
week
is
that
do
I.
I
would
like
to
have
folks
who
typically
don't
get
engaged
on
slack
a
lot.
B
A
A
Yeah
to
motivate,
basically,
I
felt
better
this
week
because
I
felt
like
everyone
has
stand
up
and
I
you
know
basically
it
felt
more
like
work
than
you
know,
I'm
helping
someone,
because
I'm
in
a
mood
I
I
felt
like
not
a
pressure,
but
I
knew
that.
Yes,
I'm
supposed
to
spend
time
answering
questions
because
that's
what
we
agreed,
I
should
do
yeah.
B
Right,
I
I
think,
let's,
let's
go
with
yarn
for
the
next
one
and
with
that,
if
any
of
you
want
to
pick
up
for
the
next
one,
just
you
could
add
in
your
name
in
the
queue
or
speak
up
for
the
next
one.
E
Yeah
I
can
warranty
the
week
after
year
on
this
week,
I'm
gonna
I'm
gonna.
Have.
I
will
ask
john
for
for
answer
anyway,
so
yeah
the
week
after
awesome.
A
B
A
And
I
think
I
just
want
to
repeat
kind
of
stress
this
proposal,
one
more
time.
So
what
jesse
mentioned
is
that
if
you
have
questions-
and
you
know
feel
free
to
and
if
you
want
to
speak
with
someone
about
the
pr
you're
working
on,
please
use
that
meeting
and
just
feel
free
to
request.
A
E
So
so
speaking
about
one
nine
right,
so
the.
D
E
So
it's
not
on
the
on
the
card.
One
nine
right
so
certainly
I'll,
be
anything
that
we
will
bring
upset
into
ago.
City
will
be
happening
after
online.
Is
that
this
is
fair
to
say,
I
think.
A
A
You
know
it's
like
a
lightweight
documentation
and
that
tutorial
should
work
and
I'm
pretty
sure
creation
of
that
tutorial
will
reveal
things
that
we
missed,
and
so
we
will
be
forced
to
fix
everything
which
is
you
know,
you
know,
stays
on
heavy
path
and
doesn't
work
and
that's
what
I
imagined
could
be.
Basically
a
lot
of
work
already
done.
There
are
a
bunch
of
tests
and
upset.
Is
I
I
feel
like
it's
almost
ready.
A
There
are
a
few
open
issues,
but
we
will,
I
think
we
will
spend
next
two
weeks
to
kind
of
just
polish
it
and
and
make
sure
it's
visible
in
argo,
cd
documentation
and
usually
it
sounds
like
not
much
of
work
but
in
reality
it
takes
days.
A
Not
yet,
but
two
pairs
are
open
by
regina
and
I
think
we
just
asked
to
make
us
like
one
line
change.
Basically,
we
have
a
banner
that
asks
user
to
go
to
latest
version
and
instead
it
should
be
stable,
jan
pointed
it
out.
So
once
it's,
I
think
it's
done
so
we
just
need
to
merge,
and
then
we
can
read
the
docs.