►
From YouTube: Che Community Meeting July 05th 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
A
B
So
here
from
the
file,
I
am
not
far
so
I
can
add
the
title
as
before,
but
here
I
have
some
welcome
information
that
will
not
be
persisted
in
my
bug.
So
this
is
some
information
that
we
can
display
to
the
users,
but
it
is
not
stored
inside
the
bag,
and
here
we
can
describe
the
bags
we
can
have
drop
down,
select
the
version.
B
If
I
click
and
create
my
bag,
I
only
have
the
useful
information
in
my
report,
so
I
don't
have
any
tasks
in
the
package
here.
I
don't
see
any
tasks
because
we
we
are
drop
down
to
select
the
value
and
here,
for
example,
in
che
I
can
see
here
for
the
18
tasks
20
different
types.
It's
because
we
have
all
the
available
values
here
listed.
A
C
B
B
B
Okay,
just
final
value.
C
Okay,
just
a
little
drawback,
probably
so,
with
that,
we,
like
close
the
whole
context,
like
the
all
platforms
that
we
have
and
if
user
is,
is
able
to
reproduce
it
on
one
more
platform.
He
would
need
to
to
find
the
way
how
we
is
expected
to
edit
there.
C
Yeah,
that's
fine
that
you
can
edit,
but
is
the
previous
way.
We
still
have
the
choice
to
tick
then
previously
and
selected
like
now,
I'm
able
to
replace
in
a
mini
cube
as
well
as
mini
shift,
and
it
was
just
simple
click,
but
now
it's
editing
markdown
and
provisioning.
C
A
A
B
D
Which
labels
will
be
synchronized
to
the
other
repositories?
Is
it
just
things
like
bug
or
new
and
noteworthy,
because
I
think
some
of
the
area
labels
would
wouldn't
make
sense
to
propagate
them
right.
B
So
the
idea
is
to
have
all
the
levels
in
the
file
and
then
we
can
decide
from
the
part
if
we
apply
all
the
or
the
kind.
D
No,
but
I
mean,
for
example,
like
like
area:
plugins
doesn't
really
apply
to
a
dashboard
repository
for
example,
or,
like
chateau
area
label,
doesn't
apply
to.
I
don't
know.
E
Yeah
the
the
areas
are
for
for
issues,
and
we
only
use
eclipse
j
for
issues
I
mean
it's
not
for
so
the
other
repositories
are
used
for
prs
and
we
we
don't
use
arias
and.
B
For
question
we
could
exclude
areas
and
we
sync
to
other
orchestras.
D
Yeah,
that's
a
good
point.
Mario.
I
forgot
about
that
one
other
thing
I
want
to
mention
about
the
team,
so
the
team
thing
is
kind
of
a
red
hat
specific
label.
So
maybe
we
could
do
like
red
hat
team,
flash
whatever
it
is,
but
people
from
the
community
know
that
it's
something
for
red
hat
only
because,
for
example,
some
random
committer
isn't
going
to
know
what
the
plugins
team
is
for.
F
What
do
you
mean
running
reports?
I'm
not
sure
how
you
you're
using
the
team
labels.
Is
it
external
tools
or
is
it?
Do
you
assign
them
or.
E
So
it's
a
way
to
to
to
let
know,
orders
that
that
team
is
going
to
work
on
that
issue
during
current
sprint.
So
that's
that's
the
the
is
not
for
generating
any
reports,
so
I
don't
know
I'm
not
aware
of
any
reports
generated
by
teams
or
using
the
team
labels.
D
E
And
then
prefix
we've
read
out
like
the
redact
plugins
team.
So
I
don't
know.
If
tomorrow
will
be
another
company,
then
they
may
have
a
team
with
a
team
working
on
something
they
may
have
like
team
slash,
the
name
of
the
company.