►
From YouTube: CHAOSS DEI Working Group 2/2/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
A
All
right,
well
I'll
share
my
screen.
Let's
see
here
we
go
and
today
I
think
it's
a
fairly
light.
B
A
Today
and
we've
been
chatting
a
little
bit
so
we
can
bring
those
up.
I
would
like
to
take
a
l
and
justin.
You
can
also
just
kind
of
stop
me
too,
as
I
guess,
if
we're
looking
at
issues
in
pr's
and
you
think
that
these
things
kind
of
align
with
what
you've
been
doing
just
go
ahead,
and
you
know
chime
in
cool,
so
issues.
A
Well,
I
think
justin.
You
can
comment
right
away
because
I
see
a
bunch
of
things.
D
Yep,
thank
you
or,
if
you
want,
maybe
I
could
just
share.
A
C
D
Yes,
perfect,
so
I'll
walk
through
the
the
labeling
system
that
I
that
I
set
up
here
and
then
look
at
the
project
board
after
that,
so
I
adapted
this
labeling
system
that
I've
used
in
other
open
source
projects
to
try
to
make
it
easier
to
both
filter
and
also
just
add
a
glance
understand
what
all
the
different
issues
are
and
what
kind
of
work
that
they're
focused
in.
So
if
you
go
to
the
in
the
issues,
tab
go
to
the
labels.
D
You'll
see
here,
I
added
some
that
I
just
updated
and
some
that
I've
added
in
I
have
a
prefix
system.
I
don't
know
this
is
over
complicating,
so
I'm
really
going
to
appreciate
your
feedback
on
here,
but
so
I
have
split
these
up
into
a
couple:
different
statuses.
So
there's
these
ones.
That
begin.
Actually,
I
think.
B
D
This
written
somewhere,
so
maybe
I
can
just
walk
through
how
I've
done
it
label
conventions,
that's
it
yeah,
so
the
the
ones
that
begin.
We
don't
have
that,
but
the
ones
that
begin
with
an
I.
These
are
what
I
call
inclusion
labels,
so
they're
focused
on
trying
to
make
it
easier
to
bring
people
in
or
or
give
people
a
chance
to
get
involved.
Help
wanted
and
good
first
issue
aren't
anything
new.
D
Those
have
been
around
already,
but
I
added
one
around
contributor
experience.
So
if
we
have
an
issue
or
something
that's
focused
on
how
people
actually
engage
and
interact
with
our
working
group,
that's
what
this
one
is
more
focused
on.
So
thinking
of
things
like
the
issue
templates-
and
I
can
probably
even
look
at
all
the
issues
that
are
tagged
that
way
now
yeah.
So,
like
the
issue
templates,
we
were
talking
about
the
inclusive
naming
checklist
and
then
the
repository
cleanup.
D
So
that's
what
all
these
ones
that
are
prefixed
with
the
I
mean
the
ones
that
are
prefixed
with
a
t
indicates
the
different
type
that
they
are
so
for
these
I
just
have
three:
maybe
the
bug
one
isn't
as
applicable
for
what
we're
doing
since
we're
not
doing
a
ton
of
software
work,
but
I've
found
having
this
improvement
or
a
new
change
label
can
be
helpful
in
understanding.
Like
is
this
a
new
idea?
D
D
Is
it
improving
a
metric
we've
already
created
versus
creating
a
new
one,
so
just
kind
of
giving
a
quick,
quick,
visual
representation
about
whether
this
is
introducing
new
work
into
the
project
or
we're
revisiting
older
or
something
that
already
is
in
our
repository?
D
So
that's
what
the
t
is
for
type
and
then
I
have
this
x
x
just
for
close
status.
So
if
you're
closing
an
issue
or
a
pull
request,
you
can
just
for
historical
purposes.
You
can
just
assign
it
one
of
these
issues
that
has
an
x
on.
D
Or
it's
invalid
or
where
we
decide
that
we're
not
going
to
work
on
it,
so
just
only
only
these
are
really
only
useful
if
you're
closing
something
out
as
incomplete,
just
to
give
some
context
of
why
this
was
being
closed.
If
we
aren't
working
on
it,
so
it's
a
quick
visual
there,
and
so
those
are
the
x's.
A
D
And
last,
and
finally,
are
these
question
mark
ones
which
I
try
to
mean
is
that
you
require
some
kind
of
more
information
and
might
need
someone
who's
a
little
more
experienced
to
move
that
issue
forward.
So
here
there's
a
blocked.
I
added
a
blocked
one.
So
if
we're
stuck
on
something
or
we're
waiting
on
someone
else
or
another
working
group,
we
can
just
quickly
label
that
as
block,
so
we
know
that
it's
kind
of
frozen
for
a
little
bit
the
question,
one
that
was
actually
already
here.
I
just
added
the
prefix.
D
You
know
if
we
have
something
we
need
more
information
from
somebody
or
there's
a
question
that
needs
to
be
answered,
a
quick
way
to
flag
it,
and
this
needs
triage
one.
We
won't
be
doing
as
much
with
it,
but
on
those
issue
templates
that
I
that
I
proposed
in
the
pull
request
whenever
someone
will
create
an
issue
from
those
issue,
templates
it'll
automatically
give
it
the
needs,
needs
triage.
D
D
Look
at
it
yeah.
So
as
soon
as
it's
been
reviewed
by
a
human,
you
can
just
drop
the
label
if
it
looks
right.
So
the
idea
is,
it's
just
a
reminder
that
hey
someone
needs
to
look
at
this
really
quick
and
just
either
do
a
reply
or
update
the
metadata
whatever
it
is,
or
just
make
sure
the
issue
makes
sense.
A
A
Yep,
I
do
I
really
like
the
the
prefixes,
so
I
think
that's
nice
and
then
is
there
any
way
that
we
could
take
what
you
were
showing
from
the
was
it
the
unicef
site
in
terms
of
what
the
prefixes
are
like,
that
the
label
convention
text
and
get
it
into
the
repository
somehow.
D
Yeah,
I
could
just
actually
in
retrospect
I
probably
should
have
added
that
into
a
pull
request.
Add
some
documentation
there,
okay
yeah!
I
could
put
this
into
the
readme.
Just
add
it
somewhere.
I
don't
think
we
have
like
explicit
contribution
guidelines.
A
Would
make
sense
because
then
we
can,
and
actually
you
can
do
it
yeah-
is
that
contributing
is
that
this
is
broad.
C
D
Same
to
that
end,
a
feature
that
I
recently
discovered
that.
D
So
you
can
have
a
dot
github
repository
in
an
organization
nope.
This
isn't
the
one
I
mean
the
dot
github
folder,
where
you
keep
the
templates.
D
Guidelines
like
that,
and
this
gets
reflected
across
all
the
repositories
unless
they're
added
or
unless
they
override
the
ones
that
are
in
this
dot
and
github
folder
so
like.
If
I
go
to
another
repo
for
any
of
this,
it's
like
a
hot
agency.
D
They
just
have
ci
pieces
here.
They
don't
have
control,
they
do.
E
D
Didn't
either
so
it
was.
It
was
a
cool
little
feature
for
me
to
discover
too
I'm
just
trying
to
look
at
one
of
their
old
repos
just
to
see
if,
like.
A
D
Yep
so
like
you'll
see
here,
this
is
a
literally
just
an
empty
repository.
There's
nothing
here.
But
if
I
go
to
open
an
issue,
it
says:
hey,
there's
contributing
guidelines
and
we
have
a
code
of
conduct
and
you
can
see
if
you
look
in
the
bottom
left
corner
there
or
if
I
click
it.
It'll
take
me
to
the
dot
github
folder,
and
here
we
are
so
that
could
be
one
way
that
we
approach
that
as
well
just
thinking
about
keeping
things
dry
or
not
repeating
ourselves
too
much.
D
D
D
Makes
the
most
sense
here
if
we
want
to
make
it
in
the
generic
one
or
just
let
me
know
if
you
want
me
to
add
this
into
the
readme
or
something
too
I'd
be
happy
to
do
a
quick
request
for
that.
I
have.
A
A
question
for
you
on
this.github-
and
you
may
or
may
not
know
the
answer,
but
if,
if
I
add
the
dot,
github
folder
and
I
add
the
just
the
contributing
markdown,
the
contributing
md
to
that
folder
or
to
that
repo-
is
there
anything
that
the
other
repositories
need
to
do
to
recognize.
That.
D
I
I
don't
think
so.
I
think
it
will
just
happen
by
default.
You
know,
just
like
I
went
and
looked
at
this
blank
repo
that
was
probably
created
a
long
time.
Oh
yeah.
If
I
look
at
the
history,
this
repo
was
created
after
this
one
and
it
just
picked
it
up.
When
I
go
to
when
I
went
to
open
an
issue,
it
was
just
okay
right
there.
So.
A
D
D
But
I'm
not
sure
on
the
repo
home
page
if
it
shows
it,
but
you
could
just
put
a
link
in
the
readme
too.
Like
that's
what
I've
done
with
a
lot
of
projects
and
you
read
me
say:
hey.
A
D
D
Again
same
thing,
you
just
put
a
readme
in
that
dot:
github
folder
and
it'll
pop
up
right
at
the
top
of
your
your
github
org.
A
E
With
me,
yeah
yeah,
my
because,
like
yeah,
I
just
I
just
went
to
one
of
mine
and
did
it
and
it
just
put
up
this
magical.
This
is
a
unique
special
repository
that
you
can
do
all
these
things
with.
So
I
I
think
it's
going
to
be
as
straightforward
as
justin
describes,
right
on
cool.
A
A
It
okay,
so
I
like
these
labels
and
how
is
the
easiest
way
to
kind
of
propagate
this
to
the
other
working
groups
just
simply
manually,
go
into
those
working
groups
and
follow
the
approach
that
you
used
in
dei.
D
D
A
Do
that?
I'm?
Okay
with
that,
and
in
fact
I
kind
of
prefer
that
in
this
case,
because
we
have
the,
as
you
pointed
out
like
with
the
label
of
bug
like
we
have
the
working
groups
that
work
on
the
design
of
metrics,
and
then
we
have
the
software
groups
that
focus
obviously
on
the
development
of
software,
and
I
wouldn't
want
to
assume
that
say.
The
folks
that
are
working
on
gremore,
lab
or
auger
would
necessarily
benefit
from
this
label
approach.
E
D
E
D
Yeah
that
was
one
I
I
found
that
one
to
be
really
helpful,
especially
when
you
have
a
lot
of
those
issues
coming
in.
It
just
gives
you
that
reminder.
It's
like
hey
someone
actually
looked
at
this
already
or
it's
a
help.
It
can
be
a
helpful
reminder
there.
I
found
so.
D
No
all
good,
so
this
yeah
the
last
piece
here
just
pretty
quick,
so
we
already
had
the
project
board
it
was.
It
was
dni
issues
I
just
renamed
it
to
project
or
working
group
project
board.
I
restructured
things
a
little
bit
so
now
we
have
the
metric
ideas,
column,
which
was
already
there,
but
I
went
through
all
of
our
issues
and
I
added
all
of
the
metric
idea
issues
into
this
column.
D
So
we
have
looks
like
we
have
12
issues
that
are
on
the
table
for
metric
ideas,
and
then
I
sell
like
six
different
things,
so
I
made
a
new
column
for
things
that
are
more
just
working
group
tasks
or
just
general
to-do's
that
we
should
keep
up
with
or
look
at
so
that
I
found
six
different
issues
that
seem
to
fit
into
that
one
and
then
there's
some
automation
in
place.
D
So
when
there's
a
pull
request
that
gets
opened,
it
automatically
goes
into
this
in
progress
column
and
when
an
issue
or
pull
request
gets
closed.
It'll
be
moved
into
this
completed
column,
so
it
helps
keep
things
tidy
and
will
help
out
with
some
of
the
triage
work.
So
someone
doesn't
have
to
always
move
things
from
in
progress
to
completed.
We
just
have
to
do
that
for
issues.
I
guess
when
an
issue
is
like,
if
we
want
to
show
it
as
in
progress,
you
just
have
to
drag
it
over
and
drop
it
there
or.
D
Alternatively,
another
thing:
that's
kind
of
an
easier
way
to
do.
It
is
if
you're,
looking
at
the
issue
directly
and
you
have
the
project
board
tagged,
you
can
also
just
click
on
this
little
drop
down
and
boom.
You
can
choose
any
of
the
columns
that
you
want
to
put
that
that
github
issue
into
that's
cool.
So
that's
another
kind
of
shortcut
of
how
to
do
that
too.
A
D
That
is
what
I
was
thinking
too.
Okay.
This
is
kind
of
like
a
especially
if
we
wanted
to
like
really
do
a
deep
dive
on
metrics,
then
hey,
here's,
all
our
metrics
or
if
we
have
one
that's
in
progress
that
we
want
to
follow
up
on
easy
to
see
same
with
the
different
tasks.
So
that
was
my
thinking
too,
is
that
this
might
be
a
better
entry
point
for
kind
of
driving.
The
working
group
discussion
around
the
issues.
A
Right
so
like
when
we
return
to
issues
the
way
that
we
historically
have
returned
to
issues
or
prs.
This
would
enable
us
to
say
listen
in
this
meeting,
we're
not
going
to
be
looking
at
metric
ideas,
so
we
just
don't
even
care
about
that
column.
What
we
need
to
do
is
kind
of
address
our
to-do's
that
are
outstanding.
A
D
A
Cool
that's
super
cool.
I
will
probably
bring
this
up
also
as
a
the
way
to
think
about
work
in
the
the
different,
at
least
for
this
part,
for
the
different
metrics
yeah
for
sure.
E
D
A
That
probably
would
be
helpful.
It's
that
tuesday
meeting
you
know
the
one
I'm
talking
about
tuesday
at
11.
Am
us
central.
E
D
I
have
to
do
a
lot
of
that
time,
zone
math
so
yeah,
so
that
should
work
for
for
next
week
on
the
8th,
I
should
be
able
to
drop
right
in
there
for.
A
D
A
A
D
So
I
just
put
two
issue
templates
together.
So
whenever
someone
goes
to
open
a
new
issue
on
the
repo,
they
would
see
they'd
be
presented
with
two
options.
They
could
either
propose
a
new
metric
or,
basically
anything,
that's
not
a
metric.
D
So
the
metric
one
is,
I
really
looked
at
the
the
template,
the
the
markdown
template
that
we
have
for
new
metrics
as
a
reference
to
try
to
frame
like
what
kinds
of
things
can
we
ask
people
up
front
that
might
make
it
easier
for
the
working
group
to
review
when
we
go
and
actually
look
at
the
metric,
and
it
also
like
I
tried
to
prompt
the
the
person
who's
opening
the
issue
about
hey.
D
D
So
I
thought
that
would
be
something
a
little
more
helpful
when
someone
comes
with
an
idea
that
will
help
us
kind
of
discuss
it
and
work
through
it
and
figure
out
next
steps
for
for
working
on
the
metric,
and
then
the
other
template
is
one
that
it's
it's
based
on,
like
a
more
of
a
personal
way
that
I
I
frame
issues
it's
with
this
sbdo
framework.
D
So
it's
that
stands
for
summary,
background
details
and
outcome,
so
it's
just
a
kind
of
a
easier
way
to
frame
like
so
the
summary
you
know:
what's
one
sentence
describing
one
sentence,
what
this
task
or
idea
is
the
background
like
what
do
we
need
to
understand
for
this
to
make
sense
or
why
this
should
be
done?
D
D
I've
had
that
as
a
really
helpful
way
for
me
to
try
to
frame
like
new
work,
requests
and
tasks,
but
I
I
disabled
blank
issues
which
might
be
a
controversial
one,
so
one
that
might
be
helpful
to
discuss
here
is
if
we
want
to
keep
the
option
open
for
someone
just
to
have
a
no
template
issue,
so
there's
a
total
blank
slate
for
them.
Of
course,
you
can
always
just
copy
paste.
D
You
know
right
control,
a
delete,
the
template,
but
those
are
the
two,
the
two
templates
that
I
put
together
to
think
that
might
help
for
us.
When
we
go
to
the
issue
tracker,
it's
just
a
way
to
help
organize
the
feedback
and
kind
of
structure
it
a
little
bit
more.
D
I'm
definitely
curious
to
get
your
feedback
oh
and
to
your
comment,
matt
just
I'll
share
here
we
could
look
at
creating
a
template
for
all
the
working
groups
and
maybe
that
could
fit
into
this.github
folder
as
well,
that
a
working
group
could
just
take
that
and
and
copy
it
into
their
own
repo
cause.
I
I
don't
know
if
that
would
get
picked
up
at
the
re
like
if
you
added
issue
templates
into
the
dot
github
folder.
I
don't
know
if
that
would
trickle
down
yeah
that.
A
Was
my
question
or
I
didn't
it,
wasn't
the
that
good
folder
was
not
part
of
my
question
because
I
didn't
know
it
existed
when
I
asked
the
question,
but
yes,
so
I
let's
see,
I
think
there
are
two
things
one
is.
This
is
the
template
for
the
new
metric
all
good
there,
and
then
this
is
the
metric
for
basically
not
I'm
sorry.
E
But
if
you
make,
if
you
make
them
pick
a
template,
then
I
think
we'll
get
more
structured
issues
that
are
easier
to
process.
Probably.
B
E
D
A
A
A
B
A
But
the
question
was:
is:
could
we-
and
I
think
you
were
kind
of
getting
at
this
like
address
wherever
it
these
like?
Could
we
put
these
in
one
place
and
maybe
that
place
is
the
github
holder
at
this
point.
D
I
I
really-
I
really
use
this
in
like
every
issue,
you
probably
notice
even
other
things,
I've
opened
that
if
you
go
and
look
at
all
those
issues,
I
always
follow
this.
This
format,
for
how
I
open
my
issues.
So
I
I
think
it's
a
really
helpful
way
just
to
structure
your
thoughts
and
kind
of
get
your
key.
Your
main
idea
across,
but
maybe
it
could
be
a
topic
for
the
community
meeting
as
well
kind
of
tying
it
into
that
github.
Repo
discussion.
A
A
A
E
D
Okay,
I'll
do
that
unless
I'll
give
you
a
wedding,
you
actually
point
to.
If
you
want
to
demo
it,
you
can
show
people
what
it
will
look
like
too.
Yes,
that's
actually
a
good
idea,
so
I'm
going
to
take.
A
A
Okay:
okay,
great
thank
you
immensely
justin
for
this
really
great
work
and
ways
to
think
about
how
to
better
do
our
work.
E
E
D
Be
cool
this
gets
starts
a
project
or
a
chaos
wired
conversation
on
this
too,
because
I
know
that
seems
to
be
like
a
sticky
point,
a
lot
of
times
with
the
github
triage
and
management.
So
hopefully
this
can
be
useful.
A
Yeah,
I
think
it
can
so
we'll
actually
tomorrow
and
you
don't
need
that's
totally
cool
to.
I
can
talk
about
this
in
the
common
working
group,
so
in
common
we've
modified
that
working
group
just
a
little
bit
to
work
on
metrics
that
are
just
that
kind
of
common
across
all
working
groups,
but
also
we,
the
common
working
group,
is
starting
to
take
on
initiatives
that
have
an
impact
across
the
entire
project
or
at
least
large
sections
of
the
project.
So.
A
Yeah,
not
just
metrics,
so
as
another
example
like
the
metrics
release
process
is
now
something
we
would
talk
about
in
common
just
because
it
has
an
impact
for
everybody.
A
E
A
Let's
see
elizabeth
I'm
gonna
just
not
talk
to
those
we
have
10
minutes
left.
I
guess
we
have
some
metric
updates
that
we
are
doing
I'll
bring
this
up.
So
just
so
folks
know
that
we
have
metrics
that
we
have
released
in
prior
years
really
yeah
and
one
of
the
the
asks.
A
Of
the
metrics
every
now
and
then
and
think
about
how
what
we've
learned
over
the
last
couple
years,
kind
of
impacts,
how
we
read
this
metric,
it's
like,
I
think
I
told
you
it's
like
reading
an
academic
paper
that
you
wrote
like
five
years
ago,
you're
like
oh
or
my
or
my
dissertation,.
A
Just
to
everybody,
you
know
we've
just
kind
of
stopped
the
meeting
and
everybody
takes
a
look
at
the
metric
and,
if
we're
good
to
go,
then
we'll
start
the
process
of
getting
it
really
retranslated
and
re-released
as
part
of
the
upcoming
release.
A
I
don't
think
we're
gonna
have
time
right
now
to
take.
Oh,
I
did
also
you
know
another
one
that
we're
gonna
take
a
look
at
is
code
of
conduct
for
events,
so
we
do
have
a
google
doc
set
up
for
that
now,
so
we
can
begin
the
same
process.
But
again
we
can
wait
on
that.
A
B
A
Understand
how
work
gets
done,
so
I
don't
know
if
people
have
thoughts
about
how
we
can
best
do
this,
because
I
think
this
is
an
inclusion
issue
that
it'd
be
great
to
talk
about
in
the
dei
working
group
as
an
example.
So,
like
we
go
through
the
google
summer
of
code
process
and
like
what
would
be
mechanisms
that
we
could
do
or
practices
that
we
could
implement
in
the
chaos
project
to
to
try
to
help
ensure
that
the
participants
in
google
summer
of
codes
stay.
B
So
I
know
the
office
hours
I
haven't
checked
how
those
have
been
going,
but
I
think
an
active
meeting
where
they
feel
the
need
or
they
have
to
or
can
show
up
every
week,
just
to
get
like
a
brief
rundown
of
maybe
what
the
other
groups
are
working
on
or
just
progress
on
the
different
projects
that
might
help
them
feel
more
involved
and
just
help
better
explain.
What's
going
on
gotcha.
A
That's
good,
I
do
know
that
ruth
and
elizabeth
did
office
hours
this
monday.
I
think-
and
I
think
there
was
pretty
good-
that
maybe
five
or
six
people
I
feel
like
it
was
tues
is
tuesday,
because.
F
Yeah,
of
course,
yeah,
I'm
sure
when
you're
talking
about
newcomers.
Actually
I
was
one
of
them,
so
I
thought
I
could.
I
could
have
an
input
yesterday.
There
was
a
session
that
was
handled
by
ruth
and
elizabeth
and
it
was
really
good
because
it
was
my
one
of
my
first
sessions
and
I
deliberately
chose
to
be
attending
all
of
these
meetings
that
I
can
follow
up
and
know
where
exactly
I
could
make
impact
and
contribution.
F
I
think
the
previous
I
don't
know
who
spoke
last
when
she
talked
about
helping
the
newcomers
engaging
all
the
working
group
sessions
to
really
know
what
they're
working
on
and
how
best
they
can
fit
is
really
a
good
initiative,
because,
actually
that's
what
I'm
doing
right
now
I
came
into
this.
I
don't
know
what
actually
is
going
on
too
much,
but
at
least
I
know
what
dei
does
and
what
it
means,
and
so
since
yesterday
and
up
to
now
there
is
really
too
much
difference.
So
now.
F
My
overview
of
the
whole
chaos
community
and
what
the
different
working
groups
do
so
are
doing
a
good
job
in
the
onboarding
and
yeah.
I
just
wanted
to
make
that
submission
course
and
when
you
come-
and
I
want
to
just
speak
about
the
impact
I'm
already
having
into
the
initiative,
I'm
putting
up
to
see
that
I
get
to
know
better.
A
Great,
so
it
sounds
like
the
the
zoom
session
is
well
received.
Yes,
it
is
great
to
have
you
here.
Enoch
can
I
can
I
ask
another
question:
do
you
say
enoch?
Is
that
how
you
say
your
name,
yeah,
yeah,
sure
sure
you
know
it's
okay,
you
know.
I
I
think
you're
also
on
slack,
is
that
right,
yeah?
Is
there
anything
in
slack?
That
would
be
helpful.
F
As
well,
I've
not
seen
too
much
activity
in
slack
actually,
for
the
previous
times
I've
joined,
I
tried
to
scroll
through
the
previous
messages
you
find
on
my
channel
right
down
the
last
messages
in
december
18th
and
you're
like
this
doesn't
look
like
an
active
channel
and
I
don't
think
I'll
get
any
response
here.
So
most
of
those
channels
that
have
previously
joined
them,
they
do
not
look
like
they
have
a
lot
of
activity
going
on
in
there.
So
that's
why?
F
Actually,
I
just
opted
to
be
attending
these
working
group
meetings,
because
I
know
I
can
get
first-hand
interaction
and
information.
F
A
F
I
I
I
don't
know
I
don't
know
whether
the
channels
you're
in
and
the
ones
I'm
in,
but
I'm
sure
we
should
share
channels
and
you
must
absolutely
somewhere.
That's
why
you
asked
so
but
yeah.
I
think
you
can
validate
that
if
you're
scrolling
through
slack
at
the
moment.
A
F
Sure
but
but
I
think,
when
you
have
this
activities
like
these
of
course
for
yesterday
and
today
conversations
have
attended,
I
see
you
get
more
updates
in
the
zoom
meeting,
so
I
thinking.
F
For
you
to
have
the
interactions
go
on
in
slack,
unless
you
deliberately
chosen
to
have
a
topic
to
continue
discussing
about
it
in
slack,
but
I
feel
like
when
you're
already
here
in
the
zone.
Call
you
have
a
lot
of
updates
and
you're
like
you,
can
just
wait
for
the
next
zoom
call.
So
there
is
nothing
ready
to
take
you
to
slack
to
have
to
continue
some
conversations
there,
unless
maybe
you
you
deliberately
choose
to
from
here
in
the
meeting.
A
D
D
Maybe
I
can
share
my
screen.
I
know
we're
getting
close
to
time,
so
I
can
try
to
make
this
really
quick.
But
again.
This
is
an
example
from
the
fedora
project
that
I
I
really
like
that
I've
seen
so
they
have
this
work,
so
they
first,
I
guess
to
start,
there's
a
join
sig
in
fedora.
So
it's
a
group
of
people
in
the
community
who
just
help
newcomers
get
involved
and
get
set
up
and
learn
about
the
project
and
how
to
get
involved.
D
So
when
someone
comes
into
the
project-
and
you
know
they're
overwhelmed
or
they're,
not
quite
sure
where
to
begin
what'll
happen
is
someone
you
know
say
they
get
in
touch
with
the
joint
sig
or
they
they
talk
to
someone.
They
say
hi
in
the
chat
channels.
D
D
So
if
I
go
and
look
here,
there's
this
huge
repository
with
all
these
different
issues
that
are
actually
corresponding
to
all
these
different
people
who
have
shown
up
and
said
they
wanted
to
get
involved
in
the
project.
And
it's
a
couple
of
things
like
there's.
A
couple
of
generic
information.
That's
kind
of
like
a
template
so
like
hey
welcome
to
the
project
here
are
some
links
that
you
can
check
out
on
how
to
get
involved
and
things
that
you
should
maybe
like
helpful
readings
and
things
to
know
and
when
you're
ready.
D
You
know,
share
an
introduction
on
this
ticket
with
us
and
let
us
know
what
you're
interested
in-
and
this
has
been
I've
seen
a
really
successful
model
that
fedora
has
done
for
bringing
in
new
people
into
the
project,
and
it
makes
it
much
more
personal
because
you
actually
get
matched
up.
You
know
different
people
in
this
join
sig
can
help
out
or
if
you
have
questions
you
comment
in
your
personal
ticket
and
someone
will
get
back
to
you
or
answer.
D
Sometimes
people
will
get
paired
with
another
contributor
more
one-on-one,
but
I
thought
this
was
a
really
creative
approach
and
it's
worked
really
well
for
fedora.
D
You
know,
and
you
can
see
all
these
different
tickets
for
people
who
have
come
in
in
the
last
few
months,
and
so
it's
kind
of
like
a
personalized
way
and
they
also
have
all
these
different
labels
here
to
kind
of
help
them
help.
The
maintainers
understand
like
how
far
along
in
their
journey
are
they,
you
know,
there's
definitely
a
kind
of
a
pretty
system
here
for
how
they
manage
it.
D
But
I
like
the
idea
just
having
like
you
know,
every
person
gets
their
own
personalized
issue
and
they
can
ask
any
questions
there
and
there's
a
whole
community
of
folks
who
get
notifications
for
those
comments
and
can
weigh
in
and
answer
those
questions.
So
just
wanted
to
share
that
as
an
interesting
model
for
how
the
fedora
project
is.
A
D
A
You
know,
I
think,
that
the
sig
and
the
working
group
are
kind
of
the
same
same
thing.
F
Yeah
we're
out
of
time,
but
it
took
me
almost
a
week
I
was
I
was
trying
to
navigate
all
the
information
on
the
community
website,
but
a
lot
of
information
was
thrown
almost
everywhere.
So
navigating
it
to
really
guide
me
on.
A
guided
process
was
really
hard
and
I
ended
up
just
getting
lost
because
there
was
too
much
information
to
digest
and
I
was
just
like.
F
Let
me
just
wait
for
a
newcomers
session
so
that
I
can
ask
those
questions
so
that
I
can
have
those
direct
questions
as
but
I,
when
I
was
navigating
almost
everything
by
myself,
there
was
just
too
much
to
digest,
but
I
got
lost
and
just
frozen
was
like
okay.
Let
me
just
wait
and
I'll
require
some
more
yeah.
A
F
And
I
was
discussing
with
ruth
yesterday
and
elizabeth
was
like
there's
some
internal
technologies
you
use
and
like
working
groups
was
really
something
I
hadn't
understood
until
yesterday's
conversation.
So
I
was
like,
what's
a
working
group?
That's
a
working
group,
so
I
was
like
you
know.
F
I
was
expecting
something
like
a
wiki
that
explained
some
of
those
things
that
don't
look
obvious
so
that,
like
I'm,
only
look
obvious
to
the
internal
community,
but
for
someone
on
boarding
they're,
actually
not
obvious,
so
that
when
they're
on
board
and
they're
ready
into
the
language-
and
they
can
figure
out
some
of
those
terminologies
easily
without
being
so
confused.
A
Right,
okay,
this
is
wonderful!
Thank
you,
everybody
for
this.
We
are
at
the
end
of
our
time,
so
always
really
great
to
see
everybody
and
I'm
sure
yeah
for
the
newcomers.
Please,
you
know
continue
to
come.
We
love
having
you
we're
looking
to
make
improvements,
that's
for
sure
sure
all
right!
Well,
thank
you!
Everybody.
Until
next
time,
we'll
see
you
all
later
bye.