►
From YouTube: Che Community Meeting May 2, 2022
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
So
welcome
everyone
to
this
eclipse,
j
community
call.
So
I
have
added
the
link
to
the
google
doc
with
the
topics
in
the
in
the
chat
or,
if
you
want
to
talk
about
something,
please
add
add
it
there
to
the
google
doc.
A
Okay,
can
you
see
the
google
docs
with
the
topics?
Yes
yeah,
all
right,
all
right,
okay,
cool,
so
I've
added
one
topic
today,
so
I
wanted
to
talk
about
something
that
we've
been
discussing
offline.
So
I
think,
like
a
discussion
of
that,
because
that's
a
major
change
since
when
we
have
switched
to
the
network
space,
so
I
think
it
was
beneficial
to
discuss
it,
and
this
is
about
starting
a
workspace
from
a
dev
file,
so
I've
opened
here.
A
Kodi
workspaces
is
based
on
previews
of
so
before
the
742
the
switch
to
that
workspace,
and
so,
if
a
user
click
on
create
workspace,
there
were
two
tabs
here.
One
was
this
one
with
a
quick
ad,
you
could
enter
a
url
or
you
could
select
one
of
the
samples
that
we
have
but
yeah
the
important
thing,
the
one.
The
thing
that
I
wanted
to
discuss
was
about
this
tab
here,
and
this
was
a
place
where
a
user
could
edit
that
file
for
from
here.
A
So
this
is
this
was
cool
because
you
could
select
like
one
of
the
examples
it
got
pre-populated,
so
the
user
shouldn't
have
to
add
manually,
plugins,
etc
yeah.
He
could
just
add
it
with
his
url
etc.
So
this
this
was
cool,
but
it's
not
here
anymore.
So
if
you
want
to
create
a
workspace
now,
this
is
how
it
looks
like
there
is
only
the
quick
add,
and
there
is
no
new
tab
here.
A
So
we
have
removed
that
okay.
So
there
are
a
couple
of
reasons
why
it's
not
here.
The
first
is
a
question
of
resources
is
that
we
would
even
we
could
not
support,
having
also
the
editor
of
that
file2.x
here
and
since
we
wanted
to
release
earlier,
we
released
without
this
tab.
So
we
say
it's
not
so
at
the
time
it
was
not
working,
so
we
we
decided
to
remove
it,
and
the
other
reason
is
that
we
got
feedback
from
people
that,
like
were
first-time
users
of
che,
that
they
could
not.
A
So
that
was
not
useful,
meaning
that
they
could
not
understand
much
how
to
use
these
and
they
started
like
changing
images
like
here
and
things
started
not
working
or
they
didn't
know
exactly
how
to
how
to
edit
that
so,
the
and
since
th
this
was
the
feedback
of
like
this
editor
not
being
useful
because
editing
a
ml
file
of
a
ml
of
a
format
that
you
you
don't
know.
It's
not
really
useful.
A
We
thought
that
instead
of
adding
this
back
so
adding
the
custom
workspace
tab
back,
we
would
prefer
having
something
different
like
letting
always
the
user
starting
from
here.
So
I
took
an
example
here
I
can
like
select
this
one.
This
is
a
git
repository
with
a
microservice
demo,
so
it's
an
example
for
microservice
and
you
can
always
put
the
guitar
positivity
here.
So
that's
what
I
expect
from
a
first-time
user.
He
does
he
create
representative
from
here,
and
if
you
look
at
here,
so
you
don't,
there
is
no
that
file
here.
A
So
there
is
no
definition
after
that
file.
So
we
we.
This
is
like
the
the
yeah
what
we
and
we
want
to
support
it
as
much
as
possible,
so
meaning
that
so
now
it's
loading
and
what
there
is
an
issue
that
has
been
included
in
this
print.
A
That
one
of
that
file
is
not
present
chase
should
include
udi
based
dev
container
in
in
the
workspace.
That
means
that
when
the
workspace
starts,
there
will
be
udi
so
based
images,
so
meaning,
if
you
go
to
the
udi
that
are
defined
at
somewhere.
A
A
Yeah,
so
it's
like
the
if
you're
not
familiar
with
developer
images-
let's
just
go
here,
so
you
have.
The
lottery.
Image
is
based
on
the
developer,
so
the
developer
universal
image
is
the
base
image.
Is
this
one
that
has
all
the
these
command
line
tools
and
then
is,
as
also
on
top
of
that
base
image
the
universal
images
java
support,
scala
c
c,
plus
plus
php
node.js
go.net
rust?
A
What
we
want
is
that
we,
when,
when
there
is
no
left
file,
we
we
use
this
image
with
all
these
language
tool,
so
that
the
user
should
be
able
to
use
the
command
line
and
start
running
and
building
the
application
from
here.
But
then
the
second
thing
that
we
want
to
add
is
that.
A
A
That
is
now
the
things
where
we
are
putting
more
effort
today,
we
would
like
to
have
a
walkthrough
extension
for
the
dev
file,
so
if
you're
not
familiar
with
walkthrough
extensions
of
for
visa
circle,
these
are
like
the
some
walkthrough
that
allows
you.
So
it
provides
you
information
and
do
some
help
you
doing
some
changes
to
your
so
adding
like
that
file
will
be
a
perfect
example
of
a
wall
through
so
so.
This
is
the
the
idea,
so
the
the
the
vision
that
we
have
for
the
for
the
future.
A
We
want
them
to
land
in
their
ide,
so
where
they
can
see
the
code,
the
source
code,
they
can
open
a
shell
and
we
want
to
guide
them
through
a
walkthrough
saying,
okay,
it
looks
like
you,
don't
have
that
file,
so
we
can
create
one
for
you
or
you
can
edit
that
one
automatically
so
with,
and
we
we
believe
that
this
is
where
users
developers
should
edit
their
dev
file,
not
in
the
in
the
dashboard.
A
We
have
removed,
remove
it
from
here,
because
we
want
users
to
be
able
to
edit
it
in
front
here
from
visas
to
a
code
from
intellij,
not
from
the
dashboard,
so
because
otherwise
you
you
are
in
your
ide,
you
want
to
change
something.
You
need
to
go
back
to
the
dashboard,
and
this
is
wrong.
So
you
you
want
to
change
something
you
are
in
your
ide,
you
change
your
configuration
and
you
just
reload
your
workspace.
A
So
that's
what
I
wanted
to
to
talk
about
so
explaining
why
so
we
don't
have
this
tab
anymore,.
B
Yes,
oh
so
it
was
mainly
rised
by
first
and
maybe
not,
firstly,
but
thanks
for
this
topic,
because
it's
significant
changes
which
maximus
young
overcoat
engineer,
found
and
tries
it
internally
and
from
from
your
explanation
now,
it's
clear
why
the
changes
was
done,
and
I
am
it's
it's
interesting
to
hear
that
it
was
not
so
popular
because
if,
if
you
ask
me,
I
I
use
this
several
times
at
least
just
to
when
I
have
the
file
wrote
the
file
just
copy
paste
it
and
that's
all
and
voila.
B
I
have
workspace
now,
with
the
one
workspace
limitation
on
devs
and
box,
we
will
have
some,
let's
say
miss
how
to
say
no,
it
would
not
so
convenient,
because
user
will
need
to
start
workspace
from
from
factory.
You
said
that
there
is
a
wrap,
always
list
of
possible
examples
here,
so
user
should
go
to
there
and
start
workspace
from
there.
No.
A
No
so
yeah!
No,
I
mean
if
you
want
to
start
workspace
now,
instead
of
creating
your
dev
file,
you
just
you
should
just
copy
paste
the
git
repository,
so
as
I
as
I
showed
before,
so
you
you
take
the
so.
This
is
my
example.
Git
repository
I
take
the
url.
I
put
it
here
and
I
say,
create
an
open.
You
should
not
start
from
any
example
or
nothing
so
just
do
create
an
open
you
go
here.
You
have
your
workspace
running
under
a
universal
developer
image.
B
The
first
user
should
have
a
link
to
that
sorry,
you
should
have
a
link
to
the
repo
I
mean
to
paste
in
that
field
so,
and
you
said
that
user
should
know
which
udi
image
to
select.
Yes,
it
wasn't
clear
for
me,
friendly
speaking
how
user
can
do
it
simply,
and
you
said
that
there
will
be
some
guidance
later
something
in
dashboard
which
will
help
user
to
select
proper
ugi
or
construct
the
file
yeah.
A
No,
no
udi
udi
will
will
be,
will
be
there
by
default.
So
you
will,
you
will
have
udi
by
default,
so
you
I
mean
you
copy
the
url
of
the
git
repository
here.
You
click
create
an
open,
and
then
it
opens
a
workspace
based
on
udi,
because
you
don't
have
any
so
we
need
to
select
the
default
image
and
the
default
image
is
the
universal
developer
image.
A
B
A
Yeah
I
mean
you,
you
have
workspace
samples
that
so
if
I
start
like
java
springboot
for
example,
here
I
will
have
an
example
that
has
already
that
file
in
it
or
that
can
be
so.
The
the
use
case
that
you
want
is
something
that
doesn't
have
a
source
code,
neither
right
so
maybe
like
you.
You
would
like
to
have
something
completely
empty.
B
A
Yeah,
I
think
this
is
so
honestly,
so
this
is
something
that,
just
last
week
a
customer
were
asking
was
asking
for
that
because
they
they
say.
Okay,
I
want
just
to
start
from
an
empty
ide,
and
then
I
I
do
everything
from
the
id.
So
I
start
I
do
like.
I
select
one
repository
and
then
I
add
multiple
repositories,
because
I
want
to
work
with
multiple
ones.
A
I
think
it's
it's.
We
need
to
think
what's
the
best
ui
like,
maybe
if
you
we
could
have
like
here,
leave
it
open
to
just
create
an
empty,
an
empty
workspace.
I
don't
know,
but
definitely
that's
something
that
it's
different
from
this
custom
workspace.
This
one
was
to
make
a
workspace
that,
as
for
that
source
code,
that
plugins
etc,
so
the
the
functionality
that
you
are
asking
like
empty
ide
yeah.
That
was
something
that
you
could
not
do
with
with
this.
B
So
what
do
you
think
about
that
case
to
let
users
change
your
space
name
after
workspace
creation.
B
C
A
So
you
know
it
will
be
used
as
prefix
and
then
the
suffix
will.
So
I
don't
know.
Maybe
that's
that's
like
a
workaround,
but
I
think
that's
a
good,
that's
a
good
thing.
So
maybe
it's
an
issue
that
you
we
should
create
like
being
able
to
add
it
easily
renaming
easily
yeah.
B
Create
it
from
samples
even
more
let's
say
I
have
factory,
and
when
I
I
tried
to
open
several
workspace
from
the
same
factory
link
and
there
is
already
existed
workspace
created
previously,
so
it
just
redirected
into
existing
workspace.
I
can't
create
several
workspaces
from
the
same
factory
link.
Oh.
D
A
Yeah,
so
thanks
also
dimitrov,
that's
again
excellent
feedback,
because
I
don't
think
we
have
communicated
a
lot
about
that,
but
this
has
been
done
by
on
purpose
because
we
got
so
because
something
is
as
we
are
used
to
use
che
since
a
few
years
we
have
been
using
it
and
we're
used
to
these
things,
and
but
the
feedback
that
we
got
from
a
few
key
person
we
have
been
asking
is
that
when
they
click
on
the
factory
link,
they
will
they
expect
the
the
previous
workspace
that
they
just
created
to
be
reopened.
A
They
do
not
expect
a
new
workspace,
so
we
made
the
default.
Yes,
we
made
the
default
behavior
to
be
to
always
reopen
the
existing
one
and
not
to
create
a
new
one,
but
so
this
is
not
like
the
so
that
can
be
overridden
now
and
it's
like
a
parameter
of
the
factory
link.
So
it's
the
parameter
is
new.
A
It
can
be.
It's
by
default
is
true.
So
sorry,
it's
false,
but
if
you
specify
new,
it
will
start
always
a
new
workspace.
A
This
was
something
that
I
explained
well
in
the
in
the
blog
post
that
we
that
he
wrote
a
few
months
ago
blog.
I
think
it's.
A
A
This
is
this
is
really
something
that
we
got
from
the
feedback
from
from
from
users
that
are
not
like
the
one
that
are
I've
been
using
chef
for
a
few
years,
as
we
have
been
doing,
and
they
were
really
that
that's
that's
a
behavior
that
they're
not
expecting
and
yeah
that
that
was
their
feedback
and
that's
what
we.
So
that's
the
change
that
so
that
this
is
done
because
of
that.
B
A
No,
I
think
it's
it's
really
the
url
right,
the
it's
not
it's
like
the
yeah,
if
you,
if
you
use
this
url
here
or
starting
a
workspace
every
time
you
click
on
this
url,
you
use
that
url
you'll
always
get
the
same,
is
the
same
workspace
if
the
git
repository
change,
but
the
name
of
the
in
the
dev
file,
you
get
the
same
name
yeah.
The
name
in
the
dev
file
is
the
same.
You
will
have
a
new
workspace.
A
C
A
A
B
Specified
specified
by
name
in
all
samples
in
create
workspace
as
far
as
you
know,
so
they
will
be.
They.
A
A
A
It
doesn't
look
like
it's
something
that
don't
allow
users
to
adopt
che.
There
are
other
things
like
the
integration
with
git
services
that
are
frustrating
users.
Today
there
are
other
things
like
the
failure
during
a
startup
after
they
have
been
waiting
for
three
minutes,
because
volumes
cannot
be
mounted
or.
A
Yeah
or
when
you
like,
a
user,
put
an
image
that
is
not
terminating
and
we
we're
not.
So
if
the
you,
the
image
is
terminating,
the
the
workspace
will
fail
to
start,
and
this
is
really
frustrating.
So
we
have
a
lot
of
things
that
are
really
frustrating,
but
from
the
name
of
the
dev
file,
something
that
usually
we
don't
really
get,
doesn't
look
like.
Those
are
critical
problems
for
users,
okay,
so.
A
If
you
have
any
anything,
you
want
to
discuss,
let's
create
an
issue
and
discuss
about
that
and
involve
others,
because
I
mean
I've
as
mentioned
those
decisions
have
been
taken
because
we
have
heard
so
reels
for
customers
supports
pms.
These
are
also
that
provide
us
those
feedback
and
we
have
reacted
to
those
feedback.
B
B
B
A
Yeah,
that's
yeah.
Can
you
so
yeah?
Would
you
mind
creating
an
issue
about
that?
Because
I
think
you
have
already
a
lot
of
a
few,
a
few
items
that
you
can
add
to
that
list
because
that's
that's
kind
of
the
documentation
issue
so.
B
Yeah
we
have
release
notes.
For
example,
do
you
think
it's
about
release
notes,
check
text,
yeah.
A
Yes,
yes,
that's
that's
something
but
yeah
just
create
an
issue,
and
then
we
we
can.
We
can
discuss
with
documentation
team
where
this
should
should
live,
but
I
think
it's
a
good.
It's
a
good
idea.
D
Over
there,
yes,
I'm
here
yeah,
I
noticed
sorry
it's
my
first
meeting,
I
I'm
joining.
I
had
great
issues
and
you
proposed
that
I
joined
this
meeting.
Thank
you
for
that.
I
noticed
that
it's
being
recorded.
Yes,
are
these
recordings
available
or
where.
A
A
Yeah
anyway,
thanks
for
for
joining,
I
hope
it
was
interesting
and.
D
A
So
here
is
the
so
the
the
link
to
the
to
the
wiki
that
should
have
recordings
yeah
of
past
sessions
and
don't
hesitate
next
time
to
to
add
the
topic
so
for
next
week.
If
you
would
like
to
discuss
about
something
particular
so
here
we
have
mainly
the
older
the
development
team,
so
yeah
you
can
get
answer
to
anything
great.