►
From YouTube: Think Small - job templates
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
and
welcome
to
the
think
small
session
on
the
job
templates,
and
this
is
a
we
are
continuing
the
discussion
from
the
big
session
and
that
we've
done
over
the
la
in
the
last.
I
think
like
almost
a
month
ago,
and
we
took
our
time
to
really
think
about
the
the
solution
that
we
want
to
to
all
out,
and
there
is
a
an
issue
that
I
hope
most
of
you
and
I'm
gonna
share
it.
Most
of
you
valid
already
where
I,
when
I
rig
up
the
the
problem.
A
I
think
it
was.
It
was
a
specific
problem,
but
it
had
like
several,
like
maybe
a
specific
theme
I
would
say,
but
have
like
several
problems
and,
as
you
can
see
here,
like
teams
are
not
aware
of
the
available
template
and
using
the
include,
and
I
think
that
in
the
think
big
session,
we
talk
a
little
bit
about
the
actual
implementation.
But
then,
when
we
start
thinking
about
okay,
like
what
is
the,
what
is
the
the
minimal.
B
A
That
we
can
bring
to
our
customers-
and
I
also
want
to
share
with
you,
like
the
opportunity
canvas
that
I've
created,
based
on
based
on
the
customer,
discuss
discussions
and
by
the
way
this
is
like
a
rolling
document
and
and
if
you're
not
aware,
this
is
something
that
product
manager
need
to
prepare
whenever
they
are
launching
something
like
a
big
feature
and
and
like.
You,
are
all
more
than
welcome
to
read
this
through
thoroughly
and
add
your
comments
and
and
questions.
This
is
your
way
to
to
contribute
and
I'll.
A
I've
explained
the
problem
when
we
start
talking
about
it
and
the
pain
and
some
of
the
work
around
and
also
the
business
case.
A
The
impact
like
how
many
users
are
impacting
by
that
and
what
are
the
potential
user,
but
at
the
end
of
the
day,
we've
reached
to
what
we
think
will
be
like
the
the
minimal
viable
solution
that
we
can
provide
for
our
users,
and
we
believe
that
the
first,
let's
the
first
time
we
see
we'll
answer,
will
obviously
will
not
answer
all
the
customer
problem,
but
will
only
answer
one
problem,
which
is
mainly
on
the
discoverability
like
how
will
users
be
able
to
know
what
are
the
available
templates
that
the
organization
have
and
when
we
thought
about
it,
we
said
okay.
A
A
Okay,
because
it
doesn't
really
matter
if
you
talk
about
like
job
templates
or
pipeline
templates
or
or
or
something
that
you
can
share,
or
maybe
something
that
you
just
need
to
clone
and
and
modify
it's
just
like
it's
just
like
nuance
on
different
templates
that
we
have
or
different
types
of
template,
but
at
the
end
of
the
day,
like
the
the
user
experience
and
the
framework
to
support
that
should
be
the
same.
It
doesn't
matter
if
it's
like
a
template
for
the
entire
pipeline
or
template
for
like
a
simple
atomic
action.
A
So-
and
this
is
why,
when
me
and
nadia
created
this,
this
solution,
obviously
based
on
feedback
from
users
and
and
from
all
of
you,
and
we
thought
that,
like
the
first
thing,
is
to
make
sure
that
the
solution
will
allow
the
user
to
be
aware
of
what
are
the
existing
template
and
know
what
the
template
is
doing.
How
can
they
use
it?
How
can
they
configure
it
if
needed,
and
what
do
they
need
to
modify
in
their
pipeline
in
order
to
start
using
that
template?
A
Only
after
we'll
have
that,
then
we
need
to.
We
can
dive
into
like
specific
okay.
Is
it
like
a
job
template
or
is
it
a
template
that
will
replace
the
entire
pipeline,
and-
and
as
I
mentioned
here
like,
why
do
you
focus
on
the
problem?
That's
the
biggest
pain
the
customers
are
experiencing
like
today.
They
build
different
framework,
different
ways
on
supporting
this
use
case,
but
the
main
challenge
that
they
have-
and
I
would
say,
the
challenge
that
we
can
help.
A
There
are
like
multiple
challenges
that
different
teams
are
addressing,
but
the
challenge
that
we
can
we
can
help
them
is
knowing
what
what
is
out
there
and
we
can.
A
We
can
harness
the
pipeline
editor
in
order
to
do
so
and
like
here
also,
I
explain
a
little
bit
what
I
just
discussed
that
doesn't
matter
the
type
of
implementation
we
need
to
have
the
framework
and-
and,
as
I
said,
we
can
lead
by
example.
We
can
tell
our
customer
hey.
This
is
how
we
do
it
in
gitlab,
okay,
because
we
have
our
own
templating
library.
C
So
that
so
that,
so
that
idea
is
that
I
sorry
can
you
hear
me
hello?
Yes,
yes,
yeah,
okay,
so
the
idea
is
that
we
we
have
a
template
guideline
right
and
then
we
provide
it
for
customers
so
that
they
can
maintain
their
templates
a
little
bit
more
efficiently
or
neatly
whatever
you
say.
So
maybe
this
is
more
than
just
a
guideline.
Stuff
like
there
is
a
future
implementation
is
going
to
happen.
C
A
B
I
just
think
kind
of
point
one
and
point
two
are
kind
of
significantly
different
like
they
could
be
separate
in
vc
steps
like
point
like
your
proposed
solution.
Number
one
be
made
aware
of
any
existing
templates.
They
can
use
that
feels
like
that's
kind
of
like
step,
one
of
the
iteration
steps
as
well
or
like
it
kind
of
feels
like
adding,
perhaps
a
link
or
making
them
more
visible
and
helping
them
understand
what
they're
doing
could
actually
be
broken
up
into
two
separate
mvcs
independently.
Almost
in
parallel.
B
In
the
sense
that
you
could
raise
the
visibility
of
the
current
templates
as
one
one
thing
that
could
be
done,
that
could
be
a
front-end
thing.
I
I'm
just
spitballing
that
it
could
be
a
link
to
them
or
a
list
of
them
or
it
may
be
just
the
same
thing
have
the
a
selector,
but
you
separately,
number
two:
you
could
as
an
mvc,
expand
the
comments
about
templates.
B
A
I
I
I
agree,
and
it
actually
it's
not
listed
here
in
the
implementation
step
I
think,
but
like
it
is.
Actually
I
think
it's
I
think
it's
this
one
but
but
like
I
agree,
I
mean
there
is
definitely
a
lot
of
work
that
we
can
own
the
on
the
content
of
the
template
in
terms
of,
but
in
content
I
don't
mean,
like
the
actual.
A
What
is
the
template
is
doing
but
like
with
with
comments
and
and
and
other
guidelines
in
the
template,
and
also
there
is
like,
if
you
take
like
a
step
back,
you
can
see.
Okay,
let's
look
at
like
the
overall
visibility
of
the
template.
A
I
would
like
to
go
over
the
implementation
step,
because
I
think
it
will
probably
help
out
understand
what
is
this
the
proposed
solution,
so
the
and
it
doesn't
need
to
be
like
the
first
thing,
but
I
think,
like
one
of
the
biggest
steps
that
we
would
like
to
do
is
first
of
all,
let's
take
all
of
our
templates
that
we
have
to
do
and
and
and
and
and
move
them
to
a
to
a
separate
group
or
a
separate
project,
because
today
there
is
an
issue
here,
a
little
bit
the
problem
and
and
how
does
it
reflect
address
the
visibility
thing
right?
A
And
if
I
find
them,
there
is
no
way
for
me
to
understand
what
the
template
is
doing
unless
I'll
go
into
the
template
and
maybe
or
maybe
not,
there
will
be
like
some
explanation
here.
For
instance,
I
don't
have
any
clue
what
those
templates
are
doing.
I
see
that
the
templates
are
including
other
templates
and
there's
no
way
for
me
to
find
it.
I
need
to
go
back
to
you
know
to
to
to
this
fall
there.
So
that's
that's
the
first
pain
like
you're,
experiencing
the
first
pain
that
I
have
as
a
user.
A
What
is
pages
like
what
are
all
of
those
now,
if
you
look
at
one
example
that
dalvin
created
like
if
you
take
like
the
same
template
and
just
move
them
to
something
like
that
to
to
like
a
group
or
a
project,
and
imagine
like
that,
every
every
liner
is
actually
a
single
template,
so
I'll
go
here,
and
there
is
a
readme
that
I
can
understand
what
the
template
is
doing
it's
in
its
own
project,
so
maybe
we
can
go
back
and
see
like
other
versions
and
so
it,
and
maybe
that
we
can
add.
A
Also,
like
example,
project,
so
there
is
more
for
me,
as
a
user,
to
help
help
me
consume
the
templates
that
we
have
and
and
once
we
will
move
those
templates
into
like
this
structure
then
like
the
first
thing
will
be
to
to
add
some
sort
of
even
a
button,
just
a
button
to
redirect
the
user-
probably
not
here
but
think
about
it.
A
C
C
A
Yes,
yes,
yes,
it's
it's
just
a
mock-up.
Okay,
I'm
sure
that,
like
in
the
implementation
itself,
you
probably
need
to
see
more
details,
but
by
the
way,
that's
a
good
question.
What
you're
asking
because,
like
the
next
thing,
this
is
maybe
something
that
we
need
to
do
before.
There
is
an
issue
that
created
about
adding
metadata
to
the
template,
okay
and
and
so
adding
different
attributes
to
the
template,
and
maybe
we
can.
A
C
So
yeah,
I
just
want
to
talk
a
little
bit
about
the
the
metadata
so
yeah
I
mean
like.
First
of
all,
your
proposal
on
the
you
know
linking
to
the
the
external
project
or
group
like
a
template
group
that
darwin
created.
Is
it
correct?
It's
interesting
idea
that,
like
it,
has
a
as
a
value,
can
ship
a
value
for
end
users.
Can
I
share
my
screen
a
bit?
C
C
So
I've
been
thinking
about
the
new
template
architecture
and
then
writing
this
the
blueprint
stuff,
it's
a
bit
lengthy,
but
it's
very
simple
and
achievable
in
like
three
months.
So
let
me
skip
to
the
new
architecture.
C
I'm
gonna
skip
the
the
program
problem
statements.
Well
so
yeah
you,
you
just
mentioned
that
we're
gonna
add
ci
cd
template
metadata.
This
is
a
you
know,
yeah.
Let
me
walk
through
a
bit
from
the
beginning,
yeah,
so
the
new
yeah.
C
So
what
I'm
thinking
about
the
rethink,
the
cd
templates.
So,
first
of
all,
we
should
correctly
capture
the
definition
of
cc
templates.
Today
we
can
observe
some
misinterpretations
in
the
future
category.
For
example,
we
see
the
following
github
serial
like
this,
and
then
you
might
think
that
the
this
github
cmo
includes
a
you
know:
autodesk
devops
template
and
then
the
helper.
Whatever
you
know,
the
local
github
say
yaml
file
that
has
some
job
specs,
but
you
know
it
technically.
This
file
also
can
be
a
template
as
well.
C
Not
only
the
template
keyword
is,
you
know,
keyword
to
specify
the
template,
whether
it's
if
it's
a
template
or
not,
the
template
can
be
the
basically
anywhere
like
a
include
local
project,
remote
template.
We
have
four
keywords.
Each
keyword
points
to
the
different
storages.
For
example.
Template
is
a
local
file
strategy
in
a
github
github
github
rails
and
include
the
project.
Is
italy,
the
other
other
repository?
They
include
local,
as
the
current
universally
remote
is
external
server
templates
can
be
existed
anywhere.
C
Well,
I
think
it.
This
is
a
obvious
and
then
like.
If
we
think
about
this
we
have
to,
we
have
to
know
that
which
kid
loves
is
a
template
or
which
is
not.
So
that's
why
we
add
a
gigantic
metadata,
like
we
explicitly
tell
to
the
system
that
this
guitar
cml
file
is
a
template.
C
So
it's
going
to
be
looked
like
this
so
from
here
to
there
it's
a
normal
github
cmo
file,
but
we're
going
to
add
this
template
keyword
that
has
her
these
attributes
that
the
name
of
the
template.
This
is
a
human
readable
name,
like
you
showed
me,
the
ui,
and
that
you
know
the
right
page,
there's
a
template
name
which
were
shown.
C
The
name
should
be
extracted
from
here
template
metadata
and
the
description,
the
how
to
use
the
template
and
the
type
of
the
template
we're
talking
about
that
pipeline
template
and
the
job
template.
I
slightly
adjusted
it
to
the
workflow
template
the
task
template,
but
it's
basically
the
same
idea
and
like
api
version,
also
about
variables
constraints.
C
You
know
these
are
things
that
to
specify
the
spec
of
the
template,
how
users
should
use
it
and
then,
on
top
of
that,
we
can
validate
it
the
template.
If
the
template
is
correctly
used
like
if
the
the
required
variables
is
actually
specified
or
the
template
is
itself
could
be
invalid.
C
Right,
like
we
have
a
50
over
50
templates
in
a
leave,
something
the
templates
folder.
But
there
are
many
inconsistencies
there
that
so
that
you
cannot
combine
multiple
templates
right,
like
global
keywords,
are
conflicting,
so
these
type
validations
we're
gonna
check
that
at
the
system
level
that
hey
this
template
is
a
valid
like
this
template.
The
discipline
is
totally
messed
up,
so
we
should
fix
it
yeah.
C
So
that's
a
idea
of
the
template
metadata
and
then
you
also
mentioned
about
the
discoverability.
So
my
answer
for
that
problem
is
ca.
Template
registry
I
mentioned
in
the
last
call,
though
so
think
about
the
content.
Outrageously,
continued
doc
registerly
we
have
already
the
future
like
users
cannot
can
upload,
can
push
the
build
image
to
the
container
registry,
either
private
or
a
project
and
then
expose
it
to
the
specific
project
group
and
then
yeah.
C
So
we
do
the
same
thing
for
the
gitlab
c
template
and
we're
going
to
extend
the
existing
package
registerly
the
thanks
to
the
the
great
default
to
the
package
team.
We
can
use
the
package
basically
for
this
purpose.
C
It's
super
easy,
so
the.
C
We're
gonna
extend
the
the
package,
the
package
structure.
This
is
the
technical
details,
blah
blah
blah,
but
basically
we're
gonna.
Add
this
table
that
every
time
user
is
gonna,
upload
user
I
mean,
including
me-
I
mean
gitlab
and
any
users,
any
external
contributors.
Any
organization
can
upload
their
templates
to
your
specific
project
registerly
and
then
these
data
are
just
into
the
database,
which
is
extracted
from
the
metadata.
C
B
C
So
this
attached
file
is
a
gitlab
same
yaml
file
in
csd,
template
context
and
then
so
here's
a
kind
of
similar
way,
the
generic
package.
You
know
the
package
works
and
we
extend
it
for
a
template
that
extracts
the
metadata
from
the
template
and
then
purchase
into
the
database.
C
C
Well,
so
so
yeah
like
a
with
this
approach,
like
I
said
since
we
have
all
database
records
that
what
templates
we
have
for
what
powers,
what
type,
what
description
and
we
can
show
it
in
the
ui
and
then.
C
So
here's
a
you
know
that
the
versioning
is
a
big
missing
piece
in
the
gitlab
cmo
csd
template
so
depending
on
the
package
registerly,
we
can
also
support
this
versioning
specification
or
even
floating
version.
This
is
really
needed
in
the
auto
devops.
C
Well,
so
sorry
that
I
don't
want
to
hold
this,
I
think
it's
a
most
of
the
time.
So
I'm
going
to
stop
here
so
I
mean
I
have
a
different
answer
for
the
original
issue
that
you
guided
us.
So
I'm
going
to
ping
you
all
in
the
blue
plenty
much
weakest!
C
A
A
C
For
example,
look
at
like,
like
I
said,
look
at
container
registry
when
you
push
the
gitlab
like
okay
images,
maybe
you
run
the
build
job
in
a
gigabyte
like
pipeline
running
pipeline
assembly,
we
can
publish
the
package
to
the
package,
basically
in
the
the
project
pipelines
and
then.
C
Yeah
the
published
package
can
be
discoverable
in
the
same
project
context
or
the
same
group.
If
it's
a
private
group,
then
the
like,
if
we
can
also
register
private
templates
for
a
specific
group,
yeah
and
someone's.
A
Yeah
I
mean,
I
guess
there
is
a
there-
is
more
to
to
look
into
that
and
like
we
are
at
the
end
of
the
of
the
time
like
I
guess
I
should
have
scheduled
this
meeting
for
a
bit
longer,
and
maybe
we
can
continue
talking
on
the
on
the
issue,
but
I
think,
like
I
I
want
to.
I
want
to
understand,
like
what
would
be
like
the
next
minimal
thing
that
we
were
able
to
do.
Maybe
we
can
work
on
that
on.
Parallel
will
be
like
adding.
A
C
Yeah
yeah
so
like
first
of
all,
template
metadata
is
needed,
like,
like
you
mentioned
in
this
issue,
that
template
metadata
will
be
useful
to
show
that
something
data
in
the
ui.
C
This
issue
is
needed
either
way
so
and
then
we
can
work
parallelly
on
the
thing
like
a
link
moving
the
templates
to
the
other
project.
I
guess
that
that
also
causes
some
problem,
though
yeah
that's
a.
A
Okay,
I
I
know
that
we
are
like
one
minute,
but
I
I
want
to
like.
I
ask
if
there
isn't
like
any
thoughts
or
questions
from
like
other
folks
that
are
hearing
that
call
before
we'll
close
it
and
continue
the
discussion
online
may.
Maybe
maybe
we
fully
need
we'll
do
like
another
thing
small
to
continue,
but
I
want
to
make
sure
other
thoughts
are
being
heard.
D
Yeah,
just
one
more
one
thing
I
just
looked
at
in
the
agenda
and
it
looks
like
we
didn't
take
any
notes,
just
a
reminder
for
all
the
future
meetings.
We
should
probably
keep
notes
in
the
agenda
when
somebody's
talking
in
their
points.
Just
so
we
can
look
bad
at
it.
Look
back
at
it
and
then
remember.
A
It's
not
the
same,
yes,
it
is
recorded,
and
so
we
can
like.
I
can.
I
can
recap
the
discussion
on
on
the
issue
actually
and
we
can
continue.