►
Description
This meeting reviews the new GitLab Blog infrastructure, deployment strategy, timelines, and follow up task with the content team.
https://gitlab.com/gitlab-com/blog-gitlab-com
B
B
Up
at
the
top,
that's
the
link
to
the
repo
and
just
a
general
summary
is
the
repo
it
still
uses
middleman
and
essentially
it's
just
a
Content
repo
that
includes
just
the
blog
posts
in
the
blog
post
images.
Everything
else
is
copied
over
from
the
dub-dub-dub
repo
during
the
build
process
that
goes
into
building
the
rest
of
the
blog
parts.
So
that
means
anything
from
my
page
layout
design
JavaScript.
All
of
that
is
still
gonna
happen
in
the
dub-dub-dub
repo.
A
B
So
that
is
going
to
happen.
You
can
see
in
that
demo.
Repo
I've
done
an
initial
sync
of
the
history
and
I
did
that
last
week,
so
it
isn't
up
to
date
with
all
of
the
stuff
you've
done.
Since
then,
the
URLs
are
gonna
remain
unchanged.
So
there's
no
URL
change
content
repository
middleman,
so
that's
the
first
part.
B
A
If
it's
on
this
Sunday
different
December
1st,
like
we
don't
we
don't
have
early
publish
over
the
weekends
as
some
it's
possible,
but
some
people
within
gitlab
choose
to
work
on
posts
of
their
own
volition
over
weekends.
You
know
just
like
sometimes
developers
they're
working
on
a
side
project
and
they
might
be
writing
about
it,
and
is
that
something
that
would
affect
it
or
is
it's
just
like
publishing
and
like
editing
existing
posts,
yeah.
A
A
B
B
A
So
I
I
mean
there's
a
chunk
like
I
I
will
be
back
in
London
I
I
can
always
if
there's
something
scheduled
for
that
day.
I
can
just
publish
it
in
my
morning
and
then
you
then
have
the
rest
of
the
day
up
for
those
time
zones,
and
then
we
just
need
to
communicate
like
that.
There's
a
blackout
on
publishing
to
the
blog
for
the
rest
of
that
day
and
people
can
just
wait.
Okay,.
B
B
A
C
A
Currently
have
an
issue
boards
in
the
wwe.com
project
because
because
the
blog
posts
are
published
to
their
projects
or
within
that
project
or
that
works
that
that's
that's
why
those
issues
live
in
that
project
because
they
are
at
request
you
create,
is
associated,
but
that
issue
it's
closed
automatically
like
I'm
I'm
open
to
adjusting
that
workflow
to
accommodate
this
move,
but
I'm
just
not
sure
how
it's
impacted.
So
would
we
want
to
create
our
issues
in
this
project
now
or
is
it
a
separate.
C
C
B
C
A
I
think
we've
done
this
before
you
know
there
used
to
be
a
separate
project
for
blog
posts.
It
was
still
connecting
you
know.
We
still
published
using
the
the
main
website
repo,
but
we
used
to
have
a
separate
project
and
I.
Think
at
one
point:
Erica,
you
and
I
just
migrated
them
all
over
manually
that
there
may
be
a
simpler
way
of
doing
that.
Just
using
the
label.
I
want.
C
B
C
B
B
So
if
I
think
I
in
that
issue
have
targeted
the
page,
that's
going
to
need
thorough
updating,
but
if
you
guys
have
any
more
information
as
to
where
documentation
is
going
to
need
to
be
updated
as
to
where
you
edit
and
create
blog
posts.
Please
put
in
that
issue
so
that
we
can
make
sure
we
get
the
handbook
updated
accordingly.
E
A
Just
added
the
question
at
the
bottom
I
expect:
we
need
to
clone
this
repository
now,
where
and
I
guess.
If
you're
wanting
to
make
handbook
updates,
you
then
need
to
switch
between
those
two
repositories
if
you're
editing
locally
yeah
yeah,
so
we
may
need
some
help
with
that.
Just
like
I
haven't
cloned
the
website
projects
in
three
years.
Someone
help
me
do
it
there.
The
instructions
makes
us
somewhere
in
the
handbook,
but
I
think
yes,
the
three
of
us
will
need
to
get
that
way.
I.
B
So
I
followed
the
same
strategy
that
the
docs
site
uses
where
they
clone
multiple
projects
into
a
single
directory
and
create
symlinks.
So
for
common
resources,
for
example,
this
would
be
like
your
layouts
and
your
includes
you're
still
pulling
from
the
dub-dub-dub
repo.
So
there's
a
single
source
of
truth,
but
in
order
to
run
the
blog
you're
going
to
need
to
have
all
three
pose
in
the
same
directory,
so.
B
D
Have
a
quick
question
and
I
can
write
it
down
so
Val
and
I
have
both
been
having
trouble
with
our
local
host
and
previewing
the
website,
and
we
met
with
William
chia
to
try
and
fix
it
and
like
since
that
meeting
Val
an
update
for
you.
It's
completely
broken
and
no
longer
works.
It
of
course
cooperated
in
that
meeting
what
we
were
trying
to
troubleshoot.
But
now
it's
still
like
I
tried
to.
C
E
D
D
E
C
So
maybe
what
we
need
to
do,
because
I
mean
I,
haven't
worked
closely
for
a
while
honestly
I
need
to
update
all
my
stuff.
Maybe
we
can
have
a
session
where
we
just
all
do
it
together
and
we
all
just
set
it
up
the
same
way,
which
is
the
way
the
handbook
I
think.
Ok,
that's
to
do
it
and
then
nobody's
on
a
special
like
I
said
just
on
so
advanced
that
you're
running
enjoy.
B
Yeah
and
I
want
to
I
need
to
find
that
place
in
the
handbook
where
that
documentation
is
because
I've
been
using
Cabrini's
that
are
in
the
repo
to
make
sure
that
that
documentation
is
synced
based
off
of
that
I
think
they
should
move
the
deployment
to
the
end
of
December,
because
I
don't
want
to
I
know
no.
It's
fine
that,
because
I
want
to
make
sure
that
you
guys
can
still
do
your
work
in
that
I.
Don't
totally
blow
everything
up
well,.
C
B
B
A
A
I
was
wondering
about
permissions
for
merging
to
this
project.
Does
this
mean
that
we
stopped
like
afresh
with
just
granting
individuals
merge
permissions?
Okay,
that's
like
we'll
just
need
Erika.
Maybe
you
and
I
just
need
to
talk
through
kind
of
who
needs
access
to
that,
so
that
we,
where
would
like
controlling,
but
also
not
blocking
people
as
well
yeah.
C
This
is
actually
a
really
good
opportunity
to
think
through
that
and
I
mean
and
then
you
like,
unfiltered,
we
don't
want
to
block
people
from
be
able
to
being
able
to
continue
to
do
that,
but
maybe
we
have
like
unfiltered
mergers
or
something
like
that
yeah.
Well,
let's
talk
about
it.
I
I
personally
am
in
favor,
though
of
not
just
giving
blanket
merge
access
to
everybody.
C
B
B
B
C
B
A
B
B
Around
mm-hmm
Alejandra
is
gonna,
help
me
with
deployment,
so
he
weren't
something
infrastructure
team
and
is
helped
with
setting
up
the
review
apps
and
said
we'll
help
set
setting
up
staging
and
it
actually
deploying
to
the
real
server.
So
I
need
to
work
with
him
to
make
sure
he's
around,
for
it
also.