►
From YouTube: CMS update Pipeline Authoring
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
Hi
everyone,
my
name
is
david
gravitz,
and
this
is
a
category
maturity
update
for
the
pipeline
authoring
team.
As
you
most
of
you
probably
know,
the
pipeline
authoring
is
a
fairly
new
team.
We
splitted
ci
continuous
integration
team
into
two
where
continuous
integration
is
responsible
for
running
and
analyzing.
Your
pipeline
and
pipeline
authoring
is
responsible
for
defining
creating
your
pipeline
and
optimizing
editing
your
pipeline,
and
since
the
pipeline
authoring
is
a
fairly
new
team
and
we
also
realized
that
traditionally,
gitlab
did
not
invest
in
improving
the
authoring
experience
when
it
comes
to
pipeline.
A
It
makes
sense
for
us
to
set
up
a
scorecard
of
minimal
for
the
pipeline
authoring
team.
Now,
if
you
want
to
learn
more
about
the
maturity
level,
that
gitlab
has
you
can
visit
our
maturity
page
where
you
can
read
about
the
minimal
viable,
complete
and
lovable
maturity
score.
So
I'm
I.
I
have
a
really
high
confidence
that
will
be
able
to
quickly
move
from
minimal
to
viable
and
I've
set
up
a
maturity
plan,
which
is
our
path
to
viable
by
completing
those
three
epics
that
you
see
here.
A
A
A
The
experience
when
it
comes
to
write
and
author
a
pipeline,
so
the
brand
selector
will
allow
users
that
are
working
on
their
non
main
branch
to
work
on
pipeline
editor.
It
appeals
to
us
that
a
lot
of
our
users
are
not
using
master
they're,
not
using
their
main
branch,
especially
new
users,
and
the
second
issue
is
the
second
epic.
So
is
the
first
time
experience
so
when
there
are
new
users
that
are
new
to
gitlab
or
new
to
ci.
A
The
pipeline
editor
does
not
support
those
kinds
of
users
and
flows.
When
we
first
introduced
the
pipeline
editor,
it
made
sense
for
us
to
aim
for
the
existing
users,
because
we
have
a
large
customer
base
that
already
have
running
pipelines.
So
those
were
like
the
first
user
that
we
want
to
interact
with,
but
now
it's
time
to
engage
and
embrace
those
new
users
that
maybe
are
coming
from
cm
or
maybe
are
new
to
gitlab.
A
We
will,
we
will
add
a
grade,
we
will
add
a
score
and
based
on
that,
will
decide
if
we
can
move
from
minimal
to
to
for
minimal
to
viable.
Now,
as
I
mentioned,
I'm
fairly
confident
that
we'll
be
able
to
do
it,
this
is
an
achievable
goal
that
I'm
planning
to
do
on
this.
First
and
complete
in
this
quarter,
so
this
is
it
and
if
you
have
any
other
comments,
thoughts
or
questions
feel
free
to
reach
out
to
me,
thank
you
and
bye.