►
From YouTube: CI/CD template vision
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-
this
is
dave
helschkovitz
from
the
pipeline,
authentic
team,
I'm
here
joined
by
netflix
nikova,
our
ux
designer,
and
I'm
here
to
share
with
you
our
cicd
templating
experience
vision
for
the
coming
year
before
we
start.
Why
are
we
sharing
this
vision?
First
of
all,
we
want
to
make
sure
we
have
an
ambitious.
We
set
an
ambitious
goal
for
the
team
to
improve
our
temperature
experience,
but
I
think
more
important
than
that.
A
A
So
we
want
to
make
sure
that
we
are
capturing
all
those
discussions
and
all
those
requirements
and
provide
the
unified
and
shared
vision.
Of
course,
engineers,
product
and
ux
make
sure
everyone
is
aligned
to
all
the
same
goal.
And,
lastly,
as
you
can
see,
it
is
working
for
caucus.
So
I
do
expect
this
vision
to
er
to
change.
Some
of
the
mocks
you
see
are
very
visionary
and
we
probably
won't
be
able
to
achieve
that
in
this
time
frame.
A
So
we
want
to
make
sure
we
are
communicating
and
capturing
the
right
feedback
feedback
and
drive
further
discussion
to
reshape
our
our
strategy
toward
the
coming
year
and
before
I'll
dive
into
the
background
and
problem
reward
about
the
practice
we've
used.
A
First
of
all,
we've
done
our
user
research,
we've
been,
we've
done
several
of
them
and
the
category
maturity
scorecard
actually
raised
some
interesting
insights
around
templates,
but
also
we've
done
a
specific
problem,
validation
on
template
management-
and
you
can
see
those
interviews
in
this
issue-
and
you
can
see
this
insight
in
in
this
link,
and
we
also
done
some
competitive
analysis
to
understand
how
other
organizations
are
using
templates
and
or
allow
users
to
use
their
templates
and,
as
I
mentioned
more
more
on
that
in
those
linked
issues.
A
So
the
background
for
this
vision,
we
know
that
there
are
many
ways:
users
can
leverage
and
use
templates
in
ci
cd,
and
if
we
look
at
the
single
developer
experience,
we
know
that,
especially
in
onboarding,
but
as
a
developer.
When
you
start
and
want
to
write
your
pipeline,
your
ci
pipeline,
you
don't
want
to
start
with
a
clean
sheet.
A
A
And
now,
if
we
look
at
the
organization
experience,
we
we
see
that
they
have
a
different
experience
so
usually
organization.
They
would
like
that
their
ci,
a
pipeline
will
run
fast,
will
be
smooth.
A
So
for
that
they've
developed
a
whole
practice,
usually
they
maintain
their
own
library
of
templates
and
they
ask
users
their
users
to
use
those
templates
as
a
part
of
their
pipeline,
but
point
to
that
in
the
problem
and
opportunities
that
I'm
going
to
cover
right
now.
So
with
that
some
of
the
issues
that
stood
up
in
the
in
the
interviews,
there
are
a
lot,
but
I
try
to
capture
the
main
parts.
So
first
of
all,
gitlab
provides
a
large
list
of
ci
cicd
templates.
A
A
So
a
partial
of
the
template,
like
a
job
that
you
can
simply
take
into
your
pipeline,
usually
they're
being
used
with
include
or
the
extent
keyword
so
with
those
two
flavors.
We
first
want
to
make
sure
and
the
user
can
easily
tell
the
difference
between
those
two,
because
it
can
be
very
confusing.
Should
I
use
the
include
or
should
they
use
the
thing?
A
The
the
the
word
phrase
is
in
addition:
if
we
are
looking
about
of
a
reusing
template,
we
know
that
reusing
and
sharing
template
will
simplify
your
authoring
experience,
especially
in
large
organization,
think
about
if
some
you,
some
of
your
colleagues,
already
create
or
have
like
a
shared
repository
of
of
jobs,
that
you
can
simply
reuse
and
take.
So
we
want
to
make
sure
it's
easier
for
you
to
to
know
the
existence
of
those
reusable
jobs
and
also
help
you
create
those
jobs
and
share
it
within
your
organization.
A
So
there
are
like
two
two
main
personas
we
are
we
are
serving
here
and
in
addition,
we
noticed
that
you
know
organizations,
especially
a
large
organization,
as
mentioned
in
the
background.
A
They
already
create
their
own
practice
around
ci
cd
on
boarding
and
with
that
templating,
so
they
they
have
their
own
templating
library
and,
and
they
ask
developers
to
use
those
templates
as
a
part
of
their
parties.
So
they
build
an
internal
documentation,
site
wikis.
They
have
to
follow
those
practices
because
they
need
to
serve
all
those
engineers
that
are
using
ci.
A
So
we
want
to
make
sure
we
help
them
drive
additional
adoption
in
the
organization
and
help
them
embed
their
practices
using
gitlab
using
our
own
user
experience
within
our
product
and
and
lastly,
basic
functionality
of
templates
is
versioning
right.
Now
we
don't
support
versioning,
we
want
to
make
sure
user
can
make
contact.
A
specific
version
then
can
use
a
specific
version
version
of
a
ci
cd
template
and
with
that,
I'm
going
to
hand
it
over
to
nadya
she's,
going
to
talk
about
she's
going
to
show
you
the
moocs
and
the
designs
she's
created
thanks.
B
So
as
dope
mentioned
templates,
cic
templates
are
a
critical
tool
for
getting
started
with
ci
and
learning
ci
and
generally
authoring
your
pipeline.
It's
the
main
tool
that
we
currently
have
today
in
gitlab
for
creating
your
your
pipeline,
the
main
aid
that
we
provide
so
all
of
the
different
templates
that
we
currently
have.
We
would
really
like
to
leverage
them
better
and
add
additional
useful
metadata
to
the
templates.
B
Allow
you
to
add
things
like
descriptions
and
perhaps
tag
your
template
in
some
way,
and
then
we
can
leverage
all
of
this
useful
information
in
the
ui
to
make
the
templates
easy
to
browse,
to
make
to
make
it
easy
for
you
to
select
a
template
based
on
the
information
that
you
see
about
it.
So
it's
easy
for
you
to
understand
what
it
does
and
also,
as
dove
said,
we
want
to
make
sure
that
we
leverage
the
different
ways
to
use
the
template
in
the
right
parts
of
the
workflow.
B
So
when
you're
first
getting
started
with
creating
your
pipeline,
maybe
it's
your
first
pipeline
ever
maybe
you've
already
created
pipelines,
but
still
you
would
like
to
have
some
eight,
so
you
don't
start
from
the
blank
slate,
so
you
want
to
start
with
your
pipeline
template
like
a
basic
workflow
template
that
gives
you
the
backbone
for
your
pipeline
and
currently
in
gitlab.
These
are
the
templates
that
are
based
often
on
the
language.
The
framework,
for
example,.
B
Very
heavily
used
template
is
the
docker
template,
for
example,
that
allows
you
to
build
a
docker
image
with
ci
cd.
So
these
are
the
template
templates
that
we
can
surface
during
pipeline
boarding.
So
what
you
see
here
is
the
empty
state
for
gift
lab
ci
cd
and
you
can
get
started
with
any
of
the
gitlab
or
perhaps
community
templates
or
partner
templates
that
are
available.
B
B
Another
problem,
currently
with
templates,
is
that
they're
difficult
to
search,
so
it's
very
difficult
to
understand
what
is
available
so
you're,
starting
with
a
pipeline
for
your
project.
You
probably
have
a
general
idea
of
the
things
that
you
want
to
automate.
Otherwise
you
wouldn't
be
creating
a
pipeline,
some
things
that
you
want
to
achieve,
so
you
probably
would
be
able
to
come
with
some
kind
of
query
in
your
head,
like
what
kind
of
template
are
you
searching
for?
B
So
if
we
make
it
possible
to
assign
some
type
of
tags
to
the
template,
then
we
can
make
it
possible
to
search
for
the
template
in
a
more
granular
way.
So
you
might
filter
the
templates
list
by
the
language
like
what
you
want
to
build,
perhaps
perhaps
test
types
or
deployment
targets,
and
things
like
that.
B
So
these
are
just
some
examples,
but
that's
kind
of
the
idea
that
we
have
to
make
it
much
easier
for
you
to
find
the
right
template
and
another
thing
we
want
to
make:
make
it
easy
for
organizations
to
create
or
to
connect
their
own
library
of
templates.
As
dope
mentioned.
We
already
know
that
many
of
our
large
customers
and
just
generally
large
organizations
maintain
their
own
libraries
of
templates
they're,
usually
a
group
or
a
project
where
they
have
all
of
their
pipeline
templates.
B
So
we
could
make
it
possible
for
them
to
connect
that
library
to
this
ui,
to
make
it
much
easier
for
them
to
onboard
their
developers
onto
their
flavor
of
ci
cd.
So
this
is
the
experience
that
everyone
would
have
so,
regardless
of
whether
you're
a
large
premium
customer
or
your
free
user.
You
would
be
able
to
leverage
existing
github
templates
and
maybe
community
templates
as
well.
B
All
of
these
are
just
ideas,
so
we're
not
making
any
commitments
to
deliver
any
of
this,
but
that's
kind
of
where
we're
going
so
here.
As
you
can
see,
we
can
offer
the
same
type
of
experience,
but
for
an
organization
that
has
a
library
of
custom
templates,
so
the
organizational
workflow
so
organization
templates
would
appear
by
default
and
we
could
recommend
a
template
from
their
custom
library
based
on
the
project
that
is
being
created.
B
You
know
where
to
go
to
and
that's
where
you
get
all
of
the
instructions
to
create
a
pipeline
that
is
compliant
for
the
organization
and
easy
for
you
as
a
developer,
to
just
set
up
and
forget
about
it.
So
once
you
get
started,
let's
say
with
this
recommended
template
for
node.js.
B
You
would
go
to
the
pipeline
editor
where
you
can
further
take
advantage
of
some
of
the
other
useful
onboarding
features.
So,
as
though
mentioned
organizations
also
have
their
own
websites
with
documentation,
wikis
and
whatnot,
where
they
maintain
all
of
the
documentation
around
their
csd
practices.
Just
like
we
do
at
gitlab,
they
have
the
same
thing
and
it
would
be
very
useful
if
we
could
maybe
link
to
that
documentation
from
the
pipeline
editor
or
allow
the
organization
to
create
custom
onboarding
inside
the
pipeline.
Editor
where
the
developer
can
just
easily
go
through.
B
B
Sorry
I
got
a
bit
lost,
would
bring
you
to
a
model,
let's
say,
or
it
could
be
a
page
or
anything
else-
we're
not
really
committing
to
exactly
like
building
building
this
way.
B
But
the
idea
is
to
make
it
easy
for
you
without
leaving
the
editor
to
browse
all
of
the
available
workflow
extensions,
your
organization,
extensions
or
github
extensions
that
we
already
have
like
set
scans
and
security
features,
and
things
like
that,
and
you
would
be
able
to
select
a
version
for
your
extension
and
then
use
the
extension
here
we're
defaulting
to
including
that
extension.
But
there
are
other
ways
to
do
this
as
well
and
we're
still
having
discussions
around
exactly
exactly
which
way
of
inclusion
we
have
to
use
here.
B
But
for
now
we
could
default
to
include,
because
this
is
what
we've
seen
at
least
in
the
customer
interviews
that
that's
what
they
require
their
team
members
to
do
and
yeah.
This
is
just
an
example
of
what
gitlab
extensions
could
look
like.
So
we
know
that
a
lot
of
existing
github
templates
are
used
with
the
include
keyword,
so
they
are
used
as
your
workflow
extensions.
It's
not
something
that
you
copy
and
paste
into
your
pipeline
usually
usually
would
include
it
and
yeah.
B
You
should
be
able
to
do
that
without
leaving
the
editor
as
well,
and
it
should
be
easy
for
you
to
get
access
to
all
of
these
useful
resources
that
we
have
and
same
thing
goes
for
the
workflow
templates.
So
what
we've
seen
is
that
with
workflow
templates,
you
apply
it
kind
of
as
a
backbone
of
your
configuration,
but
a
lot
of
our
users
also
copy
and
paste
parts
of
the
workflow
templates,
or
they
open
the
template
and
they
copy
and
paste
different
parts
from
there.
B
B
So
if
you
want
to
open
the
template,
you
can
preview
it
and
you
can
copy
and
paste
from
there
or
you
if
you
use
your
local
editor,
even
you
might
want
to
just
copy
the
template
and
paste
it
into
your
local
editor
or,
if
you
want
to
use
the
pipeline
editor,
you
can
set
up
that
workflow
directly
in
the
pipeline.
Editor
and
again,
we
want
to
offer
a
unified
experience
for
using
cic
templates,
regardless
of
like
what
type
you're
using
the
ui
should
not
vary
too
much.
B
We
just
want
to
give
you
the
right
tools
to
use
the
template
in
the
right
way,
so
there
should
be
the
same
way
to
search
the
templates
with
the
workflow
templates
as
it
is
with
the
workflow
extensions,
and
this
is
just
an
example
of
using
our
filtered
search
feature
to
search
for
the
right
template
using
the
tags.
B
So
I
thought
it
could
be
a
cool
way
to
leverage
filtered
search,
to
really
make
sure
that
you
can
find
the
right
match
for
you
as
you're
building
your
pipeline
yeah.
I
think
this
is
it.
I
think
it's
still
worth
mentioning
that
this
vision
is
in
progress
and
we
would
really
love
to
hear
your
feedback
on
these
mockups
at
this
point.
B
We're
not
necessarily
getting
feedback
on
the
details
of
the
ui,
but
we
want
to
make
sure
that
everyone
participates
in
the
discussion
around
the
overall
user
experience
for
the
templates,
the
different
types
that
we're
proposing
different
metadata
that
we're
surfacing
the
different
ways
to
include
the
template
like
using
include
or
child
pipelines
or
extend.
B
So
if
you
have
any
ideas
or
suggestions,
please
make
sure
to
reach
out
and
probably
we're
gonna
drive
discussions
in
the
epicore
issues,
though,
feel
free
to
decor
from
here.
A
Sorry
about
that,
thank
you,
yeah.
Just
as
nadia
mentioned
the.
If
you
want
to
follow
the
discussion
and
maybe
add
your
thoughts
and
comments,
I
would
highly
recommend
if
you
scroll
further
down,
you
see
the
link
issues
and
epic.
A
We
have
two
epics
that
we
just
created,
improves
the
icd
template
for
organization
and
improved
csd
template
for
gitlab,
we'll
start
with
the
gitlab,
with
our
template
that
we
provide
for
our
users
and
in
there
we
have
some
of
the
issues
we
are
trying
to
break
it
down
into
an
mvc
like
how
will,
with
version
ci
template,
how
we
add
metadata
to
our
templates,
we'll
be
able
to
see
those
nice
images
and
information
on
a
on
the
template.
A
So
those
will
be
the
ways
for
you
to
follow
the
progress
of
of
this
vision
and
contribute
based
on
your
experience-
and
this
is
it
hope
you
found
this
useful
and
thank
you
and.