►
From YouTube: Community WG GMT 2017-09-11
Description
Agenda and Notes:
https://docs.google.com/document/d/1vgi434dYkkZHs49EK4F4eMmM-3JG4f3qg-N5En-4ubg/edit#heading=h.c15r23wd99kk
B
C
C
I
am
just
here
to
say
that
I've
started
working
on
a
patch
for
that,
and
so
my
basic
strategy
was,
as
we
had
discussed
before,
to
split
it
into
two
sections
kind
of
a
first-time
contribution,
slash
beginners
contribution
section,
which
will
focus
on
the
github
workflow
and
then
a
second
like
advanced
contribution
section,
which
will
focus
on
the
review
board
workflow
for
people
who
want
to
work
on
more
significant
changes.
Okay,.
D
C
E
I
know
we
have
like
submitting
a
patch
guide
and
all
of
it
is
great
information,
but
it
really
has
to
be
the
very
first
couple
sections
of
the
first
read
me:
you
think
they'll
hit
on
how
to
sub
how
to
contribute
has
to
divulge
the
fact
that
there's
all
this
other
information
to
them
or
they'll,
ignore
it
and
never
find
like
I
mean
heck.
It
took
myself
weeks
to
find
the
readme
in
the
lib
process
folder
and
then
I'm
like
oh
yeah.
This
makes
so
much
more
sense,
of
course,
there's
a
readme
here.
E
That
explains
it,
but
it's
all
the
little
gems
up
front.
You
can
say
like
hey:
there
is
a
docs
folder
that
has
all
the
up-to-date
documentation.
If
you're
working
on
different
subsystems
take
a
look
at
it.
First,
it
seems
obvious,
but
it's
one
of
those
things
that
in
a
sentence
in
the
first
couple,
paragraphs
of
what
somebody
will
find
when
they're
looking
to
contribute
to
my
sauce
can
make
a
world
of
difference
in
how
soon
they
find
the
relevant
documentation.
Okay,.
C
E
E
But
just
like
hey,
hey,
thanks
for
contributing
to
may
sauce
before
we
go
into
how
to
submit
a
patch
just
be
aware
of
this
available
documentation
to
you
that
there
is
a
community
and
then
went
to
the
community
section,
it's
easy
to
find
if
you
know
about
it,
but
if
you
don't
it's
that
kind
of
thing
you
just
want
to
point
them
to
such
as
a
bunch
of
front
loaded
pointers,
it's
great
for
somebody
to
be
able
to
go.
Oh
I
should
bookmark
this
page
go
back
to
it.
E
It'll
tell
me
where
to
find
documentation
later
it
can
be
hard
to
do
right,
but
it's
my
in
my
experience
pretty
useful,
yeah
I'd
love
to
help
you
work
on
it
too.
I
had
to
write
a
bunch
of
documentation
to
get
the
PowerShell
guys
back
in
Windows,
move
it
over
to
github,
which
was
quite
an
experience
changing
their
whole
dev
workflow
I
spent
a
week
citing
Docs
for
them.
It
worked
out
too,
but
yeah.
C
B
A
E
A
F
B
G
D
G
C
Meeting
yeah
yeah
another
thing
that
I
had
noticed
in
the
current
contribution
guidelines
is
that
they
that
one
of
the
first
lines
is
like
so
you
so
you'd
fix
the
bug
or
prepare
to
patch
and
you're
ready
to
submit
it,
and
you
are
probably
not
there
if
you're
reading
that
guy
like
right
so
I
think
we
could
also
walk
people
through
the
act
of
actually
like
finding
something
to
work
on
or
if
they
are
thinking
of
starting
to
work
on
something.
What's
the
correct
process
to
go
so.
B
D
B
Yeah
I
think
that's
the
direction
you're
going
here.
Bandits
they
are
trying
to
focus
more
on
the
newbies
like
the
first
time
contributors
and
try
to
make
it
less
intimidating
and
had
them
just
submit
something
to
get
her
easy-peasy
and
then
once
they're,
getting
into
more
more
like
advanced
contributions.
That's
when
we'll
try
to
steal
them
towards,
like
all
the
review
board
and
JIRA,
and
all
that
stuff
and.
G
B
C
C
C
B
E
B
B
B
A
To
send
an
email
to
the
Linux
Foundation
to
propose
the
topics
for
the
town
halls
and
apparently
I
missed
the
deadline.
So
hey
it's
not
the
format
that
I
thought
it
was
you're.
Just
me
an
email
that
said
that
it's
like
we
should
seed
potential
questions
in
case
people
don't
have
questions.
So
it
sounds
like
it's
not
an
informal
meeting.
It
sounds
like
it's
more
of
a
like
panel
question-and-answer
situation,
which
I
I,
don't
know
that
wasn't
what
it
sounded
like
in
the
schedule,
but
I
guess
it's
a
different
format.
A
So
I
thought
it
was
gonna,
be
like
everybody
hang
out
in
a
room
and
discuss
like
around
a
table,
but
it
sounds.
It
sounds
a
little
bit
more
like
it
might
be
a
Q&A
format,
but
I
have
a
meeting
with
your
to
discuss
what
the
town
halls
actually
are
today,
oh
no,
we
will
find
out
at.
A
I
think
5
p.m.
tell
me
what
I'm
supposed
to
do
for
the
town
halls
and
the
other
thing
is.
He
was,
he
said,
Oh
to
be
a
contact
for
the
town
halls
and
I
was
like
oh
yeah.
Of
course
they
do,
but
it
turns
out
that
they're
all
in
separate
rooms.
Okay,
let
me
down
for
the
D
cos.
1G
is
reading
the
mesas
one
and
there's
another
one
that
yohannes
is
running
on
Cronus
and
marathon.
Apparently,
okay,.
H
B
D
A
So
also
email
out
I'm.
Actually,
one
thing
that
we
should
I
should
do,
though,
is
to
email,
the
the
working
groups
to
say
like
hey.
If
you
want
to
go
to
the
bassist
Town
Hall
go
and
meet
your
fellow
working
group
members,
so
I
still
think
we
should
encourage
people
to
go
there
to
meet
their
working
groups,
but
I'm
not
I'm,
not
entirely
sure
that
we'll
be
able
to
break
out
in
the
way
that
I
thought
it
was.
Okay,.
B
B
A
B
A
B
B
B
B
B
A
B
B
So
maybe
that's
something
that
you
can
keep
on
tracking
on
your
interest.
If
you
can
chat
with
developer
educator
and
communities
to
see
what
they
did,
all
those
things
they
pull
to
get
a
better
good
slack
account
yes,
and
for
me
the
biggest
thing
I
think
we
want
is
like
unlimited
message.
History
so
right
now
a
bit
annoying
to
use
third-party
tools
to
backup
and
doesn't
support
DM
like
DMC,
being
back
logged,
backup
somewhere
and
also
the
fact
that
we
don't
have
good
stats
in
our
free
account.
B
It's
time
to
look
at
some
stats
this
morning
on
how
we
are
doing
in
terms
of
users
and
messages
and
channels,
and
they
don't
give
that
that
good
of
em
you
in
a
free
account.
So
it
will
nice
to
get
those
things
to
kind
of
keep
track
on
how
we're
doing
in
terms
of
some
of
the
community
metrics
place
of
slack
slack
usage.
E
Not
really
for
me,
I'm,
quite
interested
in
helping
out
with
the
getting
started
documentation
just
yeah
I've
been
through
a
lot
of
it.
I'm
like
some
of
this
could
be
easier
found.
B
B
B
Maybe
we
can
propose
that
as
an
idea
and
the
hackathon
Andy
and
see
if
we
have
people
who
want
to
update
should
mostly
be
committing
coming
from
committers
I
feel
like
the
most
knowledge,
but
contributors
also
who
have
contributed
big
pieces
of
features.
There,
of
course,
have
a
lot
more
knowledge
about
that
particular
bit
that
they
can
contribute
to,
and
then
someone
can
review
and
committed
to
a
great.
B
Cool
tool-
oh
that's
all
I-
think
I
had
yep.
D
B
D
G
G
No
just
like,
if
you,
if
you
go
to
read,
to
read
the
docs
I,
think
there's
some
structure
there,
but
it's
it's
just
based
on
folders,
okay,
hamsa.
It
doesn't
it's
not
smart
right.
It
doesn't
know
how
we
want
to
go
after
it.
So
you
know
people
can
go
there,
but
since
most
people
probably
go
to
the
website,
it
would
be
nice
to
like
you
know,
when
you're
in
a
documentation,
page
to
kind
of
see
where
you
are
like.
D
B
C
B
G
G
B
G
B
G
B
Right,
yeah,
yeah,
okay,
we'll
see
if
we
can
do
something
in
hackathon,
otherwise
we'll
do
it
as
part
of
the
docket
and
they
probably
trying
to
a
different
day
beep.
You
haven't
scheduled
that,
but
that's
what
I
was
talking
about
where
we
right
okay
schedule
a
day
for
people
to
just
just
work
on
doc.
Dachshund
can
go
beer.
C
B
C
D
B
It
never
got
completed,
I
think
there's!
The
last
I
remembers
are
some
comments
from
house
dent
and
then
I,
don't
think
Tim
actually
updated
it
or
even
if
you
updated
it
may
be
harsh
and
and
committed
so
I
can
touch
base
with
with
house
and
and
see
the
status
of
that
one.
Okay.
When
actually
done
for
me
on
that
one
yeah.
G
D
Cool
anything.
B
G
B
C
B
G
A
G
Don't
like,
even
if
it's
something
very
trivial
someone
will
like
you
like,
hey
here,
Ben
can
do
this
like
what
the
I,
don't.
That's
not
like
it.
I
just
do
this
because
we
need
to
do
it
I,
don't
really
so
I
do
it
know
quite
a
bit
about
how
its
structured
now
if
people
want
to
ever
like
I,
can
help
people
but
I
I,
don't
want
to
kind
of
keep
having
to
do
all
this
renounce
mostly
like
Houston
and
me
and.
G
G
G
B
Yeah
I
think
here
we
should
make
sure
when
we
finally
big
peaches,
what
are
the
things
that
we
need
to
address
like
changes
to
documentation
and
changes
to
the
web
UI
and
make
it
part
of
the
process
for
big
features
and
try
to
follow
that?
True,
most
people
just
work
on
features,
and
then
they
want
something
else
before
wrapping
up
some
of
these
things.
So
it's
we
need
to
make
sure
when
we
file
like
feature
epics
that
that's
taken
care
of
as
well.
G
B
B
E
E
B
G
Can
we
just
reiterate
the
action
items
quickly?
I
just
want
to
write
down
the
one
that
I
was
gonna.
Do
it
there,
yeah
I
was
going
to
send
an
email
just
to
remind
people
to
help
me
figure
out
if
there's
any
features
that
I
need
to
catch
up
in
the
web
UI
or
if
there's
anything,
they
just
want
them
through
there
yeah
you
were
gonna.
You
were
gonna
schedule,
some
time
to
look
and
do
like
a
Doc's
day
which
may
or
may
not
overlap
with
the
time
that
we'll
look
into
like
the
left-hand
navigation
stuff.
G
B
B
G
Just
I
guess
a
quick
means.
No,
no
just
now
we're
just
free-balling
right,
I,
just
curious,
like
you
know,
one
thing
that
as
soon
as
I
think
about
is
which
kind
of
made
me
was
one
of
the
reasons.
I
was
also
thinking
about
the
newsletter
thinking
when
we
started
talking
about
that
was,
if
you
look
at
something
like
lwn,
I,
actually
know
what
that
stands
for
Linux.
G
B
G
B
B
Yeah
so
I
think
the
way
that
we
are
approaching
it
is.
We
are
asking
like
shepherds
about
things
that
they're
working
on
or
that
recently
wrapped
up,
that
they
want
it
to
be
called
out
and
then
we'll
call
that
out
in
the
newsletter
to
get
people
an
update
on
what
recently
happened
and
what's
happening
right
now,
and
my
words
planned
in
the
very
near
future
campaign
to
get
people
excited
and
make
it
informative
for
people
who
don't
follow
the
mailing
lists
and
all
that
it's
too
much
noise
for
a
lot
of
people
right
yeah.