►
From YouTube: SIG Contributor Strategy Governance WG 2020-10-13
Description
SIG Contributor Strategy Governance WG 2020-10-13
A
A
A
The
so.
B
Yeah
I
got
mine,
well,
the
first.
I
go
to
a
professional
and
she
she
does
most
of
it
and
then
I
just
sort
of
touch
it
up.
Just
keep.
B
A
B
A
Unfortunately,
on
on
video,
it
mostly
looks
black.
B
B
A
We're
waiting
it's
time
that
we
need
to
pester
the
existing
native
steering
committee.
B
A
A
So
but
yeah
it
would
be
good
to
know
and
be
good
to
know
what
they
expect
in
terms
of
a
schedule,
because
we're
already
past
the
original
schedule.
I
proposed.
B
A
The
and
I'm
also
not
all
that
clear
on
how
many
people
are
being
elected
so.
B
A
It
didn't
get
updated
after
they
eliminated
the
end
user
positions
yeah,
so
the
which
I'm
still
sad
about,
but.
B
B
Steering
committee
meeting
we
can
drop
into
get
answers
to
our
questions,
live.
A
I
don't
know
actually
because
right
they
were
supposed
to
make
more
of
their
meetings
public
after
the
charter
change,
but
there
wasn't
a
specific
schedule
attached
to
that,
and
it
really
is
true
that,
like
half
of
the
k-native
principles
took
the
week
off
last
week,
because
I've
been
trying
to
get
some
stuff
done
internally
for
promoting
k
native-
and
you
know,
people
just
did
not
start
returning
my
messages
until
yesterday.
So
the.
A
A
Yep
she
didn't,
I
guess,
when
we're
not
arguing
about
steering
committees,
people
are
not
really
interested
and
I'm
like,
I
don't
care.
A
Yeah
so.
A
B
A
A
bunch
of
us
the
which
is,
we
need
to
start
preparing
for
the
session
for
kubecon.
B
A
Decide
who's
recording
what
and
obviously
we
need
some
of
the
people
from
we
need
at
least
like
carol
in
there
as
well
the
for
the
contributor
growth
portions
of
things,
the
I
mean
what
I
was
seeing
was
about
10
minutes
going
over.
You
know:
here's
your
project
checklist
at
the
different
levels
of
maturity.
B
A
The
things
that
you're
expected
to
have
or
should
have
and
then
open
it
up
to
the
q,
a
where
we'll
actually
find
out
who's
participating
and
help
them
through
specific
things
that
they
need
to
have.
A
I
I
was
suggesting
10
minutes,
okay,
which
is
about
enough
time
to
go
over
our
sort
of
tree
of
things
that
projects
should.
B
A
A
Yes,
it
is
yes,
it
is
the
and
again
like
in
real
project
time.
If
the
paperwork
is
super
engaging,
then
it's
because
there's
a
problem
so
yeah.
A
So
the.
A
Yeah,
I
mean
obviously
the
most
engaging
thing
would
be
to
take
an
existing
project
that
has
a
relatively
incomplete
paperwork
profile
and
go
over.
What's
there
and
not
there,
the
problem
is
that
the
timing,
for
that
is
impossible
right.
We
would
have
to
find
such
a
project
now
and
count
on
and
count
on
them
being
incomplete
for
long
enough
for
us
to
record
the
video.
A
The
so
like
say
hey,
you
know
they
have
a
contributing.md
thing
here,
but
it
doesn't
actually
tell
you
how
to
contribute.
A
Well,
we
could
record
us
as
sort
of
a
panel
if
we
were
to
do
it
via
conference
call
stuff
like
we
recorded
via
zoom
yeah,
the.
B
B
B
However,
at
the
end
of
my
day,
after
a
day
full
of
meetings,
I
I'm
not
sure
how
much
creativity
I
have
to
offer
this
finding
something
yeah
engaging
solution.
A
Yeah,
well,
that's
another
reason
to
keep
the
presentation
part
of
things
short,
the
so
that
we
can,
you
know,
go
straight
to
helping
people
with
the
actual
problems
they
have
yeah.
The.
A
A
Need
to
create
an
outline
we
need
to.
I
mean
one
of
the
reasons
why
I
like
the
idea
of
having
a
project
to
look
at.
If
we
could
find
one
would
be
that
it
would
allow
us
to
do
something
that
wasn't
just
slides,
yeah
like
possibly
not
do
slides
at
all,
except
the
you
know
name
of
the
session
slide,
because
we
actually
could
go
back
and
forth
between.
A
A
checklist
document
and
a
and
looking
at
a
project
and
that's
going
to
be
more
engaging
than
looking
at
a
bunch
of
slides.
B
A
The
plus
it's
stuff
that
people
can
refer
to
later.
B
A
I
mean
we
kind
of
have
that
with
our
content,
our
list
of
content-
that's
required,
the
you
know,
and
so
it
would
just
be
converting
parts
of
that
to
a
checklist.
A
A
A
A
A
B
A
The
so
the
yeah,
I
honestly
thought
I
would
have
more
time
to
work
on
this
in
september.
B
B
Yeah
really
pain
there.
Maybe
we
should
just
start
that
master
checklist,
doc,
google,
doc
right
now,
throw
it
in
the
minutes
and
that
way
we
can
both
add
to
it,
and
maybe,
if
you
want
to
ping
caroline
and
have
here
add
some
stuff
to
it,.
B
A
A
B
A
B
A
A
B
B
A
By
the
way,
I
made
my
proposal
that
the
cncf
should
consider
having
a
joint
code
of
conduct
committee
for
all
of
the
smaller
projects.
Yeah
crickets.
B
A
B
A
The
not
that
angelo
really
takes
vacations,
but
I
don't
think
we
should
reinforce
that.
A
So
the
also
you
know
I
haven't
said
this
to
you-
know
the
cncf
folks,
but
there's
also
the
issue
that
if
the
code
of
conduct
complaint
is
against
a
member
of
the
linux
foundation,
event
staff-
that's
going
to
be
a
huge
conflict
of
interest
for
angela.
B
A
The
so,
okay,
the
so
what
else
we
got
here.
B
A
A
A
A
A
A
B
A
B
B
A
So
the
I
guess
the
one
difference
is
that
technically
the
list
of
end
users
could
be
less
public
at
the
incubating
stage.
That
is,
it
could
be
a
document
you
furnish
only
to
the
cncf
sigs
and
not
something
you
have
published
in
your
project.
A
Although
I've
never
actually
seen
that
because
I
mean
at
least
having
gone
through
it
with
projects,
we're
always
saying,
can
we
publicly
reference
you
because.
B
A
A
A
B
A
Because
then
you're,
not
what
version
is?
This
is
not
a
matter
of
opinion
anymore
yeah,
although
it's
not
really
true
having
having
worked
on
both
firefox
and
postgres,
you
can
have
a
very
defined
release,
process
and
version
numbers
can
still
be
a
matter
of
opinion.
A
A
A
You
know
the
way
that
I
actually
got.
People
to
switch
versioning
numbers
was
that
I
merged
a
page-long
function,
written
in
perl
to
interpret
the
version
numbers.
A
Pearl
and
I
was
like
okay-
well-
try
rewriting
this
in
python,
I
tried
it
was.
This
is
one
of
the
areas
where
pearl
really
shines.
The
python
version
was
four
times
as
long
and
they
changed
the
version
numbers
rather
than
to
use
pearl.
A
A
It
depends
on
who
the
writer
is.
I
mean
it
does
help
that
the
civs
code
came
out
of
academia
and
therefore
it's
actually
written
to
be
read
reviewed
by
faculty,
who
might
not
actually
be
programmers.
B
A
And
and
as
a
result,
a
lot
of
things
that
could
have
been
rolled
up
into
pearl
one-liners
were
not,
which
makes
it
much
easier
to
read
yeah
the
so,
which
is
good,
because
the
vote
counting
algorithms
are.
A
A
A
Okay,
yeah
and
I
think
if
we
had
all
of
that,
we
would
have
stuff
for
people
and
then
they
could
start
pitching
questions
of
hey,
I'm
pitching
my
project
to
sandbox.
Do
I
need
x
or
I
need
x,
and
what
does
that
look
like
yeah
so
and
then
I'm
going
to
ask
everybody
to
look
around
and
see
if
they
know
a
project
that
is.
B
Yeah,
do
we
want
to
put
this
in
the
in
the
github
repo.
A
Yes,
okay,
but
but
let's
finish
it
out
on
on
docs
yeah,.
A
We
can
collaborately
edit
it
and
then
yes,
no,
we
definitely
want
it
in
the
github
repo
as
a
document
that
people
can.
B
Yeah,
the
other
thing
I
think
we
should
do
before
we
publish
it
on
github
is
maybe
include
links
to
good
examples
of
these.
So
do
we
have
a
governance
md.
That's
a
good
example
of.
A
B
B
B
So
what
are
what
are
next
steps?
I
don't
think
we
can
rely
on
just
the
the
meanings
that
we
have
to
finish
this.
A
A
B
Yep
nope,
that's
cool
if
you
could
work
with
carolyn,
because
this
is
I'm
pretty
much
gonna
be
done
at
this
point,
but
I
could
do.
I
could
do
wednesday
after
9am
pacific.