►
From YouTube: 2022 04 28 Docs Office Hours
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
A
A
A
A
Two
to
three
existing
ui
regressions.
That
worry
me.
A
Exactly
I
agree
with
that:
we
we
should
not
have
the
the
the
flawed
expectation.
I
can
bring
up
that
jira
so
that
we
can
see
it.
We
should
not
have
the
flawed
expectation
for
me
at
least,
that
all
ux
regressions
must
be
fixed,
not
even
close.
It's
this.
This
set
shows
hey.
There
are
16,
but
of
those
16.
A
Many
of
them
were
not
reported
until
well.
Let's
see
roughly
half
are
in
in
the
reported
in
2021
or
earlier
so
and
yeah.
So
it's
at
least
one-third
are
are
very
old,
and
I
don't.
I
don't
see
a
compelling
reason
that
we
must
fix
those.
I
agree
it's
just
for
me.
There
are
a
few
here
this
one,
for
instance
the
credentials
pop-up.
A
A
C
I
haven't
seen
anything
that
went
against
what
I
wanted
to
do,
so
it's
not
really
easy
at
first,
but
once
you've
done
one
translation,
then
it's
okay.
C
A
A
Okay,
so
if
I
click
here,
I
should
see
here
it
is
this:
is
your
proposed
french
translation.
A
B
B
C
B
Yeah
and
currently
we
have
set
it
up
that
only
fully
translated
and
approved
files
end
up
as
per
request
on
github,
but
you
don't
have
to
select
the
files
you
want,
as
per
request
crawling
automatically
submits
fully
translated
files.
We
are
using
an
integration
with
github
actions
here,
running
cronbase,
every
12
hours.
A
Exactly
and
and
so
so
we
do
need
someone
else
who's
assigned
now
for
purposes
of
this
exercise,
I
bet
alex
you're
already
a
proofreader
for
for
design
library.
Aren't
you
yes,
so
we
could
have
alex,
approve
it
and
within
12
hours
a
pull
request
will
be
submitted
based
on
your
well
or
I
think
these
are
these
files
completely
translated.
That
was
a
piece
I
didn't
know.
Just
one
index.
B
A
A
A
B
B
A
Highlights
is
okay,
so
how
would
we
flag
this
as
oh?
I
want
to
say
that
I
can
approve
this
one,
because
that
makes
sense,
but
this
other
one
I
absolutely
should
not
approve,
because
because
it's
it's
got
an
interesting
problem.
How
do
is
there
a
way
I
can
can
describe
that
can
say
here.
Hey
take
another
look
at
this
bruno.
B
A
A
B
Yeah,
I'm
currently
in
the
process
of
writing
jenkins
io
block
article
or,
however,
you
want
to
call
that
how
to
integrate
crowden
with
github
actions,
just
as
a
little
recap,
we
could
likely
publish
after
the
online
meetup,
so
people
have
something
in
text
form
because
it's
most
most
mostly
like
most
likely
something
I
prefer,
and
this
is
definitely
something
I
should
include.
I
guess
to
not
have
to
not
end
up
with
actually
translated
code.
C
Oh
right,
there
is
a
version
I
corrected
just
below.
Yes,
no,
no,
no,
but
yeah.
C
I'm
not
so
sure
it's
mine,
it
looks
like
it's
yours.
A
B
A
A
A
B
B
A
Well,
and-
and
I
can
actually
show
that
for
for
purposes
of
our
illustration
here-
I
can
show
it
with
one
or
the
other
we
have
is
it
the
schedule.
Build
plug-in
is
the
one
that
we
have
in
yes,
yeah,
so
how
about?
If
let
you
go
ahead
and
trigger
it,
I'm
going
to
take
screen
sharing
back
and
I'm
going
to
share
my
screen
and
do
the
same
thing,
but
on
a
different
plug-in
that
way,
we've
got
a
one
more
reminder
of
it.
A
We
go
to
dot
co,
dot,
github,
slash,
workflows,
crowdin.yml,
and
here
is
the
the
the
the
thing
that
that
needs
to
be
added,
and
it's
boilerplate
this.
It
is
the
same
for
each
repository.
If
I
remember
correctly,
there
wasn't
anything
we
had
to
do
the
one
thing
that
makes
it
specific
to
a
repository.
Is
we
had
to
add
a
secret
to
this
repository
for
this
thing
or
yeah?
It
was
crowded
personal
token,
so,
and
we've
got
a
recording
of
how
to
do
that
in
a
previous
office
hours.
C
Okay,
I'll
have
a
look
at
it
and
is
it
a
template
which
is
already
existing
within
github,
or
do
you
have
to
create
it
from
scratch
or
copy
paste
from
another
repo
or
something.
A
A
A
A
B
A
A
A
B
A
A
A
B
Yeah
I
mean
our
current
integration
doesn't
submit,
approved,
strings
back
to
crowd,
and
so
correcting
here
would
basically
work
okay,
but
the
preferred
approach
would
likely
be
to
figure
out.
Why
does
that
and
set
up
a
way
to
stop
doing
that,
because
that
is
basically
nonsense
here,
because
jelly
doesn't
work
like
that.
B
A
A
A
B
Yeah,
I
will
take
a
look
and
try
to
figure
out
why
it
does
that
until
next
stock
software
session
guess
likely
something
that
we
didn't
think
about
yet
or
something
we
have
badly
configured
and
has
enabled
us
default
setting.
I
don't
know
because
that
is
the
actual,
only
occasion
that
it
happened
here,
I'm
not
aware
of
it
being
somewhere
else
yet,
or
at
least
I
didn't
notice
it
in
a
pull
request.
A
A
B
B
Yeah,
currently,
we
are
using
the
enhancement
label
for
it,
but
I
proposed
a
pull
request
to
the
gita
repository
and
to
the
workflow
actions
to
create
a
new
localization
label
for
it
using
the
globe
emoji
or
something.
So
we
can
have
a
dedicated
label
to
separate
non-code
changes
from
often
code
changes
that
are
used
for
enhancements.