►
Description
June 28th, 2022
During this Community Office hours call, David O'Regan is walking us through identifying an issue to work on and contributing to Create:Editor.
Meeting Agenda: https://bit.ly/3y8fqZc
Contribute to GitLab: https://about.gitlab.com/community/contribute/development/
Join the next office hour call: https://www.meetup.com/gitlab-virtual-meetups/
A
Hello:
everyone
thanks
everyone
for
joining,
I'm
christos
the
contributor
program,
announcer,
I'm
here
with
you,
wonderful
people
today,
hello
to
everyone,
who's
watching
the
video
afterwards.
Actually,
I've
seen
that
the
queues
are
quite
high,
which
is
super
nice.
So
thank
you
all
for
joining
and
for
tuning
in
today
we
have
an
amazing
group
of
people,
so
I'm
gonna
pass
it
on
to
for
other
people
to
introduce
themselves.
Let's
go
from
the
I'm
gonna
pick
a
person
and
I'm
gonna
be
like
with
srida
wanna,
introduce
yourself.
B
C
D
David
hi
everybody
so
so
my
name
is
david,
david
o'regan
and
at
the
moment
I
am
the
em.
The
full
stack
em
over
on
the
create
editor
team,
and
our
categories
previously
have
mostly
revolved
around
the
editing
experience
at
gitlab.
So
content,
editing,
code,
editing,
web
ide
source,
editor
single
folder,
and
we
are
now
tackling
our
newest
category
and
our
newest
addition
to
gitlab,
which
is
remote
development.
So
we're
really
excited
about
that
and
it's
going
to
be
a
big
focus
for
us
on
the
team
for
the
next
well
for
the
foreseeable
future.
E
A
C
team
members
started
doing
some
twitch
streams
over
on
twitch
that
we
then
uploaded
to
our
youtube
channel
that
we
opened
when,
where
we
basically
go
over
pick
an
issue
go
over
it
and
work
on
it
open
dmr
and
basically
we
try
to
don't
look
in
advance.
What
the
issue
is
about,
so
we
can
show
the
full
thought
process
about
how
to
tackle
the
issue
and
yeah.
I'm
gonna
be
posting
the
youtube
link
to
the
channel,
a
link
to
youtube
channel
and
the
twitch
channel
on
the
agenda.
If
that's
okay,.
A
Also,
it's
just
something
to
highlight
around
that.
Generally,
there
is
a
discord
server
which
currently,
it's
unofficially
supported
by
my
kids.
It's
a
community
discord
server
right
now,
a
lot
of
community
members,
let's
say
meet
there
and
there's
a
lot
of
activity,
and
this
actually
is
one
of
the
results
of
people
getting
together.
It's
like
coding
sessions
and
how
you
approach
stuff.
So
there
is
a
link
to
the
agenda
doc
in
a
0.7
for
discord,
server
feel
free
to
join
if
anyone's
interested.
A
All
right
so,
should
I
just
pass
it
over
to
david
david.
It's
really
pleasure
for
having
you
with
us.
David
is
one
of
the
people
that
is
for
me
is
really
close
to
the
community.
I've
seen
a
lot
of
you
know
a
lot
of
feedback,
always
valuable
feedback,
always
looking
after
after
for
the
for
the
community
and
reviewing
mrs
and
you
know
always
there.
So
I'm
really.
I
really
appreciate
that.
So.
A
Thank
you
so
much,
and
I'm
really
happy
that
he's
here
with
us
today
to
talk
about
yeah
pronoun
is
he
he
is
right?
Sorry
perfect!
So
I'm
really
happy
that
you're
here
today
with
us
today
to
talk
about
you
know
whatever
you
feel
more
comfortable
in
the
way,
but
also
you
know
about
how
we
can
have
more
people
contribute
to
kid:
love
like
best
picture,
trick,
tips
and
tricks
how
to
operate
an
issue
so
yeah.
D
Awesome,
okay,
super
stuff-
it's
great
to
be
here
so
funny
enough.
When
I
started
a
gitlab
before
I
worked
here,
I
was
a
community
contributor
back
in
the
good
old
days
when
I
had
joined
jitter
first
before
anything
else,
so
I
have
a
really
really
really
really
big
passion,
the
soft
spot
for
our
community
and
I
really
enjoy
working
with
everybody,
it's
fantastic.
D
D
Specifically,
ever
since
we
took
over
the
pages
category-
and
we
have
a
lot
of
people
who
make
use
of
our
gitlab
pages-
and
we
get
a
lot
of
traction
on
that
for
people
wanting
to
come
in
and
make
it
better,
and
we
also
have
a
handful
of
categories
like
the
wiki,
where
people
feel
comfortable
submitting
changes
and
we
have
the
web
ide,
which
is
used
by
an
awful
lot
of
people.
So
what
I'm
going
to
do
is
I'm
going
to
share
my
screen
I'll.
D
On
the
editor
side,
we
have
some
really
fantastic
developers
who
are
also
part
of
the
community,
like
we
have
paul
slaughter,
who's,
a
really
really
big
community
advocate,
and
so
when
in
doubt
feel
free
to
reach
out
to
the
editor
team.
And
we
will
try
our
best
if
we
can't
figure
out
what
the
problem
is,
we'll
try
and
triage
it.
D
And
I'm
going
to
assume
everybody
can
see
it
and
if
you
can't
feel
free
to
raise
your
hands,
but
I'll
start
with
this
is
our
handbook
page.
This
is
the
create
our
team
handbook
page
if
you're
any
point
interested
in
the
things
that
are
going
on
inside
the
create
editor
team.
You
are
free
to
visit
our
handbook
page
and
find
our
direction
you'll
find
a
list
of
our
current
team
members.
D
So
this
is
probably
well
known
to
everybody
here,
but
I'm
just
going
to
highlight
it
again,
which
is
on
our
actual
website
the
aboutgitlab.com.
We
have
a
section
on
how
to
request,
help
and
actually
engage
with
the
community,
merge,
coaches
and
people
around
gitlab
who
are
available
to
help
look
after
you
if
you
do
submit
a
merge
request,
so
this
section
is
really
really
helpful.
I
tend
to
come
back
here
quite
a
lot.
We
have
the
triage
bot,
obviously
gitlab
boss.
At
help
me
you
can
ping
any
of
the
merge
request.
D
Coaches,
we
have
a
link
to
the
team
page
outlining
who's,
a
merge
request,
coach
or
if
you
have
any
major
problems,
you
can
either
use
the
jitter
channel
for
instant
feedback
or
even
email,
the
contributors
at
gitlab.com
so
to
get
started.
The
first
thing
you're
going
to
need
to
do
is
grab
yourself
a
copy
of
gdk.
D
D
On
the
editor
team,
keep
in
mind
not
every
team
uses
weights
on
the
editor
team.
We
do
use
weights,
we
adhere
to
the
fibonacci
sequence.
So,
as
a
new
contributor,
I
would
always
suggest
by
filtering
the
issues
by
weight
from
lowest
to
highest
a
weight.
One
is
a
very
straightforward
issue.
It
usually
means
the
actual
issue.
D
So
I'm
going
to
show
you
what
a
well
fleshed
out
issue
from
us
looks
like
that
is
ready
for
a
community
contribution
and
we
have
this
web
ide
issue
that
was
actually
created
by
lead
ticket.
It
was
highlighted
recently
enough,
which
is
in
not
dark
mode,
which
is
what
I'm
using
here.
But
specifically
when
we
use
the
gray
theme,
we
have
a
css
bug
where
we
can
see
that
the
text
that's
being
represented
in
our
commit
box.
Our
commit
message
is
really
really
difficult
to
read.
D
So
lee
has
gone
ahead
and
he's
created
a
nice
explanation
in
the
title
he's
linked
the
slack
conversation
now.
Unfortunately,
most
people
won't
be
able
to
access
that
because
that's
a
closed
slack,
but
what
we
do
to
make
sure
that
this
issue
is
consumable
for
our
community
is
we
will
first
off
label
it
correctly.
So
we
adhere
to
correct
label
hygiene.
So
this
is
specifically
a
front-end
issue.
It's
a
front-end
weight
of
one
because
we're
just
changing
some
css
and
it
belongs
to
the
editor
team.
F
D
So
I've
left
a
rough
solution
for
an
mvc
that
would
actually
fix
this
problem,
but
it
doesn't
address
the
route
which
is
now
that
we've
migrated
over
to
our
gitlab
ui
components.
We
in
theory
could
actually
do
away
with
the
majority
of
this
file,
which
would
be
the
right
solution.
However,
that
will
require
more
investigation,
more
testing,
and
that
may
not
be
something
that
somebody
from
the
community
wants
to
pick
up.
D
So
with
something
like
this,
if
you
were
to
pick
us
up,
where
would
you
begin
and
how
it
just
starts?
So,
let's
assume
you've
downloaded
to
gdk
and
you've,
set
it
up
and
you're
successfully
able
to
do
your
pull
request
or
your
merge
request.
I
should
say
so:
we'll
grab
a
terminal
and
your
git
lab
development
kit
should
usually
start
on
the
master
branch.
D
So
I'm
going
to
bring
this
over
here.
So
we
have
a
code
editor
and
we
can
see.
I
was
already
looking
at
some
html
this
morning
and
what
I'm
going
to
do
is
I'm
going
to
open
up
a
terminal
inside
this
code,
editor
just
to
make
it
a
little
less
jarring,
so
we're
not
contact
switching
a
tip
for
anybody
submitting
community
contributions
when
checking
out
a
branch
where
you're
targeting
an
issue,
I
would
always
suggest
prefixing
the
branch
name
with
the
issue
number.
D
This
will
give
you
the
benefit
of
automatically
pre-filling
your
merge
request
with
the
labels
and
the
metadata
from
the
issue,
which
can
be
really
helpful
and
really
time
saving
and
even
if
you're,
a
little
bit
lost
on
how
to
reach
out
to
merge
coaches
or
the
people
on
the
team.
Chances
are
pretty
good,
we'll
pick
it
up.
If
it
has
the
right
label
page
hygiene,
I
should
say
so.
If
I
have
a
quick
look
and
see
this
issue,
is
this
number?
So,
let's
so,
I
would
very
simply
yeah
something
along
this
line.
D
So
when
you're
using
the
jdk,
you
will
run
a
command
which
is
jdk
start.
This
will
actually
physically
start
the
jdk
for
you
I'll
run.
It
here
you
can
see
that
we're
going
to
start
up
of
the
local
development
gitlab
kit.
This
will
let
you
navigate
to
a
local
instance
of
the
gitlab
project,
running
at
local
host,
3000
or
maybe
a
specific
url.
If
you
can
configure
it
and
you
can
work
with
them
chop
and
change
files
and
make
changes
locally.
D
So
let's
pretend
we
will
go
ahead
and
say
that
we've
done
all
of
our
local
testing
and
it's
specifically
this
file
that
we're
looking
at,
and
I
would
trust
people
to
do
a
better
job
than
I'm
about
to
do
on
this.
But
we
have
our
file,
I'm
just
going
to
make
a
small
change
to
our
file,
just
for
the
purpose
of
showing
how
to
actually
spin
up
the
merge
request
and
get
help
from
the
community.
I
don't
make
any
claims
that
this
is
going
to
be
a
good
solution.
D
So
let
me
have
a
look
here
and
have
a
read.
So
if
I
change
this
so
essentially
yeah
what
we
want
to
do
is
we
basically
want
to
include
for
the
input
elements
we
want
to
include
this
color
overwrite.
So
let's
do
it.
Let's
include
the
color
override
now
I
just
happen
to
know
off
the
top
of
my
head
that
what
we
want
to
include
the
color
override
is
just
on
the
input.
D
D
So
I
have
my
change.
I'm
going
to
go
ahead,
I'm
going
to
add
I'm
going
to
commit
my
change
in
gitlab.
We
use
a
changelog
prefix
in
our
commit
messages.
This
ensures
that
we
are
representing
in
our
change
log
what
our
changes
are
doing
so
specifically
what
we're
fixed
we're
fixing
a
bug
here.
So
the
change
log
for
that
is
change
log
fixed
if
we
were
adding
a
feature,
it'd
be
change.
D
D
D
It's
really
important
on
the
community
side
too.
So,
if
my
internet
holds
up,
this
in
theory
should
push.
It
gives
me
a
url
to
spin
up
a
merge
request,
super
stuff,
I'm
going
to
go
ahead
and
just
jump
to
it,
and
we
can
see.
We've
been
given
a
template
here
now
on
the
community
side
for
those
looking
to
engage
with
gitlab.
D
The
one
thing
you
can
do
to
make
our
life
easier
and
push
your
merge
request
through
quicker
is
to
really
have
your
meta
in
place,
and
that
just
basically
means
the
description
of
your
merge
request,
screenshots
and,
ideally,
a
good
guide
on
how
to
replicate
or
test
it
locally.
That's
what
maintainers
will
be
looking
for.
D
F
D
Can
outline
the
steps
you
took
to
solve
the
problem
screenshots
before
and
after
a
video
might
even
be
better
if
it's
something
that
requires
context
and
then
steps
as
to
I
assume
somebody
on
the
maintainer
side,
specifically
on
the
front
ed
would
come
in
to
fix
this,
so
I
would
give
them
a
set
of
steps.
I
would
tell
them
hey
spin
this
up
navigate
to
this
page
click,
this
button.
D
So,
since
I've
prefixed
the
merge
with
the
issue
number,
we
can
see
that
it's
actually
gone
ahead
and
assigned
a
lot
of
the
merge
meta
which
is
fantastic,
and
it
automatically
knows
what
issue
this
is
related
to,
which
is
super
stuff.
We
don't
have
any
dependence.
This
is,
if
specifically
you're
not
targeting
master.
This
might
be.
You
might
have
a
merge
that
needs
to
come
ahead
of
this.
You
might
use
this
to
reference
it,
and
this
will
keep
it
locked
in
place
microchip.
C
D
Yes,
so
normally
you
won't
be
able
to
interact
with
the
sidebar
correct,
but
I'm
assuming,
if
you
prefix
the
merge
with
the
issue
number,
it
should
pre-fill
the
meta
for
you,
so
you
should
at
least
get
a
selection
at
the
beginning.
If
I'm
not
mistaken,
although
feel
free
to
correct
me,
if
I'm
wrong,
if
I'm
wrong,
we
probably
should
we
probably
should
fix
that
on
our
side.
D
D
I
know
we
generally
already
apply
a
community
label
and
specifically
for
people
who
are
their
first
time.
We
apply
first,
but
please
do
try.
Let
me
know:
okay,
once
you've
gone
through
these
steps,
ideally
whoever's
going
to
be
jumping
into
the
review
will
handle
the
majority
of
the
meta
that
needs
to
be
updated,
and
I
would
advise
most
people
to
enable
the
squash
commits
when
the
merge
is
ready.
D
D
I
would
throw
that
to
the
maintainer
as
opposed
to
you
specifically
trying
to
decide
that
unless
you
feel
very
strongly
about
it,
in
which
case
feel
free
to
to
leave
that
unchecked
and
make
your
case
the
maintainer
we've
created
our
merge
request,
our
merge
request
is
up
and
running.
So
specifically,
the
next
part
is
what
we
want
to
do.
Is
we
want?
I
just
want
to
move
this
out
of
the
way,
so
I
can
see
what
I'm
doing
here
specifically
what
we
want
to
do
now.
D
F
D
Terms
of
giving
us
some
prompt
and
some
help,
but
if
it
doesn't
and
you're
looking
to
engage
with
people,
you
can
ask
gitlab
bot
help
to
give
you
an
idea
of
how
we
can
get
some
help.
You
can
also
use
a
handful
of
other
commands
now
that
are
available
to
us
like
at
getlab.ready,
which
means
this
merge
is
ready.
We
can
see
here.
This
is
ping
to
merge
coach
specifically,
but
we
also
have.
D
Bot
ready,
which
in
theory
should
do
the
same
thing
and
let
people
know
that
this
merger
quest
is
now
ready
to
rock
and
should
be
ready
for
review.
This
should
do
a
couple
of
things.
This
should
move
the
merge
into
workflow
ready
for
review,
and
it
should,
if
somebody
is
not
assigned
to
ping
somebody,
so
we
can
see
there.
It's
moved
in
to
ping
the
same
person.
D
D
So
if
you
are
looking
for
ways
to
engage
with
the
editor
team,
navigate
to
our
team
page
have
a
look
at
our
categories
and
you
can
filter
down
the
issues
by
the
categories
and
anything
you
tend
to
see
in
the
backlog
is
up
for
grabs
if
it's
not
already
in
development
and
we'll
be
more
than
happy
to
engage
with
you
and
kind
of
point
you
in
the
right
direction.
If
you
want
to
contribute
and
keep
your
eye
out
for
the
category
remote
development,
that's
the
that's
the
next
big
one.
D
C
C
Oh
okay,
so
you're
already
making
this
some
changes
because
I
noticed
a
I'd
say
a
discrepancy
because
and
on
a
merge
request.
When
you
include
an
image
on
the
description,
it
opens
up
on
a
new
tab
of
the
on
the
editor
because
it
has
the
target
blank
attribute.
But
issues
and
comments.
Also,
if
I'm
not
mistaken,
they
replace
the
page
and
it's
kind
of
frustrating.
D
Yeah,
it
is
it's
one
of
our
biggest
frustrations,
which
is
the
descriptions
and
issues
merges
comment,
boxes
and
wikis
all
render
mark
down
slightly
differently,
and
they
all
treat
you
slightly
differently.
So
our
goal
is
to
unify
that
using
the
content
editor.
So
if
you
want
to
have
a
look
at
that,
I'd
advise
checking
out
the
content,
editor
direction
page
and
seeing
we'll
be
starting
with
issues
and
then
we're
kind
of
building
up
from
there.
It's
already
a
wikis,
though
at
the
moment.
C
A
D
D
No,
no
you're,
fine,
you're
fine.
I
was
asking
if
there
was
anything
that
you've
noticed,
that
we
could
do
on
the
git
lab
side
so
like
as
an
example
there.
I've
just
learned
that
on
the
community
side,
if
you
prefix
a
merge
with
an
issue
number,
it
doesn't
automatically
fill
out
the
labels
we
could.
We
could
fix
that
on
the
gitlab
side
and
that
would
make
contributing
a
slightly
nicer
experience.
D
C
Well,
one
one
thing
was
done
recently
because
now
with
the
gitlab
bot,
you
can
assign
reviewers,
and
that
was
one
of
the
main
missing
thing.
I
guess,
because
it
was
you
could
ping
the
reviewers,
but
then
they
would
have
to
assign
themselves
and
all
of
that
with
the
ability
to
actually
assign
the
reviewers.
And
now
that's
really
an
improvement.
A
C
Because
there
there
are
some
channels
more
active
than
others.
I
guess
mainly
because
on
some
channels
are
dedicated
to,
for
example,
support
and
divided
to
self-hosted
and
not
set
hosts
and
all
those
things,
so
those
channels
actually
don't
get
used
that
much,
because
only
a
a
community
member
has
to
know
that
there
actually
is
a
discord
server
b.
You
have
to
have
a
problem
and
ask
a
question.
C
A
Interesting
yeah,
just
from
the
community
relations
point
of
view
in
regards
to
the
discord
server.
This
is
something
that
started
from
community,
also,
it's
equivalent
to
a
slack
instance
that
exists
out
there.
It's
a
community
around
additional
community
run
as
well,
so
we're
trying
to
figure
out
we're
working
with
the
owner
of
the
peace
corps
to
see
whether
we
can
take
ownership
or
not
because
dieter
they
want
the
tool
that
we
have
right
now.
It's
really
good
because
there
is
a
bridge
of
slack,
but
we're
also.
D
A
F
Like
I
just
wanted
to
say
that
community
office
is
very
great
thing
to
start
from
start
like
contributing
to
get
lab
like
I
started
attending
community
office
hours
like
before
hackathons,
and
I
learned
a
lot
from
attending
it,
and
I
learned
mostly
by
by
contributing
to
it
contributing
in
gitlab.
So
this
is
very
great
thing
that
you
guys
are
doing
it
and
it's
very
helpful
to
for
community
also.
So
it's
a
matter
of
time,
like
more
than
more
people,
will
come
in
community
officers.
A
Yeah,
that's
another
thing.
You
know,
thanks
for
thanks
for
sharing
that
scheduling
is
also
a
problem
in
order
to
be
able
to
support
all
time
zones.
For
example,
we
have
community
in
new
zealand.
They
wanted
to
join
what
is
like
around
three
a.m
right
now,
I
I'm
pretty
sure
you
need
this
for
late
as
well
right.
It's
should
be
something
like
12
from
the
mistake,
so
it's
really
difficult
to
accommodate
all
the
different
time
zones.
A
So
maybe
we
need
to
do
some
eroding
one
like
every
second
week
every
week
to
change
the
time
zone
to
accommodate
different
dungeons,
but
also
that's
why
we're
recording
and
yeah?
I
mean
david.
If
you
have
an
idea
about
who
do
you
buy
next
week?
That
would
be
a
nice
or
anyone
has
an
idea
reaching
out.
D
D
A
G
C
D
D
D
A
A
We
can
leave
you
our
coffee
circles
and
again,
if
you
have
any
issues
with
running
with
ci
cd
minutes,
while
contributing
there
is
a
long
bug
we're
trying
to
solve
it.
But
in
the
meantime,
if
you're
running
out
or
about
to
run
out
from
of
cicd
minutes,
please
reach
out
to
me
either
directly
or
through,
to
start
me
on
an
issue
on
gitlab
and
I
will
address
it
as
soon
as
possible.