►
Description
- Progress report on the Awareness Widget implementation
- Outlook: The roadmap to fully collaborative text editing
A
Folks
and
welcome
to
another
update
on
realtime
editing
of
issue
descriptions,
and
this
week
I
am
going
to
give
you
a
progress
report
and
an
outlook
for
what's
coming
next.
The
awareness
widget
is
currently
close
to
being
reviewed.
The
last
mr
that
is
missing
is
the
one
that
adds
the
awareness
widget
actually
to
our
front
end
and
so
that
it
becomes
visible
in
the
issue
sidebar.
A
After
this,
mr
has
shipped
we
or
I
am
actually
going
to
pivot
a
bit.
So
the
real
goal
here
is
to
have
real-time
editing
of
issue.
Descriptions
and
awareness
is
a
part
of
that,
but
it's
not
the
the
the
ultimate
goal,
and
one
thing
that
we
that
I
haven't
worked
on
so
far
is
producing
a
reliable
change
set
from
the
text.
A
Editing
like
from
when
a
user
is
editing
text
in
in
the
issue
description
text
area,
we
do
not
have
the
luxury
of
proper
bindings
for
those
text
area
like
there
is
no
ygs
text
area
binding.
That
is
really
really
good.
So
we
need
to
look
into
that
and
ideally
we
can
get
just
changes
when
a
user
types.
So
you
know
I
start
typing
in
a
blank
document,
so
I
start
inserting
some
text
at
offset
zero
and
another
user.
A
We
previously
have
shipped
and
built
and
shipped
by
rubygem
by
ruby,
gets
a
companion
in
the
form
of
ryrubi
redis.
This
helps
us
to
distribute
the
initial
document
state
to
every
client
in
a
session.
It's
a
simplification
of
the
of
the
problem
we
have,
because,
usually
you
would
just
if
you
don't
have
a
server
for
orchestration.
You
just
need
to
find
another
client.
The
client
sends
you
the
current
update
that
might
not
be
the
latest
update,
etc.
A
Both
jams
need
to
be
reliable
and
need
to
meet
the
quality
criteria
that
we
have
for
gitlab
champs,
and
we
also
need
to
make
sure
that
they
support
all
the
operating
systems
and
cpu
architectures
that
we
want.
The
reason
is
that
why
ruby
and
ruby
redis
rely
on
the
native
extension
and
those
the
negative
extension
is
not
written
in
c,
but
rust
and
rust
support
for
bundler
the
tool
that
we
that
we
use
when
we
install
champs
jams
is
in
a
ba,
is
in
beta.
A
So,
there's
not
really
an
official
support
yet
for
rust
extensions,
and
luckily
we
have,
with
the
help
of
wrecking
compiler,
we
can
work
a
rate
compiler.
We
can.
We
can
work
around
that
a
bit
but
yeah.
We
need
to
make
sure
that
this
is
not
causing
any.
You
know
frustrations
frictions
when,
when
we
roll
this
out
and
when
our
customers
install
the
next
gitlab
version
where
this
is,
this
is
going
to
be
part
of
yeah.
What
else
is
missing?
We
also
want
to
develop.
A
We
need
to
develop
a
shared
cursor
model,
so
this
is
on
top
of
the
awareness
work.
This
helps
us
to,
and
you
can
see
that
on
the
on
the
on
the
little
snippet
here
kind
of
helps
like
helps
us
to
see
like
who
is
editing
which
part
of
the
text.
This
is
super
helpful
and
it's
it's
a
nice
compromise
of
not
showing
the
mouse
cursor
of
everyone
moving
around
the
screen,
but
still
having
like
a
good
grasp
of
what
is
going
on
and
yeah.