►
Description
Draft MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/92925
Jobs to be done: https://gitlab.com/groups/gitlab-org/incubation-engineering/real-time-editing/-/epics/3
REID Handbook page: https://about.gitlab.com/handbook/engineering/incubation/real-time-collaboration/
A
Hey
folks
and
welcome
to
another
update
to
of
real
time
editing
of
issue
descriptions
this
week
is
going
to
be
a
short
one
again,
because
I
was
mostly
focusing
on
shipping
the
stuff
that
announced
two
weeks
ago.
The
awareness
ux
and
the
uranus
feature
in
itself.
This
is
a
part
of
this
bigger
issue
on
how
to
colla
how
to
start
a
collaborative
editing
session
between
two
or
more
users
and
it's.
Finally,
we
finally
made
it
to
the
last
probably
the
last
merge
request
before
this
feature
can
ships
this
like.
A
We
have
pivoted
again
to
put
it
into
the
sidebar,
because
it
seems
to
be
just
the
best
place
and
or
the
easiest
way
to
edit
there's
a
lot
of
complexity,
if
we
try
to
add
it
to
the
breadcrumbs
menu
or
to
the
test
to
the
title
of
the
of
the
issue
like
it
just
looks
different
every
time
you
scroll
and
the
breadcrumbs
movie
is
hidden
if
you
scroll
down
so
there's
no
super
easy
way
forward,
and
the
sidebar
is
just
a
very
it's
a
very
good
place.
To
put
it.
A
A
There's
a
second
like
just
ask
before
x
for
credentials
like
I've
created
additional
uses
in
order
to
test
this
out
after
this
a
ship
we
have
like
delayed
the
foundation
for
creating
collaborative
editing
sessions,
so
we
ultimately
want
to
go
into
the
text
editing.
The
text
editing
feature
like
to
to
roll
this
out.
A
This
might
change
a
bit,
but
in
general
we
want
to
see
who
we
are
collaborating
with
and
we
want
to
be
actually
able
to
collaborate.
So
those
are
the
two
jobs
to
be
done.
There's
a
bit
of
more
details
here.
The
issue
is
linked
on
in
the
video
description
below
so
yeah.
Just
let
me
know
what
you
think.
A
I
also
have
updated
the
handbook
page,
a
fair
bit
with
what's
currently
going
on,
because
the
last
update
to
the
sample
page
was
a
while
ago
and,
as
you
can
probably
see,
there's
another
jam
that
was
added
here.
It's
the
companion
for
ryrubi
on
the
server
that
allows
us
to
persist,
changes
temporarily
in
redis.
This
makes
a
lot
of
things
easier
for
us,
especially
when
new
users
join
a
session.
A
We
can
easily
restore
a
document
state
for
them
without
interacting
with
any
other
clients
which
just
helps
a
lot
with
the
orchestration
of
collaborative
collaborative
sessions.
I've
added
the
awareness
as
a
specific
thing
that
is
being
worked
on,
and
you
know
starting
next
week.
We
can
consider
it
in
a
review
process
and
not
in
the
build
process
anymore
and
yeah.
A
I've
already
started
to
look
into
the
editor
landscape,
so
this
is
by
far
the
most
interesting
thing
I'm
currently
working
on
in
particular,
because
it's
not
trivial
editors
might
or
might
not
support
crdts
out
of
the
box
like
pros,
mirror
code
mirror
or
monaco.
They
all
have
ygs
bindings,
but
they
might
have
very
different
structure
and
thanks
to
enrique,
which
I
had
a
wonderful
chat
with
this
week,
we
think
we
have
a
way
forward.
A
The
last
thing
is,
and
it's
about
those
two
champs
again
in
order
to
get
them
into
the
into
the
gitlab
code
base.
We
want
to
make
sure
that
they
meet
the
requirements
for
a
security
and
a
quality
perspective
in
particular,
because
they
include
native
extensions
and
native
extensions.
Are
those
native
extensions
are
built
in
rust
and
we
can't
just
like
simply
port
them
to
c,
which
is
still
the
standard
for
native
extensions
and
ruby.