►
From YouTube: Release Group Community Office Hours 2023-01-31
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
B
Er
in
the
release
group
and
I'm
based
in
Munich
Germany
Andrew,
why
wouldn't
you
go
next.
C
Hi
everyone,
I'm
Andrew
I'm,
also
a
senior
front-end
engineer
and
also
based
in
Toronto
Canada.
Let's
go
to
Amish.
D
Hey
everyone,
my
name
is
Emmett
and
I
am
based
in
Berlin
Germany
I'm,
also
the
senior
back
end
on
the
release
team.
So,
like
every
other
back-end
engineer
here,
you
want
to
go
next.
E
F
Hey
everyone,
yeah
I'm,
sorry,
I'm,
an
excellent
engineer
manager
on
team.
My
name
is
lat.
I
am
located
in
the
Netherlands
in
Amsterdam
and
over
to
you,
Alan.
B
I'm
Alan
cook
I'm
a
senior
backing
engineer
the
police
team
and
I'm
in
Kentucky,
USA
I
think
that's
it
for
gitlab
people
right.
H
Good
morning,
good
morning
from
the
central
time
zone
in
the
United
States,
my
name
is
Matt
dental
and
I'm
your
partner
Channel
pollutants,
architect
for
credit,
Lab,
Partners
and
I'm,
based
in
St
Paul
Minnesota
right
now,
I'm
in
Minneapolis,
Minnesota,
USA.
G
Cool
now
we
can
pass
it
over
to
some
of
our
community
members
on
the
call
to
introduce
themselves
Missy.
Do
you
want
to
go
first
sure.
I
Hi
everyone,
my
name,
is
Missy
I
am
based
out
of
the
Boston
area,
but
often
travel
a
lot
as
a
nomad
I
started,
contributing
to
git
lab
a
few
months
ago
and
I'm
working
on
getting
my
first
Mr
ready.
Hopefully
this
week,
I'm
feeling
pretty
good
about
it.
So
hello,
everyone
and
I'll
pass
to
who's
left
here.
G
G
Cool,
well
welcome
glad
to
have
you
here
and
I
think
the
last
person
is
in
Tully.
If
you
want
to
introduce
yourself
as
well
on
the
chat
or
over
Micah,
either
works.
J
Hello
I'm
Anna,
Tully
I'm,
based
in
Minsk
Belarus
I,
was
like
MVP
for
doing
some
documentation
Mrs
a
few
releases
ago,
I'm
hanging
out
mostly
to
like
making
practice
of
my
skills,
so
I
can
find
a
job
finally
somewhere.
So
yeah
I'm,
not
sure
that
if
this
group
is
for
release
of
gitlab
or
the
release
tool
that
people
use
to
make
releases
so
would
be
interested
to
to
know
this
in
in
an
intro.
G
So,
with
a
little
intro
of
this
I
noticed
we
had
someone
else
join
so
I'll,
let
them
introduce
after,
but
this
is
the
office
hours
for
the
release
team.
So
we
kind
of
work
on
the
release
features
within
gitlab,
so
around,
like
environments
deployments,
releases,
feature
Flags,
so
it's
a
team
working
on
those
tools
within
gitlab
not
to
the
team,
releasing
different
portions
of
git
lab.
If
that
answers
your
question.
G
And
it
looks
like
we
had
one
other
person
join
bavishya
if
you'd
like
to
introduce
yourself
as
well
we're
just
going
around
doing
introductions
and
you
can
do
that
in
the
zoom
chat
or
over
Mike.
G
Cool
well
I
guess
we
can
get
started
now,
I
think
main
top
before
we
get
into
the
main
topic.
Is
there
any
other
questions?
People
have
about
the
release
office
hours
or
anything
you
wanted
to
ask
kind
of
before
we
jumped
in.
E
The
controller
implementation
we
are
going
to
walk
through
the
presentation
that
I've
put
forward
along
with
code
reviews
and
local
runs
so
yeah.
Let
me
start
my
screen.
Sharing.
E
Yeah
as
if
you
are
able
to
see
my
screen,
then
the
President
should
just
give
you
something
to
that
great,
so
yeah,
I'm
balakumar
and
from
I'm,
seeing
a
backend
engineer
with
the
release
group
and
for
today's
Community
officers.
We
are
going
to
discuss
controller
implementations,
so
just
classified
the
entire
presentation
into
three
categories
based
on
what
most
of
our
community
contributors
expertise
belong
to.
E
So
roughly
it
will
be
a
simple
category
and
then
a
moderate
and
then
an
advanced
for
each
of
these
categories,
just
identified
issues
that
we
have
worked
in
the
past,
along
with
an
MR
which
we'll
walk
through
and
then
do
some
local
drugs
to
understand
what
that
code
piece
of
code
does
yeah
and
based
on
time,
I'm
planning
to
do
simple
and
modern
today
and
if
time
permits
the
advance
that
we
just
push
it
to.
The
next
step
is
us,
starting
with
with
the
simple
implementation.
E
So
we
that
there
was
an
existing
issue
feel
free
to
open
those
links,
I've
already
populated
those.
So
just
going
ahead
and
sharing
that
particular
program
now
which
just
details
for
that.
E
So
this
is
the
issue
where,
as
as
a
team,
we
wanted
to
log
additional
information
from
the
request
that
I've
been
getting
into
this
controller
and
yeah.
So
to
be
specific,
we
wanted
to
log
the
search
parameters
that
was
getting
into
the
environments
controller.
So
before
we
beat
the
this
is
the
Mr.
Let
us
see
what
this
does
in
the
URL,
so
this
is
the
cloud.
Local
and
I
have
a
test
repository,
so
I'm,
just
visiting
the
environments
page
just
give
a
few
seconds
for
it
to
load.
E
E
So
that
it
just
helps
with
identifying
the
core
workflows
that
we
are
doing
so
yeah,
the
page
is
loaded,
and
these
are
the
environments
that
are
available
for
this
project
and
let
us.
A
E
E
Environment's
controller
and
for
people
not
familiar
with
the
code,
this
might
sound
overwhelming,
so
we
just
break
it
down,
but
yeah
it
just
starts.
This
is
the
environment
controller
and
we
have
a
bunch
of
actions
that
this
controller
does
so
from
the
UI.
How
do
I
backtrack
to
identify
where
this
controller
and
data
file
locates
so
I
just
visited
that
page
right?
So
in
your
development,
Json
log
you'll
be
able
to
find
the
particular
controller
and
the
action
that
was
called
when
I
opened
that
UI.
E
The
controller
looks
just
go
back
to
the
window
and
wanted
to
drill
down
the
finer
details
there
yeah
so.
A
E
E
F
E
Level
it
this
controller,
handles
a
bunch
of
authentications
other
other
specific
requirements,
doing
a
bunch
of
checks,
filters
and
stuff
like
that,
and
most
often
we
won't
touch
the
application
controller.
So
we
just
generate
from
that
and
for
this
particular
issue
we
are
going
to
extend
on
top
of
this
particular
method,
which
is
already
existing.
E
We
wanted
to
append
some
extra
information
to
the
payload,
which
is
just
getting
locked
and
if
you're
wondering
what
the
super
does
so
we
we
are
using
the
log
rage
for
a
gem
which
does
the
structured
logging
that
we
see
in
the
application,
Json
logger.
E
And
yeah,
so
this
is
the
documentation
for
the
long
range,
and
that
gives
me
that
it
has
documentation
on
how
to
use
this
particular
method
so
that
we
love
extra
information.
So
the
gitlab
application
controller
is
extending
that
particular
feature
from
the
Lord
wage
and
if
we
notice
the
environment's
controller.
E
It's
calling
the
application
controller.
The
application
controller
enter,
calls
the
gem
implementation
for
this
particular
method,
so
I'll
just
so
that's
the
higher
level.
You
want
to
take
that
at
the
application
controller
and
then
on
top
of
that
he
did
have.
We
had
a
bunch
of
different
filters,
and
most
often
these
before
filters
are
used
to
handle
the
authorizations.
E
Adding
gitlab,
we
use
the
declarative
policies
framework
for
this
particular
authorizations
on
how
we
wanted
to
handle
authorizations.
E
E
A
E
E
A
E
E
E
E
E
E
Right
so
the
prompt
has
opened
so
I'm
just
going
to
modify
the
configuration
so
that
it
not
connects.
E
I'm
going
to
refresh
this
page
and
see
if
we,
if
a
breakpoint
is
working
foreign.
E
E
This
go
back
and
I
see
that
the
page
is
still
continuing.
It
has
moved
on
from
the
breakpoint
and
it
is
gone
to
the
next
set
of
program
lines
and
we
see
that
the
page
is
getting
loaded.
E
E
E
The
implementation
that
we
did
for
this
particular
simple
controller
enhancement
was
to
append
this
extra
information
which
was
coming
from
parents,
and
we
wanted
to
pass
it
on
to
the
log
range
payload
so
and
what
we
do
notice
is
we
were
using
snippet
called
as
feature
dot
enabled
and
a
symbol.
E
So
what
we're
doing
is
we
are
using
gitlab
feature
flags
that
we
are
using
in
development.
So
if
the
feature
flag
is
enabled
we
proceed
and
then
we
go
ahead
with
logging,
otherwise
we
just
want
it
and
of
course
this
we
are
ensuring
that
the
Paramount
was
present.
E
So
we
primarily
use
in
local
most
of
our
developers,
use
pressure
and
price.
Shell
is
the
interactive
debugger
from
that
that
works
on
top
of
multi-thread
adobe
environments
like
puma
and
sidekick.
So
we
always
prefer
that.
So
this
is
a
gym
and
it
is
made
built
by
one
of
our
gitlab
team
members
and
the
teachers
brings
in
the
features
of
pry
into
a
nice
practitioner
and.
A
E
Are
of
course,
other
Ruby
debuggers
like
Bible
pry
and
all
of
that
and
if
in
the
prompt,
if
you
wanted
to
add
shortcuts
and
stuff
like
that
or
move
by
Stacks
stack
frames
on
how
we
do
with
General
remote
debuggers
or
two
steps
and
commands
are
listed
over
interest
documentation
so
yeah
primarily
for
development.
We
use
the
private
partial
and
using
it
is
we
just
very
straightforward
on
the
particular
big
one
on
the
line
before
that.
We
wanted
to
add
a
big
point.
E
Just
add
this
snippet
and
then
you
open
the
internet,
and
you
should
the
Ruby
processed
to
delay
the
information
to
the
partial
process
and
you
should
be
able
to
keep
up,
for
example,
when
I
go
well
for
the
for
adding
the
breakpoint
to
this
line.
The
control
stops
here
and
I'll
be
able
to
view
the
request
contest
specific
to
this
particular
breakpoint.
So
let
me
just
go
through
them.
E
For
this
project
classes,
so
those
are
the
various
level
of
Deltas
that
we
can
do
and
yeah
I
think
that
that
just
explains
any
questions.
E
E
E
File
and
most
of
it
is
self
explanatory,
we
should
have
a
name
for
a
future
plugin.
The
details
are
required,
which
is
why
URL
roll
out?
You
are
my
student
that
we
wanted
to
close
this
out,
and-
and
this
is
important
before
we
turn
on
a
feature
flag,
it
is
absolutely
necessary
that
the
default
enable
state
of
it
is
always
false.
E
So,
just
having
this
yaml,
we
will
give
you
the
flexibility
to
use
the
snippet
called
as
which
is
not
enabled
and
environment
search.
Logic
corresponds
to
the
name
that
we
have
at
the
yaml
file.
E
And
internally
it
uses
the
render
storage,
so
the
gitlab
developers
have
access
to
uses
slack
and
we
rolled
out
in
faces
for
community
community
contributors.
You
may
not
have
access
but
yeah
if
the
feature
flag
is
recommended
in
development
or
it
was
suggested
by
the
rivers
or
maintenance
which
it's
good
to
correlate
or
work
along
with
your
you
as
a
maintenance
to
that
team.
E
E
E
E
So
this
is
a
straightforward
thing.
Any
questions
here.
I
E
Contributors
will
not
have
direct
access
to
it,
but
yeah.
You
primarily
want
someone
from
gitlab
to
enable
that
and
roll
out
into
roll
it
out
in
faces
and
give
you
that
information.
So
for
that,
what
we
usually
do
is
we
lab
a
rollout
issue
and
most
of
these
rollout
issues
are
publicly
available
and
the
gitlab
team
member
will
enable
that
and
slide.
So
we
have
slackbot
commands
to
do
that
and
and
then
the
progress
will
be
usually
updated
in
this
particular
rollout
issue.
E
E
Out
you
can
just
go
through
so
you'll
have.
E
Yep
so
yeah,
this
is
what
we
did.
We
appended
this
extra
information
and
with
the
love
of
the
feature
flag
and
moving
on
to
the
specs.
We
wanted
to
ensure
that
we
have
a
test
case
for
it.
E
So
in
this
particular
context,
in
order
to
check
do
this
test
without
the
flag,
so
we
have
a
global
helper
to
do
that
which
is
called
as
top
feature
Flags.
So
all.
E
The
documentation
which
is
available,
the
link
that
is
there
in
the
presentation
so
for
the
first
context
we
tested
with
false
and
then
for
the
next
context.
We
set
it
to
to.
E
Let
us
start
with
this
right,
so
what
we
wanted
to
see
is
when
the
feature
flag
is
disabled.
We
do
not
want
to
log
the
extra
payload,
so
we
are
formed,
so
we
assert
those
using
expectations
that
the
aspect
framework
does
and
you
visit
the
search
page
and
we
just
for.
E
So
yeah,
this
is
how
we
usually
run
an
aspect
and
I
think
in
their
last
Community
officers
as
well.
I
think
I
meant
spend
a
great
great
amount
of
time
on
learning
aspects,
so
I'm
just
going
to
quickly
plans
over
it.
So
environments,
controllers,
fake-
and
this
is
the
line
number
1033.
C
E
E
E
Is
this
was
a
simple
iteration?
We
saw
how
the
controllers
exchange
from
the
application
controllers,
how
we
have
different
filters
for
ensuring
authorizations
and
the
other
high
level
question
details
that
we
wanted
to
ensure
and
then
using
the
debugger
using
feature
plugs
in
declare
development
and,
let's
take
so.
This
is
the.
E
So
if
you
wanted
to
see
what
how
the
aspect
is
running,
you
just
tell
the
test.log,
like
the
development
Json
Blog
the
test
as
well
as
just
do
yourself,
so
that
if
the
controller
is
listed
by
the
test
framework,
you
will
be
able
to
see
just
details
as
well,
so
yeah.
This
is
just
booting
up
the
process.
It's
going
to
move
forward
and
then
previously
this
data,
so.
J
Yeah
I
got
a
question
like
this
session
covered.
If
you
want
to
put
some
debug
information
for
the
glob
development
to
lock
some
information.
But
what,
if
I
want
to
log
my
releases
like?
Is
there
any
way
for
the
gitlab
to
collect
those
logs?
K
J
Yeah
like
when
I
deploy,
my
web
application,
I,
usually
like,
have
to
check
the
logs
if
deployment
was
good
and
if
it's
operating
and
for
that
I
need
to
deploy
elasticsearch
with
kibana
and
and
the
stuff.
So
I
was
wondering
if
gitlab
already
have
this
login
infrastructure
built
in.
E
E
E
J
Yeah
that
that's
that's
useful,
like
I,
can
reuse
the
login
infrastructure
of
gitlab.
If
I
like
deploying
my
application
but
yeah
I
was
I
was
looking
for
something
more
for
users
like
user
sites
for
login
integrated
in
GitHub,
but
this
could
be
useful
as
well.
Thanks.
F
F
Functionality
for
clients
right
now,
but
I
know
that
the
observability
team
works
on
some
Integrations,
including,
for
example,
centers.
So
you
can
log
your
errors
and
look
them
yeah.
You
see
them
in
the
gitlab
interface,
but
it's
all
in
development
right
now
and
yeah.
For
now
you
need
to
deploy
your
own
login
infrastructure.
E
If
there
are
no
questions
on
this
topic,
I
can
just
move
on
to
the
next
section,
which
deals
with
a
moderate
level
of
complexity,
on
building
on
top
of
a
controller.
So
yeah
I
don't
see
any
hands
there.
So.
E
So
earlier.
E
The
different
endpoints
for
each
of
these
formats
in
order
to
unify
so
that
is
this
issue,
describes
that
and.
E
C
F
E
A
E
So
these
two
endpoints
were
entering
Json
data
and
then
we
had
create
and
desktop,
which
performed
the
respective
thread
operation,
which
is
the
creation
and
Destroy
right.
E
And
in
git
lab,
we
we
wanted
to,
we
primarily
doesn't
have
do
not
recommend
having
a
different
formats
each
of
these
methods.
So
what
we
prefer
is
to
have
something
like.
E
So
yeah,
that
is
what
this
issue
describes
and
on
an
high
level.
We
see
that
it
is
expanding
from
the
application
controller.
We
have
before
reaction,
which
it
checks,
the
ability
or
the
policy
for
the
user
and
the
user
doesn't
have
access
each
one
doesn't
work.
B
E
The
team
members
or
the
attendees
to
start
with
us
to
see
the
endpoints
and
crowds
but
yeah
it
should
be
straightforward
thing.
It
just
list
out
what
this
particular
controller
does
the
end
for
institutions.
E
So
in
the
cloud
we
put
our
routes
inside
config
routes,
operations
and
as
I
said,
the
index
application
is
a
the
index.
Operation
is
performed
by
particular
part
in
the
URL
called
as
operations
and
for
the
environmental
syntax.
It's
operation,
slash
environments,.
F
E
E
E
And
then
go
to
the
operations
action
of
the
UR
field,
and
then
it
opens
the
operation,
control,
dashboard
and
things
are
still
loading
on
my
remote
control
to
see
a
bunch
of
activity.
E
E
The
front
end
is
still
loading,
so
I
just
turned
out
right,
so
operations.
Dashboard
main
function
is
to
get
a
high
level
activity
and
the
status
of
the
repositories
that
we
want
now.
The
projects
that
the
admin
wants
to
monitor
in
this
case,
I've
already
populated
digital
projects
and
I,
see
that
the
pipelines
is
passing,
and
likewise
we
have
an
the
environment
dashboard.
E
Where
for
a
bunch
of
projects,
we
will
monitor
the
various
environments
for
each
of
these
projects
so
for
the
flight
project,
I
had
the
production
institution
environment,
of
course,
I,
haven't,
deployed
them
and
for
this
project
called
registered
plate
I
have
a
development
environment.
E
So
this
is
what,
at
the
UI
of
that
controller,
looks
like.
E
E
E
So
we
got
the
HTML
response
where
we
have
a
bunch
of
JS
scripts
injected
and
it
made
an
Accenture
called
and
now
with
called
operations
environments.json
which
which
got
Json
response.
So
the
format
that
particular
response
was
handled
by
this
particular
piece
of
log
code,
where
we
serialize
S3
songs
the
projects
corresponding.
E
A
E
As
analyzer
thank
you
so
hey
gitlabs
for
most
of
the
page
index
pages
and
for
listing
purposes
we
use
the
serializers.
So
this
is
the
documentation
for
it
primarily
when
you
wanted
to
serialize
to
Json.
We
use
it
and
there
are
like
and
be
primarily
ignorant
the
grape
entities
for
our
serializers.
There
is
a
lot
of
advantages
of
using
the
serializers.
Instead
of
this
one
and
the
implementation
details
are
covered
in
this
documentation.
E
E
A
bunch
of
data
that
has
to
be
said
to
be
applied
and
for
for
most
of
these
corporations
like
create
and
Destroy
we
use
the
service
is
patented
and
services
are
nothing
but
a
simple
Ruby.
A
E
Ruby
object
is
just
a
simple
class
and
it
has
a
bunch
of
public
methods,
not
specifically
a
single
public
method
in
deep
Labs
context
and
when
it
moved
it,
it
just
returns
a
response.
So
if
we
look
at
the
create
method.
E
We
call
the
execute
and-
and
this
is
what
it
does
right
so
primarily
to
keep
a
model
still
and
to
to
abstract
away
the
crowd
operations.
We
use
the
service
classes.
C
E
Of
just
going
to
release
the
specs,
because.
A
E
E
And
another
thing
that
we
wanted
to
highlight
here
is
this
particular
control.
The
controller
is
residing
in
an
high
level,
folder
called
as
the
so
in
git
lab.
We
keep
our
code,
our
Enterprise
Edition,
specific
code
bases
or
the
code
corresponding
to
the
ultimate
tier
inside
the
ee
path.
So
there.
E
E
So
we
see
this
last
line
here,
which,
which
does
that-
and
we
see
that
there
is
no
ee
here
right
and
it's
my
search
for
environments
controller.
We
see
that
there
are
two
implementations
of
this
link
control,
the
Oneness
for
the
CE
edition
and
another
one
is
for
the
Enterprise
Edition.
If
I
go
to
the
Enterprise
Edition,
what
I
notice
is
is
having
some
extra
information
or
some
extra
details
with
specific
to
permissions.
E
Right,
but
this
controller
is
actually
using.
Some
of
those
is
actually
using
the
entire
code
that
is
available
in
the
front
seat.
And
if
you
wanted
that
to
be
generated,
we
allowed
to
ensure
that
we
always
prepare
mode
with
is
added
to
the
controller
to
the
CD
controller,
so
that
the
E
controller
can
use
that.
K
K
C
E
Is
what
I
wanted
to
cover
and
I
can
just
take
questions.
E
I
I
have
another
question:
I
don't
know
if
it
specifically
pertains
to
these
two
topics,
but
in
in
one
of
the
merge
requests
you
had
briefly
shown,
there
was
talk
of
pushing
something
to
a
staging
environment
and
doing
some
testing
on
that.
Is
that
something
that
community
members
should
think
about
when
they're
ready
to
ship
something
or
is
that
something
where
that
the
maintainers
would
do
on
behalf
of
us
after
an
MR
is
ready
or
is
just
testing
on
the
local
GDK
server
sufficient.
E
I
So
usually
like
in
in
my
work
when
I
am
ready
to
ship
something
I
ship
it
first
to
our
staging
environment,
I'll
test
it
locally
on,
like
my
local
server,
then
I'll
ship
it
to
staging
and
I'll
do
some
testing
in
there
before
I
ship
it
to
production?
Does
gitlab
do
something
similar
are
community
members
able
to
do
that
or
are
we
just
capped
at
testing
out
the
local
GDK
server,
but
can't
quite
go
to
the
staging
and
that's
something
that
maintainers
would
do.
E
Yeah,
so
we
most
of
our
developers
as
well
in
gitlab,
run
the
test
in
the
local
environment
for
the
features
that
we
wanted
to
idea
to
build
upon.
So
we
ensure
that
the
aspects
and
the
code
coverage
is
good
and
submit
an
MR,
and
the
Mr
runs
on
the
pipelines
corresponding
to
the
master
Branch,
where
we
have
the
where
we
can
resolve
much
conflicts.
So.
A
A
E
Particular
Branch
alone
on
a
staging
environment
and
test
it.
It
goes
to
the
master
back,
the
more
Japanese
the
master
is
and
the
main
branch
the
git
Labs
table
branch
is
deployed
into
various
environments.
It
progresses
like
staging
Canary,
staging
and
then
production
and
the
progress
of
of
all
those
stages
will
be
seen
in
a
mass
as
labels.
E
E
E
And
which,
which
does
the
population
on
when,
when
these
merges
happens
so
yeah?
So
you
see
here
right,
the
release
of
schools
bought
the
tax.
The
labels
on
the
particular
particular.
E
This
Mrs
made
so
as
a
developer.
We
just
worry
about
ensuring
that
the
pipelines
are
green
and
then
and
then
it
is
most
so
once
it
is
merged.
Based
on
these
labels,
we
can
go
to
this
particular
environment,
where
we
can
do
QA
testing
and
then,
if
there.
H
Bella,
do
you
mind
if
I
try
answering
Mr
Missy's
question
a
little
more
directly
I
think
I
heard
your
question.
Missy
was
around,
like
am
I
stuck
like
developing
testing
out
my
apps
locally
on
my
workstation
or
like
would
get
lab.
H
Allow
me
to
do
some
of
that,
like
as
part
of
the
development
process,
so
in
a
plus
one
to
everything
in
addition
to
that,
gitlab
has
an
auto
devops
feed
period
that
you
can
go
on
in
your
project
or
repository,
go
into
settings
turn
on
auto
devops
and
then,
if
you're,
using
like
a
feature
brand
methodology
to
do
your
development
work,
the
auto
devops
automatically
turns
on
something
called
a
review
app
and
what
that
allows
you
to
do
is
actually
see
and
test.
I
F
Yeah
I'll
interject
as
well,
then
I
think
yeah.
What
is
you
were
looking
at?
Was
there
in
Europe
we
do
have
access
when
we
develop
in
the
main
gitlab
project.
I.
Don't
think
that
you'll
have
access
for
it
in
the
fork,
but
maybe
on
this
special
Community
Fork
I
asked
you
to
move
your
merge
request
too.
Maybe
you'll
be
able
to
see
if
you
go
to
the
pipeline,
try
to
find
somethings
like
start
the
review
up
there.
F
D
E
Yeah
so
so.
E
In
place
the
contributors
or
the
merge
request,
authors
will
be
able
to
view
this
particular
widget,
so
in
this
case
I
haven't
deployed
it
because
if
my
local
I
entered
it
but
yeah,
so
this
is
this
is
just
an
answer.
You
asked
for
that
particular
documentation
and.
A
E
So
yeah
thanks
thanks
for
that
external
audition,
Matt
I
lost
the
point.
E
A
E
Okay
thanks:
everyone
I
just
wanted
to
stop
sharing,
and
we
just
do
the
advanced
control.
The
topic
that
I
wanted
to
cover
in
the
next
of
his
arts
and
I'll
pass
it
over
to
Emily.
G
Nothing
yes
thanks
so
much
Bella
for
walking
us
through
all
that
I
think
we're
kind
of
at
time
now
so
I'll
speed
through
the
last
portion,
which
is
just
highlighting
some
of
our
issues
open
for
Community
contributors.
I,
think
you
all
have
access
to
the
agenda,
but
on
point
five
there's
a
link
there
and
in
that
link
you
can
kind
of
find
all
the
open
issues
for
Community
contributors
to
start
working
on.
G
So
if
you'd
like
to
help
us
out,
feel
free
to
look
through
that
list
and
see,
if
there's
anything
that
interests
you
and
as
always,
our
next
meetings
will
be
detailed
in
the
Epic
listed
under
0.6.
There
I
think.
That's
all.
Unless
anyone
else
has
any
final
questions,
we
can
kind
of
end
it
off
cool
thanks.
Everyone
for
joining
and
I'll
see
you
next
time.