►
From YouTube: SIG Contributor Experience: Weekly Update 20200909
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
Okay
welcome
everyone
today
is
september
9th,
and
this
is
the
weekly
sig
contributor
experience
meeting.
I
am
your
host
bob
killen
one
of
the
co-chairs,
just
as
a
general
reminder
that
this
meeting
is
under
the
cncf
code
of
conduct,
which
essentially
boils
down
to
please
be
excellent
to
each
other.
B
Sure
I'm
george
castro,
I
work
at
vmware,
I'm
a
community
manager
and
I'm
in
ann
arbor
michigan
welcome
everyone,
those
of
you
that
are
new.
A
That's
a
great
temperature,
though,
does
anyone
else
want
to
introduce
themselves.
C
Sure
I'm
josh
I'm
a
co-founder
and
cto
at
orbit
where
we
make
tools
for
people
who
build
communities.
D
And
nikola
did
you
introduce
yourself
right
very
quickly
at
the
beginning,
but
I
don't
think
everybody
was
here
already
so
hi
everyone,
I'm
nicolas
and
I'm
a
software
engineer
here
at
orbit
so
pleased
to
meet
y'all.
C
Welcome
we're
in
paris
not
not
michigan,
although
I'm
from
chicago.
I
know
I'm
excited
living
here.
A
Okay,
would
anyone
else
like
to
introduce
themselves
if
not
we
can
get
on
with
sort
of
our
normal
recurring.
A
Okay,
we'll
try
and
get
through
our
normal
like
stand
up
quick
and
then
you
know,
you'll
have
the
the
floor
from
orbit.
A
Okay
with
that
events,
office
hours.
B
Planning
will
start
on
friday,
so
I
have
one
new
panelist
and
she's
gonna
help
join
us.
I'm
gonna
try
to
revitalize
the
west
coast
edition,
but
we'll
see
how
people
respond
europe.
The
european
session
is
fine.
B
You
were
going
to
say
community
meeting
planning
is
in
progress.
I
synced
up
with
him
yesterday
he's
he's
doing
a
good
job,
so.
A
Okay,
next
one
is
contributor
summits.
That's
me
no
real
updates.
Yet
honestly,
this
is
still
on
like
us
to
send
out
the
survey.
If
we
want
to
do
something
steering
committee
election
updates,
ihor
you're
on
the
line,
would
you
mind
giving
an
update.
E
Yeah,
but
actually
I
haven't,
checked
the
current
current
states,
yet
we
have
a
couple
of
candidates
as
far
as
remember.
Almost
all
candidates
have
submitted
their
videos
to
the
community
ripple,
so
we
are
almost
at
the
final
stage
for
the
elections
this
year.
Please
please
check.
Please
check
github
at
the
elections,
intellectual
directions
director
within
the
coming
trip
for
more
details.
A
Okay,
cool
any
other,
I
don't
think
there's
any
other
events
updates.
So
with
that,
should
we
just
kick
on
over
to
let's
get
going
over
to
mentoring
and
meet
our
contributors?
A
I
don't
think
paris
is
on
the
line
nope.
As
far
as
I
know,
it's
still
punted
to
you
like
there's
nothing
this
month
and
it's
going
to
be
punted
till
next
month.
A
The
other
thing
that
has
been
like
we've
routinely
had
this
is
moving
on
the
next
item,
the
mentoring
meetings
and
being
rescheduled.
We've
routinely
had
problems
getting
people
to
attend
the
various
time
slots
that
we've
tried.
A
A
E
Yep
good
news
about
google,
some
of
the
code
is
just
completed
this
monday
and
cncf
had
17
successful
students
this
year
who
have
completed
the
program.
I
don't
recall
the
exact
number
of
kubernetes
only
students,
but
we
had
a
good
number
of
them.
However,
again
17
17
students
is
is
a
pretty
good
number
and
we're
probably
one
of
the
biggest
google
server
code
organizations
this
year
with
this
number
of
students
the
next.
The
next
one
is
about
community
bridge
wells,
making
program
progress
with
this
one.
E
E
So,
if
you're
interested
in
mentoring,
if
you
have
any
ideas
which
kind
of
project
would
you
like
to
mention,
if
you
have
any
project
ideas
that
you
would
like
the
mentees
to
implement
for
you?
So
please
read
the
announcement
and
all
the
information
that
I
sent
out
last
week
to
kubernetes
def
mail
at
least
put
the
link
to
the
meeting
notes
and
follow
the
procedure.
E
Yes,
it
was,
we
had
two
submissions
from
kubernetes
project
and
one
of
them
is
about
what
you
fight
for.
A
Okay,
does
anyone
else
have
any
mentoring
topics
they
want
to
talk
about
or
sorry
like
you.
I
think
I
interrupted
you.
E
A
Okay,
and
that
takes
us
to
community
management,
we
have
a
couple
items
on
the
need
to
know
chairs
email.
Is
there
any
other?
I
think
it's
mostly
about
like
zoom
the
launch
of
kates.dev
and
then
potentially
putting
let
me
pop
it
open.
A
Yep
election
news
volunteers
for
new
contributor
workshop
does
anyone
else
have
any
other
suggestions
for
the
need
to
know
email.
A
Okay,
next,
a
pack
corner
update,
doesn't
look,
there's
any
update.
Next
big
thing
is
zoom
for
those
that
might
not
have
been
at
the
last
meeting
or
heard
the
news
we
essentially
have
to
roll
out
either
a
pass
like
a
pass
key
to
every
zoom
meeting
by
september
27th.
A
The
alternative
is
that
the
waiting
room
is
enabled,
but
that
won't
work
well
for
a
lot
of
our
chairs
and
teals
or
other
people
are
leading
meetings,
because
they'll
have
to
share
some
credits
around
right.
Now
we
just
want
to
go.
Since
our
current
practices
worked.
Fine,
we
want
to
just
essentially
use
a
universal
key.
If
anyone
has
any
suggestions,
I
tossed
a
couple
in
there
like
five
sevens.
A
Maybe
it
should
be
seven
sevens
or
you
know
everyone's
favorite
luggage
code,
one
two,
three,
four:
five:
if
anyone
has
any
other
suggestions,
please
toss
it
in
there
and
we
can
send
something
out
to
the
list
or
honestly
just
start
going
with
it.
A
Okay,
devstats
laurie.
B
F
F
F
A
College
we
might
be
able
to
like
honestly
ping
folks
and
sick
docs,
since
they
have
significantly
more
experience
with
this.
Celeste
would
actually
probably
be
a
great
person.
F
F
F
Then
the
next
action
item
is
getting
the
shares
and
leads
persona
going
and
the
link,
dev
stats
link
will
show
you
what
I'm
talking
about
when
I,
when
I'm
referring
to
user
persona,
if
you're
new,
so
we
basically
have
a
number
of
personas
who
would
be
the
users
for
the
for
consuming
dev
stats,
like
information
so
chairs
and
leads,
is
one
and
george,
and
I
have
talked
about
chatting
tomorrow,
he's
having
a
busy
wednesday
does
anybody
else
want
to
join.
A
A
Okay,
I
I
know
a
couple
other
people
that
might
want
to
join.
Okay,
I
just
need
to
ping
them.
Most
of
them
are
on
the
west
coast,
though
that's
the
only
caveat,
okay
but
yeah
I
can.
I
can
reach
out
to
them
and
ping
back
with
that.
F
So
if
we,
if
we're
thinking
of
chairs
and
leads
to
get
that
input
from,
I
don't
think
they
need
to
come
to
the
meeting
or
it
would
just
be
like
asking
them
what
what
data
they
would
like.
The
purpose
of
this
meeting
would
be
more
to
package
that
user
persona,
like
we've,
tried
to
do
with
the
program
manager
role,
and
then
you
know,
when
do
we
call
it
done
and
and
how
would
our
outreach
process
run?
F
G
G
F
That'd
be
great,
I
think
what
we
would
need
to
do
to
help
you
is
to
just
have
some
messaging
prepared,
so
I
will
prepare
that
and
share
it
with
the
two
of
you,
george
and
ewan,
and
we
can
blast
that
out.
F
Okay
messaging
for
outreach
to
chairs
and
these
and
as
far
as
the
other
personas,
I
don't.
I
guess
paris
isn't
on
the
call
today,
but
she
was
willing
to
take
on
the
steering
committee
persona.
F
And
then
we
need
a
contributor
persona
driver,
we
had
one
person,
but
they
seem
to
be
rather
busy.
So
if
there's,
if
they
surface
again,
then
having
two
folks
work
on,
this
is
not
a
bad
thing,
but
does
anybody
here
want
to
actually
drive
the
contributor
persona
and
basically,
what
this
would
be?
Is
I'm
a
contributor
to
kubernetes?
I
would
like
to
know
how
my
sig
is
performing,
how
I'm
performing
in
relation
to
other
contributors.
F
C
I'd
be
happy
to
I,
I
will
need
to
catch
up
on
contacts,
but
I'm
really
in
that
area
and
I'd
be
happy
to
happy
to
be
involved.
F
Oh,
that
would
be
great.
Let
me
get
you
on
here,
so
I
can
reach
out
to
you
afterwards
and
give
you
some
context.
C
No,
I
do
not
think
I
can
join
the
slack,
though
quite
happily,.
A
Yeah
yeah
george
is
pasting
the
link
or,
if,
like
that'll
honestly,
be
the
easiest
way
to
just
sort
of
get
communication
going.
C
There
it
is
okay,
great
yes,
and
just
for
the
the
record
yeah
we
have
nikola
is
I'm
the
josh
and
the
last
thing.
F
All
right,
thank
you
and
then
the
open
source
program
manager
persona,
if
you
click
that
link
you'll,
see
that
there's
quite
a
lot
of
text
there
now.
So
that
is
rather
well
shaped,
but
george
raised
the
issue
last
week,
he'd
like
to
add
small
companies
needs.
F
A
It's
been
a
while,
but
laura
might
be
a
a
good
person.
Okay,
she
hasn't
been
on
the
conductor's
calls
in
a
while,
so
I
don't
know
how
how
active
she
is.
Currently,
though,.
F
A
A
F
And
then,
finally,
we've
had
this
feature
request
for
graphs
for
all
contributors.
I
think
that
was
fulfilled
last
week
by
wukash
from
cncf.
F
Last
week
we
determined
that
it
partially
solves
the
issue
that
george
and
paris
had
been
described
in
weeks
past
about
how
to
quickly
obtain
data
around
contributors
inputs,
and
you
know,
are
they
contributing?
How
are
they
contributing
across
the
ecosystem
so
that
partially
solves
the
issue,
and
I
was
wondering
here
if
we
can
identify
what
else
is
needed.
What
is
missing
that
we
would
want
to
request
in
some
future
contexts
and
if
we
can't
answer
that
right
now,
it
can
just
until.
H
A
Does
anyone
have
any
devstats
questions.
H
I'm
curious:
is
there
a
persona
for
specific?
No,
I
seek
like
I'm
working
for
signals
and
we're
looking
at
number
of
pr's
active
number
of
prs
closed
in
a
week.
This
kind
of
statistics,
maybe
something
about
contributors,
would
be
also
interesting.
Is
there
such
persona
or.
H
F
Mean
that
you
have
to
be
a
chair
or
a
lead
to
look
at
the
data
point,
it's
just
most
aligned
with
the
things
that
your
role
is
looking
for,
but
anybody
in
a
sig
could
actually
do
that.
Go
and
look
at
the
graph
and
see
pr's
per
week.
Close,
I
think,
that's
that's
achievable
with
the
existing
dashboards.
It's
just,
maybe
not
super
fine
super
easy
to
find.
So
I'm
happy
to
help
you
find
that.
B
F
Why
don't
we?
Why
don't
we
have
that
conversation
in
contribute's
channel
so
that
the
both
of
us
can
support
yeah,
please
raise
that.
That's
great!
Thank
you
for
raising
us.
It's
really
great.
A
Awesome,
thank
you
and
that'll.
Take
us
to
marketing
is
someone
from
marketing
here
to
give
an
update.
A
I
personally
don't
have
any
updates
here
joel.
I
know
eric
is
on
vacation
this
week,
but
do
you
have
any
any
other
updates.
G
G
That
doesn't
mean,
of
course,
we're
you
know
ever
done
with
documentation,
so
you
know
keep
us
in
the
loop
if
there's
challenges
with
that,
should
that
be
absolutely
perfect
and
have
absolutely
no
changes
after
somebody
goes
through
it.
Well,
that's
that's
just
impossible,
there's
no
way!
So
please
don't
don't
be
shy
about
letting
us
know
about
what
teas
were
not
crossed.
Eyes
were
not
dotted
and
other
things
were
just
written
completely
incorrectly.
G
That's
documentation
for
you
yeah!
Then
we
did
a
blog
post
about
our
experience,
hopefully
to
kind
of
improve
I've.
I've
decided
to
quit
using
the
word
up
level
ever
but
to
improve
process
for
documentation
going
forward
and
kind
of
trying
to
keep
things
aligned
with
growth.
So
we
hope
that
we
can
kind
of
work
on
that.
A
That's
awesome,
yeah.
I
saw
the
pr
to
the
contributor
site
repo.
I
just
honestly
like
this
weekend.
I
tried
to
unplug
and
haven't
had
much
of
a
chance
to
actually
like
look
at
it.
Yet.
H
A
wonderful
contributor
side
there
is
a
desire
to
put
information
about
end-to-end
testing
in
contributor
side,
and
but
I
think
that
one
of
the
problem
is
the
complete
documentation
is
hard.
How
do
you
feel
about
incomplete
documentation?
How
do
you
feel
about
like
progress
and
like
to
do's
in
a
contributor
side?
Is
it
acceptable.
A
A
Okay,
does
that,
like
I
know
that
contains
at
least
some
of
the
end
to
end
testing
documentation?
Does
that
sort
of
cover
your
your
needs
or
is
there?
There
are
more
e
to
e
test
type
stuff
that
you're
you're
thinking
of
doing.
H
Yeah
there
are
documents
about
organized
organizing
and
e2
tests
by
categories
and
specifically
for
signal.
There
are
like
many
different
types
of
end-to-end
tests
and
unfortunately,
documentation
is
is
not
well
structured,
so
we
cannot
just
take
a
google
doc
and
like
port
it
to
kubernetes.df,
so
I
think
it
will
be
pro
like
it
will
be
step
by
step
process,
so
you'll
contribute
like
first
iteration,
then
you'll
work
on
that
and
polish
it.
G
Looked
in
the
last
few
few
days,
sergey,
I'm
not
sure
whether
you're,
what
you're
speaking
of
is
the
pull
request
that
we
just
merged.
Oh.
H
Okay,
let
me
take
a
question
yeah.
I
I
haven't
looked
this
week
yet:
okay.
A
And
where
are
we
where
the
documentation
likely
live
at
least
for
now
is
in
the
devil
directory
in
the
our
nk
community,
and
then
we
can
selectively
surface
documents
to
the
case.dev
website.
So
if
it's
not
like,
you
know,
get
it
out,
there
get
it
merged,
and
if
we
want
to,
we
can
then
surface
that
specific.
We
don't,
we
can
hold
off
on
surfacing
it
until
it's
actually
like
ready
to
go.
A
If
it's
like
you
know,
mostly
just
like
a
blank
document,
also
putting
a
little
bit
more
work.
Your
way
joel
but,
like
you
know,
joel
and
eric
are
great
when
it
comes
to
like
information
architecture
and
how
documents
should
be
laid
out.
So
if
you're
you're
looking
for
someone
to
like
try
and
or
help
potentially
organize
that
stuff,
they
might
be
a
great
person
to
poke
and
talk
to.
G
Yeah
yeah
hit
us
up.
Yeah,
have
a
look
and
see
if
what
we've
the
recent
work
covers,
the
stuff
you
need
and
if
not
reach
out
and
happy
to
help,
have
a
look
at
it
when
eric
gets
back
will
be
more
effective
but
but
I'm
glad
you're
looking
at
it
sergey
and
then,
if
and
if
the
stuff
we
did
is
in
line
with
what
you're
looking
for
test
it
for
us.
A
A
No
okay,
we'll
just
we'll
move
right
along
to
slack
infra,
quick
update.
Some
folks
might
have
seen
it,
but
the
announcement
bot
is
live.
This
is
a
bot
for
our
contributor
comms
group
that
can
essentially
send
a
message
to
one
or
more
channels,
so
you
can
just
like
broadcast
stuff
out.
C
All
right,
great
ivor,
I
can
give
a
bit
of
an
introduction,
but
I'm
wondering
also,
if
just
from
your
side,
you
want
to
say
a
few
a
few
words
maybe
to
set
the
context
for
what
we're
going
to
share.
E
Sure
so,
I'd
like
to
remind
the
current
group
of
people
that
contributor
experience
that
the
first
presentation
about
orbit
we've
made
a
presentation
from
cncf
made
at
the
end
of
july,
and
we
made
a
representation
about
the
tools
and
possibilities
that
orbit
as
a
community
tracking
tool
can
offer.
However,
we've
decided
that
since
we
were
close
to
keep
going
and
we
had
different
priorities
within
the
community,
more
different
urgent
priorities,
so
we
decided
to
keep
this
conversation
open
and
to
continue
discussing
it
after
kubecon,
probably
later
restored
september.
E
So
we
had
a
few
conversations
at
cncf
with
with
the
orbit
team
and
what?
What
are
the
benefits
of
the
tool
to
this
community
and
what
can
they
offer?
So
I'm
happy
to
invite
to
the
right
folks
from
from
over
here.
So
nicolas
john.
So
please
please
go
ahead
and
provide
your
inputs
on
this
one.
C
Sure
yeah
thanks
so
by
way
of
some
context
or
orbit
where
we're
a
company.
I
met
chris
at
fosdem
this
year
and
that's
how
the
conversation
started.
He
saw
what
we
were
building
and
said:
oh,
maybe
that's
something
we
could
actually
use
in
the
cncf
or
for
kubernetes.
In
particular,
we
come
from
we're
software
engineers.
C
I
know
there's
an
amazing
amount
of
data
in
there
we'll
give
you
we'll
show
you
a
demo
and
you'll
see.
We
have
some
reports,
but
you.
C
To
learn
how
a
project
like
kubernetes
is
handling
the
contributor
experience,
that's
very
near
and
dear
to
our
heart.
We
hope
that
people
use
orbit
to
provide
a
better
contributor
experience
and
to
spend
less
time
like
tracking
down
all
the
little
bits
of
information
needed
to
do
that
and
more
time,
just
interacting
with
people
and
building
the
relationships
so
with
without
further
ado
I'll
see.
If
we
can
share
a
screen,
maybe
nikola
will
help
me
here.
A
A
C
Okay,
great
everyone
can
can
see
that
everything
you're
seeing
here
is
test
data
for
a
fake
database
called
dynobase.
I
hope
there's
not
a
real
database,
but
everything
in
orbit
fits
into
a
workspace.
So
what
we're
looking
at
right
here
is
a
workspace
that
contains
members
and
activities,
so
one
of
the
the
things
that
orbit
does
like
a
crm
for
your
community
members,
but
without
the
sales
of
the
sales
aspect
just
a
place
to
bring
bringing
members
and
their
profiles
into
one
place.
C
We
have
tags
that
we
can
apply
to
them
if
we
click
on
a
community
member
here,
this
is
casey
generated
with
our
test
data.
We
can
see
a
couple
of
things
on
their
profile.
This
line
right
here
is
called
the
love.
Love
is
an
engagement
score
that
comes
from
something
called
the
orbit
model,
which
is
the
open
source
model
that
we
build,
that
we're
building
the
product
on
top
of
so
I
can
share
a
link
later
to
our
github
repository.
C
That
is
a
readme
file
that
talks
all
about
the
orbit
model
and
that's
like
a
philosophy
for
community
building
and
also
a
set
of
ways
to
measure
engagement.
So
in
casey's
case
here
we
can
see.
Oh
there's
a
little
bit
of
engagement
in
march.
It
looks
like
it's
picked
up
throughout
the
the
months
and
every
member
we
can
see
the
trend
so
that
that
becomes
very
useful.
If
you
want
to
see
or.
C
Have
been
very
active
recently
or
in
the
past
in
the
middle
here
we
see
the
timeline
of
what
casey
has
done,
and
this
can
go
across
different
systems.
Here
we
see
some,
we
have
a
github
integration
that
pulls
in
poll,
requests
issues,
issue
comments
and
creates
activities
for
those,
and
then
we
also
have
a
twitter
integration
on
the
way
discourse
discord
slack,
and
we
also
have
an
api
so
that,
even
if
we.
H
C
Have
an
integration,
yet
that's
still
something
where
it
can
be
sent
in,
so
that
that's
a
view
looking
at
one
member
and
I
can
also
jump
to
the
activities
tab
where
I
can
see
everything
about
the
the
aggregate
number
of
things
the
aggregate
list
of
things
people
are
doing
in
the
community.
So
we
have
some
really
quirky
test
data.
That's
coming
here,
but
examples
are
things
like
watching.
A
twitch
live
coding.
C
Stream
orbit
has
some
users
that
do
a
lot
of
live
streaming
on
twitch
and
they
use
orbit
to
to
track
who's
coming
and
watching
my
live
streams.
C
It's
basically
just
a
list
of
community
members,
the
things
that
they're
doing
and
on
the
reporting
side,
I
can
go
repository
by
repository
or
look
at
the
whole
community
and
see
who
what's
the
number
of
members
that
I
have.
How
is
that
changing
over
time?
What
are
the
members
that
I
have
in
different
orbit
levels?
C
We
we
have
four,
we
call
them
ambassadors,
users,
fans
and
observers,
and
these
are
concentric
circles
of
activity
around
projects,
maps
pretty
well
to
things
like
a
core
team,
maintainers
and
users,
and
we
can
also
look
at
the
activity
that
might
be
specifically
on
github
or
on
twitter
and
again,
if
I'm
happy
to
give
a
demo
in
the
future
too.
That
shows
more
data.
I
think
in
this
test
workspace
we
just
have
75
or
80
members,
but
we
have.
C
We
have
communities
that
are
in
orbit
that
are
in
the
tens
of
thousands
of
members
of
track,
and
the
last
thing
I'll
show.
You
is
a
feature
that
we
have
called
actions
that
we're
just
working
on
now,
where
based
on
a
milestone
that
a
contributor
can
have.
This
really
gets
directly
to
contributor
experience
like
case
carry
here,
merging
their
first
full
request.
C
C
Agreement
could
be
following
on
twitter
or
just
sending
a
personal
message
if
they
have
an
email
registered,
and
that
way
it
just
saves
a
little
bit
of
time
from
having
to
remember
or
track
down
who
had
it,
who
had
a
first
pull
request
or
who
had
their
tenth
or
who
had
their
hundredth
contribution
can
set
it
up.
So
those
those
are
important.
Events.
D
A
Please
go
ahead
first,
big
question
for
me
is
so
how
do
you
actually
build
this
profile.
C
It's
built
through
integrations
and
it
can
also
be,
and
it
can
also
be
edited
or
added
to
manually.
So
if
I
want
to
go
here
for
juliana,
then
I
can
can
do
that,
but
the
most
of
the
the
members
are
built
through
the
github
or
the
twitter
integration.
C
It's
a
github,
org
level,
plugin,
it's
a
github,
app
that
installs
right
at
the
organization
level
and
then,
depending
on
the
repositories
that
are
selected,
it
will
start
some
notes
historically
and
also
going
forward.
We.
A
Then,
like
I
know,
I,
like
I
looked
briefly
like
this:
the
slack
integration,
some
of
the
other
things.
How
were
you
integrating
that.
C
Yeah
we
can
have
multiple
github
orgs
per
workspace
that
that's
no
problem,
so
the
the
activities
and
the
members
that
come
in
would
be
from
from
all
those
different
areas.
It
depends.
It
usually
depends
on
the
the
goals
of
having
all
the
members
in
one
place.
Here
we
have
some
some
organizations
where
they
have
a
separate
workspace
for
each
github
organization,
because
they
kind
of
see
that
each
one
as
an
individual
community,
but
then
I'd,
say
the
more
common
thing
is
any
organization
on
github.
C
They
put
it
in
the
same
orbit
workspace
and
that
way
even
activity
from
the
same
member,
the
same
github
handle
across
all
of
those
different
organizations
just
goes
into
one
person,
and
so,
if
you,
if
we
have
someone,
that's
contributing
across
all
of
those
different
github
organizations,
that
will
just
that
will
all
show
up
in
their
timeline
and
they
would
be
able
to
see
which
repository
it
was.
A
And
okay,
so
is
it
on
to
the
user
to
make
their
that
twitter
mapping
like
do
they
have
to
log
into
the
profile
and
and
do
that.
C
The
let's
see
for
the
the
twitter
mapping
and
the
twitter
to
github
mapping
we'll
do
that
automatically
if
it's
the
same
handle.
So
we
we
have
a
set
of
rules
where
we
try
to
see
if
two
members
or
across
different
platforms
are
the
same
person,
we're
incorporating
things
like
matching
on
the
name
matching
on
an
email,
if
they've
publicized,
that
in
another
place
or
handles.
C
A
Yeah,
I
would
completely
pull
out
matching
by
username,
because
we've
had
other
instances
where
people
have
tried
to
spoof
profiles
like
that
is
something
like
I
would
never
never
do
unless
it's
like
you
know,
twitter
verified
account
yeah.
C
A
C
We're
happy
to
share
links
and
all
of
that
we're
in
kind
of
an
early
access
mode,
we're
just
a
year
old
as
a
company,
so
say
that
orbit
is
ready
to
solve
all
the
community
challenges
of
the
world.
We're.
C
Sign
up
create
an
account
plug
in
a
personal
github
if
you'd
like
to
see
more
personal
twitter.
If
you
want
to
see
either
of
your
communities
there
for
us
just
to
get
the
feedback
and
get
thoughts
from
them,.
A
Like
for
me,
specifically
like
I'm,
I'm
looking
for
useful
statistics
like
and
to
break
down
like
sort
of
more
granular,
like
dev
stats,
type
thing
when
it
comes
to
like
engagement
on
twitter,
that
doesn't
matter
nearly
as
much
for
like
our
group
from
a
you
know,
contributor,
like
persona
type
view
that
you
know
if,
if
I
was
in
devrel
at
a
company
that
would
matter
more
but
like
even
when
it
comes
to
engaging
with
our
main
kubernetes
to
io
count,
we
like
that's,
not
something
we
normally
use.
A
We
do
have
a
specific
contributor
focused
account,
but
that's
that
tends
to
be
focused
on
like
announcements.
C
Yeah
well
one
thing
we
can:
we
can
do
because
again
we
don't
have
a
lot
of
data
in
this
workspace.
So
there's
some
reports.
I
can't
I
can't
show,
but
that's
definitely
something
we're
trying
to
make
more
powerful,
and
maybe
we
can
look
at
a
couple
of
the
devs.
That's
if
there
is
a
way
that
you
can
create
help
create
a
dashboard
or
a
report
or
something
that
doesn't
exist
already.
C
That's
really
definitely
something
we
we
can
do
probably
just
have
to
look
and
see
what
what
information
is
hard
to
get
today
and
if
there's
something
something
we
can
help
there.
A
Yeah,
honestly,
probably
laurie
has
put
together,
like
the
the
big
spreadsheet
of
the
various
like
personas,
the
different
dashboards
that
that
you
know
we're.
Looking
for
that.
Don't
doesn't
currently
exist
on
devstats.
C
Want
to
learn
more
learn
more
about.
What's
in
that
spreadsheet,
for
sure,
and
I
I
might
there
there's
a
lot
of
cells,
so
it
might
take
me
a
little
bit
to
digest
some
of
it,
but
that's
really
really
good
questions
and
I'm
really
interested
to
see
how
we
could
get
some
answers
to
those.
A
Where,
like
just
looking
at
where
I
think
it
would
be
more
useful,
is
for
like
smaller
projects
that
are
trying
to
grow
their
contributor
base
in
its
current
form,
kubernetes
has
around
50
000
contributors
and
roughly
3
000,
I
would
say,
like
active
contributors
with
about
1300
org
members.
A
And
just
from
the
the
general
engagement
stuff
in
there
like
I'm,
just
not
not
quite
sure
what
we
would
be
able
to
get
out
of
it,
that
you
know,
isn't
there
in
dev
stats
already
I'm
not
trying
to
like
you
know,
you
know
be
blunt
or
curtail
like
you
know
like
stop
the
idea.
It's
just
like
with
the
contributor,
like
sig
lee
type,
you
know,
hat
on.
C
C
That
that's
what
kind
of
some
work
we
want
to
dig
into
and
see
see
what,
if
there
is
something
there
and
the
the
maybe
some
things
on
the
the
personal
side.
There's
the
aggregate
data,
but
I'm
wondering.
H
C
Maybe
there's
a
part
of
the
kubernetes
community
or
a
certain
segment
of
contributors
that
maybe
it's
the
active
ones.
The
3000,
where
it's
interesting
to
have
like
a
timeline
of
activity
at
the
individual
level
or
even
a
smaller,
a
smaller
thing.
A
lot
of
the.
H
C
Maybe
a
subset
of
the
community.
That's
really
high
touch
that.
That's
very
you
know
the
where
the
where
the
contributor
experience
is
the
most
important,
but
you
know
that's,
that's
just
a
couple
of
ideas
off
the
top
of
my
head
right,
yeah.
F
I
think
it
is
directly
related
to
the
contributor
persona,
because,
if
you
are
in
a
performance
review
and
your
contributions
to
this
project
are
a
factor
and
you're
getting
promoted
or
not,
then
you're
going
to
want
to
have
that
data
to
show
your
involvement
over
time.
I
think
one
of
the
challenges
is,
though,
is
that
if
you
scratch
the
surface
of
a
commit,
there's
a
lot
of
context
there,
it's
like
you
could
have
one
super
valuable,
commit
all
quarter
right
or
a
pull
request.
All
quarter.
F
That's
just
required
a
lot
of
work
and
alignment,
and
that
story
needs
to
be
told
somehow
so
that
it's
not
like.
Oh
you,
just
did
one
pull
request.
This
quarter,
you
know
you're,
you
could
have
delivered
a
super
valuable
part
of
the
part
of
the
project.
So
just
how
do
you
actually
support?
C
Yeah,
what
one
thing
we've
worked
on
a
little
is
a
way
to
publicly
show
contribute
contribution,
timelines
and
and
make
that
make
that
easy
and
then
do
that
in
a
way.
That's
like
nicely
designed
and
really
something
that
a
contributor
would
want
to
show
off
and
want
to
be
proud
of.
C
Talk
about,
we
spent
spend
some
time
thinking
about
that,
because
the
the
timeline
is
there.
So
we
can
say
that
these
are
the
five
pull
requests
this
month,
and
maybe
even
this.
This
one
in
particular
has
a
lot
of
reactions,
a
lot
of
thumbs
up
and
thumbs
ups
and
hearts,
and
things
like
that.
So
maybe
we
should,
you
know,
lead
with
that
one
and
then
fill
in
the
other
contribution
activity
around
it.
C
We've
actually
thought
about
that,
a
little
bit
from
how
we
design
side
and
how
we
might
show
that,
but
usually
it's
the
it's.
The
community
managers
who
are
logging
into
orbit,
but
it's
an
interesting
idea
to
have
the
contributors
themselves
log
in
to
see
their
own
contribution
history.
That's
not
something
we've
thought
about
that
much,
but
it
could
be
really
interesting
context
like
this,
for
I
want
to
see
my
contribution.
History
maybe
context
on.
F
C
A
C
Got
to
know
georg
and
tergia
folks,
and
then
chaos
stopped
by
chaos
khan
when
it
was
happening
at
the
same
time
as
follows
them,
I
think
so.
Yeah
I've
gotten
to
know
gotten
to
know
them
a
little
bit.
We
still
don't
have
any
chaos
specific
metrics
inside
of
orbit,
but
that's
mostly
just
a
limitation
on
time
and
just
not
not
being
able
to
go
deep
with
them,
but
we're
big
fans
of
the
work
that
they're
doing.
A
I
was
gonna
say
like
if
you
want
a
group
to
talk
to
they're,
probably
the
the
right
people
to
ping
on
on
some
of
like
community
health,
metrics
yeah.
A
In
in
general,
like
kubernetes
itself,
doesn't
really
have
like,
like
dedicated
community
managers,
contributes
is
sort
of
that
role,
but
it's
like
we
don't
like.
We
aren't.
You
know
managing
every
contributor
anything
like
that.
Yeah,
like
we
wouldn't
be
creating
profiles
for
people.
A
A
C
A
Though
the
big
problem,
like
some
people,
might
be
okay
with
that,
but
I
know
some
of
our
more
privacy
focuses
just
like.
Why
did
you
install
this
in
the
org?
Why.
A
C
Yeah
yeah,
the
sensitivity
is
not
lost
on
us,
something
we
thought
about
a
bit
and
every
community
has
his
own
norms
and
level
of
sensitivity
around
that
every
every
person
too.
So
they
have
it's
good
for
us
to
be
aware.
They
appreciate
the
the
candor
and,
and
all
that
always.
F
I
think
you,
I
think
the
biggest
challenge
here
is
like
how
do
you
measure
value?
I
don't
know
if
anybody's
really
figured
this
out
like
because
there
are
so
many
ways
to
interpret
value,
and
so
much
of
the
value
of
a
project
is
not
necessarily
something
you
can
count
at
least
automatically
so
lines
of
code.
Well,
oftentimes,
it's
better
to
remove
code,
and
so
you
can't
go
with
that
all
the
likes
and
such
you
know,
we
covered
that.
F
G
I
absolutely
second
that
and
and
it's
it's
such
a
fascinating
part
about
this
project
or
any
open
source
project,
because
those
incentives
are
not
just
rough
metrics,
they
become
cultural,
and
you
know
people
talk
to
me
about
the
documentation
in
terms
of
how
many
pull
requests
should
I
make
how
many
lines
of
writing
should
I
make
and
that
that's
never
a
good
measure
of
documentation.
C
A
Actually
brings
up
a
good
point.
Dude,
do
you
want
to
to
mention,
or
do
you
want
me
to.
I
Sure
yeah,
I
just
so
like
the
openstack
community,
has
a
couple
different
things:
kind
of
like
dev
stats
too,
and
at
various
points
in
time,
they've
been
like
very
popular
and
lots
of
people
look
at
them
and
then
there's
a
lot
of
gamification.
That
happens.
I
I
know
that
there
are
certain
companies
that
all
tell
their
employees
that,
like
oh,
you
need
to
have
this
many
patches
every
month
or
whatever,
and
then
the
like
statistics
really
stop,
meaning
anything
because
it's
a
bunch
of
like
oh,
I
fixed
this
spelling
mistake
here
and
here
and
here
and
it's
a
hundred
different
things
and
it
should
have
just
been
one
pull
request
or
patch
or
whatever,
and
so
it's
like
really
scary
to
like
quantify
things
because
gamification
always
happens
and
keeping
context
with.
I
All
of
that,
too,
is
hard
like
how
do
you
quantify
a
contributor?
Well,
you
can
say
they've
done
this
many
you
know
reviews
which
is
good,
but
there's
a
lot
of
things
that
you
like
can't
quantify
like.
Oh
they,
you
know
spent
this
many
hours
working
on
this
document
and
they
worked
on
the
document
with.
However,
many
other
people
and
that's
hard
to
capture.
F
You
know
just
shipping
things,
and
sometimes
the
most
valuable
thing
one
can
do
is
not
to
ship
anything
at
all,
but
to
actually
help
other
people
look
at
what
they're
shipping
and
decide
if
it's
actually
the
right
thing
yeah.
It.
C
I
will
just.
A
Stop
and
because
dropping
because
I.
C
To
leave
in
four
minutes,
so
I
just
wanted
to
to
ask:
is
there
maybe
someone
laurie
if
it's
you
or
someone
else
where
I
could
keep
the
the
conversation
going,
so
I
feel
like
maybe
we
we've
had
a
little
bit
of
time
to
scratch
the
surface,
and
I
know
that
we've
talked
a
lot
about
the
staff
and
I
just
I
want
to
want
to
get
a
better
sense
of
just
just
things
that
could
be
useful.
So
maybe,
if
there's
there's
someone,
I
can
follow
up
with.
F
H
F
So
it
takes
a
while
to
figure
all
the
reads
and
dial,
and
it's
always
for
every
cig:
there's
that's
a
different
culture
in
itself,
so
you
want
to
to
talk
to
people
and
find
out
what
their
reality
is.
What
are
their
challenges
and
obstacles
and
then
decide
what's
reasonable
and
it
you
know
it
never
will
be
perfect,
because
that's
just
the
way
it
goes,
but
certainly
to
see
higher,
see
a
faster
velocity.
You
know
closing
more
things
out
and
seeing
workloads
for
different
sigs
go
down
over
time.
F
That
would
be
a
goal
because
they
carry
a
huge
workload
and
and
many
of
these
things
and
it's
just
a
you-
know
fire
hose,
and
so
how
can
we
support
them
to
get
behind
process
changes
that
will
slow
down
that
flow.
A
Sorry,
the
I
just
know
I
I
just
noticed
that
there
were
sergey.
You
had
something
on
also
the
open
mic
discussion.
I
I
completely
missed
that.
I'm
so
sorry.
H
It's
a
one
minute
thingy
and
it's
not
important.
A
Okay,
well,
if
you
want
to
we
can
we
can
follow
up
in
in
slack
about
it.
I
just
I
I
hate
that
I
missed
that
and,
like
you
know,
didn't
give
you
enough
time
to
talk
about
it.
H
E
E
E
So
probably
the
next
step
would
be
to
discuss
to
discuss
the
value
of
this
tool
for
the
community
outside
of
the
current
meeting
in
in
slack
wisdom
and
other
folks
who
could
be
interested
in
evolution,
dead
and
and
yeah.
That's
that's
it
thank
you
for
for,
for
sharing
for
sure,
until
your
blessing
josh.
A
I
think,
with
that
we
have
one
minute
left.
Is
there
anything
anyone
really
wants
to
say
at
the
last
possible
moment.
A
Okay,
well,
I
think
we
can
call
it
there.
Thank
you
for
coming
everyone.
I
will
see
all
around
slack
and
probably
at
the
next
meeting.