►
From YouTube: Che Community Meeting February 14, 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
we
are
good.
This
is
the
chi
community
meeting
from
february
14
2022
and
there
are
no
releases
today
and
only
two
topics
in
on
the
agenda.
So
elia.
It's
your
turn.
B
Yeah
so
folks,
you
might
have
known
that
we
are
having
the
list
of
articles
for
upcoming
releases
related
to
dev
workspaces,
so
one
of
the
blog
posts
that
we're
going
to
publish
this
week
is
already
out
and
in
order
to
have
this
in
place,
we
need
two
things.
So,
first
of
all,
we
need
the
docs
approval
before
so
for
reese,
will
you
be
able
to
review
the
blog
post
by
that
time?
B
I
already
think
you
folks,
on
the
shadows,
made
slack
so
just
wondering
what
is
your
plan
with
the
review.
A
So
the
review
it's
yeah
jana
it's.
It
will
be
our
very
first
very
first
task
in
the
world.
It
will
be
to
review
this
blog
post.
So
I
see
I
get.
I
gave
the
task
to
her
today
and
tomorrow.
A
It's
happening
tomorrow,
basically
and
and
we'll
see,
that's
our
first
first
contribution
to
the
project
so
welcome
jana.
B
That's
great,
but
I
just
wondering
so:
do
we
have
some
eta
for
the.
C
B
Because
you
know,
if
we
are
going
to
publish
it
on
pump
day,
then
we
we
need
to
get
a
review
before
this
right.
Okay,
if
we,
if
we
need
more
time,
then
we
can,
you
know,
shift.
I
don't
know
monday
next
monday.
A
Oh
yeah
just
just
join
the
call,
so
that's
perfect
for
the
blog
reviews.
We
just
we
just
you
don't
test.
We
just
do
a
language
review.
Fifty
would
show.
So
I
believe
that's
that's
fine
that
she
should
be
able
to
to
manage
it
in
one
day,
but
I
will
keep
you
posted
tomorrow
enough
day.
It
depends
if
there
are
blocking
things
on
the
on
the
road,
but
I
guess
let's
see
that's
our
first
contribution,
so
I
I
don't.
I
don't
know.
I
hope
it's
go.
It's
okay,.
B
Okay
yeah,
so
please
just
let
us
know,
because
if
we
will
not
get
the
review
like
tomorrow,
then
we'll
need
to.
You
know,
reschedule
the
the
posting
time
right.
So
that
is
the
first
thing,
so
we
need
to
review
from
the
docs
team.
I
already
did
both
verification
and
the
language
review,
so
I
approved
the
pull
request
plus
one
from
my
end,
the
only
thing
that
is
currently
missing
and
that
I
wanted
to
discuss
with
you
folks.
D
B
Is
a
situation
with
the
pull
request,
plugin
and
the
limitation
of
the
os
apps
on
the
changemaker
repository?
Technically,
it's
not
possible
to
approve
the
pull
request
from
the
ids
find
the
details
in
the
in
the
review.
It's
mostly
a
question
to
floron
and
mario.
So
folks,
what
do
you
think?
Can
we
disable
this
osap
access
restriction
for
chain
creator?
B
I'm
not
sure
about
all
the
other
orgs
for
sure
we
have
this
for
chairwork
and
for
change
better.
I
think
that
it
shouldn't
be
the
case
for
regular
repository.
We
can.
We
can
check
it,
but
even
even
if
there
are
restrictions
right,
even
if
there
are
restrictions
by
default.
So
this
means
we
will
not
be
able
to
showcase
the
it
helpful
review,
pull
request,
review
flow
with
with
the
regular
settings.
So
it's
kind
of
strange
right.
B
Yeah,
it's
I
mean
so
we
are
using
different
os
app
provider
for,
for
example,
for
workspaces
openshift.com,
but
it's
the
same
host
provider.
I
think
we
use
it
for
the.
This
is
the
one
we
use
like
internally,
but
it
doesn't
really
matter
because
you
know.
D
B
B
E
That
only
the
dog
foodie
instance
was
using
the
chain
kubata
os
app.
B
Yeah,
that's
true,
that's
true,
because
on
on,
for
example,
workspaces
openshift.com
is
set
up
for,
I
think
red
hat
developer,
so
I
mean
the
secret
right
with
the
access
it.
B
C
I
checked
the
document
and
probably
the
main
question
is
well
just
for
you
to
understand.
I
come
from
a
journalistic
and
a
little
bit
of
copywriting
background.
C
The
blog
post
has
a
very
sort
of
friendly
informal
style.
Is
that
something
that
you
want
to
keep?
B
B
I
don't
know
how
it's
going
to
work
actually,
so
it's
up
to
fabrice
to
decide
like
the
exact
procedure,
but
you
might
have
noticed
that
we
are,
for
example,
reusing
the
placeholders,
so
we
don't
place
like
the
project
or
product
name.
We
have
a
placeholder
like
broad
short,
which
stands
for
eclipse,
chair
or
authority
workspaces,
depending
on
on
the
on
the
context
right.
B
So
the
main
goal
is
basically
to
have
the
blog
post
and
have
it
eventually
transformed
to
the
to
the
documentation
of
the
product
and
project
by
the
documentation
team.
So
to
answer.
B
Like
about
the
style
thing,
if
you
think
that
some
styles
are
not
acceptable
or
there
will
be
problematic
to
remove
from
the
from
the
blog
post
during
the
transformation
to
the
actual
project
or
product
documentation,
then
yeah
you
should.
You
know,
provide
suggestions.
C
If
I
understand
it
correctly,
the
the
moment
we
transform
it,
it's
gonna
be
quite
formal
right,
like
it's
going
by
the
ibm
style
and
it's
sort
of
very
dry,
very
functional.
A
Very
formal,
yes
and
the
block
the
blog
post
is
is
more
relaxed
right.
It's
our
on
the
blog
post.
We
are.
We
are
filtering
for
our
for
in
english,
so
mainly
for
grammar
and
english
and
who
are
not
so
formal
and.
C
Perfect,
what's
going
to
be
happening
when
I
add
some
comments
and
some
possible
changes,
okay,
I
was
also
wondering
because
that's
actually
something
that's
in
the
very
beginning.
C
It
says
as
long
as
you're,
using
a
supported
web
browser
like
google
chrome.
What
are
the
other
ones.
B
Chrome
full
support,
plus,
I
think
we
have
a
minimal
file
firefox
in
in
place.
So
but
it's
like
kind
of
you
know,
project
project
limitations.
We
have
an
issue
for,
for
example,
safari
support.
Let's
do
neither
project,
no
product
work
against.
C
Or
fabrice,
do
you
think
that
maybe
it's
going
to
be
better?
If
we
have
a
little
meeting
tomorrow,
where
I
give
you
these
questions,
which
I
guess
you
will
be
able
to
answer,
I
can
do
that.
Yes,
okay,
good,
then
the
contents
I
will
discuss
with
fabrice
and
yeah
I
it
looks
like
very
nicely
written.
C
I
think
that
I'm
just
gonna
tighten
it
up
a
little
bit
to
make
it
like
flow
even
better,
and
the
big
work
then,
is
going
to
be
the
transformation,
because
that's
also
going
to
be
like
basically
com
yeah,
changing
the
the
style
quite
a
bit.
That's
something
that
is
like
that's
gonna,
that's
gonna
be
done!
That
shouldn't
be
a
really
much
of
a
problem.
B
B
Absolutely
and
just
for
follow-up
we
have
in
this
blog
post,
we
have
an
issue
published
into
mario
created
and
in
the
table.
You
should
be
able
to
find
the
link
to
the
actual
jira
that
that
is
meant
to
be
done
for
this
transformation.
B
Thank
you,
and
so
I
think
that
we
pretty
much
discussed
the
review
process,
but
about
the
actual
problem
with
those.
E
B
I
think
that
probably
it
would
be
better
to
so
unless
there
are
some
particular
security
concerns,
I'm
not
aware
of.
I
would
probably
allow
it
for
pretty
much
any
os
app,
because
I
mean
it's
change
beta
project,
it's
open
for
so
it's
all,
obviously
open
source
and
the
only
folks
that
can
commit
and
contribute
with
their.
You
know.
Github
tokens
are
the
emitters
right,
so
I
don't
see
any
like
violations.
B
Okay,
yeah,
that's,
but
I
mean
for
me
what
what
is
important,
probably
that
it
would
work
for
workspaces
of
achieve.com,
because
in
these
blog
posts
we
provide
both
the
file
version
one
and
default
version
two.
B
So
so
that
you
know
even
even
now
you,
even
though
the
article
is
for
devworkspace
engine
user
will
be
able
to
try
it
even
now
on
workspaces
of
tube.com.
So
for
me.
B
But
my
point
is
that
if
someone
will
deploy
eclipse
chair
on
their
own
infrastructure
and
will
try
the
very
same
steps
on
on
their
own
instance,
I
think
it
will
fail
with
the
same
so
the
approvals
that
will
fail.
But
maybe
it's
fine,
maybe
maybe
it's
okay,
that
they
it's
exampled
and
they
will
get.
B
A
Then
next
topic
is
a
very
short
one
and
I'm
on
pto
the
last
day
of
february.
B
Yeah,
for
me,
it
would
be
better
if
you
handle
it
to
someone
from
the
dog's
team.
I
would.
I
would
start
my
moderation
from
the
march
4th
unless.