►
From YouTube: How Distribution team got its name
Description
The CEO AMA call from 2018-02-23 contains the discussion as an extension from Company call on the same day. John Northrup actually made the suggestion of Distribution.
The conversation is an example of feedback process at GitLab, and how open discussion can breed better solutions for all parties.
A
A
And
with
this
we
want
to
have
a
stable
categorization
of
all
our
all
the
different
product
things
we
do
so
that
the
product
manager
knows
how
to
find
the
you
weeks.
Person
that
specialized
in
this
know
how
to
find
the
front-end
team
member
know
how
to
find
the
back-end
team
member
the
product
marketing
knows
what
the
different
elements
are.
I
find
that
that
is
one
of
the
as
we
scale
like
it's
really
important.
A
We
have
these
stable
interfaces,
and
part
of
that
is
that
we
also
want
to
make
sure
that
the
teams,
as
we
have
think
about
the
engineering
teams,
will
start
changing
them
to
reflect
these
stages
so
that
we
have
inside
and
outside
the
company.
Everyone
understands
what
whatever
the
responsibility
is
and
who
to
go
for
for
what,
and
one
of
the
first
changes.
Well,
that
is
proposed
is
to
name
the
build
team
to
rename
the
truly
install
team,
because
built
is
something
that
is
commonly
preserved
for
and
we
have.
We
also
have
a
build
product.
A
You
are
what
you
ship
in
a
reef.
Like
other
people,
see
the
end
product.
They
don't
see
all
the
effort
that
Gates
gets
into
it
and
you
can
call
it
a
bakery
or
you
can
call
it
a
or
sense
job.
This
analogy
is
not
going
anywhere,
but
the
end
product
is
what
other
people
care
about
and
and
it's
it's,
how
they
perceive
the
world
and
the
hardest
thing
for
people
is
to
find
people
and
and
I
think
also
it's
as
a
kind
of
a
side.
A
A
This
is
dangerous
because
we
can
easily
check
this
and
I
haven't,
checked
it,
but
it's
it's
important
to
care
about
the
end
product
and-
and
that's
that's
what
your
that's,
what
the
rest
of
the
world
see
you
are
value
is
results.
Our
value
is
not
all
the
work
you
do
are
variously.
The
output
of
it
per
Jason
feel
free
to
speak
up
and
also
other
members
of
that
the
bill
team,
it's
kind
of,
especially
in
Maine
that
you're
all
here
to
interrogate
me
about
this,
which
I
would
love
to.
B
Trying
to
actually
figure
out
exactly
how
to
phrase
what
you're,
saying
or
and
what
I'm
trying
to
express
we're,
not
wrong
in
any
way.
But
the
consensus
is
that
we
don't
see
that
we
do
just
install
right.
So
if
the
team
was
renamed
to
install
then
would
be
install
engineers,
we
do
everything
from
creating
on
the
packaging
to
verify
and
all
the
components,
especially
when
it
comes
to
the
various
deployment
methodologies
that
we
produce,
because
we
do
on
the
bus,
and
we
do
cloud
native
helm
charts
that
we
do
a
few
other
miscellaneous
ones.
B
A
So
I
think
I
think
there's
two
things
here.
Obviously
to
make
a
great
installation
product
you
have
to
do
all
of
these
other
steps.
So
I
think
that's
obvious.
I
think
the
one
thing
I
could
see
as
a
risk
is
that
you're
relegated
to
the
people,
think
you're
not
building
the
installation
product
but
that
you're
actually
doing
the
installation
yourself
like
you,
come
in,
give
me
the
server.
A
Let
me
pop
in
the
CD
and
I'll
I'll
pop
it
in
the
box,
for
you
so
one
hand
you
could,
if,
if
that's
a
worry
had,
maybe
it's
better
to
call
it
install
product
but
I
kind
of
prefer
short
names,
because
then
it's
like
it's
this
product
or
is
this
it's?
It
starts
to
be
confusing,
but
but
do
ya
maybe
help
me
understand
better.
If
people
think
to
make
a
good
installation
product
you
don't
have
to
like
verify
all
the
stuff
you
you
install
right.
B
Just
let's
say
we're:
gonna
go
just
with
with
the
layouts
that
are
actually
designed
in
two
stages,
as
defined
as
the
the
DevOps
lifecycle.
If,
if
we
were,
if
we
as
a
team,
were
to
really
pick
one,
we
would
probably
lean
towards
package
versus
installation
because
we're
producing
the
package
that
people
will
then
actually
use
to
install
and
configure
their
systems.
A
C
A
A
You
know
what
we
do
then
right
if
it
doesn't
work
change
it
back.
A
little
asked
won't
install
get
confused
with
it
support
team,
which
practically
helps
is
user
installs
configurations.
Yes,
there's
a
risk
of
that,
like
is
it
hand
between
installed
products
and
installed
services.
Basically,
they
Anna
asked
about
the
package
team,
but
I
think
that
was
before
a
man
and
explained
that
Alejandro
says
the
bakery
is
not
the
best
example
you're
correct
about
that.
A
A
Kind
of
would
have
been
nice
to
have
like
one
word,
that
kind
of
reflects
installation
and
then
updating,
because
I
think
I
think
the
keeping
installations
up
today
it
will
be
a
big
thing
and
where
I
think
we're
not
spending
enough
time,
for
example,
in
detecting
like
hey,
if
if
an
installation
is
updated
and
it
fails
to
restart
or
it
has
problems.
After
like
we
shut
down
the
packaging
service,
we
probably
have
a
bug
we're,
starting
with
that
now,
like
measuring
the
effect
of
our
things,
but
I
think
that
should
be
kind
of
a
a.
A
Core
the
team
should
feel
that
that's
a
core
part
of
their
mission
and
install
kind
of
distracts
from
that,
because
it
tells
about
this
one
time
thing
so
open
to
suggestions
but
I
love,
installation,
automation,
jason,
said
distribution,
I
like
it
it's
one
word
and
like
with
only
was
the
big
thing
has
been
that
we
used
the
operating
system
packages
or
not
the
operating
system
pipe,
but
that
we
have
a
packaging
system
that
works
together
with
the
distribution.
It's
it
has
like
a
logistics
analogy,
and
it's
one
word
really
important.
A
A
Like
I
see
the
problems
with
install
distribution
kind
of
stuff
makes
it
sound
cooler,
so
maybe
it's
easier
with
hiring
as
well.
It
has
to
update
in
it
the
update
element
in
it.
I
think
it
meets
all
the
criteria.
I
articulated
so
I
think
it's.
We
don't
have
any
further
insights
that
that's
that's
a
winner,
so.
A
C
A
Most
points
I
opened
opened
one
when
I
click
the
button,
if
there's
no
objections
in
the
nest.
Next,
three
questions
that
can
also
be
about
other
things,
because
this
is
an
ask
me
anything,
preferably
controversial
subjects
like
hiring
a
firing
and
composition,
and
we
don't
know
what
we're
doing
in
Department
X.
So.
D
The
question
I
have
is
whether
it's
possible
to
have
the
team
name
be
separate
from
lengthen
titles
I,
just
a
quick
search
on
like
salary,
calm
and
stuff
for
like
distribution,
engineer
and
essentially
got
zero
results.
So
I
wonder
if
it's
possible
to
try-
and
you
know,
have
a
title
and
the
team
name
be
somewhat
separate.
I.