►
Description
Community Relations Group Conversation (Public Livestream)
A
Seon-Ah
I
guess
we're
good
okay.
So
thanks
everyone
and
welcome
to
the
treaty
relations
conversation
Manila.
There
is
there
of
community
relations
and
if
you,
if
you
have
any
questions
regarding
any
other
slides,
feel
free
to
to
to
let
us
know
we
can
solve
it
to
more
detail.
Otherwise
we're
happy
to
dive
into
them
into
the
questions.
A
30
some
changes
in
the
team.
That's
the
that's
currently
line
up.
One
of
our
community
advocates
Georgia
is
going
to
be
listening
to
the
STR
team
in
in
November,
and
we
could
to
new
community
advocates
starting
one
next
week,
the
28th
October
and
another
one
on
the
18th
of
November,
we're
close
to
get
over
the
last
stages
of
such
program
manager
and
filling
in
the
position
for
boots
of
dimension
and
application
program
manager.
But
but
we're
not
there
yet.
C
If
there
are
any
mentions
of,
you
live
across
social
that
still
need
to
be
monitored
on
Twitter
hacker
news,
reddit
or
wherever,
and
then
we
clear
the
ones
that
are
that
are
currently
in
the
queue
and
then
yeah
periodically
make
sure
to
check
back
at
some
desk
to
see
if
there
are
any
more
that
need
to
be
responded
to
and
that's
kind
of
our
baseline
job,
and
then
we
also
run
some
separate
programs
like
the
edu
and
OSS
programs
kind
of
on
the
side,
so
yeah
I,
guess
that
hopeful.
Is
that
answer
your
question?
C
D
So
so
I'm
on
the
community
team,
my
name
is
John
Coghlan
I.
Imagine
the
meetups
and
heroes
programs,
but
I
have
a
question.
Another
question
for
Emily
Emily
I'm
wondering
like
how
do
you
kind
of
like
manage
your
self-care,
because
I
imagine
that
your
role
can
be
pretty
tough
with
when
they're,
like
these
periods
of
time,
where
there's
negative
responses
to
posts
and
things
like
how
do
you
manage
through
those
situations?
E
F
I
mean
think
I
guess
I'll.
Take
that
question
how
many
thanks
for
the
question
Stephen
so
I
mean
after
I
mean
even
before
they
move
to
the
single
codebase.
That's
something
that
we
were
concerned
about
me.
First
of
all,
like
I,
mean
I.
Think
for
a
long
time,
people
were
used
to
finding
issues,
for
example
in
C
e
and
that
the
whole
like
a
project
sort
of
went
away
so
wanted
to
see
how
many
people
were
following.
F
That
was
one
of
the
questions
that
came
up
and
another
contributor
jumped
in
and
reminded
them
of
the
move
that
we
made
their
single
codebase.
So
I
think
awareness
was
one
of
them,
so
I
mean
that
I
think
we
made
a
lot
of
moves,
including
making
announcements
on
on.
Mr.
As
for
people
who
submitted
Mr,
Shaun,
C
II,
but
I,
don't
think
the
word
got
out
to
everybody
so
just
but
I
think
we're
on
the
path
of
recovery.
F
E
A
Some
person
how
to
contribute
to
see
or
to
a
single
code
repository
the
other
thing
that
happened
is
that
we
couldn't
move
the
DeMars
request
automatically
onto
the
new
today
single
code
repository.
So
quite
a
few
were,
were
closed
I.
He
was
over
over
100
and
Ray
has
been
following
up
with
with
each
of
those
contributors
individually
to
get
them
resubmit
it
on
to
the
new
project
and
that's
been
slowing,
contains
a
bit
as
well
capture.
E
G
Sure,
before
I
joined
gitlab,
it
was
hard
to
figure
out
how
to
find
the
new
issue.
It
was
a
real
goose
chase
for
me
and
then
I
just
well.
Is
it
dev
up
stays
with
some
other
get
lab?
Folks
I
saw
someone
clicked
the
closed
tag
and
it
took
them
to
the
new
issue.
It's
like
wow,
that's
really
awesome,
but
I.
Don't
think
it's
easy
understand
that
when
you
just
encounter
an
issue,
that's
been
closed
and
moved
to
the
new
code
base
and
I
might
be
missing
it.
G
F
I
mean
I
think
that
was
some
of
the
discussions
that
happened
after
the
move
to
single
codebase
like
there
wasn't
a
reference
to
the
new
issue
in
in
in
I
mean
it
new,
get
lab
project
or
what
used
to
be
called
EE
right.
So
people
had
to
go
like
search
for
it
by
type
retyping,
the
title
so
that
wasn't
that
wasn't
very
elegant
and
that
was
I.
F
Think
one
of
our
learnings
from
the
single
codebase
move,
so
that
yeah
we
did
hear
complaints
from
people
about
I
couldn't
find
I
couldn't
find
where
the
new
issue
went.
To
so
I
mean
that's
a
very
good
point,
so
it's
not
necessarily
obvious
that
it
was
Auto
closed
because
of
the
single
codebase
or
somebody
actually
closed
the
issue
because
it
was
not,
but
is.
F
H
D
H
H
G
It's
just
not
easy
when
you
go
to
an
individual
issue
to
notice
that
and
I,
don't
think
it's
in
each
issue
or
is
it
documented
in
each
issue
and
then
Google
Google
is
indexing
the
old
ones
much
higher
I,
probably
because
of
past
activity
on
them.
So
when
you
do
search
it,
it
can
be
pretty
challenging
to
make
your
way
there
from
landing
on
an
individual
issue
because
I
don't
know
about
others,
but
for
myself
a
lot
of
times
how
I
found
my
old
issues
was
Google
in
the
first
place.
I
So
Mac
what
we
could
do
like
there's
a
robot
there's
the
robot.
That
has
like
a
super
long
message
about
that
it
got
moved
and
everything
else.
It
would
be
great
if
we
edit
that
message
and
say
at
the
top
move
to
and
then
a
URL
and
at
the
bottom
move
to
and
then
a
URL
and
it
showed
that
actual
URL
and
make
it
clickable
so
that
people
don't
have
to
kind
of
process
that
enormous
message.
I
I
I
B
B
B
B
J
J
J
F
Yeah,
thanks
for
the
question,
I
mean
I,
think
it
depends
on
a
case-by-case
basis.
I
mean
I.
Could
that's
something?
I
could
do
a
better
job
of
in
terms
of
follow-up,
but
I
mean
certain
em.
Ours
that
have
not
been
active,
God
gets
tagged,
and
then
we
get
a
all
the
EMR
coaches,
including
myself
and
David.
We
get
out,
we
get
a
report,
so
we
try
to
follow
up
on
it.
I
mean
what
I
typically
try
to
do
is
after
a
couple
of
follow.