►
From YouTube: KCS Amsterdam: NCW Planning (EU) 20200204
Description
KCS Amsterdam: NCW Planning (EU) Feb 4, 2020
A
C
E
D
F
B
B
A
E
So
we
want
to
try
and
have
the
schedule
locked
in
and
announced
by
the
end
of
next
week
early
following
week,
so
I
think
in
our
timeline
we
have.
The
contributor
summit
scheduled
is
announced
on
the
14th.
I
would
be
fine,
pushing
that
back
so
I
think
that's
a
Friday
I'd
be
fine,
pushing
that
to
Monday,
but
realistically
we
don't
have
to
have
individual
session
names
for
NCW
101
and
201
people
have
signed
up
for
a
day-long
workshop
and
they
are
attending
the
day-long
workshop.
D
E
D
E
So
if
you
want,
if
it's
gonna,
take
like
until
the
21st
for
you
to
actually
say
like
from
9:00
a.m.
to
10:30
we're
going
over
github
basics,
that's
fine!
We're!
Still!
When
we
publish
the
schedule
going
to
say
this
room
is
going
to
have
NCW
101.
This
rooms
can
have
NCW
201,
and
then
we
can
send
out
a
more
detailed
syllabus
later.
A
Yeah
one
of
my
big
one
of
the
concerns
that
I
have
with
us
pushing
things
out
like
the
content
proposal
is
that
leaves
us
less
time
for
slides
and
slides
are
take
quoted
quite
a
lot
of
time
to
curate
well
just
to
like
fix
things
or
even
though
we
can
copy/paste
last
year's
it's
having
those
slides,
ready
and
then
having
enough
time
for
us
to
practice,
because
I
think
the
content
that
we
have
it's
really
good.
But
the
most
important
thing
that
we
need
to
do
is
to
practice
it
yeah
yeah.
E
So,
from
a
lead
perspective,
if
you
want
me
to
say
you
need
to
have
your
content
proposal
done
by
the
14th,
I
mean
that
to
me,
that
is
an
artificial
deadline,
for
you
feel
free
to
meet
it.
But
if
you
like
want
an
extra
week
to
actually
lock
this
down,
that's
fine
I
would
prefer
it
if
we
can
get
it
done
sooner,
but
I
also
like
don't
know
what
your
time
frame
is
like
I,
don't
want
to
impose
wow
I
need
more
coffee.
I
do
need
more
team
energy
I!
A
B
C
A
C
D
E
Think,
once
the
slides
are
copied
over
and
like
Alison,
you
and
all
the
like
new
contributor
folks
have
gone
through
and
given
it
a
first
pass,
it
might
be
worth
it
not
just
to
like
practice,
individual
pieces,
but
almost
depending
on
how
much
time
we
can
like
block
out
and
who
can
commit
like
run
through
it
with
a
couple.
People
like
I
have
zero
problems
like
blocking
out
a
day
or
two
and
then
just
being
taught
and
then
providing
feedback,
or
you
know
worst
case.
E
We
like
break
it
up
into
like
two
hour
chunks
over
a
week,
but
I
mean
that
might
be
a
good
way
to
run
through
it
and
like
we
can
open
it
up
to
other
people
like
within
Contra
Bucks,
because
I'm
sure
everyone
else
will
have
opinions.
The
one
thing
that
I
always
am
cognizant
of
and
trying
to
avoid,
is
designed
by
committee.
So
whoever
does
join
I
would
want
like
no
more
than
five
or
six
people.
I.
C
Think
the
objective
of
those
meetings
sessions,
whatever
you
call
them-
would
be
to
practice
not
to
comment
on
like
design
or
anything
like
that.
If
something
is
wrong,
obviously
should
be
pointed
out,
but
I
don't
think
the
objective
should
be:
oh
I,
don't
like
the
way
you
know
that's
worded
or
whatever
at
that
point,
unless
it's
like
just
horrible
yet.
E
C
G
I
can
do
that
I
did
it
for
for
San
Diego.
So
I
have
like
the
flow
to
apply
to
the
play
that
I
do
so.
I
can
do
the
the
new
deck
and
then
start
commenting
with
Allison,
and
then
one
wants
to
join
and
then
just
paying
the
people
as
we
need
for
the
new
contributor.
So
meeting
in
San
Diego
just
go
over.
The
slide
add
comments
to
the
slides
and
then
just
work
together
to
have
the
final
one.
So.
A
You,
okay,
I,
think
that's
that
covers
quite
a
bit
of
things.
If
you
can
write
notes,
please
write
notes
because
I'm
not
really
writing
notes,
so
is
so.
The
next
thing
I
wanted
to
go
through
with
everyone
here
is
the
content
proposal,
so
I'm
gonna
just
share.
My
screen
now
hit
the
share
there
we
go.
I
A
I've
just
got
over
here
and
there
I'm,
on
which
I've
been
working
on
is
I've.
Just
I've
got
kind
of
basic,
just
just
some
like
objectives
and
some
timings
on
there
and
a
whole
list
of
things
that
we
should
create
and
some
ideas.
So
if,
if
there's
any,
if
you
have
any
ideas
or
any
feedback-
and
you
can
add
it
to
the
doc
it
would,
it
would
be
awesome
and
also
the
introduction
part
is
yeah.
We
can't
we
can't
elaborate
on
the
thing
and
get
a
whole
proposal,
but
also
as
what
Jeff
said.
J
H
A
E
C
A
B
We
talk
a
little
bit
about
the
to-do
list
there,
especially
the
the
first
bullet,
to
find
the
aim
of
each
of
the
workshops
that
have
been
a
discussion
in
the
past.
We've
only
received
relatively
indirect
feedback
or
low
numbers
of
feedback
on
the
two
tracks,
but
I
think
that
would
be
useful
for
guiding
the
specific
details
within
like
Israel's
building
out
the
101
or
going
through
the
the
list
of
information
there
201
versus
the
the
documents
that
are
on
the
community,
repo
and
under
events,
the
sort
of
module
documents
there.
B
The
lists
there
are
almost
identical
so
as
a
casual
reader
I
can
see
people
continuing
to
be
potentially
confused
on,
which
is
which
and
that's
skewing
just
as
people
walk
in
the
door
at
the
very
beginning
is
it's
confusing?
Should
I
go
to
one
Oh
or
should
I
go
to
the
to
one
based
on
the
content
and
giving
a
little
more
discussion
of
that
I
think
would
would
help
guide
the
next
few
weeks,
better
I.
A
D
A
E
That's
pretty
much
exactly
what
I
was
kind
of
going
for
I,
don't
know,
necessarily
just
in
that
out
like
if,
if,
for
example,
the
like
order
in
which
these
line
items
is
actually
how
they'll
be
presented,
I
kind
of
feel
like
putting
that
at
the
end
makes
the
most
sense,
because
it's
like
how
do
you
talk
to
people
within
the
community?
How
is
the
community
organized
and
then
okay,
now,
that
you
understand
the
community
here
is
how
you
can.
You
know,
find
meaningful
answers
to
your
questions.
A
C
E
That
that's
almost
yes,
I
feel
like
it's.
The
old
adage
of
you
know
give
someone
a
fish
he'll
eat
for
a
day,
teach
someone
to
fish.
You
know
they'll
eat
forever,
being
able
to
because
our
community
and
our
code
base
and
everything
is
just
so
widespread
and
though
we
try
to
keep
things
organized,
especially
if
you're
a
newcomer,
it
is
incredibly
difficult
to
traverse
it.
E
It
alleviates
a
lot
of
effort
if
we
teach
people
how
to
answer
their
own
questions.
That's
ultimately
what
I'm
trying
to
get
to
it's.
It's
almost
like
half
the
time
you
feel
like
there
should
be
a
like
googling
101,
how
to
phrase
your
question:
it's
it's
a
lot
like
that.
We
have
so
many
tools
available
to
us
to
like
find
what
we
need
that.
E
A
This
is
good.
This
is
really
good,
so
another
thing
that
I
also
wanted
to
bring
up
would
was,
with
all
these
tracks,
of
both
the
101
and
201
like
I
want
everyone.
Who's
like
well
I
want
everyone.
It's
really
good
if
we
separate
out
each
part
of
the
presenting
so
that
no
one's
standing
up
there
for
a
long
time
and
we
figure
out
who's
going
to
present
what
early
on.
So
we
know
what
to
practice
and
work
on
as
well.
Does
that
sound
about
right,
yeah.
D
E
A
So
I
feel
once
we
once
we
have
all
the
topics
just
fleshed
out.
You
know
that,
and
we
chuck
some
time
estimates
but
I
feel
that
us
workshop
leads
me
rail
and
Tim
wish
it
all
work
to
see
what
we
should
with
our
teams.
What
we
should
delegate
and
stuff
does
that
sound
about
right
or
am
I
completely
off
here.
H
We
comment
on
that,
once
the
slides
are
updated
and
once
the
speakers
are
identified
right
who
were
going
to
be
presenting
because
each
speaker
has
it
their
own
pace
of
going
the
slides
presentation.
So
just
the
after
deciding
the
presentation
of
deciding
they're
the
speakers
also
just
trying
to
go
through
and
then
consolidate
the
slides
afterwards.
E
Yeah
I
think
Fort
Lake,
once
things
are
copied
over
and
there's
like
that
initial
curation
period,
and
then
you
break
up
who
is
covering
what
topics
I
feel
like
the
presenters
at
that
point,
should
be
able
to
slightly
tweak.
Add
their
own
speaker
notes
that
sort
of
thing
and
I
feel
like
iterating
like
that,
will
yield
a
better
NCW
for
Boston,
and
then
you
know
onward.
E
E
Okay,
but
like
one
of
the
other
things
that
I
thought
of
when
I
was
typing
out,
like
the
answer,
your
own
questions
is
there
is
there
are
limitations,
the
github
search
functionality
that
I,
don't
think
people
realize,
and
so
they
like
type
something
in
and
they
will
get,
they
will
get
something
they
weren't
expecting
like
github
searches,
literally
ignore
special
characters.
So
if
you're
trying
to
like
type
in
you
know
a
go
object,
that's
like
you
get
what
I'm
saying
you're,
not
gonna,
get
that
you're
gonna
get
something
completely.
No
no
I
I
see.
H
Example,
the
kind
right
you
are
Jeff
you're
talking
about
the
kind.
So
if
you
can
look
at
the
link
which
I've
posted
around
the
katic
order,
some
someone
has
posted
on
the
incident
of
staff.
I
think
been
requested
someone
and
then
they
worked
on
this
category
kind
of
stuff
right.
So
if
you
can,
if
you
can
post
these
kind
of
links
right
on
that,
then
it
would
be
like
self
learning
for
them
to
just
go
and
see
what
all
the
issues
they
face
and
they
go
through.
What.
A
E
A
E
E
B
A
G
Well,
I
think
that
we
are
still
half
out
or
two
to
the
side,
the
the
basic
fountain,
but
probably
in
a
week
it
will
be
like
fresh
start,
getting
used
to
his
document
and
then
start
populating,
brainstorming,
any
ideas
and
we
can
like
curate.
The
document
for
the
next
meeting
so
would
have
like
a
better
starting
point.
Now.
We
all
know
this
government
all
we
can,
edit
that
comments
and
between
you
and
I.
We
can,
for
the
next
week,
have
like
almost
final.
A
B
That's
it
I
think,
to
focus
in
on
the
short
list
of
changes
that
are
desired
start
getting
those
nail
down
and
concrete
words,
and
then
that
gives
us
something
to
measure
the
existing
slides
by
that
the
in
prior
ones
is
we've
done
the
copy/paste
and
update
the
template
or
the
open
a
new
copy?
It's
not
really
copy/paste,
but
anyway
you
you,
the
the
basic
bulk
move
accomplished
and
then
the
next
step
is
pruning
to
to
be
pruning
against
a
fairly
fleshed
out
bullet
list
of
topics.
I
think
it
makes
sense
as
a
next
step.