►
From YouTube: Engineering Productivity team - project discussion
A
So
remy
jensen
ash.
Thank
you
so
much
for
taking
some
time
to
chat
me
today.
The
purpose
of
this
conversation
is
to
give
anyone
watching
some
insight
into
the
engineering
and
productivity
team.
Here
here
at
gitlab
and
before
we
start
off
it'd
be
good
to
begin
with
some
intros
ash.
Do
you
mind
going
first.
B
Well,
hello,
I'm
ash
I've
been
at
gitlab
for
four
years
about
just
over
a
week
ago,
so
not
not
too
far
away
from
an
anniversary.
I
am
in
the
gdk
team.
I
suppose
team
of
one
right
now,
but
as
part
of
the
engineering
productivity
team,
but
I
focus
on
the
gdk,
which
is
a
gitlab
development
kit.
I've
been
doing
that
for
almost
two
years
or
just
over
two
years
now,
but
yeah.
It's
it's
recently
in
the
last
few
months,
moved
under
the
engineering
productivity
team.
C
D
D
A
D
You
can
use
as
part
of
the
gitlab
product
and
basically
we
have
a
list
of
processors
that
are
interested
in
in
events
in
specific
events,
and
they
can
all
act
on
the
events
as
they
as
they
want
and-
and
we
so
what's
exciting-
is
that
we
iterate
quickly
on
this
service.
We
can
add
new
processors
very
easily.
D
D
We
also
added
monitoring
to
ensure
monitoring
and
alerts.
I
would
say
to
ensure
that
it's
healthy,
and
so
this
is
an
internal
project,
because
our
team
goal
is
to
really
increase
the
our
own
productivity,
gitlab
teams,
productivity.
As
well
as
the
wider
community
contributors,
creativity,
but
the
ultimate
goal
is
to
actually
integrate
that
into
the
gitlab
product
itself.
That
would
be
really
the
end
goal
and
that's
in
the
past.
That's
what
we've
also
done
in
this
team.
We
build.
A
Perfect
thing
thanks:
so
much
for
sharing
moments
really
does
sound,
exciting
and
then
jen
schier
knows
you're
wearing
everyone
on
the
school
who's
aware
of
our
values.
Here
it
gets
really
important
to
us.
They
guide
our
interactions
and
are
implicitly
and
explicitly
present
in
many
parts
of
my
day.
I'd
love
to
hear
about
the
time
that
you
saw
our
values
in
action
in
your
team.
C
Yeah,
so
the
best
part
I
like
is
that
we
have
less
silos
that
everyone
can
work
on
the
same
thing
and
and
when
something
someone
have
a
schedule
vacations
and
they
need
to
move
on
and
not
move
on.
They
take
on
vacations
and
others
can
just
take
over
what
they
they
did
in
half
and
continue
continuing
working
on
it.
So
the
progress
won't
stop
and
then
the
the
one
from
vacation
back
and
can
take
it
back
and
continue
from
where
it
is
left.
A
C
A
C
So
people
can
write
the
rules
in
simpler
language
and
just
line
by
line,
and
it
will
compute
the
form
and
of
course
that
means
that
it's
less
flexible
because
it's
no
longer
script.
So
I
think
it's
it's
also
important
to
have
a
way
to
extend
it
so
that,
like,
for
example,
we
can
still
write
plugins
to
and
that
that
will
be
script.
C
And
then
in
the
configuration
can
call
that
plugin.
Then
things
will
be
easier
from
there
and
in
three
jobs
there
are
two
parts:
one
is
reactive
part
which
runs
in
real
time
and
the
other
part
is
scheduled
pipelines
which
which,
like
we
can
run
every
monday
or
something
like
that.
And
for
that
schedule
part.
We
already
have
a
plug-in
system
and
it's
also
already
configuration
based.
C
It's
the
reactive
part
which
doesn't
have
all
this
yet,
and
it
would
be
nice
that
it
can
move
to
configuration
based
just
like
the
schedule
part
and
it's
maybe
they
can
somehow
share
the
configuration.
I
don't
know
yet,
because
why
it's
scheduled
and
the
other
one
is
real
time
they
they
might
have
condemnation,
difference
that
it's
hard
to
share
the
configuration,
but
still
it
would
be
nice
to
move
to
configuration
base
and
could
be
extended
by
plugins,
and
then
it
will
be
probably
easier
to
integrate
into
a
product.
C
B
You
so
just
extending
on
my
intro,
so
the
gdk,
the
gitlab
development
kit,
is
the
recommended
tool
to
make
contributions
and
changes
to
the
gitlab
product,
our
engineers
and
other
folk
use
it
as
well
as
lots
of
community
people
yeah.
It's
there's
a
lot
of
room
for
improvement.
I'm
really
looking
forward
to
improving
the
the
speed
at
which
it
takes
or
how
long
it
takes
to
install
an
update
as
it's
a
development
kit.
It
has
lots
of
software
that
needs
to
be
installed
and
updated,
and
that
can
be
time
consuming.