►
From YouTube: Kubernetes Contributor Experience SIG 20180711
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
All
right,
hi,
everyone
welcome
to
the
July
11th
2018
edition
of
kubernetes
contributor
experience.
I
am
experiencing
some
internet
bandwidth
issues.
So
if
I'm
cutting
out,
please
feel
free
to
interrupt
me
at
any
time
or
hit
me
up
on
chat
and
I
will
repeat
myself,
but
I
did
link
the
meeting
notes
in
the
in
the
chat
so
feel
free
to
a
at
yourself
at
agenda
items,
and
then
we
will
get
right
into
it.
So
first
things:
first,
we
usually
do
reoccurring
items
like,
for
instance,
introduction
of
new
contributors.
A
A
C
I,
don't
think
I've
ever
given
an
interval
before
hey
everyone,
I'm
Kim,
Barnard
I,
also
work
on
CN,
CF
and
also
very
involved
with
kubernetes
I,
been
the
communications
lead
on
the
release
team
I
work
on
the
blog
and
I'm,
also
working
on
sig
Docs
now
so
I
know.
I've
worked
with
a
lot
of
you
but
nice
to
see
you
all
on
here.
D
I
just
wanted
to
add
some
context
for
everyone,
so
we
had
a
call
with
Kaitlyn
and
hallux
a
few
weeks
ago.
A
A
I
don't
know
LC
if
we
want
to
have
a
sidebar
conversation
about
dev
stats
in
general,
or
maybe
if
we
have
time
at
the
end
of
the
meeting,
we
can
have
a
conversation
about
it,
but
I
feel
like
we
should
start
to
fill
that
slot.
I
mean
we've
got.
We've
got
a
cup
of
the
week
now,
which
sort
of
fills
things
up,
but
I
thought
the
dev
set.
I
thought
dad
stats
did
bring
a
nice
sense
of
we're
monitoring
the
project
health
perspective.
D
Should
just
mention
it,
you
know
we
could
say:
hey
we're
finding
some
data
problems
if
you're
interested
in
helping
here
it
is
that's
why
you're
not
getting
stats
I,
think
that
just
remains
transparent
and
then.
E
E
A
E
For
example,
if
you
look
at
the
number
of
open
pull
requests
now
it's
about
three
times
what
it
should
be,
because
we're
not
getting
all
of
the
close
event
and
Lucas
is
continuing
to
work
on
that,
but
we're
now
having
to
use
a
sort
of
complicated
system
of
pulling
stuff
from
github
archive
and
pulling
stuff
from
the
github
API
and
checking
them
against
each
other
etc.
To
try
to
avoid
missing
any
events.
We
don't
have
yeah.
F
So
last
two
weeks
I
was
from
on
the
vacation.
The
work
that
was
done
is
sinking
new
events
that
we
are
missing,
but
it
started
doing
that
about
16
days
ago
and
because
of
of
github
API
specific
working
mode,
I
would
say
we
cannot
get
past.
Even
so,
if
there
were
some
milestone,
changes
or
PR
closed
events
that
were
not
recorded
and
not
happened
during
the
last
16
days,
we
won't
have
them.
Josh
Berg
has
showed
me
two
cases
that
we
are
missing
something.
F
Unfortunately,
I
am
just
after
the
vacations
and
trying
to
catch
up
with
things.
I
didn't
yet
started
to
deep
analysis
of
this
I
am
going
to
do
this
tomorrow.
I
think
we
are
quite
good.
I
just
need
to
confirm
that,
and
if,
if
the
problem
is
only
because
we
are
missing
some
old
past
events,
we
will
be
getting
better
and
better
every
day
and
sometime,
we
will
have
almost
all
events.
So
I
just
need
to
confirm
that
this
is
the
case
yeah,
but.
E
A
Better
every
day,
yeah
I'm,
sorry
I
think
someone
else
was
attempting
to
talk
to
No,
alright,
alright,
let's
so,
let's
go
into
our
first
agenda
item
we
can
like
I
said
we
can
always
talk
a
little
bit
more
about
death
stats.
At
the
end,
the
call
I
did
put
in
agenda
I,
don't
know
in
there
just
to
capture
some
of
this
stuff
that
we
were
saying
so.
First
things
first
is
Tim
with
the
Linux
plumbers
conference,
which
just
reminds
me
I
need
to
add
another
agenda
item
so.
G
This
was
a
question
that
came
to
me
from
one
of
my
co-workers:
who's
involved
with
organizing
the
plumbers
conference.
They
have
a
format,
that's
kind
of
what
I
think
we
were
aiming
for
more
so
than
what
ended
up
happening
at
Q,
Khan
and
Copenhagen
in
terms
of
trying
to
be
minimal,
almost
no
presentation,
and
instead
conversation
and
as
as
they've
kind
of
gotten
more
broad
than
just
Linux
kernel
and
stepping
into
including
discussion
and
conversation
on
other
areas
and
having
developers
from
the
broader
ecosystem.
G
A
A
G
Impression
was
probably
sort
of
worst
of
all
I
guess:
okay
from
the
community,
but
then
spreading
word
and
the
CFP
potentially
have
a
chair
help
vets
the
things
that
are
coming
through
the
CFP,
but
just
I
think
the
first
question
was:
does
this
make
sense,
is
it
desirable?
Is
it
viable
so
I
mean
if
anybody's
got
the
slightest
interested
definitely
reach
out
to
me
and
I
can
connect
people
I.
A
Think
it's
valuable
just
because
folks
don't
want
to
go
to
China.
Well,
not
I'm,
not
in
on
that
saying
everyone
I,
some
kubernetes
folks,
don't
want
to
go
to
China
for
kube
Khan,
especially
some
of
the
folks
in
North,
America
and
I.
Think
it's
in
I
think
when
Explorer
yeah
Vancouver
I
see
it
on
the
agenda,
so
it
just
might
be
a
closer
commute,
especially
all
the
West
Coast
folks,
so
I
think
it's
I
think
it's
viable
I've
heard
nothing
but
good
things
about
some
explorers
conference.
A
A
G
So
I'm
not
sure
that
it
was
an
official
developer
day,
but
it's
a
forum
where
developers
can
get
together
to
discuss
things
and
if
folks,
aren't
all
traveling
all
the
way
over
to
China
for
for
whatever
reasons
that
week-
and
we
are
having
conversations
that'll
be
happening
that
week
anyway,
so
I
I,
don't
know.
I
I
think
the
the
more
forums
where
things
are
being
discussed
that
there's
utility
in
that,
but
also
yeah.
They
overlap
both
in
time
and
splitting
of
the
group
of
people
who
are
talking
is
potentially
a
problem.
G
A
D
So
Jeff
seeker
who's
been
participating
in
office
hours,
I'd
like
to
add
him
to
the
YouTube
channel
as
a
backup
for
me
when
I
travel,
so
when
I'm
on
the
road
he
can
cover
meet
our
contributors
and
office
hours
he's
currently
in
the
process
of
applying
for
kubernetes
org
membership
and
he's
working
on
the
dashboard
and
a
whole
bunch
of
other
things.
So
I
just
wanted
to
get
an
act
from
everybody
before
just
randomly
adding
him
I,
don't
know
what
the
process
is.
D
D
D
A
H
A
H
So
basically,
the
idea
is
that
there's
a
slack
pot
that
we
installed
and
the
kubernetes
flag
channel,
it
essentially
looks,
looks
at
the
conversations
it's
mainly
looking
at
a
kubernetes
user.
It's
looking
for
conversations
and
it
looks
for
like
where
people
are
asking
a
question,
and
somebody
else
answers
that
question
and
once
it
sees
that
it
basically
says
like
hey.
This
looks
useful.
Let
us
store
it
for
the
future
and
then
in
the
future.
When,
like
somebody
asks
the
same
exact
question,
then
we
just
pop
off
one
of
those
stored
answers.
H
It's
kind
of
a
I,
don't
know
if
it's
like
a
very
good,
descriptive
version
of
like
at
a
high
level,
but
the
idea
is
just
like
the
same
questions
keep
coming
up
on
communities
user.
So
we
want
to
kind
of
use
that,
to
you
know,
answer
questions
in
the
future.
So
what
you're
looking
at
the
screen
is
some
of
the
questions
that
were
added
over
the
last
amount
of
time.
H
H
It's
now
sorted
by
date,
so
it
was
kind
of
hard
to
like
review
these
things
if
you
ever
actually
went
into
this
dashboard
thing,
but
now
you
can
see
we
have
actually
57
things
that
were
added
in
the
last
few
months
and
also
makes
it
a
little
bit
easier,
and
actually
this
was
like
thanks
that
the
body
was
doing
this
for
a
little
bit
that
he
was
like.
Looking
at
all
the
like,
all
the
unapproved
questions,
so
the
unapproved
questions
are
basically
what
do
we
ask?
H
Somebody
like
hey,
we
found
this
question
and
answer
and
that's
very
useful:
can
we
store
it
and
then
the
person
either?
Doesn't
click
yes
or
just?
Doesn't
click
anything
or
you
know
just
kind
of
clicks
ignore
or
something
so
then
these
are
all
the
questions
that
are
kind
of
ignored
and
actually
looking
like,
I
was
looking
at
some
of
them.
It's
like
both.
Actually
some
do
look
kind
of
useful.
It's
just
it's
a
little
because
it
was
a
little
harder
to
go
through
them
in
the
past
because
they
weren't
really
sorted
so
now.
H
It
is
so
tiny
tweak,
but
makes
it
a
little
bit
easier.
If
anybody
wants
to
do
this
and
if
Bob
wants
to
go
through
this,
some
more
because
I
think
they're,
actually
every
two
hours
or
something
I'd
be
great
Bob
you're,
the
best
so
the
other
so
I
got
it
make
time
for
it,
I
mean
yeah.
So
the
other
feature
so
I
guess
the
other
big
thing
that
was
at
it.
It's
not
very
obvious
from
like
the
list
of
answers
here,
but
I
added
the
all
of
these
Stack
Overflow
questions
that
were
tagged
with
kubernetes.
H
So
now,
when
somebody
asks
a
question,
it
might
pop
up
a
Stack,
Overflow,
Stack
Overflow
answer
it's
it's
like
8,000
requests
the
9000
answer,
so
it
actually
pops
up
those
cut
answers
a
little
bit
more
right
now,
but
the
one
thing
that
also
I
did
was
to
turn
down
the
relevance
and
everything
else,
and
so
because
of
that,
it's
actually
been.
Not
that
great.
H
You
know
a
couple
of
days,
I
mean
otherwise,
there's
not
like
so
the
biggest
hurdle
and
the
biggest
challenge
from
the
last
few
weeks
has
been
like
just
improving
the
relevance
and
making
sure
that
the
questions
that
come
up
or
like
when
somebody
asks
a
question
that
the
answer
that
we're
providing
is
as
good
as
possible
and
actually
is
the
right
thing
or
if
it's
not
the
right
thing,
then
you
know,
what's
the,
how
do
we?
You
know?
How
do
we
link
just
not
show
it
up?
H
If
it's
you
know,
we
can
guess
that
it's
not
the
right
thing.
So
that's
been
kind
of
you
know.
There's
been
also
like
in
this.
In
this
thing,
the
purple
line
is
like
a
percentage
of
the
time
that
it's
useful
versus
yellow
means
it's
helpful
and
then
blue
means
hey.
We
actually
answering
somebody's
question,
so
you
know
this
is
a
pretty
good
distribution.
This
is
pretty
bad.
H
Also,
the
black
line
and
purple
line
are
showing
like
how
often
how
many
actual
questions
like
how
many,
where
all
questions
we
showed
and
kind
of
respond
related
to
this
axis
so
like
today,
for
example,
we
only
showed
three
answers,
but
all
of
them
were
not
really
helpful
versus
you
know.
Last
week
we
showed
14
and
it
was
like
one
cupful
one
used
but
like
one
of
them
was
helpful
and
one
person
actually
said.
H
H
So
there
was
a
lot
of
people
that
muted
the
beginning
actually
went
back
to
all
of
them
and
said:
hey
you
know,
do
you
mind
if
I
unmute
you
and
if
it
still
bothers
something
just
viewed
again
and
I,
don't
think
so
far?
I,
don't
think
anybody
remute
it's
good
and
then
you
know
I
mean
the
rest
of
it.
It's
like
the
storage
pipeline
is
people
are
adding
questions.
H
H
D
I
H
So
that
mean
those
are
all
just
like
part
of
the
admin
site.
I,
don't
know
how
he
you
know
it's
kind
of
back
to
like
I
guess
George
like
just
so
basic,
have
been
just
adding
people
to
that
site
whenever
George
is
like,
hey,
go,
add
this
person.
So
if
George
is
like
hey
go,
add
this
person
and
I
will
I
can
add
you
to
the
dashboard.
You
can
see
it
I'm.
A
This
is
our
in
hippie.
This
is
our
in
kind
of
like
a
test
phase
to
for
this
so
like.
If
we
decide
to
take
this
on,
then
we
can
work
with
Vlad
on
how
we
can
publicly
make
the
make
the
charts
accessible,
so
I
mean
for
right
now
we're
just
using
it
to
see
if
this
is
gonna
work
for
us,
so
you're
actually
up
next.
So
if
you
want
to
take
it
from
here,
go
ahead,
wonderful.
I
I
meeting
which
is
actually
quite
delightfully
late
in
the
day
which
is
there
but
and
then
that's
that's
I'm,
trying
to
make
sure
we
don't
as
a
culture
as
a
community
have
a
really
North
American
focus,
because
people
have
a
normal
8
to
5
jobs
there
and
they
choose
prioritization
for
their
8:00
to
5:00
and
I'm,
not
sure
how
to
like
document
or
how
we
could
encourage
that
I'm.
Just
feeling
the
personal
pain
of
that
and
I
know,
other
people
in
asia-pacific
and
and
and
westward
are
probably
feeling
similar.
I
The
other
thing
is:
wouldn't
we
when
there's
meetings
that
are
canceled
in
the
community,
if
I
get
up
at
2:30
and
I
didn't
get
a
notification
that
somebody
that
they
decided
not
to
meet
that
really
hurts
even
deeper.
So
I
just
want
to
say
when
you
do
that
it
hurts
to
the
to
the
community
at
large,
and
that
was
it's
a
unda
lightful
experience.
I
A
Definitely
a
message
that
we
can
pass
on
to
our
Sen
needs
one
of
the
major
issues
that
we're
having
right
now
is
calendar
ization,
and
these
centralization
/
decentralization
of
that,
because
right
now,
decentralized
and
individuals
and
calendars,
which
means
that
we
as
a
collective
unit
have
no
control
over
that
and
but
I
just
want
to.
Let
you
know
that
your
voice
is
very
much
heard
and
that
we
are
indeed
working
on
trying
to
figure
this
out.
A
D
A
I
I
would
one
other
quick
thing:
I
wanted
to
throw
in
there.
I've
got
two
minutes,
there's
also
things
that
the
Pacific
nations
at
least
said
where
I
live
with.
It
have
some
cultural
things
to
worry
and
I
just
put
in
a
cap
that
it
doesn't
reference
back
in
New
Zealand
that
there's
a
identity
that
goes
like
here's,
my
history
from
the
from
the
the
waka
or
canoe
that
arrived
with
further
ancestry
and
say
this
is
my
story
and
my
family.
This
is
my
identity.
I
It's
really
who
I
am
also
when
you
get
the
other
thing
who
who
who
we
are
and
when.
Why
are
you
here
so
I
just
want
to
get
some
quick,
encourage
some
feedback
on
this
cap.
It
is
trying
to
use
that
study
of
how
people
get,
how
identity
and
purpose
and
ensuring
that
together
and
actually
embedding
it
in
the
core
libraries
of
kubernetes
and
collectively
gathering
that
information
for
machine
learning
and
for
us
to
really
have
some
see
the
invisible
things
that
are
already
there.
G
Yeah
on
the
release
team,
we've
kind
of
talked
and
thought
about
this
over
the
last
while
about
how
things
are
very
largely
Pacific
time,
zone
oriented
and
so
as
the
112
release
lead
and
along
with
my
shadow
eye.
Sundar
we've
been
talking
about
whether
we
have
some
ability
ourselves
to
run
to
meetings
so
that
sort
of
standard,
10:00
a.m.
Pacific
that
captures
the
existing
set
of
people
and
maybe
do
something
earlier.
The
next
day
so
like
both
of
us,
are
potentially
available
for
like
a
6:00
a.m.
G
Pacific
Tuesday,
which
is
end
of
day
still
China,
but
earlier
afternoon,
Europe
so,
and
maybe
even
so,
trying
to
figure
out.
If
we
might
do
something
like
that.
Of
course,
it's
another
one
of
these
things
where
you
split
the
forum,
but
if,
if
it's
additive,
as
opposed
to
splitting
I,
think
that
that's
but
there's
potential
benefit.
So
in
the
the
first
release
meeting
next
week
for
112.
Oh
we're
gonna,
discuss
this
and
see
if
there's
entrance
cuz,
especially
among
the
shadows
on
the
release
team.
G
We
have
managed
to
get
a
few
volunteers
from
outside
the
standard,
North
America,
but
we
also
have
to
get
them
at
the
meetings
for
them
to
be
effective
and
we
can't
just
sort
of
leave
the
problem
to
the
113
cycle
to
say:
yeah
figure
out
meetings
in
the
future.
We
gotta
start
trying
it
somehow
and
see
what
might
be
workable
start
give.
G
A
Yeah
no
and
I
saw
josh's
comment
too
about
the
the
time
zone
problem
for
the
earliest
team.
That's
extinct
should
consider
the
same
totally
agree,
I'm,
also
very
open
to
maybe
doing
for
this
meeting.
We
could
alternate
times
because
we
do
meet
weekly,
so
we
need
four
times
a
month,
maybe
two
times
during
an
afternoon
time.
I,
don't
know
in
two
times
during
the
morning
time
or
something
so
I'm
very
open
to
that,
and
we
can
take
that
to
the
mailing
list
to
make
a
decision
on
for
our
sake.
In
particular,
I
just
went
to.
J
J
J
Is
not
located
in
North,
America
and
time
zones
I
have
to
mentioned
it.
Almost
all
the
experiences
with
having
to
duplicate
medians
in
multiple
time
zones
haven't
been
successful.
So
I
remember
when,
when
around
to
two
years
ago,
Sarah
proposed
to
have
to
attend
a
Tim
community
meetings
on
Thursdays
like
one
for
for
North
America,
North,
America
friendly
time
zones,
another
one
for
Europe
in
Asia,
and
it
wasn't.
J
It
wasn't
a
good
experience,
especially
for
the
second
meeting,
where
those
American
people
have
been
attended,
also
heard
the
similar
stories
from
some
from
some
special
interest
groups
that
also
had
a
similar
experience.
So
I
would
definitely
like
to
see
these
meetings
happening
in
more
friendly
time.
For
most
of
us
at
the
same
time,
I
feel
that
the
content
and
integrity
conversations
is
the
main
target
of
this
matrix.
K
I
mean
we
tried
to
do
the
same
thing
back
when
they
did
OpenStack
I
mean,
as
it
was
said,
we
we
kind
of
Center
everything
on
Pacific
time.
In
fact,
the
way
we
list
our
calendar
is
on
Pacific
time,
even
a
lot
of
our
cultural
norms,
for
the
way
that
we
interact
are
on
us
Pacific
time
cultural
norms.
It's
it's
just
become
very
ingrained
in
how
we
do
things,
but
it
is
something
we
could
try
and
do
more
elsewhere.
Try
to
focus
on
asynchronous
forms
of
communication,
particularly
email
and
I
know.
K
We
have
a
little
bit
of
trouble
with
that.
Like
our
Google
Groups
emailing
system
and
China
is
a
problem.
There's
lots
of
things
are.
Our
communication
is
really
geared
towards
what
works
for
us
here
in
the
US,
primarily
Pacific
time
zone.
If
we
just
start
to
ask
what
works
well
elsewhere,
it
might
lead
us
down
some
other
paths
asynchronous
when
OpenStack
I
used
to
lead
one
of
the
meetings
there,
and
we
would
alternate
weeks
like
I-
would
be
up
at
6
a.m.
Eastern
Time
to
host
a
meeting,
but
the
meetings
of
course
weren't
IRC.
K
They
were
not
video,
but
it
was
years
ago,
but
we
did
that
and
it
took
a
while
to
cultivate
that
other
meeting,
because
you'd
really
get
a
separate
set
of
people,
and
so
it
wasn't
a
repeat
of
the
same
conversation.
We
would
alternate
weeks,
but
the
conversation
would
almost
be
like
its
own
continuity
on
the
same
topic
and
a
handful
of
people
would
go
between
both
because
they
were
very
interested,
but
otherwise
it
would
almost
be
their
own
conversations.
K
And
if
you
look
at
something
like
Asia
Pacific
and
many
of
the
different
cultures
and
norms
that
are
there
and
then
holding
that
same
kind
of
meeting
in
the
US
I
mean
even
your
your
business
drivers.
Your
reasons
your
cultural
norms
are
different,
so
you
might
end
up
in
very
different
conversations
where
it's
not
the
same
kind
of
thing,
and
so
there's
I
think
there's
a
lot
more
to
it
than
just
trying
to
schedule
a
time
and
hoping
people
show
up.
K
A
Our
group
could
maybe
even
lead
the
way
I
mean
I'm
totally
game
with
super
late
meetings.
I
mean
I'm
a
night
owl
anyway,
George
hates
it,
but
I
am
especially
when
he
gets
emails
from
me
at
midnight,
but
I'm
super
game
and
I.
Think
that,
like
I
said
I'll
take
this
to
the
mailing
list
and
as
long
as
we
have
like
a
certain
number
of
sub
project
donors
that
are
on
the
call,
the
people
that
are
making
the
decisions
and
and
approving
things
that
George
has
said
harder
than
we
have
been
they.
A
You
never
respond
to
me,
though
George
I'm,
just
kidding
so
yeah
I'll,
take
this
to
the
mailing
list
and
see
if
we
can
get
started
because
now
I
think
blending
those
conversations
like
what
Matt
just
touched
on.
It's
gonna
be
crucial
because
I
don't
want
to
separate
conversations
going
on
and
then
like
it
doesn't
necessarily
get
any
one
thing
done.
So
it's
super
super
important
all
right,
so
I'm
gonna
take
that
to
the
mailing
list
and
we
can
have
conversation
there
about
it.
A
You
want
to
go
first.
I
think
the
community
site
redesign
is
something
we
should
talk
about.
I
think
the
contributors
site
is
something
we
should
talk
about.
I
think
github
management
is
something
we
should
talk
about.
Are
there
any
other
workflow
related
customizations
or
any
automation
that
we
should
be
alerting
people
about
Christoph
I,
see
you
you've
got
your
thinking
face
on.
L
A
M
It
might
be
worth
mentioning
that
really
just
more
to
give
a
warning
to
all
the
other
SIG's
that
we
will
at
some
point
be
invading
asking
how
we
can
help
them
with
with
the
non
code
roles
and
non
code
tasks.
So
it's
probably
worth
mentioning
that
we
can
just
give
them
a
heads
up
that
will
be
coming
in
the
near
future.
Awesome.
A
A
A
Request
accepted
all
right
now.
Next
is
what
I
the
main
show
for
what
I've
been
what
I've
been
looking
forward
to
is
in
Mach
4
we
have
contributor
site
down,
Caitlin,
did
you
mean
be
a
community
site
or
the
contributor
site?
It's
the
community
site.
I
didn't
I've
got
comment,
but
I
can
update
it
nope,
that's
that's
awesome.
A
C
So
we
had
a
conversation
with
George
about
two
weeks
ago
now
about
redesigning
the
community
page
on
the
kubernetes
website,
to
make
it
really
more
accessible
to
new
contributors
and
existing
contributors
to
show
the
resources
that
we
have
available
to
everyone
meetings,
communication
channels.
All
of
that
so
alex
has
been
working
on
some
designs
to
incorporate
all
of
this
and
I
dropped
this
into
the
dock
and
I'll
drop
it
into
the
chat
as
well.
So
you
can
see
them
the
mock-ups,
but
with
that
I'll
hand
it
over
to
Alex
to
actually
talk
through
these
I.
B
B
So
I
did
three
rough
mock-ups
and
obviously
the
roughest
photos.
The
content
is
very
rough.
I
wasn't
entirely
sure
exactly
what
content
we
would
be
beating
for
sure,
so
I
thought
I'd,
just
kind
of
to
experiment
with
a
couple
of
different
options,
and
so
obviously
this
is
just
like
a
placeholder
some
sort
of
statistics
at
the
top,
but.
B
Yeah,
the
video
section
upcoming
event
section
that
would
be
sort
of
fed
through
similar
to
the
CAF
site,
where
it's
automatically
fed
to
the
page.
So
there
would
also
be
some
sort
of
sort
of
event,
search
bar,
which
you
could
search,
obviously
location,
date,
etc,
and
then
I
did
I
thought
about
doing
a
community
section
and
to
find
out
find
a
meetup
search.
B
B
B
And
this
could
be
a
different
kind
of
more
visual
event,
I
kind
of
like
this
option,
but
and
then
and
then
something
maybe
more
visual
for
that,
and
then
resourcing
is
the
very
last
one
which
I
think
might
maybe
fit
the
design
of
the
site
be
the
best
I'm,
not
sure
how
everybody
feels
best.
This
one,
this
this
bar
right
here
with
future
content,
events
and
units
I'm,
sorry
I
supposed
to
remove
future
content.
That's
us
that's
kind
of
an
acre
menu,
so
you
click
on
one
of
these
one
of
them.
A
I
think
this
is
great
for
an
office
and
I
think
I
understand
exactly
where
you're
going
it's
a
lot
of
the
content.
Placement
placeholder,
so
I
have
a
lot
to
say,
I.
Think
I'm
gonna
take
most
of
the
things
that
I
want
to
say
to
the
issue,
though,
but
I
think
it's
gorgeous
I
think
all
of
them
are
gorgeous
just
so
excited
about
this.
A
Last
call
for
alcohol.
You
guys
are
awesome.
Thank
you.
So
much
you
are
benefiting
the
community.
A
hundredfold
Tim
made
a
comment
that
he
likes.
The
emphasis
on
the
people-
yes
100%
George
I
know
is
thrilled
about
that
as
well,
and
George
also
studies
and
add
stuff
to
the
issue.
Yeah
I
think
I.
Think
the
major
thing
for
this
is
this
is
less
about
cigs
and
working
groups,
because
we'll
have
a
page
that's
dedicated
to
that
now,
which
is
the
contributor
site.
A
So
if
we
could
like,
instead
of
where
the
cigs
and
working
groups
placeholder
content
is,
if
we
could
talk
about
the
contributor
site,
like
maybe
give
a
tree
of
you
in
some
kind
of
modern
way
than
just
a
link,
I
think
that
would
be
cool
but
again
I'll.
Take
that
stuff
to
the
issue.
That's
like
the
only
major
thing
that
stood
out
to
me
anyway
is
sort
of
not
necessarily
needed.
B
B
A
A
Another
contractor,
or
so
just
sources,
you
need
and
feel
free
to
ask
for.
You
know
the
world
right
now
and
then
we
because
I
mean
I
like
the
site.
I.
Think
it's
great.
It's
such
a
good
sales
point.
So
just
let
us
know
what
you
need
and
we'll
do
everything
that
we
can
do
to
make
it
happen.
That's
great
yeah!
It's
gonna!
It's.
B
That's
that's
great,
thank
you
and
it's
gonna
depend
a
lot
on
the
actual
design
we
do
end
up
with
I.
Think
I
can
do
I
would
say
probably
80%
of
it.
So
in
that
case,
if
we
finalize
the
design
pretty
quickly,
I
would
say
maybe
a
couple
weeks
or
two:
is
there
a
date
that
you
really
wanna
buy
or
is
it
cause
I.
A
Yeah
as
soon
as
possible,
I,
don't
think,
there's
necessarily
a
mega
rush.
If
you
will
I
mean
the
only
make
a
rush
we
have
right
now
is
how
to
publicly
display
the
calendar,
because
we're
having
zooming
stuff
issues
but
I
think
we
can
hold
that
off
for
a
second
and
figure
out
some
other
solutions,
but
thank
you
so
much
Alex
again.
Thank
you.
So.
N
A
All
right.
Next
agenda
item,
I'm
also
going
to
add
the
oh.
No,
the
issue
is
right.
There
awesome
so
everybody
the
issue
link
is
in
the
meeting
agenda
and
then
George.
You
have
a
question
about:
that's
that's
company
representation
and
then
after
George
I'm
going
to
skip
to
Christoph,
really
quick
because
I
know
we
need
to
talk
about
some
github
management's
of
project
stuff.
That's
super
important
and
team
structure
stuff.
That's
super
important,
so
George
and
then
Christoph
yeah.
D
Just
real,
quick,
so
I'm
trying
to
make
sure,
because
I
have
co-workers
that
are
going
through
the
membership
process
in
kubernetes
and
I,
wanted
to
ask
because
I'm
getting
questions
about
the
privacy
employment
implications
of
having
like
the
CN,
CF,
big
list
of
emails
and
stuff
like
that
and
I
was
wondering
if
someone
can
point
me
to
an
issue
or
like
how
are
people
like
if
you
have
people
that
are
at
work,
and
you
want
them
to
count.
You
know
first
company,
but
they
prefer
to
use
a
personal
email
address
their
policies.
D
D
F
F
How
can
you
request
your
personal
data
to
be
removed
and
those
documents
are
in
CNC,
FDM,
repo
and
CNCs
desktop,
and
you
can
follow
the
instructions
actions
then,
and
to
create
a
PR
with
a
specific
entry
that
you
want
your
name
removed.
In
addition,
you
don't
need
to
you,
don't
need
to
put
this
name
in
this
PR.
There
is
a
special
tool
that
generates.
F
Sha-256
hash
of
of
the
data
you
want
to
remove,
so
you
can
even
provide
encrypted
data
that
you
want
to
reverse
and
create
PPR
with
this,
and
I
will
just
ruin
few
tools
to
make
sure
that
your
data
will
never
show
up
again,
and
we
already
had
I
think
three
or
four
such
cases,
and
that's
it
up
to
this
point.
Okay,
that
answers
my
question.
I
know
we're
short
on
time.
Do.
A
F
A
Okay,
that's
cool
and
then
George.
If
you
want
to
through
that
documentation
and
if
what
Lucas
said
isn't
in
there,
then
we
can
go
back
to
this
recording
and
just
document
it
nope
you're
awesome!
Thank
you
alright
and
then
Christoph
you
and
take
it
away
about
all
the
github
management
and
team
structure
stuff.
L
Yes,
I
will
keep
it
very
brief.
I
know
we're
short
on
time,
so
there's
two
agenda
items.
Little
talk
about
really
quick.
Backpack
first
is
the
github
management's
on
project
proposal
and
proposed
up
to
the
email
list.
I
will
be
I'll,
be
creating
an
issue
and
I
won't
put
it
out
to
them.
Email
us
later
today,
but
I
would
give
you
guys
a
sneak
peek
and
we
can
bring
it
up
here.
I
am
proposing
that
we
create
a
new
sub
project
and
contributor
experience,
specifically
around
management
of
github
as
a
as
a
tool.
L
It
is
a
right
now
all
the
github
management
work
that
we've
done
has
all
been
kind
of
ad
hoc,
and
it's
been
people
with
privileges,
people
with
knowledge,
kind
of
helping
out
and
doing
things,
but
a
lot
of
that
has
been
tribal
knowledge
and
there
hasn't
been
a
lot
of
set
policies
around
who
should
do
what?
What
are
the
different
like?
What
was
the
checklist
of
things
they
should
do?
Are
we
allowed
to
do?
Something?
L
There
are
specific
things
like
in
the
proposal
at
I/o
outlined
specific
things
that
would
be
part
of
the
sub
project
and
things
that
would
not
be
so
things
like,
tooling,
and
automation
for
github,
not
under
the
sub
project,
there's
already
work
that
goes
on
there,
so
testing
for
that,
and
there's
also
the
contributor,
workflow
and
automation
sub
projects
that
handles
the
tooling.
This
would
not
be
to
handle
to
it
some
policies
around
things
like
can
a
repo
be
created.
Those
are
those
are
the
responsibilities
of
steering
committee
and
Sagarika
texture
and
things
like
moderating
github.
L
While
we
need
to
have
policies
around
like
who
has
the
button
to
push
to
moderate
things.
So
it's
clear
who
actually
owns
the
button
to
push
actually
setting
moderation
policies
would
be
steering
committee
code
of
conduct
committee
and
the
moderation
sub
project
in
contribute.
Experience
surgery
I
try
to
outline
things
that
are
in
and
things
that
are
out
so
there's
a
link
to
a
Google
Doc
in
the
meeting
notes.
I
will
also
send
out,
like
once
I
put
it
into
an
issue.
L
I
will
send
out
email
list,
I'm
going
to
gain
a
generous
time
period
for
for
comment,
because
it's
basically
I'm
slicing
out
part
of
the
pie
that
would
never
give
that
out.
It
was
never
kind
of
divvied
out
too
specifically
to
contribute
experience
or
specifically
to
sig
testing
or
specifically
to
any
other
sig
or
group.
L
It's
just
been
kind
of
you
know:
yeah
eat
or
Caleb
Garrett
myself,
Eric,
like
people
with
permissions
kind
of
doing
things
and
helping
out,
but
way
to
kind
of
codify
some
of
that
work
under
some
sort
of
some
sort
of
authority.
So
so
that
there's
also
things
like.
If
somebody
wants
to
make
a
change
to
those
policies,
they
knew
they
know
who
to
go
talk
to
as
opposed
to
it
being
kind
of
this.
You
know
opaque
group
that
I'm
just
I'm
doing
doing
the
good
for
the
project.
L
That's
number
one
number
two
is
I've,
also
put
an
issue
out
there.
We
talked
about
this
last
contra,
Beck,
meeting,
I,
think
about
github
team
structure
and
cleaning
up.
You
know
we
have
like
five
six
different
teams
that
we're
creating
for
everything
we
stopped
officially
creating
the
mirror
accounts
out
to
Google
Groups
for
it,
but
I
also
want
to
propose
like
what
should
that
github
team
structure.
Look
like
so
I've
got
I
want
to
kind
of
highlight
that
issue
that
I
already
created.
L
A
Last
call
for
objections,
Jase
said
any
steering
committee
things.
Please
create
an
issue
in
the
steering
committee
repo
and
then
she's
can
add
it
to
the
project
board.
Oh
said
project
forward,
which
means
we're
late
on
ours.
All
right
last
call
for
objections
for
Christoph
all
right
and
then
I
have
a
very
quick
objection.
Call
for
the
mailing
list
item
that
just
went
out
recently
for
the
cap
for
discussed
kubernetes
that
io
and
taking
it
on
as
a
supported
platform.
A
A
Any
objections.
This
would
be
again
for
us
to
take
on
discuss
as
a
fully
sub
the
communication
platform
under
the
communication
sub
project
for
kubernetes
and
Bob
added
in
chat
that
discuss
just
cost
over
the
900
user
mark,
congratulations
to
George,
Bob
and
all
of
the
awesome
Jeff
everybody
that
has
been
working
on
the
discus
platform.
Very
awesome
Bob.
If
you
need
schwag
schwag
you
out,
so
let
me
know
they're
all
right.
L
No
objections
for
me,
but
what
I
would
like
to
see
is
because,
if
we're
going
to
take
us
on
and
we're
going
to
support
it,
I
would
love
to
see
some
explicit
plus
ones
from
people
saying
like
hey.
We
like
this
idea
and
we
put
support
because
I
haven't
seen
a
whole
lot
of
plus
ones
on
that
thread.
I,
don't
think
any,
but
yeah.
If
people
are
in
support
of
this,
would
you
love
to
see
some
plus
ones
on
the
thread
before
Friday,
so
that
we
can?
A
A
So
everybody
on
the
call
that
was
your
message
to
+1.
If
you
are
in
favor
on
the
mailing
list
and
now
the
meeting
is
over.
I
know
that
I
have
an
item
that
I
didn't
cover,
but
that's
fine,
we'll
cover
it
next
week,
I
go
forth
and
be
awesome.
Any
other
comments
really
quickly
all
right.
A
great
Wednesday
bye,
everybody.