►
From YouTube: Working Group: 2022-11-09
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
Welcome
to
the
paquero
working
group
meeting,
I'm
glad
to
see
you
here
and
I'm,
really
sorry
about
any
confusion
that
this
lack
of
under
school
cost
seems
like
reminders.
Don't
don't
have
any
way
to
handle
them
some
changes,
so
I
will
recreate
him
and
I
will
have
to
do
the
same
on
March
or
whenever
we
enter
became
PST.
A
Okay.
Well,
let
me
show
you
my
screen.
Real
quick
here,
cool
yeah
feel
free
to
add
yourself
to
attendance
list,
including
your
affiliation.
A
Okay!
Is
there
anyone
who
would
like
to
take
notes
for
this
session.
A
Cool
yeah
new
faces
yeah
Philip,
I'm
glad
to
see
you
here,
I
think
we've
interacted
in
the
past
and
a
couple
of
places,
but
just
wanted
to
ask
you
to
briefly
introduce
yourself.
C
So
yes,
hi,
thank
you
I
guess
some
of
you
I
already
met
in
PR
reviews,
but
not
in
a
meeting
before
yeah,
so
I'm
working
in
the
team
of
Jan,
vanstein
I
think
he
always
joints
and
meetings
that
are
later
the
data
time
slot
so
also
working
for
sap
yeah.
We
know
yeah
interested
in
based.
A
Yeah,
thank
you
for
joining
dude.
It's
great
to
see
you
here
all
right.
Who
else
seems
like
forests.
We
like
to
introduce
himself
again,
but
if
that's
not
the
case,
I
will
move
you
to
the
net
in
this
list.
A
No
I'm
from
awesome,
okay,
cool
next
up,
I'm,
not
sure
if
there
is
any
RFC
non-drafted
this
week,
oh
yeah
there's
some.
There
are
some
of
them.
A
So,
let's
discuss
briefly
each
one
of
them:
careers
build
pack
RFC
mine
to
briefly
introduce
this
proposal.
D
Yeah
that
the
background
here
is
mostly
that
Kerberos
is
commonly
used,
Authentication
Protocol,
mostly
in
the.net
space,
although
it
is
not
uncommonly
used
in
other
places
like
in
Java.
D
D
Mostly
it's
installing
the
same
set
of
libraries.
You
would
get
if
you
did
like
app
get
krb5
user.
The
advantages
I.
Think
of
us
doing
this
in
a
build
pack,
is
we're
not
introducing
more
libraries
that
maybe
aren't
always
used
onto
the
base
stack
and
so
they're.
You
know
targeted
for
only
those
applications
that
really
do
mean
Kerberos.
A
D
Yeah
this
is
another
RC
for
me,
I
think
we've
talked
about
this
on
a
number
of
occasions
in
the
past.
D
D
The
main
issue
is
that
container
D,
the
way
it
invokes
some
command
deep
inside
of
its
internal
implementation,
is
to
have
some
number
of
layers
that
are
passed
as
arguments
to
a
command
and
the
shell
itself
or
whatever
it's
exacting,
I,
think
it's
some
system
call
has
a
limit
on
the
number
of
arguments
that
can
be
passed
to
it,
which
is
around
127
ish
I
individual
arguments,
so
the
stacks
themselves
take
up
depending
upon
how
the
stacks
implemented
take
up,
like
you
know,
four
or
five,
maybe
six
or
seven
layers.
D
D
This
kind
of,
like
monolithic,
stack
image
that
comes
out
the
other
side.
The
advantage
here
again
is
like
you've
improved.
You
know,
Headroom
for
the
builders
and
for
anyone
building
on
top
of
those
full
builders
that
might
be
running
into
issues
where
they're
hitting
the
layer
limit.
The
downside,
I
guess,
would
be
when
you
swap
out
a
stack,
you're,
replacing
more
bits
right,
all
those
packages
and
stuff
that
maybe
haven't
changed
on
top
of
the
base
image.
D
So
yeah,
that's
generally
the
concept
just
squash.
The
stacks
maybe
give
us
some
more
space,
there's
some
other
thoughts
around
squashing
layers
and
Builders
that
we
might
want
to
take
up
in
the
future,
but
I
figured.
This
was
a
reasonable
first
step.
E
Yeah,
this
is
just
a
small
edit
that
I
made
to
the
dependency
mapping
RFC
that
we
put
out
a
while
ago
when
we
introduced
a
new
checksum
field
to
our
build
pack
tunnels.
It
broke
service
Bindings
that
are
dependency
mappings,
that
people
can
provide
via
service
findings,
because
a
new
dependencies
that
use
that
in
checksum
field,
you're
required
to
pass
in
like
the
shaw
256
of
a
dependency
rather
than
a
Chuck
sum.
So
it
wasn't
working
well.
E
E
We
also
just
you
know,
added
a
note
that
we
have
moved
away
from
the
Legacy
CNB
dependency
mapping
or
service
binding
spec
in
favor
of
just
the
kubernetes
bindings
specification,
but
I
think
that's
been
I,
think
for
a
while
we
just
hadn't
written
it
down
anywhere,
but
I
think
this
also
already
has
two
steering
committee
approvals,
so
I
think
we're
good
to
probably
reach
this
head.
D
Yeah
we're
just
waiting
for
it
to
be
read
into
the
record
at
this
meeting.
I
feel
like
all
RFC
should
have
a
point
in
time
where
they're
they're
actually
brought
up
for
discussion
in
this
meeting,
but
yeah
I.
Think
after
this
we
can
go
ahead
and
merge
that.
A
A
A
So
next
up
any
Upstream
update
question
I'm,
not
aware
of
anything
from
last
week,
but
okay,
the.
D
I,
don't
know
if
this
got
discussed
last
week,
because
I
wasn't
here
and
I
haven't
had
time
to
watch
the
meeting,
but
there
is
a
new
version
of
the
life
cycle
that
supports
exchange,
stack
extension,
stuff,
I,
don't
know
if
anyone's
had
time
to
play
around
with
this
and
see
what
the
current
state
of
things
are,
but
yeah
it's
I
mean,
might
help
inform
some
of
the
discussion
related
to
the
Kerberos
built
back
just
a
better
understanding
of
what
extensions
look
like
in
addition
to
like
getting
some
insight
into
how
you
might
model
future
stack
definitions
using
extensions
rather
than
what
we
have
with
the
you
know,
a
tiny
base
and
full
stack
being
just
like
consecutively.
D
Larger
images.
D
E
I
have
a
quick
question
so,
on
the
RFC
related
to
Kerberos,
you
had
mentioned
that
we'd
be.
We
might
be
waiting
for
a
while
for
extension,
support
what
other
things
Upstream
besides.
The
life
cycle
need
to
change
to
get
support
for
that,
for
that,
like
I'm
kind
of
confused
about
how
I
would
test
this
out
without
having
the
rest
of
the
pieces.
D
So
I
think
that
Pac
has
some
like
minor
support
for
it,
but
I
don't
think
that
kpac
has
any
support
for
it
right
now.
Basically,
it's
like
when
they
implemented
it.
The
life
cycle
has
like
a
platform
definition
or
platform
API,
which
is
a
contract
between
a
platform
like
pack
or
kpac,
and
the
lifecycle
itself
and
I
think
the
pack
one
has
been
bumped
forward.
D
Although
I
really
have
to
look
and
see
what
the
state
of
that
looks
like,
whereas
the
kpac
one
I
don't
think
any
work
has
been
done
to
to
move
the
platform
API
forward.
D
Outside
of
that,
like
you,
can
the
life
cycle
itself
is
just
an
executable,
so
you
can
always
just
like
create
files
on
a
file
system
or
inside
of
a
Docker
image,
drop
the
life
cycle
into
it
and
like
invoke
the
life
cycle
against
files,
like
that's,
also
like
a
a
possible
way
to
to
interact
and
test
out
the
life
cycle.
E
A
Awesome,
thank
you,
Ryan,
okay,
next
up
in
Project
updates.
It's
that
time
of
the
month
again,
where
we
announce
the
contributor
of
the
month.
Remember
that
this
is
a
an
initiative
to
show
our
appreciation
for
individuals
providing
their
time
and
effort
in
many
different
ways
to
keep
improving
I
could
get
as
a
project.
A
So
we
we
have
a
set
of
candidates
and
the
maintainers
team
played
a
round
of
boats
and
for
this
time,
I'm
really
glad
to
confirm
that
it's
Philip
still
our
contributor
of
the
month
and
I'm,
really
glad
that
you
are
here.
This
wasn't
planned.
I
hope
this
is
a
surprise
for
you.
Yes.
A
Yeah,
that's
great
so
yeah.
Thank
you
for
all
your
contributions
and
yeah,
especially
the
dashboard
that
was
really
interesting
to
see
and
the
way
you
took
the
lead
to
make
it
happen.
So
thank
you
for
all.
You
and
your
team
are
doing
for
pecano.
C
Contributed
to
other
open
source
projects
before
where
it
was
a
lot
less
smooth.
So
just
it's
it's
fun
to
contribute
to
to
this
project
so
looking
forward
to
to
do
seller
contributions
and
yeah
I'm
honored.
Thank
you
and
it's
really
coincidence.
I.
No
one
informed
me
beforehand
worked.
A
A
That
sounds
I
mean
yeah.
Anything
we
may
do
to
help
you
better.
Just
let
us
know
and
yeah
I
will
send
you
details
for
you
to
order
swack
as
a
contributor
of
the
month.
So
congratulations
and
thank
you.
A
Cool
okay,
next
up,
yeah!
Well,
the
the
OSS
Health
assessment
is
something
we
do
every
six
months
in
average
to
again
measure
the
the
again
the
health
in
on
different
metrics,
the
health
of
this
community
in
general,
in
open
source.
We
try
to
not
focus
this
on
success
because
it's
a
very
limited
word.
A
We
focus
on
health
and
we
had
a
first
assessment
in
May
I
believe
the
plan
was
to
run
a
new
one
six
months
after
to
see
how
we
were
doing,
and
here
I'm
I
will
be
presenting
the
results
and
I
will
add
the
link
for
the
the
actual
slides
which
are
public
all
right.
So
we'll
try
to
go
over
as
quick
as
possible.
We
measure
six
yeah
six
domains.
A
A
It
has
to
do
with
maturity,
growth,
diversity
of
community
Etc,
so
in
summary,
what's
working
well,
I
think,
communication
channels,
different
communication
channels
available
the
the
fact
that
we
are
getting
more
and
more
organizations
contributing
to
the
project
organizations
besides
VMware,
that's
good,
it's
not
perfect.
None
of
this
is
done.
That's
the
whole
message.
None
of
this
is
done.
Everything
is,
is
subjective
to
be
improved,
but
it
certainly
it's
showing
a
positive
trend,
the
external
contributions
and
the
recognitions
to
contributors.
A
There
are
some
things
that
some
aspects
that
could
be
improved
by
by
a
lot
content
creation,
collaborative
content
creation,
I
mean
we
had
a
huge
effort
from
the
maintenance
team
to
create
content,
attend
kubecon
percent
sessions.
Etc
I
would
like
to
see
this
happening
in
collaboration
with
the
community,
so
we
can
really
scale
and
increase
the
reach
yeah.
Taking
the
word
about
potato
wheel,
packs
really
far
away
Again
release.
Note
completeness
is
ongoing
discussion,
but
it's
General,
something
with
that.
A
We
could
do
some
effort
to
improve
and
in
general
diversity
I
mean
that's
a
big
word
and
certainly
the
framework
we're
using
right.
Now.
It's
not
is
exactly
strong
on
the
diversity
front,
but
there
are
some
things
that
we
will
be
trying
to
improve
on
this.
A
Okay,
so
in
terms
of
project
maturity,
here
are
some
actions.
You
know
there
are
a
lot
of
metrics
and
the
link
is
there,
but
here's
just
some.
A
Outstanding
items
and
noteworthy
actions
that
we
could
take
to
improve
in
terms
of
the
metrics
on
Project
maturity.
We
already
discussed
this.
They
need
to
have
messaging
around
helper
care,
relates
to
This
Cloud
native
buildbacks.
There's
a
draft
blog
post
there
I
will
put
some
lines
on
it,
but
I
will
ask
you
all
to
please
contribute
to
it.
A
I'm
sure
you
all
have
way
more
context
than
myself
and
I
could
it
could
be
a
good
first
exercise
and
writing
something
along
with
the
community
there's
also,
a
all
of
the
actions
that
you
will
see
here
will
become
issues
or
are
already
issues
in
the
community
repo,
so
we
can
all
discuss
and
keep
track
of
it.
A
The
resources
section
to
the
website.
The
goal
is
to
curate
and
maintain
a
central
collection
of
all
the
content
that
exists
out
there
about
packet
of
wheel,
packs,
there's
yeah,
there's
content
out
there.
There
are
blog
posts,
so
I
I
stumbled
on
a
blog
post
a
couple
of
weeks
ago
that
I
I
didn't
know
it
existed.
A
Someone
created
that
and
how
to
use
potato
wheel,
packs
and
the
the
goal
is
to
maintain
a
central
place
where
all
these
resources
are
available,
the
style
guide
for
docs,
it's
something
that
we
should
revisit,
probably
take
some
already
existing
style
guides
and
adapt
them
to
the
to
our
needs.
A
But
the
discussion
is
right
there
and
Within,
adding
adapter
organizations
through
to
the
list,
taking
into
account
the
trend
so
far,
it's
safe
to
put
a
goal
on
adding
two
adopters
per
month
and
that's
totally
reasonable.
So
we
will
I
will
put
more
emphasis
on
on
this,
because
we
learn
a
lot
from
from
adopters
and
yeah
in
terms
of
content.
The
the
survey
that
we
run
recently
showed
the
need
for
and
some
other
research
that
I
found
on
how
developers
tend
to
learn.
A
First
thing
is
recorder:
tutorials
video
tutorials
or
code
walkthroughs.
So
that's
something
that
will
be.
We
will
be
working
on
this
and
probably
going
to
meetups
and
kind
of
replicate
content.
It's
the
reality
is
what
most
people
do
take
an
already
existing
content
presentation
session
in
adapted
to
a
specific
Meetup
or
community
and
keep
going
so
yeah.
That's
part
of
the
the
action
here
on
content,
any
questions
so
far.
A
All
right,
yeah,
another
goal
was
the
open,
SF
best
practices
batch
that
we
already
achieved.
Thank
you
all
Team
for
making
it
happen.
That's
for
passing
grade,
that's
the
Baseline
and
that's
it
next
level
will
be
aiming
for
silver.
A
Let
me
show
you
briefly
what
silver
level
requires,
and
if
we
see
here
our
our
profile,
we
have
yeah
100
of
the
requirements
passing,
but
if
I
take
a
look
at
Silver
we're
far
away,
there
are
some
things
that
are,
quite
you
know
evident
obvious,
but
there
are
some
aspects
on
security,
quality
and
Etc
that
probably
the
project
already
has.
We
could
visit
this.
We
could
review
this
to
see
if
how
how
far
the
project
will
be
in
terms
of
reaching
silver
level.
A
But
the
first
question
will
be:
do
we
want
to
work
towards
this
I
mean
it
doesn't
have
any
practical,
direct
benefit
or
implication,
but
the
the
the
resulting
quality
and
journal
the
metrics
here
for
the
project
will
be
interesting
to
achieve
for
a
higher
level,
so
yeah.
Another
discussion
that
we
could
have.
A
Cool
all
right,
regular
release.
Cadence
was
another
metric,
but.
B
A
I
believe
the
consensus
so
far
is
that
it
doesn't
apply
because
the
nature
of
the
artifacts,
the
project
really
is
having
a
regular
release.
Cadence
alongside
all
the
build
packs,
is
just
not
visible.
A
Map
quality
we're
doing
fine
fat
visibility
is
regularly
updated.
So
why
why
we
are
yellow,
because
there
are
some
things
we
need
to
work
on,
especially
on
the
content
side,
documentation,
it's
never
done.
It's
never
done.
According
to
the
survey
the
the
overall
consensus.
Let's
say
that
documentations
are
that
do
a
really
good
job,
but
probably
more
indication
how
to
troubleshoot
a
common
problems
will
be
useful,
I,
don't
know
if
Philip,
you
would
like
to
comment
something
around
this.
C
A
Got
it
so
yeah
growth
of
community?
We
recently
completed
a
small
change
to
the
governance,
doc,
updating
role,
definitions,
basically,
removing
the
member
role
that
was
between
everyone
and
contributor
was
a
member
role,
not
clearly
defined,
so
it
was
removed,
and
everyone
finally
has
a
name.
It's
Community
participant
and
it
finally
has
a
responsibility
to
follow
the
cloud
fundry
Foundation
card
of
conduct.
A
Everything
else
is
is
the
same,
so
the
goal
is
to
have
a
more
straightforward
path.
Maintainership,
the
remaining
issues
to
see
how
steering
committee
membership
could
be
handling
in
terms
of
how
to
elect
candidates
from
different
organizations.
A
It
it's
on
the
scope,
For,
an
upcoming
discussion
and
we
will
need
to
visit
this
continually.
Importing
new
controllers
is
one
of
the
metrics
and
the
growth
of
community
domain,
and
the
good
thing
is
that,
according
to
insights
from
Linux
Foundation,
we've
been
doing
that
or
the
project
has
been
doing
a
really
good
job
on
our
onboarding
new
contributors.
A
These
are
new
contributors
from
every
month,
as
especially
on
Affiliated
contributors.
What
it
means
an
Affiliated,
basically
using
individuals
accounts
in
the
individual
accounts,
individual
GitHub
account,
but
it
shows
a
constant
base
of
new
contributors
every
month,
which
is
fine
and
so
far
the
the
churn
the
contributor
the
contributor
shown
is
pretty
low.
A
So,
according
to
the
data,
every
time
someone
starts
contributing
keeps
contributing,
at
least
for
the
past
six
months.
A
That's
good
and
the
impact
it's
interesting,
because
this
is
the
impact
measured
in
terms
of
commits
by
new
contributors
since
six
months
ago,
till
now,
and
compared
to
the
total
number
of
comets,
the
contributions
by
the
India
contributors
are
pretty
relevant
for
the
project.
So
again,
thank
you
all
for
making
it
happen.
A
It's
a
huge
impact.
I
mean
12.
000
percent
growth
on
the
impact
measured
in
terms
of
comets
I
mean
there.
There's
no
other
straightforward
way
to
measure
this
because
I'm
aware
that
not
all
the
contributions
are
commits,
but
only
measuring
by
commits
the
impact
is
huge.
A
All
right
so
distribution
of
work
even
right
now,
it's
mainly
maintainer
driven
if
we
see,
for
example,
again
measuring
in
terms
of
comets,
the
amount
of
external
contributor
PRS
versus
the
total
number
of
PRS
and
commits
is
about
14
14
of
the
code.
Work
right
now
is
being
done
by
external
contributors,
so
86
by
maintainers.
A
It's
not
exactly
something
that
is
negative.
It's
just
the
nature,
probably
of
the
project
of
How
It's
organized,
but
it
it
could
grow.
I
mean
there,
there's
no
clear
goals
on
this
percentages,
but
I
will
discuss
her
briefly
about
this
later
on
decisions.
A
This
is
great
that
the
roadmap
was
discussed
with
the
community
and
but
with
the
implementation.
The
priorities
from
the
implementation
are
still
pretty
much
centralized
again.
This
is
not
negative.
There
are
some
metrics
that
result
from
the
or
some
patterns
that
result
from
the
nature
of
the
project,
but
the
good
thing
is
that
the
the
team
is
doing
every
effort
to
make
the
roadmap
open
transparent,
which
is
great,
and
it's
not
common.
A
These
days,
all
right
communication
channels,
some
metrics
on
slack
and
it's
good-
that
we
have
the
kind
of
slack
membership
that
allows
us
to
have
metrics
analytics
without
having
to
use
external
software.
A
So
we've
had
from
the
past
six
months,
21
growth
in
number
of
members
and
there's
this
interesting
metric
that
is
called
daily,
active
users
all
over
monthly
active
users.
A
A
The
reality
is
that
most
communities
don't
go
beyond
20,
so
we
are
closer
to
the
ideal.
But
again
the
goal
is
is
to
try
to
increase
the
level
of
engagement
on
slack
to
30
percent
and
on
the
mailing
list
front.
We've
been
duplicating
the
number
of
members
since
the
mailing
list
was
rebooted
because
it
already
existed.
A
Nope
cool
in
diversity
of
a
community
I
mean
the
number
of
contributors
is,
is
awesome,
I
mean
in
the
face
of
everything,
that's
happening
in
the
world
right
now
we
tend
to
see
negative
negative,
negative
Trends
and
contributors.
That's
true
even
for
huge
projects
like
kubernetes
and
these
Graphics
tend
to
decrease
the
number
of
contusions.
A
But
here
we
are
seeing
a
spike,
a
positive
trend
on
growth
on
the
number
of
contributors.
There's
there
is
total
contributors,
regardless
of
affiliation,
and
especially
since
July
there's
been
a
higher
rate
of
growth
and
yeah.
That's
that's
interesting
and,
as
I
said
it's,
it
goes
along
with
the
with
a
pretty
low
churn,
almost
zero
churn,
which
is
pretty
interesting.
A
All
right
in
terms
of
organizations
well,
this
is
the
reason
this
is
yellow,
not
green,
because
a
big
amount
of
the
contributions
come
from
VMware
and
unknown.
Typically
is
individual
personal
GitHub
accounts
that
could
not
be
tied
to
any
course
company.
But
after
that,
it's
sap.
A
Non-Vmware
contributor
is
sap,
so
in
the
past
six
months.
So
thank
you
again,
IBM.
Thank
you
all
Bloomberg
systematic
doxibility
and
individual
right.
So
as
I
say,
this
is
not
done
and
the
game,
even
when
we
have
a
positive
trend
on
mostly
all
the
metrics.
It's
not
that
because
we
need
to
work
in
increasing
diversity
of
organizations,
contributing
non-code
contributions.
A
Of
course
they
work
from
the
team
itself
and
some
external
contributions
in
terms
of
content,
which
is
great,
and
probably
you
will
need
to
add
a
plan
to
this,
to
make
it
more
consistent
and
to
distribute
the
the
work
of
the
community
outreach
and
and
and
leveraging
the
community
again
recognition
of
contributors.
A
The
goal
of
this
initiative
is
to
make
it
consistent,
I'm
aware
that
it's
not
a
program,
it's
more
an
idea
and
it
could
be
way
better
way,
more
sophisticated
the
contributor
of
the
month,
but
it's
a
first
attempt
to
show
appreciation
and
probably
in
the
future,
we
will
be
evolving
this
into
something
you
know
with
a
broader
reach
or
more
inclusive
Etc.
A
There
is
a
first
step
to
make
it
at
least
more
consistent,
yeah
release.
Note
completeness:
there's
a
discussion
on
going
for
this
discussion:
okay
and
finally,
user
Community,
engagement,
user
training,
material.
A
Probably
again,
according
to
the
survey
we're
missing
tutorials
in
how
to
kind
of
content,
we
have
a
pretty
good
getting
started
guide,
but
some
other
forms
of
content
and
for
for
the
more
common
questions
will
be
really
useful,
we'll
be
working
on
this
and
yeah
one
of
the
metrics
is
there
should
be
an
obvious
process
for
bug,
reports
and
feature
requests.
Where
obvious.
A
This
is
a
big
word,
but
I'm,
not
sure
if
it's
obvious,
but
from
from
the
First
Health
assessment
to
today,
we
have
a
much
better
template
for
new
issues
that
include
feature
requests,
bug,
reports
and
other
kind
of
requests
right:
okay,
A
bit
of
an
action
plan.
Again,
all
this
will
become
issues
or
or
some
of
them
are
already
issues.
So
we
can
all
have
visibility,
increase
the
number
of
help
wanted
or
good
for
good.
First
issue
labels:
it's
also
on
another
Avenue
to
get
contributions.
A
The
resources,
page
content
planning,
including
community
members
as
I,
said
and
Define
the
process
criteria,
tools
to
eventually
enable
stream
committee
membership
and
some
Explorations
that
I
will
be
completing
so,
for
example,
how
to
automate
this
health
assessment.
So
we
can
find
early
if
there
is
a
metric
that
is
not
performing
well
work
upstream
and
when
I
refer,
Upstream
I
refer
to,
for
example,
the
chaos
project
double
s.
A
They
maintain
a
really
good
set
of
metrics
for
open
source
projects,
including
diversity
goals,
metrics,
something
that
we
could
Define
that
could
be
attainable
and
relevant
to
this
community.
In
terms
of
diversity,
explore
and
mentorship
program.
We
I
mean
the
the
one
of
the
reasons:
I
see
more
and
more
contributions.
External
contributions
is
the
willingness
from
the
maintenance
team
to
help
to
Mentor
new
contributors.
A
That's
awesome,
so
my
next
step
will
be
how
to
make
it
more
consistent
how
to
turn
into
a
program
or
an
initiative
or
a
process
to
get
mentorship
and
also
I'll,
be
exploring
some
tools
to
gain
more
insights
on
our
users,
our
community,
what
they
need
and
what
we
could
do
to
serve
them
better.
That's
why
I
call
this
growth
with
data.
A
So
a
final
word,
thank
you,
I
mean
the
the
main
reason
this
is
working
so
far
in
some
of
the
metrics
is
the
commitment
from
the
awesome
team
of
maintainers
your
willingness
to
provide
quick
responses
to
questions
to
go
above
and
beyond
your
duties.
Thank
you.
Thank
you
to
every
Community
member
for
your
time
for
every
suggestion.
Issue
review,
comment:
PR,
meeting
attendance,
Etc.
Thank
you
all
all
right.
Any
question.
Any
comment.
A
A
A
B
A
C
So
I
think
this
one
basically
answered
itself
and
in
the
presentation
right,
so
the
the
member
is
no
longer
a
thing,
so
that
has
been
squashed
with
with
everyone
wrote
right
step
is
then
to
contribute
directly
right
right,
yeah.
A
C
Just
saw
this
commit
that
updated
this
yeah
just
mark
down
here,
yeah,
that's
exactly
this
one
I'm
just
trying.
A
Yeah
the
wall
was
to
remove
intermediate
steps
like
member
role
and
move
from
Community
participant
to
contributor,
where
the
process
is
described
here
can
be
self-nominated
or
nominated
by
contributors
and
must
be
elected
by
super
majority.
Of
that
project's
maintainers
I
believe
in
your
case
will
be
tooling
stacks
and
notes.
A
C
D
Yeah,
the
foreign
there
are
a
bunch
of
internal
sub
teams
that
are
maintained
for
like
controlling
access
and
specifying
code
ownership
for,
like
all
of
the
repos
and
all
the
maintainership
teams.
Those
things
have
attached
to
them,
like
a
forum
for
discussion
and
not
for
like
project
or
like
team,
but
contributor
and
maintainership
votes
are
held.
D
I,
don't
think
you
can
see
that
unless
you're
like
a
technical
member
of
the
GitHub
organization,
yes,
which
is
fine
the
path
for
like
contributorship,
if
you
want
to
like
self-nominate
yourself,
I
would
suggest
you
like
just
reach
out
to
like
me
or
another
steering
committee
member
or
the
maintainers
of
the
project
and
like
put
your
name
forward
to
say,
I'd
like
to
like
put,
you
know,
nominate
myself
to
be
a
contributor
at
which
point
that
person
can
like
proxy
the
vote
into
that
forum,
and
then
the
vote
can
be
held
and
we
can
like
tell
you
of
the
outcome.
D
I
think
that's
like
the
easiest
way
to
get
this
done,
just
ping
people
on
Slack,
but
then
once
you're
inside
then
you
can
like
see
that
happening,
and
you
know
if
you're
a
maintainer.
You
can
participate
in
the
voting
as
well.
A
All
right
does
that
answer
you,
your
question,
Philip.