►
Description
Weekly sync call of the Static Site Editor group focused on engineering efforts.
A
A
So
just
a
quick
shout
out
reminder
that,
from
tomorrow,
job
will
be
on
paternity
leave,
he's
twin
for
due
to
be
born
on
Wednesday
morning,
early
I'm
spoken
today.
We
talk
about
just
kind
of
like
you
know
he
was
talking
about.
You
know
how
does
he
stay
kind
of
like
involving
team
and
so
on?
He
doesn't
want
to
come
back
and
be
all
you
know
infamous
foreign,
so
I
said.
Look
everything
we
do
is
recorded
he's
more
than
welcome
to
jump
in
and
joined
calls
and
are
taking
conversations.
A
They
will
just
be
no
expectation
from
outside
on
him
to
deliver
anything.
So
I
said,
depending
on
how
how
crazy
things
might
be
that
if
he,
if
he
held
him
down
time
and
he's
bored
he's
more
than
welcome
to
pop
in
on
a
call
chat
with
us
and
slack
I
encouraging
to
post
on
keep
baby
photos
in
our
social
channel.
So
but
essentially,
there's
no
expectation
on
the
info.
A
Any
output
from
from
the
next
while
and
whatever
involvement
he
has,
is
that
his
discretion
was
wing
he's
able
to
to
do
so
yeah,
so
a
bit
like
Jacques
and
we're
holding
France
for
a
safe
delivery
on
to
the
engineering
stuff.
So
I
wanted
to
start
off
with
just
kind
of
like
looking
ahead
at
thirteen
point
three.
So
in
essence,
thirteen
point
three
focuses
a
continuation
of
thirteen
point.
A
Two
we're
going
to
carry
on
with
the
the
handbook
integration
there's
some
issues
that
we've
brought
forward
from
thirteen
point
three
that
we
plan
to
work
on
specifically
the
formatting
change,
as
you
use
the
the
editor
which
has
pushed
some
other
issues
out
and
that's
okay,
because
in
the
broad
scope
of
things
we
will
be,
we
will
be
making
sure
that
we
focus
on
continuing
with
the
integration.
The
goal
at
the
end
of
fitting
pin
three
is
to
open
up
the
static
site
editor
to
all
of
gitlab.
A
To
say:
hey
this
tool
is
now
available
to
edit
your
handbook
pages
feel
free
to
use
it.
It's
not
to
make
it
the
default
or
only
editor,
but
it
is
to
to
open
it
up
and
to
say
you
know.
We
believe
that
all
pages
in
the
handbook
is
now
editable
by
the
editor.
Go
ahead,
use
it
Dawg
through
the
product,
and
you
know,
give
us
the
feedback,
the
yeah
as
a
recapping,
that
our
our
objective
at
the
end
of
this
week
is
to
is
to
release
it
to
to
the
product
group
and
to
say
hey.
A
A
We
are
sticking
your
objectives
is
to
continue
with
the
handbook
performance
or
an
architecture
focus
so
we'll
continue
to
work
on
the
mana
repair.
Restructure
and
I
hopefully
wrap
that
up.
As
well
as
have
a
crack
at
upgrading
to
frontman
2,
to
see
what
performance
improvements
we
can
get
there,
and
we
also
want
to
improve
the
handbooks
UX
and
we
want
to
surface
things
like
who
updated
a
page
last
and
and
make
some
tweaks
to
the
UX
and
then,
lastly,
we're
going
to
continue
to
focus
on
some
strategic
support
to
the
docs
project.
Mostly
around.
A
A
A
A
We
might
have
a
sink
call
discussion
about
it
if,
if
it
makes
sense
and
if
our
timings
overlap-
or
we
just
do
an
async
discussion
in
the
issue,
but
I
want
to
start
introducing
a
lot
more
focus
in
iteration
I,
guess
not
that
we
haven't
had
a
iteration
focus,
but
a
more
purposeful
and
deliberate
focus,
and
hopefully
out
of
that
can
come.
Some
recommendation
on
process
that
we
can
adopt
going
forward.
A
And
the
last
thing
I
know
general
that
I
wanted
to
highlight
is
just
for
you
to
all
to
be
aware
that
there's
news,
frequent
labels
that
have
been
introduced
at
the
backstage
label
has
now
been
deprecated
and
we
should
stop
using
it.
There's
two
feature
related
scoped
labels
that
that's
been
that's
been
introduced.
If
you,
if
you
have
a
look
at
the
link
in
the
agenda,
you'll
see
this
feature
edition,
which
is
when
you
work
towards
create
the
creation
of
a
new
feature.
A
So
this
this
is
very
much
kind
of
like
iteration,
and
then
this
feature
maintenance.
So
that
could
be
working
with
technical
depth,
your
tests
and
adding
tastes
of
backfilling,
taste
and
so
on.
It
is
not
about
fixing
the
bug
bugs
have
their
own
specific
label
and
then
the
other
new
scrub
labels
that
have
been
introduced
is
around
tooling,
so
emails
related
to
pipelines,
configuration
will
have
tooling
pipelines
and
in
most
related
to
improvements
of
the
engineering
workflow
and
the
release
tooling
will
have
workflow.
The
teamwork
fell
apart
so
case.
A
A
A
C
C
We
are
learning
along
the
way
we
found
out
that
we
need
to
adapt
this
race
I'd
hate
to
be
more
consistent
with
the
formatting
guidelines
of
a
of
the
handbook
part
down
guide
so
that
we
are
focused
this
week.
The
reckon
I
would
work
on
on
adapting
the
hate
or
to
follow
those
guidelines,
but
at
the
same
time,
thinking
or
trying
to
keep
the
doors
open
to
meditate
or
more
configurable
to
adopt.
You
know,
preferences
from
other
users
in
relation
to
markdown
for
money,
so.
A
All
right,
the
next
one
outcome
for
jerk
is
the
image
upload
handover,
so
in
in
my
one-on-one
with
him
today.
The
only
part
of
the
image
upload
stuff
that
he
hasn't
been
able
to
complete
is
the
third
iteration
of
that
feature,
which
is
about
previewing.
The
image
in
the
editor
and
I,
asking
to
just
do
kind
of
like
a
handover
recording
which
is
done,
and
it's
uploaded
to
our
YouTube
channel
I've,
put
a
link
in
there.
They're
got
provisionally
got
you
working
on
that
in
13.3,
but
Jacques
said
he
can
make
himself
available.
A
B
So
the
plan
is
that
we're
going
to
just
not
try
to
only
move
the
blog
and
releases
down
to
their
own
site,
but
basically
you
move
everything
that
is
left
besides
the
handbook
into
its
own
mono
repo
site,
and
then
that
will
be
done.
It'll
be
separate
from
the
handbook,
which
is
the
one
clear
area
of
separation
that
we
own
and
then
they
can
decide
to
split
it
up
or
not
or
switch
to
different
tools.
However,
they
want
and
I
also
plan
on
prioritizing
like
splitting
out
the
deployment.
B
So,
ideally
maybe
they
just
have
a
their
own
bucket
that
they
deployed
who
and
will
have
no
impact
on
the
handbook
and
then
also
try
to
continue
down
the
road
of
separation
and
isolation,
pull
more
stuff
into
the
handbook.
So
we
can
do
the
styling
and
all
of
the
other
plans
that
we
have
without
being
impacted
with
the
directions
they're
going,
which
are
definitely
different
than
ours.
B
A
Just
just
also
for
for
transparency,
the
marketing
team
is
evaluating
potentially
switching
away
from
asset
excited
generated
to
to
a
CMS.
They
might
still
use
a
static
site
generator
and
go
off
like
a
headless,
CMS
and
so
on,
but
they
they
do
have
some
some
considerations
and
things
that
we,
you
know
static,
site,
editor
product.
We
won't
potentially
even
focus
on
it's
part
of
our
product
features
or
just
won't
get
to
in
quite
a
long
time.
So
they've
got
some
specific
needs
that
they
won't
address
immediately.
A
So
it's
an
evaluation
going
on
in
terms
of
what
they
want
to
go
do
going
forward
and
and
as
such,
the
the
separation
of
the
handbook
and
the
marketing
side
is
becoming.
You
know
ever
more
important
for
us
to
make
sure
that
we
that
we
can
have
that
separation
and,
and
also
as
as
Eric
mentioned
last
week.
We
are
we
where
we're
one
check
box
away
from
formally
adopting
the
as
being
the
DRI
for
the
user.
A
B
B
And
on
front
man,
so
I
thought
they
had
forked
middleman
and
just
sort
of
changed
its
strategy
to
be
more
performant
based
on
what
they
had
said
in
the
presentation,
the
conference
presentation
they
gave,
but
it's
a
really
lightweight
reimplementation
of
of
what
middleman
does,
but
basically
from
the
ground
up,
and
so
that
means
it's
a
very
little
bit
of
code.
So
it
was
easy
to
understand
and
if
we
want
to
hack
on
it,
it
seems
like
it
should
be
able
to
you.
B
B
Easily
I
don't
think
as
far
as
the
mono
repo
structure
in
the
extension
we
have
for
that
I
poked
around
at
it
a
little
bit
and
a
hack
Donna
made
a
sample
project
and
that
I
think
will
be
easier
to
do.
It's
mainly
just
a
few
places
in
their
configuration.
We
need
to
make
it
be
able
to
handle
relative
paths
and
multiple
paths
to
build
the
site
for
the
partials
and
the
layouts
and
stuff
like
that.
A
Alright,
thanks
for
that
update
right,
yeah,
I'm
I'm,
quite
keen
to
see
what
performance
of
updates
upgrades
we
can
get
renewed
in
round
one.
But
priority
is
to
get
that
mono
repo
separation
in
place,
and
then
we
can
stop
playing
all
right
onto
the
get
lapdog
stuff.
So
I
I
kind
of
like
alluded
to
it
in
the
intro
and
the
general,
but
strategic
involvement
of
talks
will
will
focus
mainly
around
Vasili
doing
research
from
the
offline
doc
support.
A
So
currently,
if
you
in
get
lab
the
product
new
go
forward,
slash
help
you
you,
the
docs
would
get
let
the
product
gets
rained
out
there.
However,
there's
some
technical
differences
between
how
that
gets
really
the
and
the
talks
to
people
after
the
comm
project
gets
rendered
and
there's
need
to
provide
the
documentation
and
a
better
experience
for
the
documentation
in
offline
environment.
So
so
I
get
environment
and
so
there's
two
considerations.
A
We
either
need
to
kind
of
like
improve
the
experience
of
the
of
the
help
functionality
and
you
know
how
can
we
bring
that
align
with
the
looking
feel
of
the
dock
site?
And
how
can
we
not?
How
can
we
keep
it
dry
so
that
we
don't
have
things
all
over
the
place
or
alternative
things?
We
need
to
actually
package
the
docs
project
as
part
of
the
omnibus
installer,
which
is
a
viable
route,
but
it
brings
a
feeling
a
lot
of
other
considerations
as
well,
so
the
cilium
will
be
doing
some
initial
research.
A
Just
in
terms
of
you
know,
technical
feasibility
and
potential
issues
we
might
run
into,
and
in
else
as
I
mentioned,
we're
looking
to
the
conflict
start
with
some
variable
also
just
doing
research
initially
around
a
variable
strategy
for
the
dock,
so
that
it's
easier
to
change
key
terminologies.
That
might
change
like
you
know
if
they
change
static
side
energy
to
something
else.
You
know
we
could
easily
change
that
with
one
from
a
variable
rather
than
using
having
to
go
and
update
multiple
parts.
D
This
is
a
little
long-winded
for
an
agenda
item,
but
as
13.2
is
wrapping
up
and
we're
starting
13.3
with
a
little
bit
lower
engineering
capacity,
I
did
want
to
call
out
that
13.3
will
also
be
the
end
of
the
quarter.
I
might
get
a
little
anxious
here
and
there
I
might
be
shifting
and
trying
to
do
a
little
bit
of
reprioritization
on
the
fly,
but
I
don't
want
you
all
to.
D
Oh
I
would
appreciate
it
if
you
called
me
out
on
it,
if
it's
disruptive
and
don't
take
it
as
a
as
an
added
level
of
pressure
to
to
ship
more
than
you
should
would
normally
be
able
to
ship.
You
should
take
time
off
when
you
need
it.
You
should
spend
time
with
family.
You
should
have
dinner
and
meals
with
your
family.
If
you
can
and
will
ship
when
we
ship
as
long
as
it's
high
quality,
we
want
to
iterate
on
our
improvements,
I'm
not
going
to
be
upset
if
some,
if
life
gets
in
the
way.
D
So
that's
still
my
stance,
but
as
we
get
into
13.3
check
me
on
an
if
it.
If
it
doesn't
sound
like
that's
how
I'm
behaving-
and
that
said
just
to
go
back
to
what
what
John
was
saying
about
the
marketing
site,
I
wanted
to
clarify
a
little
bit
about,
because
there
they're
doing
these
issues
in
the
open
and
as
they
should
be,
and
it's
great
to
have
a
transparent
view
into
their
decision-making
process
for
the
marketing
site
for
evaluating
a
CMS.
And
actually
it's
not
the
first
time.
They've
evaluated
this.
D
Regardless
of
the
recommendation
we
we
do
have
a
meeting
later
this
week
to
discuss
marketing's
requirements
for
a
CMS
and
why
they
feel
like
they
need
a
CMS.
Obviously
they're.
Probably
it's
probably
clear
that
there
are
some
people
in
the
organization
that
would
be
resistant
to
this
me
personally
and
and
for
our
team
I'm,
supportive
of
whatever
they
need
to
get
their
job
done
efficiently.
D
Our
static
site,
editors,
young,
they
have
pretty
advanced
needs
from
a
marketing
site
and
their
capabilities
might
exceed
what
we're
ready
to
deliver,
or
almost
certainly
will
exceed
what
we're
ready
to
deliver
on
so
I'm.
Taking
this
as
an
opportunity
to
inform
them
where
we're
headed
and
and
generally,
what
kind
of
timeframe
were
talking
about
and
get
valuable
information
about
what
a
Marketing
SIA
the
scale
might
need
from
the
static
site
editor
for
our
future
roadmap,
well
down
the
line.
D
So,
as
you
see
issues-
and
if
you
even
see
me
contributing
to
issues
or
you
see-
docks
being
passed
around
where
we're
evaluating
different
options-
just
know
that
I'm
not
I'm,
gonna,
try
and
come
at
it
from
a
place
where
I'm
not
being
defensive,
about
trying
to
like
hold
on
to
their
business
like
and
make
them
use
the
static
site.
Editor
and
I'm
also
not
trying
to
shift
our
direction
to
meet
specifically
their
needs
either,
which
is
an
important
distinction
as
well.
D
B
A
And
just
in
terms
of
strategic
projects,
the
two
projects
internally
that
are
really
important
to
us
in
our
our
product
vision
is,
is
the
gitlab
handbook
and
the
gate
lapdogs
project.
They
speak
directly
to
the
personas
that
we
we
want
to
target
and
that
we
feel
will
get
the
best
traction
out
of
our
offering
and
and
that's
why
we
have
them
as
categories
for
our
group
as
well.
We
are
we're
not
just
you
know.
A
So
those
are
the
two
projects
internally
that
that's
strategically
important
to
us
and
why
we're
so
involved
in
them
to
drive,
because
by
having
our
editor
dog
food
on
those
two
projects,
we'll
get
a
mains,
valuable
feedback,
the
marketing
site
laser
at
this
stage,
I
think
the
blog
would
would
would
have
probably
been
a
good
one
as
well
and
there's
a
lot
of
kind
of
like
people
who
who
do
sex
I
generated
blogs.
But
that's
in
the
end
of
the
world
either
yeah.
D
Logging
logging
is
definitely
one
we
would
want
to
keep
in
mind,
but
there
is
a
lot
of
considerations
that
go
into
and
a
marketing
page
that
it's
supposed
to
represent
a
multi-billion
dollar
company
that
that
it
might
not
be
conducive
to
a
statically
generated
Satan
in
general.
So
as
they
make
that
decision
I
think
it's
important.
We
keep
that
in
mind
and
help
them
make
their
decision
with
whatever
input
we
can
give
them
feel
free
to
contribute
to
those
issues.
D
B
D
The
I
am
personally,
as
I
said,
before
totally
comfortable
with
them
going
in
this
in
a
direction
that
is
preventing
us
from
from
using
them
as
a
dogfooding
opportunity.
Honestly,
if
they
need
these
things,
we're
just
not
going
to
be
able
to
deliver
and
I.
Don't
want
I,
don't
want
to
force
something
on
them,
but
we'll
see
what
they
are.
How
will
the
decision,
lands
and
I'll
keep
you
all
updated
and
that
issue
I
linked
should
have
ongoing
discussion
as
well.