►
From YouTube: Dev Section Group Conversation (Public Livestream)
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
B
A
A
The
team's
been
working
pretty
heavily
just
to
to
provide
context
on
the
JIRA
importer.
It's
the
number
one
priority
for
the
plan
team
and
we've
we've
been
working
pretty
diligently
on
figuring
out
what
that,
what
that
all
consists
of
and
creating
issues
and
a
plan
to
essentially
provide
a
great
importing
experience
from
JIRA.
So
here's
the
document.
We
were
actually
going
to
review
this
with
you
in
the
scaling
meeting
on
Friday,
but
we'll
just
do
it
now.
So.
A
A
It
talks
about
kind
of
the
opportunity
that
we
have
talks
about
the
various
products
that
I've
last
seen,
delivers
and
essentially
scopes
what
we
want
to
import
from,
and
so
let's
go
for.
This
is
really
JIRA
next-gen
importing,
which
is
kind
of
their
next
generation
product,
and
the
the
right
way
to
think
about
the
data
mapping
is
actually
on
page.
A
What
pages
this
page
for
page
four
is
where,
where
we
start
to
map
the
different
data
objects
between
gitlab
and
JIRA
next-gen-
and
we
talked
about
some
of
the
big
things
that
we're
missing
so
you
can
see.
The
rows
in
red
on
this
table
are
things
that
we,
we
really
don't
have
to
map
data,
and
we
talked
about
importing
from
JIRA
we're
talking
about,
essentially
the
ability
to
not
lose
any
sort
of
required
data
that
an
organization
games
is
required.
A
This
is
obviously
going
to
be
different
based
on
the
organization,
but
most
organizations
we
know
of
are
using
some
sort
of
custom
issue
type
and
constant
fields,
which
is
something
that
we
don't
have.
That's
why
you
see
it
spread
and
that's
why
it's
highlighted
in
red.
We
also
have
kind
of
the
t-shirt,
sizing
complexity
and,
if
it's
required,
for
you
know,
a
fully
capable
JIRA
importer
and
so
customized
customizable
issue
types,
customizable
issue,
fields,
sprints
and
tracking
velocity,
better
releases,
inversions
and
tying
that
back
to
issues
subtasks
and
epic
dependencies
and
then
enforced
workflows.
A
A
Slide-
let's
see
here
many
slides
on
slide,
17,
there's
a
number
one
priorities
for
each
stage
and
under
the
plans
section
there's
a
data
compatibility
link-
and
this
has
all
of
the
issues
that
are
required
essentially
for
complete
data
mapping
with
JIRA.
But
one
thing
to
highlight:
ons
you're
importing
is
that
there's
probably
there's
two
ways
to
do
this.
The
first
way
is
to
essentially
like
develop
all
of
these
features
and
functionalities
to
map
the
right
data
and
then
to
build
an
importer
at
the
end.
A
We're
actually
gonna
flip
that
so
we're
gonna
in
starting
in
1210
we're
gonna
build
an
importer
basically
allowing
people
to
import
from
G
or
next-gen
with
the
data
they
have
into
the
fields
that
get
lab
already
provides
and
and
then
what
we'll
do
over
time
is.
After
that's,
delivered
we'll
start
delivering
these.
These
additional
features
to
help
with
additional
data
mapping
and
then
add
that
into
the
importer
and
the
benefit
we
get
by
doing
that
is
we.
A
We
expect
that
there's
some
customers
out
there
that
will
import
from
zero
today,
and
so
we
might
as
well
get
both
customers
onto
the
platform.
There's
probably
some
customers
that
we'll
be
okay
with
throwing
away
data
because
maybe
they're
not
happy
with
how
they're
actually
setting
up
their
workflows
and
their
organization
in
JIRA.
And
so,
if
we,
if
we
make
importer
first
as
the
first-class
objects
inside
of
get
Bob
starting
at
12:10,
then
that
provides
this
ability
to
iterate
because
I
don't
think
importing
is
a
necessary
binary
thing.
For
you
know
every
organization
out
there.
B
B
I
get
that
Google
Docs
sometimes
easier
to
work,
so
what
I
would
advise
is
not
so
much
like
who
are
you
using
a
Google
Doc
but
like?
Why
is
the
Google
Doc
not
linked
from
the
relevant
issues
like
if
I'm
looking
at
the
data
issue?
I
would
really
really
want
to
see
this
doc,
so
it
makes
sense
links
to
it.
B
I
think
on
one
thing:
we're
not
using
enough
of
Google
Docs
after
the
function
to
publish
to
the
web
so
that
everyone
in
the
world
can
see
the
doc,
because
if
we
send,
if
we
just
put
in
the
link,
then
we
have
to
make
a
choice.
Can
people
at
the
company
still
edited
or
not,
and
we
don't
want
to
face
that
choice
so
we'll
be
maybe
good
to
say,
hey
if
you're
using
a
Google,
Doc
and
publish
the
link
I
put
that
link
it's
kind
of
one
of
the
first
things
in
the
dark
hey.
B
A
C
C
This
is
coming
to
gate
and
therefore
to
get
lab,
and
we
have
sort
of
like
indirect
information
that
github
might
announce
something
in
those
regards
in
git
merge,
which
is
happening
three
weeks
two
weeks
and
a
half
so
we're
preparing
something
because
right
now,
what
we
have
is
a
little
bit
of
that
functionality
behind
a
feature
flag
and
what
I'm,
trying
to
my
ask
here
would
be
to
prioritize
a
little
bit
more.
The.
C
Any
any
good
product
is
seen
and
historically
and
currently,
as
unavailable
for
the
game
development
workflows
for
four
reasons,
obvious
that
it
doesn't
support
large
file
transfers
among
others.
This
is
a
new
market
for
us,
so
being
the
first
one
to
be.
There
makes
a
critical
difference.
So
if
github
is
going
to
make
a
first
announcement,
we
better
be
ready.
A
Yeah,
thanks
for
the
the
thoughts
Geordi,
so
I'll
provide
some
thoughts
back
so
on
slide
35.
We
actually
wrote
down
all
of
the
updates
and
next
steps
for
better
large
file
support
and
get
loud,
ending
it
by
extension,
and
so
you
know,
as
you
mentioned
just
to
make
everyone
aware.
Partial
clone
is
now
in
experimental
support
at
get
lab.
That
became
I.
Think
in
12,
for
the
docs
would
have
the
right
the
right
release,
but
I
think
it
was
12
for,
and
so
an
admin
can
turn
on
partial
clone
and
you
can
use
partial
clone.
A
Let's
get
lab
today,
we've
been
working
with,
obviously
the
wider
get
community.
This
is
one
of
those
things
that
we
have
to
collaborate
with
Microsoft
and
github
on.
We've
contributed
a
few
things
as
the
slide
indicates,
and
then
we're
also
working
on
essentially
just
a
better
experience
there,
so
that
certain
object
can
go
to
less
expensive
storage,
as
mentioned
here
for
the
dumb
HTTP
driver
for
promises.
But
your
question
specifically
around
talking
with
customers
is,
is
like
spot-on,
because
that's
what
product
management
should
be
doing?
A
All
the
time
and
I
can
say
like
with
certainty
and
I,
can
give
you
the
list
of
customers
offline.
We
are
talking
with
some
very
large
game.
Developer
companies,
in
fact
out
it.
Sales
kickoff
last
week
had
a
great
conversation
with
a
number
of
reps
about
some
upcoming
meetings
and
renewals
about
gitlab
and
and
how
this
was
a
really
key
value
driver
for
either
an
upgrade
or
even
just
like
a
straight
Chernov
of
get
lab
completely
and
going.
You
know
doubling
down
on
perforce,
so
the
short
answer
is:
we
are
talking
to
customers.
A
We
have
been
talking
to
customers,
please
I
would
kind
of
just
you
know,
implore
the
sales
force
in
any
cams
or
anyone
out
there.
That's
dealing
with
customers
that
do
have
this
use
case.
Please
bring
us
along
myself.
Kai,
Armstrong
and
James.
Ramsey
are
all
pretty
well
versed
and
our
plans
here
and
what
we're
able
to
do
so.
Please
pull
us
along
and
of
course,
we
do
want
to
make
this
better
and
take
the
feedback.
So,
thanks
for
the
question
is
already.
B
D
C
A
B
And
maybe
maybe
it's
also
nice
to
mention
as
far
as
I
know,
a
github
has
been
working
about
partial
clone
in
the
open
were
able
to
follow
along
we're,
collaborating
and
I
think
we
should
it's
very
nice
of
them
to
to
work
in
you
open
like
that
and
not
blindside
any
any
participants,
oh
yeah
out
to
them
behaving
in
the
open-source
way.
Yeah.
A
A
C
So
this
is
not
related
to
large
file,
support
or
gaming
industry
or
whatever,
but
one
of
the
things
that
the
James
and
I
have
talked
is
that
maybe
a
post
about
git
merge
about
our
experience.
Our
presence
there
should
highlight
how
github
and
get
lab
are
collaborating
so
much
in
this
feature
and
another
upstream
yeah
yeah
your
own
spot
with
that,
and
we
will
release
something
on
that
cool.
E
B
A
A
E
A
Page
yep
and
I
figured
someone
would
ask
about
that.
I
just
I
just
found
that,
like
literally
right
before
the
good
conversation
and
if
you
click
on
basically,
what
we
forgot
to
do
is
to
set
the
available
flag
and
so
here's
the
here's,
the
heart
of
fix
this
I,
would
expect
it's
live
on
the
homepage
and
maybe
another
five
minutes.
Okay,
cool
thanks.
So
this
was
nicely.
B
A
B
Whole
maturity
page
me
like
it's:
it's
amazing
the
customer
feedback
in
the
investor
feedback.
So
far
like
people,
people
love
it
and
it
it
gives
it
it
built.
So
much
trust
where
people
say.
Okay
and
now,
I
know
what
parts
are
more
minimal
and
it
almost
seems
like
people
I'm
more
willing
to
embrace
them.
Okay,
I
know
it.
I
know
what
I'm
getting
into
I'm,
not
gonna,
throw
away
my
old
tools
yet
but
I'm
gonna
experiment
to
see
and
it
meets
my
needs.
A
Yeah,
it's
also
really
fun,
as
the
you
know,
a
product
leader
at
the
company
to
see
some
of
these
categories
that
have
been
on
our
roadmap
on
the
in
that
table,
move
up
into
added.
You
know
the
added
section,
and
so
that's
that's
really
fun
to
watch
too
and
then
there's
one
other,
really
neat
improvement.
That
is
being
worked
on,
as
well
as
a
collaboration
between
our
product,
ops
team
and
our
static
site.
A
Editor
team,
where,
when
you
go
to
the
category
maturity,
page
they're
going
to
be
sorted
in
order
of
maturity,
so
that
it
just
looks
a
little
bit
easier
and
you
can
scan
and
see
which
ones
are
at
a
higher
maturity.
Much
easier,
so
that'll
be
coming,
I!
Think
that's
in
twelve
nine
I
believe
that's
a
12-9
yeah.
B
F
G
Jeremy
has
a
question
in
the
doc
thanks
SID,
so
I
have
a
quick
question
for
for
Tim
I.
Think
I
noticed
that
one
of
our
LKR
is
for
for
q1
next
intersection
productivity,
I'm
looking
on
slide,
22
and
I
see
that
there's
a
number
of
objectives
related
to
that,
such
as
increasing
our
merge
request
rate
to
over
11,
getting
a
mean
time
to
merge
of
less
than
12
days,
I'm
really
curious
about.
How
are
you
planning
on
doing
this
and,
more
specifically,
how
can
product
partner
with
engineering
to
make
sure
that
we
accomplish
this
yeah.
D
Thanks
for
the
question,
I
believe
that
we
have
already
started,
especially
in
January,
as
you
can
see
on
the
other
slide,
that
we
have
improved
greatly
already
our
mr8
and
we
we
set
a
lot
of
focus
points,
so
we
set
focus
points
on
the
specific
teams.
So
we
look
at
the
different
metrics
that
we
have
pretty
and
look.
What
is
the
mean
time
to
merge?
D
Are
there
some
issues
that
are
way
too
big
that
basically
it's
fought
out
because
we
can
see
in
our
new
metrics
dashboard,
which
ones
I'm
taking
longer
than
14
days,
for
example,
they
are
highlighted.
So
we
look
into
details
there.
We
look
into
details
if
we
run
into
blockers,
so
we
analyze
really
on
a
team
13
basis
and
set
some
specific
action
at
goals.
This
can
also
go
to
specific
iteration
training.
D
D
Mr,
so
that
we
would
have
been
able
to
actually
ship
80%
instead
of
having
that
tortilla
slip
and
really
having
a
clear
focus
from
from
from
everyone
in
relatives
or
having
more
dashboards
and
more
data,
and
also
in
in
the
different
team
meetings
and
revisiting
the
fruitful
trade
I
believe
that
one
of
the
biggest
topics
is
really
that
was
also
just
merged
in
the
handbook.
Is,
is
iteration
from
the
start
on,
so
that
we
have
a
clear
understanding
between
PM's
and
EMS.
B
You
so
if
I,
don't
think,
there's
any
other
questions,
I
have
one
we've
been
talking
about
workspaces
and
teams,
and
things
like
that
and
I
think
we've
gotten
a
bit
into
thinking
very
far
ahead.
What
are
the
things
that
we
want
to
fix
in
the
short
term
like
things
where,
for
example,
you
can
do
things
on
the
self
host
self-managed
instance
that
you
can
do
on
comm
what
we
really
need
to
kind
of
drive
that
parity.
G
How
can
we
start
by
creating
an
instance
with
an
instance
and
the
way
the
first
iteration
that
we're
gonna
use
for
workspaces
is
not
to
solve
the
problem
of
making
sure
that
we
have
parody
from
self-management
Galib
calm,
but
to
make
sure
that
gillip,
calm
presences
are
isolated
from
the
rest
of
get
lap
comm
one
challenge
that
enterprises
have
right
now
is
they
operate
in
context
to
get
lab
comm
and
it's
a
massive
ultimate
instance.
There's
a
chance
of
information,
possibly
going
out
to
outside
of
your
group
that
you
may
find
undesirable.
G
We
want
to
be
able
to
the
first
iteration
is
going
to
be.
We
currently
plan
on
iterating
on
group
managed
accounts
and
making
sure
that
when
you
have
a
presence
on
get
lab
comm
as
an
enterprise,
you
have
the
option
of
fully
isolating
the
things
that
you
do
to
just
your
organization.
That's
the
first!
That's
going
to
be
the
first
iteration
from
there.
We
plan
on
iterating
on
and
understanding
how
we
can
pull
some
of
these
self
managed
features.
G
Like
experience
but
I
think
the
first
iteration
is
going
to
be
we're
gonna
iterate
on
groups
and
we're
gonna
continue
to
invest
in
this
concept
of
group,
managed
accounts
so
that
you're
able
to
map
users
to
groups
and
then
you're
able
to
have
a
group
level
admin
and
have
your
life
on
gitlab
comm,
isolated
to
just
your
presence
and
just
your
company,
and
then
we
can
iterate
from
there.
Oh.
B
Yeah,
that
sounds
like
a
great
first
step.
I
think
I
always
care
a
lot
about
Kenneth
the
language
we
use
and
if
you
maybe
came
from
reading
the
book
domain,
driven
design
and
I,
hear
you
say
in
this
conversation,
I,
usually
spaces
workspaces
group
managed
to
count.
We
sometimes
hear
teams,
and
things
like
that.
It's
almost
like
all
of
these
things
are
not
needed
to
talk
about
problems.
B
We
have
at
hand
like
what
we
haven't
give
an
instance
within
an
instance
is
kind
of
weird,
because
it
feels
like
a
self
managed
thing,
so
you
could
I'm
not
sure
what
to
call
it.
I'm
thinking
of
words
like
digital
loss
loss
prevention.
What
you're
basically
doing
with
this
isolation?
We
could
call
it
isolation.
G
That's
good
feedback.
Yes,
you
obviously
picked
up.
We
we've.
We
haven't
gotten
the
naming
correct
yet
once
we
do
and
I
in
coalesce
on
something
we'll
make
sure
that
everyone's
in
the
loop
will
use
the
naming
channel
and
CEO
channel
to
make
sure
that's,
it's
circulated,
but
I
think
you're
right,
but
the
experience
we
want
to
offer
to
our
customers
is
isolation.
That
is
the
main
problem
that
costs
that
many
of
our
customers
have
one
get
lab
comm
and
that's
what
we're
gonna
offer
in
this
first
iteration.
Okay,
thanks.