►
From YouTube: Dev Section Group Conversation (Public Livestream)
Description
Dev Section Group Conversation (Public Livestream)
Nov 5, 2019 07:50 AM Pacific Time (US and Canada)
A
Hello,
everyone
and
welcome
to
the
dev
section
group
conversation
today
is
November
fifth
and
I'll
be
your
host.
My
name
is
erick
rincon
I'm,
the
director
of
product
for
the
dead
section
and
I'm
joined
by
Tim
Zalman
who's,
the
director
of
engineering
for
the
deaf
section
and
the
broader
dev
section
team
members,
as
well
from
both
engineering
product
and
product
design.
A
This
will
largely
be
a
repeat
of
the
video
if
you've
watched
that
on
the
title
slide,
there's
a
five
minute
highlight
video
that
has
me
walking
through
each
of
these
things,
but
just
a
few
things
to
highlight
from
a
from
a
hiring
perspective,
we've
added
two
PM's
and
three
designers.
Since
our
last
group
conversation
from
a
strategy
perspective,
we
recorded
a
few
videos
that
walk
through
the
fiscal
year,
21
dev
strategy,
as
well
as
what
we're
doing
and
thinking
and
iterating
about
on
compliance
and
compliance,
is
becoming
something.
A
We've
also
focused
and
added
a
group
that
is
going
to
be
focused
around
the
handbook
and
I'm
sure.
A
number
of
you
have
seen
this
if
you've
been
watching
slack,
this
is
actually
called
the
static
site.
Editor
group
and
the
the
group
lives
in
the
create
stage,
and
the
group
has
two
categories:
static,
site,
editor
and
the
gitlab
handbook,
and
so
the
static
site
editor
focus
is
going
to
be
around
creating
an
editing
experience
around
static
site,
editing
of
which
the
handbook
is
a
static
site.
A
Okay,
still
no
questions.
I
will
keep
going
from
an
accomplishment
perspective.
We've
done
some
really
neat
things
and
most
of
twelve
three
and
twelve
for
highlights
on
the
blog
post
were
actually
came
out
of
the
dev
section,
so
things
like
em
are
dependencies
in
the
same
project.
Api
is
breeze
this
little
audit
events.
We
now
have
code
owner
approvals
for
protective
branches.
One
one
thing:
that's
really
interesting
is
the
ability
to
do
a
parcel
clone
and
so
selecting
which
files
you
actually
want
to
clone.
A
When
you,
when
you
clone
a
repository,
this
is
an
alpha
support,
but
something
that
will
really
help
kind
of
increase,
the
usability
of
repositories
that
have
large
files
and
then
kind
of
something,
that's
really
cool
and
I
know.
A
lot
of
people
have
been
asking
about
it.
You
can
now
move
multiple
cards
on
a
board
at
one
time,
and
so,
if
you
didn't
know
that
now
you
know
and
feel
free
to
check
that
out
and
let
us
know
if
you
are
lucky
night
feature.
B
Sure
so,
I'm,
just
looking
at
the
road
map
around
plan
and
I,
saw
there's
really
for
doing
smoke
around
epics
going
through
2020,
but
I'm
curious
as
to
if
we
have
any
kind
of
roadmap
for
things
like
personal
Kanban,
for
example,
I
work
across
four
or
five
groups
and
I
want
to
Kanban
that
joins
all
those
together.
So
I
can
see
a
personal
board
just
my
items.
The
ability
to
you
know
go
look
at
things
that
I'm,
simply
tracking
or
notifying
and
making
to
do
a
little
more
level
right
like
that.
B
Basically,
this
would
stuff
that
will
go
into
like
the
bottom
here.
It's
for
the
individual
contributor,
but
things
that
make
that
quality
of
life
better
make
it
easier
to
track
your
own
work,
because
right
now,
I
know
a
lot
of
folks
keep
all
their
fat
and
stuff
in
a
side,
Google
Doc,
and
then
it's
just
not
really
efficient
right.
Oh
it's
like
duplicating
data,
so
I'm
just
wondering
if
there's
what
the
roadmap
is.
You
know
where
that's
going.
A
You
can't
do
it
across
groups
right
now.
I
know
that
Gabe's
got
a
bunch
of
improvements
on
making
boards
just
work
better
in
general.
The
other
thing
that
we've
talked
about
is
this
concept
of
a
workspace.
Where
you
know
you
could
have
not
just
seeing
the
items
that
you're
responsible
for
but
like
an
activity
feed
that
is
kind
of
tailored
to
you
and
the
items
that
are
assigned
to
you
and
and
what
you
care
about
so
yeah
in
general.
A
We
want
to
make
the
personal
experience
of
get
a
little
bit
better
and
we'll
be
focusing
on
that.
In
fact,
we
we
Jeremy
and
I
were
just
talking
about
creating
a
group
to
focus
on
on
workspaces
and
teams.
Teams
is
another
construct
that
we
have
right.
We
have
you
know
the
instance
for
most
good
lab
users.
Today,
then
we
have
groups,
and
most
people
are
organizing
their
teams
within
groups,
but
most
large
organizations
have
the
concept
of
a
sprint
team
which
may
span
multiple
groups,
multiple
projects.
It
doesn't
actually
matter
which
group
you
live
in.
A
It
just
matters
who's
on
your
team
kind
of
an
org
chart.
So
this
is
a
construct
we
don't
haven't
get
up
today.
That
will
also
be
focusing
on
and
then
the
concept
you
know
back
to
your
point:
Marat
Robert.
Is
this
constructor,
this
idea
of
a
group
level
workspace
or
a
group
level
dashboard
that
could
be
kind
of
up
leveled
from
an
individual
but
into
a
into
a
team
members
dashboard
that
so
you
can
see
kind
of
the
work.
D
Christopher,
you
got
the
next
question
yeah.
This
is
totally
real-time
in
regards
to
I.
Think
the
EMR
for
the
aesthetic
site,
editor
group
in
the
handbook
team
it
got
merged
and
I,
know
I
added
a
little
bit
of
a
comment
because
we're
having
the
team
distributed
so
I
want
to
make
sure
you
and
I
your
honor,
the
same
page
Eric
in
regards
to
the
effect
of.
Is
it
a?
Are
you
thinking
it's
one
team,
two
teams.
How
do
you
think
about
this?
These
two
categories,
specifically,
which
is
it's
a
little
bit
different.
A
Of
it
as
a
single
team
and
so
yeah,
just
to
give
others
listening
a
little
bit
of
context,
I
think
the
decision
was
to
put
the
product
manager
in
the
create
stage
because
it's
more
of
a
creation
activity,
but
the
engineers
out
of
the
growth
team,
because
we
were
looking
to
solve
this.
This
teams
needs
with
full-stack
engineers
and
a
good
team
has
the
the
model
for
essentially
growth.
Sorry
full
stack,
engineering
there
and
so
yeah.
A
It
is
meant
to
be
a
single
team
where
this
single
team
would
focus
on
enhancing
the
single
site,
editing
experience
as
well
as
essentially
making
the
handbook
more
efficient,
and
you
know
focusing
on
things
like
upgrading
middleman.
If
that's
gonna
give
us,
you
know,
build
time,
increases
and
in
terms
of
speed
and
deploy
it.
A
Good
question:
it's
a
little
bit
of
a
TBD
I
can
give
you
some
initial
thoughts
on
on
what
the
they're
gonna
be.
Focusing
on
one
of
the
thoughts
that
we've
we've
had
out.
There
is
just
focusing
the
team
on
upgrading
our
version
of
middleman,
which
should
help
with
our
our
our
builds
our
build
speeds.
A
Thankfully,
because
you
lose
a
lot
of
the
version
control,
you
lose
a
lot
of
the
approval
flows
that
you
have,
and
you
know,
there's
there's
just
some
benefits
to
leaving
it
as
part
of
a
static
site
where
it's
it's
more
of
a
version
control
system
with
the
approval
flows.
So
that's
probably
the
the
two
things
that
we
would
have.
The
team
focus
on
in
the
short
term,
I
think
there's
even
a
possibility
for
integrating
something
like
like
notify,
CMS
or
some
sort
of
other
open
source
static
site
editor
into
the
application.
E
The
next
one
so
I
was
just
setting
up
some
recent
milestones
in
epics
I
promoted
a
miles,
a
crate
wanted
to
read
the
level
and
I
promote
it
to
the
group.
However,
it's
a
challenger
but
a
larger
thing,
so
I'd,
like
demo
systems
and
infrastructure
to
subgroup
and
the
milestones
don't
seem
to
share
group
hierarchy,
I'm
just
curious.
If
I'm
missing
something
from
moving
between
groups
or
seeing
you
know,
parent-child
hierarchy
of
milestones.
F
I
can
I
don't
the
child
group
Mouse
and
is
also
not
visible
in
the
parents
list
of
milestones.
The
hierarchy,
Goes
Down
words,
if
that
makes
sense,
not
upwards,
so
like
I,
don't
believe
if
you're
in
the
parent,
you
would
see
what's
in
the
child,
but
if
you're
in
the
child,
you
should
see.
What's
in
the
parent,
that's
the
basic
relationship
there.
So
does
that.
E
E
F
F
G
E
C
F
I
can
speak
that
too
we've
played
around
with
it.
There
is
an
open
issue
that
somebody
is
open
to
discuss
it.
The
it
makes
sense
I
think,
especially
as
we
look
to
have
more
configurable
like
workflows,
that
kind
of
map
to
cycling
ilex
work
that
the
manage
group
is
doing
I
think
well.
The
first
thing
that
we're
probably
going
to
do
is
introduce
horizontal
swim
lens
into
issue
boards
so
that
you
can
track
epics,
among
other
things,
within
an
issue
board.
F
Teams
typically
go
through
like
a
planning
phase
or
a
grooming
phase
or
like
their
current
sprint
view
and
I
would
like
to
provide
like
specific,
layouts
and
configurations
for
each
of
those
common
team
tasks,
and
one
of
those
could
very
well
be,
like
a
merge
request
view
that
lets
you
see
like
the
workflow
of
merge
requests.
So
I'm
definitely
open
to
it
and
if
you
want
to
look
up
the
issue
and
put
it
into
the
agenda,
so
you
can
add
to
it.
I
just.
D
Yeah,
it's
just
a
curiosity,
so
I've
heard
a
little
feedback
from
you
know:
senior
leadership
around
the
fact
that
this
is
one
of
the
more
mature
areas,
the
product-
and
you
know
we
should
really
be
focusing
on
great,
if
not
fantastic
user
experience
in
this
area.
So
one
of
the
things
I
was
looking
at
the
charts.
I
was
kind
of
noticing.
We've
gotten
we're
getting
two
complete,
obviously
in
the
middle
of
next
year,
in
a
number
of
areas,
but
like
I'd
be
curious.
D
If
there
was
any
feedback
of
you
know
like
things
we
should
be
thinking
about,
and
the
way
I've
posed
is,
if
you
had
infinite
resources,
you
know
which
category
would
you
want
to
make
loveable
is
kind
of
just
a
high-level
just
to
kind
of
give
us
a
feel
for
that
or
you
know
how
we
would
basically
push
it
push
this
over
the
threshold.
From
that
perspective,
I
think
it's
it.
That's
a
really
good
question.
Do
I
only
get
to
pick
one
category.
I
know
you
can
pick
several,
but
you
can't
pick
all
not
all
I.
D
It
that's
that's
too
much
of
an
out
like
you
like,
like
you
have
to
have
like
something
someone.
So
if
you
know
hey,
this
is
the
most
important
like
what
I'm
really
looking
for
is
less
about
getting
infinite
resources
and
more
about
you
know
which,
which
things
we
see
is
being
critical
to
customers.
A
Yeah
yeah
so
I'll
caveat
my
answer
and
say
that
source
code
management
in
code
review
are
two
or
three
level
Bowl
categories
across
all
of
github
and
something
before
I
answer.
Your
question.
I
will
answer
it
in
a
sec.
Something
that's
just
really
important.
To
keep
top
of
mind
is
that
we
stay
loveable
in
those
categories.
A
We
have
to
stay
level
in
those
categories,
because
if
you
look
at
the
sales
motion
for
how
a
lot
of
adoption
happens,
a
lot
of
a
lot
of
how
a
lot
of
deals
coming
in,
they
really
get
their
ends
in
to
get
lab
and
either
source
code
management,
code,
review
or
CI.
And
those
are
our
three
loveable
products
and
they
start
there
in
the
middle
of
the
DevOps
lifecycle.
And
then
you
start
to
see
people
expand,
kind
of
left
and
right,
and
so
you
know
the
dev
section
strategy
that
I've
linked
in
slide
2.
A
If
you
go
down
to
some
of
the
themes
that
we're
going
to
focus
on
over
the
next
year,
you'll
see
kind
of
like
a
growth
driver
and
most
of
those
growth
drivers
are
actually
going
to
be
something
like
expansion
or
retention.
Where
we
expect
people
to
come
into
the
product
for
create
and
verify.
We
expect
them
to
stay
for
things
like
plan
and
some
of
the
analytics
and
manage,
and
some
of
the
package
repository
features
and
hopefully
even
secure,
defend,
monitoring
all
the
way
down
to
the
to
the
right
side
of
the
DevOps
lifecycle.
A
But
we're
not
necessarily
you
know,
leading
the
tip
of
the
spear
from
a
sales
motion
with
you
say.
Plan
features
at
this
point
in
time
or
configure
features
at
this
point
in
time,
and
so
assuming
that
you
give
me
those
two
for
free
Christopher
that
I
get
to
keep
source
code
management
and
code
review
lovable,
which,
in
my
opinion,
is
probably
the
most
important
thing
to
do
in
in
over
the
next
year,
probably
even
over
the
next
two
or
three,
the
ones.
A
That
kind
of
pop
to
the
top
of
my
mind,
are
board's
roadmaps
and
off.
Those
are
the
three
that
come
to
my
mind
and
just
to
focus
really
quick
on
often
Jeremy
I
would
love
you
to
kind
of
chime
in
with
color
this.
This
is
really
going
to
help
us
get
more
enterprise-grade.
We've
talked
about
enterprise-grade
being
a
big
theme
for
dev
in
fiscal
year
21.
You
can
see
that
as
part
of
our
dev
strategy
document
in
our
handbook
and
something
that
I
really
want
to
see
become
loveable
ASAP
is
authentication
and
authorization.
E
Yeah,
it's
second
that
Eric,
it's
just
the
table.
Stakes
thing
that
enterprises
need
to
be
successful
in
our
application
and
I.
Think
that
we
see
this
especially
on
gitlab
comm,
where
I
just
got
off
a
customer
call
where
they
enumerated
their
biggest
concerns
and
SSO
is
kind
of
at
the
top
of
that
list
with
a
bullet.
So
I
think
that
you
know
right
now
this
the
group
that
is
responsible
for
authentication
authorization,
kind
of
struggles
with
the
you
know,
prioritization
trade-off
decisions
between
security
issues
and
you
know
kind
of
solving
those
problems
for
those
customers.
E
D
Thanks
for
that
question,
Christopher
no
problem
can
I
do
one
more
follow-up,
absolutely,
since
nobody
else
has
ones
so
I
hate.
To
do
this
to
you,
you
opened
yourself
up.
You
said
that
you
want
to
keep
the
two
categories
lovable.
So
how
do
we
really
make
sure
they
stay
lovable
because
they're
anything
we're
thinking
about
or
or
what
is
what
is
their
tactic?
There
yeah.
A
Let
me
head
on
over
so
there's
a
few
things
that
that
I
think
we
need
to
do,
and
these
are
all
in
the
dev
strategy
page
in
our
handbook.
So
one
of
the
things
that
we
need
to
do
is
embrace
real-time,
a
little
bit
more.
You
mentioned
real
time
before,
but
real
time
in
this
context
means
the
application
being
real
time
in
the
fact
that
most
to
two
or
more
people
looking
at
the
same
thing
should
be
able
to
see
how
the
other
person
is
moving
things
around.
A
So
boards
is
a
big
thing
when
you
focus
on
getting
real-time
but
think
about
like
the
IDE
getting
live
coding,
real-time
editing
of
issue
in
M,
our
descriptions,
comments,
real-time
diff
and
syntax,
highlighting
in
the
M
R
for
code
review.
Experience
is
important,
so
there's
that's
a
theme
that
you'll
see
into
the
create
section,
there's
basic
things
like
good
availability
and
performance,
and
so,
if
you
look
at
perform,
it's
our
merge.
A
Requests
page
takes
a
while
to
load
right
now
and
if
you
look
at
what
we've
scheduled
in
twelve
five
and
I
believe
this
is
in
the
second
slide
of
the
deck.
As
well,
you
can
see
a
ton
of
issues
that
were
focused
on.
Essentially,
loading
diffs
in
the
m
are
improving
the
caching
for
some
of
the
syntax,
highlighting
and
making
sure
that
that
thing
is
like
super
super
snappy,
because
it's
really
the
center
of
the
whole
application.
A
So
that's
something
that
we
need
to
do
obviously
gittel
eh-eh,
incredibly
important
for
organizations
that
are
hosting
this
thing
themselves.
Most
people
are
running
and
get
Leon
a
giant
single
node.
That
is
a
single
point
of
failure
in
their
application
and,
while
that's
not
necessarily
related
to
source
code
and
code
review,
it's
actually
a
separate
category
that
we
don't
have
on
our
on
our
home
page.
It's
a
foundational
component
of
essentially
good
availability
and
performance.
Also
enhancing
the
code
review
experience
to
just
be
a
little
bit
more
intelligent.
A
These
are
all
things
that
you
know:
Tim
and
I,
and
the
broader
team
have
kind
of
iterated
on
together
and
thought
about,
and
then
I
think
just
making
like
large
files
work
and
get
like
I
already
mentioned
kind
of
the
partial
clone
feature
that
we're
iterating
on
right.
Now,
no
one
really
likes
using
LFS.
So
that's
something
that
we
would
like
to.
A
We
would
like
to
have
people
not
think
about
which
files
need
to
live
in
LFS
which
files
don't
need
to
live
in
LFS.
We
just
want
everything
to
go
into
the
into
the
repo
and
then
you
you
can
decide
if
you
need
to
actually
clone
that
thing
or
not.
If
you
have
to
clone
that
repository
those
are
there
a
few
things
I,
don't
if
you
want
to
ask
any
follow-on
questions
or
anyone
else
on
the
team
has
thoughts.
A
G
Thanks
Eric
gave
already
give
an
answer,
but
I'll
ask
it
again
for
the
recording,
so
one
of
my
pet
peeves
of
issue
boards
at
the
store
could
be
in
how
the
order
effects
other
boards.
Without
me,
really
realizing.
It
I'll
be
moving
issue
from
issues
from
lists
lists
and
in
effect,
where
I
dropped
them
will
kind
of
affect
the
ordering,
in
other
words
and
I,
was
just
trying
to
pick
your
brain
Gabe's.
How
we're
planning
to
fix
this
and
Gabe
already
gave
an
answer.
Okay,
yeah.
A
A
Okay,
there
are
no
other
questions,
and
so
I
will
leave
you
all
with
a
very
happy
happy
national
donut
day
and
here's
my
fun
fact.
For
the
day.
Did
you
know
that
Donuts
similar
to
get
lab
have
their
origin
in
the
Netherlands,
because
I
actually
didn't
know
that
until
I
book
this
up,
the
earliest
origins
to
the
modern
donut,
is
generally
traced
back
to
oil
cake,
and
if
someone
can
pronounce
that
better
than
I
can
please
chime
in
which
Dutch
settlers
brought
with
them
to
early
New,
York
so
happy
national
donut
day,
everyone
I.