►
From YouTube: Working Group: 2022-10-18
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
A
All
right,
I'm
sharing
here
again
a
link
to
the
agenda
notes.
If
you
want
to
ask
any
question
or
start
a
discussion
topic,
please
feel
free
to
edit
the
last
section
of
the
agenda,
and
let
me
share
my
screen:
real,
quick,
okay,
all
right,
also
yeah
I.
Consider
adding
yourself
to
the
attendees
list,
including
your
affiliation.
A
A
A
Mainly
in
implementing
accepted
proposals,
but
again,
if
there
is
any
idea
you
may
have-
and
you
consider
writing
an
RFC,
please
feel
free
to
do
it.
A
There
are
some
updates
and
the
RFC
in
the
proposal
to
donate
kpac
to
the
cloud
native
buildbacks
project.
A
If
you
want
to
chime
in
or
add
anything
that
will
be
interesting
and
in
our
related
note,
there's
also
a
discussion
to
extend
governance
for
the
potential
donation,
so
that
will
mean
creating
the
component
maintainer
role,
also
a
very
active
discussion
in
the
proposal,
and
you
can
see
Jan's
comments
there.
That's
great!
A
A
Moving
on
to
the
next
one,
there's
a
project
of
the
I
had
at
least
two
of
them
and
not
sure.
If
anyone
else
would
like
to
share
anything
else,
but
first
one
will
again
next
week's
cubecon.
We
are
one
week
away
from
the
cloud.
Foundry
Day
will
happen.
October
25th,
the
links
are
in
previous
sessions,
notes
links
for
for
the
sessions
that
the
maintenance
team
are
presenting
there,
one
from
Ryan
Safi
and
what's
new
with
potato
build
packs
and
one
more.
A
This
is
a
lighting
talk
from
Timothy
and
remote
debugging
of
Darkness
apps
and
in
the
cubecon
North
America
schedule.
We
also
have
a
session
from
Frankie
and
Sophie
around
s-bombs,
very
hot
topic
right
now,
so,
if
you're
attending
whether
virtually
or
physically,
we
will
encourage
you
to
attend
these
sessions.
They
will
be
also
office
hours
space
from
the
project
and
there
will
be
a
cloud
fund
reboot
a
viewer
attending
again,
whether
in
person
or
virtually
in
the
expo
hall
or
I,
don't
know
how
it's
called
these
here.
A
There
will
be
a
cloud
Foundry,
Foundation
Boot
and
you
will
find
their
maintainers
from
the
packet
of
build
packs
project.
You
can
ask
questions,
get
the
conversation
started
there
so
be
awesome
to
meet
you
there,
all
right
and
finally,
users
survey
results
are
in
I
share
what
what
I
think
is
a
a
bit
of
preliminary
analysis
and
data
first
thing
that
I
need
to
say
is.
Thank
you.
Thank
you
to
all
the
users
community.
A
Yeah
sorry
I
think
all
the
community
members
Who
provided
feedback
this
week,
you'll
receive
a
message
through
the
instructions
to
get
your
well-deserved
swag.
A
So
some
of
the
findings
here
and
I
I
plan
to
expand
this
material
with
with
the
whole
set
of
responses
from
the
community,
but
right
now
this
is
what
we
can
see.
The
commentation
seems
to
be
the
one
number
one
Learning
Resource,
so
every
effort
we
put
into
making
it
even
greater
will
be
well
received
by
the
user.
Community
right
second
place
is
video.
Tutorials,
probably
there's
some
work
to
do
on
that
front,
but
the
number
one
resource
is
still
documentation
for
learning,
but
not
so
much
for
troubleshooting.
A
Because
kind
of
the
message
here
in
the
summary
of
of
most
of
the
responses
is
that
when,
when
everything
works
as
intended,
documentation
is
easy
to
follow,
and-
and
you
know
it
has
this
logical
sequence
of
steps
and
it's
fine,
but
but
sometimes
when
something
fails
or
where
the
user
intends
to
do
something
a
bit
different
from
the
intended
use
case.
A
Documentation
seems
to
be
lagging
so
user.
Community
finds
this
slack
workspace
really
useful.
A
Try
to
problems
I'm
having
some
audio
issues
here.
Why
well?
This
is
Bittersweet.
I
mean
it's,
it's
great,
that
our
users
find
quick
responses
from
from
the
maintainer
scene
and
from
other
community
members
on
Slack.
That's
great,
but
probably
you
will
need
to
put
more
effort
into
troubleshooting
resources
available
right
there
in
the
documentation.
A
A
A
Probably
is
not
exactly
covered
right
now
in
the
docs
I
have
to
say
that
some
of
the
users
recognize
how
much
the
docs
have
improved
over
time,
but
some
of
them
have,
you
know,
need
to
go
to
the
CMB
website
and
some
other
resources
to
understand
how
things
work,
and
especially,
why
or
some
of
the
design
decisions
that
are
already
present
in
the
project
and
in,
for
example,
to
understand
to
have
a
single
and
place
to
find
out
which
versions
of
languages
and
tools
are
supported,
which
makes
a
lot
of
sense.
A
A
This
was
a
great
one
or
an
interesting
one.
White
potato
versus
oral
other
build
pack
implementations.
A
Immunity
was
a
common
reason
on
most
of
the
responses,
which
is
great,
I
mean
kudos
to
you
all
who
make
this
an
active
community
and
friendly
responsive
community.
So
that's
really
helpful.
Thank
you.
That's
it's
the
demonstration
that
sometimes
it's
mainly
the
non-technical
part,
which
makes
a
community
successful
a
project
successful,
so
the
the
support
for
many
languages.
The
broad
the
broader
support
is
also
a
big
reason
to
choose
pick
it
over
all
our
implementations
and
some
nice
extra
features
right.
A
So
that's
interesting
and
while
the
number
one
feature
request,
build
artifacts
other
than
oecia
oci
images,
something
around
specifying
dependencies
on
the
Fly
and
arm.
B
A
Tackle
right,
so
this
is
just
an
excerpt
of
the
feedback
that
the
users
provided.
I
will
be
extending
the
the
content
here
in
the
slides.
The
link
is
there,
so
you
will
be
able
to
read
the
the
whole
content
of
all
the
responses
in
the
survey.
A
Is
there
yeah
the
action
items
on
this?
The
goal
is
to
turn
this
into
issues,
so
we
can
continue
discussion
there
and
see
how
we
can
prioritize
and
put
some
time
and
effort
on
improving
what
needs
to
be
improved.
A
So
you
will
see
that
in
the
coming
days,
is
there
any
comment
around
these
updates?
Sorry,
yeah
yeah,
please
there's.
C
Like
the
the
qualitative
feedback,
I
guess
is
definitely
worth
to
put
in
issues
and
start
discussion
there,
but
the
quantitative
feedback,
it's
quite
a
just
like
what
was
it
11
people
participating.
C
Maybe
we
should
rather
draw
a
conclusion
to
find
out
how
we
can
actually
get
more
people
to
participate
or
or
whatever,
that's
maybe
the
main
thing
I
wouldn't
derive
anything
in
terms
of.
We
now
need
to
shift
any
things
into
documentation
or
troubleshooting
guides
just
based
on
on
these
numbers,
because
they
don't
seem
to
really
be
yeah.
A
A
So
yeah
one
of
the
conclusions
will
be
how
to
make
sure
that
we
we
have
the
feedback
from
marketing
members
to
confirm
if
these
Trends
are
are
what
the
majority
of
the
communities
thinking
right
now
yeah
this.
This
was
the
first
exercise,
and
certainly
we
will
have
a
second
iteration
trying
to
cast
a
wiring
it.
B
B
It's
like
you
initially
triaged,
how
it
all
works
to
begin
with,
and
then
people
understand
that
so
I
don't
know
if
it's
like
a
reflection
on
your
documentation,
but
maybe
more
that
there
needs
to
just
be
like
a
I.
Don't
know
if
it's
better
documentation
for
Upstream
build
pack
like
the
pack
tool,
but
maybe
just
a
pack
troubleshooting
documentation,
that's
more
General!