►
From YouTube: [SIG ContribEx] Weekly Meeting for 20220803
Description
[SIG ContribEx] Weekly Meeting for 20220803
B
So
today
is
the
august
3rd
seg
computer
experience
bi-weekly
meeting.
As
a
general
reminder,
these
meetings
are
recorded
and
we
posted
the
internet.
Some
time
later
we
abide
by
the
cnc
code
of
connect,
which
essentially
boils
down
to
please
be
excellent
to
each
other.
B
I
apologize
again
if
I'm
a
little
bit
slow.
Today,
it's
been
a
bit
of
fun
evening
with
a
lot
less
sleep
so
with
the
regular
business
or
you
know
entries
out
of
the
way
we'll
pop
over
to
events.
I
don't
think
we
have
any
office
hours
updates.
A
B
And
we'll
ping
or
later
on
the
contributor
summit,
we
did
not
have
a
meeting
this
week
as
myself
and
jeff
were
at
a
conference.
Alexander
was
there
too
and
most
of
the
ais
at
this
point
we
can,
you
know,
start
tackling
in
slack.
B
C
B
Yeah
cool
yeah:
we
should
try
and
have
all
the
staff
selected
by
well
assigned
to
various
positions
by
end
of
week.
B
B
Okay
pop
over
to
mentoring,.
A
B
A
Yeah,
I
think
cli
and
c
gaps
are
coming
up
for
that
and
today
6
eli
has
started.
I
think
paris
has
two
or
shadows
for
her
who
are
working
with
her
and
helping
out
getting
on
done
with
that
awesome.
B
B
But
that's
still
tbd
at
this
point
in
time.
B
C
Yeah,
so
the
election
officers
have
been
selected
and
confirmed
by
the
steering
committee.
They
have
drafted
a
schedule
that
is
awaiting
approval.
The
election
I
actually
started
writing
role,
documentation
for
the
election
officers.
C
This
is
something
that
we've
really
needed,
and
the
next
thing
is
to
actually
go
to
the
people
who
volunteered
to
be
the
election
sub
project
and
start
parceling
out
tasks.
C
I
just
have
not
had
a
chance
to
get
to
that
honestly.
I
would
have
launched
the
election
subproject
somewhat
later
this
year,
except
that
we
kind
of
needed
to
choose
election
officers.
So
the
there
is
a
bunch
of
stuff
to
do.
I
just
haven't
organized
it
and
and
of
course
other
people
don't
know
what
needs
to
be
done.
A
B
B
B
I'll
say,
like
you
know,
cloud
native
in
general
and
then
at
least
ideally
have
some
past
experience
with
code
of
conduct,
type
things,
but
nominations
for
that
are
still
open,
and
at
least
last
time
I
looked,
we
could
definitely
use
more
people.
If
you
know
people
that
would
be
potentially
interested.
B
A
B
We'll
pop
over
to
marketing
castle
is
not
around,
but
can
someone
else
potentially
give
an
update
on
that.
D
A
Have
anything
the
sick,
dog
spotlight
blog
was
out
this
week
and
there
is
another
spotlight
blog.
I
don't
know
it's
sick,
it
is
focused
on,
but
that
is
yet
to
come
out
rest.
Even
I
left
the
meet
last
meeting
early,
so
I
don't
have
much
updates.
Okay,.
C
C
C
A
B
Then
we'll
pop
over
to
contributor
docs,
no,
you
have
an
update
on
the
contributor
guide.
A
A
B
Eric
is
and
some
of
the
other
tech
critics
that
are
working
on
the
workshop
haven't
popped
on
this
call,
but
I
know
that
they
are
should
hopefully
have
a
draft
of
the
at
least
first
pass
at
the
workshop
soon-ish
or
replacement
for
the
new
computer
workshop
new
contributor
course
again.
Sorry
very,
very
tired.
Today.
B
And
that
actually
will
tie
in
slightly
to
you
actually,
if
we
pop
down
to
craig
your
open
item
on
code
spaces,
because
I
know
they
potentially
want
to
integrate
that
into
the
course
and
being
able
to
to
get
people
doing
stuff.
There.
E
B
Okay,
I
will
reach
out
to
them
later
today
and
try
and
do
a
follow-up.
B
I
want
to
wear
that
well
I'll,
like
do
like
start
group
dm
or
something
like
that
to
for
an
intro.
B
B
That's
right
cool,
then
that
will
take
us
back
down
to
our
open
mic
items
and
craig-
and
I
kind
of
touched
on
it
a
little
bit
a
moment
ago.
But
you
want
to
give
a
bigger
spiel
about
the
the
fun
stuff
you're
working
on.
E
Awesome
thanks
bob
yeah,
so
hi
everybody.
I
don't
know
how
many
I
know
a
lot
of
you,
but
not
everyone
actually
did
vibrato
and
I
met
this
morning
or
his
evening
earlier
to
talk
about
coach
bases
and
how
it
might
play
a
role
as
a
follow-on
to
the
now
defunct
catacota
work.
So
let
me
take
a
big
step
back
and
tell
you
what
I'm
doing
what
I'm
hoping
to
accomplish
and
some
ideas
for
how
we
might
proceed
so
I
joined
github
in
april.
E
I
am
a
product
manager
on
the
code,
spaces
team
focused
on
enabling
open
source
communities
to
get
the
absolute
most
out
of
cloud-based
developer
environments,
and
it's
amazing
to
get
paid
to
do
that.
It's
like
a
job
made
for
me
so
code
spaces
for
anyone
who
doesn't
know
yet
because
not
everybody
has
access
to
code
spaces.
Yet
that's
actually.
The
first
thing
I'm
working
on
fixing
is
making
sure
that
everybody
on
github
can
use
these
powerful
cloud-based
developer
environments.
What
is
a
cloud-based
developer
environment?
E
It
is
not
only
an
ide.
Currently,
the
default
is
vs
code,
but
we're
working
on
enabling
other
ides,
plus
all
of
the
configuration
of
the
tooling
for
those
ides
everything
from
customization
specific
to
a
repository.
So
you
may
have
specific
tools:
linters,
testing
and
tools.
Things
like
that
that
you
want
to
configure
and
personalization
like
how
what
extensions
for
vs
code
do
I
like,
and
how?
How
does
it
feel
like
it's
exactly
for
me
and
all
the
associated
runtimes?
E
All
of
that
is
packaged
up
in
a
customized
development
container,
so
we're
leveraging
the
same
underlying
technology.
The
visual
studio
code,
remote
development
works
on
we've,
worked
together
with
the
vs
code
team
to
out
open
source,
the
dev
container
spec
and
a
cli
implementation
of
that
and
we're
now
partnering
github,
together
with
the
vs
code
team,
we're
co-developing
it
now
and
we're
looking
for
other
people
to
take
advantage
of
that
same
spec.
And
so
that's
how
you
encode
all
the
customizations
that
you
want
for
this
development
environment,
and
so
what
you
get
out
of.
E
It
is
the
ability
to
put
into
a
repo
a
button
that
says
open
in
github
code
spaces
and
you
will
have
pre-built
a
container
with
all
of
your
dependencies
that
will
then
run
any
setup
scripts
as
it's
creating
and
so
within
a
minute
or
less.
You
can
have
a
fully
blown
kubernetes
inner
loop
kind
of
development
environment.
That's
running
not
on
your
local
machine.
E
You
can
connect
to
it
from
your
local
vs
code,
but
it's
running
in
the
cloud
managed
by
us
and
the
idea
is
to
have
transient
environments
that
automatically
clone
all
the
code
into
your
environment
and
then
you
can
just
get
it
started.
Coding,
run
your
tests
and
when
you're
ready
you
get
rid
of
it.
It's
done
and
you
all.
Your
work
is
persisted
in
the
repo
in
your
fork
in
your
branch,
wherever
it
is
you're
working.
E
So
there
are
a
couple
of
awesome
use
cases
that
in
talking
to
a
bunch
of
different
open
source
communities,
we've
identified,
so
one
is
the
new
contributor
experience.
So
I
come
to
kubernetes
and
I
start
reading
the
contributor
guide
and
I
am
lost
so
fast.
I
don't
know
about
you.
We've
we,
as
a
community
I've
been
a
part
of
this
for
years
too,
like
how
we've
done
a
lot
of
work
to
try
to
make
it
easy
to
approach.
E
E
Then,
as
a
maintainer,
I
have
to
maintain
a
set
of
environments
for
each
repo
and,
if
I'm
doing,
reviews
on
prs,
how
do
I
maintain
that?
That's
a
big
headache
for
all
of
us.
The
idea
is
code
space.
I
can
just
go
to
a
pr.
I
can
create
a
code
space
from
that
pr
click
space
pulls
in
all
the
dependencies
applies
the
commits
from
the
pr
to
my
repo.
I
can
both
review
the
code
and
test
the
code
in
this
environment.
That's
specially
set
up
for
doing
pr
reviews.
E
So
there's
a
couple
of
there's
a
lot
of
different
use
cases
that
I'm
really
excited
about.
I
don't
want
to
try
to
boil
the
ocean,
I'm
first
curious.
If
what
questions
there
are.
E
Second:
are
there
sort
of
practical
low-hanging
fruit
we've
identified
already
working
on
the
catacota?
Getting
people
started
kind
of
scenario
as
a
logical
one
and
de
barbata,
and
I
started
working
on
that
this
morning
or
his
evening
and
are
going
to
proceed
there,
but
I'm
also
interested
to
see
where
there
might
be
other
initiatives
that
I
could
get
involved
in
the
number
one
question
people
ask
is
well:
how
does
this
work
from
until
we
have
code
spaces
available
to
everyone
perspective
today
I
have
the
ability
to
make
everybody
who's.
E
Members
of
an
org,
a
github
org,
have
access
to
code
spaces
before
we
roll
it
out
to
everyone
else.
That
would
be
a
big
switch
to
flip
for
the
whole
kubernetes
org.
I'm
definitely
willing
to
do
that
and
all
of
the
support
and
everything
else
that
that
entails,
because
that
learning
is
you
know
nothing
is
perfect.
E
E
So
rich,
it
looks
like
you've
used
code
spaces,
probably
in
your
own
forks
and
prs
for
a
while
I'd
love
to
work
with
you.
You
should
love
to
learn
from
your
experience.
Doing
that
I've
just
done
the
basics
of
you,
know,
testing
build
and
build
works
great,
but
I
haven't
taken
it
a
whole
lot
further,
just
myself
yet.
D
I
can
say
I
love
it,
I
I
do
a
lot
of
work
from
an
ipad
and
I
use
codespaces
quite
frequently
and
we
have
it
turned
on
at
our
organization.
So
it's
also
very
good,
and
I
I
think
that
would
be
an
awesome
thing.
C
E
C
People
who
are
already
org
members
the
so
I
almost
think
if
it's
work
during
this
phase,
when
it's
only
open
to
a
group
that
it
might
actually
be
better
to
create
a
group,
something
called
like
kubernetes
learners
or
something,
and
then
have
people
sign
up.
E
I
agree:
that's
exactly
the
model
we've
used
for
workshops,
so
when
people
are
running
workshops,
we'll
have
them
create
a
an
org
set
up.
Repos
that
are
specifically
designed
for
those
workshops
enable
and
then
join
everybody.
Who
is
a
part
of
that
workshop
into
that
org,
and
that
way
it
becomes
a
very
smooth
experience.
B
We
do
have
the
contributor
playground
repo
for
people
to
test
new
pr's
and
things
like
that
against.
They
don't
work
members
at
least
to
interact
with
our
bots,
but
I
don't
know
if.
B
I
don't
think
that
would
be
a
problem
for
trying
to
get
people
to
try
like
doing
stuff
for
kk,
which
is
the
the
most
complicated
one
to
have
an
environment
and
do
everything
for.
C
Yeah,
well,
I
guess
that's
so,
but
that's
a
question
like
I
don't
know
how
this
a
group
assignment
and
sort
of
thing
work.
So
if
somebody's
in
the
group
I
can
still
use
code
spaces
against
one
of
my
own
forks
or
not.
E
So
the
yeah,
the
repo
needs
to
be
in
the
organization
which
has
access
yeah,
that's
going
to
make
that's
difficult
exactly
and
that's
what's
going
to
change
in
november,
when
I
can
release
this
to
everybody
on
the
planet,
we
just
have
a
lot
of
work
to
do
between
now
and
then
so
the
so.
Essentially,
the
challenge
is
we're
going
to
have
to
just
find
ways
to
do
if
this
makes
sense
and
people
for
people
are
interested
to
to
do
some
exploration
around.
E
We
would
kind
of
showcase
some
of
this
in
workshops
at
kubecon.
If
that
made
sense,
I
don't
know,
and
then,
when
we
turn
it
on
we'll
have
it
in
november
december,
then
everyone
will
have
this
great
experience
kind
of
all
set
up.
B
B
So
one
other
potential
idea,
since
we
do
have
a
lot
of
people
that
don't
necessarily
contribute
to
kk
proper
but
are
in
the
you
know
in
in
the
kubernetes
project,
would
be
to
like
send
something
out
to
kdev
or
ask
him
like
korea's
contributors,
because
there
there
are
probably
people
that
are
org
members
that
haven't
done
any
real
work
in
kk
that
might
be
able
to.
E
B
B
That
could
probably
be
a
good
sample
group
to
get
going
with
this
because
they
they
would
also
they
have.
At
least
you
know
some
experience
in
our
community,
so
they
might
be
able
to
be
able
to
provide
sort
of
at
least
a
bit
more
informed
feedback
and
still
get
that
some
somewhat
new
contributor
experience
in
terms
of
going
through
it.
E
E
We
can
use
the
organization
administration,
so
I
could
enable
code
spaces
for
the
kk
org
well
for
the
kubernetes
org,
and
then
we
could
essentially
enable
code
spaces
for
a
specific
set
of
people.
So
we
don't
open
the
floodgates
and
you
know
have
the
risk
of
some
people
having
a
bad
experience
and
that
way,
then
we
could
do
that.
I
I
just
need
you
know.
We.
D
Would
it
be
beneficial
to
create
personas,
send
an
email
to
kdeb
with
those
personas
saying
looking
for
volunteers
that
meet
these
personas?
You
have
sort
of,
I
would
say,
not
your
no
code
people,
but
there
are
some
individuals
that,
like
bob,
was
saying
that
don't
directly
work
on
kk
and
then
you
have
your
core
code,
people,
if
you
identify
those
and
then
just
maybe
throw
something
to
kkm,
you
may
get
some.
You
may
get
a
bunch
of
things
back
and
but
you'll
be
able
to
weed
through
them
a
little
bit
better.
E
So
yeah,
okay,
that
sounds
like
a
good.
A
E
Step
for
me
marky,
I
will
I'll
do
that.
I
would
appreciate
because
this
this
I
I
have
not
been
very
active
in
the
last
year.
Unfortunately,
I
was
distracted
with
a
startup
thing,
and-
and
so
I
would
appreciate-
maybe
if
one
of
y'all
is
kind
of
interested
in
pairing
with
me,
because
I
don't
know
what
kind
of
issues
and
activities
are
current.
That
would
benefit
everyone
unless
the
use
cases
I
described
are
resonate
with
everybody
right
off
the
bat.
D
E
B
Were
there
any
other
open
mic
items
that
potentially
weren't
in
the
docs
that
people
want
to
talk
about?
We
have
20
minutes
left.
D
And
I'd
like
to
see
if
everybody
is
okay,
with
adding
a
new
section
to
the
topics
that
we
cover
for
moderation,
and
maybe
we
and
I
gotta
work
sort
of
with
noah
code
ranger
kentowicz
on
this
to
just
to
make
sure
what
we'd
like
to
you
know
publicly
give
an
update
on
moderation,
things
and
but
I'd
like
to
add
a
section
on
there,
where
we
were
sort
of
capturing
that
in
a
you
know,
bi-weekly
cadence
or
even
a
monthly
cadence
moderation
side.
B
I
think
I
think
that's
that's
fine.
We
actually
probably
need
to
update
our
template
in
general,
because
there's
a
few
things
that
we
pretty
much
always
skip
or
the
the
people
aren't
necessarily
around
consistently
to
give
updates.
So.