►
From YouTube: Che Community Meeting November 8th 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
C
B
The
train
web
id
github
action
published
on
github
marketplace
already.
We
have
a
couple
of
blogs,
one
of
four
developer:
red
hat
blog,
the
other
one
is
for
eclipse
chat
blog.
So
you
can
find
the
links
at
the
bottom
of
the
issue
description.
B
The
next
proposal
is
going
to
be
enabling
this
try
and
web
id
gita
batch
into
every
single
eclipse,
chair
related
repository.
So
basically
the
idea
is
to
be
more
proactive
on
that.
C
B
And
have
a
fixed
deadline,
let's
say
for
the
next
community
called
so
in
a
week.
We
should
enable
all
the
triv
id
github
action
to
every
single
eclipse
share
related
repository,
and
you
know
I'm
not
sure
how
exactly
we
can
plan
this
work,
because
I
mean
each
team
probably
can
just
go
through
the
repository
list
and
identify
their
ownership
and
add
the
github
action.
B
So
we
already
have
some
github
actions
for
some
repositories,
like
I
think
gallery
is
opening
the
plugin
registry,
which
already
have
it
it's
find
web
id
is
the
start
from
the
bottom.
Yes,
this
one,
so
it's
pretty
simple
one.
It
has
some
configuration.
I
know
there
was
a
comment
already
on
the
community
meeting
minutes
that
it
comments
basically
on
every
single
pr
update.
If
you
don't
like
it,
you
can.
C
B
Check
the
the
code-
and
it
would
be
great
to
hear
also
some-
you
know,
success
stories
and.
A
B
You
know
fail
stories
next
spring.
For
example
like
for
this
repository,
we
can
leverage
the
action
and
our
host
environment
very
well
and
for
that
one,
not
so
much
because
that
and
this
so
it
will
allow
us
to
better
understand
what
we
are
missing
and
have
more
consistent
setup
for
the
repositories
so
yeah.
This
is
the
first
topic.
So
folks,
if
you
have
any
questions,
concerns
comments.
B
C
B
Someone
would
love
to
comment
on
that.
Like
fabrice
already
commented
that
he
likes
it
and
did
she
talks
or
maybe.
B
B
Yeah,
so
it's
just
a
quick
announcement.
Majority
of
us
probably
know
that
we
are
going
to
merge
the
two
teams,
starting
from
the
next
spring,
so
hosted
team
will
formally
cease
to
exist
and
will
be
one
big
controller
team,
but
we
still
have,
of
course,
the
hostage
here
label
and,
as
you
know,
we
are
doing
the
upstream
issue
triage
and
it's
like
rotation
process
for
the
teams.
So
I
wanted
to
someone
to
delete
the
hosted
team
from
the
upstream
issue.
B
B
Mission
days,
yeah
probably
marta
would
be
the
right
contact
person
for
that,
but
I
think
we
don't
have
martial
in
the
call.
B
Calendar
mostly,
I
I
meant
calendar
I
mean
now
so
maybe
we
yeah
it's
true
that
we
do
need
to
update
wiki
it's
in
the
in
my
to-do
list.
So
on
wednesday
this
week,
I'm
going
to
remove
the
team,
hosted
shell
label
and
we'll
try
to
remove
it
from
you
know,
wikis
from
from
other
parts
of
the
of
the
documentation
where
I
will
be
able
to
find
it,
but
the
most
important
thing
that
you
know
we.
We
need
to
come
up
with
the
better
triage
idea,
because
you
know
we
will
do
as
a
controller
team.
B
Try
you
know
month
on
fridays
and
on
monday
this
is
yeah
on
monday
isis
backhand
at
this
point.
So
today
is
the
very
last
day
that
we
are
doing
the
trials.
E
E
Okay,
we,
I
think
that
we
yeah,
we
can
discuss
that
yeah,
maybe
with
with
managers
or
well
so
I
I
don't
know
if
there
is
somebody
so
maybe
since
we
we
have
a
pm,
we
we
now
have
a
pm.
We
may
see
if
pm
can
join
us
to
do
that.
Maybe
that's
a
way
to
to
get
more
familiar.
A
So
we
can
go
to
the
next
topic,
it's
for
me
and,
as
we
already
discussed
sometimes
ago,
we
should
have
a
rotating
system
to
choose
a
moderator
of
the
recommended
call
on
this
call.
So
the
idea
is
that
the
moderator
will
be
changed
monthly
and
it
it
will
be
similar
what
we
do
with
the
process
of
issue
trading,
so
I
propose
that
a
team
leader
or
a
team
will
be
assigned
to
moderate
the
checkup
for
one
month
and
then
this
responsibility
will
be
moved
to
another
team.
A
B
I
mean
I'm
not
again,
I'm
not
against
the
you
know
monthly
trials,
but
just
was
put
yeah
just
my
thinking
was
that
maybe
the
community
goal
to
leverage
more
the
community
adaptation.
It
will
be
more
interesting
for
pm
to
handle
the
moderation,
but
rather
than
do
it
in
a
rotation
mode,
because
we
already
have
rotation
for
triage.
A
E
Yeah
we
can.
We
can
ask
that.
I
think
that
maybe
the
the
moderator
should
be
some
someone
that
has
already
attended
a
few.
E
A
few
calls,
so
maybe
that
that
may
yeah
take
some
time,
whereas,
like
the
triaging
of
the
issues,
is
something
that
so,
if
you
don't
know
you
can
ask
how
you
need
to
triage
an
issue
doesn't
need
to
you're,
not
actually
a
moderator
of
anything.
It's
more.
E
So
yeah,
that's
that's
my
point
of
view,
but
yeah
we
cannot.
We
can
ask
her
if,
if
that's
okay,
to
the
to
to
to
do
the
tool
to
be
added
here,
but
they
won't
change
much
for
us,
I
mean
to
be
10
or
11.
E
The
only
thing
that
honestly,
I
think
it's
it's
we
may
do
is
that
we
we
could
add
other
people
not
not
only
the
the
team
leads
yeah.
A
I
mean
they're
engineers
yeah.
It
can
delegate
some
this
responsibility
to
someone
else.
A
B
E
A
D
Yes,
so
since
I
don't
know
something
like
june
or
so
since
a
few
months
there
we
we
we
received
so
the
way
that
steam
capture
things
to
do
is
to
look
at
github
to
the
area
dock
level
label.
So
basically
we
we
look
at
issue
they're
entering
our
radar
when
there
is
this
label
and
since
some
something
like
june,
maybe
a
little
bit
more.
We
have
almost
no
issue
there
and
maybe
half
of
the
issue
are
created
by
ourselves.
D
So,
as
a
consequence,
our
some
things
that
have
done
doc
impact
entering
our
radar
only
at
pull
request
time.
So
when,
when
someone
from
engineering
is
doing
the
pull
request,
that's
that's
a
little
bit
uncomfortable
for
us
because
we
cannot
plan
anything.
So
even
if
sometimes
we
lag
so
much
behind
it,
it
doesn't
help
so
question
is:
can
we
maybe
think
about
adding
this
label
even
on
issues
where
the
issue
is
not
completely
dug,
but
that
needs
a
little
bit
of
talk.
D
I
I
I
mean
that's
in
in
the
issue
when,
when
when
so
at
triage
time
or
even
later,
if
it
happens
later,
but
when
when
when
someone
can
notice
that
there
is
an
impact
on
dogs
on
an
issue
that
you
add
this
label,
because
that's
the
way,
we
know
that
there
is
something
that
that
needs
stocks,
tax
team
attention
and
so
that
so
that's
that
was
quite
efficient
before
the
thing
that
was
not
efficient
is
that
we
we
are.
We
we
have
the
issue
in
our
backlog
and
we
don't
manage
to
handle
everything.
D
That's
another
problem,
but
now
we
don't
even
know
what
is
what
is
so.
We
don't
even
have
a
backlog,
we
don't
have.
We
don't
have
a
pile
of
tasks,
because
we
don't
have
issues
that
are
up
here.
D
So
it's
just
please
when
you
are
doing
some
triage.
If
you
see
it's
about
dogs
at
this
lab
label,
it's
there
and
it's
they
are
it's
it's
it's
useful.
It's
very
useful
for
us.
C
D
C
D
Then
so
then
the
the
thing
is,
we
have
to
rethink
some
some
some
some
of
the
things
I
believe,
but
for
now
we
have
to
create
always
recreated.
We
create
an
issue
in
gerhard
and
that's
what
we
are
supposed
to
do,
but
it
doesn't
mean
that
we
can
handle
everything
in
in
our
sprint.
So
we
are
under
capacity,
let's
say
so:
we
we,
we
lag
a
lot
behind
and
we,
but
we
we.
D
D
It
means
that
when
the
task
enter
our
radar,
that's
when
it's
in
the
dawn
stream,
epic
and
given
our
lead
time
to
produce
the
dogs,
it's
too
late.
So
that's
our
problem.
We
are
always
too
late
because
we
we
we
see
the
things
happening
too
late,
because
when
you
are
when
we
test
the
soap
now
we
have
more
process
so
we
are.
Are
we
have
more
time
to
test
the
procedures
and
then
more
time
to
review
the
procedures?
So
it
means
it's
it's
it's
longer
than
before
and
we
need
to
start
more
upfront.
C
So
you
are
asking
not
just
for
label
but
to
create
issue
in
time
yeah
for
documentation.
It
looks
like
oh.
C
D
C
D
So
it
doesn't
need
to
be
to
be
a
separate
issue
as
any
way
we
create
a
duplicate
in
general,
so
we
will
create
a
duplicate
in
in
our
our
our
dog's
jira.
So
if
it's,
if
it's
a
engineering
issue,
that's
that's
perfect
for
us,
because
we
don't
need
to
synchronize
the
two
tasks.
So
that's
that's
easier
for
us,
but
I
I
believe
we
are
quite
agnostic
on
the
fact
of
one
issue,
two
issues.
D
That's
the
this
split
brain
situation:
it's
not
very
comfortable,
but
we
have
to
so
that's
not
something
I
decide.
That's
that
everything
should
be
done
in
in
jira.
I
would
be
much
more
comfortable
to
to
handle
all
the
upstream
issues
directly
in
github
and.
C
C
D
Yeah,
probably
we
can
leverage
the
the
gira
script
to
do
that.
Apparently
we
do
it
manually
because
we
have
one
issue
every
two
weeks.
So
that's
not
a
lot,
and
so
the
the
the
cool
thing
is
that
we
don't
have
a
lot
of
work
by
to
create
the
issue.
Then
that
nice
thing
is
that
we
are.
We
are
losing
track
of
what
needs
to
be
done.
E
That's
why
I
usually
set
the
label
aria
dock
when
it's
a
dock
and
I
think
that
a
lot
of
people,
so
a
lot
of
us
doing
triage-
are
still
doing
it.
Some
kind
of
like
do
you
think
it's
do
you
have
in
mind
someone
in
particular
that
or
some
team,
or
I
don't
know
it's
just
look
at.
D
The
list
of
area
duck
issues
and
we
have
two
per
month
and
that's
and
we
have
more
to
do
than
that
and
we
see
receive
talks.
So,
for
example,
one
of
the
last
one
was
about
the
backups,
so
we
received
the
so
that
was
one
of
the
last
one
one.
Just
one
pull
request
that
came
today.
It's
about
removing
a
helm
and
we
have.
E
D
E
E
D
So,
given
so
I'll
give
you
the
example,
I
will
try
to
find
so
I
believe
the
the
one
that
made
me
think
about
it.
That
was
the
that
was
about
the
backups.
D
And
and
the
last
one,
the
last
interesting
one-
that's
remove
helmet
installer
from
dark.
That's
the
the
really
last
last
last
good
request
that
we
received
today.
So
it's
just
just
in
time
for
the
communicable
so
they're
just,
and
so
we
have
that
issue
in
jira.
We
we
don't
have
we
don't
have
any
control
parts
in
in
github,
an
issue
for
that
and
now
we
receive
the
the
pull
request.
So.
E
D
And
it's
linked
to
it's
linked
to
an
issue.
E
But
that's
that's
mainly
because
that's
that's
the
installer
theme
that
will
take
care
of
it,
so
they
are.
They
are
not
so
that
that
that
makes
sense
for.
For
that
reason,
so
yeah
I'm
just
trying
to
understand,
because
I
think
that's
like
if
we
do
that
99
percent
of
the
time
you
will
end
up
with
with
an
aria
dock
on
the
issue.
D
D
Cycling,
so
I'm
sorry,
it
will
be
difficult
so
because,
because
we
know
we
know
some,
so
we
can
we
we.
We
know
the
things
before
just
to
put
requests
and-
and
we
don't-
I
don't
know
it's
just
a
capacity
to
plan
capacity-
to
understand
where
the
police
requests
come
from
and
for,
for
example,
for
the
the
helm,
installer
question.
We
captured
it
on
jira,
also
during
one
during
one
one
of
the
session.
D
It
was
one
of
the
topic,
and
so
we
are
planning
now
to
to
put
it
in
the
next
print.
But
it's
already
done
so
it's
a
very
good
news,
but
but
it's
it's
quite
uncoordinated.
D
That's
a
that's!
That's
that's
a
very
interesting
question
because
I
now
it's
one
it's
one
of
our
internal
problem
in
the
dog's
team
is,
is
to
manage
all
the
all
the
pull
requests.
B
D
Yes,
but
so
so
it's
so
it
will,
it
will
help
us
not
to
not
starting
to
work
on
something.
In
the
same
time,
some
engineer
is
working
on
the
same
topic
and
to
have
to
have
you
know
conflicting
pull
requests,
so
that
happened
for
the
for
the
for
the
backup,
for
example,
where
we
had
one
pull
request
coming
with
with
a
few
changes
and
in
exactly
the
same
time
we
had
one
writer
working
on
the
same
topic
and
we
didn't
notice
the
pull
request.
B
D
C
D
B
Yeah,
just
I
mean
if
someone
from
dog's
team
is
working
on
the
you
know,
documentation
on
some
featured
checkup
with
the
initial
developer,
like
hey
man,
how
it's
going
to
be
documented?
B
Do
you
want
like
documented,
oh
yourself
and
review
it
like
reviewed
by
the
dogs
team,
or
you
expect
the
dog
symbol
writes
the
actual
dogs
on
something.
D
I
don't
know
I
have
no,
I
have
no
expectation
on
that,
but
I
so
we
will
know
what
is
what
is
what
is
happening
so
what
is
happening
next?
We
can.
We
can
know
about
it,
because
now
what
we
are
doing
is
more
reverse
engineering.
The
the
downstream
epic.
B
Yes,
I
mean
fabrice
how
you
would
know
that
that
pull
request
is
going
to
to
to
be
in
place
for
for
review
by
the
area
dock
label
in
the
issue.
It's
just.
I
just
cannot
grow
it.
Okay,
and
just
I
understand
that
you
want
to
set
up
the
process
and
yeah
I
mean
everyone
would
love
to
help
you,
but
we
just
at
least
me.
I
just
don't
understand
how
you
want
to
implement
this.
B
B
Course,
because
everything
it's
what
you
propose,
because
everything
needs
to
be
documented
as
part
of
the
pull
request.
For
example,
we
are
adding
monitoring
for
their
workspaces
and
we
are
going
to
shoot
a
pull
request
this
week
and
it
need
to
be
reviewed
and
it's
part
of
the
epic
part
of
the
story
like
as
an
admin.
I
want
to
have
monitoring
in
place
so
and
we
do
expect
that
dogs
will
do
the
first.
The
language.
D
So
here
we
are
more
here
to
so
then
our
role
is
more
to
to
take
the
draft
and
and
and
and
take
it,
take
it
from
the
draft
and
just
wait
the
pull
request
to
happen
and
make
the
magic
happen
afterwards.
That's
it.
B
Procedure,
review
and
approve,
or
not
a
proof
based
on
this.
So
that's
how
I
understand
it:
everyone
there
is
no
separation
for
pull
request
review
depending
on
on
the
role.
It's
like.
The
the
rules
are
the
same
for
everyone,
so
it's
like
language
review
and
the
procedure
review.
Actually
it
works
and
verification
right.
So.
D
Okay,
I
I
will
know
the
fault:
that's
just
asking
for
a
rare
duck
label
will
be
leading
to
such
complicated
files,
but
okay.
B
D
The
duck
impact,
we
don't
use
this
one,
that's
basically
we
use
this,
this
area
dock
level.
We
look
at
that
and
we
are
at
team
dock
when
we,
when
we
know
that
we
have
to
take
ownership
of
the
issue,
but
it's
it's.
The
problem
is
that
it's
less
and
less
so
we
had
more
issue
in
the
past
and
now
it's
getting
it's
getting
an
empty
and
empty
queue.
If
you,
if
you
look
down
the
look
down
the
loop
under
the
queue
of
issues,
we
add
more,
it's
just
that
it's.
D
D
We
don't
really
know
what
is
what
is
happening.
So
we
are,
we
are
a
little
for
me.
We
are
losing
a
little
bit
of
control
of
what's
what's
in
the
pipe
and
what
is
happening
or
we
would
have
to
follow
every
every
issue,
every
request
in
everywhere.
So
it's
more
more
uncertainty.
D
Yes,
that
is
the
impact,
but
that's
yeah,
but
that's
quite
the
same,
so
aria
dark
or
status
duck
impact.
That's
right,
bella!
That's
a
label
to
pick
the
dog's
team
that
there
is
something
happening.
E
Yeah
and
what
about
like,
if
you,
if
you
look
at
the
sprint
planning
every
week,
so
you
know
that
what
what
every
team
is
working
on
so
is.
Is
that
something
that
you
you
you're
trying
to
do
like
to
figure
out
what
what's?
Actually
teams
are
going
to
work
on?
Maybe
that
that
and
you
can
like
figure.
B
D
Yeah,
but
that
means
just
more
reverse
engineering,
so
it's
more
more
more
reading.
Reading
that
to
to
to
take
that,
that's
the
thing:
that's
the!
How
to
make
it
more
efficient
where
we
are
nikhil
will
not
be
replaced
in
our
team.
So.
E
It's
just
that.
I
think
that
from
from
the
issue,
understanding
exactly
when
so,
if
it's
in
one
week
or
in
three
months
that
you
will
actually
need
to
review
10
lines
or
100,
I
think
that
you
won't
be
able
to
to
figure
that
out
so
who
is
who
setting
the
area
labels
won't
be
able
to
figure
out
that,
whereas,
when
you
see
that
a
team
is
working
next
next
spring,
so
the
sprinter
will
start
in
a
few
days
they
will,
or
it's
already
started.
E
They
are
working
on
something
that
is,
that
is
changing
an
important
feature
of
the
of
the
product.
It's
like
you.
You
will
probably
think
about
okay,
so
if
they
are
changing
that
in
in
in
the
few
few
few
weeks
they
are
coming,
there
will
probably
be
changes
on
dock,
and
I'm
just
just
trying
to
understand
how
how
we
can
help
help
you.
D
E
I
think
that's
that
in
in
general,
so
there
is
this
thing
that
we
have
done
with
the
qe
that
have
been
because
qe
has
the
same
problem
right
like
they
will
need
to
test
to
start
writing
automated
tests
for
features
that
will
land
somehow.
So
it's
kind
of
similar
right
of
of
the
problem
that
you
have
yes,
so.
E
D
It's
that's!
That's
exactly
that!
That's
and
and
the
rabbit
is
going
faster,
every
every
sprint
and
we
are
lagging
behind.
E
Yeah
it's
but
the
the
thing.
That
is,
that
what
is
successful,
I
think,
is
like
there
are
some
member
of
the
queue
team
that
are
working
with
the
the
teams,
so
they
are
attending
the
the
stand
up
so
that
they
are
kind
of
part
of
the
of
the
team
so
that
they
can
be
updated
real
time
and
they
know
and
and
they
can
update
also
on
the
work
they
are
doing
the
the
team,
so
that
that's
that
that
is,
I
think
it's
really
effective.
E
So
maybe,
if
you
can,
I
think
that
you
have
like
a
lot
of
impact
are
in
our
like
the
team
that
is
working
on
installation,
so
the
deploy
team
provide
a
lot
of
documentation.
So
maybe
you
can
start
thinking
like
having
one
someone
from
your
team
attending
the
stand
up
yeah
how
much
time.
E
So
it's
a
few.
I
think
it's
a
few
minutes
per
day.
It's
not
so
that's
that's!
That's
at
least
it's
the
goal
of
the
stand
up,
but
what
what
is
missing
is
you're
missing
documentation,
so
somehow
you're
missing
communication.
So
there
is
a
communication
that
is
not
happening
to
get
more
of
the
communication
you
somehow
have
to.
So
it's
not
just
adding
a
label
arya
doc.
E
I
don't
think
you
will
get
the
enough
to
go
into
the
communication
that
you
are
looking
for.
Okay,
so.
D
See
that
yeah,
maybe
we
can
manage
that,
that's
how
many
teams
do
we
have
now.
E
D
D
E
Yeah,
so
if
you
want
to
do
that,
yeah
yeah
you
can,
but
I
would
not
suggest
that
so
no,
the
the
qe
team,
what
they
they
don't,
have
a
qe
engineer
on
every
team
they
just
they
have
on
just
starting
with
one
so
adding
just
one
person
participating
to
the
stand-up
the
work
of
one
team,
like
the
team.
That
is,
I
don't
know
if
you
go.
For
example,
controller
team
today
is
working
on
a
lot
of
stuff
that
probably
will
need
to
be
put
into
the
documentation.
E
E
D
That's
that's.
That's.
E
B
E
B
Fix
that's
two
queries,
so
we
we,
we
are
having
very
time
spokes
stand
ups,
so
we
are
doing
the
actual
stand-ups
with
comments
in
the
chat
mode.
B
We're
going
to
do
this,
so
you
can
just
asynchronously
follow
up
on
the
standups
and
if
you
have
questions
like
ask,
ask
the
questions
in
the
tracks
of
the
standups,
so
you
even
don't
need
to
attempt
a
call.
You
can
just
follow
up
on
the
you
know
daily
daily
stand-ups
asynchronously
whenever
you
have
some
time,
do
that
and
ask
questions
if
you
have
any.