►
From YouTube: Progressive Delivery Office Hours
A
All
right,
hello,
everyone!
Thank
you
all
for
being
here.
This
is
the
first
time
that
we've
done
community
office
hours
for
my
group,
the
progressive
delivery
group
at
get
lab,
and
so
we're
new
to
this
and
we're
just
gonna
like
we're
just
gonna
torch
through
and
do
our
best.
I've
got
a
small
agenda,
but
I
thought
maybe
it
would
be
good
to
start
with
introductions.
A
A
A
B
C
Hi
everyone,
my
name,
is
etienne.
I
am
backend
engineer
in
the
progressive
delivery
team
I've
been
at
with
gitlab
for
the
past
year
and
a
half
not
quite
and
yeah.
I
mainly
work
on
integrating
our
yeah
ci
tool
touring
with
aws
and
I've
been
recently
also
been
doing
some
some
work
on
deep
blue
keys
and
if
I'm
cutting
off
it's
because
my
connection
teleconnection
has
been
pretty
bad
this
afternoon,
so
I
may
turn
off
turn
on
we'll
see
the
camera.
The
video
fyi.
E
Yeah,
so
I'm
rajendra
I'm
based
out
of
mumbai.
I
work
in
the
open
source
team
here
at
august
tech.
I
contribute
to
selenium
and
the
entire
ecosystem
full
time.
I
also
contributed
to
bitlab.
I
have
been
a
gitlab
hero.
Few
months
now
and
today
I
just
got
the
news
from
david
that
I
have
been
nominated
in
the
core
team,
so
I'll
be
joining
the
coding
soon
I'll
be
on
the
page
and
yeah
that's
about
it.
So.
D
A
Contributing
to
the
efforts
that
progressive
delivery
works
on
just
as
like,
with
anywhere
inside
kit
lab
there's
a
you
know.
There
are
we,
everything
is
powered
by
issues
and
those
issues
are
sort
of
segregated
by
labels
and
so
like
the
progressive
delivery
label
is
a
key
one
to
look
for
as
well
as
like
the
accepted,
merge
requests
or
some
other
ones.
A
We
might
look
at
here
in
a
second
and
just
like
to
know
where
to
to
find
us
in
the
handbook
on
the
progressive
builder
group
page
and
myself
or
the
other
people
here
who
are
merge,
request
coaches
can
help
you
through
getting
your
your
stuff
merged.
If
you're
not
already,
don't
already
have
permission
to
do
so
or
to
to
to
do
that
so
yeah,
I
think
just
most,
notably
some
issues.
A
There's
like
we
have
a
pretty
large
backlog
of
issues
that
have
been
that
the
bot
has
labeled
accepting
word
requests,
but
anything
between
bugs
to
you
know
certain
types
of
follow-up
and
ux
debt
or
technical
debt
or
features
that
have
just
been
languishing
the
back
backlog.
So
there's
no
shortage
of
work
and
places
for
people
to
contribute,
and
we
welcome
all
those
contributions
from
everyone,
so
so
yeah.
A
I
thought,
like
I,
I
have
seen
like
a
couple
of
recent
and
there's
a
couple
of
most
recent
like
submissions
I've
seen
from
sashi
about
like
web
hooks
and
some
some
like
notifications
and
other
those
types
of
things
have
like
come
through
recently.
Those
are
the
ones
that
are
like,
like
kind
of
like
front
most
on
my
radar,
but
that's
not
not
to
not
to
discount
rajendra's
contributions.
I
just
don't
know
exactly
where
they
are
at
the
moment,
so
so
yeah.
A
Atn
has
done
some
work
there,
that's
pretty
new
to
us
and
we're
still
trying
to
get
through
the
the
organizational
like
triaging
of
what
issues
were,
how
we're
going
to
prioritize
what
issues.
So
I
don't
know
I
I
had
an
item
here
and
I
don't
know
if
atn
might
know
better.
But
if
there's
like
a
an
entry
point
for
someone
to
contribute
to
that
effort,
since
it's
it
may
not
be
reflected
in
those
other
issues
that
are
that
are
shown
there.
C
I
will
just
yeah
jump
here
and
what
can
I
what
else
can
I
add
on
auto
devops?
Yes,
I've
been
working
on
that
as
chase
said
like
over
the
past
few
months
or
so,
but
specifically
just
like
efforts
on
connecting
auto
devops
with
aws,
right
and
and
just
providing
users
the
capability
to
deploy
on
an
ecs
stacks
more
recently
trying
to
automate
to
automate
the
provisioning
of
an
aws
stack
with
cloud
formation.
C
So
we
opening
up
onto
major
cloud
platforms
and
our
efforts
have
been
like
focused
mainly
on
aws,
but
yes,
future
efforts
will
focus
on
azure
and
and
and
then
yeah,
I
think
more
with
gcp.
I'm
I'm
I'm
not
that,
as
you
know,
knowledgeable
on
that
side
of
things
but
yeah,
my
effort
has
been
focused
mostly
on
aws
but
yeah.
There
is
like
a
big
opening
and
lots
of
like
upcoming
work
for
us
regarding
the
ability
to
deploy
onto
major
platforms.
A
Thanks
again,
one
product
category
that
we've
moved
into
core
that
you
may
have
seen
that
part
of
13
5
is
that
feature
flags
are
now
available
to
everyone
and
that's
like
a
an
area
which
we're
looking
to
get
a
lot
more
feedback
from
other
people.
The
community
to
you,
know
kind
of
kick
the
tires
and
help
us
mature
that
product
category.
A
A
Both
of
these
things
are
are
just
as
well
documented
as
other
product
categories
and
things
that
we're
working
on.
So,
if
you're
curious,
there's
things
to
look
at
there
is
there
anything
that
we
can
do
to
like
help
help
you
all
contribute
more
easily
or
or
can
we
answer
any
questions
or
help
provide
any
guidance
for
your
contributions
either
of
you.
E
As
for
me,
I
don't
think
is
that
there
is
anything
like
the
documentation
is
it's.
I
feel
like
it's
top
notch
and
helps
me
in
contributing
to
issues
I
just
go
by
looking
for
labels
that
accepting
more
gps,
and
particularly
the
backend.
So
I
don't
remember
what
part
of
the
devops
I
have
contributed
to
as
such,
but
it's
mostly
something
that
needs
to
be
done.
If
it's
done
so
for
the
past
few
months
I
have
been
focusing
on
four
decks
around
fixing
some
offenses
of
rubocops
and
stuff.
A
D
I
also
don't
have
any
specific
thing.
Maybe
one
thing
to
call
out
is
the
documentations
on
the
feature
flag.
I
worked
on
this
feature
where
I
worked
on
enabling
web
hooks
for
feature
flags.
It
was
kind
of
easy
for
me
to
get
started
because
the
documentation
was
in
place,
and
I
also
simultaneously
worked
on
enabling
web
hooks
for
deployments,
which
I
kind
of
struggled
a
bit
to
get
through,
because
I
had
to
set
up
a
local
environment
and
connect
to
a
kubernetes
cluster
to
do
that.
D
A
B
E
I
started
off
with
error
tracking
sorry.
I
started
off
with
error
tracking,
so
peter
leads
him
has
been
very
helpful
in
getting
up
and
getting
me
up
and
running
around
contributing
to
api
so
and
during
that
time
I
think
that
needed
a
lot
of
work
around
so
the
pm
for
error
tracking.
I
think
she
had
a
lot
of
tasks
the
pipeline
and
I
sort
of
took
the
api
integration
stuff
with
sentry.
E
A
E
No,
I
think
labels
haven't
been
very
helpful,
so
sort
of
it
filters
out,
of
course,
the
backend
and
the
front
end
itself
first
and
then
whatever,
but
one
thing
that
we
can
maybe
add
is
so
recently
like.
If,
if
some
issue
has
the
merge
request
being
worked
upon,
it's
not
seen
in
the
filter,
I
think
so.
I
have
to
go
to
the
issue,
details
page
or
maybe
check
out
on
the
right
hand
side
of
the
issue
this.
It
shows
a
symbol
of
icon
having
a
mouse
request.
E
So
sometimes
people
end
up.
I
mean
working
two
people
working
on
the
same
issue
and
then
the
second
one
knows
like.
Oh
it's
been
locked
upon
by
someone
else.
Then
the
time
is
gone
and
the
mod
has
been
closed
or
something
like
that.
So
maybe
have
a
filter
around.
I'm
not
sure
if
it
comes
under
your
radar
to
have
the
issue
filter
in
place.
Whether
issue
has
a
request
or
not.
E
A
Sometimes
I
think
that
there's
difficulty
adding
other
people
who
are
not
part
of
the
get
lag
or
get
lab
organization
to
the
issue
as
like
an
assignee,
I
know
we
have
we've
had
that
some
trouble
there
in
the
past
of
having
to
reass
having
to
assign
it
to
a
like
an
internal
person
like
a
teammate
to
in
order
to
like
just
track
it
a
little
more
effectively
but
yeah.
That's
that's
that
those
are
that's
a
good
call
out.
Thank
you,
sashi!
Do
you
have
any?
A
B
C
A
A
B
I've
been
personally
I've
been
I've,
been
interested
in
the
merger
quest
coach
part,
so
I'm
checking
what
is
required
there
to
help
the
the
contributors
be
more
effective
and
maybe
triaging
some
mmrs
and
stuff
like
that,
so
yeah.
I
would
second
what
you
asked.
If
the
there's
anything
we
could
help
or
be
there
for
it
would
be,
I
would
be
super.
I
would
be
super
happy
to
help.
A
B
A
Like
a
small
series
of,
like
you
know
like
behaviors
to
to
follow,
but
but
otherwise
that
there's
no
like
formal
training
or
anything
else,
you'll
just
be
at
like
a
on
another
list
for
for
for
people
to
help
them
navigate
like
reports
of
issues
or
merge,
requests
that
show
up
from
from
the
community
to
to
help
find
a
adequate
reviewer.
The
right
you
know,
maybe
the
right
group,
the
provide
feedback
reviews
move
it
through
the
workflow.
That
is
one
thing.
A
You
all
may
already
know
this,
but
that's
kind
of
the.
What
has
to
happen
with
that
with
that
with
the
planning,
and
also
with
the
the
execution
of
delivering
features
and
and
in
all
contributions?
So
that's
just
something
to
be
aware
of
for
those
who
may
be
watching
this
in
the
future.
That's
that's
sort
of
part
of
it.
A
Yeah,
I
guess
there's
nothing
else.
I
just
want
to
reiterate
that,
like
we
greatly
appreciate
your
contributions
and
thank
you
so
much
for
for
contributing
in
the
past
and
hopefully
continue
continuing
to
contribute
into
the
future,
I'm
happy
to
stick
around
and
answer
any
more
questions,
or
we
can
talk
about
if
there's
something
you'd
like
to
talk
about
something
currently
that
you
have
open
and
you'd
like
to
share,
and
we
you
know
to
walk
through
the
mr
or
or
whatever
happy
to
take
like
the
next.
A
A
Yeah
so
because
this
is
kind
of
new
to
us-
and
we
didn't
know
what
the
wait
I
kind
of
didn't
know
if
anybody
would
show
up.
So
that's
it's
great
that
you
all
are
here
the
yeah
we
were
considering
like
starting
with
quarterly,
but
if
there
is
demand-
and
if
there's
value
in
having
this
conversation
more
frequently
to
to
further
the
you
know
the
contributions
longer
or
make
sure
that
you
are
getting
the
resources
you
need
to
contribute,
then
I
think
we
could.
A
Cool
awesome:
well,
thank
you
all
for
your
time
for
being
here
and
for
for
everyone
taking
time
part
of
their
evenings
and
part
of
their
their
mornings
to
to
be
here
and
just
just
again.
Thank
you
for
all
the
contributions
and
all
the
hard
work,
and
you
know
how
to
find
us
now
and
and
and
don't
be,
don't
be
hesitant
to
reach
out
to
us.
If
you
need
something
so
cool.
Thank
you.
I
hope
you
all
have
a
good
day
bye.
Thank
you.
So
much.