►
From YouTube: CNCF SIG Contributor Strategy Governance WG 2020-09-15
Description
CNCF SIG Contributor Strategy Governance WG 2020-09-15
A
A
A
A
D
B
A
A
The
okay
see,
are
we
recording?
Yes,
we
are,
I
guess
we
auto
record
in
this
channel
the
we
don't
have
a
heavy-duty
agenda
for
this
jennifer.
Last
week
we
had
a
discussion
around
this
whole
steering
committee,
etc.
Suggestion
that
alexis
has
advanced
at
the
toc
level,
folks
from
the
nats
and
grpc
projects
showed
up.
B
A
C
D
D
C
D
A
A
A
D
A
C
A
D
A
A
D
I
feel
like
there's,
there's
so
many
levels
to
that
particular
area
for
the
contributing
thing.
We
definitely
have
the
template.
It's
it's
in
process.
It's,
I
think,
there's
a
few
areas,
it's
not
in
github
for
code
of
conduct
stuff.
I
feel
like
it's.
It's
such
I
don't
know.
There's
I
want
to
use
the
word
cesspool,
but
that's
not
quite
it
either.
I
I
don't
want
to.
I
don't
I
don't.
D
D
D
Know
or
if
this
is
a
an
area
where
we
can
ask
people
like
get
people
more
involved
in
this
group
to
to
like
contribute
their
thoughts
here.
I'm
just
trying
to
think
like
this
is
an
area
where,
like
I
think,
a
lot
of
engineers,
don't
even
think
about
it.
Just
like
oh
everybody's
going
to
be
nice,
like
I
saw
this
all
the
time
with
chef
like
oh
everybody
will
just
be
nice
like.
No,
that's
not
that's.
That's
not!
It.
D
C
I
mean
how
the
conducts
are
a
little
bit
tricky
yeah,
I
don't
know.
Maybe
we
do
just
need
a
hacking
session
where
we
can
kind
of
work
on
work
on
some
of
this
stuff,
because
I
feel
like
I
feel,
like
several
of
us-
have
bits
and
pieces
of
this
already
like
I've
written
code
of
conducts
and
I've
been
on
the
enforcement
committees.
But
but
I
think
it's
a
little
bit
different
too
for
the
cncf
projects.
C
D
That
that
makes
sense,
so
so
basically
think
about
it
from
like
a
perspective
of
what
are
some
of
the
instead
of
all
the
examples
I
have
in
my
head
of,
like
oh
man,
I
totally
wasn't
prepared
for
that
thing.
Think
about
like
that,
the
the
the
the
low-hanging
fruits
of
like
here
are
the
specific
strategies
make
sure
you
do
these
things.
Here's
an
example
of
how
to
add
this
to
your
repositories,
your
projects.
D
A
I
I
think
that
would
be
an
excellent
thing
to
bring
up
with
the
staff
and
if
the
staff
tells
us,
you
know,
doesn't
have
answers
with
the
toc,
because
you're
right,
a
lot
of
projects
are
too
small,
because
particularly
one
of
the
other
things
that
you
want
in
the
coc
committee.
Right
is
some
personal
diversity,
because
if
your
coc
committee
is
composed
entirely
of
white
men
who
work
for
the
same
company,
that's
going
to
lead
to
an
inability
to
handle
certain
kinds
of
reports.
A
C
I
really
like
the
idea
of
bringing
it
up
with
staff
for
the
tv,
because
I
also
think
you
know
being
on
some
of
these.
In
the
past,
some
of
the
most
helpful
people
were
like
hr
people
and
companies.
You
know,
foundations
have
have
hr
people
who
understand
kind
of
the
understand
how
to
keep
things
confidential.
They
understand
how
you
know
how
there
might
be
legal
implications.
They
understand
some
of
the
some
of
the
ways
of
dealing
with
with
violations
that
we
might
not
think
of.
A
A
I
think
that's
all
really
good.
So
who
wants
to
take
the
ball
on
that
I
mean,
I
would
say
the
first
person
to
talk
to
about
that
is
amy
and
then
amy
will
tell
us
what
other
staff
we
want
to
talk
to
and
then,
if
the
staff
you
know,
if
we're
extremely
lucky
they'll
say
well,
we
were
already
working
on
that
and
more
likely
they
will
say
you
need
to
bring
this
up
at
the
october.
You
know
15th
toc,
meeting.
D
D
D
A
The
now.
This
might
also
be
one
of
the
ones
of
hey
that
never
re
reached
the
top
20
in
our
priority
list,
in
which
case
you
know
next
step
is
to
bring
it
to
the
toc,
but
we
can
often
save
some
effort
by
finding
out
from
the
staff
first,
whether
or
not
there's
something
in
process,
because
I
agree
with
you
that
having
reports
go
to
the
single
person
at
the
linux
foundation
is
really
not
adequate.