►
Description
Contribex: Mentoring Subproject Meeting for February 28, 2020
A
Welcome
everybody:
this
is
the
sink
contra
vex
mentoring,
sub
project
meeting
it
is
Friday
February
28th
I
am
Marky.
I
am
one
of
the
people
working
on
this
project.
We
have
a
lot
of
people
online
just
before
we
get
started.
I
want
to
let
everybody
know
that
we
do
have
a
code
of
conduct
which
amounts
to
just
to
be
nice
to
everyone.
I
am
going
to
lazy
link
the
doc
again
in
the
zoone
chat.
You'll,
see
a
section
for
February
28
mentoring.
A
A
D
A
A
E
Fit
all
I
mean
cuz
I
feel
like
the
the
thing
is
like
Nikita
and
you're
the
sub-project
owners
here
with
me,
and
so,
if
we
don't,
if
we're
not
here
like,
we
can't
approve
the
stuff
right,
so
I
think
that's
kind
of
where
all
this
scheduling
Fiasco
stuff
has
been
in
is
like
most
of
us
and
too
and
I.
Think
all
three
of
us
are
like
super
early
morning,
people
as
well,
so
we
might
want
to
just
revisit
the
old
doodle
or
the
last
doodle
and
pick
a
time.
That's
like
earlier
than
9:00
a.m.
yeah.
G
E
A
Do
it?
Okay,
so
I
will
take
the
risk.
I
will
get
that
Oh
figure
it
out
between
them.
I'll
get
it
I'll
meet
with
them
on
like
Monday
early
morning
their
time
and
to
see
what
would
be
a
good
time
and
then
I'll
get
something
out
to
the
community.
That
sort
of
goes
and
says:
hey
we're,
gonna
move
it
to
this
time,
so
we
can
make
it
more
EMEA
friendly.
A
E
Not
many
updates
other
than
cheese.
What's
next
month,
January
February
March
to
March,
so
yeah,
no
other
than
we're
ready
to
go
for
marches
edition,
still
have
yet
to
put
a
doodle
out
to
Kate
of
to
figure
out
either
a
new
time
or
a
second
time.
And
if
there
is
a
second
time
then
pick
a
new
host
and
I've
got
quite
a
few
people
that
have
said
that
depends
on
the
time,
but
they
would
help,
but
nothing
else,
still
grinding
the
gears.
A
E
E
So
if
we
want
to
definitely
do
the
next
one,
which
is
in
the
technically
winter
quote
quote,
we
should
definitely
figure
that
out
I've
got
the
marketing
team
helping
with
a
calendar
of
sort
of
events
and
alerts,
so
this
is
actually
going
to
be
one
of
them.
So
we'll
start
keeping
a
calendar
of
like
reminders
and
things
instead
of
like
on
our
own
personal
calendars,
so
that'll
be
better
I.
Think
for
the
project
as
well.
F
E
E
B
E
It's
not
hard,
it's
just
a
lot
of
back-and-forth.
It's
a
courtly,
a
typical
things
that
you
would
expect
from
a
coordinator
sort
of
like
you
know,
person,
somebody
being
a
clue.
You
know
making
sure
a
thing
goes
off:
yeah,
not
good
at
that,
especially
when
I
was
on
leave
so
yeah.
So
what
above
I
added
the
gallery
tee
site
there
Bob
it's,
we
can
talk
offline,
but
you
just
go.
E
And
then
you'll
start
getting
emails
from
sage
and
or
other
folks
at
outreach
e
that,
like
are
just
like
either
the
reminder,
emails
or
the
whatever
emails
about
the
program
and
then
what
we
do
is
we
just
make
sure
that
we
CC
everyone
when
we
talk
to
them
so
that
everybody's
on
the
same
page,
let's
see
what
else
about
out
Ricci,
that's
pretty
much.
It
I
think
for
our
Ricci
I
feel
like
as
long
as
we
have
the
contributor
site.
By
the
way.
E
This
is
something
I've
said
to
Bob,
but
I'll
say
to
an
other
mother,
nine
of
you,
eight
technically
so
I'm,
counting
myself.
Now
that
we
had
the
contributor
site
I
think
that
we
always
have
an
outreach,
II
project
I
feel
like
web
development.
Web
upkeep,
Web,
Design
stuff
like
that,
is
just
like
the
neverending
story
of
Internet
projects,
so
always
think
about
that.
Even
when
I'm,
not
here
and
stuff
like
that,
so
it's
just
one
example
of
a
thing:
that's
like
you
can
always
constantly
have
it's
all
I
got
for
outreach
me
all.
E
And
I
think
Tim
and
I
are
also
definitely
does
Tim
and
I,
say
Tim,
as
in
pepper,
I,
apologized
and
Tim
and
I
are
really
looking
for
folks
to
help
us
out
with
this
as
well.
We're
gonna
do
it
this
time,
but
for
future
we're
looking
for
coordinators
to
help
us
with
the
on-site
pod
mentoring
like
we
call
it
pod
kind
of
internally,
but
externally
we
call
it
like
with
mentoring,
where
three
people
pair
up
instead
of
two
one,
because
we
don't
usually
have
enough
mentors,
but
three
output,
two.
E
E
Sorry,
not
two
rooms
two
times,
but
the
one
time
is
a
very
odd
time,
but
it's
butted
up
against
some
other
talks,
so
we
either
might
reduce
it
to
one
for
Amsterdam
or
just
run
with
it,
we're
not
sure
yet,
but
we
are
going
full
steam
ahead.
For
sir,
damn
so
and
help-wanted
and
we'll
put
an
issue
together
too
for
a
help
on
a
tissue
for
coordinators
for
future
events,
make
that,
like
a
roll,
if
you
will.
A
Done
a
few
updates
I'm
still
working
on
a
couple
issues
to
get
with
mainly
the
I'm
starting
with
the
release
team
and
seeing
how
they
do
their
shadowing
process
and
see
how
we
can
sort
of
use
that
same
modeling
for
other
SIG's.
There
is
an
open
issue.
Unfortunately,
don't
have
it
right
at
the
top
of
my
head,
what
that
is,
but
it
is
on
the
mentoring,
step,
project
board,
cool.
E
E
E
B
E
Mean
it
is,
it
is
structured,
Josh
and
saying
like
it's
like.
They
have
check-in
points.
It's
structured
in
that
regard.
It's
not
structured
from
a
sense
of
the
release
team,
where
you
have
a
role
book
like
that
structured,
like
you,
have
a
role
you
have
job
duties
like
an
approver
generally
doesn't
have
like
a
role
other
than
moving
the
project
forward.
Saying
no
and
hoping
you
have
a
vision
like
I
can't
really
come
up
with
a
role
book
for
that.
E
So
we
tried
to
an
history
lesson
me
Phil
what
Rock
Ken,
Owens
and
quite
a
few
other
people
when
we
first
started
this
adventure
like
decided
to
do
a
it
extreme
see
it
can
actually
see
from
the
version
history
of
that
doc.
But
we
decided
to
do
a
extremely
structured
version
of
this
where,
like
they
had
training
sessions
every
week,
and
it
was
more
like
the
OpenStack
upstream
Institute
but
online,
and
it
was
so
over
engineered
and
extensive
that
we'd
never
got
anything
done
so
like
we
definitely
tried
I.
E
C
A
A
C
E
E
Right
me,
like
I,
I'm
thinking
like
a
readme
in
this
folder
or
something
along
those
lines
like
pro
in
the
program
section,
just
a
basic
readme
and
then
a
neat,
and
it
collects
all
the
links
from
like
the
past
and
cw's.
You
can
actually
like
maybe
see
the
growth
via
readme,
right
and
kind
of,
like
explains
at
a
very
high
level
what
it
is
what
the
goals
are.
Do
we
have
that
I?
F
E
We
do
I
feel
like
that
would
be
hella
awesome,
so
that's
kind
of
what
I
was
envisioning
there
for
like
on
the
readme
for
the
mentoring
cuz
like
I'm
thinking
once
we
get
like.
If
we
do,
you
know
eventually
call
this
from
you
know
from
a
contributor
site
perspective.
This
is
it's
like
a
canonical
link
of
everything
that
we've
got
from
a
processing
program
perspective
right
so
like
at
a
high
level
like
what
are
these
things
like
when
people
click
on
them
so
be
cool?
E
If
people
could
see
like
Oh,
what
is
the
new
contributor
workshop?
I
mean
it
might
not
link
them
immediately
to
you
know
the
newest,
but
maybe
on
the
readme,
then
the
new
contributor
workshop
lead
could
always
make
sure
that,
like
on
the
readme,
x'
and
stuff
that,
like
the
latest
reg
was
always
there
yeah.
E
D
E
D
B
I'm
Josh
burkas
I
worked
on
the
release
team
shadowing
program
for
a
long
time,
the
and
and
being
delighted
this
particular
release
cycle
with
not
being
involved
in
it
at
all,
which
is
what
I
call
a
victory
condition.
The
yeah
and
I
haven't
been
on
this
meeting
because
the
previous
timeslot
conflicted
with
a
standing
work
meeting
I.
C
H
A
E
I
I
E
Well,
this
is
the
human
aspect
to
that.
That's
for
sure
the
human
side
to
those
who
make
the
control
plane
as
I
say
thanks
for
joining
us.
My
name
is
Paris
I
used
to
code.
Chair
contributes
the
sig
for
about
two
years.
They
don't
do
that
anymore,
now,
I'm
just
a
helper,
B
and
I'm
on
the
steering
committee
and
do
some
things
with
CNC
F.
Now.
That's
me.
E
Have
one
more
thing
that
I
did
for
that:
I
added
a
added,
a
shadow
roll
page
to
the
programs
list
in
the
mentorian
folder
I
added
it
to
the
agenda.
This
is
just
a
PI.
It's
pretty
much
a
tombstone
slash,
please
holder,
slash
parking
lot
right
now.
The
idea
of
this
page
is
to
list
again
and
like
a
high-level
list,
a
hallway
all
of
the
shadow
roll
programs
that
we
have
within
the
project.
So,
for
instance,
we
have
the
API
review
team.
E
You
can
see
I
listed
them
all
in
one
big
line
like
ap
review,
contributor
summit,
triage
team
marketing
team,
sig,
Docs,
blog
team,
all
of
these
teams
that
have
reviews
that
have
role
books
and
it
would
be
cool
when
we're
talking
to
new
contributors
and
stuff
when
they
say
like
what
are
your
all
boarding
programs
like
these
are
nine
of
them
right.
This
is
like
what
I
always
told
me
when
people
are
cocoa,
Bernays
doesn't
have
any
onboarding
programs
like
it's
like
yeah.
E
We
actually
have
nine
of
them
at
least
so
we
just
don't
have
a
way
to
high-level
place
to
point
that
we
just
have
been
pointing
them
to
like
individual
things
like.
Oh
here's,
the
release
team
page,
here's
the
API
review
committee
page
that
kind
of
thing,
so
it
would
be
cool
just
to
like
list
them
all
and
things
like
that.
So
if
anybody
out
there
is
looking
for
PRS
things
or
want
to
partner
with
me
on
this
reach
out.
A
C
I
A
I
A
A
B
A
But
if
you
ever
have
a
question,
you
can
always
ask
us
in
the
sky,
the
Contra
Bex
slot
channel
and
if
you
don't
feel
comfortable
doing
that,
please
by
all
means
do
feel
free
to
ping
me
I.
Do
I
bet
you.
If
people
ask
in
the
country
Beck's
channel
because
there
may
be
somebody
that
has
the
exact
same
question,
is
you
so
don't
be
afraid
that
anybody's
gonna,
you
know,
say
something
or
you
know
we're
all
pretty
nice.
I
A
I
A
I
A
Not
only
in
the
country
backs
which
I
find
extremely
interesting,
I'm
also
part
of
the
release
team.
So
knowing
like
how
all
the
releases
come
together
and
as
Paris
was
dating,
there's
a
lot
of
roles
on
that
team.
So
you
have
the
ability
to
for
every
release
which
is
done
quarterly.
You
have
the
ability
to
shadow
on
the
team
and
be
a
part
of
it
and
then
hopefully,
maybe
become
a
lead
on
the
release
team.
A
B
Sometimes,
there's
already
something
that
you
have
an
interest
in
either
because
you
work
on
it
on
your
job
or
because
it's
something
that
you've
been
intensely
personally
interested
in,
so
sometimes
it's
better
to
start
from
a
different
area
like
if
you've
really
been
into
CEO
eyes.
You
know,
okay,.
I
B
C
The
community
repo
itself,
every
sig
has
ravine,
which
has
a
good
description
of
sort
of
what
they
do
want
areas
of
like
the
code
base.
Essentially
what
they're
responsible
these
are.
So
that
might
give
you
a
like
sort
of
little
TLDR
overview
and,
if
anything
beats
your
interest
start
attending
those
okay.