►
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
I'm
joined
by
some
of
the
members
of
our
awesome
product
team.
They
are
in
order
which
they
will
be
presenting.
Josh
lambert,
director
of
product
for
our
enablement
and
sas
platform
sections
will
provide
updates
for
the
enabling
section.
Sarah
waldner
group
product
manager
for
the
create
stage
will
provide
updates
for
our
dev
section.
A
Matt
wilson
senior
pm
for
government
threat.
Insights
will
provide
updates
for
our
sac
section.
Taylor,
mccaslin
group,
product
manager
for
model
ops
and
anti-view
stages
will
provide
us
updates
for
the
data
science
section.
Yes,
that's
the
new
name
for
it
and
kevin
chu
group
product
manager
for
the
monitor
stage
will
provide
updates
for
our
ops
section.
A
We
are
focused
on
delivering
value
iteratively,
with
a
focus
on
our
fy23
product
investment
themes.
Our
first
theme
is
getlab
hosted.
First,
please
note.
This
does
not
mean
gitlab
posted.
Only
gitlab.com
is
the
largest
known
self
managed
deployment
that
we
manage
for
our
users,
and
we
know
if
we
can
meet
our
requirements,
we
will
meet
our
users
requirements.
A
A
This
this
includes
areas
like
our
code
review
experience
our
security
experience,
and
we
know
if
we
can
improve
that
both
usability
and
learnability.
A
Before
I
hand
it
over
to
josh,
we
have
a
short
public
service
announcement
on
this
live
stream,
we'll
be
discussing
our
product
roadmap,
which
includes
upcoming
features
and
functionality.
It's
important
note
that
the
information
presented
on
this
live
stream
is
for
informational
purposes.
Only.
Please
do
not
rely
on
it
for
purchasing
or
playing
decisions.
A
B
Thanks
david
super
excited
to
take
everyone
through
the
enablement
highlights
for
this
coming
milestone
and
with
that,
let's
jump
into
get
that
posted
first,
as
david
mentioned.
All
these
benefits,
of
course,
will
be
available
to
our
sas
platforms,
but
also
to
everyone
who
runs
a
self-managed
instance
as
well.
So
with
that
we
can
move
on
into
the
geo
group
and
they
are
continuing
to
work
on
the
last
remaining
items
that
were
moving
into
the
cell
service
framework.
B
The
goal
of
this
is
to
have
all
of
our
content
types
being
replicated
with
the
same
piece
of
code,
so
we
can
duplicate
all
the
other
code
paths
as
well
as
have
one
place
to
add
all
new
features
going
forward
where
it
benefits
all
content
types.
That
way
we
can
go
faster
in
the
future
and
work
on
new
and
exciting
features
in
the
geo
team.
B
So,
looking
forward
towards
wrapping
up
that,
we
are
also
starting
a
new
long-term
project
over
in
the
getaway
cluster
group,
where
we
want
to
improve
the
efficiency
and
effort
required
to
operate
the
gili
cluster
service.
The
service
is
intended
to
help
have
a
resilient
guilty
service
across.
You
know
many
nodes
to
make
it
more
highly
available
in
case
of
certain
types
of
challenges
or
incidents
and
with
getaway
cluster
right
now
we
have
multiple
sources
of
truth.
We
have
a
database
and
we
have
multiple
nodes.
B
Those
can
lead
to
some
challenges
like
the
ones
outlined
here,
and
we
want
to
go
ahead
and
actually
utilize
raft
to
have
the
guillotine
those
themselves
manage
consensus,
implication
removing
one
potential
source
of
truth
that
could
potentially
become
inconsistent,
so
this
will
overall
improve
the
ability
for
get
a
lead
to
just
kind
of
operate
on
its
own
and
self-heal,
which
you're
looking
very
much
forward
to
in
the
again
kind
of
longer
term
future
here,
but
we're
working
on
it.
Starting
now,
we
are
also
working
on
the
improvements
to
our
overall
database
framework.
B
This
is
important,
as
our
teams
start
to
think
about
partitioning
their
tables
in
particular,
ci,
which,
as
you
can
imagine,
with
every
single
job
being
tracked
in
our
database,
that
table
can
become
quite
big,
so
we're
working
to
help
us
the
ci
team
partition
that
table
and
making
sure
we
have
the
tools
to
help
support
them
in
that.
So
they
can
go
ahead
and
improve
performance
and
ensure
scalability,
for
you
know
time
to
come
here.
B
Moving
on
over
into
key
workflow
usability,
we
can
talk
about
some
improvements
working
on
global
search,
really
excited
about
these.
These
will,
unfortunately
carry
over
from
14
4
into
14.5,
but
again
really
high
impact
and
can't
wait
for
them
to
become
available
on
the
platform.
In
particular,
we
are
making
a
large
change
to
how
advanced
search
looks
and
feels
by
moving
towards
a
left
kind
of
vertical
navigation
method
for
filtering
and
fastening
on
your
search
items.
This
is
a
much
more
common
way
of
viewing
this
and
offering
it
it's
also
more
extensible.
B
So,
for
example,
with
that
we'll
be
adding
labels
to
the
ability
to
facet
as
well
or
filter
on
which
is
really
a
lot
of
the
ways
folks
get
out
there
and
categorize
issues
and
merge
requests,
and
things
like
that
and
so
offering
this
and
the
ability
to
filter
on
will
really
help.
Folks
find
what
looking
for
faster,
which,
again
we
are
really
excited
to
get
out
there
and
have
you
all
be
able
to
take
advantage
of
moving
over
into
more
of
the
maintenance
area
for
our
groups.
B
We
are
working
to
improve
how
our
distribution
team's
pipelines
work.
These
are
the
pipelines
that
build
all
the
container
images
all
of
the
packages
for
all
of
our
just
develop
developers
and
all
our
customers,
and
so
improving
how
fast
these
can
run
and
how
reliably
they
can
run
will
overall
benefit
velocity
and
developer
productivity
across
gitlab
and
all
contributors
which
we
are
very
excited
for.
B
We
are
also
working
towards
improving
support
for
multiple
architectures
on
our
container
images.
We
have
support
for
intel
based
images
today,
but
we
get
a
lot
of
requests
for
arm.
64
builds
for
things
like
graviton,
pi,
4
and
other
arm64
based
platforms,
which
can
offer
higher
similar
performance
for
cheaper
operating
costs
on
these
cloud
vendors,
and
so
we're
looking
forward
to
having
this
available
for
our
customers,
but
we
have
to
build
the
kind
of
support
for
multiple
architecture
first
before
we
can
go
at
arm64
next.
B
C
Thank
you
so
much
josh
hi
everyone,
my
name
is
sara
willner,
I'm
the
group
manager
of
product
for
the
create
stage-
and
I'm
here
today
to
walk
us
through
the
highlights
for
the
dev
section
for
the
15.5
milestone
so
for
the
planned
stage
manage
stage
and
the
create
stage
all
highlights.
I'm
talking
about
today
support
the
fy23
investment
theme
of
key
workflow
usability
I'll
start
with
a
manage
stage
coming
from
our
authentication
and
authorization
group,
we're
going
to
be
working
on
extending
group
as
cim
to
the
instance
level
full
self-managed
users.
C
Now
this
is
going
to
allow
administrators
to
better
manage
end-to-end
life
cycle
management,
namely
the
deep
provisioning
of
users
at
the
end
of
their
life
cycle.
This
means
that
when
users
are
deactivated
in
their
identity
provider,
they'll
automatically
be
deactivated
in
gila.
Previously
this
was
a
manual
step
we
required
administrators
to
take
on
to
the
optimize
group.
The
optimize
group
is
going
to
be
starting
on
a
proof
of
concept
for
a
metrics
comparative
dashboard,
so
git
lab
analytics.
We
know
provide
high
value
to
executives.
C
C
We
want
this
experience
to
be
intuitive,
for
them
to
be
able
to
glean
insights
that
are
relative
specifically
to
their
business
from
the
import
group
for
the
manage
stage,
they'll
be
making
iterative
improvements
to
the
github
importer,
so
when
migrating
projects
from
github
to
gitlab
for
merge
across
specifically
those
are
mapping
to
pull
requests
from
the
originating
tool.
Today,
all
comments,
including
the
pull
request
itself,
are
migrated
into
gitlab.
However,
any
of
the
associated
history
and
events
are
not.
C
C
Onto
the
create
stage
coming
to
us
from
the
code
review
group
they'll
be
working
on
making
the
merge
widget
on
the
merge
request.
That's
a
mouthful
real
time,
so
this
widget
on
the
merger
quest
takes
inputs
from
lots
of
different
checks
and
actions
on
the
page.
In
many
cases,
things
can
be
resolved
or
changed
quickly,
but
the
merge,
but
button
status
is
not
updated
to
reflect.
The
latest
changes.
C
These
include
protected
branches,
approval
rules,
code
owner
approvals
and
many
more
and
you
put
these
in
place
to
enforce
adherence
to
policies
that
maintain
the
quality
of
your
source
code.
A
written
study,
along
with
much
customer
feedback
revealed
to
us
that
today,
people
struggle
to
find
all
the
different
controls
and
understand
how
they
impact,
along
with
other
settings,
people's
experiences.
C
C
We
will
be
remote,
removing
view
and
creation
permissions
from
the
guest
user
role
and
finally,
from
the
plan
stage,
we
recently
released
tasks
as
of
an
available
work
item
in
gitlab
and
in
gitlab
fashion.
We're
iterating
on
the
future
to
continually
add
value.
Each
milestone
and
50.5
will
be
enabling
labels
on
tasks
as
a
way
to
categorize
them
and
associate
them
with
larger
projects
or
initiatives.
C
Much
like
issues,
epics
and
merch
requests
all
right.
That's
it
from
the
dev
section
and
david
I'm
going
to
pass
it
back
to
you.
D
D
Don't
have
api
definitions
available,
but
these
are
important
because
they're
used
to
guide
the
testing
coverage,
and
so
it's
a
barrier
to
entry
to
help
with
that
and
the
fact
that
we
have
all
the
source
available,
they're
going
to
start
trying
to
automatically
detect
and
create
these
api
definitions,
which
can
then
be
fed
for
dynamic
analysis.
Api
testing,
based
on
their
research
java
spring
boot,
is
one
of
the
most
common
enterprise
platforms,
so
they're
going
to
start
their
first.
D
D
Our
static
analysis
group,
their
main
feature
that
they're
going
to
continue
working
on,
is
automatic,
revocation
of
any
gitlab.com
tokens
that
are
discovered
in
public
repositories.
So
this
is
a
great
security
and
safety
feature
for
any
public
projects.
That
may
not
even
realize
that
this
sensitive
information
has
been
leaked
out,
they're
going
to
leverage
this
the
functionality
on
gitlab.com,
because
that's
where
the
revocation
utility
currently
lives
in
the
future.
The
plan
is
to
extend
this
to
our
self-managed
customers
as
well.
D
D
for
our
composition,
analysis
team,
they
are
looking
to
start
replacing
license
finder
so
license.
Finder
is
the
open
source
project
that
we
used
to
scan
for
and
detect
any
of
the
licenses
in
your
dependencies
and
projects.
But,
unfortunately,
the
project
is
not
very
well
maintained
and
that's
made
it
very
difficult
to
quickly
add
any
new
features,
rather
than
simply
replace
it
with
another
analyzer.
D
The
plan
is
to
leverage
the
fact
that
we
can
generate
s-bom
files
from
our
container
and
dependency
scanners
and
we'll
start
storing
those
in
a
dedicated
database.
This
will
essentially
allow
us
to
keep
track
of
all
of
the
licenses
across
all
of
the
third-party
dependencies.
In
your
entire
gitlab
instance,
it
won't
require
re-scanning
projects
that
are
not
seeing
any
new
dependencies
inside
of
them
now.
This
group
is
also
going
to
continue
to
contribute
some
resources
towards
continuous
vulnerability
scanning.
D
So
the
threat
insights
team
is
part
of
the
move
to
govern,
has
picked
up
a
new
category
dependency
management
and
we'll
be
taking
on
some
of
this
work
to
to
continue
forward
the
continuous
vulnerability
scanning.
What
this
essentially
does
is
again.
We
are
creating
dedicated
databases
to
store
all
of
the
dependency
information
from
these
s-bom
files,
as
well
as
all
of
the
security
advisories
that
come
from
our
various
feed
and
information
sources.
D
By
storing
these
in
the
database,
rather
than
relying
on
scan
jobs,
we're
now
able
to
track
any
changes
to
new
dependencies
or
new
security,
advisories
automatically
cross
reference,
those
on
the
real
side
and
surface
any
vulnerable
dependencies,
for
instance,
anywhere
inside
of
your
gitlab
instance
with
while
without
having
to
rescan
those
projects.
We
can
also
leverage
this
to
create
new
vulnerability
records
against
those
projects
again
without
having
to
do
any
scanning.
D
For
our
compliance
team,
which
is
also
a
new
addition
to
the
new
governed
stage,
they
are
going
to
add
start
adding
default
compliance
framework
labels
at
the
group
level.
So
today
the
compliance
framework
is
a
great
way
to
enforce
policies
against
your
projects
simply
by
applying
one
of
these
group
compliance
framework
labels
to
it.
D
D
This
is
something
that
is
available
today
for
our
scan
result
policies
so
for
customers
or
users
that
are
not
comfortable
or
familiar
with
hand
creating
yaml.
This
is
a
simple
way
to
build
these
inside
of
the
gui.
It
is
still
backed
by
the
same
yaml
information
that
gets
committed
and
stored
in
your
project.
Repository.
E
Awesome
thanks
matt
hi
everyone.
My
name
is
taylor
mccaslin.
I
am
a
group
product
manager
for
our
recently
renamed
data
science
section.
Today,
I'm
going
to
talk
about
a
couple
of
different
areas
to
start
I'll
cover
our
model.
Ops
apply
to
ml
area
which,
for
our
product
theme,
is
focused
on
key
workflow
usability
improvements
with
15.4.
E
We
are
releasing
gitlab's.
First
novel
machine
learning,
powered
feature,
suggested
reviewers
it's
behind
a
feature
flag
and
is
rolling
out
over
the
next
couple
of
weeks
as
part
of
a
limited
availability
with
15.5
we're
going
to
expand
that
availability
to
all
ultimate.com
customers,
as
well
as
reserve
time
to
create
feedback
fixes
for
any
early
customer
usage.
We
also
are
going
to
transition
our
existing
beta
bot
customers
to
this
new
ui
integrated
experience.
We
have
various
other
planned
improvements
to
the
underlying
model.
E
The
way
that
we
do
authentication
with
the
back
end,
as
well
as
additional
data
collection
to
improve
the
model
itself.
E
So
that's
a
quick
overview
of
suggested
reviewers
and
then
moving
on
to
our
ml
ops
group.
This
again
is
focused
on
key
workflow
usability.
We're
planning
to
modify
the
existing
gitlab
package
registry
to
support
model
hosting
for
a
model
registry.
You
can
actually
accomplish
this
today
using
generic
packages.
E
However,
we
want
to
provide
support
for
models
natively
within
the
package
registry,
so
we're
going
to
begin
our
experiment,
basically
expanding
the
package
registry,
if
you
host
models
and
need
to
manage
various
different
models
and
metadata
associated
with
them,
we'd
love
your
participation
in
this
issue
and
feedback
of
what
you'd
like
to
see,
particularly
in
terms
of
what
kind
of
metadata
you
want
displayed
in
the
ui
and
then.
Finally,
our
incubation
engineering
group
is
focused
on
integrating
enough
flow
within
gitlab.
E
So
if
you
use
ml
flow
today,
which
is
an
open
source
technology
to
do
experiment,
tracking
related
to
model
management
and
machine
learning
research,
this
would
be
a
great
issue
for
you
to
participate
in
and
to
look
at
how
we're
potentially
going
to
integrate
ml
flow.
E
Basically
you'll
be
able
to
track
your
model
experiments
within
gitlab.
Again.
This
is
an
experimental
feature
from
our
single
engineering
groups,
and
I
will
just
briefly
touch.
We
also
do
have
our
anti-abuse
group
focused
on
get
lab
hosted.
First,
while
there's
no
user
facing
features
to
highlight,
I
do
want
to
cover
that
they
are
doing
behind
the
scenes,
work
to
improve
stability
and
to
combat
abuse
across
the
platform.
That
is
an
ongoing
effort
and,
with
that
I'll
hand
it
over
to
kevin
to
talk
about.
F
Hi
everyone,
my
name,
is
kevin
I'll,
be
representing
opps
today,
so
the
ops
section
is
comprised
of
five
stages:
verify
package,
release,
configure
and
monitor,
and
we're
responsible
for
building
and
testing
your
code
to
releasing
and
deploying
it
to
configuring
and
managing
your
cloud
infrastructure
and
finally,
monitoring
in
13.5
we
have
quite
a
number
of
improvements
planned
around
the
theme
of
improving
key
workflow
and
extending
our
lead
in
ci
cd.
But
today
I'm
just
going
to
share
four
of
those
with
you.
F
First
and
foremost,
the
runner
group
is
making
it
easier
for
administrators
to
manage
their
fleet
of
runners.
Previously
previously,
admins
can
only
set
c
runners
that
they
can
administer
in
the
ui
we
plan
to
enable
them
to
see
and
manage
all
runners
that
are
available
to
them,
including
shared
runners,
run
and
runners
from
other
parent
groups.
Here's
a
mock-up
of
what
that
will
look
like
so
you'll
see
that
there
are
runners
that
you
can
administer
as
well
as
runners
that
are
simply
available
for
you
to
run.
F
The
second
item
I
want
to
share
is
that
the
group
pipeline
insights
is
working
to
enable
a
better
workflow
to
manage
artifacts
previously
without
the
appropriate
information
on
the
artifacts
page.
It's
really
hard
to
understand
where
the
artifacts
came
from
and
what
they
can
be
used
for
we're,
adding
critical,
contextual
information
to
in
to
enable
better
and
morgan's
in
a
single
view.
F
The
third
thing
I
want
to
show
you
is
something
I
am
personally
really
excited
about,
and
so
the
configure
group
has
been
working
to
allow
projects
to
use
agents
from
groups
that
the
project
is
not
directly
related
to
without
following
a
specific
group
or
project
hierarchy.
This
is
really
important
because,
as
a
group,
you
may
want
to
only
register
a
certain
number
of
agents
that
has
access
to
your
kubernetes
cluster.
So
if
you
look
at
this
particular
setup
here,
the
feature
project
actually
previously
cannot
use
the
agent
that
was
registered
under
the
agent
project.
F
But
with
this
improvement,
that's
rolling
out
in
15.5,
we
will
enable
you
to
not
have
that
strict
hierarchy
or
change
your
hierarchy
in
order
to
use
agents
are
registered
somewhere
else
within
your
group
organization.
We
think
this
is
a
huge
improvement
and
will
allow
a
lot
more
people
to
take
advantage
of
the
agent
using
ci
cd,
workflows.
F
Last
but
not
least,
I
want
to
share
something
that
the
release
group
is
working
on.
They've
been
busy
continuously
improving
the
environments,
page
and
gitlab
users
today
use
the
environment
space
to
detail
and
manage
their
deployments
and
answer
questions
such
as
what
is
deployed
to
production.
Exactly
and
one
thing
that
I
was
previously
missing
was
the
environments
page
didn't
show
the
git
tags,
that's
related
to
a
commit,
so
that
made
it
harder
to
answer
that
question
what
is
deployed
so
in
15.4,
in
the
release?
F
A
Thank
you
kevin
and
thank
you
all
presenters.
This
is
another
great
kickoff
call
some
of
the
things
that
I'd
like
to
highlight,
and
I
will
note
these
are
just
a
couple.
I
grabbed
there
are
lots
of
more
available
on
the
kickoff
page
for
gila.
I've
hosted
first
automatic
revocation
of
gitlab.com
tokens
found
in
public
repos
very
excited
to
see
the
continued
improvement
of
our
security,
offering
utilizing
raf
for
replication
and
consensus
with
getaway
cluster.
I'm
going
to
tell
you.
A
These
are
all
my
favorite
features,
so
just
don't
bear
with
that
as
I
go
through
them,
but
excited
to
see.
Getaway
cluster
continue
to
mature,
improved
database
framework
to
support
teams
and
partitioning
their
own
tables.
A
The
verify
team,
in
partnership
with
enabling
did
a
great
job
to
improve
performance
around
ci
and
be
great
to
see
other
teams
and
leverage
that
as
well
for
improved
key
workflow
usability,
which
I'll
tell
you
most
of
our
features
were
today,
which
excites
me
a
lot
to
have
usability
at
the
forefront,
suggested
reviewers
will
move
to
ga
for
all
ultimate
sas
users
great
to
see
our
first
say:
ai,
assisted,
applied
machine
learning,
feature
ship
improved.
A
The
artifacts
table
view
to
support
more
data
kevin
just
highlighted
that
it
was
great
group
level
settings
for
default
compliance
frameworks
to
apply
to
new
projects
due
to
improvement
of
what
we're
doing,
with
ultimate
extend
our
lead
or
I'm
sorry,
extend
our
efforts
on
work
items
and
introduce
labels
onto
tasks.
Task
by
far
is
growing
very
quickly.
If
you've
not
played
with
it,
it's
awesome
be
sure
to
check
it
out.
A
A
Efforts
for
our
executive
dashboard,
including
comparative
metrics
as
gillab,
becomes
more
and
more
valuable
enterprises
executives
want
to
see
those
stats
and
it's
exciting
to
see
what
heims
team
is
doing
and,
finally,
for
our
externally
nci
cd
group
runners
and
being
able
to
see
all
runners
available
in
that
group,
kevin
showed
some
really
great
screenshots
of
that
a
lot
of
projects
to
use
agents
from
groups
not
directly
related.
I
agree
with
kevin.
A
I
was
one
of
my
exciting
ones
from
the
op
section
and
then
finally
beginning
to
look
at
the
package
registry
as
a
model
registry
and
beginning
to
support
mlap's
needs
for
our
users.
So
again,
that's
just
a
small
sampling
of
everything
everyone
covered
and
thank
you
very
much
for
presenters
for
that
great
overview,
again
check
out
the
kickoff
page
to
see
the
full
list
of
items
and
please
like
and
comment
on
the
issues
to
engage
with
the
team.