►
From YouTube: Shanghai Summit Planning
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).
B
When
is
when
you
have
to
leave
Josh.
A
A
B
Yeah
sorry
Pat
finger
some
keys,
so
some
of
the
meta
changes
were
that
I
sent
the
we
sent
the
deck
out
beforehand,
though,
that
everyone
has
them
as
a
reference
on
their
computer,
and
we
still
like
I,
said
yesterday.
We
still
had
a
person
that
was
like
whoa.
We
want
like
a
two
monitors
set
up
so
that
we
can
have
the
reference
side
on
one
side
and
then
messing
around
with
code
slide
on
the
other
side.
So
I
don't
know
which,
which
workshop
that
commenter
was
from,
but
yeah.
A
B
That's
one
thing
to
keep
in
mind
so
I've
been
using
basically
I
killed
most
of
the
speaker
notes
and
have
been
using
the
slides,
mostly
as
a
reference
and
extemporized
the
rest
yeah,
mainly
because
the
fewer
details
are
in
the
slides
honestly,
the
better,
because
that
means
that,
when
details
change
such
as
orc
structure
and
seek
membership
and
six
structure,
I
have
to
change
fewer
things.
B
Also
because
speaker
notes,
I
can't
figure
out
how
to
make
speaker
notes
available
in
any
useful
fashion,
while
giving
a
presentation
so
I
might
as
well,
if
I
really
want
them
have
a
set
of
like
you
know,
paper
cards
really
yeah.
Those
were
the
meta
changes
then
do
you
want
me
to
screen,
share
and
just
kind
of
go
through
the
sections
sure
yeah?
Okay,
let
me
go
ahead
and
grab
some
water
first,
because
I'm
feeling
my
mouth
go:
dry.
B
That
was
just
right
here.
So
welcome
workshop
or
devote
operations.
Then
a
quick
slide
on
who's
eligible.
Everyone
is
eligible.
Why
we
changed
that
out
for
the
kubernetes
contributor
patch
as
a
joke.
It
was.
It
was
funny
to
us
it
was
less
funny
to
them,
but
whatever
I
swapped
out
the
image
details,
sorry
for
the
ink
on
tribution
isn't
a
gender.
B
B
Yeah
yeah
I
I
thought
it
was
hilarious,
so,
but
maybe
maybe
if
it
were
in
its
own
slide,
like
I,
think
that
the
beep
like
then
he
anyway,
whatever
then
I,
talked
a
little
bit
about
what
not
to
do
by
using
my
origin
story.
B
Figuring
out
what
to
contribute
and
in
this
exercise,
and
then
we
have
people
just
basically
introduced
each
other
and
talk
about
why
they're
here
and
what
they're
hoping
to
get
out
of
it.
We
didn't
have
time
to
actually
like
raise
hands
and
take
a
couple
of.
B
So
we
mentioned
individual
state
groups,
working
groups
and
sub
project
user
groups
and
then
governing
committees
that
was
new
this
time.
I
just
decided
that,
because
their
partner,
dick
things,
are
getting
better
organized
in
service.
Now,
though,
they're
pretty
easy
to
find
and
then
picking
the
pickup
picking
a
cig
joining
a
cig,
making
it
very
very
clear
that
you
join
the
mailing
list.
D
B
D
I
think
we'd
simplify
the
slides,
and
we
don't
have
much
in
the
way
of
speaker
notes,
but
I
think
sig
contributes
is
on.
That
slide
is
an
example
of
hey.
Look
the
SIG's
all
have
theirs
without
enumerate
all
of
them
to
show
the
pattern
and
there's
more
later,
as
we
talk
about
the
six
there's
more
on
that
as
well,
that
all
the
SIG's
have
their
standard
set
of
things.
B
And
then
I
have
quick
reference
to
of
repositories.
I
mentioned
kubernetes
kubernetes,
but
we're
doing
the
big
code
walk
through
in
the
201
workshop.
That
was,
it
kind
of
a
point
of
contention.
I
felt
that
a
lot
of
people
who
were
in
the
101
might
have
appreciated
this
as
well,
but
that
won't
be
an
issue
for
you
guys.
B
D
B
D
Okay,
so
there
was
a
morning
and
afternoon
session
and
in
the
morning
we
went
through
like
the
basic
structural
organization
stuff
in
details
very
similar
to
what
the
the
new
contributor
workshop
has
been
in
the
past,
where
Gwen
and
her
the
201
did
much
more
of
a
deep
dive
and
some
suppose
Arius.
So
this
is
mostly
the
the
standard,
stuff
I
think
one
of
the
things
so
next
slide
added
just
a
quick
overview
of
what
kubernetes
looks
like
so
the
people,
because
this
is
the
101.
It
is
people
who
are
new.
D
Some
portion
of
the
people
weren't
familiar
entirely
with
this,
but
when
we
say
cubelet,
what
is
that
when
we
say
this
or
that
what
are
the
different
parts
and
then
from
there
on
the
next
slide?
Having
just
sort
of
mention
that
reminding
people
you
got
your
control
plane,
the
goal
is
run
containers,
let's
dive
in
and
look
at
the
code
where,
if
you're
wanting
to
work
on
cubelet
or
wanting
to
work
on
that
this.
D
D
Then,
on
the
next
slide,
what
we
were
hoping
to
do
was
get
a
little
more
hands-on,
ultimately
in
this
session
and
have
people
actually
building
stuff,
but
to
set
that
up
and
hopefully
be
successful,
because
there's
a
ton
of
stuff
to
download
early
on
right
here,
like
we're.
Only
ten
minutes
into
the
101
session
describe
the
development
environment
for
building
and
testing
which,
in
the
past
we've
had
more
at
the
end,
is
just
sort
of
an
FYI
when
you
go
off
on
your
own.
This
is
where
you're
gonna
go
look
for
stuff.
D
It
was
here
at
the
beginning
so
that
people
could
start
actually
trying
to
prep
this.
So
there's
a
few
slides
there
about
the
stuff
and
then
sort
of
a
hey
folks
start
trying
to
get
this
stuff
going
on
your
machines
and
then,
during
the
rest
of
the
session.
We
checked
back
in
repeatedly
and
had
a
bits
of
time
here
and
there
and
the
people
floating
around
the
room,
who's
managed
to
get
this
installed
out
installed
and-
and
it
actually
to
my
surprise,
I
thought
we
were
gonna
there.
I
I
feared
we're
gonna
fail
on
this.
D
D
A
D
Forward
a
couple
you
can
kind
of
scroll
through
you
slides,
so
these
are
the
the
normal
things
oh
and
we
hadn't
really
talked
about
this
before
because,
like
stepping
back
to
101
hey,
you
got
a
fork:
the
kubernetes
repo,
so
there's
a
few
things,
they're
they're
a
little
more
detailed
on
setting
things
up,
and
then
we
had
pre
figured
out
a
number
of
the
things
that
would
be
necessary
and
had
some
URLs
here
in
the
notes
so
that
people
could
pull
from
this.
Gainor
images
would
come
from
the
local
machine.
D
A
E
D
A
small
modification
to
something
in
kubernetes
and
then
do
a
synthetic
ish
test
to
see
that
they
were
actually
using
their
modified
thing
right
and
that's
awkward,
because
you
you
need
I
mean
if
you're
on
a
bun.
You
need
build
essentials
which
you
might
not
have
and
that's
like
a
gig
or
two.
If
you're
on,
you
need
Xcode,
which
you
might
not
have
and
that's
a
gig
or
two,
then
you
need
to
go
and
you
need
the
KK
repository
at
a
minimum
and
you
need
docker
and,
like
everybody,
ends
up
needing
to
download
two.
A
D
Five
gigs
worth
of
stuff
potentially
so
we
were
trying
to
with
the
goal
of
getting
people
on
their
keyboard
building
something
in
that
the
endorphins
from
that
we
had
to
figure
out
how,
across
the
day,
can
we
get
them
to
a
point,
zooming
almost
nothing
pre-installed,
but
that
nobody
read
the
instructions
which
a
lot
of
people
actually
had,
which
was
good
but
try
to
get
them
to
some
endorphins
of
hey
I
built
something
I
ran
something
cool.
Okay.
Do
this
so.
F
D
Was
those
couple
slides
right?
There
are
basically
the
setup
for
that
letting
people
in
talking
to
this.
Like
saying
this
is
what
we're
aiming
to
do.
We've
heard
the
feedback.
People
want
to
be
more
hands-on,
we,
but
we
got
to
get
you
there
this
afternoon.
So
this
was
the
first
thing
in
the
morning
like
try
to
get
your
bits
going
on.
We've
got
the
floaters
around
the
room,
helping
people
and
then
from
the
next
slide.
D
We
head
back
into
sort
of
the
standard,
stuff,
SIG's
and
labels
and
all
of
the
the
normal
workflow
e
stuff
and
then
every
half
hour.
45
minutes
we
pop
back
to
the
developer
environment
like
hey.
Is
anybody
able
to
run
make
successfully
or
not,
and
the
the
floaters
in
the
room,
Dovan
and
helped?
And
we
we
amazingly
got
everybody
there
by
the
afternoon,
so
this
set
of
slides
is
all
basically
familiar,
I
think
the
next
I
don't
know
how
many
is
the
the
standard
stuff
similar.
D
B
D
Is
as
we
go
through
time,
part
of
this
is
speaking
to
the
changes
we
have
these
here
in
the
slides.
We're
trying
to
the
overall
theme
is
common
heisting
labels,
but
then,
as
a
group
there's
a
community,
the
thousands
of
people
have
to
decide-
and
this
is
one
area
where
trying
to
build
a
better
workflow.
B
Why
there
was
actually
no
slides
on
the
tour
of
repos
or
very
few,
because
what
I
did
was
I,
went
to
kubernetes,
cigs
and
kubernetes
in
the
kubernetes
org
and
showed
the
top
pinned
repositories
or
the
most
and
the
most
busy
ones,
and
then
a
couple
few
more
of
interest
and
encouraged
people
to
learn
more
about
those
and
poke
around
personally
on
you
know,
while
the
well,
the
workshop
was
happening
just
because
that's
what
people
are
gonna
see
in
real
life
and
there'll
be
changes
there,
so
yeah,
sorry,
Tim!
That's.
D
Okay,
the
the
next
slide
gets
into
a
set
of
things
that
are
new
because
breaking
into
the
101
section,
one
of
the
things
that
we
were
hearing
kind
of
feedback,
wise
was
some
people
were
also
just
new
to
open-source
and
was
kind
of.
My
contributes
hat
on
I
want
those
people
to
better
understand,
and
especially
as
the
community
grows,
with
more
proprietary
minded
software
getting
people
developers
getting
told
like
hey,
you
need
to
go
work
on
kubernetes
I
wanted
to
put
some
slides
in
about
open
source
process
and
and
that
sort
of
stuff.
D
So
there's
a
series
of
I,
don't
know
eight
ten
slides
something
here.
That
kind
of
talk
about
that,
and
this
was
one
of
the
areas
where
I
was
pleasantly
surprised.
I
had
multiple
people
come
up
to
me
as
we
broke
for
lunch
and
then
also
there
were
a
couple
of
tweets
where
people
are
like.
Oh,
this
is
awesome.
This
is
like.
There
was
one
person
it
was
like
I'm
totally
new
to
open-source
I
never
knew
all
this
stuff.
D
D
So
then
it's
slide
79
and
80.
We
sort
of
transition
from
abstract,
open
source
stuff
to
concrete.
How
does
this
work
these
collaborations,
that
we've
just
talked
about
in
kubernetes
on
github?
So
we
talked
about
the
and
I
think
these
again
are
kind
of
slides
that
have
been
around
for
a
bit
the
our
github
workflow,
how
you,
how
you
get
something
merged,
the
commands
and
the
bots,
and
how
this
is
all
and
then
sort
of
verbally
tying
it
all
back
to
that
other
stuff.
Around
collaboration.
E
F
D
Just
how
have
you
been
able
to
get
the
bits
going?
And
at
this
point
this
is
just
before
lunch.
We
were
actually
well
above
50%
people
were
able
to
they.
They
didn't
know
what
was
happening,
but
they
type
make
and
it
didn't
error
out
it
sort
of
like
sweet.
What
will
follow
on
from
there
and
there
are
a
few
people
during
lunch
to
me,
a
little
more
are.
D
So
we
didn't
we,
we
tried
to
decide
like
what
it
would
take
to
do
that
and
we
went
with
just
one
less
layer
in
the
stack.
You've
got
your
dev
machine
that
you're
going
to
be
using
do
the
things
that
are
native
there
and
at
the
very
beginning,
to
show
hands
zero
people
on
Windows
80,
75,
80
percent,
maybe
were
Mac
or
Linux
in
a
VM
and
then
a
fairly
small
percentage
or.
D
A
D
B
D
B
D
One
of
the
questions
is-
and
this
is
something
that
Grant
and
I
spent
a
fair
amount
of
time,
trying
to
figure
out
and
I
think,
especially
for
Shanghai.
It's
something
we
need
to
think
about
in
in
the
future.
You're
short
on
time
now,
but
do
we
build
and
maintain
a
developer
vm
for
these
playgrounds?
D
B
I
have
what
I
have
what
I
decided
that
if
there
were
enough
people
with
Windows
machines
in
my
workshop
was
I
was
going
to
ask
them
to
pair
with
someone
who
wasn't
so
that
they
can
see
in
the
meantime,
I
do
think.
The
windows
developer
story
is
improving,
so
I'm
hoping
to
actually
go
and
find
out
who
that
is
and
incorporate
them
into
the
next
new
contributor
workshop
yeah.
You.
A
A
A
Have
this
be
at
the
end
of
the
day?
Have
this
be
like
the
last
hour
or
so
of
the
day?
Yeah:
hey,
hey,
you
know
if
you
didn't
come
prepared,
if
you
don't
have
the
tools
in
your
laptop,
etc,
then
you're
welcome
to
leave.
At
this
point
we
watch
people
on
not
just
in
Windows
laptops,
but
an
old
Windows
laptops,
yeah.
D
And
they're
gonna
be
hyper-v
they're,
probably
so
that's
kind
of
what
we
were
doing
thinking
was
that
if
nothing
else,
we've
done
most
of
the
basics
in
the
morning
and
if
people
stumble
in
the
afternoon,
they
could
pair
with
somebody
as
we
go
through
the
actual
doing
things
after
lunch.
But
still
we
had
a
two-hour
block
after
lunch.
It
wasn't
just
the
last
hour.
D
So
after
lunch
we
came
back
and
slides
96
through
107
I
would
say
those
are
kind
of
an
updated
version
of
the
slides
that
had
been
what
I'd
presented
in
Copenhagen
just
more
iteration
on
there,
a
little
more
detail
and
back
then
I
just
spoke
to
all
here,
since
we
had
two
hours.
I
was
speaking
to
him
and
bouncing
back
and
forth
with
the
terminal,
and
everybody
in
the
room
was
also
doing,
and
I
was
amazed
that
basically,
all
of
these
we
were
successful.
D
People
were
actually
doing
building
modifying
running
testing
in
the
room
to
to
varying
degrees,
and
some
of
the
things
take
a
long
time
to
run
so
we'd
sort
of
start
on,
like
okay,
so,
like
you,
can
leave
that
running
or
not
trying
to
go
on
to
the
next
slide.
But
you
see
how
it
works.
It's
in
your
shell
history.
You
can
kind
of
give
it
a
try,
so
we
were
amazingly
successful
there
and
then
on
the
last
one,
which
is
the
one
of
slide
107.
D
D
D
This
is
kind
of
the
the
standard
stuff
again,
but
this
was
at
the
end
because
we
were
just
about
to
move
into
hey
reminder
of
the
cigs
you've
seen
all
of
this
stuff.
Where
would
you
like
to
get
engaged
and
now
we're
gonna
bring
in
all
of
the
cig
leads
and
do
the
cig
meet
and
greet
at
the
end
of
the
day,
and
that
was
that
was
the
overall
101
flow
then
and
in
parallel,
Gooden
was
in
the
other
room,
doing
201
yeah.
B
D
If
you
had
a
cluster
somewhere,
if
we
made
a
simple
local
change
in
cube
cuddle,
you
could
run
your
cube
cuddle
but
also
see
that
it
was
talking
to
something,
but
the
cluster
up
is
actually
a
prerequisite
in
or
a
cluster
based
on
your
code
and
some
form
cluster
up
is
kind
of
the
documented
way
to
run
it
into
n
tests.
Local,
oh
I,.
E
C
B
So
that's
fascinating,
I
think
I.
Think
somebody
commented
on
the
two
one
workshop
that
they
would
have
loved
to
have
this
thing
in
there
as
well.
So
yeah,
it's
it's.
It's
been
tricky.
It's
like
I
think
the
split
is
great,
but
it's
kind
of
been
tricky
and
deciding
which
topic
should
go
anywhere
really.
A
B
B
But
people
asked
really
specific
employed
questions
and
I
think
we
managed
together
to
answer
them
all
and
it
was
cool
because
we
kind
of
just
took
our
time
and
walked
through,
and
it
was
good
that
it
was
ended
by
lunch,
because
by
the
end
of
that
hour,
I
could
tell
people
are
getting
tired.
It's
hard
to
focus
on
dry
stuff
for
that
long.
So
if
you
want
to
do
a
more
I,
can't
hear
you
Josh
yeah,
no
I
do.
A
B
Had
four
hours
late
yeah
we
had
no,
we
had
eleven
to
one
am
I
right,
Tim
I'd
I
mean
I,
don't
know,
I,
don't
know
what
his
schedule
is
good.
D
Question
and
I
actually,
because
I
was
confused
on
this
thinking
about
it
up
front,
I
and
I
was
trying
to
figure
out
how
to
wedge
the
info
into
the
time
and
keep
myself
on
track.
I
made
a
little
spreadsheet.
Let
me
share
this
with
you
all.
Actually
it's
already
you
they're
pasting
it
into
the
zoom.
Oh.
B
A
B
B
It
it
was
hard
to
make
a
connection
between
my
PR
and
what's
happening
on
test
grid
because
test
grid
tests,
a
lot
of
things
and
test
creators
I
think
more
valuable
in
the
context
of
like
overall
conformance
and
less
I'm
like.
Why
is
my
PR
broken?
If
my
PR
is
broken,
I
can
click
the
regular.
You
know,
I
can
look,
look
at
my
PR
and
follow
the
bots
instructions
kind.
B
Yeah,
so
it's
it's
cool,
but
but
we
just
kind
of
decided
it
was
a
little
less
relevant.
Besides
there
is
a
video
up
with
Michelle
giving
it
so
you
know
I
mean
if
people
really
want
to.
We
can
direct
them
to
her
video
and
I.
Don't
think
it's
too
out-of-date
by
now.
Let's
see
yeah
so
so
this
is
kind
of
the
yeah.
We
did
have
five
hours
so
eleven
to
one
yeah,
so
I
did
the
I
did
the
so
that
sorry,
thanks
for
joining
my
memory,
I
think
what
happened
is
I
did.
B
So
I
did
the
core
repository
walkthrough
in
about
an
hour,
and
then
we
had
a
break
and
there
were
snacks
at
the
break,
and
that
was
good
because
I
was
hungry.
I
had
nuts
and
coffee
creamer,
her
breakfast.
It
was
great
and
then,
after
that,
I
basically
assumed
that
everyone
had
their
set
up
already
kind
of
I.
Basically,
everyone
has
go.
Everyone
has
docker,
everyone
has
kubernetes
cloned
locally
and
then
I
kind
of
linked
her
the
developer
guide
and
did
some
of
the
QuickStart
QuickStart
instructions.
B
So
we
built
cube
cut'
all
together
and
that
worked
great
for
the
most
part
I'm,
assuming
that
some
people
self
opted
out
for
this.
Just
because
that's
that's
usually
what
happens,
but
we
basically
yeah.
We
went
off
screen.
We
went
to
the
developer
guide
instructions
I
mentioned
that
they
are
wildly
under
construction,
but
that
this
was
a
good
place
to
start
this
time
in
history.
What
it
is
is
it
goes
to
quick
start.
The
QuickStart
instructions
on
developing
MDE.
B
Then
we
broke
a
test,
so
I
pulled
up
a
test
in
front
of
everybody
and
I
chose
a
part
in
the
repository
and
I
broke.
A
parallel
test
in
front
of
everyone
and
and
I
said
yeah
I
mean
you.
Can
you
can
follow
this
alone?
Let's
try
this
locally
or
you
can
watch
so
I
broke
a
test
in
front
of
everyone
and
then
ran
the
check
again
and
it
broke
the
test
and
that's
how
you
test
packages
individual
packages
rather
than
having
to
run
the
entire
monolith
through
your
tests.
B
B
So
this
this
actually
takes
just
a
few
minutes
and
it's
pretty
easy
to
do
even
as
a
demo
I
kept
mine,
actually
more
demo
focused
unpractical
focused,
because
that
was
the
prerequisite
for
the
people
in
my
class.
That's
kind
of
why
I
had
Tim
do
the
101,
because
it's
actually
harder
to
teach.
Thank
you.
Tim
yeah,.
A
D
You're
being
realistic,
especially
given
the
the
network
issues
that
we
saw
there
and
I
was
amazed
at
how
successful
we
were
in
Barcelona,
so
I
think
it's
right
to
be
pessimistic
on
that
and
plan
to
figure
out
how
to
be
successful.
Instead
of
coming
with
a
set
of
content,
that's
not
going
to
be
successful
and
there
I
think
we.
We
need
Jung,
Lee
and
others
in
Shanghai
to
to
help,
or
in
in
China
in
general,
to
help
figure
out
how
we
could
do
something
here.
D
F
A
I
mean
I
think
we
want
to
go
through
it
step
by
step
enough
that
if
somebody
does
arrive
with
a
full
go
developer
set
up,
they
actually
follow
along,
but
I
don't
think
we
can
expect
people
to
follow
along.
The
other
thing
is:
if
they
took
five
hours
to
go
through
their
101
content,
we
need
to
do
less
yeah.
E
E
D
Think
if
I
I
mean
I'd,
I
can't
do
Chinese,
but
if
I
think
English
to
German,
where
I'm
almost
fluent
ish
the
slides
that
I
added
on
the
build
and
test
flow
with
all
of
the
details,
so
people
could
copy
and
paste
and
and
see
what
I
was
saying
if
I
had
to
translate
those
on
the
fly
in
the
room
forget
about
it.
I.
B
Would
do
really
poorly
cuz
I,
don't
even
know
how
to
talk
about
this
stuff
in
German,
I
run
into
German
people
at
who
comes
all
the
time
and
they
start
discussing
this
stuff
in
German,
with,
like
all
the
technical
terms
in
English,
and
it
just
like
wrecks
my
brain.
Do
you
have
a
to
youngly
like
people
are
mentioned
like
talking
in
like
Chinese,
and
then
they
throw
the
English
technical
terms
in
and
it
kind
of
throws
you
off.
B
Yeah
so
so
we
broke
a
test
or
I
broke
a
test
in
front
of
everyone,
and
people
played
around
with
it
and
tried
it
out
so
I
showed
you
know.
This
is
what
happens
when
you
run
a
test
on
just
like
a
little
bit
and
I
had
a
bunch
of
windows
set
up
previously,
and
this
is
and
now
let's
break
the
test
and
see
what
happens.
B
D
Reminder
this
reminds
me,
oh,
that
the
plan
didn't
work
figure
out
what
it
is.
You're
gonna
do
for
your
content
on
the
the
demo
stuff
and
if
nothing
else
have
the
get
tag
where
you
were
checked
out
at
the
time
recorded,
cuz
just
doing
things
on
head
a
good
chunk
of
my
demos
on
head
KK
master
broke
the
Friday
before
that's.
B
D
B
B
B
We
went
to
the
contributor
playground,
I.
Think
I
commented
on
a
pull
request
or
I
had
I
had
an
open,
I
had
an
open,
PR
issue
and
we
demonstrated
and
played
a
little
bit,
but
we
didn't
do
any
of
the
playground
exercises.
I
just
said
this
is
a
safe
place
for
you
to
see
how
the
workflow
runs,
how
the
bots
go.
Even
if
you
have
signed
the
CLA
I
hit
a
link
to
the
bots
commands
and
we
demonstrated
some
space
kitties.
B
I
showed
basically
I
went
to
this
issue
here,
which
is
not
very
technical
really,
and
it
has
really
well
outline
steps
that
are
easy
to
run
and
I
mean
I
did
it.
I
did
I
did
a
couple
of
them,
and
only
a
few
weeks
before
so
that
I
could
find
some
of
the
gotchas.
Some
of
the
some
of
these
golden
failures
cannot
be
cleaned
up
with
the
way
the
code
is
written.
Currently
so
I
chose
one
that
would
work
and
I
open.
B
A
PR
and
kind
of
you
know
showed
showed
the
labels
showed
everything
in
relation
to
that
and
I
encouraged
people
to
pick
one
of
these
goal
and
failures
and
try
to
do
their
own
poll
requests
and
some
of
them
did
and
I
said.
This
is
basically
your.
This
is
a
really
you
know.
I
understand
this
is
not
writing
code,
but
it's
a
really
easy
way
to
kind
of
work
through
the
mechanics
of
how
everything
works
in
this
community.
B
This
is
going
to
be
your
best
bet
at
experiencing
that,
and
so
basically,
everyone
who
wants
to
could
walk
away
with
with
an
issue
with
a
pull
request,
because
this
particular
issue
has
hundreds
of
potential
pull
requests.
So
it's
a
really
good
source
for
for
newcomers
to
do
some
cleanup.
You
have
to
look
at
the
code
base
as
part
of
it,
because
when
you're,
a
lot
of
these
going
failures
are
like
doc
like
go
doc
failures,
so
you
have
to
know
what
certain
things
are
for
in
order
to
fix
it.
B
A
B
B
B
B
So
that's
that's
not
a
whole.
Lot
of
this
is
just
here's.
The
information
you
need
to
open
a
pull
request.
I
didn't
talk.
What
I
did
what
I
didn't
talk
about
is
good
first
issues
and
Help
Wanted
labels
I
may
have
mentioned
those,
but
I
don't
mention
them
specifically
in
the
slides.
So
that's
something
that
Tim
talked
about
in
his
part
of
the
workshop,
and
we
also
talked
about
you
know
how
to
how
to
get
started.
How
to
find
your
area
in
the
combined
session
in
the
morning,
I.
B
Was
hoping
that,
for
the
sake
meet-and-greet
six
would
a
little
bit
would
be
a
little
bit
more
prepared
with
an
onboarding
mechanism
who
are
there
sig,
but
that
is
something
we're
currently
still
working
on.
Let's
stick
ctrl
X,
actually
Eric
theta
I
mentioned
this
in
sig
testing
like
just
this
week.
He
was
great.
He
said
you
know
every
time
that
I
have
put
the
effort
into
writing
a
good
first
issue.
It's
been
worth
it.
B
D
D
F
D
F
D
D
Sorry
so
there's
a
Lego
Millennium
Falcon.
If
that
was
what
was
above
my
head.
Otherwise
these
are
lights.
They're,
they're,
normal
drop,
hang
lights.
It
made
to
look
like
knob-and-tube
with
old
hundred-year-old
actual
knob-and-tube
stuff.
So
it's
kind
of
going
for
like
a
steampunk,
II
sort
of
retro
light
system,
I
don't
want
to
just.