►
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
All
right
happy
wednesday,
so
everybody
is
doing
well,
it's
having
a
good
week,
I'll
jump
into
the
announcements
and
then
we'll
proceed
to
the
agenda.
So
from
the
engineering
week
in
review,
there
are
a
few
things
that
are
worth
highlighting
on
call
schedule
which
affects
a
lot
of
us
back
engineers,
so
the
spreadsheet
for
weekdays
is
being
deprecated,
so
more
information
is
available
in
the
issue
in
mmr.
As
far
as
how
this
process
is
particularly
is
changing.
A
Next
one
is
about
some
tooling
updates
that
are
worth
knowing
about
there's
a
in
the
performance
bar
there's,
there's
more
about
memory
allocation
memory,
usage
how
it
is
to
be
used
and
more
and
is
available
within
within
the
docs
and
there's
also
a
how-to
video,
that's
available
for
us
for
our
reference.
Should
we
be
looking
for
it
and
last
but
certainly
not
least,
from
engineering
week
in
review.
There
is
another
family
and
friend's
day
it's
been
scheduled
in
june,
it's
june
25th.
A
So
please,
hopefully
everybody
can
can,
can
take
advantage
of
that.
Next.
What
we
do
every
week
celebrating,
we
should
celebrate
features
and
high
priority
bugs
been
closed
in
the
past
seven
days.
The
list
is
available
here.
If
you
would
like
more
information
about
what
was
closed
and
how
it
was
closed.
Please
click
through
for
for
more
information
about
that
and
david
looks
like
you
claim
to
let
the
next
one
so
four's
here,
sir.
B
Yep,
so
everyone
please
welcome
hillary.
She
joined
last
week
as
our
director
of
product
for
the
secure
and
protect
stages.
Hillary
for
those
on
the
call.
Would
you
tell
us
a
little
bit
about
why
you
joined
get
lab
where
you
were
and
a
little
like
what
you
like
to
do
for
fun
and
let
everyone
know
the
pm
team
is
very
excited
that
hillary
has
joined
as
well.
C
Thanks
david
yeah,
so
I
think
a
few
of
you
have
already
heard
this
spiel.
So
I'm
sorry,
if
you're
listening
to
this
for
the
second
time,
but
in
terms
of
why
I
joined
two
main
things,
I
would
say
the
culture
and
the
opportunity,
so
I've
been
kind
of
watching
gitlab
for
a
long
time.
C
I
was
you,
know
very
interested
in
remote
work
and
sort
of
those
things
before
it
was
the
cool
thing
to
do,
and
you
know
even
back
in
25
2015
2016,
I
you
know
read
about
the
get
lab.
Culture
was
really
impressed
with.
You
know
how
the
company
operates,
and
so
I
became
aware
of
it
and
then
I've
been
trying
to
work
for
git
lab
actually
for
a
few
years
now.
C
So
scott
williamson,
you
know,
reached
out
to
me
a
couple
years
ago
about
a
role
and
timing
was
bad
for
me
and
then
we
tried
in
2020
and
then
ended
up
being
bad
timing
for
gitlab,
and
then
it
looks
like
third
time's
a
charm,
so
because
I'm
here
now
so
it
worked
out.
So
it's
good
and
then
I
think
that
you
know,
based
on
what
I
was
doing
prior
to
gitlab
it's.
C
You
know
a
good
fit
for
for
the
opportunity
as
well
and
what
y'all
are
trying
to
do
in
the
security
space
so
prior
to
get
lab.
I
was
working
as
a
product
executive
for
a
container
security,
startup
called
stackrocks
they're,
now
part
of
red
hat
and
oh
my
gosh.
What's
the
third
thing,
oh
for
fun,
right
so
for
fun,
I'm
super
into
outdoor
stuff,
so
snow,
sports
and
camping
and
hiking
and
hanging
out
a
lot
with
my
my
dogs.
We
have
two
welsh
corgis
and
yeah.
That's
about
it.
B
I
think
hillary
and
for
everyone
on
the
call
todd
is
super
excited
that
hillary
started,
because
now
he
doesn't
have
to
deal
with
me
anymore.
So,
if
you're
like
todd,
you
can
be
excited
as
well.
I.
A
Well,
we'll
go
ahead
and
get
into
the
agenda
I'll
cover
for
lucas.
Since
he's
not
here
the
there's
there's
a
tool
that
he's
developed
that
he
is
now
publishing
his
makeup.
He
was
using
it
personally
and
is
now
publishing
it
for
for
our
for
our
use,
that's
about
it's
a
schema
validator,
making
sure
that
what
we
are
publishing
is
is
compliant
with
the
schemas
themselves.
So
the
that
project
has
been
moved
to
security
projects
group.
A
It
is
now
live
at
the
link
that
he
is
that
he's
provided
we're
working
on
working,
getting
a
proper
sub
domain
once
he's
back
in
the
office,
though,
all
are
welcome
to
contribute,
and
so
this
is.
This
is
a
neat
little
side
project
to
be
sharing
with
us.
A
Okay,
alrighty
I'll
cover
for
thiago
as
well,
since
this
is
not
his
not
his
time
zone.
So
we
have
two
security
reports,
projects,
one
underneath
gitlab
examples
and
one
that
is
underneath
the
the
gitlab
org
namespace.
A
A
E
A
Alrighty,
this
is
an
open
inquiry.
It
may
be
worthy
of
an
issue
to
track
a
decision,
in
which
case
we'll
make
a
call
on
whether
or
not
to
open
that
in
the
later
iteration
of
this
of
this
meeting
series,
and
so
or
we
could
just
do
it
now
so
yeah.
D
A
All
righty
I'll
move
on
also
since
cam
is
in
another
diff
and
it
will
be
in
the
other
iteration
of
this
call
the
secure
schemas
that
we
have
our
json
report.
Schemas
there's
been
a
request
that
we
also
publish
these
to
npm,
which
is
which
is
neat
and
interesting.
A
There's
an
mr
that's
been
opened
for
this
if
you
have
any
concerns
or
want
to
participate
in
this
particular
and
in
this
proposal
and
the
decisions
for
it,
mr,
is
linked
from
the
agenda.
So
any
questions
on
this
one
or
commentary.
A
All
right
moving
on
next
I've
got
this
one's
from
me,
so
this
is
something
I
realized
that
we
did
not
broadly
announce.
So
this
is
something
we'll
also
be
bringing
taking
to
the
engineering
week
in
review.
Probably
before
the
weeks
expires,
some
grip,
it's
a
tool
we've
been
trying
to
get
into
into
the
sas
suite
of
analyzers
for
quite
some
time.
We've
declared
that
generally
available
it's
it's
currently
working
for
python,
javascript,
typescript,
and
so
at
least
that's
where
the
that's.
What
that's?
A
So
you
will
see
this
running
in
pipelines
if
we
have
matches
for
those
particular
languages,
so
one
we
wanted
to
make
sure
everybody
knew
that
it
was
here
and
that
we
are
starting
to
use
it.
We
are
we've
done
a
lot
of
work
to
make
sure
that
the
analyzers
that
we
intend
to
deprecate
with
those
are
running
side
by
side
that
we're
not
creating
two
vulnerabilities
for
the
two
analyzers
that
are
detecting
the
same
thing.
A
So
deduplication
work
should
has
been
done
and
you'll
see
this
running
within
our
main
rails
and
within
our
main
pipelines
within
gitlab
as
well.
So
we
want
to
make
sure
everybody
knew
it
was
here
what
it
was
for
we're
intending
to
drive
standardization
of
tooling
onto
some
group
itself.
We
want
to
retire
a
number
of
projects,
so
we're
actively
trying
to
figure
out
which
ones
those
are
as
well
as
what
order
they
will
be
retired
in
and
so
feedback
is
most
certainly
welcome.
E
A
A
E
E
So
this
is
a
kind
of
a
follow-up
so
that
we
keep
that
up
today,
because
it
happens
that
some
updates
have
been
done
on
both
sides
while
we're
keeping
both
locations.
So
this
is
making
things
a
bit
cleaner.
So
if
someone's
volunteered
to
review
that
feel
free
to
do
that.
Otherwise,
I'll
pick
someone
up
later
today.
A
A
Here
all
right
hearing,
nothing!
Thank
you,
everybody
for
your
time
and
attention
we'll
call
that
a
close
to
this
particular
to
this
weekly,
I'm
going
to
stop
the
recording
and,
if
folks,
want
to
stay
on
for
a
coffee
chat.
Please
do
please
feel
free
to
do
so
and
otherwise
have
a
great
rest
of
your
week.
We'll
talk
soon,
see
ya.