►
From YouTube: [SIG ContribEx] Weekly Meeting for 20220928
Description
[SIG ContribEx] Weekly Meeting for 20220928
A
Hello,
everyone
welcome
to
the
September
28th
meeting
of
Sid
contributor
experience
for
the
kubernetes
project.
A
This
is
an
official
meeting
of
the
kubernetes
project,
so
it
is
under
the
kubernetes
code
of
conduct,
so
please
be
excellent
to
each
other
and
with
that,
let's
get
started
I
everybody
that
we
have
in
the
meeting
today
is
a
regular
contributor,
so
I
think
we
can
skip
introductions
the
and
given
that
let's
move
straight
into
events
so
which,
because
Bob
is
not
here,
we're
not
going
to
discuss
the
contributor
Summit
unless
somebody
else
unless
he
designated
somebody
else
to
take
that
up.
A
Yeah
cop
is
open
for
the
contributor
Summit.
The
have
you
been
getting
submissions
for
that.
Do
you
know.
A
A
Now
we,
we
have
a
contributor
commas
problem
in
that
we
can
currently
have
registration
for
the
summit
cfp
for
the
summit
and
the
steering
election
open
at
the
same
time,
speaking
of
which
I
need
to
put
the
steering
election
further
down
in
the
agenda.
A
So,
okay,
so
community
meeting
Laura.
D
We're
not
going
to
have
a
community
meeting
for
this
month
because
kubecon
in
case
anybody
didn't
know
that
was
coming
just
you
know
thought.
But
where
is
that
I?
Don't
even
know
I
don't
even
know?
What's.
D
Worry
my
hotel
is
booked
and
my
tickets,
so
don't
worry,
I
will
be
there
I'm
just
teasing
y'all
anyway,
so
yeah
we're
not
gonna,
have
a
community
meeting
this
month,
but
the
new
tags
are
ready,
so
big,
huge
gigantic,
shout
out
to
madhee
for
getting
all
of
that
out
and
going
and
chasing
that
to
the
Finish
Line,
so
huge
shout
out
there.
I
do
want
to
sync
with
marketing
about
how
to
get
that
socialized.
D
If
y'all
want
a
blog
post,
an
email
or
whatever
I
need
to
know
where
who
do
I
talk
to?
Where
do
I
go
so
I
will
catch
up
with
you
all
about
it.
Those
are
like
the
main
updates,
so
questions
comments,
pillow,
throwing
screaming
yeah.
A
Plus
one
and
blog
post,
particularly
the
blog
post,
should
address
what
sort
of
items
should
people
be
flagging?
Okay,
because
I
think
that's
that's
going
to
be.
The
number
one
is
that
people
are
just
really
not
gonna
know
right
right.
A
So
the
yeah.
A
Sounds
good
and
the
the
other
place
I
would
socialize
it
with
believe
it
or
not
is
enhancement,
sub
project
and
the
release
team,
because,
if
anybody's
going
to
come
across,
say
features
and
changes
that
require
community-wide
discussion,
that's
them.
B
A
A
So
the.
C
A
C
A
Type
that's
good
okay,
yeah
is
that
is
that
the
cncf's
mentoring
working
group
is
getting
underway
with
a
lot
of
the
same
sort
of
you
know,
concerns
and
needs
that
we've
had
from
entering,
and
so
the
extent
to
which
we
can
coordinate
with
them.
A
It
might
actually
reduce
effort
like,
for
example,
one
of
the
things
that
we've
talked
about
doing
for
quite
a
while
is
assembling
a
sort
of
rotating
and
constantly
updated
set
of
internship
opportunities
that
can
just
be
reused
across
the
various
internship
programs,
so
that
we're
not
hunting
for
those
individually.
Every
time
it
becomes
a
deadline
for
Google
summer
code
or
Outreach
or
whatever
the
at
the
same
time
we
actually
need
to
recruit.
A
We
probably
want
to
recruit
coordinators
for
each
program,
ideally
people
who
are
not
already
pulled
in
five
different
directions
for
other
things,
the
so
like
to
have
one
volunteer
coordinator
for
outreaching,
and
we
actually
have
somebody
who's
volunteered
that
we
need
to
follow
up
with
to
plan
next
outreachy.
A
A
A
A
A
A
So
the
so
yeah,
so
that
would
be
it,
and
the
thing
is
that,
if
somebody's
doing
one
program,
it's
a
very
minor
time
commitment
from
that
perspective
well
and
then
they
would
also
be.
You
know
one
of
order,
the
admin
for
that
program,
and
so
that
would
be
a
little
bit
more
of
a
commitment
when
the
internship
is
going
on,
because
the
admin
is
kind
of
the
backup
person
when
things
go
wrong.
E
Yeah
but
yeah
a
few
months
back,
you
know
me
and
Paris.
We
documented
a
particular
role
for
this
by
this
didn't
go
up
as
plan
because
we've
been
fine
folks,
foreign
applications.
E
So
with
that,
it
will
be
easier
to
try.
You
know,
rather
than
just
having
a
post,
but
not
having
a
calendar
would
also
not
help
us
with
this.
E
So
I
think,
let's
plan
with
the
initial
forms,
you
know
that
we
are
starting.
We
are
looking
forward
for
people
and
then
start
with
you
know
initial
discussions
and
have
a
chat
at
the
early
Charter.
Maybe
we
could
keep
that
a
place
in
our
contacts,
Report
with
mentoring,
things
mm-hmm.
A
E
Let's,
let's
walk
with
bombs,
I
guess
I
can
draft
a
consent.
We
could
send
it
out
by
this
week
or
by
next
week.
Regarding
this
and
let's
get
folks
and
started
foreign.
A
Okay
sounds
good,
did
I.
A
The
I
mean
we
should
work
with
our
volunteer
for
outreach
e
and
and
get
them
set
up
and
and
working
on
being
ready
for
next
outreaching
cycle.
B
A
C
A
Would
be
number
one
to
find
out
that
if
it's
happening
and
who's
running
it.
C
The
the
group
mentoring
event
at
kubecon,
yeah
cncf,
runs
that
I
think
I
can
ask
and
yeah
one
of
the
channels.
C
A
A
Okay
Noah:
could
you
take
on
communicating
with
Wendy
yeah.
C
C
A
The
okay
Community
Management,
moving
on
steering
election
steering
election
is
still
voting,
is
still
open
through
effectively
Thursday
night
I.
Think
yeah
anywhere.
A
And
last
I
heard
from
no
voting.
Numbers
have
been
very
low,
oh
boy,
because
then
this
might
be
our
lowest
turnout
for
any
steering
election.
So
far,
so
please
use
your
individual
social
media
to
remind
people
that
that
steering
voting
is
currently
going
on.
A
A
The
sometimes
wonder
if
we've
taken
the
no
campaigning
rule
too
far.
A
B
I'm
here
today,
I
haven't
been
able
to
join
for
the
last
like
month
or
two,
because
I
had
a
a
meeting
that
kept
that
was
like
recurring
on
top
of
this
one,
so
I
finally
got
them
to
move
that
meeting.
So
I
will
be
here
now.
B
Anyway,
thank
you
so
much
Josh
for
asking
me
to
come
in
and
talk
about
the
new
roles
that
we're
creating
in
the
comms
team.
Also,
as
we
mentioned
earlier,
we
do
have
a
channel
now.
So,
if
you
ever
need
to
reach
us,
you
can
find
us
in
Sig
contribexcoms,
so
definitely
reach
out
to
us
there
for
the
roles.
I
was
wondering
if
I
could
share
my
screen
so
that
I
could
show
folks
the
all
the
different
pull
requests
that
we
have
open.
B
But
essentially,
we
have
four
roles
that
we
are
newly,
creating
we've
been
going
over
a
a
process
over
the
last
several
months
like
six
months
or
something
more
than
that,
probably
where
we've
been
trying
to
figure
out
what
roles
for
our
team
should
be
today.
B
So
previously,
when
the
role
when
the
the
team
had
first
been
started,
we
have
we
had
a
concept
of
roles
and
we
had
some
defined
roles
based
on
what
we
thought
the
team
would
be
when
it
was
created
over
time.
They
kind
of
got
meshed
together,
and
there
were
a
few
of
us
that
were
regular
members
of
the
team
and
we
were
all
kind
of
just
doing
everything.
B
B
So
we
got
rid
of
the
roles
and
we
replaced
it
with
a
concept
of
a
marketing
Council
to
more
accurately
reflect
reflect
how
we
were
actually
running
things,
but
then,
to
our
surprise,
we
actually
had
a
lot
of
people
join
the
group
and
they
all
wanted
to
get
involved
with
roles
and
have
a
way
forward
with
greater
ownership
within
the
group.
B
So
we
did
again
need
roles,
but
we
needed
to
redefine
them
for
how
our
team
was
actually
working.
So
over
the
last
several
months
we've
been
going
through
this
process
where,
every
week
we
talk
about
the
work
that
we
are
doing
and
discuss
what
roles
we
need
to
have
ownership
over
those
types
of
tasks.
So
at
this
point,
we've
finally
come
up
with
four
or
five
rolls
I.
B
Think,
there's
probably
one
more
that
we'll
need
to
create,
but
we
have
four
that
are
either
in
or
out
for
review
the
first
one,
the
social
media
lead
role
is
actually
in
already
that's
why
we
don't
have
that
one.
Yet
it's
in
the
marketing
team
role,
handbooks
area
did
somebody
get
that
yet
I'm
grabbing
that
link
now?
B
Okay.
So
now,
in
the
the
chat
or
in
the
notes,
there
should
be
links
to
all
of
the
different
roles
and
I
can
share
my
screen.
No
I
can't
okay,
then
we'll
just
talk
about
it.
So
if
you
go
to
the
first
link,
you'll
see
the
social
media
lead
role.
This
was
a
role
that
we
had
before
the
marketing
Council
and
now
have
again
after
I've,
actually
just
been
working
on
updating
that
role.
B
When
we
decided
to
move
to
the
marketing
Council,
so
I
had
something
to
go
off
of
and
we
still
haven't
updated.
B
The
main
marketing
team
page
with
like
here
are
the
roles
and
here's
who's
doing
them,
because
we're
still
going
through
the
process
of
creating
them
all,
but
I
think
I'm,
probably
going
to
be
the
lead
for
this
one.
We'll
talk
about
it
in
our
group.
B
We
also
need
to
update
our
Charter
with
new
information
about
the
rules,
but
basically
the
social
media.
Lead
role
is
responsible
for
making
sure
that
things
are
going
well
with
the
Kate's
contributors.
B
Twitter
account
making
sure
that
any
tweets
that
need
to
get
written
are
getting
written,
making
sure
that
they're
going
out
on
a
timely
fashion,
helping
anyone
new
who
wants
to
contribute
to
Twitter,
making
sure
that
they
have
access
to
the
tools
making
sure
that
they
know
how
to
use
them
all
of
the
kinds
of
stuff
related
to
our
our
Twitter
account
and
the
next
role.
What
do
I
have
next
on
the
list
is
blogging
lead
yeah,
so
this
was
probably
the
the
most
recent
one
that
we
came
up
with.
B
We
realized
that
we
were
doing
more
work
on
blogging
than
maybe
we
have
in
the
past.
We
have
had
this
Sig
spotlights
task
concept,
where
that's
like
an
ongoing
task
for
us.
Anyone
new
who
joins
the
team.
It's
a
good
good
first
issue,
kind
of
thing
where
they
can
interview
Sig
chairs
and
create
a
blog
post,
so
that's
popular
for
new
folks
to
get
involved
with,
but
they
often
get
intimidated,
and
it
requires
a
good
amount
of
guidance
to
help
them
understand
how
to
do
that.
B
We
do
them
for
events,
we
do
them
for
all
kinds
of
things,
and
this
actually
does
also
involve
collaboration
with
the
Sig
docs
blogging
sub-project.
So
there's
a
number
of
things
here
to
manage.
Helping
new
folks
understand
how
to
write
blogs,
making
sure
that
we
have
good,
up-to-date
documentation
on
how
to
write
blogs,
coordinating
all
the
various
projects
that
need
blogs
and
coordinating
with
Sig
Docs.
B
So
we
have
someone
in
the
group
who
has
been
doing
an
incredible
job
with
a
lot
of
those
components
and
has
kind
of
brought
a
lot
of
those
components
to
our
attention.
So
we
asked
him
Frederico
to
take
on
writing
a
new
lead
role
to
take
on
those
types
of
responsibilities.
So
you'll
see
that
there
is
a
pull
request
there,
which
I'm
hoping
to
go
through
these
a
little
bit
later
today,
since
I'm
talking
about
them
anyway
and
put
my
LG
TMS
and
approvals
on
them.
B
The
blogging
lead
role
has
been
around
for
a
few
weeks,
I
think,
but
it
was
in
a
hack
MD.
There
have
been
a
couple
rounds
of
review
on
it,
so
it
should
be
in
a
pretty
good
place.
B
The
next
one
is
events
lead,
so
this
I
think
it
can
be
a
little
bit
confusing
at
first,
but
basically,
the
concept
here
is,
for
example,
the
community
meeting
or
kubernetes
contributor,
Summit
or
any
other
event
that
we
run.
We
usually
have
a
comms
lead,
also
elections.
We
usually
have
a
comms
lead,
that's
involved
with
each
of
those
projects
and
that
doesn't
have
to
be
someone
from
the
contributor
comms
team.
B
Often
it
is
thankfully,
because
we
have
some
very
involved
members,
which
is
wonderful,
but
if
someone
were
to
take
on
a
comms
lead
role
for
one
of
those
events
and
they
weren't
a
member
of
the
comms
team,
how
would
they
get
involved
with
comms
and
how
would
we
make
sure
that
those
events
were
being
served
properly?
We
need
someone
with
ownership
to
make
sure
that
we
are
doing
all
the
comms.
We
need
to
do
for
events,
because
those
are
usually
very
time.
Sensitive
and
they're
large
projects
that
require
a
lot
of
communications.
B
So
that's
the
concept
of
this.
It's
someone
to
have
ownership
over
events.
There
might
be
someone
else
on
the
team
Who's
acting
as
comms
lead
for
those,
but
this
person
has
ownership
in
making
sure
that
all
the
things
for
those
events
are
getting
done
poking.
That
comms
lead,
if
it's
not
themselves
and
just
and
also
working
with
the
social
media,
lead
and
blogging
lead
to
make
sure
that
they
know
about
the
tasks
that
need
to
be
done.
For
those
events,
does
that
make
sense.
C
B
Yep
and
then
the
last
role
that
we
have
out
currently
is
Tech
lead.
So
previously
we
had
a
team
member
rajula
who
was
kind
of
our
our
Tech
Guru
of
the
team.
B
He
helped
to
manage
the
the
automation
for
our
Twitter
account
on
GitHub,
so
we
have
Twitter
together
a
GitHub
actions,
type
thing
on
our
Kate's
contributors,
tweets
repo,
and
so
that's
a
process
that
anyone
in
the
community
can
use
to
file
a
PR
and
once
that
PR
is
approved,
it'll
actually
be
tweeted
from
the
Twitter
account
that
has
some
limitations
and
sometimes
the
automation
breaks.
So
we
need
someone
to
take
care
of
that
repo.
We
also
have
some
level
of
ownership
with
the
kids.dev
site.
B
We
want
to
make
sure
that
we
are
involved
with
the
that
that
site.
Since
it's
focused
on
the
contributor
audience,
we
write
a
lot
of
blog
posts
for
it,
so
we
want
to
be
able
to
help
with
that
site.
That's
not
something
that
we've
traditionally
had
a
lot
of
scope
in,
but
we're
trying
to
add
some
scope
to
our
group
with
this
role.
B
Also,
the
slackbot
is
another
area
of
technical
leadership,
so
slackbot
Twitter,
Automation
and
case.dev
are
the
main
technical
areas
that
the
tech
lead
has
ownership
of.
Speaking.
B
So
I
started
trying
to
do
that
earlier
this
week
and
I
needed
to
ask
some
questions
and
then
I
got
lost
on
it.
So
I
need
to
ping
someone
about
that.
Okay,
the
because
I
am
not
the
tech
leader,
yeah.
B
C
A
A
A
Yeah
but
we
yeah,
we
broke
it
when
we
moved
slack
the
slack
sign
up,
page,
okay
and
and
nobody's,
and
and
had
to
reinstall
it,
and
nobody
has
nobody
has
used
it
since
then,
because
of
of
our
various
slack
Services,
it's
the
one
where
we
can't
necessarily
casually
test
it.
Yeah.
A
A
Actually,
the
goofy
thing
the
gooey
thing
about
it
is
I
can't
actually
run
a
test
caslin
can't
because
the
the
only
the
only
you
have
to
be
a
member
of
the
college
team
comes
team.
On
slack,
we
can
make
you
a
member
yeah,
so
the
I.
A
Let's
do
it,
but
but
Boeing
that's
the
only
team
that
actually
does
need
access
to
it.
So
the
the
I
suppose
you
could
make
a
case
for
the
steering
committee
also
wanting
access,
but
so
far
that
has
not
happened
that
the
steering
committee
wants
something
sent
out
to
all
of
slack.
They
come
to
come
so
which
words.
C
B
E
I
was
saying
we
could
test
it
out
next
week.
Let's
try
that
okay.
A
A
The
the
two
requests
I
actually
have
across
all
of
the
role
proposals
is
number
one
that
they
all
have
like
a
couple
of
lines
about
how
succession
happens,
because
certainly
some
of
the
roles
proposed
could
be
quite
time
intensive
and
and
for
that
reason
we're
gonna
need
and
also
a
bunch
of
the
roles
mentioned
shadowing,
and
it
only
makes
sense
to
have
shadowing
if
there's
some
finite
time
in
which
the
shadow
is
going
to
step
up
to
be
the
lead.
A
The
and
the
other
thing
is
I'm
actually
going
to
request
a
name
change
on
a
couple
of
them.
Wonderful
Tech
lead
to
really
becomes
Tech
lead
for.
A
A
Because,
otherwise,
we're
going
to
get
it
confused
with
the
contrivance
technique,
yeah,
which
in
fact
I
did
because
the
first
thing
I
saw
when
I
saw
the
proposal
is:
oh,
hey.
Somebody
wrote
a
formal
role,
definition
for
the
contribex
tech
lead.
That's
awesome,
oh
wait.
No!
This
is
not
for
the
contrivance.
Tech
lead.
C
Yeah
so
foreign.
A
B
Cool
I
like
it
and
then
the
one
other
role
by
the
way
that
I,
don't
think
is
defined
yet
is
some
kind
of
more
General
leadership
role
within
our
sub-project
group
like
running
the
meeting
was
that
just
sub
project
owner
could
be
yeah,
I,
don't
know
if
we
need
to
write
a
definition,
though
for
that
person.
B
And
by
the
way,
the
folks
who
are
doing
the
lead
definitions
for
blogging
lead
and
Tech
lead
blogging
lead.
Oh
no
I
said
that
one
that
one
is
Federico,
events
is
Avinash
and
Tech
lead
is
Imran,
so
there
will
be
people
to
put
into
these
roles
immediately
once
we
have
them
yeah
and.
A
By
the
way,
I
think
it's
a
good
example
for
the
rest
of
the
sake,
because
we've
discussed
having
various
sort
of
volunteer
jobs
in
contrabex
and
we
really
for
contribex.
On
the
whole,
we
really
need
to
actually
prepare
a
you
know
at
least
some
brief
role,
definitions
and
a
grid
that
has
you
know,
you
know,
role
who's,
currently,
volunteering
for
it.
You
know
you
know
and
and
a
link
to
to
that
person
so
that
people
can
volunteer
for
these
things,
which.
A
Linking
off
to
the
comms
one
so
the
because
it
would
make
it
easier
for
us
to
recruit
people
if
they
could
actually
find
the
thing
that
they're
volunteering
for.
B
A
Okay,
so
that
was
all
about
that.
We
should
also
have
similar
role.
Definitions
for
contributes
roles,
including
maybe
the
the
com
subpractic
owner,
and
then
we
should
probably
put
that
on
a
page
that
is
linked
from
our
Charter
but
is
not
on
our
Charter
itself.
Simply
because
every
time
we
update
the
charter,
we
have
to
rebuild
sigs.yaml,
which
is
annoying
so
and
if
we're
assigning
and
unassigning
people
it's
anyway.
C
A
Okay,
do
we
have
anybody
from
the
contributor
documentation
team
here
today.
C
I'm
halfway,
not
quite
really
participant
in
some
of
that
do.
C
I
know
that
there
has
been
some
progress
on
the
developer
guide,
self-paced
training,
content
outline
and
development
as
I'm
a
reviewer
on
some
of
that.
It's
still
in
progress
and
not
I,
don't
think
yet.
I'm
gonna
shape
to
be
ready
for
wide
distribution
for
reviews.
A
Okay,
yeah,
okay,
we
need
to
find
out
I
didn't
I
got
late
notice.
That
Bob
was
not
going
to
make
this
meeting
so
I
didn't
have
a
chance
to
to
touch
base
with
that
team.
A
Yeah,
among
other
things,
one
of
the
reasons
I
want
to
actually
arrest
them
is
work.
We're
kind
of
accumulating
people
who
individuals
who
want
to
make
minor
contributions
to
the
contributor
guide
and
when
the
bad
situation,
where
we
have
to
tell
those
people
to
wait,
which
I
always
hate
doing
the
so
I'd
like
to
get
something.
Even
if
it's
not
finished,
I'd
like
to
get
something
online
that
is
contributable
to
so.
A
C
Tangential
to
that
I've
been
trying
to
schedule
the
non-code
contributor
guide,
and
that
is
just
going
to
not
happen
until
after
kubecon.
At
this
point,
okay.
B
Also
be
good
to
mention
that
our
team,
the
the
comms
team,
does
bring
this
up
in
all
of
our
meetings.
We
are
trying
to
track
what's
going
on
with
these,
because
it's
related
to
kate's.dev
and
it
has
a
contributor
audience.
So
we
want
to
make
sure
that
we're
aware
of
what's
going
on
with
these
and
can
help
continue.
Jenny.
A
Okay,
well,
I'll
try
to
find
out
what
status
is
the
okay,
so
other
stuff,
so
getting
to
GitHub
management
and
Omer.
Let's
talk
about
issue
hierarchy,
so
by
the
way
we
had
a
bunch
of
people
join
this
meeting
late.
Omer.
Do
you
know
the
other
people
in
the
meeting.
A
F
Sure
so,
Omer
Benson
on
I'm,
a
senior
pm
at
GitHub
I'm,
currently
focused
on
issue
hierarchy.
I
also
used
to
be
a
k-native.
Maintainer
was
a
part
of
getting
that
project
into
the
cncf
and
I've
worked
with
Josh
in
the
past
yeah.
We
miss
you.
A
I'm
one
of
the
chairs
for
sick
contributor
experience.
C
C
Hi
I'm
Noah,
Abrahams
I'm
a
long
time,
contributor
and
or
lurker,
depending
on
what
role
I'm
in
at
any
given
point
in
time,
and
my
primary
focus
is
the
non-co
contributor
stuff,
Ray,
Hey,
I'm
raylano,
also
the
co
one
of
the
co-chairs
for
Sig
docs.
Some
also
been
a
release,
leads
and
I
still.
F
I'm
part
of
sick
release
and
also
in
part
of
six
security
as.
C
Well,
you'll
see
me
around
all
right,
caslin.
B
And
Ray
is
also
a
wonderful
help
with
comps
all
the
time
and
hello,
I'm
chasmine
Fields
I
primarily
do
my
contribution
in
the
contributor
comms
group.
B
C
E
Yeah
I
work
for
hardness
as
a
big
job.
I,
basically
I've
been
contributed
to
qualms,
being
active,
but
not
so
active
now,
I'm
also
part
of
release,
forms
and
yeah
I
contributed
something
significantly
called
want
to
go
to
category,
and
now
we
are
working
on
code
spaces.
Let's
see
how
it
works
out,
and
there
are
some
things
on
mentoring
as
well.
Sometimes
yeah,
that's
it.
You
could
find
me
doing
things
on
release,
forms
and
comfortable
prompts.
C
C
Er
I
would
never
met,
but
I
work
on
I'm,
a
product
manager
in
code,
spaces
and
I've
worked
historically
in
things
like
sync
windows
and
Landing,
getting
with
a
stable
support
and
also
take
Docs,
as
well
as
been
a
shadow
in
the
enhancements
group
and
then
now
I'm,
essentially
trying
to
find
my
place
where
I
can
contribute
on
the
contribex
foreign.
E
X
at
least
I'm
also,
currently,
a
shadow
for
the
sick,
contradicts
that
lead
position
so
nice
to
meet
you.
E
I've
been
I've
been
a
part
of
released
him
for
1.25
and
1.26
now,
and
I
am
currently
contributing
to
contracts,
contributor,
comms.
So.
E
Me,
oh
yeah,
also
I,
just
I'm
coordinating
with
this
Excel
I'm
entering
sub
project
so
yeah.
That's
me.
D
All
right
and
I'll
take
up
the
rear.
My
name
is
Laura
Sienna
Maria
I'm,
a
developer
Advocate
over
at
palumi,
but
mainly
I'm
here,
to
help
with
the
community
meeting
I've
been
driving
that
now
for
a
couple
years.
I
think
time
has
no
meaning
but
yeah
so
I'm
here,
working
on
that
and
anything
else,
people
toss
things
at
me,
so
cool.
F
I
hope
too
sorry
in
advance,
if
my
internet's
a
little
spotty
I'm
currently
in
Tuscany
on
vacation
but
I
know
this
meeting
only
happens
once
a
month.
So
I
was
like
okay.
C
F
The
last
thing,
I
do
oh
okay,
twice
a
month.
Okay,
maybe
I
should
have
stayed
drinking
wine,
then
no,
but
I
I
I'm
glad
to
be
here.
I
I
wanted
to
walk
you
all
through
issue
hierarchy.
F
F
This
feature
and
I
sort
of
wanted
to
see
if
there
was
any
interest
from
from
this
group
like
in
in
this
feature,
the
way
that
we're
doing
issue
hierarchy
is
like
I,
think
kind
of
cool
and
like
not
quite
the
typical,
not
quite
your
typical
sort
of
like
sub
issue
field,
so
I
can
give
you
guys
a
quick
demo
on
that
and
then
or
we
give
you
all
rather
a
quick
demo
on
that
and
then,
if
there's
interest,
I
would
love
to
have
like
one
POC
work
with
me
to
figure
out
how
to
collect
feedback
from
the
community
right
now.
F
F
Is
it
gist,
and
there
is
a
walkthrough
of
this
of
this
feature
in
case
you
want
it
in
the
future,
but
I
will
quickly
walk
you
all
through
this
and
I'm
trying
to
try
to
make
this
like
the
shortest
ever
demo
and
we're
gonna
be
Off
to
the
Races
here.
If
my
internet
starts
to
be
wonky,
please
send
messages
in
the
chat
because
oh
can
I
share
my
screen.
Whoever
the
host
is
you.
A
F
F
F
So
one
thing
that
often
happens
in
open
source
projects
is
you
have
these
like
larger
initiatives
and
those
larger
initiatives
tend
to
have
like
smaller
things
under
them,
and
we've
heard
a
lot
from
especially
our
Enterprise
users
that
like
they
really
want
a
way
to
define
things
like
epics
inside
of
GitHub
right
we've
held
up
from
doing
this
in
the
past,
because
part
of
the
beauty
of
GitHub
is
its
Simplicity
right
and
we
don't
want
to
add
a
bunch
of
knobs
and
whistles
and
one
of
the
first
things.
F
I
said
when
I
joined
this.
This
team
working
on
GitHub
projects
was,
if
you're,
trying
to
build
the
next
year.
Please
count
me
out,
and
that
is
not
what
we're
trying
to
do
and
we're
very,
very
keen
keenly
aware
of
that
sort
of
the
limitation,
so
I'm
going
to
show
you
all
really
quickly
what
it
looks
like
to
create
issue
hierarchy
inside
of
GitHub.
This
is
an
alpha
feature,
and
maybe
you
all
can
give
me
some
some
feedback
on
it.
F
We
can
talk
about
it,
so
this
is
functionally
what
our
issue
hierarchy
is
based
off
of
it's
completely
based
in
markdown,
which
I
think
is
pretty
neat,
so
you
can
do
things
like
ADD
child
issues
to
to
these
task
lists.
You
can
also
add
multiple
task
lists,
and
this
also
probably
means
nothing
to
you
all
right
now,
because
you
don't
know
what
this
looks
like
rendered.
But
I'll
just
do
this
really
quickly.
This
is
a
trapped
issue,
traffic
issue
and
let's
call
this
one
kubecon.com
comms
and
let's
call
this
one
kubecon.
F
Marketing
comms
and
we'll
call
this
kubecon
technical
comps
right,
so
you
can
sort
of
see
how
we
can
split
these
things
up
into
different
categories,
and
you
get
these
interesting
things.
These
are
called
taskless
blocks
and
some
of
the
features
you're
going
to
see
today
are
not
yet
shipped
to
Alpha.
So
you
will
not
have
access
to
this
as
an
example.
The
ability
to
search
for
issues
inside
of
your
repo
with
this
nice
little
drop
down
so
I
can
add
things
like
that.
F
But
this
is
functionally
what
issue
hierarchy
is
based
off
of
and
we
went
with
a
markdown
first
approach
right,
so
you
edit
it
it's
still
marked
down
if
I
refresh
the
page,
because
it's
still
Alpha,
you
should
see
the
thing
I
added
earlier.
That
Foo
is
currently
there
right.
So
all
this
is
marked
down.
The
reason
I
think
is.
F
This
was
a
good
idea
and
the
reason
I
took
this
team
on
a
multi-month
voyage
to
make
this
possible,
as
opposed
to
just
adding
a
sub
issue
to
the
feel
to
like
the
the
issue
field
or
an
issue
field
called
sub
issue
is
because
you
can
do
things
like
take
this
right
and
you
can
move
it
to.
You
know
a
code
editor
for
example,
and
make
edits
there
and
then
put
it
back
into
the
issue.
F
Right
You
can
do
things
like
when
you're
creating
issue
issue
templates
as
Open
Source
Products
often
do
you
can
bake
these
into
the
actual
markdown
that
you,
hopefully
that
hopefully,
contributors
are
reading
and
lots
of
other
I
think,
like
extra
external
reasons,
why
we
did
that
one
thing
this
does:
it
creates
the
same
sort
of
track
in
relationship
that
you're
used
to
from,
like
the
traditional
task
lists
the
way
that
it
worked
before,
but
the
way
that
this
really
comes
alive
is
in
projects.
F
So,
if
you
go
to
projects
and
I
go
to
my
vandelay
Industries
Board,
we
do
importing
exporting
of
of
latex
anyway.
This
is
a
sign
called
reference.
If
anyone
gets
it,
but
basically
what
you
can
do
is
you
can
start
to
navigate
the
hierarchy
through
breadcrumbs?
F
You
could
do
that
like
on
many
different
levels.
So
if
this
one
had
another
one
in
it,
for
example,
I
can
click
that
one
too
and
I
can
click
that
one
too
and
I
can
go
all
the
way
back
up
the
hierarchy
right.
So
you
can
see
how
this
starts
to
be
useful,
we're
currently
working
on
a
way
to
see
labels
in
this
view,
as
well
as
assignees
and
yeah.
You
can
also
create
circular
references,
no
problem.
It's
not
gonna.
It's
not
gonna
blow
up
get
help.
F
We
promise
there's
also
this
nice
little
tracks
column,
which
shows
you,
like
the
number
you
have
completed
in
that
task
list.
F
We're
building
on
this
actively
and
quickly
and
I,
would
really
love
to
get
some
of
this
out
to
kubernetes,
because
I
know
you
all
are
currently
trying
to
move
your
releases
over
to
GitHub
projects,
which
I
am
very
happy
about,
and
I
was
wondering
if
there's
interest
in
getting
this
enabled
for
the
kubernetes
organization.
F
This
will
only
work
for
folks
who
have
edit
rights
on
kubernetes,
yeah
I.
Think
that's
all
the
features
I
wanted
to
show
off
sorry
that
wasn't
the
world's
fastest
demo.
It
was
just
like
a
regularly
timed.
What's
up.
F
Yeah
yeah,
so
if
you
have
the
ability
to
edit,
oh
sorry,
so
if
you
have
the
ability
to
edit
issues,
you
will
have
the
ability
to
use
that
that
bar
to
add
things
right.
It's
not
just
like
anyone
who
sees
the
issues,
it's
anyone
who
has
access
to
edit,
the
markdown
will
have
access
to
add
new
things
from
that
task
list.
Basically,
in
the
future,
maybe
we'll
do
something
cool
where
we
have
like
permissions
for
just
people
to
add
tasks,
that'd
be
kind
of
neat,
but
that's
not
currently,
where
we're
at.
A
A
F
A
Yeah,
okay,
you
know
I
can
see
that
being
useful
because
we
already
use
the
existing
checkbox
lists,
sometimes
de
facto
in
that
way,
and
so
the
fact
that
they
can
automatically
link
will
be
an
obvious
Improvement
for
people.
What.
F
You
can
also
do
is
like
just
take
the
existing
checklist
that
you
have
right
and
then,
just
like
add
some
formatting
on
top
of
them
like
it's
just
that
easy
right,
that's
like
part
of
the
part
of
the
thing
here
is
like
you
want
to
like.
Take
care
of
people
have
been
working
and
make
it
easy
to
move
these
things
over.
These
don't
yet
support
things
like
this
issue
needs
a
fix
or
something,
and
then
like
link,
it's
not
quite
not
quite
there
yet
so
it'll
just
support.
F
It's
like
a
dumb
list
of
issues
right
now,
but
we're
like
working
on
this.
We
have
a
lot
of
features
that
are
that
are
coming
up,
that
I'm
really
excited
about
that
I'd
love
to
work
with
you
all
on
it
and
here's
some
some
feedback
requests
from
you
all.
We
get
a
lot
of
stuff
from
our
Enterprise
folks,
but
getting
open
source
involved
in
this
would
be
great
I.
A
Mean
that
would
be
the
thing
that
that
I
would
see
as
being
super
helpful,
which
is
the
ability
to
add
some
kind
of
a
comment,
as
well
as
the
issue
right.
F
Josh
I
do
value
your
feedback
I
just
and
for
the
purposes
of
this
meeting,
all
I
would
need
is
just
like
someone
to
sort
of
take
point
on
this,
so
that
I
can
like
get
it
enabled,
assuming
that
y'all
would
like
to
have
it
enabled
so
that
I
can
make
sure
that,
like
a
everyone
knows
where
to
go
to
submit
feedback
and
then
B,
maybe
there's
also
like
a
a
shared
slack
Channel
opportunity,
somehow
between
GitHub
and
kubernetes,
where
we
can
like
have
a
place
to
chat
that
might
be
good,
so
I
don't
know.
A
Know
see
this
would
be
under
the
GitHub
admins
group,
the
so
you
know,
and
they
would
decide
who's
going
to
be
the
point
person
for
it
the
so
let
me
go
ahead
and
take
that
I.
Don't
do
we
have
any
GitHub
admins
on
right
now.
E
I
I
I
was
gonna,
say
the
same
thing.
It
probably
is
worth
bringing
it
up
with
them
at
once
as
well
and
considering
it's
Bob.
A
E
Also
considering
a
lot
of
the
folks
who
regularly
attend
this
meeting,
aren't
on
call,
it
might
be
worth
sending
out
the
gist
that
you
pasted
in
the
meeting
notes
to
the
contradicts
meeting
list
just
so
that
people
are
aware
that
this
is
a
thing
and
you
get
his
interest
to
sort
of
enable
this.
F
I've
worked
with
him.
I've
worked
with
him
in
the
past
on
some
other
stuff,
so
I'll
I
will
just
like
appoint
Bob
I'll
just
ask
him
if
he
wants
to
take
a
point
on
it
because
I've
talked
about
other
stuff
and
hopefully
you'll
say
yes,
and
then
we
can
get
something
out
on
the
mailing
list
and
we
can
get
this
enabled
we're
also
going
to
put
on
the
tasks
itself
like
Alpha,
send
feedback
and
that'll
link
to
like
a
Google
form.
F
So
anyone
who
sees
it
will
be
able
to
like
send
feedback
and
like
we
don't
need
to
like
have
the
penetration
of
this
messages
need
to
be
like
the
entire
Community
right.
Just
needs
to
people
need
to
know
that,
like
some
warning
basically,
but
it
will
also
this-
this
is
actually
might
be
relevant
and
and
might
affect
your
interest
in
this.
F
If
there
are
no
task
lists
in
an
issue,
we
currently
show
this
button
add
task
list,
it's
a
bit
of
an
eyesore,
but
it's
like
the
only
way
we
found
that,
like
people
can
like
find
this
feature
so
yeah,
but
I'll
follow
up
on
on
all
this
and
I
will
send
out
a
message
in
the
mailing
list
and
I
wait
to
get
comments
before
I
enable
anything
because
we
will
be
changing
the
way
that
issues
look
for
everyone
who
has
edit
permissions
on
on
on
GitHub
issues,
which
is
the
channel
I,
should
use
get
GitHub
management
is
what
I
should
bust
it
out
on
yeah.
F
Okay,
I
will
I
will
write
that
down
and
I'm
really
excited
to
get
you
all
on
board.
We
have
a
lot
of
really
exciting.
C
F
So
that's
that's
always
the
first
question
not
yet,
but
it
will
eventually,
so
you
can
do
things
like,
for
example,
in
the
future
we'd
like
to
be
able
to
say,
hey
here
are
the
four
links
PRS
that
close
this
issue
right,
as
opposed
to
like
the
one-to-one
relationship
that
we
that
we
currently
have
between
issues
and
PRS.
So
we're
hoping
this
like
resolves
a
bit
of
craft
there
too,
but
yeah,
that's
a
good,
that's
some
good
feedback
and
exactly
the
sort
of
stuff
we're
looking
for.
A
Okay
sounds
good
and
before
we
close
out
the
meeting
I
noticed
a
lot
of
put
on
the
agenda
that.
C
E
This
is
just
an
update
yeah.
This
went
out
as
comms
as
well
earlier
this
week
that
you
can
close
issues
that
is
not
planned
and
not
planned.
Now
the
bot
Auto
closes
issues
has
not
planned
as
well.
E
A
Okay,
cool
thanks.
Everybody
and
I
will
see
you
online.