►
From YouTube: Kubernetes SIG Contributor Experience 20180912
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
Hi
everybody
welcome
to
contributor
experience.
My
name
is
Paris.
Today
is
Wednesday
September
12th,
it
is
9:35
a.m.
Pacific
time
and
we
have
a
wonderful
plethora
of
contributors
with
us
in
multiple
time
zones
today.
Thank
you,
everybody
for
joining,
so
we
do
have
a.
We
do,
have
a
note-taker
LLC.
Just
did
that
and
then
I'm
going
to
be
assigning
Christoph
the
co-host
duties
thanks
crystal
and
that
is
spent
alright
and
then
I'm
gonna
fix
our
ins
share,
screen
settings
really
quickly
and
then
done
that
all
right
and
then
first
things.
A
First,
you
have
a
code
of
conduct
that
we
abide
by,
that
is
under
the
ciencia
umbrella.
The
TLDR
there
is,
please
be
excellent
to
each
other.
Also,
if
you
do
have
something
to
say,
just
raise
your
hand
if
somebody
from
the
middle
of
speaking
and
one
of
us
will
see
it.
I
have
everybody's
pretty
avatars
and
faces
on
my
screen
right
now,
so
I
should
be
able
to
see
you
with
your
hands
up
and
then
first
things.
A
Small
second
thing:
now:
do
we
have
any
new
contributors
on
the
line
that
have
never
been
on
this
call
before
that
would
like
to
introduce
themselves
and
I
think
I've
seen
most
of
our
regular
folks,
Zack
puppet
I.
Don't
believe
I
have
seen
you
in
here
before,
if
you'd
like
to
introduce
yourself
feel
free.
If
not
don't
worry,
we
can
always
come
back
to
that
or
again,
don't
feel
free
to
introduce
yourself.
A
Next
we
have
the
next.
We
have
the
office
hours
community
meeting
and
meet
our
contributors
kind
of
check
in
and
make
sure
everything's
good.
There
I
think
a
room
is
doing
the
community
meeting
tomorrow.
George
has
had
an
off-site
this
week,
Jeff
you're
doing
the
livestream
correct
all
right,
everything's
been
with
you.
All
right
sounds
like
everything
was
good
with
the
room
when
I
checked
with
him
he's
not
on
the
tall
right
now
or
by
their
office
hours
these
next
week,
Jeff
you're
also
gonna
be
a
part
of
that
too
right
Bob,
you
as
well.
A
Then
meet
our
contributors
were
really
good
with
meet
our
contributors
right
now,
but
if
anybody
on
the
table
would
ever
like
to
attend,
come
on
feel
free,
we
have
like
one
or
two
slots
available
for
most
times
and
that
happens
again
on
the
first
Wednesday
of
every
month
and
that's
kind
of
a
contributor
AMA,
but
the
last
month
that
we
had,
which
was
last
week,
we've
already
seen
over
a
hundred
views
on
both
sessions,
which
is
scaling,
and
that's
amazing.
So
I'm
super
happy
about
that.
A
So
thanks
everybody
that
has
put
time
into
both
the
community
meeting
office
hours
I
meet
our
contributors,
I
think
our
program
so
Iran
that
are
really
starting
to
be
full
steam
ahead.
All
right,
Oh,
exactly
did
Chad
haven't
set
my
makeup
yet
I
work
with
going
to
beer
and
just
listening
in
today,
hey
Zach,
sorry
to
put
you
on
the
spot,
but
feel
free
next
time
when
you
get
your
mic
come
on
in
and
introduce
yourself
actually.
A
So
nice,
to
have
you
and
so
good
to
hear
that
Gwen
is
your
coworker.
She
will
be
an
excellent
person
for
you,
two
to
get
plugged
in
with
all
right.
So
Lucas
said
that
the
project
board
link
is
not
working.
It
works
for
me.
I
know
that
there's
been
some
github
issues
within
the
last
couple
of
days
with
certain
I
think
like
sleeps
and
regions
and
stuff
going
down,
so
it
could
be
just
a
temporary,
giving.
A
A
Alright,
no
sorry
I've
been
having
github
issues
all
week,
so
I
thought
maybe
was
just
tied
to
that.
Alright,
so
I
had
been
filing
my
life
away
with
issues.
Also,
if
you
see
humongous
issues
blowing
in
that's
kind
of
what
I've
been
doing
so
right
now,
I
have
the
only
thing
that
we're
blocked
on
is
the
communication
and
collaboration
platform
sprawl
and
that
we're
actually
not
blocked
anymore.
We
were
blocked
with
the
survey,
but
now
that
the
survey
is
gone
out,
we
are
going
back
to
in
progress,
for
that.
A
Know,
oh
my
gosh
things
are
slowly
flowing
and
how
weird
awesome
very
cool
all
right,
and
then
there
are
some
help.
Wanted
labels
good
first
issue
labels
in
there
as
well.
So
if
you
hear
of
other
new
contributors
that
are
looking
to
contribute
outside
of
code,
definitely
feed
them
to
feed
them
sounds
kind
of
weird
but
feel
free
to
have
them
come
over
sauce.
A
Some
things
that
we're
doing
that's
in
progress
right
now.
They
we
should
definitely
talk
about
on
this
call
things
like
the
steering
committee
election.
For
those
that
don't
know.
No,
we
are
having
a
election
right
now
with
the
steering
committee
for
three
different
seats
that
are
up
for
grabs
this
year,
based
on
their
term
limits,
and
that's
the
current
committees
term
limits.
A
This
Friday
is
the
next
deadline
and
that
deadline
is
for
people
who
would
like
to
nominate
either
themselves
or
other
people,
and
then
also
candidate
buyers
will
be
starting
to
flow
into
the
voters
guide
as
well,
and
then
the
eligible
voter
exception
form
as
well.
So
the
steering
committee
this
year
has
determined
that
50
contributions
or
more.
It
means
that
you
are
eligible
to
vote
for
this
year
in
committee
positions.
A
There's
a
voters
MD
file
in
the
election
folder,
that's
under
events
in
the
cake
community
repo
and
feel
free
to
look
up
your
handle
there
and
then,
if
not
feel
free
to
fill
out
the
exception
form
if
you
feel
like
you've
made
at
least
50
contributions
and,
yes,
they
do
come.
They
do
count
non
contributions
as
well,
but
of
course,
easiest
way
for
us
to
collect
metrics
into
github
events.
So
that's
why
we
have
the
forum
is
for
for
those
times
when
you've
contributed
that
just
unfortunately
did
not
generate
and
github
of
that.
A
That's
right,
verge
on
vacation,
I
didn't
hear,
call
me
Josh,
hi,
Josh
seniors.
The
I
did
decide
to
start
also.
Finally,
issues
for
all
of
our
events.
That's
one
of
the
areas
that
I
think
we've
really
lacked
with
issues
and
people
don't
know.
What's
going
on
a
lot
of
the
time
with
her
events,
because
we're
just
usually
in
little
subgroups
I
did
not
set
one
for
first
nine
hi
I
set
one
for
China.
A
However,
I
said
in
the
issuer
that
if
Josh
wants
me
to
do,
Shanghai
as
well,
I
will
actually
be
in
that
so
I
figured.
He
might
want
to
be
the
author
of
the
issue
so
feel
free
to
next.
When
you
talk
to
Josh,
asked
him
how
he
wants
to
track
me,
Shanghai,
stop
and
github,
and
if
he
does
and
then
I'm
gonna
update
that
issue
today
for
those
who
are
interested
to
see
what's
going
on
with
the
Seattle
contributor
summit,
we
have
definitely.
A
We
definitely
have
a
little
bit
more
information
this
week,
we're
actually
hoping
I'm
crossing
my
fingers
right
now
to
solidify
the
venue
for
the
first
day,
which
will
be
just
pretty
much
a
dinner
and
then
the
next
day
will
be
ultimately
like
the
big
day
of
work.
If
you
will
it'll,
be
unconfident
all
experience
of
a
feather
workshops
and
then
high-level
a
state
of
type
of
conversations
from
both
army
engineers,
as
well
as
steering
committee
members.
So
that's
how
we'll
be
a
contributor
summit.
It's
ending
laid
out
right
now
and
again.
That
is
in
progress.
C
To
get
in
touch
with
me,
I
am
not
bothered
by
slack
messages.
Please
DM
me
on
slack
it,
especially
since
you
brought
up
github
issues.
They
are
great
for
tracking,
but
they're,
not
really
great,
for
getting
my
attention.
If
you
add
me
on
there
right
now,
I'm,
like
I,
don't
know
it's
it's
like
release
team.
Does
that
to
you
apparently
have
been
warned
about
this,
but
I
didn't
really
believe
it,
but
now
I'm
yeah
anyway,.
A
G
Mean
yeah,
there's
been
so
there's
been
a
whole
flurry
of
work-in-progress
stuff,
that's
kind
of
a
like
somewhat
contraband,
but
also
a
lot
of
its
big
testing.
As
far
as
tightening
up
automation
in
the
kubernetes
orgs,
so
Aaron's
been
kind
of
spearheading.
A
lot
of
this
we've
got
this
week.
Yeah
we
got
tide
running
on
KK.
G
G
Eva,
okay,
basically
works
with
the
process
in
and
the
flow
in
in
the
kubernetes
repo,
as
well
as
all
the
first
process.
Changes
to
work
with
the
automation,
and
now
we
can
have
consistent
automation
across
across
everything
is
been
work
and
I.
Don't
want
to
take
any
credit
for
for
the
things
that
were
like
these
exceptional
individuals
and
that
those
work
that
they've
been
putting
in
for
years.
G
So
that's
been,
that's
been
a
thing.
There's
been
a
lot
of
cycles,
kind
of
going
into
that
and
shoring
up
that
we've
been
from
the
github
administration
team
side.
As
far
as
like
a
contributor
experience,
a
project
we've
been
kind
of
humming
along
as
far
as
working
through
the
processes
of
the
types
of
requests
are
coming
in
now.
G
Those
are
all
funneling
through
us,
as
opposed
to
like
individual,
like
steering
committee
members
going
in
creating
something
ad
hoc,
we're
able
to
kind
of
have
an
established
process
that,
if
we're
gonna
take
like
a
github
administration
action
such
as
creating
a
repo
or
changing
a
repo
setting.
We
are
enforcing
that.
We
want
to
create
an
issue
for
it,
so
that
we're
communicating
internally
between
us
and
anybody
who
wants
to
watch
the
org
repo
inside
of
kubernetes.
G
They
can
see
publicly
the
Evo
act,
the
actions
being
taken
and
that
we
can
do
things
like
follow
up
with
documentation
and
policies
around
things
that
are
happening.
If
we've
come
across
a
request
that
doesn't
have
a
policy
or
it
doesn't
have
documentation,
we
can
market
to
get
that
to
get
that
at
it.
G
G
Yeah,
the
the
only
other
thing
that
I
wanted
to
mention
here
and
III
added
this
to
the
agenda.
The
agenda
item
for
a
github
issue
template
so
in
the
orga
repo
I
tried
out
a
new
github
feature
where
we
can
establish
multiple
different
issue
templates
for
different
issue
types,
and
there
is
a
link
in
the
agenda
as
well
as
what
that
looks
like
for
our
repo.
G
I
just
thread
in
the
in
the
agenda,
so
there's
a
gears,
basically
a
chooser
that
you
can,
when
you
click
on
the
green
new
issue
button
in
the
repo.
It's
like,
hey,
here's,
some
suggested
templates
and
when
you
click
on
one
of
those
templates,
it
pre
fills
out
here's
the
information.
We
need
from
you
to
execute
this
certain
type
of
request
and
that's
been
working
well
and
that's
been
really
helpful
in
the
org
repo.
That
kind
of
acts
like
a
pseudo
ticketing
system
for
fur
for
tracking
actual
github
requests.
G
But
it's
been
working
well
for
us
and
then
notice
that
the
other
day
and
was
like
hey.
We
should
probably
roll
this
out
to
other
repos
like
kubernetes,
and
that
is
a
great
idea.
That
was
something
that
was
always
kind
of
in
the
long-term
but
never
got
thrown
into
an
issue.
So
he
made
an
issue
to
do
that
and
if
people
want
to
help
out
with
that,
there's
there's
some
there's
been.
G
Somebody
who's
already
meant
to
comment
it
on
the
issue
that,
though
they
want
to
like
help
out
and
initially
design
those
templates,
but
there'll
be
PRS,
Macan
stuff.
If
that
is
like
those
issue
templates
again,
if
they
work
out
in
KK
and
tests
infra,
if
there
are
other
repos,
we
want
to
do
that
and
I
think
that's
very
good
and
very
helpful.
I
have
direct
those
direct
those
requests
kind
of
into
a
funnel,
like
hey,
if
you're
filing
this
type
of
request.
G
These
are
the
types
of
information
we
need
from
you
as
well,
as
we
can
do
things
like
you
know.
We
had
on
the
the
current
issue.
Template
is
like
uncommon
one
of
these
for
a
kind
bug
or
kind
feature.
We
can
integrate
those
as
part
of
the
template
so
that
certain
requests
get
auto
labeled
into
a
particular
bucket
at
the
time
of
filing
without
necesitan
somebody
saying
kind,
bug
kind
feature
because
that'll
be
built
in
as
part
of
a
template.
G
There's
a
lot
of
interesting
things
that
we
can
do
there
and
III
think
that'll
be
very
interesting
to
track.
If
anybody
cares
about
that,
go.
Take
a
look
at
that
issue.
Subscribe
to
that
issue.
Take
a
look
at
the
you
know.
Subsequent
PR
is
that
are
filed
because
I
think
that'll
be
cool
for
both
kubernetes
committees,
as
well
as
any
other
repos
that
we
decide
to
roll
this
role
as
how
to
I
think
if
that
works
out
well
for
Carre's
Cabrini's,
it's
also
something
we
should
send
out
to
cig
leads
and
communicate
like
hey.
G
Yeah
I
wanted
I
wanted
to
bring
that
up.
I
don't
have
a
cycle
to
drive
up
if
there
are
people
who
are
interested
in
that.
Go.
Take
a
look
at
that
issue,
because
that
would
be
very
helpful
to
have
other
people
involved
in
that
kind
of
that
wing
of
the
contributor
flow
or
you
know,
other
end
user
flow.
As
far
as
filing
issues.
D
We've
been
doing
this
at
VMware
all
the
open
source
projects
that
we
have
we've
been
adding
github
issued
templates
to
it,
I
put
in
a
link
to
one
of
them
where
we
actually
use
some
emojis
as
well
to
spruce
it
up
a
little
make
it
look
even
even
more
inviting
and
it's
yeah
it's
a
great
thing:
I
love
it
because
it
makes
it
so
much
easier
to
see
what
type
of
issues
were
filing
and
it
makes
it
so
much
easier
for
all
the
contributors
when
they
want
to
do
a
feature
proposal
or
a
bug,
request
or
an
issue.
A
Mean
I
can
definitely
help
to
I.
Think
I'm
gonna
seem
pretty
come
in
as
Kristoff
I.
Don't
have
any
full
cycles,
but
I
have
a
ideas
and
be
helped
work.
So
if
you
want
a
partner
on
that
and
I
know,
Quinn
does
as
well
so
I
know
she
also
doesn't
have
any
cycles
but
I
think
like.
If
we
get
like
three
to
five
of
us,
we
could
probably
get
something
get
something
done.
I
I'm.
D
A
We
can
continue
the
chat
in
the
Select
in
the
contrive
ex
lock
channel
and
then
maybe
able
set
an
issue
today
and
and
get
some
things
going.
I
have
some
ideas,
particularly
around
community
management
and
I'm.
Sure
George
and
ER
will
as
well,
especially
like
the
highly
transactional
stuff
that
we
see
like
getting
a
zoom
account
and
I
mean
like
one
of
the
issues
could
be
like
community
management
desk
related
I,
like.
D
G
A
A
A
Super
high
level-
that's
just
my
brain
again,
going
to
the
like
meet
the
developers
where
they
are
kind
of
thing.
Instead
of
like
having
extra
stuff
float
around
and
workflows,
so
I
just
set
an
issue
actually
on
that.
One
group
on
the
group,
mentoring,
umbrella,
I
think
it
was
just
recently
so
anyway,
Jonas
long
story,
short,
let's
get
in
touch
yeah,
we'll
get
that
done.
Alright,
awesome.
G
A
F
Don't
know
if
you
mentioned
it
or
not,
but
since
people
here
tend
to
maintain
Doc's
really
to
contribute
their
experience,
cherry-pick
requirements
as
mildly
changed,
probably
for
the
better
milestones
are
no
longer
required
for
cherried
things.
If
we
find
we
want
to
do
that,
we
should
add
that
back
in
there
are
technical
reasons.
Why,
apparently,
like
Muslims
were
necessary
because
of
a
technical
way
to
Jade
hug
worked
and
you're
not
required
because
of
the
technical
way
that
tied
works?
F
If
we
want
to
go
back
to
the
world
where
milestones
are
required
for
all
of
these
branches,
we
should
add,
like
a
release,
automation
stuff
for
that
I
have
an
open
PR,
where
I've
gotten
feedback
from
two
of
the
three
existing
patch
release,
managers
and
they're
both
happy
with
that
they
don't
they're
fine
with
it.
I
brought
it
up
at
say,
release
yesterday
and
I
will
bring
it
up
here
again
a
day.
I
think
our
trade
pick
process
could
use
a
lot
of
improving
I'm
tearing
down
all
the
complex
stuff
that
we
don't
really
use.
C
C
A
I
F
C
F
A
G
That's
consistent
with
my
understanding
too,
the
last
time.
I,
don't
think
we
have
any
open
issues
about
changing
those
definitions,
I
think
we're.
We
were
kind
of
locked
in
as
far
as
what
we
have
right
now
and
yeah
Help
Wanted
is
basically
there's
a
commitment
there
like
if
you
apply
Help
Wanted
you're
at
least
going
to
handhold
enough
to
be
hey.
This
is
kind
of
you
understand
what
to
do
and
where
to
go
and
who
to
ask
for
questions.
G
A
So
I
feel
like
just
from
from
those
definitions
that
we
just
discussed
I.
Think
we're
really
good,
like
the
good
first
issue
sent
me
someone
that
doesn't
really
contribute
to
kubernetes
and
then
help
on
it
has
sent
me
current
contributors
that
are
looking
for
projects.
However,
they
needed
to
be
filled
in
with
like
the
overview
in
the
contest,
but
alright
Christophe
for
github,
I,
guess
Aaron
as
well.
Is
there
anything
that
anybody
on
this
call
could
help
you
with
outside
of
what
Aaron
just
mentioned
with
documentation.
A
G
I
think
I
think
there's
a
number
of
like
hey
here's,
a
gap
in
policy
or
a
gap
in
documentation
that
we've
identified
a
need
to
go
and
create
policy
or
create
documentation.
I
think
there's
a
number
of
those
that,
like
Aaron
myself
and
other
people
involved
with
it
have
indicated,
but
we
just
haven't
filed
issues
and
I
I
know:
I
haven't
filed
issues
for
them.
Yet
that
is
something
that
I
can
definitely
go
and
do
so
we
can
either
market
them.
G
F
Returns,
tactically
speaking,
maybe
the
next
thing
I
see
her
Kristof
myself
and
other
members
of
the
admin
team
is
to
stop
inviting
people
manually
and
start
inviting
people
with
our
tool
they're
using
we
had
held
off
on.
That
was
because
beta
was
in
literally
on
the
other
side
of
the
planet
he's
back
now,
but
I'm
about
to
drop
off
into
a
black
hole.
So
I
think
we'll
look
to
do
that
next
week
and
accelerate
our
stuff
and
I'm
kind
of
curious
to
see.
F
A
Awesome
alright,
so
we
are
officially
closing
the
book
on
github
but
related
management
stuff
for
this
hall,
I'm,
going
through
the
backlog
right
now,
and
we've
got
some
really
really
old
stuff
in
here
and
I
wanted
to
see.
If
anyone
had
any
updates.
I
know
some
of
the
folks
on
these
are
on
the
call
right
now,
Aaron,
you
have
removed
direct
right
access
to
this
repo
where's.
That
right
now
looks
like
it's
in
the
light
you
have
a
life
cycle
frozen
on
it
right.
F
So
the
largest
thing
that
is
blocking
that
is
a
nontrivial.
It's
a
it's
a
boulder,
it's
not
a
pebble!
It's.
How
do
we
make
our
release
notes
process
work
such
that
contributors?
Don't
feel
the
need
to
go
through
and
I
guess
I
should
say
like
maintainer
x'
people
who've
been
around
awhile,
don't
feel
the
need
to
go
through
and
edit
other
people's
PR
descriptions
and
at
other
PRS
people's
PR
titles
and
so
on.
Just
to
get
the
release
notes
to
look
right,
that's
kind
of
the
biggest
blocker
there.
F
Also
a
couple
knits
in
the
description
about
how
like
somebody
would
have
to
physically
touch
the
repo
to
create
a
new
milestone.
So
this
is
an
adding
a
milestone
to
label
but
saying
I
want
to
make
the
V
114
milestone,
so
we
can
start
stuffing
issues
into
it.
But
if
the
release,
the
other
thing
is
the
big
big
hurdle.
F
I
thought
something
from
Nikita
about
attempting
to
improve
that
process
somewhat,
but
I
view
that,
as
like
a
quarter
length
thing
unless
somebody
is
willing
to
go
and
try
and
suggest
a
compromise
or
find
a
way
to
reduce
the
set
of
people
who
feel
compelled
to
edit
PR
descriptions
for
cleaner
release.
Notes,
I
personally
haven't
kept
track
of
how
the
release
note
process
has
been
going
through.
This
ongoing
release,
but
like
I,
would
I
would
love
to
hear
feedback
from
those
folks
about
what
could
be
done
to
improve
the
process.
F
So
we
can
get
that
done
very,
very,
very
few.
People
who
direct
write
access
to
kubernetes,
kubernetes
and
then
I
think
that
probably
folds
into
the
broader
policy
thing
that
Christophe
and
I
need
to
write
up
is
our
preference
to
have
as
few
people
as
possible
have
direct
effect,
mr.
EKOS,
so
yeah
that
is
still
open
and
frozen
for
those
reasons
and
I
think
that
is
reflected
in
the
description
of
the
I.
Try
to
sort
of
cross
out
things
as
they're
done
in
the
description
of
that
yeah.
I
A
All
right
and
then
we'll
speaking
of
the
release,
notes,
there's
also
a
super
old
one
in
here
as
well
from
Eric
Paris
like
it
seems
like
40
years
ago,
but
that's
not
really
not
the
case.
It
is
renamed
relief's
note
and
cherry-pick
labels
to
conform.
The
category
subcategory
norm
I
feel
like
this
has
already
been
addressed.
No.
F
It
hasn't
so
we'd
love
to
be
like
the
release
date.
Labels,
like
almost
every
label
that
we
used
to
do
stuff,
has
a
prefix,
slash,
suffix
and
release
notes.
Are
the
exceptions
to
that?
You
have
like
release
note
non
release.
No
action
required
blah
blah
blah
I
would
lump
that
into
the
same.
You
need
or
release
that
process
overhaul.
This
isn't
the
sort
of
thing
that
iterating
on
really
feels
appropriate
for
and
that's
more
of
a
like
the
labels
cleaner
that
way,
yeh
I,
don't
see
a
huge
benefit
to
that
when.
F
G
G
Even
if
they're,
not
the
ones
I
gently
taking
the
action
and
I
don't
know
with
something
the
two
big
ones
there
being
cherry-picks
and
release
notes.
Unless
somebody
has
the
time
commitment
to
say,
like
I
can
at
least
commit
the
time
to
like
explain
to
you,
the
state
of
the
world
and
where
we're
going
and
be
available
to
answer
questions
when
somebody's
willing
to
put
their
name
to
that,
then
I
don't
think
we're
Help
Wanted
yeah.
F
A
All
sorts
of
the
release
team
and
see,
if
there's
anybody
they
can
like,
maybe
any
of
the
shadows
or
any
anybody
that
would
be
willing
to
help
out
with
that
part.
Alright,
well
I'll
just
leave
this
issue
for
another
day
in
there
for
a
while,
anyway,
alright
Aaron
I
know
you
didn't
put
anything
on
the
agenda.
Do
you
have
anything
that
you
wanted
to
discuss
outside
of
they
gave
up
stuff
that
you've
already
mentioned.
H
F
A
Aaron
with
your
steering
committee
hat
on
I,
have
not
the
one
thing
that
I
have
not
been
following
with
steering
committee
is
working
group
stuff
in
like
clarification
and
like
requirements
specifically
like
the
requirement
of
having
a
sig
sponsor.
Has
it
has
there
been
any
clarification
around
that
or
any
work
done
there?
No.
F
J's
put
together
a
proposed
Google
Doc,
which
I
was
going
to
move
into
pull,
request
form
and
go
from
there,
but
been
wedged
behind
a
bunch
of
other
things.
I
suspect,
if
I
put
it
in
all
requests
form.
Many
more
opinions
will
form.
So
it
requires
attention.
So
if
it
was
like
I,
that's
why
I'm
not
sure
I
can
just
hand
it
off
to
you
to
mechanically
turn
into
a
pull
request
and
then
just
shove.
It
through,
along
a
similar
front
I've,
been
trying
to
get
the
steering
committee
to
enumerate.
F
Criteria
for
a
sink
or
working
crew
to
retire,
whatever
you
want
to
call
it
disband,
mercs
on
set,
and
so
far
that
also
seems
to
me
to
be
queued
up
or
discussion
rather
than
iterated
on
the
docks
we
might
get
to
that
today
were
one
person
away
from
not
having
enough
quorum
to
meet
today,
but
I
think
we're
pretty
clear
on
the
fact
that
the
steering
committee
just
wants
to
enumerate
the.
Why
and
then
we're
free
to
let
y'all
move
on
the
details
of
how.
F
A
A
Why
is
because
the
community
meeting
we
wanted
to
start
having,
potentially
working
groups,
come
in
and
give
updates,
and
things
like
that
so
and
then
all
their
various
community
management
topics
and
and
things
like
that.
So,
but
if
it's
not
a
requirement,
a
sig
sponsors,
a
working
group,
then
I,
guess
that
wouldn't
be
needed.
So
hey.
F
I,
don't
know
if
that's
a
requirement
be
tangled
up
in
this
discussion
is
a
strong
opinion
that
many
working
groups
should
not
actually
exist.
They
should
be
temporary
and
just
become
sub
projects
of
other
things,
but
I've
worked
yeah
I
agree
with
you.
There
definitely
some
working
groups
that
span
I'm,
also
tangled
up
in
this,
is
the
group
of
people
who
want
to
work
on
moving
project
infrastructure
from
people
over
to
the
CN
CF.
F
F
Agree
another
model
that
was
proposed
is
the
release
team,
because
the
release
team
is
a
group
of
people
that
like
comes
together
and
then
disbands
and
comes
together
in
dis,
pants.
That
to
me,
sounds
like
a
sub-project
of
sake,
release
and
that
sort
of
direction
I
heard
Stephen
Augusto's,
taking
it
for
their
Charter,
but
because
it
sounds
like
a
working
group.
That
brings
us
back
to
what
is
a
working
group
and
can
we
pin
down
what
needs
to
happen
for
to
be
created
and
what
should
its
Charter
be
in
motion?
Its
governance
policies?
H
A
A
I
mean,
like
that's,
obscene,
there's,
there's
areas
of
it
that
are
a
little
ambiguous,
but
I
mean
to
me
when
I
read
the
policy
when
I
read
the
working
group
governance,
it's
pretty
much
like
it's,
it's
a
temporary
thing
and
you
don't
own
any
code
and
like
a
cig
should
and
that's
where
it
kind
of
gets
ambiguous.
This
thing
should
sponsor
you
kind
of
thing
right.
A
And
that's
why
me
like
I
think
like
if,
if
we
just
all
the
steering
committee,
we
need
to
do
essentially
it's
just
like
changed.
Some
of
those
words
like
should
and
and
maybe
insert
more
for
clarity
purposes
or
something
like
that
anyway.
So
yeah,
no
I,
think
I've
got
a
couple
items
on
the
backlog
that
relate
to
working
group
policy
and
stuff,
like
that.
So
all
right
and
then
anybody
else
have
anything
to
add.
For
today.