►
From YouTube: Source Code Weekly Meeting (2021-05-26)
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).
B
B
B
Sarah.
Can
I
attend?
That's
fine,
so
my
yeah.
My
first
point:
I
wanted
to
get
a
bit
of
status,
update
on
the
move
of
gitlab
project
from
master
to
maine.
I
know
that
there's
a
separate
effort
to
make
the
default
branch
on
gitlab
by
default
for
customers
main
not
master,
but
I
don't
know
this
is
slated
to
later
in
in
the
year
like
in
the
summer
somewhere,
but
I
noticed
that
there's
an
issue,
there's
kind
of
like
a.
I
feel
like
it's
stalled
a
little
bit.
A
No,
no,
it's
all
good.
Okay,
so
I'll
link
the
epic
just
grab
the
epic
okay.
So
had
you
asked
me
this
morning,
I
would
have
said
everything's
going
great.
However,
we
seem
to
run
into
a
a
problem,
so
I'm
just
linking
the
epic
there.
So
there's
actually
three
parts
right.
So
the
first
part
is
changing
the
default
branch
for
new
projects
on
gitlab
sas.
A
A
In
fact,
I
think
it's
basically
done
nick
was
working
on
to
do
a
migration
or
feature
flag
which
direction
he
chose,
but
to
do
it
for
self-hosted
instances
as
far
14.0,
so
that's
basically
ready
and
then
the
third
part
is
which
has
no
due
date
on
it
at
the
moment,
which
is
to
the
more
the
much
more
difficult
job
of
changing
the
default.
Changing
master
domain
on
the
good
lab
project
itself
because
of
all
the
associated
projects
and
yeah.
So
we
don't.
A
So
it's
actually
a
separate
project,
it's
kind
of
an
invisible
project
and
he
thinks
what's
happening,
is
it's
being
created
with
master,
even
though
the
main
project
is
made
so
yeah
so
investigating.
Is
this
what's
actually
happening
and
then
what
can
be
done
about
it?
So
it's
kind
of
not
actually
breaking
anything.
You
know
it
broke
some
tests
because
the
way
he
ran
them,
but
it's
not
actually
breaking
anything
specifically.
B
B
So
from
my
understanding,
the
the
case
that
you
mentioned,
I
think
there,
from
the
top
of
my
mind,
there's
at
least
three
cases
where
we
do
like
this
hidden
repository.
One
is
the
wiki.
The
other
is
the
snippets
and
the
other
would
be
a
security
project,
the
the
hidden
mrs
confidential,
mrs
functionality,
so
at
least
those
three
things
should
be
checked
in
this
investigation.
You're.
Looking
into
I'm
going
to
write
down
here
about
wiki,
snippets
and
confidential,
mrs
knowledge
yeah,
I
think.
A
Yeah,
so
it's
not
confirmed
this
is
actually
happening
yet
we're
just
trying
to
work
it
out,
but
that's
zagaryan's
thoughts.
He
also
was
wondering
whether
we
might
have
a
problem
with
import
export,
which
I
don't
believe
was
tested,
which
yeah
that
could
also
be
so
that's
the
latest
I'll
I'll.
Keep
you
I'll.
Keep
you
all
in
the
loop
I'll
ping
you
on
the
issue,
if
you
like
when
says.
B
A
Awesome
andre,
thank
you
very
much,
so
I
appreciate
that.
Okay,
that's
it
next,
okay,
so
I've
got
I've
got
an
idea,
okay,
so
this
is
actually
something
I've
struggled
with.
Since
I
came
into
this
role,
is
you
know
people
constantly
pinging
me
and
saying?
I
think
this
belongs
to
source
code
and
does
it
you
know?
Sometimes
I
you
know,
especially
when
I
first
started.
A
Some
of
them
are
a
bit
vague,
like
you
know,
gideous
fast,
for
example,
but
I
think
this
is
not
a
bad
place
to
start,
I'm
also,
it's
also
a
bit
confusing
the
way
that
they
the
feat
in
this
particular
page.
I
know
what
other
people
think
is
that
you
know
we
kind
of
duplicate
all
the
features
that
are
in
core
over
into
premium.
A
A
I
always
disagree,
okay,
cool,
okay,
so,
and
so
then
so
still,
what
does
that
actually
mean
what
belongs
to,
for
example,
source
code
back
end
right,
so
you
know
we
basically
work
on
endpoints
and
things
like
that,
and
so
there's
been
an
effort
to
go
through
the
code
and
actually
in
in
the
the
rails,
ruby
code
and
nominate.
I
think
it's
apis
and
background
processes
and
some,
I
think,
some
services,
but
it's
not
completely
completed
as
to
who
they
belong
to
so
feature
category
source
code
management.
A
So
that's
actually
fairly
recent.
I
think,
and
that's
that's
quite
useful,
and
so
the
third
kind
of
piece
of
information
here
is
that
if
we
scroll
down
to
here's
an
example
of
internal
layout
endpoint,
this
is
something
that
robert
put
together
and
I
think
it's
a
really
great
resource,
because
what
we
don't
have
and
there's
pros
and
cons
for
this.
What
we
don't
have
at
gitlab
is,
we
don't
have
technical
documentation.
A
So
we
have
generic
technical
documentation,
for
example,
how
the
security
system
works.
You
know
how
we
do
testing
or
whatever,
but
we
don't
have
specific
technical
documentation
on
what
does
this
endpoint
actually
do,
and
how
does
it
do
it
and,
and
so
the
the
problem
with
creating
that
type
of
documentation
is,
it
goes
out
of
date
quickly.
A
A
You
know
with
exception
to
one
of
them,
not
all
of
them
actually
know
the
whole
product,
they
know
different
different
parts
and
pieces,
and-
and
so
that's
something
I've
linked
cross-skilling
existing
team
members,
I'm
going
through
an
effort
to
try
and
develop
the
team
members
by
assigning
them.
You
know
bits
of
work
from
the
areas
they
haven't.
You
know
had
much
experience
in
that's,
of
course,
a
long,
a
long
process
but
okay.
A
B
Yes,
so
I
I
I've
seen
a
lot
of
conversation
about
this
in
the
past.
This
is
particularly
useful
when
addressing
an
incident-
and
you
know
the
code-
that's
causing
it,
but
you
don't
know
who
owns
it.
There's
been
competition
in
the
past
to
do
sort
of
a
mapping
of
ownership
of
this.
So
this
is
great.
Thank
you
for
erasing
this.
B
My
biggest
concern
here
is
that
if
you,
if
we
do
this
on
the
ruby
code
attached
to
the
ruby
code,
there's
a
lot
of
hidden
a
lot
of
features
that
won't
be
able
to
be
documented
on
the
ruby,
because
they're
built
in
view,
for
example,
so
absolutely
yeah,
building
something
like
this
attached
to
any
of
them
like
whether
it's
vue
or
ruby
would
always
leave
the
other
one
outside
of
the
scope.
But
we
can
always
build
the
same
implementation
across
multiple
languages,
so
we
can
then
have
a
way
to.
B
B
You
can't
specify
specific
methods
inside
a
file,
so
it's
mostly
per
file
per
path
and
I'm
trying
oh
yeah,
I'm
trying
to.
I
I'm
trying
to
find
out
the
mr,
where
kerry,
added
the
groups
of
code
owners
in
code
review,
because
our
plan
is
to
start
using
that
as
an
approval
rule
on
the
on
the
gitlab
project.
A
B
A
Yeah
so
yeah
that
will
actually
help
with
with
speeding
up
reviews
right
because
we
can
route
them
to
people
in
you
know
who
might
know
about
them
right,
rather
than
just
kind
of
like
the
random
way.
It
does
now.
Okay,
awesome,
and
so
yes,
and
then
this,
I
guess
also.
The
second
part,
was
this,
mr
that
robert's
done
where
it's
actually
quite
you
know
what,
if
we
click
on
email,
it's
like
you
know:
what
does
the
endpoint
do?
Where
is
it
defined?
A
You
know
what?
How
does
it
in
this
particular
point?
It
connects
to
italy
how
what
does
it
connect
to
in
italy,
and
so
this
information
can
of
course,
easily
go
out.
So
that's
pretty
valuable
to
an
engineer
working
on
it.
It
can
go
out
of
data
and
I
thought
the
way
we
might
be
able
to
handle
the
going
out
of
date.
Is
you
know
we
have
already
this
kind
of
like
badge
section
where
we
say
released
in
gitlab,
you
know
12.8
or
whatever,
and
so
we
could
possibly
use
something
similar.
A
I
don't
know
what
you
think
amy
about
and
say
you
know
this
is
this
document.
This
part
of
documentation
is
valid,
is
known
to
be
valid
as
of
14.0.
So
if
you're
on
14.4
and
you're
looking
at
it,
then
you
have
to
kind
of
take
it
with
a
grain
of
salt
and
possibly
do
an
mr.
If
you
find
out
it's
right,
it's
wrong.
Yeah!
You
just
put
a
paragraph
for
documentation,
especially
in
the
the
development
section
of
the
docs,
which
is
sort
of
a
free-for-all,
just
put
a
paragraph
up
at
the
top
okay,
okay.
A
Well
great.
Now,
as
far
as
the
code
own
the
code
owner
stuff
andre,
I
want
to
make
sure
that
I
mention
the
technical
writing.
Team
has
run
into
that
problem
too.
If
you
look
at
the
docs,
we
had
to
solve
it
by
front
matter,
but
there
isn't
a
way
to
hook
that
front
matter
back
into
code
owners.
We
we
couldn't
wait
for
an
engineering
solution.
B
A
B
A
B
A
B
B
And
I'm
this
is
my
computer
being
slow,
so
we
have
all
of
these
things
and
each
one
of
these
boxes
might
have
a
different
owner.
Most
of
us
most
of
them
are
code,
our
code
review,
but,
for
example,
if
you
go
to
a
this
code
review
this
one,
the
nine
is
verify
so,
as
you
can
see,
we,
this
granularity
is
only
possible
at
the
code
level
and
we
are
able
to
do
that
by
code
owners
because
we
can
specify
a
path
and
basically
what
we
say
everything
inside
diffs
is
code
review.
B
Everything
inside
I
don't
know
the
verify.
The
group
metrics
reports
app
that's
testing
and
so
on
and
so
on.
So
it
is
complicated
to
get
when
you
get
to
the
granularity
of
all
this,
but
it
is
useful
because
then
you
will
be
quicker
to
identify
owners
and
to
solve
them
so
good
stuff
I'll
share
the
mr
once
I
find
it
awesome,
so
you
can
take
a
look.
A
It's
really
great
information
and
I
think
we
can
use
accommodation,
and
so
the
note
you
just
put
about
gems
that
can
generate
diagrams
of
classes.
So
that's
actually
a
really
good
point
also
because,
like
if
you
look
at
the
rails,
documentation
or
any
big
project,
they
have
our
docs,
which
is
a
list
of
all.
You
know.
It's
automatically
generate
all
the
classes,
and
you
know
you
can.
A
So
there
must
be
some
historical
reason
why
we've
chosen
not
to
maybe
it's
too
hard
to
build
or
something
I
don't
know,
and
then
the
other
one
is
so
there's
a
there's,
a
gem
that
you
can
use
to
map
the
database
tables
back
to
a
diagram
which
is
called
something
erd.
I've
used
it
in
the
past
and
I
went
and
looked
at
it
recently.
I
noticed
kerry
is
a
maintainer
on
it.
A
B
A
B
Yeah,
take
a
look
at
that.
I
remember
one
very
vividly
about
the
state
machines
and
state
machine
state
machines
when
you
get
really
complex
knowing
which
state
can
transition
to
which
ones.
It's
it's
incredibly
useful
to
understand
like-
and
we
were
talking
on
about
this
recently
about
in
the
context
of
mergibility
of
mrs.
If
we
can
understand
the
states
that
the
the
mergers
request
can
be
in
if
we
can
find
a
way
to
automatically
push
out
a
diagram
that
documents,
the
current
state
of
the
code
is
invaluable,
but
I
don't
think
anyone.
A
Good
point:
yeah,
yeah,
okay,
that's
a
good
point,
run
with
it
and
from
the
front
end
like
the
finance.
Actually,
because
the
back
end
is
you
know,
we've
got
a
bit
of
name
spacing,
but
generally
it's
pretty
much
all
indicate
together
right,
whereas
the
front
end
is
actually
a
lot
more
organized
right,
like
the
folders
yeah
kind
of
component.
B
B
B
A
B
A
Yeah
absolutely
yeah
cool,
okay,
so
the
next
one
I
put
in
for
in
case
sarah
had
a
chance
to
look
at
this.
I
was
just
wondering
if
we
had
any
updates
on
the
hiring.
I
know
that
I
know
the
wreck
went
out.
I
think
it
went
on
linkedin
and
everything,
but
I
don't
know:
if
do
we
have
any
candidates
or
anything
they.
B
B
A
B
B
Around
the
summer
around
the
summer,
the
summer
months
we
usually
do
so
we
can
have
a
section
at
the
start
of
each
agenda
to
just
announce
paid
time
off
on
the
upcoming
weeks.
So
yep
do
you
have
anything
coming
up
sean
yeah
I'll,
take
off
a
couple
of
weeks
in
july
right.
So
once
you
have
that
settled
up,
oh
nice,
that
sounds
so
good.