►
From YouTube: CHAOSS Weekly Community Call 2/8/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
Hello,
everyone
good
morning,
good
afternoon,
good
evening,
good
of
good,
whatever
chaotix.
How
are
we,
I
hope,
we're
doing
good
today.
Here
are
the
minutes
for
you
in
case
you
missed
that
it'd
be
great.
If
you
want
to
add
your
name
to
the
list
of
the
other
chaotics
that
are
joining
our
meeting,
I
got
to
get
used
to
saying
that
I'm
so
in,
like
like
chaotic,
neutral,
chaotic
good,
I
guess
we
can
all
decide
which
category
we
fit
in
individually,
chaotic,
evil,
good
or
neutral.
Anyway.
Sorry,
I
digress.
Let
me
share.
A
Awesome,
yes,
for
those
who
don't
know
the
bengals,
my
cincinnati,
bengals
professional
american
nfl
football
team
is
playing
they're
playing
in
the
super
bowl
this
sunday.
So
I
will
shut
up
about
this
eventually,
but
not
today.
So
sorry,
you
have
a
few
more
days
with
which
to
put
up
with
my
obnoxiousness
on
the
bengals,
but
it's
just
very
exciting
because
it
just
hasn't
happened
in
like
30
years.
So
it's
very
unless.
A
A
That's
right,
we
made
it.
That's
all
that
matters
to
me
personally.
However,
if
we
do
win,
then
I
might
be
a
little
more
obnoxious
next
week,
I'm
so
sorry
anyway.
Sorry,
yes,
so
go
bengals.
Moving
on
to
number
two,
so
this
was,
I
don't
think
ruth
is
on
the
call.
Yet
do
you
see
ruth
anybody,
no
worries?
If
not,
I
literally.
A
C
That's
fine.
Can
you
hear
me
yep,
yeah?
Okay,
so
so
she
called
africa.
First,
like
it's,
a
it's
an
ngo
or
that
you
know
in
pause.
Women
in
africa
like
provide
opportunities
for
women
to
learn
technology.
C
You
know,
provide
resources
as
well
mentorship,
so
they
have
like
a
whole
lot
of
programs
and
personally
I've
benefited.
You
know
starting
up
with
tech.
I've
benefited
a
lot
from
those
programs
and
all
that
so
last
year
they
launched
a
program,
something
similar
to
g-shock
called
contribution.
C
So
I'm
going
to
get
a
link
to
that
very
soon
contribute
on.
So
it's
yeah,
exactly
that's
fine!
So
it's
like
a
month-long
contribution
to
open
source
attached
to
a
project
and
the
the
parts
funds
get
500.
C
So
how
this
works
is
so
they
are
like
different.
So
chicago
africa
has
like
they
reach
out.
They
have
sponsors
who
sponsor
the
events
right
and
then
there's
the
the
organizations
or
projects
that
participate
as
mentoring,
organizations
and
yeah.
Those
are
like
two
categories:
sponsoring
organization
you
know,
mentoring
organization
which
is
like
you
know,
participate
as
a
project,
so
usually
the
ladies
that
it's
just
for
female
females.
So
the
ladies
that
apply
to
participate
in
this
program
right,
they
are
attached
to
like
different
different
projects
right.
C
The
first
stage
is
mentoring
organizations
applied
to
be
part
of
the
program
right
and
they
have
their
projects.
You
know
their
mentors
are
going
to
be
in
charge
of
that
project,
something
it's
just
similar
thing
to
g-shock
and
these
ladies
work
on
the
project
for
one
month,
it's
one
month
period,
so
yeah
after
one
month
after
the
end
of
one
month,
they
have
like
a
a
call.
C
That's
you
know,
rounds
up
a
collaborative
call
kind
of
where
all
the
projects
you
know
they
pick
a
time
and
then
like
a
graduating
kind
of
thing,
so
yeah
and
then
she
called
africa
pays
the
participants.
This
depends
at
the
end
of
you
know
that
period
evaluates
their
contributions
and
all
that
stuff.
C
So
I
participated
as
so.
That's
a
project.
I
contribute
another
project,
open
source
project.
I
contribute
to
yeah
so
last
year
when
they
launched
the
program,
I
participated
as
the
organizer
from
that
project's
end,
so
I
was
able
to
organize.
C
Projects
in
the
community
that
you
know
that
needs
contribution
that
could
work
within
the
period
of
one
month,
so
I
was
able
to
organize
some
projects
and
we
had
like
six
participants
from
chicago
africa
that
were
able
to
contribute
both
documentation
of
code,
both
documentation
and
code.
So
I
I
drew
up
like
projects
that
needed
help
within
the
community
and
we
had
six
parts
once
and
you
know
six
mentors
as
well.
I
participated
as
both
in
mentor
and
over
and
saw
through
like
the
whole
process
from
the
open
source
community.
C
So
I
talked
to
elizabeth.
I
was
last
week.
It
would
be
great
if
chaos
would
participate
and
she
could
have
guys
going
to
send
an
official
email
coming
weeks,
but
it
would
be
something
great
that
we
can
participate
in
as
a
mentoring
organization
yeah.
So
I'm
happy
to
answer
any
questions.
B
C
Yeah,
this
event
is
provided
by
the
sponsors
right.
So
they
are
sponsors.
That's
you
know,
participates
in
the
program
right,
so
she
called
africa
on
their
end,
collects
the
funds
and
dispense
to
the
participants.
So
not
the
mentoring
organization
provides.
B
Gotcha,
thank
you.
I
mean
listening
to
your
talk.
I
don't
see
any
reason
at
all
why
we
shouldn't
participate
in
this.
I
guess
maybe
that
there
would
just
be
a
like
few
logistical
things
that
we'd
want
to
sort
out.
One
is
I
went
to
that
link
that
you
provided
and.
C
B
I
didn't
follow
through
on
it
but
like
if
we
provide
our
projects
candidate
projects
through
that
survey
process
or,
if
which
I
think
is
similar
to
like
what
outreachy
does
or
if
we
were
applau
or
if
we
provide
our
candidate
projects
like
in
our
own
community
github
repository
the
way
we
do
for
google
summer
of
code
either
is
fine.
It's
just
a
logistics
question.
D
D
C
Yeah,
thank
you
for
the
question,
so
I'm
going
to
get
the
particular
the
particular
details,
but
last
year
the
program
had
participation
from
about
three
countries:
yeah.
I
think
that's
three
countries
in
africa,
so
nigeria
I'm
going
to
get
the
exact
countries,
but
it
had
like
three
countries
from
africa
that
participated
in
the
first
cohort.
C
I
don't
know
if
that
answered
your
question.
I'm
strong
and
we
are
also
trying
to
you,
know,
spread
the
word
out
as
well,
because
she
could
africa
is
more
like
it's
not
just
it's
not
just
an
organization
in
nigeria,
although
the
founder
is
in
nigerian,
but
it's
like
you
know,
for
africa
as
a
whole,
so
plans
like
spread
the
word
more,
so
we
get
more
applicants
from
other
countries.
Last
the
last
the
last
cohort
was
from
three.
D
Okay,
yeah,
because
to
me
it's
a
great
project,
it's
something
that
really
looks
good
from
what
you've
described
and
I
really
wish
we
should
really
spread
the
word
across
to
get
a
rich
set
of
diverse
people,
even
though
you
are
focused
with
girls,
which
is
another
which
is
a
plus,
it
really
needs
to
touch
as
much
as
as
much
people
as
possible.
A
Okay,
so
for
this,
thank
you
ruth
you're
awesome.
I
think
next
steps
is
just
to
kind
of
wait
for
them.
They're
supposed
to
be
emailing
us
some
more
specifics
on
how
we
get
involved,
but
it
sounds
like
it's
definitely
something
that
we
want
to
move
forward
with
unless
something
else
comes
up
so
exciting.
I'm
very
excited
about
that.
Thank
you
so
much
for
bringing
that
to
us
ruth.
It's
awesome,
any
other
questions
for
ruth.
E
I
guess
this
is
just
a
comment
for
people
like
matt
and
others,
like
I
don't
know
if
he
already
had
ideas
for
for
google
summer
code,
but
I
assume
we
can
make
submission
for
the
same
project
idea
for
for
both,
and
you
know,
like
I
mean
we'll
deal
with
that.
If
it
gets
accepted
by
both
but
yeah,
I
don't
think
we
need
to
create
separate
ones
for
it.
C
Ruth
go
ahead.
Yeah.
I
think
I
think
one
thing
that
might
conflict
with
g-stock,
because
since
g-shock
is
a
three-month
period-
and
you
know
this
is
one
month
period-
I
think
that
might
have
you
know
some
conflict,
because
the
timing
for
the
idea
is
the
project
can
be
done
in
a
month
right
because
that's
like
the
court
period
for
for
some
of
the
participants,
they
stay
longer
right.
Even
after
a
contribution.
C
A
Okay,
so
we're
gonna
move
along
thanks
again
ruth
for
bringing
that
up
and
the
next
one
is.
I
just
wanted
to
because
it's
been
a
while,
since
we
did
our
working
group
updates,
we
used
to
do
them
all
on
one
day
of
our
weekly
meeting
here
and
then
we
decided
the
end
of
last
year
to
break
those
up
and
just
do
like
one
update
a
week.
So
we're
gonna
kick
that
off
again.
A
A
A
I
love
to
voluntold
yay
matt
g
is
a
person
awesome
thanks,
matt,
okay,
next
on
our
agenda,
is
this
place
for
internal
chaos
project,
so
the
dei
badging
kind
of
kicked
this
off
and
then,
as
ruth
and
I
were
speaking
earlier
today.
This
we're
there's
a
lot
of
like
knowledge
around
our
newcomer
initiatives
that
we're
working
on.
But
these
also,
these
this
these
pieces
of
knowledge
also
contain
some
personally
identical
identifiable
information
or
pii,
which
means
we
want
to
keep
it
kind
of
private.
A
If
we
can
things
like
email
addresses
and
we
don't
want
that
information
to
get
lost
so
in
essence
like
when
the
dei
badging
we're
kind
of
doing
some
shifting
of
transitioning
of
leadership
there
and
the
list
of
reviewers,
for
instance,
here's
all
the
reviewers
here's
our
email
addresses
like.
Where
does
that
document
live,
and
we
want
to
make
sure
that
there
isn't
just
like
one
person
that
has
that
information.
A
So
we
were
ruth
and
I
were
thinking
like.
Maybe
there
should
be
a
private
repo,
just
an
idea.
Private
repo
on
our
github
chaos
account
organization
that
we
could
put
some
of
these
docs.
That
are
a
little
bit
more
sensitive
that
we
don't
want
to
have
public
per
se,
but
we
do
want,
like
maybe
the
core
chaos
group
to
be
have
access
to
like
someone
else.
A
B
A
Yeah
so
it'd
be
like,
for
instance,
we
ask
here's
another
example:
we
ask
newcomers
to
fill
out
a
form
when
they
join
our
community.
B
A
Yeah
yeah,
that
would
you
know
because
we're
we
are
sharing
these
docs
back
and
forth
and
collaborating
on
on
different
ideas,
but
we,
you
know,
I
don't
like
not.
Everybody
needs
to
see
that.
I
see
some
comments
in
the
chat
about
a
shared
drive
on
google.
That
could
also
work
because
we
have
that
already
and
the
chaos
the
chaos
project
has
its
own
gmail
account.
So
we
could
do
that
too.
F
That
think
we've
already
used
private
google
docs,
so
I
think
I
think,
that's
kind
of
common
practice
right
now
for
for
some
of
those
things,
okay,.
A
G
Yeah,
so
one
thing
is:
there's
this
nice
feature
I
had
access
when
I
was
at
my
university,
I'm
not
sure
what
kind
of
account
chaos
has
with
google.
If
there's
a
google
like
business
account
there,
but
you
can
create
these
shared
drives,
which
is
like
the
times
I'd
use
them
is
a
really
great
way,
especially
if
you're
working
across
a
wide
organization
to
organize
all
the
things
and
people
can
have
different
access
and
rights.
This
is,
I
think,
a
layer
on
top
of
google
docs.
G
That
can
be
really
helpful,
but
I'm
not
sure
you
probably
have
to
play
around
and
see
if
you
can
create
that
from
the
chaos
gmail
account
depending
how
it's
set
up.
If
it's
possible.
I
think
that
would
be
a
really
cool
approach,
just
to
add
a
little
more
organization
around
the,
because
I've
gotten
lost
trying
to
find
google
docs,
and
I
get
I
have.
G
I
I've
created
my
own
folder
and
bookmarks
of
all
these
chaos
docs,
but
it'd
be
nice
to
have
that
centrally
managed
instead
of
it
having
to
you
know,
have
the
right
link
and
make
sure
you
have
the
right,
folder
saved
and
so
on.
A
Yeah
totally
agree,
and
the
only
the
only
reason
I
was
thinking
of
a
github
repo
is
that
we
could
kind
of
create
our
own,
like
wiki
or
like
internal
handbook,
to
to
kind
of
explain
like
okay,
for
instance,
here's
the
dei
badging
stuff.
Here's
where
the
list
of
current
reviewers
are
here's,
how
many
reviews
they've
done
and
who's
up
next,
here's
the
way
that
this
bot,
who
owns
the
bot-
and
this
is
where
it's
located
and
just
like
all
of
that
those
pieces.
A
G
Yeah
you
could,
you
could
have
like
a
read
made,
google
doc,
it
wouldn't
quite
be
the
same
effect,
maybe
just
trying
to
make
any
other
files
are
organized
within
subfolders
by
working
group
or
by
other
another
way
of
organizing,
but
you
know
kind
of
thinking
about
it.
A
github
wiki
could
also
work
nicely
and
tie
in
with
some
of
our
other
workflows,
so
I
I
could
go
either
way
on
it.
I
guess.
H
I
would
think
about
where
what
format
all
of
these
stocks
are
in
now,
when,
when
you're
thinking
about
whether
to
use
a
shared
drive
or
or
google,
because
if
a
lot
of
it's
coming
from
google
forms,
then
you
might
be
better
off,
leaving
it
in
google
and
creating
a
shared
drive.
We
use
a
shared
drive.
We
use
it
internally
here
at
vmware.
We
also
have
one
that
we
use
for
open
uk
for,
like
all
of
the
confidential
board
meeting
stuff
and
it
works.
It
works
pretty
well
for
things
like
that.
H
On
the
other
hand,
we
have
in
the
to
do
group,
we
have
a
private
private
repository
where
we
manage
things
like
member
lists,
for
example.
F
I
would
I
would
like
to
also
add
that
the
the
the
content
we
we
do
want
that
to
be
private,
but
the
fact
that
the
content
exists.
We
should
have
some
transparency
around
that.
F
So
I
think
that's
one
of
the
reasons
that
the
I
think
google
docs
also
kind
of
makes
sense
to
me,
because
we
could
actually
have
the
links
to
those
private
documents
displayed
in
a
transparent
fashion.
And
then,
if
someone
tries
to
access
them,
they
have
to
basically
request
request
access
so
that
that
also
kind
of
creates
the
process
by
which
we
would
allow
people
access
to
those
documents
right.
A
There's
a
couple
comments
and
chat
about
wikis
and
the
github
wikis.
Can
we
create
a
private
repo
to
then
create
a
wiki,
that's
kind
of
melbourne?
What
I
was
what
my
original
thought
was
like
if
we
just
had
a
private
repo
that
you
know
some
of
the
chaos
admins
and
maintainers
had
access
to
that
would
kind
of
just
be
like
almost
an
internal
community
handbook
for
things
of
like
how
does
stuff
work
like.
If,
if
I
you
know,
I
don't
know,
ran
away
tomorrow,
I
won't
say
got
hit
by
a
bus.
A
But
if
I
ran
away
like
you
know,
a
lot
of
this
stuff
is
in
my
head
and
and
that's
kind
of
what
we
were
finding
out
with
matt
in
the
dei
badging
initiative,
like
a
lot
of
that
stuff
was
in
his
head,
which
was
fine
because
he
was
the
one
working
on
it,
but
you
know
to
pass
that
information
along.
It's
almost
like
we
needed
a
handbook.
You
know
if
I
won
the
lottery
and
retired
on
a
beach.
Yes
don.
Thank
you.
A
A
So,
okay,
any
other
final
comments,
because
we
do
have
other
stuff
to
talk
about.
A
Okay,
well
we'll
keep
marinating
on
this
whole
thing
of
how
we
want,
maybe
that
to
be
set
up
for
long-term.
You
know
kind
of
use,
keeping
track
of
everything.
So
thanks
everybody.
I
appreciate
you
all
right.
The
next
one
on
here
says
matt
g
and
jwf,
so
matt
and
justin
github
templates
galore.
So
I
will
let
you
all
take
that
away.
B
B
B
B
That
provides
some
more
than
just
a
picture
perhaps,
but
you
know
ways
to
connect
with
the
project,
and
so
that
was
relatively
easy
to
do
so.
What
I
did
was
I
created
a
github,
and
then
I
created
an
initial
repo
that
was
created
prior
to
the
github
repo
and
a
secondary
repo
that
was
created
after
the
github
repo,
because
I
wanted
to
see
the
effect
of
creating
the
github
repo.
B
You
know
kind
of
going
both
of
these
directions.
So
the
github
repo
is
structured
like
this.
So
it
has
these
kind
of
high
level
files
here
code
of
conduct
contributing
in
readme.
B
It
has
a
profile
folder,
which
is
where
this
you
can
see
that
that
org
level
readme
is
taken
up
from.
So
we
just
would
create
a
profile
folder
within
there.
That's
easy
enough
to
do,
and
then
it
also
contained
another
github
folder
that
contains
some
issue
templates
and
some
pull
request
templates,
because
I
wanted
to
see
if
those
would
cascade
through
as
well
to
the
other
repositories.
B
B
Prior
to
the
repository
that
was
created
prior
and
it
went
to
the
repository
that
was
created
after
the
dot
github
repo
and
what
this
looks
like
in
the
initial
repo
one
of
them
didn't
carry
through.
But
here
is
the
code
of
conduct
over
here
right.
So
it
doesn't
show
up
in
this
list
here,
and
this
read
me
is
the
readme
that
I
put
in
the
initial
repo
all
right
and
that
stays
there.
So
that's
that's
overwritten,
but
the
code
of
conduct.
B
If
I
click
it,
you
can
see
that
it
goes
to
the
github
repo
and
again,
for
this
repository
I
had
I
just
created
it
ahead
of
the
dot
github
repository,
because
I
was
curious
if
this
would
show
up
so
a
few
outstanding
questions
for
me
is.
I
had
also
put
a
contributing
in
there,
so
unless
I
spelled
it
wrong
that
didn't
seem
to
go
to
the
other
repositories,
I
don't
know
why
I
was
told
that
it
would,
but
it
didn't.
G
G
It
did
get
picked
up,
but
okay,
so
yeah,
maybe
then
maybe
contributing
just
has
to
be
special,
but
I
was
thinking,
maybe
just
as
a
context
to
hear
I
don't
know
how,
if
folks
had
prior
context
to
this,
but
in
the
in
the
dei
working
group,
we
were
recently
playing
around
with
issue
templates
as
a
way
to
try
to
streamline
some
of
our
how
we
collect
metrics
and
other
feedback
on
our
github
repositories,
as
we
were
going
through
and
doing
this
triage
and
trying
to
clean
things
up,
and
it
was
from
that
discussion
that
we
started
thinking
about
well
like.
G
Are
there
ways
that
we
could?
You
know,
have
these
templates
be
useful
for
other
working
groups
and
other
teams
in
in
chaos
like
you'll,
see,
there's
this
new
metric
template?
If
you
look
at
the
link,
I
just
put
in
the
chat
you'll
see
the
issue
templates
that
we
we
try
it
out
and
for
the
dei
working
group.
G
You
have
all
these
like
kind
of
prompts
and
questions
and
something
else
that's
kind
of
come
up
since
we
talked
about
this,
that
we
could
also
look
at
is
github
is
trialing
out
this
new
issue
forms
feature
which
is
actually
like,
like
a
google,
doc
or
google
form,
but
in
github
issue
form,
which
I
thought
was
kind
of
cool.
G
So
this
could
be
one
way
that
we
try
to
better
standardize
for
all
the
working
groups
to
make
it
easier
to
review
and
for
anyone
in
the
community
whether
it's
from
you
know,
I
think
it's
a
total
new
contributor
or
someone
who's
coming
from
another
working
group.
Is
that
there's
a
more
standard
workflow
across
the
working
groups
and,
of
course,
things
like
code
of
conduct
and
contributing
guidelines.
We
could
also
try
to
standardize
those
across
chaos
and
then
just
have
them
get
picked
up
by
all
the
other
working
groups.
G
So
I
think
it'd
be
something
that
both
reduces
some
of
the
the
maintenance
labor
for
all
the
working
groups
for
having
things
like
code
of
conduct,
contribution
guidelines,
even
issue
templates,
but
also
would
give
us
a
chance
to
try
to
better
organize
workflows
for
how
we
I
try
to
make
it
easier
to
manage
the
github
working
groups
and
and
the
issue
trackers
that
are
there.
So
we
were
trialing
this
out.
G
This
idea
out
in
the
dei
working
group
and
just
wanted
to
share
it
back
here
to
see
if
having
the
github
repo
at
the
chaos
org
level
would
be
helpful
as
a
way
to
try
to
standardize
this,
maybe
try
to
drive
some
conversations
around
around
how
people
can
propose
metrics.
So
that
was
just
some
of
the
background
and
context
for
where
this
is
coming
from
and
and
why
we
were
experimenting
with
this.
I
hope
that
helps.
F
F
That
way,
there's
not
redundancy,
but
but
currently
the
the
community
repo
serves
the
function
that
that
you've,
just
described,
justin
or
or
we've
been
trying
to
get
it
to
serve
that
function.
A
I
would
just
add
that
the
community
repo
also
does
keep
things
like
feedback
on
chaos,
con
and
other
things
besides
just
template
stuff,
so
my
personal
feeling
would
be
to
move
whatever
is
like
more
templatey
things
to
the
get
github
repo
and
keep
the
community
repo
as
a
place
where
people
can
just
open
issues
if
they
have
something.
You
know:
community
culture
for
instance,
or,
like
we
said,
chaos,
con
feedback.
That
kind
of
stuff
is
those
kind
of
conversations
still
do
happen
in
the
community.
Repo.
F
So
I
would
I
cautioned
this
in
the
last
community
meeting
and
I
suppose
I'll
say
it
again,
having
too
many
platforms
for
communication
or
too
many
repos
kind
of
creates
a
lack
of
transparency
or
it
it
reduces
transparency
so
when,
when
we
have
to
start
looking
around
to
see
where
everything's
happening,
so
I
would
just
I'm
not
saying
I'm
not
saying
I
disagree
with
you,
I'm
just
saying
we
when
we
introduce
new
communication
technology
when
we
create
new
repos,
I
think
we
really
need
to
be
careful
about
limiting
the
number
of
places
that
people
have
to
look
look
to
to
see.
A
No,
I
totally
get
that.
I
think
too,
like
some
of
the
issues
in
the
community.
Repo
are
kind
of
placeholders,
so
that
information
doesn't
get
lost
and
and
is
more
transparent,
for
instance
like
the
feedback
on
chaos
con.
So
we
had
that
those
conversations
here
in
these
meetings
and
whatnot,
but
like
that
issue,
keeps
it
top
of
mind.
So
I
wouldn't
like,
if
I'm
coming
to
a
new
org,
I
wouldn't
necessarily
be
going
to
a
github
repo
to
find
out
about
the
community
or
like
open
something
that
I
thought
was.
A
You
know
a
question
or
an
issue
about
community,
so
that
would
be.
My
only
thing
is.
I
think
they
do
serve
two
separate
purposes
but
like
and
matt
also
just
commented,
we
have
like
g
sock
things
in
the
community
repo,
but
would
those
fit
in
a
github
repo?
I
don't
I
don't
know
like
I
wouldn't
think
so,
but
maybe.
B
G
F
So
do
we
so
so
currently
the
the
way
we
use
the
the
community
repo
is
we
we
create
the
templates
and
the
contributing
document.
The
mission
statement,
those
documents
in
the
community
repo
and
then
we
just
point
to
them
that
way:
there's
not
duplication
or
replication
of
documents
in
all
of
the
other
repos.
F
So
the
from
what
I'm
understanding
the
the
benefit
of
the
dot
github
repo
is
that
we
can
create
one
contributing
document
in
dot
github
and
then
it
would
automatically
populate
that
document
into
all
of
the
repos
that
are
in
the
the
group.
Is
that
correct.
A
G
And
maybe
one
thing
too
that
using
that
organizational
readme
on
the
point
of
trying
to
reduce
confusion
on
where
to
look
and
which
repositories
are
for
what?
I
think
that
organizational
profile
readme
could
be
a
really
great
way
of
trying
to
reduce
that
complexity
of
saying:
hey:
are
you
looking
for
working
groups
boom?
Here's
all
the
working
group,
repos
hey!
Are
you
looking
for
something
else?
G
Here's
a
community
place
for
community
or
gsoc,
so
maybe
we
could
try
to
avoid
that
that
rabbit
hole
of
having
too
many
places
for
too
many
things
and
just
trying
to
use
that
that
profile
readme
as
a
way
to
basically
annotate
where
to
find
which
things
and
that
might
reduce
some
of
the
confusion
there
too.
Over.
B
B
A
Sounds
cool?
How
do
we
want
to
go
forward.
B
My
one,
my
one
thought
that
maybe
we
should
maybe
think
about
was
we
have
a
lot
of
different
repositories
in
the
chaos
org
and
I
don't
know
that
they
all
necessarily
function
the
same
way.
B
F
I
I
think,
I
think,
the
the
organization,
I
think
we're
all
kind
of
in
agreement
that
the
organizational
readme
is.
We
should
just
do
that,
so
I
would
vote
let's
move
forward
with
the
organizational
readme
and
the
the
rest
of
the
functionality
in
that
dot
github
repo.
Maybe
we
continue
to
discuss
and
look
at.
B
Yeah
I
mean
I'm
I'm
happy
to
keep
talking
through
it.
I
think
I
was
pretty.
I
was
pretty
happy
with
the
way
it
worked
at
least
just
the
way
that
it
worked
with
existing
repositories
as
well
yeah
code
of
conduct.
There
are
a
couple
that
would
be
pretty
easy,
so
they
don't
show
up
in
the
main,
like
folder
structure,
you
have
to
look
to
the
right
side
of
the
you
know.
I
don't
know
if
you
notice
that,
like
I
have
to
look
a
little
bit
to
the
side,
but
maybe
that's
not
an
issue.
A
Awesome,
thank
you.
That
was
really
the
only
that
was
the
last
item
on
the
new
stuff,
so
we
can
go
back
to
wait
a
minute.
Let
me
share
again.
A
Okay,
so
just
a
few
reminders
from
last
week:
visa
we
have
applied,
and
the
list
is
of
ideas
is
here.
So
if
you
have
an
idea
for
something
you
can
fork
this
and
submit
a
pr
to
add
an
idea
to
this
list
and
the
old
list,
I
think,
is
somewhere
here:
g
stock
ideas
2021..
A
Okay,
any
questions
on
that
something
to
add.
Okay,
all
right
and
the
next
item
very,
very
important.
We
are
doing
a
photo
mural.
So
if
you
are
a
chaotic
which
you
all
are
because
you're
here
or
you're
watching
this-
and
so
you
are
connected
to
us
whether
you
want
to
be
or
not,
you
are
so
you
should
absolutely
join
in
and
you
can
see
there's
a
link
here
in
the
minutes
to
what
we're
looking
for
as
far
as
like
file
format
where
to
send
them
all
of
that
stuff.
A
So
click
that
link,
if
you
have
any
questions
at
all
on
that,
please
reach
out
to
me
elizabeth
chaos.community,
or
you
can
hit
me
up
on
slack,
I'm
also
on
twitter
and
facebook,
I'm
everywhere
it's
like
20
times,
20
ways
to
get
a
hold
of
me.
So
I'm
good
and
bad,
but
yeah
just
hit
me
up
be
happy
to
answer
any
questions
you
have
and
I
wanted
to
give
some
time
out.
B
B
That
this
is
really
preliminary,
so
obviously
we
have
the
chaos
dei
event
badging
program
that
has
been
running
really
really
well
for
the
last
year
and
we've
all
often
talked
about
a
project
badging
at
the
project
level.
But
it's
always.
We
always
seem
to
get
stuck
on
kind
of
a
scale
issue
like
if
we
just
say
hey
project
badging
is
open.
There's
the
potential
for
just
an
overwhelming
number
of
projects
to
request
badges,
not
to
mention
the
need
to
re-certify
or
re-badge
a
project
within
some
given
period
of
time.
So
it
just
it
really.
B
It's
a
really,
not
bad,
but
complicated
scale
problem
that
we
just
can't
overcome
and
we
don't
have
an
unlimited
supply
of
reviewers.
So
part
of
me
was
thinking
you
know.
We've
talked
a
lot
about
these
different
programs,
such
as
all
in
we've
talked
there's
a
group
called
code
for
society.
Obviously,
the
outreachy
program
that
are
looking
to
include
projects
that
individuals
can
apply
to
participate
in
right
or
an
all-in
is
is
from
a
maintainer
perspective.
B
You
know
code
for
societies
from
a
scientific
organization
or
scientific
project
perspective,
so
each
each
different
kind
of
of
those
boxes
down
at
the
bottom.
It's
kind
of
a
different,
a
different
program,
and
so
what
I
was
thinking
was
with
with
chaos.
Perhaps
we
could
start
thinking
about
programs
that
we
would
like
to
participate
with.
B
So,
if
I
just
stick
with
all
in,
for
example,
as
projects
or
maintainers
would
like
to
join
the
all
in
program,
they
have
to
go
through
a
project.
The
chaos
project,
badging
program
as
part
of
joining
all
in
I
don't
know
if
this
is
acceptable
with
the
folks
at
all
in
this
is
just
me
thinking
aloud
or
if,
if
projects
would
like
to
join
code
for
society,
they
have
to
go
through
part
of
that
process.
Is
the
chaos
dei
project
badging
program?
B
B
Yeah-
and
I
mean
it
could
be
something
that
we
say
if
you
want
to
participate
or
have
the
dei
project
badging
as
part
of
your,
you
know,
having
people
join
the
all-in
project
or
having
projects
join
code
for
society,
for
example,
we
the
one
resource
that
that
we
may
ask,
or
the
one
thing
that
we
may
ask-
is
to
have
reviewers
help
in
this
process.
Like
can
you
help
us
kind
of
you
know?
B
A
B
A
Yeah,
I
was
thinking
more
like
so
like
all
in
for
maintainers.
They
might
be
focused
on
one
aspect
of
community
health
and
might
not
be
as
concerned
with
others.
C
B
A
All
right
any
comments,
I
see
a
few
plus
ones
love
the
idea.
Are
you
chat?
Anybody
have
thoughts
on
this.
We
have
two
minutes.
A
A
I
think
we
can
call
it
thanks
so
much
to
everyone
for
coming,
especially
our
newcomers
non.
So
melba
enoch
ish
great
to
see
you
all.
Thank
you
for
joining
us
and
we
will
see
everybody
next
week.
Go
bangles
cheer
us
keep
cheering
bye.
Everybody
bye!
Everybody.