►
From YouTube: Che Community Meeting June 28th 2021
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
Okay,
so
I
just
heard
according
to
started
so,
let's,
let's
kick
things
off,
welcome
everybody
to
the
j
community
meeting
today
is
monday
28th
of
june
2021.
A
we're
going
to
just
jump
right
in
there's
a
few
topics
on
the
on
the
agenda.
First
topic
is
fabrice
you're,
going
to
talk
talk
about
doxp
or
templates.
B
Yeah
hi,
so
I'm
here
to
discuss
changing
the
peer
template
in
for
the
documentation
and
I'm
mainly
before
bef
before
we
merge
this
or
we
rework
it.
I
would
like
to
have
the
the
to
to
see
to
see
the
reception
on
this
change,
so
I'm
trying
to
to
have
something
where
where
so,
the
idea
is
to
make
more
clear.
What's
what
as
a
writer,
what
is
the
checklist
that
we
are
using
as
a
technical
writer
and
to
make
it
surface
into
the
the
the
piercing
plate?
B
So
that's
the
main
idea,
then
I
want
to
make
sure
it's
not
overkill
so
where?
Where
should
I
put
the
limit
of
of
items
in
the
checklist?
That
is
not
too
much
and
the
other
idea
was
to
make
visible
what
is
automated
in
our
process
and
what
is
not
automated,
so
I'm
open
to
any
remarkable
question
about.
B
B
It's
like
it's
a
little
bit
long,
but
it's
all
what
we
do
and
I'm
I
don't
know
what
makes
sense
to
to
make
visible
on
what
what
is
completely
overwhelming
for
engineering.
B
That's
that's!
That's
a
very
good
question.
It's
it's!
It's
that
it's
do.
We
need
that
yeah
to
make
so
because
in
the
check
is,
is
I
have
I
ever
I've
already
heard
people
telling
me
that
the
the
checks
are
not
clear
and
that
that
that's
so
you
know,
when
I
say
hey
you
are,
you
are
the
links
are
broken
and
hey.
Where
do
I
see
that-
and
I
was
thinking-
maybe
this
specs
more
clear
to
check
the.
D
B
Yeah,
so
that's
also
that's
so
the
the
the
levels
are
also
here
to
to
to
to
explain
so
what
so,
it's
all
all
what
we
are
doing
and
from
from
from
our
perspective,
we
are
not
expecting
so
our
work
is
mainly
to
work
on
the
level
three.
So
as
a
writer,
we
are
more
expecting
work
on
the
on
the
level.
Three
in
the
review
process
is
to
make
sure
that
all
of
that
is
happening
and
under
level.
B
The
level
two
is
something
that
is
not
automated,
but
it's
what
is,
let's
say,
more
simple
to
achieve,
so
that
would
be
our
our
next
targets
in
in
the
documentation
in
terms
of
of
of
quality,
and
that's
something
where
I
believe
that
something
that's
achievable
for
for
everyone.
E
E
B
Do
so
so
the
aim
also
is
to
have
something
so
something
for
our
for
our
new
ielts,
so
for
our
new
writers,
because
it's
it's
more
easy
to
it's
more
easy
to
do
a
review.
If
you
have
the
checklist
directly
in
the
pull
request.
Also,
it's
like
you
can
check
the
boxes.
B
B
When
it's,
when
it's
a
fix,
usually
we
still
have
to
have
the
the
the
validation,
but
on
the
fixed
typo
it's
there
is
so
the
the
the
the
scope
of
the
content
to
verify
is
very
small,
so
it
goes
fast,
it's
more
for,
for
the
it's
more
for
the
new
content
that
we
have
to
have
some
some.
You
know
some
some
some
process
to
cla.
So
some
clarification
to
do
it's
like
what?
What
are
what
are?
B
What
are
the
expectations
clarify
the
expectation
and
so
it's
we
will
propose
change
for
this
thing
because
of
these
principles.
So,
to
make
things
clear
that
that
we
have
some,
we
have
some
tool
that
we
want
to
achieve.
Also
that
we
want
to
have
something
and
clarify:
what's
what
are
the
rules?
So
what
are?
What
are?
B
So
tight
title,
like
that
doesn't
don't
make
sense
right
would
be
madness,
like.
B
I
so
like
a
level
level.
Three,
please
request
the
help
of
of
technical
writer,
something
like
that.
I
don't
know
how
to
work
towards
it.
So
the
idea
is
is
halfway
clear
to
me
at
the
moment-
and
I
I
expect
a
lot
from
the
discussion
here-
to
make
it
more
clear.
But
for
me
is
level
two
is
something
that
that
a
notor
could
be
able
to
do,
but
we
have
to
to
discuss
this
because
I'm
not
sure,
maybe
my
assumption
is
completely
false
and
level.
B
Three
is
more
like
request,
the
assistance
of
a
technical
writer.
If
you
feel,
if
you
feel
challenged
by
this-
but
I
don't
know
exactly
how
to
write
it
and
what
what
how
to
express
that
thing.
B
But
it's
for
the
reviewer
so
because
it's
a
full
request
where
you
go
to
a
review
process
and
the
review
process
that
we
are
following
is
basically
it's
iterating
over
these
items.
But
it's
it's
not
visible.
It's
it's!
It's
it's
the
checklist
that
we
follow,
but
the
checklist
is
that
it's
not
visible
by
the
contributors
and
I
believe
that's
not
that's
not
fair.
You
know,
that's
that's
not
fair
to
to
not
display
it.
B
And
you
don't
need
to
know
you
don't
need
to
do
the
details
on
your
arnold
wilde.
E
No,
I
mean,
if
I'm
just
a
contributor,
I
would
say
I
can
have
a
link
to
see
what
other
steps
are
used
by
the
docs
team.
But
I
don't
know
from
my
point
of
view
yeah
it's
too
many
items
to
to
flower.
B
So
it
would
make
more
sense
to
have
this
as
a
described
in
the
contributing
page,
but
not
in
the
pull
request.
Template.
A
A
You
know,
like
one
step,
is
you
know
following
the
start
guidelines,
and
then
you
have
title,
and
you
know
information
is
clear
and
concise
that
sort
of
stuff,
and
then
you
have
one
section
about
spitting
the
pull
request
and
so
on.
Just
so
that
I
know
each
bullet
point
is
is
a
step
in
itself,
but
just
calling
them
steps
means
kind
of
you
know
exactly
which
way
to.
A
A
Also
a
question
I
notice
level
three
language
is
compliant
with
the
ibm
style
guide
and
supplementary
style
guide.
This
is
my
ignorance,
but
is
there
an
eclipse
style
guide
for
documentation?
Does
anybody
know.
B
Not
that
I
know
not
that
I
know,
and
so
the
supplementary
sky
get
from
red
hat
is
open
source,
so
it's
published
on
the
internet
and
the
ibm
style
guide
is
a
problem
because
there
is
a
there
is
a
publication
from
2011,
which
is
a
book
that
you
can
buy
and
then
there
there
was
a
web
version
in
developerworks
and
it
has
been
shut
down,
and
then
there
is
the
the
ibm
style
guide
as
a
pdf
that
you
can
have
at
red
hat.
If
you
are
a
writer,
but
it's
a
written
confidential.
B
So
so
we
have
a
problem
with
that
and
we
are
not
the
only
one
so
and
currently
so,
who
are?
Let's
say
we
are
working
on
it.
So
the
idea
is
to
get
at
some
point
with
some
some
implementation
in
veil
of
some
open
source
style
guide,
which
is
inspired
by
ibm,
but
who
are
where
we
are,
who
are
not
dependent
of
a
resource
that
is,
that
is
not
available
to
anyone.
B
But
currently,
that's
not
something
that
we
can
talk,
which
I
and
other
people
in
in
ccs
and
in
in
our
docs
team
are
trying
to
move
things
around.
But
it's
it's
a
it's
a
long.
It's
a
long
process.
It's
it's
something!
That's
you
know
we
have
the
microsoft
style
guide,
which
is
which
is
a
publish,
publishly
public.
We
have
the
apple
style
guide,
which
is
public,
but
no
red
hat
for
that,
it's
the
ibm
style
guide
and
it's
a
closed
source
resource.
B
Yeah
and
the
supplementary
style
guide
is
quite
helping,
but
it's
it's
just
you
know
the
little
topper
ponder
on
on
a
big
topic
stuff.
So
it's
oh
yeah,
so
we
have
where
we
have
a
problem
with
that
we
do
as
the
best
as
we
can
to
so
to
have.
The
veil
shake
makes
it
here,
because
you
have
just
you
know,
feedback
in
your
in
the
idea,
exactly
directly
of
what
is
good.
What
is
not
good,
you
don't
need
to
have
the
pdf
in
under
your
hands.
B
So
that's
the
idea
is
to
remove
the
necessity
to
have
this
500
pages
book
and
to
have
something
in
the
editor
to
give
feedback,
and
that
makes
perfectly
sense
because
it
it
matches
with
the
with
the
project
goal
so
to
have
something
where
you
can
develop
easily.
So
you
write
shadows
on
eclipse,
you
have
you
have
the
the
plugin
testing
the
docs,
so
that's
really
cool,
so
good
good
convergence.
A
B
So
I
know
now:
that's
not
in
the
template,
so
the
pull
request
on
plate
is
not
the
the
right
place.
So
then
I
have
to
figure
out
something
else
for
for
the
new
varietals,
because
so
we
have
we
have
a
plan.
B
We
have
a
page
in
confluence
which
is
basically
the
same
and-
and
I
know
people
are
copying
the
file
to
check
things
when
they,
when
they,
when
they
review
pull
request
so
to
have
the
items
directly
in
the
request,
makes
their
life
easier,
because
it's
I've
checked
that
that
that
that
and
now
yes,
I
can
validate,
we
will
survive.
A
Febreze,
okay,
we'll
we'll
move
on
then,
if
you
need
any
more
feedback
on
that,
I
suggest
posting
on
the
mailing
list.
If
you
haven't
already
or
we
can,
we
can
discuss
again
in
another
meeting
if
you
need
to
okay.
C
Yes,
so
can
you
open
the
the
main
list
email?
The
second
link.
A
C
Here,
yes,
so,
two
years
ago
or
two
years
ago,
six
months
ago,
we
brad
has
left
hadlett
red
hat
and
his
google
account
was
owning
the
youtube
channel
and
and
we
couldn't
so,
we
tried
to
to
activate
that
account.
But
we
couldn't
do
that
because
of
legals
and
so
on.
C
So
now
you
have
no
way
to
to
to
reactivate
this,
how
to
to
to
have
access
again
to
this
account.
So
you
cannot
publish
any
videos
in
this
this
channel.
C
So
the
idea
was
to
now
to
create
a
new
youtube
channel
and
to
yeah,
so
people
can
publish
videos
ready
to
cheer
again.
So
there
is.
C
C
A
C
Okay,
is
it
okay?
Now
you
can
hear
me
yes,.
A
C
No,
so
so
I
tried
to
send
a
message
to
put
the
youtube
support.
C
Channel
but
I
didn't
have
any
answer
reply
and-
and
I
sent
like
three
or
three
times
the
same
request:
no,
no,
the
answer.
Then
I'd
try
to
to
reach
the
red
hat.
I
t
to
see
if
they
could
reactivate
a
broad
account
and
we
could
access
to
it
and
then
change
the
owner.
C
C
C
A
gmail
account
as
as
a
member
of
the
the
brand
account
that's
also
possible,
and
that
is
what
we
would
do
for
most
people
publishing
videos
and
we
will
try
to
keep
the
number
of
people
having
the
password
as
many
more
as
possible.
E
C
Yes,
it
still
exists,
so
what
I'm
doing
now
is
that
I
have
created
two
playlists
in
the
new
channel
and
the
good
thing
is
that
we
can
reference
the
videos
from
other
accounts
or
other
channels
in
this
playlist.
So
I
could,
for
instance,
in
the
playlist
committee
meetings,
add
videos
from
the
the
old,
your
channel,
okay
right.
C
Unfortunately,
I
have
no
way
to
edit
the
description
of
the
old
account.
That's
that
we
cannot
do
because
we
have,
we
don't
have
the
access,
but
we
have
to
live
with
that
and
what
else?
Yes,
I
still
have
to
or
me
or
someone
else
we
still
had
to
to
update
the
other
one,
all
the
friends
references
to
the
old
channel.
C
So
maybe
you
know
how
to
look
at
the
readme
ducks
the
dog,
the
dogs,
the
dog,
the
with
me
fries
and
so
on,
to
see
if
there
is
any
references
to
their
channel
and
yeah.
E
E
Instead
of
just
using
red
hat
people.
C
The
password
with
anyone,
even
from
the
eclipse
foundation,
that
won't
be
an
issue,
but
I'm
not
sure
if,
if
it
is
a
good
idea
to
have
the
an
eclipse
account
or
no
eclipse
webmaster
whatever
on
this,
I
don't
know
yeah.
A
So
so
at
eclipse,
our
marketing
team
runs
our
youtube
channels
and
we
have
one
for
the
foundation
for
sure
I
don't
know
if
we
have
other
ones,
but
the
only
channels
that
would
really
own
would
be.
You
know
the
main
foundation,
one
and
perhaps
working
group
channels,
but
not
on
the
project
level.
A
So
any
any
such
panels
slash
assets
need
to
be
owned
at
the
project
level,
but
in
saying
that
you
know
we're
happy
to
be
one
of
the
admins
contributors
in
some
way
as
well,
so
feel
free
to
share
with
me
some
of
the
details.
We
publish
a
lot
of
check
content
as
well
on
the
foundation
channel.
There's
a
cloud
dev
tools,
playlist
on
the
foundation
channel,
so
check
that
out
feel
free
to
pull
in
videos
from
there
into
your
playlists.
I
see
there
might
be
one
already.
A
A
All
right,
so
this
item
number
three
releases.
I
put
that
on
myself.
I
don't
know
if
it
warrants
this
question
today,
but
I
see
there's
a
question
above:
do
we
need
to
keep
releasing
our
listing
releases
and
dates
over
the
at
the
top
section
of
this
document,
and
so
you
have
a
comment
we
can
discuss.
A
A
A
C
Yeah,
I
don't
know,
but
I
I
thought
that
would
be
interesting
to
have
a
quick
update
of
the
last
release
that
we
we
have
done
and
what
is
the
content?
That
would
be
good
for
anyone
joining
the
meeting
to
know
yes,
so
yeah,
for
instance,
we
just
released
7
32.0.
What
is
in
there?
We
have
this
big
picture
there.
C
We're
fixing
these
issues,
and
so
that
would
be
interesting
for
anyone
coming
and
it's
also
useful,
sometimes
because,
if,
if
there,
this
debate
for
some
reason
to
know
that
it
is
going
to
come,
which
date
it
happens,
that
the
the
release
is
delayed
for
some
reason
and
yeah
to
just
to
know
if
we
have
any
a
new
date
or
when
it
is,
what
is
the
new
plan
for
for
the
next?
C
C
C
Yeah
but
then
I
I
didn't
know
about
this
mathematics
channel.
I
just
found
that
that
one
just
two
months
ago
and
that.
C
Who
would
know
that
it
does
exist?
That's
maybe
we're
not
we're,
not
we're
not
exposing
that
properly.
It
has
to
be.
C
Has
to
be
a
performance
references
in
in
with
me
files
or
in
the
website.
I
don't
know,
but
at
the
moment
only
a
few
people
knows
about
about
that.
Matamus
channel.
A
Yeah
and
I
think
to
make
this
section
more
useful
as
well,
I
think
you
should
add
in
information
about
not
just
latest
release,
but
but
upcoming
milestones
and
in
particular
how
to
get
an
item
do
an
upcoming
milestone,
so
something
related
to
planning
so
whether
that's
just
a
link
to
the
planning,
docs
or
or
or
whether
it's
a
link
to
you
know
some
label
and
github,
but
just
somewhere
where
people
can
see
talked
to
mario
a
little
bit
about
this
recently
and
tim,
and
you
know
there
is
a
process,
but
it's
it's
not
very
obvious
right
now.
A
What
that
is.
So,
I
think
maybe
a
little
bit
of
work
needs
to
be
done
on
documenting
that
someone
wants
to
write
that
down
as
an
action
item.
If
you
need
more
context
about
that,
just
contact
me,
I've
got
some
information
about
it.