►
Description
Chris Balane (Senior Product Manager) and Daniel Fosco (Senior Product Designer) get together to review the epic to Foster environment and deployment adoption, and plan for next steps.
See more:
Epic – https://gitlab.com/groups/gitlab-org/-/epics/6821
Meeting Notes – https://docs.google.com/document/d/1jqHhwoC1BYbe31osVyGraOySsSqZR6gadrZPjcdWjwY/edit#heading=h.768jx874zfxm (internal)
A
So
this
meeting
is
a
brainstorm
for
how
we
can
improve
adoption
of
environments
through
in-app
notifications
in
the
product.
So
we
already
have
an
epic
for
this.
With
a
few
suggestions
that
we'll
go
over
but
yeah,
we
will
try
to
come
up
with
other
ones
in
the
process
as
well
before
we
we,
we
move
down
the
list.
The
first
thing
that
I
actually
want
to
propose.
B
Definitely
I
think
when
we
wrote
this
originally,
we
were
thinking
about
how
we
haven't
been
leveraging
that
that
tactic
specifically,
but
really
the
goal
here,
is
to
increase
adoption
through
the
application
and
getting
users
that
are
using
one
part
of
the
application
to
continue
to
adopt
environments
and
other
release
functionality.
So
perfect.
A
And
I
think
it's
important
to
add
deployment,
even
though
our
customers
can
deploy
using
lab
ci
without
using
environments,
and
they
go
together
very
strongly.
So
I
think
there's
opportunities
for
us
to
foster
environments
themselves
and
then
deployments
themselves,
but
they're
always
talking
to
each
other.
A
A
It's
basically
this,
and
this
is
an
in-app
notification.
I
think
that's
that's
where
the
name
original
name
of
the
epic
came
from.
So
if
you
have
a
yaml
file
that
doesn't
have
deployments
detected,
we
suggest
that
we
have
that
in
the
product
already
there
is
a
a
secondary
step
to
do
the
same
thing
in
the
single
file.
Editor,
the
one,
the
current
implementations
on
the
web
ide.
So
let's
go
over
some
of
the
suggestions
that
we
have
here.
A
I
think
this
this
first
one
you
you
were
mentioning
right
before
we
started
recording
like
some
some
small
low
hanging
fruit.
We
can.
We
can
adopt
in
this
in
this
epic
and
I
think
these
first
ones
are
really
low
hanging
fruit,
just
listing
the
environments
that
we
have.
We
already
have
the
releases
here
so
for
a
given
project.
We
have
these
this
many
environments
and
if
you
click
it,
you
go
to
the
environments
page.
A
I
guess
this
one
would
show
only
if
you
have
environments,
if
you
don't,
we
would
have
an
empty
state,
perhaps
down
here,
there's
a
good
example
here.
So
here
where
you
can
see
the
you
can
go
straight
to
the
readme,
to
the
change
log
to
the
cicd
configuration
and
then,
if
you
don't
have
integrations
configured,
it
shows
this
dashed
button
as
an
empty
state.
So
we
could
have
configured
environments
as
well.
So
if
you
have
environments
they
show
up
here,
if
you
don't,
then
you
have
an
option
to
configure
them
down
here.
A
We
have
this
really
good
suggestion
from
jamie
as
well
that
that
goes
along
with
the
the
issue.
We
have
to
better
connect
releases
and
and
deployments
and
environments,
and
I
think
this
is
a
great
example
where
they
can
help
each
other
right.
Maybe
a
specific
customer
uses
releases
a
lot
to
save
specific
versions
of
their
application
and
specific
assets,
but
then
they
deploy
using
something
else.
A
A
So,
if
you
don't,
maybe
we
have
a
good
empty
state
opportunity
here
linking
to
the
docs,
but
if
you
do,
then
we
can
show
if
a
release
is
deployed
to
which
environment
that's
deployed.
How
long
it's
been
there,
you
know
maybe
status
of
the
pipeline
there's
a
lot
of
opportunities
here.
The
empty
state
would
help
in
issue
adoption,
but
at
the
same
time,
if
I,
if
once
you
adopt,
you,
have
really
good
visibility
here,
that's
one
more
reason
that
you
would
adopt
it
in
the
first
place.
A
A
I'll
be
honest,
I
think
the
way
our
releases
and
our
environments
product
work
is
a
bit
counter-intuitive
in
the
sense
that
they
have
a
lot
of
overlap
with
each
other
because
they
were
created
at
different
different
stages
of
gitlab
existence.
For
with
different
focuses
so
now
we
have
the
opportunity
to
bring
them
closer
together
and
even
though
some
users
will
only
use
releases,
some
users
will
only
use
environments
and
they
can
be
used
for
different
things.
I
think
they're
more
powerful
if
we
bring
them
closer
together.
A
A
We
currently
don't
have
a
lot
of
those
and
I'm
I'm
unsure
if
this
view
here
this
screenshot
is
a.
Is
it
like
a
view
for
for
how
it
could
look
like
in
the
future?
But
if
you
go
to
new
project,
we
have
these
templates
here
right.
Some
of
them
already
have
deployment
setup
embedded
right,
so
I'm
more
familiar
with
the
static
side.
So
you
know
if
you
have
hugo
or
jack
you.
A
I
know
some
of
these
facilitate
deploying
to
a
certain
target
already
we
have
them
here,
netlify
as
well,
that
helps
you
deploy
into
network,
but
we
don't
have
anything
specifically
tailored
to
deployment
right.
Maybe
you
don't
care
too
much
about
which
framework
framework
you're
using
to
your
project.
You
just
want
to
start
a
project
that
deploys
a
target,
so
we
can
definitely
help
help
users
more
more
closely
with
this,
and
this
would
would
also
be
a
huge
collaboration
with
the
pipeline
authoring
group
that
is
already
working
on
these
interfaces.
A
B
We
could
even
have
yeah
like
a
template
for
the
sort
of
typical
environment
setups
like
a
dev
staging
in
production
and
maybe
have
that
you
can't
put
out
of
the
box.
So
all
one
click,
the
the
users
and
their
teams
have
have
all
these
environments
set
up
and
then
that
combined
with
all
of
the
other
sort
of
like
kind
of
nudges
we
were
talking
about
earlier,
I
think,
would
lead
to
the
more
environment.
Adoption.
A
Yeah
absolutely-
and
the
focus
here
is-
is
in-app
changes
right,
so
it
changes
the
ui,
but
obviously
there's
things
to
documentation
and
and
other
other
assets
other
avenues
we
can
use
to
to
foster
this
adoption,
and
this.
This
idea
of
having
having
better
deployments
templates
in
ci
cd
reminded
me
of
of
your
initiative
to
have
like
better
examples
for
how
how
our
product
is
set
up
right.
So
if
we
either
documentation
or
in
the
gitlab
blog
then
come
up
with
content
that
shows
users
hey.
This
is
how
you
deploy
to
gte.
A
This
is
how
you
deploy
to
ecs.
This
is
how
you
configure
your
environment
set
up
for
all
of
these
use.
Cases
like
you
were
mentioning
it
also.
It
will
help
a
lot,
and
I
think
it
should
be
in
this
epic-
maybe
maybe
not
as
an
initial
focus,
but
then
we
can
break
it
down
later,
perhaps
as
something
that
will
contribute
towards
the
same
goal.
A
I
I
made
a
suggestion
back
then,
here
of
an
empty
state
in
the
environments
page.
It's
I
don't
think
it's
not
necessarily
as
strong
as
adding
an
entry
point
elsewhere,
because
the
user
has
to
go
to
the
environments
page
to
see
the
empty
state,
but
we
can
definitely
have
clear,
clear
use
cases
being
shown.
The
empty
states
that
direct
to
specific
points
in
the
documentation
so
how
to
protect
your
production,
how
to
visualize
your
deploys
with
you
know,
maybe
some
illustrations
that
that
shows
the
user.
A
B
B
A
Yeah
from
other
people,
so
this
this
is
what
we
have
in
terms
of
like
the
the
plane.
Onboarding
right
like
you,
either
go
to
the
documentation
or
you
go
here
and
it
takes
you
to
the
documentation.
So
it
is
something,
but
it
can
definitely
be
improved.
I
think
the
documentation
for
environments
is
pretty
good
in
explaining
the
concepts
and
and
the
general,
the
general
gist
of
it,
and
how
to
get
started.
But
we
can.
We
can
do
a
better
job
at
helping
the
user
visualize.
A
What
it
looks
like
when,
when
they're
successfully
using
it
right,
so
that
that
goes
over
what
you
mentioned
right,
like
us,
some
kinds
of
step
by
step
onboarding-
and
there
are
initiatives
for
this
across
the
lab-
that
we
can
connect
with
other
groups
that
are
doing
it
but
yeah.
We
also
have
a
slow,
low
hanging
fruit
to
improve
this
one
for
sure,
then,
the
last
suggestion
here
that
you
brought
from
ali
was
detecting
deployed
jobs
in
in
the
cia
and
the
yaml
file
and
nudge
users
to
use
an
environment.
A
B
B
Yeah
and
just
to
jump
from
there
yeah,
I
think
it's
a.
I
agree
as
when
you,
when
you
mentioned
that
one
earlier
this
chat,
I
realized
the
connection
to.
I
think
it's
very
similar,
similar
messaging,
something
like
it
seems
like
you're
deploying
deploy,
safer
or
in
a
better
way,
some
some
sort
of
language
or
messaging
to
encourage
using
environments
here
right
now
it
looks
like
it's
still
just
where
does
the
learn
more?
I
guess
it
goes
to
the
documentation.
I
imagine
or
I
I.
B
A
B
A
A
A
B
A
A
B
A
If
it's
listed
here,
it
doesn't
mean
it
exists,
it
only
means
it
will
be
created
according
to
these
instructions.
That's
right,
yeah,
right
all
right,
so
that
that
was
the
last.
Let
me
see
if
I
added
you
know
I
just
kind
of
listed
out
in
text
format
them
all
here.
Do
you
have
any
other
suggestion
that
came
up.
B
This
is
a
pretty
good
list
already
in
just
reading
reading.
Through
this
again
yeah,
I
think
maybe
any
of
the
other
suggestions
are
some
of
the
details
and
you
know
details
that
fall
under
one
of
these
items
like
I,
I
just
did
a
you
know
a
couple
weeks
ago
I
made
it
my
own
test
project
and
I
checked
out
code.
I
made
an
update.
B
So
I
think
that
that
area
is
is,
is
probably
the
best
place
to
focus,
so
I
think
like
educating
like
like,
for
example,
I
didn't
know
I
had
to
create.
I
didn't
know
how
to
I
had
to
create
an
environment.
I
didn't
know
how
to
I
kind
of
have
to
stumble
my
way
through
and
then,
even
after
I
created
an
environment,
I
didn't
really
know
what
to
do
with
it
right.
A
A
No,
not
from
my
side,
I
I
did
think
of
one
more
suggestion
that
that
mapped
to
the
work
that
we
were
doing
with
deployment
approvals
to
to
to
better
show
the
the
approvals
right
in
the
in
the
pipelines
list,
but
I
think
that's
far
too
much
into
you
already
having
environment
set
up.
So
so,
even
though,
like
it's,
it's
a
feature,
improvement
and
official
edition.
So
in
theory
it
will
also
help
drive
adoption,
but
it's
too
too
down
the
line.
So
I
don't
think
it
necessarily
impacts
for
this
epic.
B
B
A
Right
yeah,
I
think
amazing.
It
makes
a
lot
of
sense
to
have
this
distinction
and
and
making
sure
that
also
for
both,
we
have
really
good
tracking
for
the
further.
You
know
the
badges
on
on
the
on
the
project
home
for
for
environments,
we
track
how
many
people
are
seeing
that
for
clickable
elements
we
track
how
many
people
are
clicking
that
and
try,
at
least
in
the
aggregate
map,
the
interactions
with
the
with
the
changes
we
made
to
to
adoption
of
environments
right
right.
B
Later
on,
just
to
drop
this
thought
just
later
on,
and
then
it's
not
the
focus
now
but
later
on.
We'll
we'll
want
to
think
about
like
when
we
measure
it
we'll
want
to
see
how
people
start
to
adopt
it,
but
also
how
how
much
we
want
to
like
retention
right.
How
many
people
continue
to
use
environments,
because
it's
a
useful
concept
and
feature.
B
We
I
believe
we
have
the
raw
material
like
the
data
to
be
able
to
do
that.
I
don't
know
if
we've
looked
at
that,
I
have
personally
not
looked
at
that
since
I've
been
here,
I've
looked
at
it.
I've
looked
at
a
height
sort
of
a
higher
level.
Just
because
I
look
at
you
know,
we
look
at
monthly,
active
users
and
smile,
and
it
continues
to
increase,
so
that's
good,
but
yeah.
I
think
we
want
to
zoom
in
on,
like
as
we're
developing
new
features.
B
B
B
You
know
I
was
able
to
I'm
kind
of
trying
to
remember
what
I
did
back
back
a
few
weeks
ago,
but
in
general
really
easy
to
make
updates
able
to
see
pipelines
and
see
the
status
I
did
run
into
an
error.
I
can't
remember
exactly
why,
but
I
remember
trying
to
use
the
ui
and
then
oh
okay,
that's
what
it
was
something
about.
B
I
didn't
have
a
credit
card
loaded
into
my
into
my
account,
and
so
when
the
pipeline
tried
to
run,
I
think
automatically
just
from
the
sort
of
step-by-step
guide.
It
failed,
so
kind
of
had
to
debug
a
little
bit
and
figure
that
out,
but
anyway
I
was
able
to
run
it,
and
so
because
it
was
a
the
project.
Template
already
had
a
ciaml
file,
but
what
I
was
pointing
out
to
daniel
just
earlier
is
that
even
after
having
set
this
up,
it's
a
little
unclear.
B
You
know
just
from
from
from
viewing
what's
in
the
product
itself
today,
it's
not
exactly
clear
what
to
do
next
in
terms
of
setting
up
a
release
or
setting
up
an
environment,
and
I
think
this
is
the
area
where
you
know
there's
a
lot
of
opportunity
for
us
to
educate,
to
having
products
guidance
to
maybe
be
more
kind
of
pointed
and
maybe
opinionated
about
what
steps
station.
You
know
a
user.
A
team
should
do
next
to
deploy.
B
B
Is
to
be
really
maybe
aggressive
is
the
wrong
word,
but
really
kind
of
just
highlight
that
the
first
thing
you
should
do
is
to
try
to
deploy
this
project
to
production
just
to
test
it
out
right.
So,
like
you
know,
it's
kind
of
an
extreme
thing
we
could
do,
but
you
could
imagine
ways
and
in
multiple
areas
throughout
the
ui
here
that
help
and
guide
the
user
to
be
able
to
do
that
really
quickly.
A
A
So
so
it's
hard
to
say
like
what
should
we
suggest
specifically,
but
we
should
definitely
suggest
something
right
like
set
up
an
environment
in
a
certain
way
and
then
try
to
find
the
the
sweet
spot
where
we're
suggesting
something
that,
at
the
very
least,
for
a
first
set
up
makes
sense
for
most
of
our
users
and
if,
if
like,
we
have
any
way
to
to
slice
that
into
if
you
have
certain
configuration
a
certain
size
of
organization.
I
don't
know
if
we
can
do
that.
A
B
And
that
that's
that's
a
great
way
of
putting
it
daniel,
like
I
think
it
was
a
dead
end.
I
I
hit
you
know,
I
I'm
a.
I
have
a
software
background.
You
know
I
kind
of
understand
that
the
basics
and
sort
of
the
next
steps
after
running
a
pipeline
and
testing,
but
you
know
it
wasn't
obvious
to
me
and
that
I
think
that's
what
we
want
to
do.
It
wasn't
obvious
for
me
what
to
do
next,
even
in
terms
of
using
the
other
release
functionality.
B
So
again,
like
you
said,
suggesting
to
create
a
new
environment.
If
we
don't,
if
we
know
that
they
don't
have
one,
because
that's
probably
a
best
practice
that
we
wanna,
we
wanna
convey
yeah
and
then,
of
course,
we
also
want
them
to
use
our
features
and-
and
things
like
that,
so
that's
sort
of
what
I
was
getting
at
earlier
and
I
think
you
know
this
conversation
will
do
a
lot
to
the
ideas
we
talked
about
today.
We'll
do
a
lot
here
to
help
increase
that.
A
Yeah
makes
sense,
so
I
added
one
more
item
in
the
in
the
dock
that
reads:
once
you
set
up
a
pipeline,
it's
unclear
what
to
do
next,
set
up
a
release
set
up
environments,
how
to
actually
deploy
right
right,
because
that's
that's
the
pain
point
I
also
went
through
when
I
right
after
I
joined.
I
was
tasked
with
with
doing
a
test
setup
to
understand
the
product
deploying
to
aws
and.
B
B
A
B
A
B
A
That
that
points
back
to
the
to
the
work
that
pipeline
authoring
is
doing
with
the
deployment
templates,
the
cic
templates,
where
at
some
point
the
idea
is
to
have
a
broader
pool
of
templates
that
that
the
community
can
can
contribute
to.
So
your
idea
might
seem
farfetched,
but
I
don't
think
it's
that
much
good.
A
A
A
B
Because
I
think
it
would
probably
be
great
to
get
and
jinya
jaime
and
others
have
been
already,
I
think,
contributing
which
is
fantastic.
But
I
think
once
we
create
the
issues,
we
could
get
edge
feedback
on
the
ideas
and
sort
of
idea
of
scope.
Just
because
it's
great
for
you
and
me
to
discuss
some
of
these
ideas.
But
then
definitely
we
want
to.
We
want
to
get
the
team,
but
I
skipped
that
step
for
sure,
no,
no
good
and
then
yeah.
B
A
Yeah,
I
think
one
one
like
horizontal
effort
within
this
epic
is
the
the
tracking
making
sure
we
have
a
consistent
tracking
strategy
right
that
we
can
reapply
for
each
one
of
these
small
changes
we
could.
We
could
reach
out
to
the
to
the
growth
team
to
see
like
what
they
what
they
are
currently
doing
in
terms
of
experimentation.
I
don't
think
these
necessarily
have
to
be
experiments.
B
B
My
understanding
is
that,
especially
if
we
decide
to
use
in-app,
like
specifically
in-app
notifications
for
some
of
these,
I
think
there's
a
it
seems
like
there's
already
like
a
foundation
for
for
doing
experimentation
with
that
and
and
hopefully
measuring.
Hopefully,
that
includes
measuring
as
well.
B
A
A
B
A
All
right,
cool,
so
I'll
I'll
I'll
defer
to
you
to
create
the
issues.
If
that's
okay,
yeah
yeah,
feel
free
to
bring
me
each
one
of
them
and
I'll
help
filling
up
details
and
and
the
ux
proposal
for
each
one
of
them.
That
kind
of
thing
perfect,
all
right,
that's
good
cool!
So
if,
if
you
don't
have
any
other
points,
I
think
we
can
wrap
up
the
recording.