►
From YouTube: Kubernetes SIG Release Meeting 20200630
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
we
are
recording,
so
this
is
the
June
30th
2026
lease
meeting.
This
is
a
kubernetes
community
meeting.
We
adhere
to
the
kubernetes
code
of
conduct.
The
meeting
is
obviously
being
recorded
as
I
just
mentioned
and
we'll
be
posting
it
on
to
YouTube
a
little
bit
later.
So
please
be
mindful
of
the
code
of
conduct
and
be
good
collaborative
people
here.
A
A
B
A
A
A
Okay
and
release
engineering
for
folks
who
are
newer.
We
were
alternating
weeks
so
this
week
is
the
overarching
cig
discussion
and
in
the
alternating
weeks
we
have
a
focus
just
on
the
release.
Engineering
topics
so,
for
the
most
part,
I'll
leave
that.
But
we
have
one
mention
here
around
some
release:
notes,
fix-ups,
Adolfo
and
Sascha.
You
want
to
talk
about
the
the
process
that
we're
discussing
with
the
BSC.
For
that.
C
Because
I
can
just
give
in
short
introduction,
so
we
were
talking
about
some
possible
enhancements
to
the
release,
notes
and
the
process
at
all
and
because
we
had
an
ongoing
cap
and
this
cap
is
mostly
resolved.
We
have
Krell
release,
notes
and
some
other
tooling
around,
and
we
amended
many
many
enhancements
in
the
past
weeks
and
months
which
are
now
already
used
in
production.
Then
we
were
thinking
about
how
we
can
improve
the
overall
process.
D
D
Okay,
can
you
see
it
now?
Yes,
yep
okay,
so
let
me
start
by
I'm
gonna
generate
the
release,
notes
for
version
1
18.1
here,
because
I
want
to
show
something
and
that
release.
That's
actually.
So
this
is
our
standard
release.
Notes
for
that
much
version
which
has
around
I,
don't
know
Sony
or
so
changes,
and
the
idea
here
is
that,
for
example,
we
don't.
Let's
say
that
we
want
to
change
things
before
code
phrase,
for
example,
I
was
thinking,
and
maybe
we
instituted
a
policy
of
not
allowing
things
like,
for
example,
here
in
this.
D
So
the
idea
is
that
we
can
create
mapping
files
with
the
release
enough
information
to
change
that,
before
the
actual,
without
needing
the
actual
PR
to
be
changed.
And
so
what
would
be
is
now
we
created
this
cause
of
your
file
of
mapping
file,
which
asks
all
of
the
all
of
the
release
note
information
in
there
and
you
can
change
anything
any
any
of
the
fields
if
you
want
so,
for
example,
I
want
to
change
LP.
D
D
Can
just
I
can
just
save
that
piece
of
information
and
then
do
regenerate
the
they
release
notes,
taking
into
account
all
of
those
mapping
files
that
I
can
which
I
can
use
to
modify
information
so
I,
we
have
added
a
new
flag
to
the
release,
notes
tool,
which
is
this
one
here
not
from
what
should
currently
reads
a
directory
in
such
such
as
for
all
the
yamo
files
that
it
finds
in
there.
Looking
for
this
this
part
in
here
and
if
I
run
that
and
really
generate
the
notes,
it
should.
D
D
Okay,
so
maybe
the
next
one
will
work
so
the
first
one
is
just
updating
a
note
information
before
and
having
being
able
to
change
information
before
the
release
cycle
is
up
and,
and
then
there's
the
next
part,
which
is.
C
Until
the
release
has
been
cut
and
usually
we
would
have
a
chance
to
actually
solve
the
same
issue
the
same
way,
but
we
would
have
the
need
for
adding
additional
information
and
additional
fields
like
the
scoring
of
the
CVE,
the
overall
impact
resolution
and
sort
of
information,
and
that
way
we
had
idea
to
enhance
the
format
not
only
to
be
able
to
map
release
notes
from
a
to
b,
but
also
to
add
some
further.
Maybe
security,
related
information.
D
D
D
So
it
has
these
reliefs
note
that
such
reduce
fam
events
during
a
volume
operation
error
which
it's
it
says
that,
because
the
the
since
it's
been
fixed
out
in
the
open,
they
put
another
release
note
in
there
and
another
so
that
they
can
put
up
the
code,
but
the
actual
vulnerability
is
not
shown
to
the
public.
So
the
idea
is
that
we
can
produce
this
sort
of
files
here
that
we
can
patch
the
notes
with
new,
with
with
a
new
text
which
shows
more
of
a
more
relevant
information.
D
So
this
here
is
I'm,
changing
the
text
to
implement
the
changes
to
mitigate
that
vulnerability
and
then
I'm.
Changing
the
author
to
the
product
security
comedy
I
mean
this
is
just
a
like
it
sampled
to
demonstrate
the
thing
and
then,
if
you
see
here,
I'm,
adding
a
new
we're,
adding
new
information
to
the
release
notes.
This
is
a
data
field
and
which
is
a
actually
CV
information
to
the
release.
Notes.
D
That's
like
the
proper
title,
the
rating,
the
score
that
it
was
published
and
the
link
PRS
were
where
the
vulnerability
was
fixed
and
assured
the
ball.
I
mean
this
is
the
actual
description
that
that
the
security
committee
published.
So
the
idea
here
is
that
I
should
be
able
to
trust
in
my
code
anymore,
though.
The
idea
here
is
that
I
should
be
able
to
rerun
that
and.
D
Okay,
so
if
I
run
this
one
here
and
I
read
regenerate
the
notes
for
that
revision,
that's
if
it
works
now
should
pick
up
that
information
and
okay.
This
one
did
work,
so
it
added
the
information
of
the
of
the
CV
vulnerability
right
here.
So
it's
like
a
a
modification
to
the
template.
We
used
to
generate
the
release,
notes
and
now
it
includes
all
the
information
and
what
what
so
I
can
have
any
of
these
nothing's
mapping
sources
to
to
be
able
to
read
from
any
sources.
A
A
Let's
change
them
to
load,
balancer
be
more
descriptive
for
for
folks
and
spreads
Fred
the
work
out
to
be
more
more
of
a
team
on
it
more
broadly,
but
then,
especially
that
frees
us
up
at
the
last
minute
to
deal
with
the
emergencies
instead
of
all
the
standard
stuff
and
the
emergency
case
of
a
security
issue
as
a
as
a
key
one,
and
this
is
a
huge
amount
of
nice
flexibility.
The
another
really
nice
benefit
that
we
never
had
before.
A
In
that
regard,
is
we'd
slap
the
thing
in
it
get
committed
somewhere,
github
it
get
updated,
we'd
run
the
tool.
It
would
reap
the
thing
this
you
can
put
those
mapping
files
locally,
see
what
they're
gonna
look
like
what
they're
gonna
render
like
we've
had
all
sorts
of
weird
little
rendering
issues
or
a
long
message
gets
truncated
or
indentions.
A
Weird
like
this,
you
can
know
that
that
that
leading
header
that
highlights
the
security
issues
is
gonna,
render
nicely
and
I'll
just
tested
locally
on
your
machine
push
that
yam
will
file
and
go
and-
and
we
know
that
we've
got
good
release.
Notes
like
the
this
is
for
everybody
on
the
call
this
pattern
of
testability
is
huge
is
something
we
basically
had
almost
none
of
a
couple
years
ago
and
as
we're
slowly
nibbling
away
on
each
of
these
points
to
to
have
more
testability,
it's
it's
making
things
so
much
more,
reliable
and
and
safe.
A
It's
not
everything
doesn't
become
run
it
in
production.
Thank
you.
This
is.
This
is
great
work
and
the
the
meta
issue
here
to
also,
though
one
thing
I
want
to
mention,
like
a
lot
of
people
have
said,
like
release
notes,
let's
just
automate
that
away,
but
this
highlights
exactly
why
you
can't
do
that.
There's
humans
involve
there's
choices.
Is
we
have
a
few
thousand
PRS
and
any
release?
What
was
mentioned
for
the
release?
A
Note
might
not
be
super
human,
readable
or
comprehensible
or
is
as
accessible
to
the
reader
as
we
might
desire
to
be
really
really
helping
the
broad
community
base
out,
as
they
read
them.
So
this
getting
the
tools
in
place
to
automate
the
automatable
parts
but
allow
the
humans
to
focus
on
making
something,
that's
really
readable
and
high-quality.
That's
where
I
think
we
drive
a
special
value
instead
of
people
just
saying,
like
automate
those
release,
people
away,
that
they
see
that,
like
we're,
actually
doing
a
human
curatorial
task.
That
adds
a
lot
of
value.
A
So
speaking
of
release
team
next
sub
project
is
release
team.
It
was
that
Taylor,
who
is
typing
a
little
bit
of
updates
in
on
that
absolutely.
E
So
how
do
you
everybody,
happy
Tuesday
I?
Think
it
is
so
we
are
eight
weeks
away
from
release
week,
I
how
everything
is
going.
We
have
a
couple
Reds
a
couple
yellows
a
couple
of
greens.
You
know
all
throughout
our
sis
updates
we
had
yesterday,
but
nothing
too
concerning
we
Stephan
myself
and
Jeremy
were
talking
late
last
night
because
we
got
on
the
topic
of
cherry
picks
and
kind
of
some
of
the
modifications
that
we've
done
in
this
release
cycle.
I
know
there
have
been
quite
a
few.
E
One
of
them
was
around
fast
forwards
and
cherry
picks
and
kind
of
what
the
1.20
release
will
look
like
going
forward.
We're
going
to
be
opening
that
up
we're
noodling
that
right
now,
but
it
looks
like
August
6th,
it's
gonna
be
when
that
is
opened
up
again.
I
put
some
notes
into
the
agenda.
Basically,
the
thought
was
fast
forwards
until
rc2.
E
Everything
else
is
cherry
picks,
which
is
about
one
week
of
fast
forwards
and
three
weeks
of
tricks
and
have
merge
restrictions
for
roughly
a
month
from
could
freeze
branch
cut
to
cherry
pick
deadline
so
we're
going
to
be
getting
some
text
together
in
that
front
and
then
sending
that
out
to
UK
dev
sig
release
and
a
couple
other
deals
on
that
front.
But
overall,
looking
good,
very
excited
to
see
us
getting
closer
to
release
and
very
excited
about
cube
con
as
well.
But
any
any
questions
on
that
front.
E
A
Something
dementia,
Stephen
and
I
were
were
wondering
about
shifting
over
to
go
115
and
we
sent
an
email.
We
just
looked
like
I
get
hub,
/
golang
/
go
if
you
tunnel
into
their
releases,
they
have
like.
You,
can
see
the
names
of
the
people
who
have
committed
the
releases,
so
we
understand
email
to
them.
Yesterday,
like
hey,
what's
up
with
go
115,
we've
heard
it
might
be
coming
soon.
Historically,
it's
been
August,
maybe
into
September,
and
they
did.
Let
us
know
that
it's
at
its
earliest.
It
will
be
August
1st,
so
that
yeah.
E
A
We
were,
we
were
kind
of
hoping,
like
maybe
hey
Co
vid,
they
they
dialed
back
there,
their
content
and
okay,
it's
into
June
they're.
Finding
the
project
done.
Ci
is
green,
let's
just
ship
it
early,
but
they
said,
and
they
had
actually
quoted
what
somewhere
in
there,
their
public
release
documents
that
they
never
release
early,
which
is
interesting
to
know,
and
they
also
said
if
we
frequently
release
late.
So
we
will
have
to
figure
out
what
we
do.
A
A
We
probably
aren't
gonna
want
to
switch
to
go
115
the
week
or
two
before
release,
but
we've
got
a
month
basically
to
kind
of
set
up
CI
and
get
some
signal
and
make
some
choices,
whether
we
we
aim
for
the
one
19.1
in
September
or
if
it
feels
like
the
risk,
is
contained
and
CI
is
showing
good,
but
we'll
have
to
we'll
have
to
figure
that
out
on
the
fly
in
the
next
month.
Two
months
absolutely.
F
Hey
I,
don't
have
any
major
a
place
for
today,
other
than
that
I'll
be
giving
the
status
update
tomorrow
and
for
the
first
time,
and
so
I
have
to
have
to
reach
out
to
Dan
I,
don't
know
how
he
does
it.
It's
a
big
job
and
it's
a
little
bit
daunting,
but
he'll
be
doing
that
tomorrow
and
we've
a
few
changes
and
coming
in
on
CI
infrastructure
that
we're
expecting
to
and
think
some
jobs
and
so
I'll
give
detailed
reports
on
that
tomorrow.
F
A
F
A
G
E
G
H
Their
selves
should
folks
use
should
be
provide.
Some
images
and
I
have
gotten
response
that
we
should
see
with
signaled
and
I'm,
going
to
send
an
email
to
both
signals
in
series
upcoming
days
to
bring
up
this
topic
because
deems
told
me
that
the
running
cubelet
in
containers
is
deprecated.
So,
let's
see
a
little
bit
so
to
get
a
formal
response
from
signaled
and
then
we
can
see
if
there
is
anything
we
can
do
about
this.
So
that's
mostly
it
from
that.
I
have
forgot
to
add
edit
section,
but
there's.
A
We
don't
have
a
quality
decision-making
process
around
this
type
of
thing.
It's
been
a
recurring
question
across
all
the
artifacts
which
of
the
binaries,
which
the
RPMs
debs,
which
of
the
containers
should
we
be
making.
What
should
their
contents
be,
how
how
broad
or
narrow
and
how
many
different
variations
and
they,
whether
supported
or
deprecated,
not
supported
or
sort
of
hobby
wise
best
case
available?
We've
we've
not
had
a
serious
matrix
of
commitment
and
and
backing
for
that.
A
So
yeah
I'm
really
curious
on
this
one,
because
it's
sig
knowed
what
preferences
they
have
and
and
if
there's
any
technical
concerns
that
they
have
like
what
it
what's
the
rationale
for
it
being
deprecated.
Was
it
or
the
benefits
of
hypercube?
Are
there
things
that
we're
just
not
aware
of
so
yeah
that
it'd
be
a
really
interesting
email
thread
to
start.
H
A
I
I
I
You
so,
as
you
see,
we
have,
we
have
a
lot
of
jobs
for
Canaries
perform
and
also
we
have
created
as
some
some
conformance
test
jobs
or
arm
platform
pay
see
the
for
the
three
links
here
we
can
use
could
be
addameer
and
the
cops
to
deploy
performance.
Tester
cast
and
pace
see
that
testing
result
here.
I
Also,
we
we
create
some
jobs
to
choose,
as
we
thought
about
the
kind
or
our
platform
and
integration
and
another
complements.
So
we
want
to
know
if
we
want
to
later.
The
committee
to
announcement
announces
that
the
community
had
already
inches
for
the
arm,
so
how
many
cats
are
there?
Also,
we
have
discussed
about
this
question
with
us
with
some
some
Kunis
vanilla
members,
such
as
bun-buns,
adder
and
Tim's.
A
So
is
another
area
where
I
feel
like
the
project
doesn't
have
the
best
of
decision-making
process
from
a
cig
release
perspective
we're
generally
a
trailing
indicator
of
support.
To
now,
let's
say,
support
sort
of
in
air
quotes
maybe
with
a
lowercase
s
instead
of
a
capital
S.
We
we
don't
have
the
strongest
concept
of
what
it
means
to
support
something
as
a
project
globally.
So
from
a
sig
release
perspective,
what
we
try
to
do
is
understand
what
the
project's
commitment
is,
how
how
broadly
folks
are
committed
to
making
sure
something
is
maintained.
A
There's
a
lot
of
diversity
and
potential
systems
out
there
and
any
developer
in
the
project
could
make
a
code
change
somewhere.
That
is
built
on
their
internal
biases,
for
example,
to
Linux
and
x86
or
xat
664,
even
and
certain
platform
assumptions.
So
we
we
need
to
make
sure
that,
for
the
platforms
we
are
intending
to
support,
the
developers
understand
generally
how
not
to
accidentally
break
them.
A
What
are
the
quirks
or
differences
on
those
platforms
and
then
that
there
are
some
key
people
who
understand
and
watch
for
these
things
that
the
test
coverage
is
sufficient
and
that
they
get
quickly
fixed?
So
certainly
a
first
step
in
all
of
that
I
think
is
getting
the
test
grid
data
there
so
that
people
can
see
it
having
a
board
for
signo,
darm,
64
I
think
is
really
important.
A
The
the
the
way
that
I've
been
pushing
on
this
is
to
try
to
get
this
being
discussed
at
sick
node,
specifically
and
at
cig
architecture,
because
there
one
sig
note
is
going
to
be
the
the
subject
matter.
Experts
set
to
people
who
could
kind
of
give
the
the
green
light
or
the
thumbs
up
and
say
like
yeah.
We
believe
that
this
is
as
healthy.
It's
ready
it's
sufficiently
supported
and
then
it's
an
architecture
level.
That's
the
first
place
where
I
would
see
things
going
broadly.
A
Are
the
key
architect
sort
of
people
broadly
across
the
project,
feeling
that
all
of
the
things
for
some
fuzzy
definition
of
that
are
present
so
I
I
would
be
looking
to
them
from
a
cigarette
lease
perspective.
To
say
these
things
that
are
in
there
in
tester,
it
may
be
from
an
informational
perspective.
Are
they
ready
to
move
towards
a
a
release,
blocking
criteria,
and
that
takes
a
little
bit
bigger
conversation?
So
I
think
it's
great
that
you've
had
some
discussion
with
with
them's
and
then
I'm
curious.
I
A
I'm,
just
trying
to
pull
up
the
cig
architecture
meeting
last
week
was
going
to
talk
about
some
of
this
architecture
stuff
and
didn't
because
the
the
that
jinda
was
really
full,
so
I'm
just
looking
to
see
if
that
got
pushed
to
a
next
meeting,
it
doesn't
look
like
the
agenda.
There
has
been
updated
yet
and
let
me
just
confirm
when
their
next
meeting
is.
A
Note
yeah,
okay,
that
sounds
right
for
Signet.
Sick
architecture
is
every
other
Thursday
at
11:00,
Pacific
or
1800
UTC.
So
let
me
just
Seconal
paste
pasting
this
into
the
zoom
chat.
The
link
for
cig
architecture
and
I'll
also
link.
A
A
So
the
over
the
last
month
we've
been
having
some
initial
discussions
with
some
people
from
illumos,
which
is
kind
of
the
the
follow
on
to
open,
solaris
and
they're,
looking
to
try
to
figure
out
how
they
could
get
support
with
kubernetes
and
containerization
on
their
platform.
So
we
have
kind
of
a
multi-dimensional
array
between
initially
Linux
and
Mac,
OS
and
Windows
and
potentially
other
operating
systems,
and
then
all
of
the
hardware
architectures
are
their
specific
operating
systems
that
you're
intending
to
support.
At
this
point,
beyond
Linux.
A
Then
that
kind
of
kind
of
makes
sense
we
again
kind
of
going
back
to
as
a
project.
We
don't
have
a
clear
policy.
Linux
obviously,
is
the
first
place,
I
think
or
something
came
for
a
hardware
architecture
without
linux
support,
I,
think
that
would
feel
slightly
weird
at
this
point,
but
beyond
Linux,
the
other
things
start
becoming
a
little
more
niche
and
it's
it's
unclear
to
what
extent
we
would
expect
everything
to
be
supported
on
all
platforms.
A
There's
been
some
past
discussion
about
wanting
to
make
Windows
for
sure
a
first-class
citizen
and
have
things
equally
supported,
but
that
also
depends
on
having
official,
stable,
builds
of
the
OS
on
the
platform
and
I.
Don't
know
the
current
status
of
that
from
Microsoft
I
feel
like
they
they've
done
things
in
the
past,
but
I
don't
know
where
support
stands
much
less
around
the
cloud
side
of
things.
A
You
so
I
I
appreciate
you
coming
to
us.
I
think
we
might
be
sort
of
the
later
part
of
the
required
conversations,
but
it's
good
for
maybe
to
start
here
that
we
can
point
to
the
other
places
and
then
we
also
start
tracking
the
conversations
I'm
curious
to
I'll
try
to
attend
the
sig
note
meeting
and
I'm
I
need
to
ping
the
sig
arch
people
to
see
if
they
are
gonna
circle
back
around
they're
talking
about
a
Lumos
this
week
and
and
see
if
they
would
also
discuss
arm
there
as
well.
A
So
I
think
we
can.
We
kind
of
carry
the
conversation
on
to
the
next
level
and
locations
and
then
kind
of
be
cycling
back,
but
I
I
think
I
would
think
from
what
I'm
seeing
you're,
probably
getting
close
to
at
least
being
useful
to
to
possibly
have
in
a
release
informing
sort
of
state
what
that
would
mean
for
us
as
we
we
try
to
watch
that
from
a
release
perspective
and
and
if
there's
issues
we'll
we'll
spend
some
initial
time,
triaging
back
to
the
proper
owners
and
and
see
like,
is
this
a
major
issue?
A
Yeah
sort
of
two
weeks-
maybe
although
it
yeah
it's,
it's
variable
the
dates
on
which
they
run.
Maybe
that's
a
question
then,
are
the
are
the
periodic
supposed
to
run
on
a
timer?
Are
they
more
manual
or
what's
the
trigger
because
they
go
from
the
June
15th
to
17th
to
23rd
to
24th,
so
it's
kind
of
kind
of
gapi
like
and
it
may
be
meta.
A
K
High
themes,
actually,
the
testes
were
stable,
but
it's
wrong
in
our
virtual
machine
and
the
gap
is
because
way
to
another
tests
on
the
host.
So
it's
broke
the
Internet
in
way
M.
So
the
ho
test
stopped
so,
but
there
is
only
four
tested
there
I
think
now,
but
before
that
the
test
is
quite
stable
and
the
pure
Reddick
is
is
about
one
day.
We
do
one
test
yeah,
but
we
can
make
it
more
frequent.
K
A
A
L
So,
in
sequence,
lifecycle,
we
are
already
aware
that
arm
works
with
our
tools.
Like
cops
cube
again,
we
already
know
that,
because
we
had
user
reports,
but
we
highly
appreciate
this
new
signal
that
we
are
going
to
get
because
of
course,
we
cannot
claim
that
our
tools
work
if
we
don't
have
a
stay
signal.
So
thank
you
very
much
for
this
effort.
B
B
A
B
B
A
Okay,
any
other
things
of
folks
on
this
front.
I'll
take
the
action
item
to
reach
out
to
sig
arch
about
the
this
arch
distro
discussion.
If
see,
if
we
can
get
it
on
the
agenda
for
Thursday
I,
don't
know
if
I
have
a
way
specifically
to
reach
out
to
the
arm
folks,
but
I
can
are
y'all
on
slack
like
in
in
sig,
node
or
somewhere.
If
I
wanted
to
bring
you
yeah.
A
A
Thanks
for
coming
to
us,
I
think
like
like
Loomer,
says:
I
think
this
would
be
great
too
to
be
able
to
announce
that
we
have
additional
better
test
signal
and
for
that
to
lead
out
into
something
more
than
what
we've
already
had
for
initial
support
to
start
formalizing,
something
bigger
than
that.
If,
if
we're
ready
for
it
technically.
J
Good
morning
party
people
good
afternoon
good
evening,
the
final
PR
was
merge
yesterday
evening.
I
believe-
and
we
just
have
to
do
a
few
updates
on
our
end.
Arnott
was
here,
but
he
had
to
drop
I.
Think
the
last
piece
that
we're
doing
it's
just
some
DNS
tweaking
and
then
we
will
be
live
so
I
just
wanted
to
give
a
quick
update
on
that.
J
J
For
me,
dumb
question
on
my
part:
nope,
not
dumb,
I
already
covered
the
dumb
part,
I,
probably.
A
J
J
A
Was
gonna
get
some,
so
my
name
is
relatively
unique
in
English
like
there's,
not
that
many
Tim's,
but
somehow
on
the
kubernetes
project.
There
are
a
ton
of
Tim's,
so
I
was
I,
was
gonna,
get
some
shirts
made
that
were
a
cig,
Tim
shirt
for
kube
Khan,
but
I,
don't
think
we're
ever
gonna
physically
see
each
other
anytime
soon,
and
so
that
the
sick
Tim
is
still
stuck
in
the
formation
phases.
J
A
Okay,
thank
you.
Now
we've
got
people
from
all
over
the
planet,
and
ours
are
sick
updates
and
things
coming
up
at
the
middle
of
middle
end
of
August
for
cube,
convert
xual
EU
as
something
we'll
want
to
make
sure
we're
getting
recorded.
I
forget
who
all
had
signed
up
for
those
I
know:
we've
got
it
somewhere
in
the
minutes,
and
Steven
is
also
on
top
of
that
I
think.
But
if
you
somebody
people
on
the
call
were
the
ones
who
are
gonna
do
our
our
cig
sessions
for
cube
con.
You
should
have
gotten
some
notification.
A
I.
Think
this
week
about
pre
recording
I
had
seen
some
chatter
that
those
were
going
out.
I
haven't
seen
it
like
the
specific
details
on
what's
being
requested,
but
there's
something
something
that
you
you're
supposed
to
do
to
record
and
upload
your
video
ahead
of
time,
just
to
make
sure
that
things
work
and
then
I'm
actually
kind
of
partly
attending
this
week.
The
open
source
summit
North
America,
which
is
a
Linux
Foundation
conference,
and
it's
my
first
time
in
a
virtual
event,
and
it's
unusual.
It's
different,
I'm
curious.