►
From YouTube: Working Group: 2021-09-02
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
All
right,
there's
still
some
people
not
signed
in,
but
you
know,
I'm
not
gonna.
Shame
you
so
we'll
move
forward.
Let's
see
any
introductions
new
faces.
B
A
Awesome
welcome
welcome
all
right,
thank
you
for
showing
up,
let's
see,
release,
planning
and
or
updates.
I
could
kind
of
kick
one
off
yesterday
we
went
ahead
and
released
an
rc
for
pack
o
21.
Oh,
I
believe,
and
so
right
now
we
are
kind
of
in
what
is
it
code
freeze
for
that
release,
but
yeah
if
you're
able
to
test
it
out,
see
if
there's
any
kinks
with
it
that
we
might
need
to
work
out
we're
planning
to
release
that
by
next
week,
wednesday.
C
Sure
I
can
speak
for
natalie.
I
guess
today
gearing
up
for
o120
release.
We
have
rcs
out,
as
you
know,
arm
support
and
cosine
usage
is
going
to
be
in
there.
So
we're
just
doing
a
little
bit
more
validation
on
there,
and
you
know
you
know
nothing's
nothing's
really
blocking
us.
You
know
once
we
have
our
acceptance
ready
to
go
we'll,
maybe
ship
the
next
one.
A
A
All
right,
moving
on
to
our
freestanding
items,
docker
desktop
implications.
Sam.
D
I
think
this
is
just
a
continuation
of
the
item
from
the
core
teams
like
yesterday.
Would
it
be
worth
creating
an
issue
or
something
on
our
back
repository
and
docs
repository
to
like
add
some
steps
or
examples
for
using
podman
or
something
else
with
back?
D
A
Who
what
extent
do
you
envision
this
going
into
like?
Is
it.
D
Statement,
I
think
we
can
just
say,
install
boardman
and
then,
if
there's
anything
else,
that
needs
to
be
done
to
make
back
compatible
with
it.
Those
steps
should
be
documented,
not
sure
if
they
were
like.
I
remember
there
was
this
issue
opened
a
while
ago
on
portland
support
where
you
had
to
do
a
few
extra
steps
to
get
back
working
with
partner,
not
sure
if
that's
still
the
case
or
that's
changed,.
A
Yeah,
I
don't,
I
don't
believe,
that's
the
case
any
longer.
I
think
there
was
a
fix
in
the
life
cycle
too,
to
improve
some
of
that
yeah
I
mean
the
minimal
right.
I
think
that
you're
asking
is
basically
just
it's
in
places
where
we
say,
install
docker
right
or
depend
on
docker
just
add
mentions
to
podman
as
well
right.
I
think
that
would
be
maybe
good
enough.
I
do
wonder
if
this
is
a
really
good
marketing
art
opportunity,
though,
for
us
to
create
a
blog
post.
A
That
says
you
know
this
is
how
you
use
pack
with
podman,
but
it
actually
goes
into
setting
up
podman
on
like
a
mac
or
something
like
that,
and
then
we
could
point
contributors
if
need
be
right,
that
again
run
into
the
sort
of
limitation
to
that
blog
post,
and
it's
kind
of
going
onto
this-
I
wouldn't
say
fanfare,
but
it's
going
on
with
the
kind
of
motion
of
what's
currently
happening.
A
Joe,
would
you
be
open
to
that
blog
post
idea?
Yeah?
Definitely
all
right!
I
might
take
a
swing
at
it.
I'm
terrible
at
writing.
So
you'll
have
to
be
a
very
good
copy
editor,
but
yeah.
B
I
would
love
a
blog
post.
We
literally
just
had
someone
in
our
pockets,
like
the
other
day
being
like
hey.
Have
you
guys
thought
about
trying
to
make
this
work
without
docker
so
being
able
to
point
something
at
them
saying?
Well,
actually
it
is
being
thought
about,
and
here's
some
stuff
would
be
super
excellent
yeah.
I
agree
anything
we
can
do
to
get
ahead
of
it.
Sort
of
cool.
A
I'll,
let
that
and
then
I
think
there
was
a
doc's
issue
for
introducing
odd
man
sam.
Do
you
want
to
take
care
of
that?
Second,
one.
A
Right,
yes,
I
think
that's
there's
like
a
bigger
question
right
of
like
what
does
this
docker
desktop.
A
Change
really
mean
for
the
project
as
a
whole,
and
we
were
talking
about
that
yesterday.
A
I'm
not
like
for
me
personally.
I
feel
like
it's
still
way
too
early
to
tell
like
I
felt
like
they've
made
decisions
in
the
past
that
then
they've
kind
of
backed
away
from
right,
like
the
registry
changes
where
I
think
they
were
going
to
put
a
harder
limit
on
the
dakota
and
then
they
eventually
kind
of
eased
off
on
it
a
little
bit.
If
I
remember
correctly,
so
I
do
wonder
if
something
similar
will
happen.
D
D
The
other
option
we
have
is
using
noid
coil,
which
is
sort
of
like
the
more
experimental
version
equivalent
of
docker,
which
also
ships
with
a
vm
utility
called
lima,
which
can
also
be
used
for
like
non
it
quietly
uses
like
you
could
also
use
it
with
portman
and
lima
seems
to
support
arm,
which
podman
currently
doesn't.
A
Yeah,
what
what
I
would
hate
to
do
really
is
kind
of
try
to
re-implement
the
functionality
of
virtualization
within
pack
which
I've
experimented
with,
and
it's
just
really
really
painful
and
there's
just
a
lot
to
take
into
consideration
as
far
as
maintenance
overhead.
So
if
we
could
delegate
that
aspect
to
other
existing
tools,
I
think
that
would
be
the
best
approach.
E
And
when
you
say
it
comes
with
podman,
you
mean
not
following
so
the
partner.
I
o
instructions.
B
A
B
A
A
E
I
I
feel
like
the
biggest
amp
is
the
thing
you
just
said,
javier,
which
is
the
vm
machine
setup,
at
least
from
what
I've
looked
into
so
far
at
work,
docker
machine.
If
any
of
this
stuff
is
based
on
docker
machine
like
that
has
been
in
maintenance
mode,
since
I
feel
like
a
few
years
ago,
2019
or
something
ever
since
basic
docker
moved
to
docker
desktop,
I
know
mini
cube,
also
uses
daca
machine,
there's,
basically
a
repo.
E
I
think
that
someone
made
of
basically
a
bunch
of
things
that
docker
abandoned
of
like
adapters
and
other
things
and
docker
machine
got
moved
up
under
there
and
in
the
maintenance
issue
on
the
daca
machine
repo.
E
There's
like
a
link
to
that
thing,
and
then
also
the
mini
cube
issue,
because
I
think
they
also
try
to
tackle
this
issue
as
well.
But
some
things
I
think
are
challenging
is
like,
I
think,
probably
the
proprietary
docker
desktop
stuff
is
a
little
better
from
what
I've
seen
from
what
the
issues
and
stuff
have
been
reported
of.
Just
dealing.
E
Of
hang
ups
around
that,
when
you're
kind
of
spinning
the
the
vm
up.
A
A
A
D
A
What
do
you
envision
when
we're
talking
about
the
life
cycle,
doing
image
signing.
D
I
am
open
to
either
it
was
just
a
matter
of
reimplementation.
I
guess
every
platform
at
some
point
will
have
to
implement
this,
so
might
make
sense
to
implement
it
in
the
life
cycle.
If
and
it
could
be
an
optional
thing
right
like
if
the
platform
wants
to
do
something
extra,
it
could
just
give
that
flag
not
provide
a
key
or
not
enable
cosine
support
and
lifecycle
will
publish
it
as
it
is.
D
If
you
pass
an
additional
flag,
you
don't
have
to
then
download
the
cosine
binary,
implement
the
signing
logic
as
a
separate
step,
possibly
useful
for
things
like
techdom
or
like.
D
A
Yeah
I
I
would
agree
that,
that's
what
came
to
my
mind
to
you
right.
It's
like
thinking
about
the
different
platforms
that
would
have
to
support
to
re-implement
it.
It
makes
more
sense
to
put
it
in
the
life
cycle,
although
it
does
feel
like
a
more
platform
specific
concern,
but
if
they
could
opt
out
and
then
do
like
again
if
they
want
to
like
mutate
it
right
after
the
fact
and
then
sign
it,
then
you
could
still
be
able
to
do
that.
C
C
A
C
That's
a
fair
question.
I
yeah,
you
know
I've
seen
capec
adopted.
You
know.
I
know
internally,
we've
been
talking
a
little
bit
more
about
it
too.
Yes,
my
my
worry
has
been
lessened.
A
So
I
do
wonder
if
that
plays
into
anything
on
the
road
map,
if
I'm
not
mistaken,
that
would
kind
of
fall
into
the
supply
chain.
Security.
D
A
E
No,
I
mean,
I
think,
basically,
what
anthony
said
was
probably
the
biggest.
I
think
thing
when
we
talked
about
this
like
a
year,
I
feel
like
it
was
a
year
ago.
E
It
was
a
while
back
and
it
just
wasn't
clear
and
then
I
think
when
we
talked
about
when
steven
brought
this
up
even
two
or
three
years
ago,
it
was
even
much
more
influx
and
I
think
people
weren't
a
big
fan
of
notary
or
something
or
he
wasn't
at
the
time
so
yeah
I
mean,
I
think
the
base
question
is
probably
which
can
get
sus
down
and
the
rfc
is
like
whether
we
actually
want
this
as
a
platform
level
feature
or
one
in
lifecycle
or
if
it's,
if
it's
in
lifecycle
like
if
people
don't
want
it,
is
it
like
an
extension
thing
like,
I
think,
that's
probably
a
lot
of
open
questions
and
I'd
be
curious.
E
Where
kind
of
people
stand
on
it,
but
overall,
I
think
it's
a
feature
we
probably
want
somewhere.
D
E
So
I
guess
when
it
you
say
it's
independent:
we
would
just
put
up
the
bomb
stuff.
We
already
have
if,
like
that,
if
we
went
and
implemented
that
today
and
that
other
one
was
not
finished,
being
implemented
or
something
right.
E
Oh
yeah
so
like
basically
even
in
that
other
one
like
if
people
are
doing
the
kind
of
build
pack
bomb
today
and
we
implemented
cosine,
you
would
just
upload
that
bomb.
As
for
that.
B
A
I
mean
I
know
that
this
is
maybe
a
little
bit
conflated
with
the
docker
desktop
right,
but
like
in
the
in
just
general
right
any
daemon,
whether
it
be
podman
or
docker.
D
A
D
A
A
Cool
all
right,
wait!
Isn't
that
never
mind
I'm
gonna
shut
up,
I'm
not
gonna,
go
too
far
into
the
weeds.
Just
gonna
ignore
ignore
me
all
right,
cool
anything
else
on
that
topic.
A
All
right,
it
seems
like
we
came
to
the
end
of
the
agenda.
Any
last
comments.