►
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
And
create
inside
of
Gitlin,
and
we
would
welcome
any
questions
that
you
all
have
about
some
of
the
debt
content
or
anything
that
might
not
be
in
the
deck
but
would
be
relevant
to
the
DOS
section.
Be
happy
to
answer.
We
have
a
number
of
team
members
on
a
lot
of
product
managers
and
all
the
engineering
managers
as
well.
A
All
right,
while
waiting
for
a
question
roll
in
I'm
just
going
to
talk
through
slide,
two
to
just
walk
through
a
few
highlights
and
to
get
us
going
a
little
bit.
So
just
some
quick
updates
on
hiring
as
I
announced
yesterday
on
the
company
call.
I
am
really
excited
to
announce
that
James
Ramsey
who's
led
our
source
code.
A
I'll
start
early
in
next
year,
very
excited
for
that
individual
to
start,
and
then
we
also
have
a
few
new
team
members
in
UX,
as
well
as
development,
so
welcome
to
get
lab,
Nick,
Brandt
and
then
there's
a
ton
of
dev
team
members
on
slide.
17
alex
pablo
david
Josiane,
john
chad,
simon
roman
and
robert
and
so
welcome
to
the
team.
A
From
an
accomplished
accomplishments,
perspective,
I
highlighted
a
few
things
here,
but
just
wanted
to
bring
those
to
the
top
of
everyone's
attention.
We've
launched
an
audit
events
API
for
groups
which
is
really
helpful
for
customers
who
want
to
get
audited
events
out
of
an
API
for
into
their
own
reporting
system
or
tracking
system
for
compliancy.
We've
also
launched
an
epic
tree
view
in
the
in
any
sort
of
issue
or
epoch
that
you
have.
You
can
now
see
the
hierarchy
of
how
epics
and
issues
line
up,
which
is
which
is
great.
A
We've
also
released,
contextual
now
for
groups
of
group
and
projects.
It
can
be
hard
to
tell
if
you're
in
a
group
or
a
project
or
a
sub
project,
and
so
now
there's
a
quick
fix
to
the
top
left
of
your
navbar.
That
says
whether
or
not
you're
in
one
of
those
three
we've
released
code
intelligence
via
source
graph,
which
is
the
ability
to
jump
to
definition
for
functions.
It's
available
for
a
private
project,
I'm
sorry
for
public
projects
on
get
lab.
A
Comm
we've
made
a
change
to
the
default
behavior
for
deleting
source
branches,
which
is
enabled
by
default.
Just
in
order
to
better
clean
up
after
ourselves,
this
is
a
configurable
setting,
but
it's
enabled
by
default
and
then
one
thing
that
we've
as
we
talked
about
in
our
last
group
conversation
we've
built
a
static
site,
editor
team,
that's
focused
on
this
static
site,
editing
experience
inside
of
get
lab,
but
also
the
lab
handbook
and
as
a
first
iteration,
for
what
that
team's
going
to
do.
A
We've
built
out
handbook
build
time
dashboards
which
outlines
how
fast
it
takes
our
handbook
to
build
a
test
and
deploy,
and
it's
around
12
to
13
minutes
on
average,
so
check
out
that
periscope
dashboard.
If
you
want
to
see
and
track
the
the
handbook
build
times
as
we
work
to
improve
those
and
drive
those
down.
B
What
has
changed
in
the
maturity
levels
and
the
current
plan?
Since
the
last
time
you
presented
I
see
what
the
current
slides
look
like
on
paint
kind
of
ten
but
I,
don't
know
what
they
looked
like
a
month
ago
or
whatever
it
was.
Has
anything
up,
leveled
become
you
know,
more
mature
or
been
pushed
out.
A
C
A
One
of
the
things
that
the
team
was
working
on
was
getting
prefect,
which
is
the
cluster.
Basically,
the
the
the
cluster
B.
We
set
up
to
essentially
wrap
around
multiple
giddily
nodes
set
up
on
Caleb
comm.
Just
so
we
could
make
sure
that
you
know
it
works,
there's
not
anything
wrong
with
that
sort,
sort
of
a
set
up
and
then
to
do
a
some
sort
of
test.
Failover
event
you
can
follow
along
in
the
epic
I've
put
it
in
slide.
A
A
The
second
half
of
it
we've
also
talked
about
using
our
package
repository
as
a
it's,
a
git
LFS
target
to
better
make
that
experience
a
little
bit
more
seamless
inside
of
the
application,
but
I
don't
have
a
better
answer
for
you
right
now
and
unfortunately
James
because
he's
in
Australia
right
now.
It's
not
my
call
so
I
hope
to
get
back
to
you
on
that
one
with
a
little
bit
better
answer:
cool.
A
D
Vocalize
though
yeah
I
saw
the
accomplishment
for
better
context,
navigation
between
subgroups
groups
and
projects
just
curious
to
learn
kind
of
more
about
that,
as
certainly
as
a
I
frequently
when
the
wrong
like
I'm
in
get
lab,
I
want
to
be
in
get
my
best
or
or
something
like
that,
and
and
so
I'm
curious
yeah.
What
that
is,
I
think.
E
Sure
yeah,
so
you
know
it's
actually
a
really
simple
change
and
I
linked
to
the
issue.
You
can
that
we
did
the
work
and
you
can
actually
see
some
screenshots,
but
you
know
talking
to
a
lot
of
customers.
They
just
said
you
know
it's.
The
experience
is
frustrating
or
confusing
just
to
understand
what
part
of
my
hierarchy
I'm
in,
and
so
the
change
is
literally
at
the
top
of
the
left-hand
nav.
Just
saying,
like
group
overview
subgroup,
overview
project
overview
and
we
actually
had
a
couple.
E
Is
users
creating
issues
in
the
wrong
and
in
a
place
that,
in
their
account,
where
they
don't
mean
to
and
then
having
to
move
them
and
dealing
with
the
frustration
of
closing
it
and
having
a
new
issue,
so
we're
monitoring
feedback
now
so
right
now
you
know
we
don't
have
any
other
major
changes
around
that
one,
but
we're
hoping
that
additional
user
feedback
will
help
us
understand
improvements
to
the
left
hand,
map
in
general,
cool
Thanks.
E
D
A
Okay,
well,
if
there's
no
other
questions,
then
we
can
go
ahead
and
end
the
call-
and
please
let
me
know
if
there
are
questions
I
can
answer
them.
Asynchronously
and
John
I'm,
going
to
do
some
work
offline
and
get
back
to
you
in
particular,
on
your
questions.
Okay,
yes,
thank
you
all
right.
Thank
you.