►
From YouTube: GitLab 13.1 Kickoff - Create:Knowledge
Description
GitLab 13.1 Kick for Create:Knowledge Issues Mentioned:
1) Resolving Design Comments: https://gitlab.com/gitlab-org/gitlab/-/issues/13049/designs
2) Group level wiki MVC 1: https://gitlab.com/groups/gitlab-org/-/epics/2214
A
Hi
there,
my
name
is
Kristen
de
Benko
and
I'm
the
PM
for
the
knowledge
group
in
the
create
stage.
This
is
our
13.1
kickoff.
Our
group
works
on
two
category
level
features
the
wiki
and
design
management
in
13.1.
We
have
one
direction
issue
that
we're
focusing
on
and
it's
an
important
one
in
the
design
view.
Currently,
when
you
make
comments,
you're,
not
able
to
resolve
them
and
get
them
off
of
the
design.
This
is
a
difficulty
when
you're
making
edits
to
a
design.
A
You
upload
a
new
version
and
then
your
comments
are
out
of
date
and
the
comment
pins
actually
don't
apply
anymore.
I'll
actually
show
you
this
here
as
an
example.
So
I
have
this
layout
for
a
blog,
and
you
could
see
here
that
there's
a
comment:
I've
decided
I,
don't
want
the
ads
on
this
blog
post,
so
we
have
to
scrap
that
top
layer.
So
if
I
go
to
my
design
tool,
get
rid
of
the
top
layer,
save
it
and
re-upload
it
to
get
lab.
A
So
now
they're
gone
at
this
point.
I
would
love
to
just
be
able
to
resolve
it,
get
it
off
the
screen,
because
this
pin
number
one
no
longer
applies.
Maybe
we'd
have
to
move
it
to
the
bottom,
so
we
stop
seeing
it
so
in
this
release
we
have
a
solution
and
we'll
look
at
it
here
in
Sigma.
So
there's
two
different
ways:
you
can
resolve
a
dot
design
comment
and
if
we
look
here
so
here's
another
example,
we've
got
one
comment
and
we
want
to
resolve
it.
A
The
first
and
easiest
way
kind
of
like
an
mr
comment
is
you
can
just
click
the
check
box
and
it
goes
down
into
your
resolved
comments
section.
So
it
actually
is
demoted.
It's
no
longer
on
the
design,
but
it
still
exists.
If
you
want
to
scroll
down
and
see
what
it
was
later,
we're
also
capturing
which
version
it
happened
on
which
is
pretty
cool,
and
so
this
one
would
be
like
a
quick
check
mark
get
it
out
of
my
face.
It's
done.
We
also
have
resolving
with
a
comments
similar
to
em
ours
again.
A
A
So
we're
really
excited
about
this
one.
It's
a
fairly
large
issue
overall,
but
it's
the
front-end
and
back-end
team
is
going
to
run
in
parallel
to
get
it
done.
We
wanted
to
get
the
MVC
up
so
that
it
would
be
usable
and
so
towards
the
beginning
of
the
release,
we're
all
going
to
focus
on
this
first
direction
item.
A
We
also
have
the
group
level
wiki
epic,
which
is
chugging
along
there's
five
issues
slated
for
thirteen
one,
so
lots
of
progress
is
coming.
We've
updated
the
projection
to
thirteen
for
right
now
it
looks
like
13
in
this
epoch.
We're
still
figuring
out
what
how
much
we
need
to
test
and
if
we
need
another
release
to
test
group
level
wiki,
but
amazing
progress
happening
there
and
lots
more
coming
in
31.