►
A
If
you
do
have
any
questions
in
between,
I
would
say,
put
them
in
the
chat
and
would
just
talk
afterwards
about
the
specific
things
with
that
yeah
I'm
michael
typically,
my
last
name
doesn't
really
work
in
english.
So
I
I
just
said:
I'm
martin,
I'm
a
developer
evangelist
at
gitlab,
which
means
I'm
trying
to
share
the
latest
tech.
Try
to
engage
with
our
community,
make
your
life
easier,
create
trainings,
presentations,
education,
material.
A
A
I
super
much
enjoyed
the
tool
boost
button
on
the
the
old
computers
from
33
to
66
megahertz,
and
this
was
kind
of
the
inspiration
to
study
how
the
software
systems
engineering
on
the
university
of
applied
sciences
in
harding
and
up
austria,
and
after
a
while
I
figured
well.
The
hardware
is
not
really
my
story.
A
I
might
just
look
into
more
into
software,
and
I
came.
I
went
to
vienna
for
nfc
development
in
early
2005
at
the
mobile
commercial
back
then
went
a
little
up
above
and
beyond
into
multimedia
streaming
with.
Linux
came
into
the
dns
development
at
the
university
of
vienna
and
somehow
touched
monitoring
and
monitoring
was
my
first
open
source
project
back
then,
and
I
kind
of
traveled
the
world
because
I
moved
to
nuremberg
eight
years
ago
joined
open
source
communities
became
a
gitlab
trainer
actually-
and
this
was
this
opened
my
doors
to
joining
gitlab.
A
A
So
I
want
to
dive
a
little
bit
how
my
first
impressions
were
and
how
everything
everything
worked
out.
We
do
have
some
resources
in
our
handbook
on
questions
for
companies
or
people
who
are
suddenly
remote
right
now,
so
this
wasn't
really
planned
or
maybe
just
going
ahead.
So
I
have.
I
I've
just
linked
the
top
questions
from
our
handbook,
because
darren
shared
that
I
think
two
hours
ago
in
in
the
past,
or
was
it
yesterday
in
a
different
time
zone?
A
Actually
so
I
wanted
to
share
it
with
you
as
well,
but
the
most
interesting
part
is
probably
how
a
workspace
could
look
like,
and
I
was
planning
quite
quite
a
while
or
actually
I
was
planning
to
have
everything
in
march,
but
then
the
pandemic
started
and
I
couldn't
buy
a
webcam.
I
couldn't
buy
a
standing
desk.
A
Basically
I
was
working
on
my
macbook
and
after
a
while,
I
had
the
chance
to
actually
create
my
workspace
and
I
was
eager
getting
a
standing
and
the
sitting
desk
because
I'm
two
meters
tall
and
it
it's
it's
still
complicated.
So
flying
on
an
airplane
is
yeah.
It
doesn't
it's
not
fun.
I'm
also
short-sighted,
which
means
I
needed
a
monitor,
which
is
good
for
my
eyes,
not
to
get
that
tired,
and
so
I
was
trying
some
things
and
revving
monitors
and
hardware.
A
I
also
have
a
noise
cancelling
headphone
which
I'm
using
right
now,
so
any
neighbor
who
might
ring
the
bell
right
now
is
I
don't
hear
it
and
you
won't
hear
it
either
and
one
thing
I'm
I'm
also
like
capable
of
I'm
living
a
little
bit
outside
of
nuremberg
in
the
countryside.
So
normally
I'm
looking
into
the
green,
which
also
helps
me
refresh
my
mind
or
relax
my
mind
a
little.
A
A
I
basically
got
a
new
gitlab
issue
assigned,
so
I
got
access
to
my
gitlab
account
and
my
my
gmail
account
before,
and
then
it
was
all
the
way
through
going
to
secure
my
account
because
two-factor
authorization
is
required
for
our
accounts.
We
have
a
strong
security
policy,
my
macbook
needs
to
be
encrypted
and
everything
is
basically
with
marked
on
tasks
list
and
checkboxes
in
gitlab
itself.
A
You
might
have
tasks
for
one
week,
but
still
if,
if
you
cannot
do
it,
onboarding
takes
a
month.
Onboarding
might
take
three
months
and,
to
be
honest,
there
might
be
some
things
which
I
haven't
done
yet
because
it
can
get
overwhelming
and
oftentimes.
You
learn
more
when
you
just
try
things
out
or
you
ask
someone
and
yeah.
It
went
really
really
well
and
I
was
not
working
70
hours
a
day
a
week.
It
was
just
like
the
40
40
hours,
but
I
also
needed
to
find
the
daily
routine
and
other
things.
A
A
A
It's
it's
just
a
way
of
keeping
information
in
the
cloud
keeping
it
available,
because
when
I
write
something
down
two
hours
later
or
maybe
10
hours
later
in
a
different
time
zone,
someone
else
can
say:
oh
we
talked
about
this.
Mighty
is
sleeping
currently
and
we
have
it
available.
It's
not
somewhere
in
your
directory
tree
on
your
notebook.
A
It's
it's
a
boy
label
for
everyone
at
gitlab.
The
other
thing
we
do
is
when
a
meeting
happens.
It
has
an
agenda.
Otherwise
it's
no
meeting
and
we
do
keep
live
notes,
which
means
there
is
no.
There
is
no
direct
person
assigned
to
to
writing
the
the
protocol.
This
happens
naturally,
in
the
meeting.
Someone
takes
the
role
and
it's
it's
just
being
done,
and
it's
also
possible
to
define
to-do's
from
the
google
google
notes
and
then
later
on,
create
action
items
from
that
and
a
similar
thing
happens
with
presentations.
A
So
right
now
you're
seeing
a
google
slide
presentation,
which
is
what
we
use
for
anything
where
we
want
to
create
a
presentation
from
yeah.
The
other
thing
is
what
I
needed
to
learn
is
slack,
so
I've
been
using
some
chat
tools
before
and
I
knew
about
slack
and
I
thought
well,
I
would
be
just
training
in
there
and
then
maybe
search
for
for
past
events
or
past
discussions
yeah,
but
it's
actually.
A
So
slack
is
not
the
knowledge
base
and
it's
not
the
single
source
of
truth,
which
is
our
handbook.
So
anything
which
has
has
an
impact
or
needs
to
be
documented
or
defines
a
process
or
maybe
even
is
a
change
to
a
process
needs
to
be
added
to
the
handbook
which
makes
this.
I
think
there
are
7
000
pages
right
now.
If
you
would
print
it,
I
haven't
read
it
all
to
be
honest,
but
the
handbook,
for
example,
being
public
really
helped
to
prepare
for
my
role,
because
I
could
look
up
everything
in
advance.
A
A
There's
normally,
there's
no
live
presentation,
because
when
you
do
presentations
over
soon,
which
is
right
now
as
well,
it
can
get
quite
exhausting
because
you
are
just
listening
or
just
watching
the
presentation
and
after
a
while,
you
might
get
distracted
or
might
be
doing
something
else,
and
it's
we
use
slides
in
a
way
to
just
review
them
and
we
discuss
the
changes
or
the
the
things
we
see
in
there
and
also
have
the
notes
in
the
agenda.
Back
then,
with
that
on,
on
the
right
hand,
side,
I've
actually
taken
a
screenshot.
A
A
So
when
there
were
100
people
editing
a
google
document,
it
might
get
stressful
a
little
for
for
for
the
google
servers,
but
still
it's
live
editing.
We
do
want
to
add
that
to
gitlab
as
well,
but
the
technology
is
not
yet
there,
but
we
do
have
some
ideas
and
feature
requests
for
this,
but
right
now
we're
using
google
docs
for
that
yeah
a
little
bit
more
about
the
direct
collaboration
and
things
we
do
together.
A
I
needed
one
thing
which
fascinated
me
that
everyone
can
see
what
I'm
doing
so
any
issue
update
any
much
request.
Anything
which
which
happens
in
the
public
public
is
there
and
you
can
respond
to
me
so
when
you're
following
my
activities
on
gitlab.com,
for
example-
and
you
see
some
interesting
stuff
for
some
interesting
feature-
requests
going
on,
you
could
just
jump
in
there
and
comment
and
say:
hey,
michael.
Maybe
we
can
implement
this
that
way
so
that
our
development
workflow
gets
any
better
in
in
regard,
for
example,
with
the
travel
integration
to
gitlab.
A
The
other
thing
is
our
meetings
and
discussions
are
getting
recorded
and
we
try
to
record
it
every
time,
just
because
everyone
who
is
not
in
our
time
zone
or
not
cur
not
able
to
attend.
The
meeting
can
watch
the
recording
later
on
and
there
is
no
pressure
to
attend
any
meetings
you
could
also,
for
example,
say
I
have
a
busy
week.
I
need
to
prepare
for
presentations
or
I
might
just
implement
a
new
feature
and
I
watch
the
recording
later
on,
maybe
with
double
speed,
just
to
get
a
glimpse
on.
A
Also,
normally
I'm
trying
to
look
into
the
camera,
which
is
a
total
strange
feeling.
Sometimes
it's
totally
okay
to
look
to
do
something
else
or
to
like
work
on
the
site.
And
when
someone
says
your
name
say
hey
sorry,
I
didn't
listen.
Can
you
repeat
the
question
and
then
you
can
join
the
conversation
as
well
and
if,
if
you
want
to
like
look
from
the
outside,
everything
is
uploaded
to
our
youtube
channels.
A
So
before
joining
gitlab,
I
was
watching
group
conversations
and
I
got
an
idea
how
things
work
or
maybe
how
features
are
getting
implemented
and
oftentimes.
There
are
also
live
streams,
which
means
the
group
conversation
is
live
streamed
to
to
youtube
and
you
can
watch
it.
This
also
happens
for
release
planning.
So
if,
for
example,
the
next
release
will
be
13.5,
so
the
release
kickoff
videos
are
already
online
and
everyone
can
look
into
it.
What's
coming
and
what's
what's
cooking.
A
There
is
no
immediate
response
and
I
shouldn't
write
anything
in
slack
and
say:
hey.
I
need
to
respond
now,
because
the
other
person
might
just
be
out
for
a
walk
or
might
just
be
sleeping
or
something
else
so
there's.
No.
We
shouldn't
put
any
pressure
on
that.
The
other
way
is
getting
attention
is,
should
be,
should
be
focused
on
a
single
person
or
maybe
a
group
of
people,
but
using
the
ad
mentioned
for
for
a
channel
with
600
or
maybe
even
1,
300
people
this.
A
The
other
thing
is,
we
do
use
private
messages,
but
we
are
also
trying
to
avoid
it,
because
the
private
message
message
cannot
be
shared
with
new
conversation
members
later
on
sorry
or
they
might
be
just
yeah.
You
want
to
add
a
new
member
to
the
conversation
share.
It
link
it.
You
cannot
do
that
with
a
private
message
and
we
are
trying
to
create
just
a
public
channel
with
the
small
group
for
that.
Instead.
A
But
I
would
say,
generally
speaking,
because
they're
listed
on
is
the
fifth
point:
switching
to
email.
I
think
I'm
not
using
email
that
much
most
often
times
we
are
discussing
in
slack
and
when
there
is
an
action
which
needs
to
be
documented
because,
like
gets
retired,
we
just
move
ahead
with
creating
an
issue
or
directly
proposing
nmr.
A
A
Some
other
tips
for
remote
communication,
because
this
is
something
I
needed
to.
I
would
say
I
needed
to
learn
and
adopt
it,
because
some
things
are
just
not
the
same
as
when
you're
sitting
in
an
office
or
maybe
just
going
over
to
your
colleague
and
saying
hey.
I
want
to
talk
about
this.
Do
you
have
time
focus
on
on
or
embrace
asynchronous
communication,
which
means
you
don't
really
expect
an
immediate
answer.
A
You
either
communicate
in
slack
or
even
in
gitlab
issues,
and
you
have
a
golden
rule,
which
means,
if
you're
going
too
much
back
and
forth
that
often
so
playing
ping-pong
with.
I
want
to
do
this.
What
do
you
think
and-
and
things
like
that,
we
do
have
the
the
rule
when
it's
sweet
three
times
we
just
schedule
a
coffee
chat
or
a
sink
call
and
say
hey.
Let's
just
talk
talk
about
it.
A
The
same
goes,
for
example,
for
production
incidents
when
gitlab.com,
for
example,
is
affected
and
different
teams
need
to
cross-collaborate
on
resolving
the
issue.
We
oftentimes
just
start
a
zoom
session
and
discuss
what's
what's
next:
what's
coming
to
some
screen
sharing
and
so
on,
if
we
communicate
asynchronously,
we
look
for
low
context
conversations
which
means
providing
as
much
detail
as
possible.
So
I
it
shouldn't
be
like
the
10
pages
brain
dump
thing,
but
it
should
someone
who
joins
the
conversation
later
on
should
be
able
to
understand.
A
What's
what's
going
on,
maybe
even
providing
a
tldr
tldr.
So
too
long
didn't
read
summary
at
some
point:
yeah,
and
maybe
someone
is
getting
on
on
vacation
and
someone
else
needs
to
take
over
so
there
shouldn't
be
the
need
to
explain
everything
from
the
beginning
again
and
the
last
one
which
is
mentioned
here
again
document
everything
have
the
meeting
agenda
actions
records.
A
A
A
We
don't
have
any
short
toes,
which
means
you
can
you
can
approach
someone
in
a
respectful
way?
We
can
work
together
and
it's
no
problem
if
someone
wants
to
give
a
talk,
for
example,
which
I
would
which
would
be
my
profession
at
gitlab
or
just
like
saying,
hey,
you're
you're
actually
doing
my
job.
Currently,
this
is
not
a
problem.
A
A
A
Okay,
another
tip
for
remote
collaboration,
and
this
is
something
I
I
wasn't
sure
about
to
be
honest.
When
joining
when
you're
working
in
different
time
zones,
you
also
have
different
daytime
formats
and
there
is
the
one
with
the
american
format,
and
then
europe
has
one
and
basically
parsing
parsing
it
reading
it
automating
it
becomes
not
so
nice
and
at
gitlab
we
agreed
on
using
the
iso
date
time.
A
A
A
Is
it
around
about
four
pm,
so
in
pt
it's
00
am
people
are
just
getting
up
and
we
also
do
have
helpers
inside
gmail,
for
example,
and
everything
around
it.
So
this
really
helps
to
focus
on
the
details
in
the
conversation
and
not
just
yeah.
This
may
might
be
minus
five
hours
and
this
might
be
minus
nine
hours
and
everything
else
gets
complicated
if
you
don't
have
a
single
source
of
truth
for
the
date
and
times.
A
This
was
lots
of
technical
and
collaboration
things,
one
thing
which
really
was
nice
also
in
the
first
week.
You
want
to
engage
with
your
future
colleagues,
you
want
to
work,
but
you
also
want
to
get
to
know
each
other
and
at
some
point
you
also
want
to
build
a
friendship
of
build
relationships,
and
that
was
the
plan
to
meet
everyone
in
prague
at.
I
think
it
was
end
of
march
for
gitlab
contribute.
A
So
all
gitlab
team
members
in
one
place,
but
that
didn't
work
out
in
terms
of
the
pandemic,
but
still
it's
just
every
year
we
try
to
meet
meet
each
other
in
in
one
place.
This
happened
didn't
happen.
Yet,
on
the
flip
side,
we
do
have
coffee
chats
and
the
coffee
chat
is
just
a
meeting
without
any
agenda.
You
talk
about
social
life,
about
family,
about
technology,
about
whatever
you
want,
and
you
can.
A
You
are
not
obligated
to
record
it,
for
you
don't
need
to
like
prove
that
you
did
something
valuable
for
the
company
in
that
regard.
It's
just
having
30
minutes
or
like
in
a
speeding
min
speedy
meeting
having
25
minutes
just
a
good
time
together
and
one
way
I've
been
also
using
it
for
engaging
with
the
wider
community.
Creating
some
product
feedback.
A
Ask
me
any
things
or
even
technology
exchange,
so
I've
kind
of
created,
a
german
everyone
can
contribute
caffeine,
which
is
like
the
german
version
of
the
coffee
chat
and
it's
super
nice
to
engage
with
our
community
and
share
some
technology
and
educate
each
other
on
the
latest
tech,
because
it's
often
times
it's
really
hard
to
keep
up
and
say
what's
coming,
what's
next,
what
is
kubernetes?
What
is
world?
What
is
ci
cd?
What
is
what's
what's
going
on.
A
But,
oh
I'm,
I
think,
I'm
running
a
little
out
of
time
in
terms
of
an
insights
into
my
workday,
and
this
will
be
rather
short.
I
think
I've
just
tried
to
collect
what
I'm
doing,
I'm
kind
of
checking
my
calendar
looking
what's
basically
coming
up.
I
have
my
focus
time
schedule
so
for
today's
presentation,
I
blocked
some
more
focus
time
being
able
to
just
create
the
slides,
I'm
checking
my
emails.
A
I'm
not
checking
them
often
so
it's
in
the
morning
at
lunch
at
maybe
end
of
the
day,
just
because
it's
as
synchronous
communication
and
no
one
expects
any
fast
responses
in
that
regard,
and
I
do
I
have
many
open
tabs
which
can
be
seen
in
the
screenshot,
I'm
just
keeping
things
which
I
read
in
an
email
or
like
in
an
issue
notification
and
just
work
on
it
later
on
when
I
get
the
time.
This
also
brings
me
to
to
my
to-do's.
A
A
This
was
a
recent
update
in
slack
which
really
helps
it,
and
everything
else
is
basically
I'm
trying
to
hide
it
behind
one
of
my
chrome
windows
on
my
huge
screen
just
because
it's
time
sync
and
every
time
I'm
trying
to
keep
up
with
all
the
messages
on
slack
I'm
losing
too
much
time.
To
be
honest-
and
this
is
why
I'm
trying
to
keep
it
organized
and
focused
on
specific
times,
I
do
check
on
slack
and
not
off,
not
not
enough.
A
You
have
so
many
columns
to
read
to
focus
on,
and
it's
really
impossible
to
say:
hey,
I'm
checking,
15
minutes
of
twitter
and
then
you're,
watching
the
clock
and
say:
oh
it's
two
hours
later
on,
so
I'm
trying
to
just
keep
focusing
on
it
and
the
other,
the
other
workflow.
During
the
days
I'm
exclusively
working
on
gitlab.com
on
issues
on
the
mrs.
A
I
do
prefer
the
web
ide,
which
is
embedded
into
gitlab
over
any
cli
access.
I
might
have,
might
need
so
I
can
do
anything.
Any
changes
for
documents
or
for
the
website
or
even
smaller
bug,
fixes
demos
directly
in
the
browser,
and
I
don't
need
to
switch
to
context
other
than
that.
I'm
using
google,
slides,
docs
social
media
and
yeah,
and
sometimes
when
I
like,
want
to
focus
I'm
also
listening
to
music,
some
edm
or
trance
stuff,
which
helps
me
focus
even
more
yeah.
A
The
second
thing
which
is
important
is
we
try
to
keep
the
merge
request
throughput
as
good
as
possible,
so
we're
trying
to
work
in
short,
iterations
or
with
the
minimal,
minimal,
viable
change.
You
might
see
that
in
our
ecosystem
as
an
mvc
and
we're
not
trying
to
ship
the
perfect
feature
which
might
take
six
months
to
complete,
but
just
in
smaller
batches
and
smaller
changes,
and
the
idea
is
that
everyone
can
contribute.
A
A
We
do
have
a
timeline
for
releases,
and
this
worked
since
many
years
now,
so
there's
the
plan
to
release
gitlab
on
the
22nd
of
each
month
month.
This
has
been
done
for
107
months
now,
and
you
can
like
set
the
time
to
see
that
the
release
kicker
for
the
next
release
happens
on
the
18th
and
then
afterwards
on
the
22nd.
There
is
a
new
release
coming
out
in
terms
of
how
the
the
issues
and
the
life
cycles
are
being
done,
just
a
quick
overview.
A
A
You
should
be
able
to
integrate
gitlab
with
other
ticket
systems,
especially
chara
for
that,
for
that
example,
and
it
should
be
possible
to
not
only
kind
of
sync
the
issues
but
also
interact
with
them
in
a
way
that
the
merge
request
or
something
which
triggers
a
ci
test
of
some
feedback.
Loop
also
updates
the
gyro
issue,
and
there
is
a
deep,
inter
integration
between
gitlab
and
gyro,
and
this
gets
improved.
Our
release
in,
I
think
in
the
current
release,
there's
also
something
inside.
A
We
also
have
community
contributions,
which
means
everyone
can
contribute,
contribute
to
anything
which
gets
proposed.
There
is
an
accepting,
much
request
label
specifically
for
these
kind
of
features
and
issues
and
our
engineers
and
our
teams
are
trying
to
help
with
reviews
help
with
on-boarding
in
in
terms
of
making
it
easier
to
improve
gitlab
as
it
on
its
own.
A
Oftentimes
there
is,
there
are
lots
of
things
going
on
between
the.
I
think
it's
14
stages
right
now,
and
there
are
many
open
issues
around
about
33
000.
I
think
in
summary,
just
for
the
the
main
product
we
use
bots
to
help
which
help
us
stay
organized,
and
this
helps
us
in
a
way
of
doing
automated
review,
updating
the
labels
having
tried
reports,
which
means
there
are
10
open
issues
which
haven't
been
triaged.
A
We
do
have
staging
environments,
but
sometimes
you
trigger
bug
in
production
and
we
coordinate
each
other
in
resolving
that
yeah.
This
was
the
latest
release
and
everything
single
month
still
happens
last
but
not
least,
automate
everything-
and
this
should
be
probably
interesting
for
everyone
integrating
with
gitlab
and
working
with
gitlab
in
the
future.
A
There
are
some
ways
to
engage
slack
at
gitlab
and
with
gitlab.
We
use
slack
in
specifically
with
bots
for
taking
pto
paid
time
off,
we're
also
having
people
ops,
announcing
new
hires,
but
we're
also
integrating
it
with
incident
management,
meaning
to
say
our
on-call
engineers
can
create
tickets
from
with
chat
ups
integration.
A
A
Other
than
that,
next
to
the
aforementioned
issue,
triad
spot
and
review
roulette.
We
have
developer
evangelist,
also
have
created
our
own
bot,
which
helps
us
with
specific
campaigns
on
doing
some
release.
Eventualism,
which
means
sharing,
was
coming
and
was
cooking
in
our
releases
and
some
more
social
media
things
and
everything
is
developed
in
the
open.
So
if
you
need
inspiration,
I've
linked
it
at
the
bottom.
A
So
it's
possible
to
integrate
that
into
gitlab
and
saying
please.
I
want
to
deploy
it
into
my
kubernetes
cluster,
maybe
even
a
different
virtual
machine,
and
I
can
see
the
website
live
and
don't
need
any
local
development
environment
just
to
verify
the
formatting
of
the
blog
post.
The
changes
on
the
website
the
changes
on
the
web
application
anything
which
comes
to
mind,
which
needs
a
deployment
deployed
environment
to
be
reviewed
and
verified.
A
Yeah,
next
to
that,
we
also
keep
using
feature
flex
feature
flex,
allow
us
to
roll
out
specific
features
behind
the
flag,
and
there
was
there
are
deployment
strategies
behind
that.
Where
you
can
say,
I
want
to
only
test
a
small
group
of
people
which
could
be
the
gitlab
team
members,
for
example,
and
customers
are
not
affected,
and
it's
also
possible
to
hide
like
experimental
features
behind
the
feature
flag
and
on
and
have
them
not
affecting
the
self-hosted
release,
which
comes
on
the
22nd
even
more.
A
You
can,
if
you
can
integrate
security
scanning
and
security
testing
in
your
ci
cd
pipelines
within
into
gitlab,
to
get
an
idea
whether
the
code
changes
would
introduce
a
security
problem
would
introduce
maybe
runtime
problems
or
the
rest.
Api
is
affected
from
any
problematic
queries.
There
is
container
and
dependency
scanning
as
well.
A
We
are
dog
fooding,
our
own
release,
gitlab
release
feature
in
a
way
that
we
kind
of
present
our
own
releases
from
that
and
there's
a
there's
also
the
possibility
to
automate
that
within
the
gitlab
ci
cd
most
recently,
because
we
have
12
stages
of
different
products,
product
managers
and
features
we're
also
automating
or
improving
the
release
post
generation.
So
everything
you
read
on
about
gitlab.com
on
the
blog
is
a
huge
collection
of
many
features,
and
this
also
needs
to
be
coordinated,
because
you
cannot
really
write
a
single
blog
post
page
from
that.
A
Okay,
I
think
I
have
too
many
slides.
I
think
this
is
one
of
the
last
ones:
quality
engineering
like
q
and
a
is
also
a
big
part
next
to
us
being
next
to
us
testing
gitlab
on
a
daily
basis.
Actually,
we
have
our
quality
engineering
team,
which
ensures
that
everything
gets
tested,
that
workflows
get
improved
and
to
end
monitoring
improvements
on
unit
tests
and
further
ideas,
everything
out
of
that
basically
new
adventures.
A
Since
we
document
everything
you
can
kind
of
find
everything.
I've
talked
about
now
on
gitlab.com,
be
it
inspiration
for
your
own
workflows
in
terms
of
labels,
issue
templates
boards
and
so
on
many
different
things
you
can
also.
Maybe
maybe,
if
you
want
to
kind
of
review
your
documents
for
marketing
strategies
and
have
that
in
gitlab
as
well.
So
it's
not
just
about
code
and
there's
also
things
which
some
sometimes
happen.
A
Naturally,
with
like
stepping
on
each
other's
toes
and
one
story
I
wanted
to
share
was
I
did
a
ci
monitoring
webcast
recently.
We
also
had
a
discussion
on
ci
efficiency
and
in
a
different
issue
and
quality
engineering
added
some
more
ideas
to
improving
and
to
improving
the
ci
pipelines
and
cost
savings
and
other
things,
and
then
we
created
the
documentation
which
benefits
our
users
and
customers.
A
I
would
recommend
to
check
out
the
remote
handbook
if
you
haven't
already
join
social
media,
follow
our
all
remote
experts
ever
evaluate
your
workflows.
What
you
want
to
use
with
gitlab
the
gyro
integration,
the
automation
with
triage
bots
for
issues,
use
the
rest,
api
deployment
releases
yep
and
maybe
adopt
some
culture
or
adopt
the
culture
and
values
update,
create
your
own
company
handbook
in
a
way
that
it
involves
everything
we
do,
or
even
let
you
let
inspire
you
by
that
yep
and
that's
about
it.
I
think
yeah
I'm
in
time.