►
Description
Eric Brinkman - Director of Dev Product & John Jeremiah with Product Marketing discuss the Dev section product strategy and vision for the next year & take questions.
Issue:
https://gitlab.com/gitlab-com/sales-team/sales-enablement-videocast-series/issues/19
Meeting Notes:
https://docs.google.com/document/d/1MswVO_kIBXkuvqVQiFTZY7oVNZkR30j00ZPx8X229KM/edit?usp=sharing
Sales Collateral:
https://www.gartner.com/doc/reprints?id=1-6K9591X&ct=190423&st=sb
A
All
right,
thank
you
for
joining
today's
sales
enablement
session.
My
name
is
John.
With
the
sales
and
customer
enablement
team.
We
are
recording
this
meeting.
We're
gonna,
make
it
publicly
available
on
our
company
YouTube
channel
later
today.
Please
make
sure
that
your
microphone
is
muted
and
we'll
be
happy
to
take
questions
for
about
plane
cuts
with
the
end
of
the
presentation.
Today's
topic
is
the
F
section
outlook
for
the
next
year
and
our
expert
speakers
are
Eric
Brinkman
and
John
Jeremiah
from
marketing.
B
B
Over
the
next
year,
things
are
going
to
be
focused
on
it's,
not
gonna,
get
into
a
ton
of
specific,
specific
epics
or
issues
just
kind
of
high
high
level
themes.
The
teams
will
be
focused
on,
but
I'm
gonna
pass
over
to
John
is
going
to
talk
about
some
of
the
analysts
work
that
we've
been
doing
and
then
we'll
open
it
up
for
questions
and
I
put
the
doc
for
questions
in
the
zoom
chat.
So
please
start
populating
questions
there
as
we
go
along
alright
and
I
get
a
thumbs
up.
Can
everyone
see
my
screen?
B
Awesome
Thank,
You
Kyla.
So
this
is
a
handbook
page,
it's
it's
public
and
it
lives
at
slash
direction.
Slash
day,
you
can
find
other
section
pages
here
as
well.
So
if
you're
looking
for
CIC,
B
or
ops,
you
can
also
find
them
here
and
basically
just
as
a
quick
overview.
Dev
is
the
first
three
stages
of
the
DevOps
lifecycle,
as
we've
defined
ed
get
lab.
B
So
that's
what
we
call
managed
plan
and
create
I
presented
this
plan
and
we
did
a
longer
Q&A
as
well,
and
so
you
could
take
a
look
at
the
video,
that's
embedded
at
the
top
of
this
page.
If
you
wanted
to
understand
what
other
questions
engineering,
product
design,
other
PMS
have
asked
as
well,
so
take
a
look
there.
It's
a
it's
about
55
minutes
long.
But
if
you
don't
get
your
question
asked
you
can
watch
that
and
of
course,
ping
me
offline.
B
If
you
need
to
just
a
quick
overview,
so
one
of
the
one
of
the
things
that's
really
interesting
about
the
dev
sections
that
we
spend
so
much
scope
and
we
we
really
compete
in
a
ton
of
different
areas.
So
dev
really
spans
things
like
value
stream
management,
all
of
the
project,
portfolio
management,
Enterprise,
agile,
planning
tools,
source
code
management.
I
des
design
management
even
ITSM
with
some
of
our
service
desk
functionality.
B
So
it's
hard
to
truly
kind
of
estimate,
our
total
addressable
market
for
the
for
the
dev
section,
and
we
know
that
it's
it's
at
least
3
billion
based
off
of
a
few
analyst
reports.
It's
likely
far
higher
than
that,
especially
if
we
capitalize
on
on
really
nailing
like
the
designer
experience.
That's
a
really
really
big
market.
Things
like
the
crm
market
are
also
really
big.
That
plan
could
eventually
morph
into
overtime.
B
So
we
have
a
huge
market
ahead
of
us
to
go
and
actually
capitalize
on
which
is
really
really
exciting
and
then
there's
a
whole
bunch
of
other
great
information
here
that
I'm
not
going
to
spend
time
on,
because
we're
already
three
minutes
into
this.
We've
got
a
SWOT
analysis
here.
If
you
want
to
understand
what
we
think
some
of
our
strengths
weaknesses,
opportunities
and
threats
are
and
then
also
some
vision,
themes
which
are
really
targeted
at
the
three-year
level.
B
So
I'm
gonna
skip
those
for
now
and
really
focus
on
what
we're
going
to
do
kind
of
at
the
one-year
level,
which
is
what
we
call
plan
playing
a
scope
to
one-year
strategy,
a
scope
to
three
years.
So
in
manage
there's
a
few
themes
that
we're
going
to
focus
on
the
first
one
is
enterprise
readiness.
What
does
this
mean?
B
We
have
invested
a
lot
of
work
into
making
our
logging
and
audit
capabilities
a
lot
more
robust
and
we're
going
to
continue
to
do
that
over
the
next
12
months.
We're
also
going
to
actually
help
customers
understand
and
measure
some
of
the
things
that
are
inside,
of
get
lab
from
a
compliance
perspective.
So
who's
last
touched
you
a
specific
project
when
who
has
access
and
when
was
the
last
time
each
of
the
people.
You
know
in
a
project
access
those
things,
those
things
and
then
making
that
available
via
you
eyes,
weld
API.
B
It's
really
important
to
a
lot
of
people
that
are
in
regulated
industries,
lowering
time
to
production
for
our
customers,
so
we've
had
some
analytics
capabilities
inside
of
get
lab
for
quite
a
while.
We've
had
cycle
analytics
as
a
feature.
We
really
want
our
customers
to
understand
where
the
inefficiencies
and
the
software
development
lifecycle
is
going
to
be.
We've
started,
launching
features
like
productivity
analytics
and
get
lab.
12:3
I
will
continue,
making
that
more
robust
and
also
investing
into
things
like
code
analytics,
which
will
help
customers
analyze
their
code
base
as
well.
B
So
it
really
investing
into
analytics
import.
A
great
import
experience
is
something
that
managed
is
going
to
be
focused
on,
because
very
few
people
are
coming
to
get
lab
and
not
using
previous
tools.
Most
people
are
using
something
sort
of
cobbled
together
DevOps
tool
chain
that
consists
of
github
and
Jenkins,
and
maybe
JIRA
and
so
being
able
to
import
data
from
these
other
competing
tools
is
something
that
we're
going
to
be
focused
on.
B
We
want
to
make
a
great
import
experience
and
we'll
start
with
things
like
Jenkins
and
github
first
and
then
expand
out
from
there
and
then
the
last
theme
and
manage
is
just
creating
a
better
way
to
organize
individuals
right
now.
We
we
really
have
one
construct
inside
of
get
lab
for
managing
a
team,
and
it's
really
the
group
feature
that
we
have
and
it's
it's
kind
of
a
foundational
piece
of
the
architecture.
But
many
organizations
use
groups
to
kind
of
segment
permissions.
B
B
B
What
I
mean
by
that
is,
if
you
want
to
just
quickly
edit
an
issue
inside
of
a
board,
you
can't
do
that
today,
you
have
to
click
on
it
and
you
you
have
to
open
up
a
new
tab
and
then
you
get
into
the
situation
where
you've
got
40
tabs
open
and
then
you
kind
of
lost
track
of
what
you're
doing
you
lose
your
context.
I
want
to
make
that
easier.
B
We
want
to
make
the
ability
to
edit
things
easier
inside
of
a
board
when
I
provide
things
like
epic
swimlanes
inside
of
boards,
so
you
cannot
just
have
board
lists,
but
also
horizontal
swimlanes
to
help
structure
work
inside
of
a
board.
The
other
thing
that's
real
important
too,
is
real-time.
I'm
going
to
talk
about
this
and
create
as
well,
but
boards
do
not
get
updated
on
real-time.
B
B
Sorry
project
roadmaps,
easy
top-down
planning
right
now,
it's
very
difficult
to
start
with,
like
a
stret,
a
strategic
objective
or
some
sort
of
top-level
milestone
that
you
want
to
then
drill
down
into
and
say:
hey
I
want
to
start
with.
Maybe
a
strategic
theme
then
create
a
bunch
of
epics,
then
create
a
bunch
of
issues
very
difficult
to
do
inside
of
gitlab.
Today,
it's
also
difficult
to
link
those
things
without
a
bunch
of
copy
and
paste
kung-fu,
that's
going
to
be
a
much
easier
experience.
B
We're
planning
on
that
being
an
easier
experience
in
2020,
investing
in
reporting
analytics
and
then
also
requirements,
management
requirements.
Management
is
the
ability
to
create
a
requirement
and
then
link
that
requirement
down
to
each
piece
of
work
that
happened
in
the
software
development
lifecycle,
so
mapping
a
requirement
all
the
way
down
to
a
specific
line
of
code
or
specific
test
super
important
and
there's
some
really
big
pieces
of
software
and
this
industry
that
do
this,
such
as
IBM
Gorge,
IBM
doors
in
Java
software.
B
That's
a
lot
of
customers
have
to
use,
but
don't
necessarily
really
like
using,
and
so
we
want
to
make
a
better
experience
for
those
individuals
and
then
lastly,
I'll
quickly
touch
on
create
and
we'll
move
on.
Creek
has
a
ton
of
stuff
going
for
it
versus
real-time.
We
need
to.
We
need
a
fully
embrace
real-time,
like
real-time
merger,
best
descriptions.
Real-Time
updates,
on
a
on
a
on
a
merge
request,
if
you're,
if
you're
viewing
the
same
diff
real-time
inside
of
the
web
IDE,
if
you
are
editing
something
at
the
same
time,
another
person
really
exciting.
B
There's
a
ton
of
opportunity
in
real-time
get
availability
and
performance.
I
know
this
is
something
that
is
a
single
point
of
failure
for
a
lot
of
customers
today
is
giddily
and
we
really
want
Gilly
to
be
to
be
highly
available
or
have
that
architecture
available
to
customers
that
want
to
invest
into
that
architecture.
So
we're
investing
a
lot.
Their
code
review
is
something
we're
already
a
leader
in.
We
have
to
continue
to
be
a
leader.
B
We
want
code
review
to
be
more
of
like
an
IDE
like
experience,
that's
more
interactive,
syntax,
highlighting
jump
to
definition,
type
signatures,
adding
support
for
first-class
reviewers.
These
are
things
that
we
know
we
need
to
do
and
we
want
to
make
that
experience
better
and
continue
investing
they're,
making
large
files
just
working
it.
B
Continuing
investment
in
our
wiki
product
is
something
that
I
want
to
call
out.
We
haven't
done
a
ton
with
the
wiki
in
2019,
but
it's
something
I
want
to
change
in
2020
I'm,
not
looking
for
a
massive
investment
here,
but
we
need
to
do
things
like
pull
the
wickiup
to
the
group
level
just
make
it
work
a
little
bit
better,
enhance
them
work
down
formatting
these
types
of
things,
so
we're
gonna
make
the
wiki
just
easier
to
use
in
general,
we're
also
gonna
focus
on
the
gaps
in
the
design
management
workflow.
So
these
are.
These.
B
B
Well,
because
we
we
could
compare
those
things
we
we
want
to
be
the
single
datastore
for
designs,
and
so
it's
something
I'm
really
excited
about
focusing
on,
but
then
also
just
the
ability
to
version
design
assets
a
little
bit
easier,
but
also
do
like
quick
architecture
sketches
inside
of
issues,
something
that
we're
also
investing
in.
We
want
to
make
our
editor
experience
better.
I
know
I'm
going
quick,
so
bear
with
me
I,
just
don't
I
have
a
lot
to
get
through,
but
not
a
lot
of
time.
B
B
Live
coding,
features
for
pair
programming
to
be
a
part
of
our
IDE
experience,
and
so
we
want
to
invest
there
as
well,
and
then,
if
you
came
to
the
last
dev
section
group
conversation
which
was
on
November
5th,
you
also
heard
us
build
a
new
handbook
group
which
is
called
the
static
site,
editor
group.
So
this
is
going
to
be
a
team.
That's
focused
on
a
great
static
site.
Editing
experience
as
well
as
improvements
into
our
handbook
ran
through
that
as
fast
as
I
could
and
so.
C
The
fact
that
these
pages
exist
that
Eric
and
team
curating
these
involving
these
means
we're
listing
and
we're
open
and
transparent
about
what
we
do
and
the
way
we
work
and
I
think
this
is
one
of
the
things
that
all
you
have
to
realize.
Is
you
talk
to
customers?
It's
a
differentiator!
It's
what
makes
us
different
and
I
apologize
for
background
noise.
C
I
am
in
a
hotel
lobby
cell
and
do
my
very
best
with
with
this
I
wanted
to
quickly
share
a
slide
view
of
the
enterprise,
agile
planning
report,
which
will
also
be
included
in
the
call
to
action,
and
it's
relative
and
it's
related
to
what
we're
talking
about.
You
know
in
the
most
recent
report
that
came
out.
This
was
just
a
few
months
ago.
They
reported
out
as
to
where
treat
different
organizations
are
at
with
enterprise,
agile
planning
tools,
so
this
is
one
that
we've
been
competing
in
and
we're
growing
in
and
I.
C
If,
when
I
look
at
this
I
see
us
as
the
second
farthest
to
the
right
on
vision
on
the
completeness
of
vision
and
as
we
continue
to
grow
in
Excel,
we
are
going
to
move
further
up.
If
I
look
back
several
years
ago,
agile
craft
was
actually
down
about
where
we
are
several
years
ago,
and
so
the
trajectory
that
we
have
the
potential
we
had
was
to
move
up
into
the
right.
C
The
other
thing
to
realize
as
well
is
that
in
enterprise
agile
planning
we
are,
we
are
one
of
three
organizations
and
companies
that
were
customer
Choice,
Award
winners.
So
that's
another.
You
know
feather
in
our
cap
that
we,
when
we
competed
and
we
took
in
customer
reviews
or
Enterprise
identifying
our
reviews
were
sufficiently
deep
and
broad
with
you
know
a
4.6
average
rating
I
think
I
can
get
that
specific
for
you,
but
again
it's.
These
are
a
couple
of
proof
points
for
how
strong
we
are
in
this
space
and
how
we're
getting
stronger.
D
B
B
D
B
Obviously,
it's
partial
clone
we've
released,
partial
clone
in
alpha
in
the
last
release,
which
lets
you
kind
of
say,
hey,
I,
don't
want
to
grab
that
file
when
I
clone,
because
we
don't
want
people
have
to
think
about
where
I'm
storing
files,
so
we
don't
want
to
have
to
people,
have
to
go,
think
and
put
that
in
elephants
or
not
put
that
LFS
based
off
of
some
sort
of
criteria.
We
just
want
everything
to
go
into
get
and
then
to
give
you
the
controls
to
get
stuff
out
of
it.
B
D
I
know
for
some
of
our
customers,
which
I
can't
mention
here,
but
there's
there's
a
lot
of
growth
opportunity
at
existing
customers
who
use
their
developers
use
gitlab,
but
some
of
their
back-end
storage
folks
or
their
their
artists
use
perforce
is
a
good
example
for
for
their
large
file.
So
I
think
there's
a
lot
of
growth
potential
here
as
well.
Yeah.
E
I'm,
try
to
type
map
happy
enough.
I
just
joined
the
QPR
yesterday
and
the
couple
last
couple
days
and
heard
a
fair
bit
of
feedback
on
running
into
enterprise
accounts
that
they're
using
IBM,
rational
and
right
now
it
is
a
fairly
difficult
to
directly
compete
against
that.
So
I'm
very
excited
to
hear
about
the
features
around
the
requirements,
management
and
our
approach
to
taking
more
traditional
enterprise
requirements,
management
than
down
to
the
agile
and
down
to
the
specific
tasks.
I
just
want
to
get
a
little
bit
more.
B
That's
a
that's
a
great
question
and
I
like
how
you
diplomatically
put
it
that
it's
difficult
to
compete.
It's
it's
actually
impossible
for
us
to
compete
right
now
with
the
existing
functionality
and
and
we
don't
shy
away
from
that.
We
we
know
this
is
a
big
use
case
that
we're
not
serving
at
this
point
in
time
with
gitlab
and
so
yeah.
It's
difficult
and
I
I
just
want
you
to
know
that
we
are
investing
in
this
area.
We've
we've
got
a
product
manager,
that's
focused
on
requirements,
management.
B
B
We
are
planning
on
releasing
the
MDC
of
requirements,
management,
which
is
very
simply
the
ability
to
define
a
first-class
requirements,
and
this
is
important
because
you
could
define
requirements
and
issues,
but
issues
do
not
have
the
kind
of
rigid
structure
necessary
to
actually
define
requirements
because
for
most
regulated
industries,
these
requirements
should
should
never
change
and
issues
are
far
too
malleable
and
you
can
update
them.
You
can
change
them,
they're,
not
even
version
control
at
this
point
I'm.
So
that's
our
NBC
beyond
that
we'll
be
iterating
every
single
month.
B
Every
single
release
we'll
be
making
a
requirements
management
all
bit
better
by
adding
new
features.
I,
don't
know
at
what
point
in
the
future
we'll
get
to
when
we
can
say:
hey
we're
we're
a
drop-in
replacement
for
something
like
an
IBM
doors.
It's
probably
going
to
take
a
very
long
time,
but
we're
gonna
start
next
release
and
then
each
release
after
that
will
get
better
yeah.
E
We
don't
have
to
directly
compete
with
IBM.
We
have
an
advantage
where
we
can
take
more
traditional
requirements,
management
on
Mac
very
easily
into
agile
approach
and
the
IBM.
Perhaps
there
are
some
areas
that
it
don't
do
a
very
good
job
on
that,
so
you
know
we
can
ambe's
position
this
new
feature
to
business
stakeholders
give
them
to
use
a
gala,
because
then
you
know
we
can
start
getting
the
whole
value
chain
in
you
know
from
the
enterprise
perspective
into
our
pod
offerings.
So
that's
why
I'm
quite
key
on
tracking
this
feature.
Developments
yeah.
B
I
think
I
think
you
just
hit
the
nail
on
the
head.
We
would
expect
people
to
come
by
get
lab
for
things
and
create
and
things
in
verify
so
get
get
lab
source
code
management
and
get
lab
CI
and,
as
I
talked
about
in
our
dev
conversation
a
week
and
a
half
ago,
we
want
people
to
move
left
and
right
from
there
and
so
I
think.
What's
gonna
happen
is
we're
gonna
start
launching
these
requirements
to
engines
features
and
as
people
use,
get
lab
for
kind
of
the
bread-and-butter
things
and
they
realize
oh
wow.
B
They
actually
have
a
requirements
management,
that's
really
cool
I'm
gonna
start
using
that,
and
then
that
renewal
comes
up
for
something
like
IBM
doors
or
another
product
they're
using
for
a
primer
stand
and
they
think
maybe
I
don't
have
to
use
that
anymore.
I'll,
just
stick
with
gitlab
and
kind
of
moving
left
and
right
out
of
the
middle
of
the
DevOps
lifecycle
is
something
that
I
think
is
really
powerful
for
us
and
how
I
see
us
attacking
requirements.
B
C
I
want
to
just
before
we
go
to
the
next.
One
I
want
to
ask
two
questions.
If
you
could
type
your
answer
into
my
two
questions,
ad-hoc
survey,
what's
the
biggest
thing
you're
most
excited
to
see
in
what
Eric
just
shared
and
what's
missing,
so
just
go
ahead
and
type
in
your
notes
up
the
top
and
the
notes
document
love
to
get
your
feedback
asynchronously
while
we're
doing
this,
but
we
can
go
to
the
next
question
or
we
go
because
I
want
make
sure
we
get
that
Cynthia
you're
next.
F
We
have
any
kind
of
timeline
for
on
the
ability
to
purchase
stories
on
Caitlin,
calm.
I
know
we
have
a
lot
of
customers
asking
for
this,
and
it
does
also
actually
impact
support
as
well,
since
a
lot
of
users
won't
no
longer
be
able
to
push
to
the
repository
when
they
go
over
the
limit,
and
you
know
they're
always
asking
for
this
and
I
know.
B
I
think
that
concern
makes
a
lot
of
sense.
Unfortunately,
I
don't
have
a
good
answer
for
this
one.
This
is
an
issue,
that's
being
driven
out
of
the
growth
section,
not
the
dev
section
at
this
point
in
time,
but
I'm
happy
to
circle.
Back
with
that
team
and
and
then
drop
an
answer
back
in
the
dock
later.
F
Sure
I
usually
have
the
link
for
the
growth
epic.
It
focuses,
though,
on
the
implementation
of
the
purchase
itself
and
my
understanding
is
on
the
like
it.
The
features
to
kind
of
actually
be
able
to
kind
of
trigger
that
additional
storage
is
more
on
the
dev
side,
but
all
I
had
the
link,
and
maybe
you
just
follow
up
yeah.
B
Please,
please
add:
the
link
all
of
the
kind
of
purchase
flow
stuff
also
lives
in
growth
at
one
point
that
did
live
in
managed
that
would
have
been
in
dev.
That's
not
spun
out
to
growth,
but
if
there's
something
I'm
missing,
I'm
happy
to
follow
up
on
it
Cynthia
so
yeah
I,
just
drop
a
link
and
I'll.
Take
a
look.
Okay,.
G
I
just
noticed
that
in
general,
all
of
us
who
are
in
code
communities
and
get
based
communities
tend
to
end
up
lacking
a
rich
expression
in
our
documents
because
of
basically
having
to
hand
code
markdown
not
having
instant
instant
capability
to
see
that
resolved
in
type
aura
is
an
application
that
does
do
both
of
these.
But
it's
concerning
in
that
we
end
up
with
a
lot
of
things
like,
for
instance,
great
big
lists.
It
would
be
better
as
a
table
and
other
things
that
are
make
communication
a
lot
harder.
G
Just
wondering
if
there's
any
study
into
this
area
of
UX
and
especially
checklists,
are
something
where
we
have
interactivity
on
the
website
of
just
in
mrs
and
issues
so
creating
a
checklist
that
makes
sense
that
people
can
follow
in
real
detail
like
even
our
own
onboarding
checklists
it'd,
be
nice
to
have
expandable
regions,
but
even
just
being
able
to
have
a
table
and
that
kind
of
stuff
would
make
it
a
lot
more
pleasant.
Just
wondering
if
there's
been
any
thoughts
around
this
area.
B
Yeah
I'd
say
generally:
we
want
to
make
kind
of
a
markdown
editing
experience
better
for
not
just
issues
and
mr
descriptions,
but
also
for
things
like
editing
the
handbook,
which
is
why
we
made
that
handbook
team.
So
the
answer
is
yes,
just
as
a
quick
aside,
you
can
already
do
a
collapsible
section
via
markdown,
I'm,
sure,
there's.
It's.
G
B
Yes,
I
think
that
actually
still
still
is
an
issue
yeah.
We
won't.
We
want
to
make
this
better
I,
don't
have
specific
issues
that
I
can
link
you
to
like
on
the
spot.
I
think
a
lot
of
them
do
already
exist,
but
yeah
if
I
have
to
make
a
big
table
like
I'll.
Just
use
like
a
free
markdown
table,
editor
someplace
else
end
and
cutting
a
copy
and
paste
that
into
my
issue
description.
That's
that's
not
a
great
experience.
We
should
make
that
better.
So
short
answer
is:
yes,
we've
thought
about
this.
B
We
we
do
want
to
make
this
better.
I
would
imagine
that
plan
focuses
on
things
like
this
next
year,
just
in
general,
I
don't
want
people
to
have
to
know
a
whole
bunch
of
markdown
tricks
just
to
use
the
product.
So
that
includes
not
just
issue
and
merge
request
descriptions,
but
also
the
handbook
we
kind
of
impose
this.
You
really
need
a
new
markdown
to
edit
a
handbook
as
well.
What.
G
B
Is
pretty
much
the
purview
of
the
static
site,
editor
team
that
we
just
created,
and
so
we
we
want
the
ability
to
do
like
a
side
by
side,
editing
like
you're,
editing,
something
and
then
you
seek
I
know
how
its
rendered,
and
so
yes
like
that
is
absolutely
coming.
We
just
have
that.
We
just
created
that
group
about
two
weeks
ago,
and
we
have
our
first
engineer
on
it
today.
Okay,.
G
I
G
H
H
B
I
Hey
so
yeah
I'm
glad
you
touched
on
the
web
IDE
and
I'm
glad
progress
is
being
made
on
that
front.
For
me,
I
see
the
web.
Ide
is
something
convenient
if
you're
on
an
iPad,
and
you
need
to
change
a
single
line
and
push
to
production,
something
like
that,
but
increasingly
I'm,
seeing
Burbage
in
some
of
these
RFI's
and
RFPs
from
the
federal
government,
where
they
they're
very
much.
Looking
for
an
IDE
to
be
browser-based,
you
know
as
part
of
a
complete
solution
that
Ghaleb
could
deliver
on
and
for
now.
I
What
we're
prototyping
is
a
system
external
to
get
lab,
where
it's
a
browser-based
virtual
machine
with
vs
code
in
it
and
that
essentially
meets
all
the
acceptance
criteria
for
these
contracts,
but
it
would
be
fantastic
to
see
a
better
idea
built
in
to
get
lab.
I
would
also
be
interesting
and
I
don't
even
know
how
possible
this
is,
but
in
the
same
way
that
Mozilla
aims
to
support
Chrome
extensions,
where
maybe
they
already
do
I
don't
know.
Yet
what
their
timeline
is
on.