►
From YouTube: SIG Contributor Experience 20180228
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
A
This
is
just
a
reminder
that
this
week
we
will
not
be
talking
about
automation
or
workflow.
We
will
save
that
for
bi-weekly
meetings.
These
meetings
are
for
people
of
the
project
as
I
call
it.
So
anything
that
has
to
do
with
mentoring,
roles
and
responsibilities
with
an
organization
volunteer
opportunities,
contributor,
died,
information,
anything
documentation,
related,
etc,
etc.
A
So
we
do
have
a
full
agenda.
I
know
we
have
a
lot
of
small
items
to
to
get
through,
so
we'll
probably
get
through
this
relatively
fast
George.
Do
you
want
a
cake?
Actually
I'm?
Sorry,
Arthur
I,
don't
believe
any
new
contributors
on
the
line,
nope
I
see
all
places
that
I
know
I,
don't
think
I,
don't
think
Mario's
been
to
this
call.
Yet,
though,
everyone.
A
C
Telling
my
co-workers
to
shut
up
because
I'm
in
the
office
I
am
Mario
Lauria
I'm
from
Ann
Arbor
Michigan
a
little
mile
from
George
I,
see
him
monthly
at
a
local
native
I
started
called
ARCA
structure
around
DevOps
and
infrastructure
concepts
and
people
in
the
community
and
I
have
kind
of
recently
started
to.
You
know:
come
to
these
meetings
and
being
more
involved,
so
I
look
forward
to
doing
a
lot
more
stuff,
I'm
also
on
office
hours
as
well,
so
yeah,
it's
gonna,
be
fun
and.
A
B
So
I'm
gonna
I'm
gonna
just
stick
the
URL
for
the
spreadsheet
and
slack
so
we
don't
lose
it
in
the
zoom.
And
so
this
is
the
community
meeting
trekker.
So
here's
what
happened.
We
all
went
to
a
face-to-face
and
then
we
forgot
to
assign
a
host
week
and
then
none
of
the
six
showed
up
because
we
forgot
to
remind
them
so
we're
gonna
do
is
scheduled.
Hosts
ahead
of
time
and
I
figured
every
contributes
meeting.
B
B
The
whole
world
doesn't
fall
apart,
so
Solly
Ross
is
gonna
do
next
week
and
that
after
that
is
myself
and
then
Paris
and
I
figured
every
meeting
will
just
confirm
what
the
three
you
know,
the
upcoming
three
three
weeks
worth
so
I
added
that
on
the
spreadsheet
and
then
the
spreadsheet
also
has
when
all
the
SIG's
are
going.
If
you
look
for
222
that's
the
week,
we
didn't
remind
any
SIG's.
B
So,
if
you
don't
remind
them,
they
don't
show
up
so
I
think
what
we're
gonna
do
is
when
it's
your
week
to
host
you
you're
responsible
for
basically
chasing
down
the
SIG's
and
I,
constantly
publish
this
URL
to
sig
leads,
and
it's
at
the
top
of
the
community
notes.
So
we
need
to
basically
continue
to
remind
them
that
hey,
you
know,
you're
going
on
a
schedule
now,
so
hopefully
we
will
get
any
of
the
oh
I'm
totally
surprised
by
this.
So
so
for
sure
we
have
to
chase
on
the
SIG's.
A
B
A
That's
good
next
agenda
item
is
outreach
for
meet
our
contributors
and
office
hours.
I
did
include
the
mentorian
sign-up
sheet,
which
has
a
tab
for
meet
our
contributors.
George.
If
you
could,
in
the
agenda,
insert
the
office
hours
link
for
me.
A
I
just
didn't
have
time
to
do
it
not
necessarily
right
now
sure,
but
I
won't
speak
for
George,
but
on
the
meet
meet
our
contributor
side,
we
definitely
could
use
some
more
folks
signing
up
right
now
we
have
a
pretty
standard
set
of
people
and
I'd
like
to
have
a
rotating
a
rotating
meeting,
but
luckily
for
our
next
one,
which
is
March
17th,
I'm,
gonna
I'm,
not
I'm.
Sorry,
not
March,
17th,
March
7th,
which
I'll
put
in
here
as
well.
A
We
do
have
a
full
schedule
and
we
actually
have
a
second
time
zone
opened
up
now,
which
is
awesome,
so
you'll
have
I
think
it's
like
a
3:30
p.m.
UTC
and
a
9:00
p.m.
UTC
time
slot.
So
it's
great
that
should
get
us
most
of
the
globe
covered
at
reasonable
hours
and
then
George.
Do
you
want
to
say
anything
about
office
hours,
yeah.
A
D
A
A
How
did
you?
How
did
you
join
open-source?
Why
did
you
join
kubernetes
and
we
take
questions
from
slack
and
Twitter
and
it's
about
an
hour
and
then
what
we
are
also
trying
to
do,
which
we
can't
seem
to
get
enough
motivation
for,
but
a
lot
of
people
seem
interested.
Is
a
live
peer
code
review
this
time
from
one
of
the
time
slots
we
do
have
a
live
Doc's
code,
it's
not
going
to
review
a
live.
B
We
also
need
developers
to
commit
to
office
hours
so
unfortunately,
like
Ilya
was
the
only
person
to
show
up
in
the
Europe
timezone
and
Mario,
basically
powered
through
the
West
Coast
time
zone
cuz
we
were
all
at
the
face-to-face,
so
it
actually
happened,
but
I
I
feel
like
we
kind
of
let
everybody
down.
You
know
by
not
chasing
down
people,
so
what
I'm
doing
now
is
basically
being
more
explicit,
so
I
went
back
to
work
and
said:
I
want
us
to
commit
like
commit
commit
on
the
schedule
with
an
engineer.
B
So
if
we
can
find
people
who
are
willing
to
commit
to
put
it
on
their
calendar,
I
think
that's
a
good
good
way
to
go
because
the
users
are
showing
up.
So
we
have
to
like
give
them
something.
On
top
of
that,
the
marketing
team
at
CFCF
is
now
actively
tweeting,
so
I
noticed
they
started
tweeting.
Yesterday,
I
made
a
blog
post,
are
gonna,
publish
it
all
that
stuff
we're
gonna
link
to
it,
so
the
CFCF
is
actually
ramping
up
the
marketing
for
this.
C
B
That's
one
of
those
things
where
normally
I
spent
that
whole
week
chasing
people
down
and
then
we're
at
the
face-to-face,
and
it
didn't
happen.
It
was
just
like
so
at
least
we're
finding
bus
factor,
stuff
and
Paris.
They
will
do
the
same
kind
of
marketing.
For
your
ask
our
developers
thing
as
well,
so
hi
I'm,
a
blog
post
yeah
that
actually
took
much
longer
than
I
thought
it
would.
A
That's
how
it
usually
works
all
right,
so
anybody
have
any
questions,
concerns
comments
about
office
hours
and
or
meet
our
contributors,
or
maybe
how
we
can
advertise
for
this
better.
Like
George
mentioned,
CN
CF
is
going
to
ramp
up
marketing
efforts
around
this
stuff.
So
that's
always
a
plus,
but
if
anybody
else
has
any
other
suggestions,
we're
happy
to
take
them.
B
A
Works
out
alright
and
then
I'm
the
agenda.
There
is
a
link
for
a
pull
request
that
just
went
in
I'm,
actually
looking
to
see
if
it
was
approved.
No,
it
has
not
been
approved,
yet
it's
still
open.
This
is
for
moving
the
maintainer
role
and
merging
it
into
owner.
So
this
has
to
do
with
the
community
membership.
Excuse
me,
I
have
a
cold
too
I
feel
like
I'm
talking
out
of
my
ears
kind
of
but
anyway.
So
this
is
removing
the
maintainer
role
and
marking
it
into
the
owner.
A
A
Does
anybody
have
any
immediate
questions,
concerns
or
comments
about
this?
So
this
would
mean
that
we
now
have
member,
which
is
the
first,
which
is
the
first
step
on
the
ladder
reviewer
like
code,
reviewer,
doctor
viewer
and
then
approver
and
then
owner
so
owner
would
be
the
last
wrong
and
again
this
is
all
stuff.
That's
being
worked
on
tying
things
and
code
to
owners
files
within
the
repos.
B
A
B
Basically
said
we
have
meetings
and
we
decide
to
do
stuff,
and
then
we
start
public
Westing,
but
if
at
any
time
you
feel
that
something's,
like
a
surprise,
absolutely
posts
on
there,
they're
all
approach
steering
committee
he's
basically
saying
you
know
we're
all
approachable.
If
something
like
this
catches,
you
off-guard
ask
us
to
put
on
the
list
and
we'll
do
so.
Yeah.
E
D
D
F
So
so
kind
of
just
jump
in
here.
This
is
my
friend
real
quick
with
something,
though
communication
hasn't
been
a
strong
suit
around
here
and
so
like
how
many
people
are
gonna
go
watch
the
YouTube
channels
for
what
it's,
probably
a
boring
bureaucracy
meeting
a
lot
of
times,
or
at
least
that's
the
perspective-
that
a
lot
of
people
shares
and
how
many
people
are
gonna
want
to
want
to
go,
spend
their
time.
F
Reading
the
meeting
minutes
on
what
is
gonna
be
seen
or
perceived
as
a
boring
bureaucracy
meeting
with
little
movement,
it
might
be
worth
them
saying.
This
is
a
decision
that
affects
you
here
is
the
executive
summary
on
it.
If
you
want
to
know
more
go
here
and
send
that
out
to
kubernetes
dev
anytime,
this
happens
because
otherwise,
most
folks
are
gonna
be
like
I
was
oblivious
I
ignored
it,
because
it's
bureaucracy
in.
D
B
B
You
know
as
part
of
contributor
experience,
so
maybe
maybe
we
should
run
interference
between
the
Senate
committee
and
everyone
else
would
be
like
hey
I
noticed
you
guys
are
discussing
this.
You
might
want
to
run
that
by
kubernetes
to
this
by
community.
You
know
basically
kind
of
be
there
to
remind
them
that
a
this
affects
a
lot
of
people.
You
might
want
to
run
this
by
the
list.
So
I
mean
I,
always
watch
the
meeting,
so
maybe
I
start
doing.
A
Yeah
I
watch
intermittently
I'm,
not
gonna
lie
I.
Try
to
when
I
can
I
mean
another
thing
we
actually
I.
Don't
want
to
talk
about
it
now.
I
want
a
sidebar
it
for
a
few
weeks
is
that
we
can
transcribe
videos.
So
we
have
the
technology
that
powers
that
so
I
mean
at
Google
and
there's
plenty
of
other
api's.
That
will
help
us
with
transcribing
videos
and
like
podcasts,
do
so.
I
think
that
we
should
definitely
do
that
more
and
project-wide
so
like
to
Matt's
point.
Not
many
people
had
the
time
to
watch.
A
Videos
I
totally
agree
with
that.
So
alright,
any
other
last
items
I
put
on
the
meeting
notes
that
we're
taking
an
action
can
steering
committee
post
changes
to
mailing
lists.
Can
they
have
like
a
communication
pipeline
process,
I,
actually
kind
of
want
to
set
an
issue
with
the
steering
committee
repo
to
see
if
we
can
get
them
on
a
cute
like
a
communication
schedule
or
if
one
of
us
from
contributor
experience
can
be
that
liaison
and
post
everything
for
them?
A
E
What
the
steering
committee
is
trying
to
say
is
away
from
is
the
need
for
write
access
to
the
repo
which
is
fine,
but
the
other
part
of
it
is
like
it
describes
a
rung
in
the
ladder.
That's
somebody
who
has
you
know
a
degree
of
responsibility
around
holistic
health
of
the
project
and
I.
Don't
know
you.
We
move
away
from
a
defined
maintainer
role
that
it
comes
with
associate
github
permissions,
I,
don't
know
if
we
in
contributor
experience
want
to
think
about.
E
E
If
that's
something
that
if
we
move
away
from
maintainer
role,
as
is
that
we
would
want
to
consider
thinking
about,
is
there
a
place
for
holistic
project,
health
and
people
who
are
keeping
that
in
mind
and
caring
about
holistic
project
housed
in
core?
Or
does
that
does
not
make
sense
as
the
world
is
today.
F
E
Well,
it
depends
on
what
you
mean
by
owners,
because,
again
you
know
the
owners
owners
are
typically
scoped
to
a
part
of
the
code
in
the
repo
in
in
core.
We
have
the
top-level
owners
file,
so
those
people
are
definitely
you
know
caring
about
holistic
project
health,
but,
as
is
those
top-level
owners,
are
also
being
the
bootstrap
committee
they're
the
like
they're,
all
on
the
steering
committee
right
now
so
they're
already
caring
about
holistic
project
health.
E
But
you
know
again
that
idea
of
that
role
made
may
not
translate
today.
I
was
just
put
throwing
out
the
idea
of
like.
Maybe
we
should
think
about
that.
Like
does
that
responsibility
we're
pulling
out
the
github
permissions
that
it
does?
Is
there
a
need
for
a
rung?
That's
caring
about
the
holistic
project,
health,
as
opposed
to
their
part
of
the
coke?
What
that's
you
know,
network
code
or
scheduling,
code
or,
and
something
like
that.
F
A
F
A
Necessarily
think
we're
getting
rid
of
that
element.
I
think
that
element
has
now
seeped
into
multiple
multiple
facets
of
this
project,
like
the
cig,
like
cig
architecture,
when
Matt
said,
like
the
steering
committee,
so
I
think
there's
multiple
bodies
of
folks
here
who
care
about
that
now,
so
not
necessarily
defining
that
by
a
membership
status,
but
definitely
still
comment.
I'm
very
curious
to
see
would
like
Phil
and
Brian's
have
to
say
about
that.
Yeah.
A
A
A
A
Alright
next
up
is
to
charter,
so
the
Charter
has
been
waiting
review
for
a
few
days
now
kind
of
same
store
there,
with
the
with
projects,
I'm
gonna
fix
any
last
for
meaning
that's
today,
I
did
fix
a
lot
of
them
yesterday
as
well.
So
this
is
last
chance
to
update
for
version
fun.
There
are
some
things
that
were
still
to
doing
at
the
bottom.
One
of
the
things
that
I
actually
wanted
to
talk
to
this
group
about
to
hear
feedback
is:
how
are
we
collecting
feedback
about
this
sake?
A
That's
actually
something
I'm
gonna
put
on
the
agenda
here.
How
are
we
collecting
feedback
from
the
cig?
Are
we
doing
our
job?
Are
the
leads
performing
okay
and
that's
something
that
I
don't
know
I'm
also
getting
kicked
out
of
this
room
right
now?
Does
anybody
have
any
suggestions
on
how
we
should
collect
this
performance
feedback.
A
I
mean
that's,
that's
a
suggestion,
so
I'm
just
curious
to
see
what
other
people
say:
I
mean
I'm,
I'm,
totally
game
with
may
be
doing.
Regular
surveys
like
a
specially
anonymous
survey
is
I
know.
Folks
might
not
want
to
tell
me
to
my
face
that
you
know
I'm
not
doing
a
great
job
but
for
reasons,
but
I
still
want
to
hear
that
information.
So
I
was
thinking
of
at
least
twice
a
year,
sending
out
a
contributor
experience
survey
of
what
are
we
doing?
A
How
do
our
prize-
and
this
is
another
reason
for
the
project's
markdown
file
of
how
are
we
doing
against
these
projects
or
these
projects,
something
that
we
should
be
working
on,
etc?
So,
if
anybody
else
has
any
comments
about
that
leave
it
on
the
dock,
so
we
can
do
that
and
then
what
I
want
second
I'm
getting
kicked
out
towards
you
want
to
take
it
over
for
graph
of
the
week
and
then
I'm
gonna
hop
it
into
another
room.
Sure.
B
So
graph
on
the
week
for
this
week,
Josh
already
volunteered
so
I
think
we're
good
there.
What's
next
I've
got
the
next
item
so
there's
this
company
called
Pensieve
that
sent
me
a
mail
randomly
that
it
basically
takes
questions
that
people
ask
in
slack
and
then
indexes
them
and
then
there's
like
a
bot
that
it
uses
machine
learning.
So
if
a
new
user
joins
and
they
ask
a
question
and
the
buff
thinks
it
knows-
a
pm's
then
was
like
hey
here's
some
possible
solutions.
B
I
sent
a
video
of
this
to
the
dev
list,
maybe
last
month
and
a
lot
of
people
showed
interest.
But
when
they
came
back,
a
pricing
was
per
question
and
I
was
like
there's
no
way.
That's
gonna
fly
with
30,000
people
in
kubernetes
users,
so
they're
open
to
changing
that
talking
to
us.
So
they
basically
said
hey.
Why
don't
you
try
it
free
for
a
few
weeks
on
kubernetes
users,
and
then
we
can
talk
about
that.
So
I
posted
some
feedback
in
kubernetes
users
and
I.
B
D
B
I
was
debating
doing
novice
first,
but
the
way
they
explained
it.
It
sounds
like
the
more
corpus
it
has
initially
the
better.
It
will
be
so
the
way
it
works
is
it
will.
It
will
sit
in
the
channel
silently
and
then,
when
it
thinks
a
user
is
asking
a
question.
It
will
spam
a
group
of
us
which
I'll
define
and
then
I'll
say.
Okay.
That
seems
like
a
good
question
index
this
one
index
this
one
in
Nexus,
one
collagen
and.
D
B
B
B
You
know
the
way
she
explain
it
to
me
and
all
that
kind
of
stuff
and
I
looked
at
the
video
how
to
actually
works.
It
looks
like
something
that
could
be
relatively
transparent
and
I
think
it
might
be
a
tool
that
we
would
give
to
people
who
sit
in
kubernetes
users
and
might
see
all
these
questions
popping
up
every
once
in
a
while
and
I'm
thinking.
We
would
enable
them
give
them
the
bot
powers
to
kind
of
manage
the
bot.
B
We
could
crowdsource
it
a
bit
across
time
zones
and
then,
as
new
users
join,
and
they
ask
us
a
relatively
easy
question:
the
bots
will
PM
them
transparently
and
then
I
think
that
will
actually
help
kind
of
funnel
people
into
the
right
places.
Brian
gran
has
some
questions
about
like
how
will
this
integrate
with
Stack,
Overflow
and
stuff
and
there's
a
whole
bunch
of
medium
and
long
term,
things
that
we
need
to
look
at
but
I.
You
know,
I
figured
they're
gonna,
give
us
a
free
three
weeks
to
kick
the
tires.
B
We
should
give
it
a
shot.
I
mean
we'll
see
how
well
it
works
and
then
get
feedback
from
the
community,
and
if
you
like
it,
you
know
approaches
CN
CF
about
I,
don't
know
how
the
commercial
licensing
works,
but
you
know
before
having
those
discussions
I
wanted
to
see
if
users
liked
it
so
I'll
probably
turn
that
on
this
afternoon,
so.
B
A
B
A
A
All
right,
cool
I
just
wanted
to
make
sure,
because
I
was
super
rude
and
ran
out
of
that
room.
All
right
group
mentor
and
we
are
currently
in
well
actually
almost
complete
with
the
mentoring
test
code
work
that
we
have
going
on
here.
There's
been
a
lot
of
lessons
learned
on
my
end
about
how
to
facilitate
this,
one
of
which
I've
been
very
vocal
about,
which
is
to
not
have
multiple
time
zones
in
the
same
cohort,
but
there's
some
other
things
that
we
need
to
do
like
curating,
more
camaraderie
and
things
along
those
lines.
A
But
we
are
I,
am
in
the
middle
of
forming
a
new
quote,
a
new
cohort.
This
will
be
new
contributors
to
members
and
I.
Think
right
now,
I'm
going
to
be
like
it's
not
official
yet,
but
so
far,
storage
and
CLI
are
interested
and
I'm.
Looking
for
one
more
one
more
sake
for
that
I'm
going
to
write
up
a
lessons
learned
shortly
as
well
from
like
I
said
what
we've
learned
I
know:
Chris
is
on
the
line
too
he's
been
the
mentor
for
kube
ADM
I
mean
tops,
oh
my
god
wrong.
A
One
chris
has
been
mentoring,
tops
for
individuals
within
that
group,
so
I'm
sure
he
can
give
some
perspective
there
too,
but
we
definitely
have
a
lot
more
work
to
do
a
lot
more
documentation
to
do
for
this
idea.
I
do
think
it
will
work
eventually,
I.
Don't
necessarily
think
that
the
one
that
we're
currently
running
is
necessarily
the
most
successful,
but
at
the
same
time
this
is
new
and
unchartered
territory
for
open
source.
D
E
D
A
Know
one
percent
I
think
that
goes
back
to
the
time
zone
thing
where
we
should
definitely
set
a
time
in
the
beginning.
I
was
I,
was
so
empathetic
and
like
tried
to
get
this
off
the
ground,
so
I
figured.
We
could
like
do
a
round
robin
for
meeting
times
and
time
zones
and
things
like
that
and
it
just
my
empathy
killed
us
essentially.
D
It
may
have
killed
you
personally
yeah.
It's
really
good,
in
my
opinion,
I
agree
with
what
you,
with
the
feedback
that
you
said
in
terms
of
more
engagement,
public
engagement,
I
think
there's
been
lots.
At
least
within
our
group.
There's
been
lots
of
engagement,
the
two
primary
gentlemen
that
I've
been
working
with
one.
So
there's
three
that
I
have
one
of
them's
been
doing.
Alright,
two
of
them
have
just
been
doing
rock
star
work,
so
you
know
that's.
H
A
D
A
He
did
an
actual
code
review
and
like
actually
talked
out
loud
about
what
the
things
were,
that
he
was
saying
and
and
how
some
some
trends
impact
the
review
and
it
was
really
great,
and
then
we
also
in
a
communication
session
from
Laurie
Apple,
who
talked
about
empathy
and
talked
about.
You
know
your
what
you
say
on
github
is
public,
etc,
etc,
and
that
was
really
good.
And
then
this
week
we
actually
are
having
a
testing
session
and
a
doc
session.
A
Instead
of
what
we
have
right
now
we're
all
new
contributors
are
on
the
page
of
their
state
or
they're
working
through
for
their
sub
project
or
they're
outside
kubernetes
repo,
which
you
know,
I
guess
it's-
okay
for
for
that,
sub-project
etc.
But
from
like
the
the
grand
perspective
of
you
know
like
when
Christoph
and
others
are
trying
to
change
automation,
that
kind
of
stings
so
coming
up
with
this
learning
and
development
portal
is
a
part
of
this
project.
Essentially,
so
that's
what
I
was
getting
at
with
us.
A
B
D
A
Problem
with
that,
though,
is
like
especially
in
the
Laurie
Apple
session.
I.
Think
some
of
the
people
that
were
responding
to
her
we're
responding
from
very
honest,
honest
takes
I
mean
I,
will
I
will
gladly
ask
everyone
if
they're
comfortable
with
publishing
this
to
YouTube,
but
you
know
she
was
asking
some
very
personal
questions
like
tell
me
about
a
time
when
somebody
was
not
nice
to
you
on
a
gift,
a
comment
and
like
how
are
they
not
nice
to
you?
You
know
in
that
kind
of
fashion
yeah,
maybe
where
it's
appropriate
right,
yeah
yeah,
maybe.
B
B
D
A
Just
gonna
say:
I
did
ask
Layton
to
do
a
102
session
as
well
so
Clayton's
on
I
just
need
to
hear
back
from
him
on
that
I'd
like
to
ask
every
steering
committee
members
essentially
founders
to
do
a
session
on
something
so
that
we
could
have
a
brain
dump
in
some
area
and
I.
Think
that
would
work
really
well
for
us
too,
because
then
again
we
can
build
docks
around
those
das
there
doing
nothing.
A
H
H
D
I
A
D
A
And
it's
not
necessarily
goofy
it's
just
that.
Every
time
I
tell
people
that
they
think
that
they're
piloting
kubernetes.
So
no
like
hey
we're
gonna
try
out
test,
drive
uber
nettie,
it's
not
necessarily
like
you
know,
because
then
in
the
world
of
testing,
you're
piloting
something.
So
that's
the
the
feedback
that
we've
been
getting.
Some
people
love
it.
Some
people
are
like
and
different,
so
I
guess
in
the
back
of
everybody's
heads
between
now
and
the
next
week.
A
G
Yeah
no
I
mean
just
minor
thing
that
I
think.
Oh,
we
need
a
name
which
is
more
like
itself.
You
know
in
to
do
right,
self-described
what
that
what
it
is
right
at
something
you
know
just
look
at
the
name
and
say
hey.
This
is
for
mentoring,
so
I
think
not
like
fancy
name
but
just
very
simple
name,
which
you
uber.
G
H
A
I
I
A
I
B
A
A
So
if
you
do
not
want
to
help
with
this,
it's
we
have
about
ten
minutes
left
and
I'm
I'd
really
like
to
work
on
this
because
I
want
to
ship
this
today,
George,
you
won't
stay
on
the
line
and,
like
I
said,
if
anybody
else
wants
to
stay
on
the
line,
I'll
share
the
dock
with
you
and
we
can.
We
can
go
through
it
cool
all
right.
So
let
me
share
the
dock
here.
A
A
G
A
It
looks
like
it
looks
like
Sodom.
We
do
need
a
few
more
things
actually
covered.
I,
don't
know
if
you're
interested
in
doing
this,
but,
like
I
said
it
would
just
be
going
to
that
saying
and
saying
that
you're,
a
member
of
contributor
experience
and
then
the
script,
that's
on
the
that's
in
the
other
tab
that
says
script
next
to
cigs.
This
is
what
will
be
polished
up
and
sent
with
you
to
their
agenda.
A
A
For
instance,
one
of
them
is
issue
triage,
like
what
do
we
want
to
tell
them
about
issue
triage
and
and
mine?
You
will
most
likely
have
maybe
ten
minutes
to
go
through
all
of
these
things,
so
it's
just
a
high
level
of
what
this
is
and
then
the
docs
to
explain
it
further
and
then
get
any
like
high
level
questions
from
them
that
they
might
have.
G
Not
absolutely
found
that
he's
saying
I'm
looking
at
the
docs,
so
I
think
I'm,
sorry,
yeah,
I
think
that
was
a
little
tricky
for,
but
the
way
on
this
two
days.
Basically,
we
represent
country
backs
at
this
one
particular
or
you
know
one
of
these
things
and
sort
of
brief
about.
What
are
you
doing
right
so
in
my
case,
say
I
can
break
all
of
these
to
be
outside
that
speak
and
is
that
gonna
be
all
to
see.
So
we
just
thinking
turned
on
the
scene
so.
A
G
A
So
let's
scrub
this,
let's
scroll
this
up
a
little
bit.
Alright
Stata,
if
you
have
number
three
so
like
I,
said-
include
on
line
three
include
the
issue
triage
links
that
you
want
feedback
on
and
anything
that
you
think
that
people
should
have
from
a
documentation
perspective
there
I
will
take
I
will
take
line
four
and
then
the
other
thing
to
set
up
is
that
we
all
have
to
be
comfortable
talking
about
every
one
of
these
issues
at
a
very
high
level,
so,
for
instance,
for
mentoring
strategy.
What
we
should
be
doing
is
asking
them.
A
How
are
you
growing
your
current
contributors?
You
have
a
strategy
like
that's
what
we
want
to
know
and
then
then,
of
course,
how
can
we
plug
you
into
what
we're
already
doing
and
the
what
we're
already
doing
piece
is
going
to
highlight
things
like
meet
our
contributors.
Why
don't
you
send
a
contributor
to
this?
This
is
like
learning
on
demand.
A
A
I've
been
doing
sort
of
like
one-on-one,
telling
them
that
they
should
be
pinning
things
to
their
swag.
Now
people
are
using
slack
a
lot
more
I
mean
we
have
the
data,
that's
that
shows
it
I
see
the
slack
analytics
so
people
should
we
should
be
doing
more
than
we
can,
with
slack
so,
for
instance,
pinning
the
agenda
a
meeting
notes
to
the
slack
pinning
the
slack
guidelines
which
advocates
for
people
to
join
the
slack
admin
channel
and
then
important
links
from
the
mailing
list.