►
From YouTube: Intro: SIG PM (Kubernetes) - Ihor Dvoretskyi, Cloud Native Computing Foundation & Dustin Kirkland
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Intro: SIG PM (Kubernetes) - Ihor Dvoretskyi, Cloud Native Computing Foundation & Dustin Kirkland, Google
Program, project, and product management in open source software communities represents a significant challenge. Such positions traditionally rely on hierarchical structure to drive work from the executive tier down to the team level, whereas in OSS there is little or no accountability other than that gained through influence and commutative trust. SIG-PM of the Kubernetes community focuses on the aspects described above, and the current session will provide the intro overview of Kubernetes SIG-PM.
To learn more click here: https://sched.co/FuLL
A
All
right
so
welcome
everyone,
just
a
brief
intro
again,
my
name
is
iridar
etske
I'm,
a
developer
advocate
at
cloud
native
computing
foundation
and
I
am
a
co-chair
of
6:00
p.m.
at
kubernetes
community
and
today,
we'll
have
the
brief
intro
to
to
6:00
p.m.
what
6:00
p.m.
is.
What
are
our
goals?
What
what
are
our
roles
and
how
can
you
potentially
engage
with
us
as
a
as
a
p.m.
or
potential
new
p.m.
within
a
cabinet
is
community.
A
So
let
me
start
with
the
brief
history
here
or
right
before
start,
so
any
project
managers
here
in
this
audience
on
any
program-
managers,
perfect
yeah.
So
just
a
brief
description
of
p.m.
what
what
is
sick
p.m.
initial
we've
been
established
as
a
product
management
group
as
a
product
management,
C
cuisine,
kubernetes
community
in
our
first
goals,
were
to
to
work
on
the
features
to
work
on
them
on
the
roadmap
and
a
backlog
and
so
on.
So
we
we
even
haven't
started
as
the
cig
we've
started.
A
As
a
working
group,
we've
been
one
of
the
first
working
groups
within
the
kubernetes
community.
We
had
only
a
few
people
from
different
companies.
Who've
been
interested
in
working
with
with
the
kubernetes
community
and
working
on
the
features
and
a
roadmap
of
kubernetes.
How
can
we
define
the
future
of
cabinet
as
what
should
we
do
to
make
when
it
is
more
successful
not
only
to
do
tomorrow
but
in
on
a
strategic
perspective?
So
what
what
should
we
do
with
kubernetes?
A
What
should
we
do
always
in
the
communities
community
to
to
ensure
that
communities
as
a
project
as
a
super
sauce
project
will
survive
him
in
five
or
ten
years?
And
how
can
we
see
its
future,
so
they've
been
established
as
the
working
group,
the
difference
between
working
group
and
a
sig
sig
is
a
special
interest.
Group
working
group
ISM
is
well,
WG
is
a
working
group,
so
the
main
difference
between
them
is
that
seek
is
the
our
main
atomic
unit
of
the
kubernetes
community.
A
So
if
you
are,
if
you
are
remember
the
sig,
if
you
have
a
sig,
that
means
that
you
should
have
the
well-defined
process.
You
should
have
the
like
the
regular
meetings,
so
sig
easy
is
a
constant
unit
within
the
kubernetes
community.
Working
group
is
a
bit
of
a
flexible
soap.
Working
group
can
can
be
established
to
solve
some
specific
question
and
you
can
can
be
all
the
way
after
after
this
question
after
this
single
specific
question
will
be
solved,
so
sig
is
more,
is
no
constant
unit
and
as
a
sick,
we
are
working
permanently
on.
A
On
the
same
on
the
same
scope
of
questions,
so
we've
started
as
as
a
working
group.
Now
we
are
a
sick
p.m.
and
on
this
slide
you
can
notice
the
general
overview
of
the
kubernetes
community.
So
we're
where
we
are
this
slide
can
be
a
bit
outdated,
I've
checked
it,
so
it
was
updated
by
me
around
two
months
ago.
Today
we
may
have
a
bit
more
working
groups
and
six,
but
in
general,
its
the
general
review
of
the
kubernetes
community
of
they're,
all
six
that
we
currently
have
of
all
the
working
groups
and
any
committees.
A
So
on
this
slide,
you
may
notice
that
we
have
the
group
of
six
that
are
called
the
project
white
six.
The
Sikhs
are
working
on
the
are
on
on
the
questions
that
are
related
to
the
scope
of
the
entire
project
of
the
entire
cabinet
is
project.
So,
for
example,
we
have
sig
release
that
is
working
specifically
on
the
questions
related
to.
How
can
you
release
cabinet
I
suppose
is
a
process
of
losing
cabinet
is
sig
releases,
stuff
and
they're
really
same
and
so
on.
So
we
have
contributor
experience
working
group.
A
Oh
sorry,
contributor,
experienced
seek,
which
is
also
established
for
enhancing
their
our
knowledge
about.
How
can
you
contribute
to
communities?
What
should
you
do
to
become
a
contributor?
How
can
you
success,
as
or
as
an
existing
contributor
as
an
you
bien
sûr,
and
we
have
a
CPM
here
so
again,
sig
p.m.
is
one
of
the
project
wide
groups.
We
are
focused
on
the
on
the
entire
health.
The
biggest
difference
between
the
project
wide
groups
with
horizontal
or
vertical
groups,
is
that,
for
example,
vertical
groups
are
more,
let's
say,
technical
oriented,
so
at
6
p.m.
A
we
generally
do
not
deliver
any
code.
We
deliver
different
artifacts,
but
we
are
not
writing
code.
Who
cabinet
is
itself
if
you're
looking
for
some
for
writing
some
some
code
for
for
adding
some
new
functionality
to
cabinets?
You
should
take
a
look
at
one
of
these
groups,
so,
for
example,
if
you
are
looking
for
for
the
networking
technical
error,
so
sig
network
is
here
are
the
same
with
storage,
for
example,
node
schedule
anus.
So
the
biggest
difference
again
between
between
the
between
these
groups
between
these
special
interest
groups
are
comparing
to
the
project
wide
groups.
A
Is
that
generally,
these
groups
at
the
way
and
the
technical
functionality
to
kubernetes
itself
the
project
wide
groups
are
more
like
management
style
groups
again
as
seek
releasing
contributor
experience.
Sick
PM,
sick
dog
season
has
a
great
sample
of
of
the
project
wide
project
white
interaction
with
the
wizarding,
with
the
entire
kubernetes
project,
so
sick
dogs
is
exactly
that
cig
that
is
focused
on
the
right
and
documentation
for
cabinet
is
not
the
code
base,
and
so
so
that's
that's
in
general.
So
in
this
slide
you
can
see
our.
A
What
is
our
place
in
the
cabinet
is
community,
and
just
recently,
a
few
months
ago,
we
finally
defined
our
charter
or
the
goals
of
sig
p.m.
what
we
are,
what
we
are
doing
within
the
communities
community
as
a
CPM.
What
is
our
all?
What
we
are
responsible
for?
What
we
are
not
responsible
for
word
is
responsibility
of
the
of
the
different
special
interest
groups,
and
so
on.
So
specifically,
CPM
is,
is
a
Seikh
that
focus
that
is
focused
on
on
enhancing
kubernetes
as
a
product
on
enhance
and
current
processes
within
community.
A
So
sick
PM
is
a
sick
product
management.
It's
a
sick
program
management
and
sick
project
management,
as
I
mentioned
before,
we've
been
initially
established
as
a
product
management
only
sig,
but
with
the
scope
extension
today
we
are,
we
simply
call
ourselves
as
CPM
and
it
can
be
defined
in
in
a
different
way.
So
if
you,
if
you
prefer,
are
calling
it
as
a
product
product
management,
it
will
be
correct,
but
calling
it
a
program.
Management
signal
be
correct
as
well,
and
we
are
also
at
6:00
p.m.
A
we
are
also
responsible
for
staffing
the
different
release
roles.
So,
as
I
mentioned
before,
our
cig
release
is
that
group
within
the
kubernetes
community
that
is
focused
on
the
release
process
and
how
and
in
which
way
to
you
early
SKU,
Benares,
it's
develop
Realty
at
the
same
time
are
the
group
of
so
sick
release
is
stuff
in
the
release
team.
So,
when
you're,
when
we
are
releasing
communities,
we
have
a
group
of
people
who
are
responsible
for
different
roles
and
all
these
people
are
forming
the
single
release
team
and
at
6
p.m.
A
we're
responsible
for
stuff
and
if
he
rolls
for
our
for
the
release
team.
So,
first
of
all
it's
the
release
features
lead.
It
was
one
of
the
first
roles
within
the
within
the
release
team,
the
first,
the
first
witches
lead
we
had
even
before
the
early
steam
as
East
was
formed.
So
another
background
at
the
beginning,
kubernetes
was
released
not
by
the
well
define
team,
not
by
the
not
by
the
people,
but
we
had
a
single
person
who
was
responsible
for
releasing.
He
was
called
release.
A
Our
and
some
different
people
from
kubernetes
community
could
help
him.
So
one
of
these
folks,
who
has
helped
him
really
serve
around
2
or
3
years
ago,
was
was
the
feature
ously,
so
features
features.
Error
was
one
of
the
most
important
during
the
release,
process
and
you're.
In
some
period
of
time,
we've
we've
decided
that
we
should
establish
there.
The
team
instead
of
the
single
person
and
the
release
lead,
was
one
of
their
one
of
the
first
first
people.
A
First
members
also,
we
are
staff
in
their
lease
Marketing
Coordinator,
its
comparably
brand
new
role,
so
we
we
have
started
working
on
their
market
in
collaboration
with
with
the
community,
not
not
so
much
time
ago.
So,
typically,
it
was
the
vendors
responsibility
or
C&C
of
responsibilities,
but
now
the
key
bananas
community
it.
A
So
at
the
same
time,
around
one
one
or
one
and
a
half
years
ago,
we
decided
that
we
should
have
the
designated
person
who
will
focus
on
their
the
market,
marking
collaboration
ways
with
with
the
wider
setting
up
interviews
with
media,
publishing,
block-posts,
promoting
them
in
the
social
networks,
and
so,
and
so
this
is.
This
is
the
role
of
their
release.
Marketing
coordinator,
why
coordinator?
A
Because
it's
not
the
single
person
who
is
responsible
for
the
marketing
marketing
activities
around
release,
it's
just
a
person
who
is
working
with
other
people
in
the
error
on
on
the
stuff,
and
we
are
also
working
on
on
defining
the
product
roadmap
committee.
We
don't
have
this
committee
yet,
but
we
are
working
on
heaven,
even
a
group
group
of
people
who
will
focus
on
creating
their
well-defined
roadmap
for
kubernetes.
So,
for
example,
around
two
years
ago
we
heard
we
we
had
our
first
session.
A
There
are
kubernetes
contributor
summit
where
we
had
a
brief
discussion
with
there
all
six.
How
can
we
seek
Benares
in
them
during
the
next
year?
So
what?
What
can?
What
what
we
should
focus
on
in
development
for
kubernetes
in
the
next
year?
And
what
should
we
not
focus
on
what
our
main
goals
so
and
and
the
year
after,
after
after
this
session,
we
had
yet
another
session
recapping
our
achievements
during
the
last
year
and
also
defining
our
goals,
our
roadmap
for
14
years,
so
as
I
mentioned
for
6
p.m.
A
is
responsible
for
roadmap
as
well,
and
we
are
exactly
debt
seek.
That
is
that
is
interested
in
heaven.
The
clear
vision
of
we're
given
a
this
is
headed
to
in
the
next
few
years
ghostly.
Today
we
are
all
excited
about
communities,
but
nobody
knows
what
what
will
happen
in
five
years.
We
probably
may
have
an
answer
on
that
question.
We
don't
have
an
answer
on
that
question,
but
we're
working.
That's
our
world
all
right
and
user
Berg
housekeeping
information.
So
if
you
are
interested
in
reading
more
about
6:00
p.m.
A
here
shortly
in
bitly,
it
points
to
github,
so
we
have
defined
shorter
on
github.
We
have
all
the
defined
roles
and
responsibilities
of
our
group.
We
have
a
group
of
chairs,
so
it's
apartments
in
high-caliber
miles
in
myself.
We
are
teachers
over
the
entire
seat.
We
also
have
sub
project
the
program,
management,
sub-project
and
jason.
Redeemers
is
he's
one
of
the
most
experienced
program
managers
within
the
communities
community
in
his
day.
It's
a
project
lead
here
and
we
also
have
the
project
management's.
A
A
project
were
Steven
Augustus
and
Dustin
Kirkland,
who,
which
name,
was
not
able
to
join
me
today.
They
are
leading
this
again
speaking
about
stuff
in
the
roles,
for
example,
Steven
Augustus,
who
is
the
project
management's
a
project
lead,
he
salsa
day,
features
lead
for
all
for
the
last
few
releases,
all
right
and
the
final
one.
So
the
main,
the
main
artifact
did
that
CPM
is
focused
on,
are
the
features
and
enhancements.
So
initially,
we've
created
the
terminology
or
featuring
the
concept
of
features
around
two
years
ago.
A
Two
and
a
half
years
ago
and
feature
was
specifically
some
some
group
of
new
functionality
for
Cuban
artists
that
can
deliver
that
can
bring
some
some
new
experience
to
the
end.
We
haven't
had
the
well-defined
terminology
of
what
is
feature
or
what
is
not
a
feature,
but
we've
agreed,
like
informally,
agreed
that
if
you
can
write
a
blog
post
about
this
new
functionality,
this
is,
if
the,
if
the
scope
of
this
of
this
code
base
of
you've
discovered
unity
is
wide
enough,
so
you
can
write
a
blog
post
and
describe
it
in
details.
A
What
what
does
it
bring
new
for
us?
It's
a
feature:
if
not
it's
selective
ography,
some
minor
features
are
tracked
as
the
github
issues
on
there
or
kubernetes
slash,
enhancements
repo.
It
was
initially
called
features,
but
not
so
much
time
ago,
we've
renamed
the
process,
we've
renamed,
echoing
the
features
itself
to
enhancements
we're
also
tracking
the
features
in
the
feature
stretch
in
spreadsheet,
and
this
slide
should
be
shirt
so
you'll
be
able
to
open
the
link
here
and
see
there.
A
The
spreadsheet,
with
all
the
features
that
attract
for
the
current
the
biggest
difference
between
between
features
and
enhancements
is
dead,
so
in
we've
defined
a
new
terminology
for
enhancement
just
a
few
weeks
ago,
that
PR
was
finally
merged
on
this.
On
this
link,
the
pure
that
was
finally
merged
with
their
name
in
features
two
enhancements
and
with
combine
in
the
process
of
caps
cap
is
a
kubernetes
enhancement
process
and
it
could
be
combined
with
with
the
features.
So
today
we
have
much
more
complex
procedure.
If
you're
interested
in.
How
can
you
as
a
developer?
A
Can
you
deliver
the
new
feature
to
key
Boneta?
So
the
process
is
pretty
straightforward.
So
initially
you
have
to
discuss
your
idea.
Your
feature,
the
Airways
with
the
group
with
some
specific
group,
for
example,
if
you'd
like
to
deliver
some
functional
functionality
to
the
to
the
networking
networking
error,
you
have
to
discuss
this
idea
with
Signet
work,
which
is
responsible
for
delivering
center
node
in
the
network
era
after
you
have
after
you
have
this
idea
defined
here.
I
have
to
prepare
the
the
cap,
which
is
the
enhancement
proposal.
A
Where
are
you
you'll
describe
older
all
the
benefits
of
bringing
this,
which
you
notice
and
after
that
you
can
create
a
new
feature,
the
new
issues
in
the
enhancements
report,
where
you'll
start
tracking
we
have.
We
typically
have
three
stages,
four
features,
so
we
have
all
four
features
we
have
beta
features
in.
A
If
you
have
some
against
some
significant,
the
branding
functionality,
we
are
strongly
asking
our
developers
to
to
bring
it
as
an
alpha
feature,
so
it
could
be
tested.
It's
not
recommended
for
any
kind
of
production
usage.
So
if
you
are
running
the
kubernetes
cluster
in
here,
you
can
notice
any
alpha
features
there.
If
you
are
going
to
run
discriminators
classes
production,
we
do
not
reach
here
to
our
to
enable
this
alpha.
A
But
if
you
are
using
this
this
cluster
for
the
testing
purposes
and
if
you'd
like
to
to
have
some
tourists
and
new
experience
working
with
some,
you
stopped,
it
was
recently
print
to
communities
code
base.
It's
a
great
time
to
work
with
the
alpha.
Alpha
features
are
absolutely
unstable.
The
API
is
not
stable,
so
please
do
not
commit
any
kind
of
alpha
ap
ice.
If
you
are
developing
some
on
top
of
the
API,
which
is
the
biggest
difference
compared
to
beta
features,
so
beta
feature
is
much
more
stable
or
feature
its.
A
It
will
not
bring
any
extremely
new
functionality.
It's
the
enhancement
of
the
existing
alpha
feature.
Also,
if
you
are
using
the
beta
features
in
here
right
and
he
is
using
the
beta
API
to
write
some
new
functionality.
You
can
commit
to
that,
because
if
this
feature
is
promoting
to
beta,
the
API
of
of
the
beta
feature
will
not
be
changed.
We
have
the
deprecation
policy,
so
it
can
be
changed
someday,
but
we
have
the
deprecation
policy
that
once
once
this
API
is,
is
committed
to
be
to
be
stable.
A
We
have
it
should
pass
approximately
a
year
before
this
API
will
be
completely
deprecated.
So
we'll
have
enough
time
to
write
some
functionality.
I
using
the
Ulta
brigade
and
the
stable
feature
is
almost
the
same
as
beta
feature,
but
it's
it's
also
called
G
AIDS.
The
general
in
general
will
build
if
it's
the
typical
general
functionality
of
Combinator
the
biggest
difference
between
alpha
and
beta
features
is,
if
you
are
a
vendor
who
is
who
is
bringing
delivering
some
product
of
Cuba
natives,
for
example.
A
If
you
are
a
public
cloud
who
is
Decker,
Burnett
is
commercial
offering
you
can
commit
with
the
with
the
SLA
on
on
the
stable
features.
It's
unlikely
to
do
that.
This
beta
features
because
beta
features
can
be
broken,
sent
right
and
what
I'd
like
to
say
and
as
a
note
about
all
this
process.
So
if
you
are
working
not
only
on
communities
project
as
an
open
source
project,
you
have
to
know
that
that
prod
that
process,
that
we
have
delivered
and
depend
that
we
have
developed
during
the
last
few
years
for
6:00
p.m.
A
for
the
feature
spoon
for
the
features
and
enhancements
for
roadmap
and
so
on
will
not
necessarily
work
for
another
projects.
So
the
uniqueness
of
kubernetes
is
that
it's
probably
one
of
the
few
open
source
projects
in
the
world.
It
can
be
also
described
as
a
product,
so
we
have
the
well-defined
roadmap.
We
have
the
well-defined
backlog.
We
have
the
group
of
the
designated
product
managers
and
again
it's
the
uniqueness
of
communities.
Community
and
uniqueness
of
cabinet
is
project.
A
So
if
you
are
developing
a
different
of
Innocence
Project,
it's
a
great
sample
to
be
inspired
by,
but
you
should
not
necessarily
copy
and
paste
ever
send.
It
was
mentioned
in
the
slides
to
your
existing
process
and
that's
all
for
me,
I'm
open
for
your
questions.
I'm,
not
sure
how
much
time
we
have
with
around
15
minutes.
A
Oh,
perfect,
yeah,
that's
a
great
question,
so
please
get
started
with
this
link.
It's
the
six
pm
shorter
and
6:00
p.m.
or
6
p.m.
description,
and
what
we
are
asking
from
the
new
are
from
the
new
PMS
within
your
communities
community
that,
ideally,
if
they
have
some
existing
commercial
experience,
but
that's
not
necessarily
so
we
are
not
so
strong
in
your
current
experience.
A
We
are
like
again
we
it's
more
likely
for
us
that,
if
you're
in
a
new
person
to
the
product
management,
world
and
you'd
like
to
receive
your
first
experience
with
working
on
the
features
working
with
decidin
such
a
huge
project
and
working
with
as
a
p.m.
CPM
is
the
great
great
place
to
get
started
before
you'll
receive
your
first
commercial
experience
with
it.
We
have
our
regular
meetings.
A
We
have
the
bi-weekly
meetings
where
you
can
just
show
up
and
tell
us
that
you
hear
it
in
your
person
here
and
you,
like
you
like
to
start
with
the
with
the
sick
p.m.
activities
in
the
cabinet,
is
community
and
specifically
where
what
are
the
errors?
Where
are
your
help
can
be
where
you?
You
can
be
helpful,
for
your
cabinet
is
as
a
sick
p.m.
specifically
the
release
process
and
the
features
process,
so
at
add
release
team.
A
We
have,
we
have
release
early
steam
lates
like
the
features
lead,
and
we
also
have
shadows
so
shadow
within
the
within
the
release
within
the
listing
is
a
person
who
is
new
to
this
project,
who
is
new
to
this
process,
but
would
like
to
receive
more
more
my
experience
in
working
with
this
and,
if
you'd
like
to
be,
for
example,
the
features
lead
in
the
next
release.
We
have
to
apply
to
be
a
shadow
in
the
current
release.
A
A
yours
if
you
do
your
basic
knowledge
about
working
with
the
features
working
with
the
backlog
working
with
with
with
the
existing
instruments,
and
you
can,
you
can
convert
that
experience
to
be
to
be
a
features
lead
in
the
next
iteration.
We
are
absolutely
welcome
to
new
people,
so
there
are
any
people
who
can
be
interested
in
this
audience
who
are
interested
in
in
working
with
sick
p.m.
in
bringing
year
experience
receiving
some
new
experience
with
kubernetes
approach
with
kubernetes
project,
with
working
on
features,
roadmaps
and
so
on.
A
A
A
A
Yeah,
so
the
question
was:
is:
is
the
regular
meeting,
wonderful
members
of
CPM
or
all
put
a
wider
audience,
for
example,
for
developers
and
so
on?
So
the
meetings
are
open.
The
only
requirement
for
you.
How
can
yours,
if
an
invite
that
you
have
to
join
the
seek,
be
a
mailing
list
and
after
joining
the
mailing
list,
to
receive
your
invite?
And
after
that
you
can,
you
can
easily
journals.
A
The
general
scope
of
discussion
during
the
CPA
meetings
is
mostly
about
the
process.
We
are
not
discussing
any
technical
questions,
but
if
you
are
developer,
who
would
like
to
discuss
some
technical
questions
with
us?
We
absolutely
open.
So
our
agenda
is
open.
Just
added
a
few
notes.
There
just
show
up
to
the
meeting
and
we'll
discuss
your
question.
A
A
Well,
it's
not
necessarily
true.
We
have
we
have
select
channel
so
unfortunately
that
states.
The
constant
issue
is
Ricky
bananas.
Community,
sir
we're
working
worldwide.
We
cannot
cover
all
the
time
zones,
so
you
can.
You
can
pick
any
cig
and
if
you,
if
you're
based
in
our
APEC
region,
it
may
happen
that
you
won't
find
the
convenient
slot
for
you.
We
also
have
the
same
issue
for
Amir
Fox,
for
example.
A
So
sick
peer
meetings
are
not
not
really
so
convenient
for
our
Amir,
focusin
and
bi
am
based
in
Europe
and
my
local
time
when
I'm
joining
the
sick
p.m.
agency's
9:30
p.m.
so
pretty
late.
At
the
same
time,
we
are
trying
to
offload
all
our
activities
from
from
the
meeting
itself
to
melon
lists
to
to
dislike
channels.
We're
also
collaborating
with
other
six
like
sick
BMOC
contributor
experienced
on
their
own
cross
project.
Collaboration
also
were
working
in
this
like
channels
and
melon
listen
zone.
A
So
again,
it's
not
necessarily
for
you
to
join
our
our
regular
video
meetings.
If
it's
not
convenient
for
you,
we
have
another
channels,
but
if
you
have
a
chance,
please
do
it.
Also.
All
the
meetings
are
recorded
or,
and
they
are
available
on
YouTube.
So
if
you
are,
if,
if
you'd
like
to
to
you
them
later,
if
it's
2
P
2
a.m.
for
your
local
time,
we
are
not
able
to
do
animation.
Just
just
click
on
the
link
and
our
view.
A
A
Yeah,
so
the
question
was
how
many
members
we
have
at
6:00
p.m.
and
the
question
was:
how
can
you
build
the
process
right
fantastic
conducted
like
how
could
how
can
you
join
the
CPM?
What
is
the
process
of
joining
the
CPM
as
a
member
you
find
listed
correctly,
yeah,
okay,
assume
we
have.
We
have
a
bunch
of
folks
on
the
listed
on
this
slide,
who
are
deletes
or
deletes
of
CPM
itself,
where
teachers
of
sick
p.m.
itself
and
our
sub
project
leads.
A
we
have
also
the
group
of
people
who
are
not
listed
on
this
slide,
but
they
are
active
and
permanent
participants,
so
the
meetings
they
are
actively
involved
into
the
activities
did
that
sick
is
is
doom.
At
the
same
time,
if
you'd
like
to
join
the
think
as
a
member,
it's
pretty
easy,
so
we
don't
have
the
street
barrier
for
all
the
new
people.
A
How
can
you
join
as
a
member
just
show
up
again
just
show
up
on
the
meetings
if
meeting
if
the
video
meeting
time
is
not
convenient
for
you
just
show
up
in
the
select
channels
participating
in
mailing
list
discussions,
if
you
have
any
ideas,
how
can
you
enhance
like
what
can
you
bring
to
us
just
just
email
us
just
write
a
message
in
in
on
slack.
Ask
us
a
question
at
so
and
yep.