►
Description
For more info see https://git.k8s.io/community/sig-docs
B
B
My
name
is
Celeste
I
am
leading
this
special
edition
of
Sig
docs
to
manage
the
1.2
or
4
removal
of
the
docker
shim
stuff
from
the
documentation
as
usual
code
kind
of
clients,
please
be
kind
to
each
other.
This
meeting
is
recorded
and
I
don't
know
if
the
intention
is
to
post
these
recordings
or
not,
and
we
are
not
keeping
notes,
because
this
is
kind
of
a
an
ad
hoc
thing.
B
C
Hey
hi
hi:
this
is
dobreta,
so
basically
I'm
part
of
the
release
team
I
am
a
com,
Shadow
also
I'm.
Writing
a
few
of
the
talks
for
this
talk
questionable
one.
So,
okay
as
part
of
the
last
meeting
also
but
I
joined
a
bit
late.
Okay,.
B
C
B
Cool
cool
anybody
else
on
the
call,
okay.
D
E
Yeah
hey
good
morning,
this
is
Mickey
I'm.
The
communications
coordinator
for
the
1.24
release,
so
I
was
on
last
week
as
well,
but
I
think
it
was
sort
of
as
an
introduction
to
make
sure
that
our
teams
can
work
together
as
as
needed
all.
B
Right,
cool,
okay,
I,
apparently
just
have
very
poor
memory,
so
I
apologize,
yeah.
D
And
I'm,
basically
new
into
the
release
process
and
I
just
came
to
know
about
the
docker
shim
removal
process
that
has
been
going
on
and.
D
Of
interested
like
what
is
going
on
in
this
meeting
so.
D
B
This
is
very
much
a
status
update
meeting
to
essentially
manage
the
many
many
moving
parts
around
removing
darker
shim
I
can
do
some
specific
handing
out
of
tasks
the
better
way
to
go
about.
That,
though,
is.
A
B
Switch
between
a
Mac
and
Windows
machine
for
like
gaming
and
for
like
work
and
I,
sometimes
forget
how
to
copy
and
paste
between
one
and
the
other
I've
been
just
there.
B
B
It's
the
copying
paste
that
always
gets
me
okay.
So
if
you
take
a
look
at
the
project
board,
your
best
bet
is
actually
to
claim,
particularly
in
the
pre
1.24
column,
any
good
first
issues
which
are
not
claimed
so
again
I
can
do
some
specific
handing
out
of
tasks
at
the
end
if
we
have
time,
but
that's
not
the
main
main
purpose
of
this
particular
meeting.
Okay,
okay,
any
questions.
B
Okay,
so
the
next
topic
on
our
non-existent
agenda-
because
we
do
not
have
notes-
is
I
actually
have
an
announcements
for
the
group
and
the
announcement
is
that
I
am
leaving
my
current
position
at
the
end
of
the
month.
The
Linux
Foundation,
so
I
have
accepted
a
new
position.
Hooray
me.
B
Unfortunately,
it
is
not
a
position
where
I
get
to
do
open
source
full-time,
not
hurray
me
and
I'm
a
little
upset
about
that,
but
it
is
what
it
is.
So
I
will
be
here
until
the
end
of
the
month,
which
does
not
give
us
a
lot
of
me
time.
B
Nate
and
I
probably
need
to
meet
up
about
what
that
handoff
looks
like,
but
I.
Imagine
that
some
amount
of
the
managing
of
all
this
is
going
to
fall
on
Nate.
B
B
So
that's
kind
of
the
end
line
that
I'm
running
for
so
if,
at
the
very
least,
if
I
leave
early,
there
is
an
accurate
list
of
everything
that
needs
to
be
done.
Any
questions.
B
Thank
you
so.
B
Just
to
give
you
a
little
bit
of
a
timeline
last
paid
day
is
end
of
January.
I
start
my
new
job
in
March
I
will
probably
I'm
debating
I.
Don't
like
the
idea
of
working
for
free.
That's
my
only
real
thing,
however:
I
don't
I
also
don't
like
the
idea
of
like
leaving
the
project
in
a
large,
and
there
is
a
month
between
when
I
start
the
new
gig
and
when
I
leave
this
gig
for
reasons,
if
I'm
also
relocating
I
am
moving
to
the
US
for
this
on
pandemic
times,.
G
B
I
will
attempt
to
poke
in
if
I
can
like
get
over
like
doing
the
same
work
for
free.
That
was
doing
for
pain
like
mental
obstacle
here,
because
I
also
just
really
hate
the
idea
of
how
the
high
projects
in
the
launch,
for
reasons
of
like
employment
contracts,
that
that
also
really
bothers
me.
So,
okay,
that's
my
statement.
I
will
probably
be
around
in
February.
F
B
B
All
right,
foreign.
B
Progress
done
last
week
on
assessing
continuing
issues
in
this
simply
because
I
was
busy
with
the
aforementioned
resigning
of
my
current
position.
B
To
these,
because
it
looks
like
Shannon,
the
lovely
Shannon
has
actually
updated.
Some
of
these
was
just
sweet,
so
this
actually
just
needs
to
be
broken
down
into
individual
issues
or
a
big
group
issue
to
actually
action
on
this
change.
So
this
is
actually
done,
even
though
it's
not
marked
as
done.
H
Sorry
in
terms
of
the
the
list,
the
the
okay,
sorry,
I,
didn't
see,
the
I
didn't
see
the
title
in
there,
the
yes,
it's
been
checked
and
there's
I,
think
four
pages
that
need
updating,
really
the
rest
of
them
are
mentions
of
of
Docker,
but
not
necessarily
in
a
way
that
is
problematic
for
us,
okay
and
I.
Think
I
agree
with
Tim's
suggestions
here,
so
I
would
I
would
make
the
point
that
Tim's
suggestions
are
probably
the
only
updates
that
need
to
be
done
at
this
point.
Okay,.
B
I
think
that
is
very,
very
reasonable,
and
thank
you
all
for
digging
into
that.
So
my
next
step
here
after
this
meeting
is
to
break
this
down
into
like
actual
issues
that
can
change
I.
B
So,
just
to
address
your
comment:
Tim
around
omitting
older
case
studies
from
the
index
of
case
studies,
that
is
a
bit
of
a
contentious
topic.
My
understanding
is
historically
and
I.
Don't
know
what
the
current
status
is,
but
historically
cncf
marketing
has
been
involved
in
that
pretty
heavily
and
by
involved
in
that
pretty
heavily
I
think
they
meet
I.
Think
they
drafted
like
most
of
the
initial
case
studies
I,
don't
know
that
they
currently
maintain
these
case
studies.
B
Issue
for
another
call,
the
tldr
is
I
suspect
somebody
would
get
very
upset
if
we
omitted
those.
It
may
not
be
the
fight
we're
looking
to
pick
right.
This
second
does
that
make
sense.
Okay,
all
right.
So
the
next
big
big
topic
is
I,
had
checked
the
blog
for
mentions
of
Docker
and
add
warning
labels.
B
B
Just
a
warning
that
automatically
pops
up
and
says
this
blog
post
is
older
than
a
year
proceed
with
caution
and
for
anything
that
directly
pertains
to
Docker
or
the
docker
shim
removal
within
the
past
year,
especially
we'll,
actually
go
back
and
update
those
posts
and
point
them
to
newer
posts
as
applicable,
because
those
are
things
that
people
are
going
to
start
googling
pretty
imminently:
I
nudged
Patrice
chalene
about
this,
who
is
another
technical
writer
who
works
with
myself
and
with
Nate
prior
to
the
break.
B
G
Questions
I
think
that
30936
maybe
split
out
the
warning
labels
into
its
own
issue.
B
And
actually,
this
is
already
done.
I
just
need
to
open
up
follow-up
issues
for
that.
So
that's,
okay
for
those
on
the
call
who
are
maybe
looking
for
like
a
task
to
pick
up
I
will
not
have
tasks
for
you
right
this
second
on
this
call
because
I
actually
need
to
go
through
these
issues
and
break
the
results
out
into
tasks.
But
if
you
go
to
sing.
B
If
you
go
to
Sig
doc,
stalker
shim
on
kubernetes
Slack,
probably
in
the
next
hour
or
two
I,
will
mess,
I
will
do
like
a
Mass
dump
of
issues
that
can
be
picked
up
and
actioned
on
and
updated.
B
I'll
try
to
cross
post
those
to
Sig
docs
as
well,
but
FYI.
That's
your
next
step,
if
you're
just
looking
to
pick
something
up.
Most
of
these
are
actually
going
to
be
pretty
good
first
issues.
B
The
beauty
of
this
work
is,
it
is
not
super
tactically
complex,
in
most
cases
at
least
as
far
as
the
documentation
updates
go
okay.
What
else
do
we
need
to
do
that?
Has
this
been
taking
on?
It
has
been
thank
you
Shannon,
and
he
opened
up
a
follow-up
issue:
you're
delightful,
okay,
sweet!
That's
what
we
like
to
see.
B
Wonderful
and
the
references
section
was
the
one
I
think
Tina
had
a
discussion
about
this
last
time:
Shannon
just
an
MVP,
but.
B
Yeah:
okay,
thank
you
for
picking
that
up.
Tim
I
appreciate
it
because
it
looks
like
we
are.
B
B
B
So
that's
that's
the
bulk
of
the
scary
work,
because
now
we
at
least
know
the
scale
of
the
problem
is
and
I
would
say.
The
scale
of
the
problem
is
solidly
a
medium
quantity
of
work
is
High,
difficulty
of
work
is
actually
I
would
say
low
to
medium,
and
really
we
just
need
to
continue
to
manage
our
moving
pieces.
To
get
this
all
done
is
how
I'm
feeling
about
it.
B
Okay,
so
I
think
I
have
some
follow-up
items
and
that
I
need
to
clean
up
this
board.
I
need
to
make
sure
that
each
of
the
actual
action
items
that
we
have
has
an
actual
task
attached
and
that
all
those
are
captured
on
the
board.
B
Aside
from
that,
I
think
that
sorts
out
our
our
things
that
need
to
be
done
within
the
course
of
this
release.
Tim
you've
got
a
cheeky
hand
up
just.
B
Okay,
let's
at
least
capture
the
the
done
ones
and
actually,
while
I'm
here.
B
This
I
need
to
camp
yeah.
This
probably
needs
to
be
categorized
you're
over
here.
G
B
B
Everything
in
this,
like
second
column
titled
1.24
release,
needs
to
happen
like
before
the
release
ends,
but
probably
a
little
later
in
the
cycle.
Release
Days,
release
day,
I
think
that's
pretty
self-explanatory,
and
then
there
are
probably
going
to
be
some
follow-up
on
things
that
we
have
that
need
to
happen
after
the
release.
B
G
B
That's
the
I
think
that's
the
distinction
that
I
wanted.
Thank
you
so
much
for
saying
that,
okay,
so
this
board
is
probably
gonna
get
massively
changed
in
the
next
two
hours.
B
Based
on
that
very
insightful
comment,
just
FYI,
if
you're
looking
at
us,
okay,
so
I
know
somebody
and
I
forget
who
mentioned
that
they
had
a
blog
post
out
for
peer
review.
Did
you
want
to
talk
about
that
briefly.
C
Yeah,
it's
me
it's
me
actually.
So
basically,
I
was
trying
out
the
things
myself
like
it
is
changing
from
processing
to
culturality.
So
that's
there
in
the
board.
It's
a
priority.
Important
too,
that
comes
under
that.
So
I
got
a
lot
of
reviews
and
I
was
trying
out
the
thing
myself
on
my
own
device.
How
does
it
work
so
I'll
be
completing
it
by
this
week,
like
no
the
whole
thing?
Okay,.
B
Just
as
a
question
who
asked
you
to
do
that
blog
post,
just
because
we
and
it's
not
it's
awesome
that
you
did
it
on
your
own.
I-
really
really
love
it.
But
this
is.
B
It
involves
a
lot
of
companies
who
are
a
little
bit
touchy,
so
we're
trying
we're
trying
to
like
not
step
on
any
toes,
which
means
that
we
sort
of
have
to
manage
blog
posts
or
media
releases,
and
we
need
to
manage
the
media
releases
really
well
and
I
know
that
cat
has
a
very
similar
blog
post
that
she
was
asked
specifically
to
write
for
a
whole
bunch
of
reasons
and
I.
Don't
I,
don't
want
there
to
be
I
just
want
to
make
sure
that
your
work's
not
going
to
go
to
waste.
C
So
it's
like
it's
more
of
a
technical
thing
like
it's
changing
or
talk
as
him
to
continuity.
So
it's
more
like
it
doesn't
involve
anything
anything
controversial
or
something.
D
C
Yeah,
it's
like
a
technical
documentation
only
which
is
part
of
you
know,
which
is
part
of
the
major
issue.
You
know
guide
to
shift
from
Docker
Sim
to
cryo
continuity
and
other
things.
It's
a
step-by-step
guide.
So
that's
it
it's
more
of
a
technical
part
rather
than
you
know:
okay,
okay,.
C
Yeah
that
that
beer
has
already
work
on
the
progress.
Okay,.
G
Blog
editor
here,
I
am
definitely
gonna.
Ask
cats
to
have
a
look
at
that
yeah.
B
I
think
that's
probably
a
good
idea
and,
like
maybe
in
the
end,
it
becomes
something
that
you
both
collaborate
on,
because
I
think
there's
actually
pretty
significant
overlap.
Which
is
why
I
wanted
to.
A
So
I'm
I'm
not
actually
all
that
territorial,
so
yeah,
so
it's
just
I
would
like
to
review
the
pr
sorry,
my
cat's
in
my
lap
and
she's.
It's
it's
early
and
she's
mouthy
about
it,
I'd
like
to
review
the
pr
and
where
I
can
I'll
just
avoid
overlapping
too
much
with
what's
already
written
or
maybe
if
it
gets
published.
First
I
can
reference
it
but
yeah.
Since
there
is
like
a
a
specific
GitHub
issue
for
the
thing.
B
Okay,
does
anybody
else
need
anything
from
me
on
this
call
in
the
next
five
minutes.
E
G
B
To
answer
your
question,
the
answer
is:
no:
it's
not
that
the
kubernetes
project
hasn't
deprecated
things
before
it's
just
that
Docker
shim,
very
specifically,
because
it's
of
its
relation
to
morantis
and
Dockers
companies
is
very
high
visibility,
and
this
is
a
learning
moment
for
the
project
in
terms
of
how
to
communicate
and
manage
deprecations
so
for
the
comms
team,
something
that
I
think
would
be
really
really
interesting
for
you
to
spend
some
early
release.
Cycles
on
right
now.
B
B
So
in
this
case,
container
D
is
the
suitable
alternative,
slash
upgrade
path,
and
then
you
have
to
communicate
that
change
in
a
slightly
more
empathetic
manner
to
people
which
is
a
part
of
what
we're
talking
about
with
these
blog
posts,
is
essentially
trying
to
explain
ourselves
to
our
users,
which
is
we
know,
we're
about
to
cause
you
a
bit
of
pain.
B
But
this
is
why
we
think
it's
the
best
viable
path
forward,
and
this
is
why
tulip
and
devarata's
blog
post
it
immediately
like
sent
up
a
bit
of
a
red
flag
because,
as
we
mentioned,
this
is
a
little
bit
larger
than
kubernetes
as
a
project
itself.
B
It
has
to
do
with
how
we
relate
to
Docker
publicly,
as
a
group
that
frankly
commands
a
lot
of
companies
that
command
a
lot
of
money.
B
So,
even
though
it
seems
like
a
pretty
innocence,
this
is
just
the
bare
bones
of
how
we
do
this
upgrade.
There
are
implications
to
quite
literally
everything
that
you
say
as
a
result.
B
For
example,
containerdy
is
not
the
only
cryo
runtime
yep,
it
is
the
preferred
crier
runtime
of
cloud
native
Computing,
Foundation,
Pro
and
related
projects
and
things
that
may
seem
innocent
to
you.
From
your
perspective,
for
example,
saying
oh
well,
it's
a
quick
and
easy
install
can
get
very,
very
Troublesome
from
the
perspective
of
a
media
Outlet,
because.
B
Super
fast
they
will
yeah
they'll,
seize
on
that
and
say
well,
the
kubernetes
project
doesn't
think
Docker
is
very
quick
or
easy.
They
think
it's
hard.
They
think
it's
difficult
and
very
specifically,
they'll
come
to
you
because
you're,
the
author
of
the
blog
post,
and
so
it
seems
like
we're
getting
a
little
worked
up,
we're
just
trying
to
save
you
from
a
particular
conversation
with
the
media
that
could
go
very
poorly
for
you,
for
your
company
and
for
the
project.
B
F
B
No,
but
he
would
care,
but
to
answer
Mickey's
question
I
think
it
would
be
really
really
cool
to
see.
Sig
release
have
a
slightly
more
documented
and
regular
process
for
announcing
deprecations
executing
on
deprecations
and
communicating
that,
like
every
deprecation
needs
its
own
blog
posts
that
goes
out
during
the
cycle.
The
release
cycle
before
that
deprecation
actually
hits
it
needs
certain.
Like
communication
with,
say
the
people
who
run
the
scenes
you
have
Twitter
account.
B
It
needs,
maybe
a
ping
to
see
in
CF
marketing
to
make
sure
that
when
you
speak
on
behalf
of
the
project,
you
don't
say
anything
that,
like
is
upsetting.
It
needs
communication
with
State
docs
to
make
sure
that
we
have
adequate
time
to
remove
the
thing
that
you're
deprecating
from
the
documentation
or
it
needs
an
analysis
before
you
announce
the
deprecation.
B
So
this
process
of
checking
through
the
documentation
that
we're
doing
right
now,
we
reasonably
could
have
done
like
a
few
months
ago,
but
say.
E
B
B
If
you
are
somebody
who
is
here
looking
for
a
task
go
to
Sig
dog
stalker
shim
on
slack
and
I
will
have
tasks
for
you
in
an
hour
or
two
and
in
the
meantime,
have
a
wonderful
rest
of
your
day
and
rest.
Your
weeks
Tim
can
we
get
cntf
marketing
to
drop
into
future
docs
dockershim
docs
call
solid.
Maybe
we
can
certainly
potentially
get
Amy
scarada
Perrin,
who
coordinates
project
services
to
drop
in
and
Amy.
B
Very
much
has
a
repulses
her
finger
on
this
one
like
pretty
much
every
time
we
have
one
of
these
meetings,
I
then
go
and
DM
Amy
with
exactly
what
happened.
So
again,
it's
very
much
being
watched
over
and
I
think.
This
is
also
a
learning
opportunity
for
the
cncf
that
occasionally
the
project
needs
to
be
reached
in
and
helped
out
in
a
particular
way,
and
this
is
maybe
also
something
for
Mickey's
documentation
on
deprecations.
B
That
needs
to
be
written
down,
and
you
can
absolutely
DM
me
about
this
Mickey,
which
is
when
the
project
needs
media
support
to
handle
a
particularly
difficult
deprecation,
who
is
their
contact
and
I
will
find
that
out?
For
you,
okay
sounds.