►
From YouTube: Kubernetes Contributor Experience SIG 20190320
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
Well,
alright,
hello.
Everyone
welcome
to
today's
edition
of
our
Weekly
contributor
circus,
aka
contributor
experience.
My
name
is
Paris.
I
will
be
your
host
today,
along
with
Nikita
we're
gonna
be
co-hosting
because
we've
got
a
special
edition
of
the
circus
for
you
today
again
meeting
I
mean
trying
trying
to
be
funny
anyway.
A
First
order
of
business,
we
do
have
a
code
of
conduct.
This
is
a
different
kind
of
meeting
so
make
sure
that
if
we
are
talking
above
each
other
try
to
either
raise
hands
or
say
something
in
the
chat
just
because
there
is
going
to
be
a
lot
of
back-and-forth
I
do
not
see
any
new
contributors
on
the
line
right
now,
so
we're
gonna
go
ahead
and
skip
new
contributor
introductions
and
then,
let's
go
on
to
our
regular
program,
updates,
really
quickly,
George.
Why
don't
you
take
both
office
hours
and
community
meeting
in
one
shot.
B
So
office
hours
is
sad.
We
had
our
first
session
this
morning,
I
kind
of
changed
a
You
Tube
workflow
a
little
bit
so
that
the
URLs
are
unique.
So
we
can
do
them
ahead
of
time
instead
of
telling
people
to
just
go
to
slash
live,
which
is
weird
and
so
we're
all
set
with
that
community
meeting
is
also
for
this
week.
Jonas
is
hosting
next
week.
A
A
The
next
one
is
April
3rd
7:30
a.m.
Pacific
as
well
as
1
p.m.
Pacific,
and
we're
mostly
full
for
those
which
is
nice,
and
we
will
have
a
code
based
tour
on
the
one
o'clock
and
I
think
we
also
might
have
one
on
the
7:30,
which
is
super
cool
as
well,
which
will
achieve
a
lot
of
the
code
based
or
goals
that
we
have
set
in
in
the
issue
which
is
nice.
So
that's
my
update
for
meet
our
contributors
and
would
love
to
see
your
shining
faces
each
one
of
you
on
an
episode.
A
C
C
A
B
Can
you
ask
any
of
them
that
are
having
any
kind
of
calendar
problems
to
just
sort
of
file
an
issue
in
K
community
I
just
want
to
make
sure
that
like
I
I
did
see
some
sig
struggling
with
it
and
I
was
like
man
I
wish
it
would
centrally
report
them.
So
we
can
kind
of
like
trying
to
figure
this
out.
We.
A
Need
to
do
an
audit
too,
which
is
a
little
bit
of
a
pain
but
I
think
Arnold
actually
started
one
I'm
not
sure
how
far
I
need
to
go.
I
get
I
need
to
go,
look
back,
but
according
to
the
shared
calendar,
it
looks
like
I,
don't
know
about
half
of
the
SIG's
have
shared
calendars
and
are
doing
it
correctly
and
then
the
other
half
don't
so.
We
just
need
to
get
them
on
board
with
with
the
other
half
or
create
their
calendars
for
them,
etc,
etc.
So,
if
you,
if.
D
So
the
blog
post
just
went
live
half
an
hour
ago,
excellent
work,
Paris
and
you're.
Getting
that
updated
some
formatting
will
that
also
include
today's
date,
so
it
will
be
xx
instead
of
14
yeah
cool
awesome
registration
is
live
for
Barcelona,
so
send
this
over
to
anyone
that
you
know
that
would
be
interested
in
participating
in
the
contributor
summit,
and
that
includes
sync
face-to-face
for
existing
contributors
as
well.
D
D
So
not
not
a
single
person
gets
stuck
with
the
registration
desk
all
day
and
then
say
face-to-face
facilitation
as
well,
making
sure
that
no
stakes
are
too
loud
or
six
nowhere
to
go
stake
members
and
they
know
where
to
go
and
at
what
time
and
so
on,
so
that
it
should
be
pretty
easy.
So
if
you
want
to
volunteer,
if
you
know
you're
going
and
you
want
to
volunteer,
you
haven't
been
involved
so
far.
Please
let
me
know.
E
And
the
other
next
step
is
to
actually
put
up
registration
for
Shanghai
contributors,
summon
the
so
we're
pulling
that
together
to
do
kind
of
all
at
once.
The
other
thing
that
we're
actually
doing
is
this
Friday,
a
bunch
of
us
who
worked
on
the
new
contributor
workshop
for
multiple
events
are
going
to
get
together.
Go
over.
A
All
right,
sorry
about
that
long
pause,
I
was
taking
some
notes,
all
right,
Thank,
You
Josh
and
go
Shanghai
team.
All
right,
San,
Diego
I,
don't
have
much
luckily
were
in
November.
I
did
set
an
issue
for
the
team.
Building
and
I
do
not
have
the
link
in
there.
So
if
anybody
can
possibly
you
would
be
amazing
and
that's
really
it
for
San
Diego
until
I'd
say
we,
our
next
major
update,
will
probably
be
in
I'd,
say
two
to
three
weeks,
so
nothing
there.
A
So
on
to
our
awesome
project
forward
exercise
we
have
over
160
issues
within
the
kubernetes
community
repository
and
these
are
not
milestone
or
anything
like
that.
I
just
before
I
logged
on
I
checked
the
K
community
repo
and
there's
so
many
in
there
that
still
don't
have
any
milestones
whatsoever.
So
if
anybody
here
has
cycles
today
or
tomorrow
through
the
rest
of
this
week,
that
can
help
us
with
issue
triage,
we
would
greatly
appreciate
it.
A
Nikita
and
I
are
working
on
hopefully
trying
to
build
that
issue
triage
team
within
the
next
couple
of
weeks
and
again.
If
anybody
wants
to
wants
to
help
us,
that
would
be
totally
awesome
before
we
get
started
on.
I
am
gonna
share
my
screen.
Does
anybody
have
any
questions
about
any
of
the
labels
or
any
of
the
or
anything
that
Nikita
mentioned
in
the
email?
Also,
if
you
don't
necessarily
want
to
ask
the
question
publicly,
you
can
always
feel
free
to
privately
DM
me
and
I'll.
Ask
it
on
behalf,
for
instance,
I'll.
A
Let
you
know
I
was
a
little
confused
about
milestones
when
the
heeta
and
I
discussed
like
how
how
we
were
going
to
attack
this
so
just
wanted
to
at
least
throw
a
my
throw
my
confusion
out
there
in
case
anybody
else
is
confused
as
well.
Ask
now
or
forever
hold
your
peace,
otherwise
we're
gonna
get
to
it.
Maybe
Nikita,
why
don't
you
drive
the
car
as
far
as
sharing
your
screen
and
then
I'm
gonna
come
I'll,
come
behind
you
and
start
documenting
and
stuff
like
that
cool.
A
Then,
if
anybody
else
like
I
said
on
the
call
right
now
can
help
us
we're
gonna
try
to
do
sort
of
a
live,
triage,
/,
update
session
right
now
and
it's
gonna
be
a
lot
of
things
flying
around
including
comments
and
stuff.
So
if
anybody
wants
to
jump
in
and
help
us,
that
would
be
much
obliged.
Alright,
Nikita,
take
it.
Okay,.
F
So,
first,
before,
like
going
through
the
project
board,
I
wanted
to
just
look
or
just
skim
through
the
issues
in
the
milestone
that
everyone's
already
added.
So
my
first
question
would
be:
is
anyone
blocked
on
anything
that
they've
already
added
in
the
milestone,
or
they
have
questions
about
issues
here?.
F
Okay,
I'll
take
that
as
a
no
and
the
second
thing,
I
was
wondering
if
we
could
just
like
go
through
issues
that
don't
have
anyone
assigned
and
and
don't
have,
the
Help
Wanted
label
and
just
discuss
if,
like
someone
wants
to
work
on
it
or
if
we
should
be
adding
the
Help
Wanted
label
to
just
make
it
actionable.
Does
that
sound
good?
F
F
A
B
F
F
E
E
A
F
C
A
F
Okay,
moving
on
pre
publish
and
the
some
elite
materials
for
Barcelona
contributors
summit
does
anyone
know,
should
I
also
assign
grin
yeah.
F
H
H
F
F
I
won't
read
through
all
of
this
yet
but
I
think
everyone's
opinion
will
count
here:
I
just
added
it
in
the
milestone,
but
I
don't
know
if
ulis
was
like
there
was
something
being
planned
about
it
from
the
released
inside
or
what's
going
on
with
this,
but
I'm
not
going
to
assign
anyone
to
this.
But
if
everyone
could
have
a
look
and
just
if
you
have
opinions
comment
on,
and
that
would
be
great
sorry
or
does
anyone.
H
Have
anything
to
add
for
this
issue
I've
been
looking
at
it
and
sort
of
mulling
it
over
I
think
I.
Think,
overall,
it's
a
pretty
good
idea
and
we
should
definitely
let
me
go
take
lead
on
it
because
he's
doing
with
the
most
recent
experience.
H
Okay,
I
I,
just
the
only
worry
I
have
is
that
I,
just
I
I'm
always
for
Less
labels,
usually
like
make
a
really
good
case
for
I
mean
a
lot
of
those
labels
were
retired
for
a
reason,
so
I'm
not
entirely
sure.
What's
going
on
here,
I,
just
just
retraining
people
on
how
to
use
labels
is
yeah.
I,
know
I'm
way
in
there.
Okay,.
G
A
F
A
F
Next
assignment
establish
new
github
theme
structures,
so
I
added
this
year,
because
I
was
already
talked
eventing,
something
about
teams
and
the
team
structure.
I
think
there
is
a
little
bit
more
to
this
issue,
but
I
think
we
could
probably
discuss
and
figure
something
out:
I've
added
it
to
the
milestone,
I'm
most
happy
to
assign
it
to
myself,
but
I
think
this
needs
more
of
a
discussion
and
then
figuring
things
out.
Does
anyone
else
have
opinions
on
this
issue?.
F
C
H
We
do
have
information
on
this
in
the
docs
there
is.
There
is
a
large
chunk
of
what
to
do.
If
my
PR
doesn't
get
reviewed.
It
focuses
on
the
contributor
rather
than
on
the
reviewer.
There
is
also
a
section
on
code
review
that
is
a
little
bit
more
generic
and
boils
down
to
you
know,
be
nice,
be
patient,
be
kind,
so
I
would
be
fully
in
favor
of
updating
that
to
the
current
status
or
maybe
putting
it
in
a
more
obvious
location,
but
I
do
know.
We
have
this.
C
There
is
a
doc
that
I'd
wore
and
I
had
worked
on.
That
is
sort
of
just
a
sort
of
a
very
lightweight
cheat
sheet
version
of
this.
The
intention
is
that
it
can
then
be
translated,
like
it's
easy
for
the
docs
team
to
translate.
So
we
can
link
to
other
people
that
where
we
might
not
be
able
to
translate
the
full
guide
sure.
H
Yeah
sorry
I'm,
maybe
I
just
have
a
little
bit
of
and
have
not
enough
context
for
this
I
anyway.
I
think
I
think
it's
great
and
I
just
want
to
make
sure
that
we
take.
What's
there
andö
consideration
and,
if
necessary,
revamp
it
right.
Combine
the
two
because
I,
what
I
just
want
to
avoid
is
having
two
documents
that
cover
similar
things,
because
that's
where
confusion
happens,
yep.
B
F
F
So
this
is
completely
new
for
us
like
doing
all
of
this,
so
I
was
just
thinking
that
we
could
go
through
the
project
with
the
individual
fiber
boards
and
see
if
there's
something
else,
that
someone
like
do
a
small,
regular
stand-up
but
not
like
go
through
each
issue,
or
else
we
could
be
something
else
to
figure
things
out.
Does
anyone
have
suggestions
about
how
we
should
proceed
for
this.
F
Okay,
so
we
have
a
lot
of
project
boards
right
now,
so
I
will
go
through
the
main
country
back
sport
in
the
end,
because,
right
now
it
has
issues
which
are
more
broad
and
umbrella
issue
types
and
really
old
ones
like
audit
owner
files,
and
things
like
that
which
will
it
was
breeches,
probably
not
actionable
at
the
moment,
so
I'm
just
going
to
go
through
the
individual
partial
boards,
and
we
will
see
how
much
we
can
cover
right
now.
So
first
of
the
github
management
project
board,
so
in
progress
right
now,
I
have
so.
F
F
G
Fog,
so
I
want
to
make
sure
that,
like
every
issue,
that's
on
this
board
has
an
area
github
management
label
on
it,
so
I
don't
have
to
search
for
three
different
kinds
of
labels
and
three
different
kinds
of
repos
to
understand
what
other
work
is
not
accurately
represented
on
this
board
and
I
will
work
with
you
and
the
other
github
admins
to
come
up
with,
like
a
consistent
prioritization
to
figure
out
what
we
believe
is
most
important
versus
least
important
to
work
on.
First.
F
F
A
F
A
F
A
F
We
move
it
to
the
end
of
this
column.
Yeah
talk
more
duties
for
YouTube
admins.
Do
you
need
anything?
Your
no
PPR
is
impolite
okay.
We
discuss
about
this
and
github
management
calendar
at
Lyons
creation,
I
think
those
already
appear
open
for
this
yeah
PR
and
flight
auditing
meetings
and
community
calendar.
B
A
B
A
Our
responsibility
to
come
up
with
a
workflow
that
makes
sense
for
everybody,
including
ownership,
but
the
thing
is
we
can't
own
individual
calendars,
the
way
that
I've
put
in
it.
The
way
that
I
put
the
text
into
the
calendar
guidelines
is
like
I
feel
like
the
tried
by
true
method,
but
the
problem
with
that
is
that
you
then
give
access
to
over
five
people
to
edit
your
calendar,
which
means.
H
A
A
B
A
A
Yeah
no
I
know
about
it.
Yeah,
your
your
explicit
is
know
you're
responsible
for
your
own
calendar
creation
and
maintenance
of
it
and
we're
here
to
help
you.
If
you
add
us
to
the
shared
calendar,
we
can
help
you
out
with
things
like
someone
leaving
their
employer
or
whatever
I
think
that's
our
role
here.
I.
E
Mean
the
problem
is
that,
like
I,
would
like
to
have
annexed,
Cuba,
Nettie's
or
owned
account
for
calendaring,
just
because
redhead
has
restrictions
on
calendar
items.
I'm
logged
in
to
my
Red
Hat
calendar
I,
can't,
for
example,
invite
groups
not
at
Red
Hat
to
calendar
items
and
I,
don't
think
I'm,
the
only
one
who
has
that
restriction
yeah.
We
are
various
people,
there's
a
whole
assortment
of
things
like
this.
E
A
Exactly
and
I
feel
like
I
see
how
much
they
I
mean.
We,
we
all
I,
feel
like
our
Sigma.
Every
Wednesday
for
the
most
part,
but
I
feel
like
half
of
our
SIG's
are
so
volatile
with
their
meetings
that
we
would
just
be
just
sitting
here
on
our
keyboards
all
day
messing
with
their
meetings,
so
it
does
I,
don't
know,
there's
got
to
be
a
better
way.
A
I
feel
like
the
best
way
like
I
said,
is
showing,
and
we
just
need
to
get
everybody
on
the
best
way
for
that
to
be
the
best
way,
but
yeah
I'm,
very
down
with
other
people's
thoughts
on
automation
like
we
do
have
the
G
suite
API
at
this
point.
So
if
folks
have
experience
with
that
by
all
means,
let's
work
on
something
yeah.
B
B
Like
whatever
way
we
decide,
is
fine
I
just
want
to
make
sure
that
we
have
everything
that
there's.
No,
that
there's
no
ambiguity,
ambiguity
on
who
is
responsible
for
what
I,
just
yeah
I'll.
A
Say
that
we're
responsible
for
the
shared
calendar
only
yeah
see
okay,
cool
all
right.
Sorry,
Nikita
go
ahead!
No.
F
A
But
that
the
individual
sig
calendars
are
powering
the
community
calendar
right
right.
So
we
have
to
audit
to
make
sure
that
they're
that
they
have
like
the
right
tag
on
their
meeting
ID.
We
have
to
make
sure
that
they
have
a
shared
calendar.
We
have
to
make
sure
that
we're
on
it
for
edit
rights,
so
I
just
I
see
the
audit
as
like
three
things
essentially
like
are
we
do
we
have
capability
to
edit
their
meeting?
Do
they
have
a
shared
calendar
and
then
are
they
on
the
shared
calendar?
Okay,.
A
A
My
calendar
I
feel,
like
that's
very
I,
feel
like
that's
very
explicit
now
in
the
safe
working
group
document.
Okay,
extremely
explicit:
it
says
you
create
your
calendar,
you
do
these
things.
You
do
that.
Okay,
so
I'm,
like
I,
said
I'm
gonna
put
in
our
Charter
that
the
in
scope
is
the
shared
calendar
and
out
of
scope,
is
the
individual
entries
that
power
it
yeah
yeah
all
right,
shared
calendar
already.
B
A
Like
I
also
have
a
very
hot,
take
I
feel
like
our
leg.
After
doing
all
of
this
community
maintenance
stuff
with
calendars,
zooms
all
of
the
resources,
I
think
when
we
have
a
Sager
working
group
that
bubbles
up
I
think
we
should
do
it
all
for
them,
because
me,
the
next
one
meaning
yeah,
meaning
like
create
their
community
meeting
for
them,
create
their
shared
calendar
for
them,
create
their
zoom
for
them,
create
everything
and
then
hand
off
their
passwords
and
some
kind
of
secure
method
like
signal.
A
A
I
think
it
would
save
us
a
lot
of
time.
I
think
it
would
take
us
a
lot
of
time.
I
think
it's
gonna
take
us
at
least
three
hours
to
like
set
up
a
cig,
at
least,
but
at
the
same
time,
like
I,
said
three
hours
versus
six
months
on
the
zoom
audit
is
pretty
substantial,
I
think
when
we're
talking
about
the
hours
of
yeah
exactly
three
hours
once
yeah,
so
I'm,
actually
gonna
file,
an
issue
right
now
put
on
other
note
file
issue
discuss
can
try
that
taking
over
sig
lifecycle.
F
H
A
F
F
I
A
Process
and
millions,
no
I,
think
we're
I
mean
I
feel
like
we're
sort
of
rolling
I
mean.
Maybe
we
should
put
blocked
4G
suite
until
CN
CF
gets
back
to
us,
because
that's
kind
of
where
we
are
so
ya
know
I
would
say:
let's
put
G
suite
in
the
blocked
and
I'll
comment
that
were
blocked
on
ciencia,
okay,.
A
A
So
we
just
want
to
get
somebody
on
the
phone
looks
like
we
pay
for
this
service,
and
people
at
Google
won't
talk
to
me
because
I'm
not
Linux,
Foundation
and
folks
have
ethics.
So
that's
cool
too,
but
I
don't
know
or
maybe,
if
you
can
put
me
on
the
account
as
someone
that
can
talk
about
it
and
then
Google
can
talk
to
me.
I
just
feel
like
we're
just
kind
of
shooting
ourselves
in
the
own,
our
own
foots,
because
we
have
this
as
a
service
and
we're
not
using
it.
A
C
A
It
was
splain
which
it
still
works
and
we're
still
using
it
on
certain
SIG's.
The
problem
is
that
the
problem
is
that
they
failed
on
Cluster
lifecycle
because
they
want
their
meetings
posted
right
away
and
unfortunately
we
don't
have
a
YouTube
team
large
enough.
For
that
I
mean
we
need,
like
a
team
of
pretty
much
10
YouTube
folks
to
get
the
service
levels
that
some
of
our
SIG's
would
need.
In
order
to
do
that,
because
splain
I
mean
we
would
still
need
some
kind
of
trimming,
even
though
spleen
has
definitely
gotten
better
on
the.
A
If
you
press
the
record
button,
it
starts
there
so
like
that
functionality
has
been
fixed,
but
there's
still
other
quirks
that,
like
you,
need
a
human
on
the
other
end
for
meaning
like
the
to
assign
it
a
playlist
and
things
like
that
and
then
ultimately
publish
it.
So
like
I
feel,
like
the
automation
piece,
is
smooth
and
awesome
again,
it's
just
the
end
piece.
A
That's
not,
and
until
we
can
get
a
YouTube,
a
youtube
team
in
place
actually
yeah,
let's
block
it
on
the
YouTube
team,
well
block
it
on
the
YouTube
team,
and
until
we
get
that
in
place,
then
we
can
come
back
to
that
and
then
the
YouTube
team
can
figure
out
the
automation
needs
sweet
delegation.
Sorry
Oh.
A
Content
strategy
for
the
contributor
site
that
I'm
about
to
go
really
hard
on
I'm
done
all
the
my
analysis,
so
I
just
need
to
update
it.
I
need
to
talk
to
me
again
about
Megan
Bruce
with
VMware
about
the
focus
groups.
I
think
she's
also
lost
touch
just
based
on
busy
schedules,
nothing
detrimental,
so
we
just
need
to
get
back
on
the
horn.
With
this,
the
major
thing
that
we're
missing
and
I'm
sure
George
can
can
pipe
up
on
this
I
think
it's
kept
sand
and
Josh
I
know
you're
on
the
line
too.
A
I
think
the
entire
intent
for
the
kept
itself,
or
they
kept
for
the
contributor
site
itself,
was
kept
period,
but
kept
seemed
to
be
still
in
a
not
great
state
of
affairs
as
far
as
like
displaying
information
is
concerned,
so
I
feel
like
for
what
we're
doing
right
now
for
the
content
strategy
is
thinking
of
other
things
that
we
had
put
up.
In
addition
to
that,
since,
like
the
kept
scene
is
still
a
little,
not
wonderful
Josh,
do
you
want
to
talk
a
little
or
George?
A
E
A
B
E
H
E
E
The
so
you
know
at
some
forum
we
need
to
look
at
moving
caps
to
some
format
other
than
a
file
tree,
and
so
doing.
Something
like
saying,
hey,
we're,
gonna,
have
more
intelligible
display
of
caps
on
the
contributor
site
requires
us
to
enable
more
intelligible
display
of
caps
at
all,
which
is
currently
not
the
case
and
needs
to
be
led
by
Vice
Adm
as
I
understand
it.
E
A
Sorry,
I'm
taking
notes
and
I
think
the
heat
is
too
probably
all
right.
Yeah
so
I
feel
like
for
this
one,
we'll
just
go
ahead
and
keep
it
I'm
gonna
milestone,
May
it
because
I
feel
like
for
what
the
what
the
issue
was
set
for,
which
was,
let's
get
just
an
MVP
of
content
that
we
want
ready
to
go
lined
up.
I.
Think
we
can
achieve
this
based
off
of
based
off
of
what
I
know
now,
so
I
will
go
ahead
and
milestone
natus,
okay,.
F
F
B
F
B
Working
group
closing
down
process
sounded
good
when
I
wrote
it,
but
it's
like
it's
like
too
verbose.
We
should
be
like
optional.
You
could
post
it
if
you
want,
but
if
you
don't
post,
we're
still
gonna
close
the
working
group
anyway,
like
not
block
on
yeah.
So
that's
my
bad
for
the
convoluted
process.
I,
don't.
A
B
So
in
hindsight,
the
whole
work
group
creation
brought
like
all
these
work
groups.
Have
we
been
closing
or
ones
where
everyone's
like
you
get
a
work
group
and
everyone
gets
a
work
group
and
like
no
one
thought
it
through
I.
Think
from
now
on,
the
last
few
ones
that
we've
created
have
like,
like
LTS,
took
its
time
like
doing
it
right
and
all
that
stuff.
B
F
C
F
A
A
A
Just
because
I
feel,
like
other
people,
might
and
can
do
those
things
and
I've
heard
from
a
couple
people
that
if
they
see
my
head
on
it,
they
don't
touch
it
so
I
removed
I
removed
my
head
in
hopes
that
other
folks
will
help.
But
the
stuff
in
progress
is
mostly
like
vanity
edits
so
like
meet
our
contributors
for
YouTube
needs.
A
thumbnail
created,
I
created
one,
but
it
needs
yet
another
one,
because
information
has
changed
and
then
like
need
to
figure
out
some
kind
of
transcription
I,
don't
know.
A
If,
like
we
go
with
office
hours,
I,
don't
know
I,
just
I
guess
we
need
to
figure
that
out,
but
that's
like
sort
of
an
immediate
need
and
then
also
clip
out
some
more
good
questions
like
we
had
for
the
code
base,
tour
and
things
like
that.
So
that's
someone
else
and
then
documentation
changes
for
me
to
our
contributors
and
the
group,
mentoring,
automation
and
formation.
A
That's
sort
of
okay.
We've
got
people
that
said
that
they
are
interested
in
group
mentoring
for
a
certain
thing
and
they're
interested
in
a
certain
level.
What
now,
how
can
we
automate
that
process
so
that
they
can
self
they
can
self
form
and
that
they
don't
necessarily
need
us,
because
what
I
was
doing
for
the
group
mentoring
is,
is
like
hand,
picking
people
off
of
a
list
and
then
like
forming
them
into
a
thing
and
then
setting
up
their
resources
so
like.
A
Essentially,
how
do
we
self-service
this
and
I'm,
hoping
that
I
can
wrangle
Josh
into
this
I
politely
asked
him
the
other
day
and
by
politely,
I
was
like
you're
doing
so
that's
pretty
much
everything.
That's
I
feel
like
in
progress.
As
far
as
sweet,
our
contributors
and
group
mentoring
is
concerned,
and
then
everything
else
is
mostly
backlogged.
Actually
I'm
gonna
take
the
code
based
tours
and
put
them
in
the
in
progress
and
then
I'm
also
gonna
to
the
how-to
for
me
meters
in
progress
as
well.
A
F
A
A
Those
updates
during
the
regularly
scheduled
program,
stuff
and
I
feel
like
just
for
my
open
mic
topic
for,
like
30
seconds
I'd
like
to
see
us
to
a
point
where
these
sub
project
boards
have
their
own
meetings,
and
then
we
all
collect
here
bi-weekly
and
we
do
like
project
some
project
stand-ups
and
it
open
mic.
So
I
don't
know
what
everybody
else's.
Thoughts
are
on
that,
but
I
feel
like
now
we're
starting
to
kind
of
see
more
and
more
divisions
of
flavor
and
who
owns
what,
with
the
project
and
stuff
like
that.
A
A
A
B
A
Good
I
don't
know,
I
feel,
like
we've
been
inching
closer
and
closer
to
this
result,
like
I
mean
we
started
like
hey,
we've
got
a
project
board.
This
is
a
thing
and
now
here
we
are
we're
all
growing
up
and
we
have
like
nine
project
boards
and.