►
From YouTube: Flatcar Container Linux community meeting
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
A
Welcome
to
the
live
chat.
Well,
it
seems
like
we
have
one.
B
A
A
A
A
I
don't
see
too
many
of
them,
so
I'll
just
take
the
stage
so
hi,
I'm
danielle,
I'm
the
community
manager
program
manager
at
microsoft,
slash
kinfolk
for
flat
car,
so
yeah
that
and
been
around
for
a
couple
of
years
now
here
in
folk
and
quite
excited
to
live
my
own
first
stream
here
so
yeah.
I
give
it
now
to
perhaps,
let's
start
with
the
guests.
So
how
about
you
mark?
You
want
to
take
the
stage.
D
Sure
thing
mark
peake,
I'm
a
principal
engineer
at
vmware
and
then
just
wanted
to
drop
in
and
see
what
the
community
was
like
here.
D
E
Hi
everybody
I'm
joseph
animal,
I'm
with
adobe.
I
know
pilo
because
we
talked
probably
just
about
a
week
ago
just
coming
in.
I
know
we
we've
been
using
five
car
for
a
while.
I've
also
been
a
friend
of
andy
randall,
so
always
have
a
big
love
for
the
company
and
just
here,
because
I
just
we
had
so
much
stuff
that
we've
been
sharing
feedback
wise
and
just
felt
like
we're
overdue
to
start
contributing
more
to
the
community.
C
Thanks
for
joining
joseph,
I
have
an
agenda
item
just
for
you
today.
I.
C
F
G
H
Absolutely
my
name
is
william:
I'm
on
the
flat
card
team
at
microsoft
based
in
rotterdam.
It's
a
lovely
almost
sunny
day
here,
matthieu
hello,
mature
from
the
flat
car
team
two
and
I'm
based
in
france.
H
C
Hey
I'm
tilo,
I
am
a
manager
of
microsoft
and
I
work
with
the
flatcar
container
linux
team
and
I
have
a
one
spotlight
item
today,
which
is
the
c
group's
v2
experiences
that
we've
made.
I
think
tony
you
just
joined,
can
you
say
quick,
hello.
J
Hi,
my
name
is
tony
goslin,
I'm
also
coming
from
adobe.
I
work
with
joseph
sandoval,
so
hi
everybody
hey
there.
C
So
we
have
a
slight
change
in
the
like
how
we
approach
this
meeting.
It
felt
a
little
too
top
down
regarding
just
having
everyone
stare
at
slides.
So
what
we
wanted
to
do
is
one
of
us
will
share
the
screen
and
not
talk
and
just
basically
edit
the
agenda
that
we
have
as
a
github
discussion
and
we'll
use
it
as
as
kind
of
the
the
meeting
minutes
as
well.
C
So
I'm
volunteering
to
type
today,
if
someone
can
take
over
typing,
when
I'm
doing
the
secrets,
you
do
stuff
and
hand
back
to
danielle.
A
Okay,
I
could
take
over
typing
I'm
a
bit
nervous
to
share
that,
because
I'm
dyslexic
and
then
just
like
sharing
life
would
be
a
bit
embarrassing,
but
fine.
So
I'll
do
that
part.
But
how
about
someone
else
sharing
then
the
screen,
because
I'm
honestly
quite
embarrassed
about.
C
It
no
that's!
Okay,
I'll!
I
can't
share
my
screen:
wait
a
second
and
I'll
I'll
type,
most
of
the
time
and
then
just
hand
off
to
you
for
the
c
group
v2
stuff.
I've
noticed
recently
that
I
really
can't
speak
and
type
at
the
same
time.
It's
a
personal
weakness.
C
A
Yeah
so
last
weekend
on
friday,
we
had
our
first
smashing
day,
which
was
quite
exciting.
We
smashed
quite
a
lot
of
bugs.
I
mean
I
think
it
was
close
to
40
that
we
had
and
if
we
scroll
a
bit
down,
I
kind
of
pulled
a
list
of
everything
that
we
closed
in
the
last
month.
So
you
can
see
their
case
issues
open
versus
the
issue
closed
and
there's
quite
an
extensive
list
there
so
like.
If
you
open
the
discussions,
there's
like
one
of
the
comments
there
it's
like
issues
closed.
A
A
If
you
want
to
join
like
that
or
join
us
at
metrics,
because
we
kind
of
shared
throughout
the
day,
yeah
there's
also
nine
hours
recording.
I
guess
if
someone
really
interested
to
see
that
it's
out
there
yeah
and
we'll
announce
the
next
date
pretty
soon
yeah,
so
community
issues
that's
for
january
february,
I
guess
it's
kind
of
covered
there.
I
didn't
put
up
the
numbers
exactly,
but
you
can
see
they
said
at
least.
A
That
was
quite
an
extensive
effort
on
the
team
there,
so
I
think
I'll
hand
it
to
someone
more
technical
than
me
to
kind
of
go
through
the
extensive
effort
that
was
required
there
to
to
get
it.
I
So
yeah,
I
can
just
talk
about
the
release
itself,
but
I
won't
deep
dive
into
the
implementation,
but
basically,
in
this
release
of
cluster
api,
there
is
the
ignition
support.
So
it
was
a
long
year
and
it's
been
a
while,
since
we
started
to
work
on
it
to
work
on
it
so
yeah.
This
is
pretty
cool
and
citing
in
the
community
security
ecosystem,
but
yeah
I
wanted
diver.
I
didn't
do
the
implementation
itself.
G
Yeah,
but
maybe
for
context,
so
this
unlocks
flat
car
support,
for
example,
there's
a
pull
request
for
an
aws
for
the
you
know,
for
the
azure
provider
and
also
for
the
aws
provider
to
end
this
yeah
also
work
for
the
vmware
provider
to
have
them
support,
provisioning
flat
car
and
that
needs
ignition
user
data
instead
of
cloud
and
user
data,
which
is
the
default.
A
And
just
for
the
background,
I
think
it
was
half
a
year
to
to
get
this
pull
request
getting
through
and
I
think
the
list
just
a
list
of
reviewers
that
was
on
this
pull
request
was
longer
than
my
seven
in
the
19
each
screen
so
and
I
think
it
was
like
four
thousand
style
end
of
code
or
something
in
that
neighborhood,
so
yeah.
It
was
a
quite
extensive
work
that
the
team
required
to
to
get
it.
A
We
were
expecting
it
to
go
to
better,
but
it
was
actually
released
so
part
of
cluster
api,
so
that
was
very,
very
exciting
for
all
of
us,
yeah.
C
Just
a
tiny
addition
to
the
to
the
vmware
pr
in
particular,
that
is
still
a
little
work
in
progress,
but
we
are
doing
some
broader
upstream
work
there,
as
well,
so
as
a
as
a
basis
for
that
pr.
We
require
cluster
api
v110
because
of
the
ignition
bootstrap
provider
that
that
went
in
there
and
we
are
we're
helping
the
foreign
provider
open
source
project
to
upgrade
to
that
version.
So
it's
it's
some
broader
work
that
is
happening
there
and
it's
all
in
progress
and
aws
are
discussed
to
be
merged.
A
Goody,
so
I
think
the
next
item
is
one
of
the
spotlights
item,
which
is
the
v2.
A
C
Yeah,
that
is
that
is
me,
so
I
will
update
the
discussion,
so
you
can
edit
and
stop
sharing
my
screen.
A
Okay
and
you
trust
me
that
I
edited
it
and
then
after
some
editing
of
my
spelling.
C
I
misspelled
vmware.
Please
fix
thanks
mark
good
catch.
C
All
right,
let
me
let
me
check
my
notes
here.
So
it's
quite
a
journey
with
c
groups.
V2
right
on
the
on
the
outside.
C
It
took
us
a
while
to
build
everything
in.
We
were
always
aiming
for
like
a
seamless
upgrade
path
and
we
were
always
aiming
to
not
disrupt
existing
workloads
that
rely
on
c
groups
v1,
and
it
spent
quite
some
time
in
alpha
until
we
thought
it
was
feature
complete
and
then
it
spent
a
few
weeks
in
beta.
C
We
made
a
few
announcements
around
that
and
at
some
point
in
late
november,
we
felt
it
was
time
to
move
it
to
stable,
to
make
it
the
default
for
new
provisionings,
so
mainstream
docker
had
upgraded
to
v2
support,
kubernetes,
widely
supported
v2
and
several
distributions,
which
we
all
look
at
and
use
in
our
private
time,
as
well,
have
already
switched
to
using
v2
as
a
defaults.
We
thought
the
world
is
ready
and
it's
about
time.
C
We
didn't
want
to
break
existing
workloads.
So
all
instances
that
use
the
the
flat
car
auto
upgrade
feature
would
remain
on
c
group
v1.
You
would
basically
test
respective
kernel
parameter.
That's
also
read
by
systemd,
so
there's
no
interference
and
the
thing
that
we
did
not
account
for
is-
and
that's
that's
an
interesting
learning
item
for
us
there's
a
number
of
of
cluster
operators
who
upgrade
their
operating
system
by
just
recycling
the
instance
and
redeploying,
basically,
a
rolling
upgrade
kind
of
the
green
grass
approach.
C
That
is
actually
pretty
common
with
kubernetes
operators.
Now
that
wasn't
fully
on
our
radar
and
we
did
not
account
for
for
workloads
that
relied
on
legacy
c
groups
features
and
not
very
not
easily
to
upgrade
to
the
new
version.
So.
C
The
thing
that
we
did
is
we
looked
a
lot
of
the
we
looked
a
lot
to
how
people
were
applying
and
using
beta.
He
kind
of
overestimated
the
the
coverage
of
beta
across
all
scenarios.
So
we
know
that
many
users
pull
and
install
beta.
We
do
not.
We
did
not
realize
or
factor
in
that
it
is
not
equally
used
across
all
scenarios.
So
that's
a
learning
there
as
well.
C
After
the
upgrade,
we
received
reports
from
a
number
of
users
who
were
blocked,
upgrading
their
their
stable
series
to
the
newer
version,
because
testing
showed
that
their
workloads
kind
of
didn't.
Take
the
the
c
group
c
to
upgrade
very
well
so
since
it's
already
possible
to
configure
flat
car
right
now,
even
after
you've,
provisioned
a
freshly
provisioned,
an
entirely
new
major
stable
to
use
c-groups
v1
we're
just
investigating
currently
to
provide
the
same
to
to
freshly
deployed
instances.
C
Now
the
the
thing
that
works
today
is
you
can
provision
an
instance
and
then
you
have
to
interact
with
the
instance
to
tell
it
no
no
you're
supposed
to
use
c
groups
v1,
and
it
requires
a
one-time
reboot
after
provisioning,
so
that
ran
into
some
issues
with
the
provisioning
automation
that
some
flat
car
users
use
and
we're
now
investigating
making
the
v1
usage
a
provision
time
option.
C
This
is
sufficiently
complicated,
because
for
that
we
need
to
look
at
the
ignition
data
that
the
flat
car
instance
was
provisioned
with
now,
when
we
look
at
the
ignition
data
we're
already
in
user
space,
systemd
is
already
running
and
systemd
is
our
c
group's
manager.
So
systemd
needs
to
be
restarted
in
a
safe
way
to
switch
back
to
c
groups
v1,
and
all
of
that
is
possible.
I'm
just
saying
that
we're
very
careful
because
we
don't.
C
We
don't
want
to
break
things
by
just
providing
this
option
and
that
this
is
actually
presenting
itself
as
one
of
the
viable
paths
forward.
There's
another
option,
which
is
more
brute
force
and
a
lot
simpler,
and
that
is
just
issuing
two
distinct
images:
one
using
c
groups
v2
and
the
other
using
c
groups
we
want.
By
default.
C
We
currently
have
a
little
helper
script,
that
is
in
a
gist
on
github
that
can
take
an
image
as
an
input
and
it
will
just
make
it
do
c
groups
v1
as
like
a
short
time
workaround.
So
if
there
is
a
inter,
if
there's
an
immediate
urge
for
the
next
weeks,
then
that
may
also
be
an
option
in
any
case,
we're
looking
at
the
options
to
give
users
the
freedom
to
make
instances
use
c
groups.
We
wanted
provisioning
time
while
it's
not
part
of
the
current
release,
which
is
actually
ongoing.
C
While
we
are
speaking,
we
aim
to
include
it
in
the
next
release
by
mid
or
end
february.
So
that's
something
that
we're
consolidating
we're
testing
and
then
that'll
be
included.
We
understand
that
some
of
the
users
are
having
some
pressure
here
and
we're
going
to
address
that,
and
so
there's
a
number
of
learnings
that
we
had
during
this
whole
scenario.
C
So
for
for
the
flat
card
team,
we
just
learned
about
one
new
scenario
that
we
need
to
consider
when
people
just
you
know,
upgrade
in
general,
and
so
we
need
to
kind
of
think
out
of
the
box
when
we
have
breaking
changes
like
that
in
the
future,
and
even
more
improve
our
communication
and
double
down
on
the
community
communication
side
there
as
well,
because
it
turns
out
some
of
our
users
just
missed
the
message
and
that
is
partially
on
us,
like
we
could
have
beaten
the
drum
a
little
louder
in
general.
C
C
It's
fully
tested
multiple
times
as
as
far
as
we
can
test,
and
it's
the
point
in
time
where
we
need
to
understand
where
this
new
release
works.
With
your
use
case.
Beta
is
also
a
good,
a
good
point
in
time
to
get
back
to
us
and
stop
us
from
releasing
that
to
stable
before
it
hits
all
of
your
of
your
clusters,
and
we
will
always
listen
to
users
when
we
break
their
use
cases.
So
that's
that's
kind
of
the
summary
that
the
flat
card
team
took
from
that.
E
So
even
though
they
say
they
support
it,
a
lot
of
things
are
broken
or
not
or
not,
fully
functional.
When
you
skip
from
like
version
121,
even
to
version
124
they're,
even
advising
us
like
hey,
can
you
help
with
some
of
this
to
validate?
So
I
think
that's
where
some
of
the
disconnect
kind
of
happened,
and
I
would
assume
that
the
majority
of
people
using
flat
car
are
probably
running
kubernetes.
E
On
top,
I
know,
there's
probably
some
other
ones
who
are
not,
but
I
think
I
I
would
assume
at
least
half
are
so
I
just
think
that's
something
to
kind
of
weigh
in
aside
from
us
as
a
community.
You
need
to
need
to
really
work
at
providing
testing
out
and
coming
in
early
so
that
we
help
steer
the
direction.
But
this
is
just
more
my
looking
back
and
retrospecting
on
how
this
kind
of
got
to
where
we're
at.
C
That
is
excellent
feedback.
Thank
you.
C
G
Yeah,
no,
it's
just
more
about
this
general
topic
of
having
yeah
kernel
parameters
configured
through
ignition,
which
is
a
bit
difficult.
So
with
ignition
v3,
that's
a
planned
update.
Coming
later
this
year
there
will
be
some
mechanism
that
allows
to
define
the
kernel
parameters
in.
G
And
then
it
will
issue
a
reboot
to
match
the
expected
kernel
parameters
like
for
in
some
cases
we
can
skip
the
reboot,
for
example.
Now
this
c
group
trick
would
be
possible
to
skip
the
reboot
but
yeah
in
all
cases,
it's
not
possible.
So
that
was
something
that
we
like
to
have
until
now,
an
easy
way
to
say.
I
want
to
have
these
kernel
parameters
and
I
don't
have
to
like
find
my
own
tricks
on
when
to
reboot.
It
will
do
it
for
you,
then
yeah.
So
it's
not
there
yet,
but
it's
something
upcoming.
C
That's
actually
good
news
in
general
ignition
v3
support
matthew
has
been
working
hard
on
that.
Maybe
you
can
just
you
know,
distract
a
little
and
you
wanna
share
something
on
your
work.
Matthew.
I
Yes,
still
working
on
this
upgrade
there's
a
couple
of
elements
to
take
into
account
because
it's
not
only
upgrading
a
software.
We
also
ensure
background
compatibility
with
ignition
d2.
That's
why
we
don't
just
upgrade
to
upgrade
b3.
We
try
to
find
some
mechanism
to
preserve
compatibility
with
over
with
existing
infrastructure.
I
Currently,
the
statues
is,
we
have
only
two
remaining
failing
tests
in
pre-mu
providers,
so
this
is
really
encouraging,
but
we
need
also
to
deal
with
other
mechanisms
like
coding,
support
and
so
on
so
yeah.
It's
it's
it's
in
progress
for
sure,
but
yeah
and
it
should
be
landed
soon
into
alpha
and
yeah.
Let's
hop
to
to
a
bit
sooner.
C
I'm
very
glad
you
brought
up
the
the
backwards
compatibility
part.
So
that's
what
takes
the
most
time
on
our
end,
to
make
sure
all
the
v2
workloads
work
with
v3
as
well,
and
I'm
not
aware
of
any
any
other
distro
that
uses
ignition.
That
kind
of
supports
that.
C
That's
pretty
much
my
c
groups
v2
the
the
c
groups,
v2
speech,
if
prepared.
Thank
you
dani
for
taking
notes
how
about
we
go
with
someone
else
for
the
foster
party.
I
don't
want
to
ever
keep.
I
don't
want
to
keep
talking
any
volunteers
from
the
team.
Folks.
I
I
So
basically,
we
gave
five
talks,
which
are
recalled
correctly
around
factor
and
and
sorry,
and
we
got
two
of
them
outside
of
the
distribution,
the
rooms
and
the
other
one
into
the
distribution
day
rooms.
I
I
It
was
a
big
overview
and
we
got
deeper
into
the
test,
defining
how
we
write
actual
tests
with
a
flat
car
and
yeah
fun
story
around
that,
but
with
the
fosdem
with
this
edition,
all
talks
are
pre-recorded
and
fosdem.
Forks
got
some
issue
with
infrastructure
ever
sunday
in
the
morning.
So
I've
been
asked
to
do
my
talk
in
live
so
yeah.
That
was
a
pretty
exciting
to
go,
live
but
yeah.
So
it
was
cool
event.
I've
been
to
other
talks
about
java,
open
gdk,
been
to
one
about
the
nemo
mobile,
so
yeah.
B
Sure
so
I
I
gave
a
talk
on
on
how
to
secure
and
hardnet
container
host
and
we
shared
basic
tips
on,
or
rather
like,
the
tools
that
you
can
use
to
secure
the
container
hosts,
not
just
flat
card,
but
others
as
well
other
than
that
I
was
mostly
in
the
dev
distributions
dev
room,
because
I
was
one
of
the
person
volunteering
for
it
and
other
than
that.
I
was
also
like.
We
had
a
couple
of
talks
in
other
rooms
like
stock.
B
It
was
in
infrastructure,
one
and
then
theta
stock,
which
was
in
the
containers
one.
So
those
are
the
talks
that
I
attended
and
it
was
it
was
fun
and
good
knowledge
acquired
over
the
weekend.
Okay,.
G
G
If
you
don't
want
to
throw
away
the
full
machine
but
kind
of
keep
the
your
data
on
the
disk
for
various
reasons,
yeah,
there's
no
good
mechanism
right
now
and
I'm
trying
to
introduce
some
os
reset
functionality
and
made
proof
of
proof
of
concept
there
to
be
able
to
like
update
your
ignition
data,
and
then
it
results
in
some
configuration
update
on
the
machine,
discarding
old
config
state,
while
still
keeping
your,
I
don't,
know
important
app
data
that
we
want
to
have
cached
there
on
the
node.
C
Yeah,
maybe
if
you
want
to.
C
Checking
what
they
actually,
what
actually
did
yeah?
I
had
two
talks.
One
was
extremely
tight
because
I
had
a
30
minute
slot
and
the
pre-recording
went
for
29
minutes
and
41
seconds.
C
That's
about
building
your
custom
operating
system
image,
and
I
recommend,
if
you
want
to
start
flat
car
development
or
are
interested
in
how
to
extend
the
operating
system
image
from
sources.
I
recommend
this
talk
because
it
just
walks
you
through
the
whole
process
and
it
fits
within
30
minutes.
C
I
I
C
A
Cool,
I
think
that
sums
up
on
the
weekends
event,
so
yeah
the
release
planning.
So
maybe
back
to
you,
son,.
B
Yeah
I
lost,
I
lost
the
window,
but
yeah
yeah.
Is
it
visible.
B
Yeah
yeah
so
as
discussed
in
the
last
meeting.
So
this
time
we
are
planning
like
the.
Let
me
give
you
an
update
of
the
current
release,
so
we
are
doing
a
alpha
beta,
stable
release.
Let
me
edit
this
wait.
Oh
okay,
I'll
edit
it
this
one.
So
this
should
not
be
lts.
We
are
not
doing
an
lts
for
this
one,
but.
B
Yeah,
so
for
the
current
releases,
we
are
almost
done,
the
tesla's
green.
We
have
one.
We
have
one
flaky
test
which
should
be
here
on
the
it's
not
but
yeah.
So
we
have
a
flicky
test
that
was
there
so
other
than
that.
We
are
green.
So
tomorrow,
we'll
start
off
with
the
release
process
and
the
release
would
be
out
tomorrow.
So
that's
the
current
status
and
for
the
next
release
of
the
next
release
is
planned
in
three
weeks.
B
This
is
because
we
usually
have
the
release
planning
and
the
next
week
we
do
the
releases
and
due
to
the
holiday
christmas
holidays,
we,
the
cadence,
was
a
bit
broken,
so
just
to
fix
it.
We
are
doing
the
release
towards
the
end
of
february,
so
the
next
date
is
20th
of
feb
28th
of
february
and
yeah.
So
the
team
has
been
mostly
busy
working
on
a
couple
of
items
and
the
the
package
updates
have
taken
a
bit
of
a
tool
there,
so
we
have
added.
B
So
a
lot
of
them,
which
was
there
in
progress,
continues
to
be
there
in
the
in
progress
state
for
the
next
one
as
well.
We
did
much
a
couple
of
them
in
the
last
release,
so
we,
the
ones
that
were
immersed,
are
in
in
the
planned
section
of
the
seventh
february
release,
which
is
the
on
current
one
and
moving
back
to
the
next
one.
So
so
20th
february
with
the
next
would
be
the
next
one
and
then
in
the
backlog.
B
We
have
a
couple
of
the
outdated
packages
so
in
the
next-
and
we
hope
like
in
this
video
is,
we
can
close
all
of
those
backlogs
as
well
now
coming
back
to
the
next
next
one.
So
the
release
after
the
20th
of
february
would
be
on
14th
of
march
back
to
the
regular
cadence
and
we
have
a
triage
section.
B
So
these
are
the
list
of
packages
which
are
outdated
and
has
not
been
updated
in
a
long
time,
but
we
need
to
see
like
if
they
need
an
update
or
not,
and
what
are
the
complications
that
are
there
like
try
tools.
One
comment:
I've
mentioned
it
there,
like
the
current
binary
size,
is
increased
a
lot.
So
we
need
to
see
how
we
can
banish
the
update
there.
B
So
similarly,
we
go
through
all
the
packages
and
we
as
we
try
as
this,
we
move
them
to
the
backlog
and
and
then
into
the
in
progress
state
as
it
goes
so
folks,
if
you
are
joining
in,
if
you
want
to
contribute
to
a
flat
card,
this
is
a
good
place
to
start
working
on.
We
are
there
on
matrix
to
help
you
out
and
yeah
now,
moving
into
the
in
progress
section
we
have
the
systemd
250
like
resume
has
been
working
on
it
and
there
have
been
a
few
blockers.
B
So
it's
still
in
in
progress.
State
dongsu
has
been
working
on
the
gcc
update
to
10,
so
that
is
also
a
big
pier,
but
then
we
should
be
done
by
this
current,
like
the
28th
february
release
and
so
skye
started
working
on
the
cdm
issue,
and
so
I
have
added
that
guy
to
the
in
progress
and.
B
Yeah,
so
other
than
that,
I
did
not
find
any
other
thing
that
needed
to
be
added
added
to
in
progress.
So
folks,
if
you
are
working,
please
add
it
to
the
in
progress.
B
One
now
for
the
discussion,
I
have
added
a
couple
of
issues
so
for
from
these
from
the
next
releases
I'll
start
to
pick
up
now
that
we
have
done
a
good
buck
triage
the
box
matching
day,
so
a
good
number
of
bugs
has
come
on
to
the
radar,
so
I
start
putting
them
into
the
release
planning
as
well.
So
I
think,
like
these,
two
issues
can
be
like.
B
We
did
some
progress
on
the
missing
gcp
images,
so
we
did
some
progress
there,
but
we
can
probably
end
this
over
in
the
next
release
and
then
triage
the
slow,
gcp
connection
thing.
Does
this
sound
good.
C
This
sounds
excellent
and
it
kind
of
implies
that
people
can
enjoy
the
release
planning
and
bring
up
their
their
favorite
bugs
that's
cool.
B
I'll
take
that
as
a
no
for
now,
but
if
you
want
to
you,
can
always
like
communicate
to
folks
over
in
the
matrix
channel,
and
we
can
update
the
updated
to
the
planning
section
and
I
also
added
the
bpf
tool
dongsukai.
B
B
One
minute
yeah
flat
car,
so
this
is
this-
is
good,
probably
go
to
demo.
But-
and
already
we
mentioned
this,
but.
B
We
have
a
good
number
of
good.
First
issues
like
you
have
a
big
big
list.
So,
if
you're
looking
to
contribute,
we
have
a
huge
number
of
good
first
issues
that
can
be
attended
so
yeah.
That's
all
for
my
side
over
to
it
or
daniel.
A
Yeah,
I
think
we're
pretty
much
at
the
end
of
the
agenda,
so
just
like
want
to
open
the
stage.
If
anyone
wants
to
bring
some
topics,
I
got
some
questions
or
just
want
to
share
their
favorite
netflix
serious
lately.
I
don't
know.