►
From YouTube: CHAOSS Weekly Community Call 4-6-21
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everyone
welcome
to
the
april
6th
edition
of
the
weekly
community
call
for
chaos.
This
is
the
first
one
of
the
month,
so
we
usually
try
to
do
a
round
table
of.
I
don't
know
if
that's
the
right
word,
but
we
try
to
go
around
and
do
the
the
working
group
updates
and
give
any
other
big
updates
for
people
who
don't
have
an
opportunity
to
join
us
on
the
weekly
meetings.
This
monthly
one
is
usually
a
pretty
good
one.
A
So
so
that's
on
the
agenda
and
we
do
have
quite
a
few
other
things,
so
we're
going
to
jump
right
in
and
start
on,
item
number
one,
and
let
me
just
make
sure
that
everyone
has
the
minutes
really
quick,
one
more
time.
A
Okay,
so
item
number
one
is
a
few
weeks
ago
we
had
talked
about
changing
mailing
lists
from
the
the
old-fashioned
ones
that
we
were
using
that
with
the
interface
from
like
1995..
So,
but
I
don't
know
like
what
happened
with
that.
So
I
have
put
this
on
the
agenda.
I
just
like,
if
I'm
supposed
to
be
doing
something
someone
needs
to
tell
me
or
if
there's
any
action
items
or
or
what
we
need
to
do
with
that.
B
B
That's
you
that's
using
it,
so
this
is
less
of
a
conversation
that
we
had
years
ago
when
we
were
talking
about
doing
this
anyway.
B
So
I
think
honestly,
at
this
point,
when
I
saw
your
note
there,
elizabeth
you
know,
maybe
it's
just
a
series
of
steps
that
we
need
to
take
to
make
sure
that
we
successfully
tell
everybody
that
we're
making
this
change
and
perhaps
have
two
lists
running
for
a
while.
I'm
totally
thinking
out
loud
here
and
then
you
know
final
deprecation,
because
we
we
can't
just
move
people
over.
B
I
think
that's
against
the
rules.
You
know
to
just
copy
names
of
people.
We
can't
sign
people
up
for
mail
lists
so
without
their
consent.
So
I
think
it's
really
just
about
that.
What
people's
thoughts
are.
C
B
A
Okay,
so,
as
far
as
like
setting
up
the
new
list,
how
how
do
we
go
about
doing
that.
A
Oh,
all
right,
checked
done,
did
we
we
have
one
for
the
dni
also
and
the
I
think
there
was
also
like
the
board
had
one.
A
G
F
D
D
B
Okay,
so
it
looks
like
there
might
be
a
few
more
lists
to
make
and
I
think
honestly
they're
made
right
now,
they're
just
marked
as
inactive
by
brian
werner
who
set
these
up.
So
I
guess
maybe
the
next
set
is
for
me
to
reach
out
to
brian
and
just
kind
of
ensure
that
we
have
these
four.
Maybe
five
lists
like
kind
of
ready
to
go,
and
then
the
next
step
could
be
sending
out
an
email
to
the
list
to
sophia's
point.
Maybe
for
a
couple
weeks
saying:
hey
we're
changing.
B
Let
us
know
if
you
want
to
opt
out
and
then
a
week
later,
something
hey,
don't
forget,
we're
changing.
Let
us
know
if
you
want
to
opt
out
and
then
at
the
end
of
two
weeks
we
go
ahead
and
start
the
new
list
or
we'll
have
to
migrate
people
over
names.
It'll
take
a
little
bit
of
time
and
then
just
shut
down
the
new
list.
Sorry
shut
down
the
old
list
and
start
the
new
one.
B
I
don't
recall
asking
that
so
I'll.
Ask
that
again
when
I
reach
out
this
time.
A
A
A
Let's
go
into
number
two,
and
this
says
new
blog
post
on
the
website
by
shoya,
and
there
is
a
link
in
the
minutes
which
we
can
post
here.
I
have
not
seen
this
blog
post.
Shame
on
me,
so
let
me
just
post
this
here.
A
Right,
what
am
I
even
doing
with
my
life?
I
don't
know.
Oh,
this
is
very
cool,
so
she's
written
about
the
github
2020
digital
insight
report,
and
we
will
drop
that
in
the
minutes
here.
A
So
anyone
who
wants
to
read
that
can
do
so
right
here
it
is,
and
we
will
it
actually
will
automatically
go
to
twitter,
but
if
anybody
wants
to
help
promote
that
and
do
the
retweeting
thing
and
that
you
all
do
so
well
just
follow
chaos,
chaos
proj
on
twitter
and
then
you
can
just
retweet
that'd,
be
great
and
help
show
you
out
to
get
a
little
bit
more
eyes
on
that.
A
A
A
All
right,
then,
I
guess
we
will
move
along
to
number
three
just
to.
I
think
we've
talked
about
this
the
last
few
times
so
in
case
anyone's
missed
it.
We
are
doing
a
standardization
project
across
all
the
working
groups,
to
kind
of
get
us
a
little
more
organized
a
little
more
standard
in
preparation
for
some
automation,
primarily
that
we'd
like
to
do
when
it
comes
time
for
like
metrics
releases
and
things.
A
So
I
just
wanted
to
shout
out
to
yash
and
ritik
and
georg,
and
I
don't,
if
there's
anyone
else
working
on
this,
I
don't
think
there
was.
But
if
there
is,
we
want
to
make
sure
we.
We
recognize
that
they've
all
been
working
super
hard,
because
it's
there's
a
lot
a
lot
to
do,
but
we
are
at
the
end
of
this
project,
will
be
very
efficient
and
very
standardized,
and
we
will
look
amazing
so
so,
and
that'll
set
us
up
for
future
automation
and
future
efficiencies.
A
H
Metric
thing
that
broke
today,
yes,
yeah,
okay,
so
I
I
I
guess
I'm
working
on
this
as
well,
but
I
but
I
don't
need
recognition.
H
When
that
changed,
it's
made
just
drop
a
rep,
a
line
into
the
github
repost,
so
that
I
can
go
in
and
and
change
the
links
on
the
website
side.
Otherwise
it
will
break
the
the
metrics
that
we've
released
on
the
website.
B
D
B
Quite
a
bit
of
volume
and
work
across
the
repository.
So
thanks
for
tracking
that
and
asking
for
changes
and
merging
stuff
kind
of
looking
right
at
you,
george,
you
can't
tell
that
I
think
I'm
always
concerned
when
zoom
and
switch
is
a
feature
where
you
can
tell
where
you're
looking
but
looking
at
you
gear.
So
thanks
for
doing
that,.
A
A
B
I
can
tell
you,
I
mean
it's
continuing
to
work
on
on
metrics
I
mean
this
is
going
to
be
the
update
from
common.
I
hitches.
I
was
jotting
down.
This
is
the
reason
that
I
knew
some
of
the
risk
links
had
broken.
I
was
kind
of
jotting
down
what
some
of
the
new
metrics
that
had
come
out
and
so
reviewed
cycle
duration
with
within
a
change
request,
was
a
new
one.
A
And
I
think
the
one
that
is
currently
being
worked
on
if
memory
serves-
I
probably
should
have
looked
at
this
beforehand,
but
I
believe
it's
the
time
waiting
for
reviewer,
no
first
submitter
action
as
the
one
that
we're
currently
working
on
right
now.
So
if
that's
something
that's
interesting
to
you
feel
free
to
join
the
common
working
group
on
whatever
day
that
is
thursdays,
I
guess
every
other.
A
Okay:
let's
go
on
to
risk,
I'm
looking
at
you
sean!
You
want
to
get
an
update.
C
We
also
merged
a
pull
request
that
standardized
our
repo,
so
team
risk
is
on
board
with
the
new
standard
repos
and
at
this
point,
we're
just
we've
got
some
metrics
language
level
upstream
dependency
enumeration
which
we're
going
to
try
to
clean
up
that
name
under
development,
and
then
us
pdx,
approved
licenses
is
in
development
and
free
software
foundation
approved
licenses,
possibly
is
in
development
as
well,
so
we're
looking
kind
of
as
licensing
types
as
a
early
sort
of
low
hanging,
fruit,
type
of
signal
of
dependency
risk
that
we
can
pursue,
and
I
imagine
we'll
build
more
metrics
as
we
as
we
could
towards
the
summer
release,
which
is
she's
probably
only
three
months
away.
C
A
I
think
one
other
quick
comment
on
that
was
that
I
believe
they
decided
to
kind
of
pull
together
the
dependencies
in
one
focus
area,
whereas
it.
C
C
B
Back
in
the
group
with
I'm
again
looking
at
georg,
do
you
know
if
gramor
lab
is
is
looking
at
licensing.
I
know
that
the
answer
has
been
no
historically
I'm
just
the
reason
I'm
asking
is
just
because
it's
always
that
alignment
between
the
development
of
metrics
and
into
tooling
I'm
just
always
trying
to
see
where
these
points
of
connection
are
occurring.
B
D
Grimoire,
lab
suite
does
have
a
module
for
licenses
called
growl,
which
is
was
developed
as
a
google
summer
code
project
or
really
advanced.
It
was
developed
by
valerio
some
time
ago,
but
valeria
is
no
longer
part
of
the
georgia,
no
longer
part
of
the
grammar
lab
community.
So
there's
no
activity
on
that
module
and
it's
not
supported
by
beterja
itself.
So
it's
currently
sits
idle
in
the
open
source
community
gotcha.
E
I
just
have
a
general
one
within
the
dependency
work.
We've
alluded
the
need
to
at
some
point,
maybe
reference
other
metrics
across
chaos.
E
Are
in
nature
very
complex
and
it
might
be
like
if
you're
looking
for
other
ways
to
add
more
depth,
to
the
way
that
you
measure
this,
then
we
would
suggest
say
looking
at
some
metrics
from
the
common
working
group,
and
I
was
curious
if
there
are
other
examples
about
cross-referencing
metrics
from
other
working
groups.
And
if
that's
something
we
can
add
to
our.
C
I
we
should,
I
agree,
I
think,
that's
part
of
what's
motivated
the
standardization
of
the
working
groups,
but
I
don't
think
we
have
a
mechanism
for
like
one
common
did
it
with
other
working
groups.
C
As
I
recall,
it
was
really
sort
of
hand,
knitting
the
links
between
the
working
groups
so
pointing
directly
at
the
metrics
that
another
working
group
built
there
was
there's
no
sort
of
searchable
index
or
network
view
of
of
the
metrics,
which
I
think
might
be
called
for
by
some
of
the
work
that
risk
is
doing
because,
as
soon
as
you
identify
a
dependency,
you
want
to
know
what
the
health
and
sustainability
of
all
those
dependencies
are,
and
so
you
end
up
in
a
kind
of
a
different
model
of
looking
at
the
health
and
sustainability
of
your
own
project.
C
E
B
H
H
To
a
couple
of
discussions
we've
had
recently,
one
of
them
is
about
editing
the
template
to
have
documents
on
how
to
link
to
other
working
group,
metrics
and
and
other
metrics
in
general,
and
then
the
other
discussion
we
had
is
is
related
to
how
the
metrics
are
presented
and
that's
actually
part
of
one
of
the
one
of
the
google
summer
code
projects
rather
than
presenting,
rather
than
always
presenting
the
metrics
by
working
group.
C
I
agree
I
mean
it's
working
groups
are
kind
of
how
we're
creating
them
and,
as
we
develop
more
metrics,
I
think
we
probably
need
a
more
human-friendly
way
of
organizing
their
presentation
for
people,
so
I
think
it
would
help
with
utilization
a
bit.
H
That's
that's
how
I've
been
seeing
it
as
well,
but
I
am
biased.
E
F
New
further,
I
will
add
to
the
dependency,
and
that
group
is
like.
We
tried
to
clarify
some
terminologies
like
there
was
so
much
confusion
on
the
transitive
dependency,
indirect
dependency.
We
try
to
like
clarify
those
terminologies
so
that
we
have
the
same
framework
when
we
are
defining
those
metrics
around
dependence.
E
But
I
think
that's
a
good
point,
because
I
think
it
kind
of
alludes
to
the
need
to
have
a
separate
glossary,
which
I
think
could
be
something
if
we're
thinking
about
a
broader
reference
architecture
for
all
the
metrics.
It's
also
metrics
and
terminology,
which
is
what
we
were
thinking
about
just
in
the
context
of
dependencies.
But
I
know
we've
had
that
in
other
working
groups
and
metrics
as
well,
where
we've
had
to
decide.
This
is
how
we're
defining
this
thing,
and
maybe
we
need
a
sort
of
a
central
place
for
that.
F
C
I
agree
I
mean
we
definitely
discussed
it
a
lot
in
the
last
risk
meeting
I
mean
all
the
notes
from
it
are
all
those
different
definitions
and
I
think
what
the
group
needs
we'll
bring
back
to
the
larger
community
is
some
some
boundaries
and
definition
around
those
things
I
mean,
I
think,
that's
that's.
Why
we're
discussing
what
we're
discussing
right
now.
B
B
I
like
that
better
than
simply
linking
between
like
metric
to
metric.
You
know
like
worrying
about
those
we
can
do
it,
but
that
can
get
kind
of
thorny
kind
of
quickly.
So
I'm
just
listening
to
the
conversation.
B
C
Yeah
and
it's
you
know,
it
starts
with
full
request,
merge
success
and
how
long
that
takes.
Those
are
common
questions
and
immediately
sort
of
drifts
into.
How
are
we
treating
newcomers?
Are
they
coming
back
and
that's
building
the
community
and
then
quickly,
as
you
build
a
software
asset,
the
dependency
problem
starts
to
sort
of
lurch
toward
the
top
of
your
list.
C
So
I
mean
those
three
things
seem
to
be
quite
common
and
the
dependencies
have
been
operationalized
up
until
this
point,
as
just
through
entirely
a
licensing
view
which
agar
provides
right
now,
and
I
think
that's
had
some
utility
to
help.
People
understand
code
risk,
but
it
doesn't
really
give
them
that
software
dependency
sustainability,
understanding
that
we're
pursuing
now.
H
So
the
the
kind
of
the
prototype
displays
that
that
I've
created
so
far
have
actually
been
connected
to
those
initiatives.
H
So
I
have
a
prototype
that
basically
looks
at
all
of
the
metrics
that
go
into
the
the
diversity
and
inclusion
event
badging,
and
then
I
have
one
that
would
connect
to
the
the
community
reports.
So
we
we
could
build
those
based
on
community
reports,
dashboards,
the
badging
things
alternately
we
could.
We
could
also
build
them
based
on
issues
and
poll
requests
right.
These
are
all
the
metrics
that
have
been
defined
across
chaos
that
point
at
understanding,
issues,
yep
or.
B
B
Are
you
concerned
about
people
leaving
your
project
for
I'm
totally
making
these
things
up,
but,
like
are
you
concerned
about
people
leaving
your
project
in
favor
of
another
open
source
project?
You
know.
How
can
you
come
to
understand
that
migration
and
what
can
you
do
to
try
to
just
whatever
like
understand
that
more
deeply
like.
C
F
H
I
think
these
these
would
need
to
be
bounded,
though
you
wouldn't
want
too
many
metrics
attached
to
these.
These
ideas
right,
maybe
look
at
you
know
10
metrics,
that
can
give
you
insight
on
this
one
thing
at
most
more
more
than
that
would
probably
lead
to
confusion.
A
It
might
be
interesting
to
lump
them
by
size
of
project
or
or
age
of
project.
You
know,
like
new
projects.
Generally,
probably
have
you
know
a
certain
set
of
things
that
they
care
about
versus,
like
an
old
established
project,
might
be
looking
at
a
totally
different
set
of
of
things.
So
to
your
point
matt,
I
think
that
is
really
cool.
A
I
think
that's
a
really
great
idea,
so
that
would
be
a
little
more
compelling
for
someone
who
comes
to
the
site
instead
of
just
being
presented
with
a
list,
a
laundry
list
and
they
all
are
equal.
You
know
equally
presented,
so
it's
really
hard
to
know
like.
Where
do
you
start
so?
But
if
you
see
a
story
that
fits
what
you're,
what
how
you
identify
right
there
at
your
with
your
project,
then
that
will
be
way
better
and
way
more
effective
for
for
the
people
who
are
trying
to
use
this
like.
H
It
would
be,
it
would
be
nice
if
we
could
link
those
to
an
auger
or
a
gremore
lab
dashboard
or
provider.
C
C
C
A
C
A
G
A
C
Since
last
since
last
month,
really
the
biggest
things
that
we've
done
is
start
work
on
working
on
some
new
metrics,
and
maybe
we
proposed,
I
think,
was
last
weekly
meeting
the
possibility
of
like
the
boundaries.
We've
got
some
boundaries
that
we
discussed
about.
C
When
do
we
put
a
metric
update
through
community
review
and
had
a
long
discussion
about
that,
and
I
think
when
the
when
the
evolution
groups
meet
meets
again
next
week,
we'll
we'll
sort
of
work
towards
using
those
guides
that
were
provided
in
the
either
last
week's
discussion
or
two
weeks
ago
about
you
know
what
should
we?
When
should
we
put
it
through
community
review?
C
C
So
that's
that's
kind
of
and
we
got
a
pull
request
from
one
potential:
google
summer
code,
student,
who's,
cleaned
up,
some
other
repos
that
took
on
evolution
and
just
a
couple
small
changes
and
I
think
we'll
actually
get
cleaned
up
pretty
fast.
A
A
Okay,
let's
move
on
to
the
dei
and
the
dni
badging
pro
sorry
initiatives
there.
Anyone
want
to
take
a
stab.
I
don't
know
matt
g,
if
you
want
to,
I
can,
if
you
don't.
A
I
just
talk
a
lot
in
these
meetings,
so
I
don't
want
to
hog
it,
but
yeah
dni
badging
is
exploding
with
applications.
We
had
11
come
in
at
one
time
and
they
were
all
related.
They
were
part
of
the
kubecon
group
so
and
all
of
those
related
activities
and
mini
conferences
around
that.
So
congratulations
to
the
whole
team.
I
mean
it's
just
fantastic,
this.
The
exposure
that
we're
getting
from
that
dni
badging
initiative.
A
You
know,
matt
snell,
is
just
doing
an
amazing
job
and
he's
been
training
a
bunch
of
new
reviewers,
myself
included
so
yeah,
it's
been,
it's
been
fantastic
and
it's
a
really
interesting
thing.
So
I
think
we're
we're
good
on
reviewers,
but
if
anyone
is
interested
in
becoming
a
reviewer,
I'm
sure
that
matt
would
be
more
than
welcome.
A
I'm
more
than
happy
to
give
you
an
orientation
just
in
case,
because
I
think
that
there
are
some
more
applications
that
are
coming
what
he
said
in
this
meeting
this
morning,
the
badging
meeting
this
morning
so
yeah.
So
if
anyone
is
interested,
it's
super
easy.
It's
not
difficult,
but
it
is
very,
very
interesting
work
and
so
feel
free
to
reach
out
to
matt,
snell
or
or
me,
and
I
can
put
you
in
touch
with
them.
There
is
an
application
too
that
I
can
send
to
you.
They
can
fill
out
anything
else.
B
I
would
just
like
to
say
I
mean
we,
we
badged
kubecon
right
with
our
biggest
the
biggest
application.
Yet
so
that's
super
cool,
and
it's
just
and
wendy,
I
think,
is
her
name
based
on
her
handle
is
just
been
amazing
in
terms
of
not
only
the
applications
but
responding
to
the
comments
and
questions
and
the
issues.
B
B
A
The
only
other
thing
I
would
add
is
that
you
know
one
of
the
goals
of
that.
That
initiative
is
to
help
organizers
find
ways
to
improve,
and
I
think
that
some
of
those
conversations
have
actually
affected
how
they're
going
to
present
data,
especially
around
like
demographics,
and
things
like
that.
So
you
know
it's
not
just
like
hey.
They
did
this
thing,
here's
a
badge
back
and
forth,
but
there's
actually
like
this.
A
This
collaborative
effort
to
just
make
the
events
better
in
general,
so
it
was
very
cool
to
see
that
some
of
our
questions
prompted
them
to
make
some
changes
on
their
end
as
well.
So
I
think
that's
really.
The
whole
point
is
that
we're
just
trying
to
make
everything
better
through
this
process.
So
that's
just
fantastic
to
see.
I'm
really
excited
about
that.
It's
really
great.
A
Yeah
as
soon
as
I
I
think,
wendy
and
we
can
certainly
ask
they're
we're
still
going
through
them,
but
I
think
when
it's
all
said
and
done,
then
I
think
definitely
a
good
candidate
for
that.
So
that's
a
great
idea.
E
B
B
B
E
Yeah,
no,
I
think
that
I'm.
This
is
a
personal
plug,
not
a
plug
with
interest
here,
because
I
was
working
with
the
kubernetes
community
on
their
community
survey
and
there
were
some
issues
around
asking
demographic
questions
and
part
of
it
was
because
the
cncf
wanted
to
have
more
influence
over
what
was
asked
and
when.
So,
it's
just
interesting
to
see
that
it's
now
being
asked
as
part
of
this.
E
So
I'm
wondering
where
that
handoff
is
and
if
we
were
just
totally
different
people,
because
that
could
happen,
but
that
could
hopefully
improve
our
process
of
getting
things
like
that
into
the
right
place.
So
just
more
of
a
like
trying
to
fix
a
another
dysfunction,
and
thankfully
everything
is
publicly
documented,
perfect.
B
A
And
just
from
the
dei
working
group,
I
think
the
main
thing
is
still
working
on
some
metrics,
some
new
metrics,
just
as
everybody
else
is
doing,
but
I.
B
Will
say
that
there
was
a
there
was
a
revision
of
the
metric
that
we
had
talked
about.
So
one
of
the
one
of
the
metrics
was
with
respect
to
speaker
demographics,
and
we
wanted
to
ensure
that
so
we
modified
that
metric
and
it's
going
into
the
badging
program
to
ensure
that
if
there's
a
selection
process
of
keynotes
there's
a
way
to
ensure
diversity
in
keynotes.
C
B
Well
as
diversity
in
the
teams
that
are
selecting
keynotes,
as
well
as
how
the
conference
is
arranged
to
make
sure
that
there's
no
people
involved
in
the
in
the
conference
who
are
marginalized
as
part
of
that
scheduling.
So
this
was
an
addition.
This
was
kind
of
something
that
revealed
itself
to
us,
as
we
were
going
through
this
process
as
well,
that
we
need
to
strengthen.
A
Okay,
we
have
seven
minutes
left.
We
have
quite
a
lot
of
things,
so
we
might
not
get
everything.
Apologies!
Let's
talk
about
value,
real,
quick
vanilla.
Do
you
want
to
give
a
quick
update.
F
H
A
project
popularity
was
released
when
was
that
released.
A
A
Okay,
thank
you,
venad
for
being
so
efficient
with
the
meeting
time
and
everything
you
had
it
all
together.
I
love
it
so
much.
Okay,
let's
go
ahead
and
move
on
today
we
actually
hosted.
Well,
I
say
we
like,
I
did
any
of
it
sean
I
actually
did
all
of
it
hosted
the
first
chaos
software
tutorial
workshop
this
morning.
C
Yep
and
so
we
had
five
people,
and
I
think
some
people
got
a
lot
out
of
it
and
I'm
it's
hard
to
know
it
wasn't
a
real
chatty
group,
but
we
we
talked
through
and
walked
through
an
auger
installation
and
encountered
sort
of
the
real
issues
that
you
encounter
when
you're
setting
up
a
python
development
environment
using
a
database
and
web
servers
and
those
kinds
of
things,
and
so
we
actually
updated
some
augur
documentation
that
will
be
released
here
later
today.
C
Try
to
make
it
slowly
a
little
bit
more
clear
for
folks
and
and
so
yeah.
This
has
been
so
far.
It's
been
a
great,
I
mean
it's
been
one,
but
it's
it's
been
great,
because
it's
helped
helped
us
to
help
us
to
see
the
holes
in
our
docks
and
also
just
I
think
we
were
able
to
show
both
the
auger
tool
and
the
auger
community
reports
tool
and
we
updated
both
of
them
during
the
hackathon
based
on
discussions
and
feedback.
So
I
thought
it
was
that
was
sex.
It
was
a.
C
I
had
a
good
first
experience
myself
and
I'm
hopeful
that
you
know
that
will
continue.
You
know.
A
And
we'll
keep
announcing,
because
I
know
it
takes
a
lot
to
sift
through
to
burst
through
the
noise
of
twitter,
so
we'll
keep
tweeting
about
them
as
well.
We
and
there's
a
whole
series
of
these,
which
is
now
I
see
on
the
website.
Thank
you
kevin.
So
the
link
is
in
the
minutes.
If
anybody
wants
to
sign
up,
there's
various
topics:
jupiter
notebooks
and
wrestle
api
development,
other
things
so
take
a
look
at
that
and
they're
all
free
and
they're
all
at
the
same
time,
8
to
10
a.m.
U.S
central
times.
H
You
will,
I
can
write
it
I'll
I'll
I'll.
Take
a
look
at
the
what's
been
tweeted
so
far.
Maybe
I
can
just
throw
something
together:
real
quick.
A
A
Okay,
we
have
two
minutes
quickly.
Do
you
want
to
talk
about
the
privacy
statement
matt.
B
A
Thank
you
for
doing
that.
Matt
gsoc
applications
are
due
april
13th.
So
if
you're
a
student-
and
you
want
to
do
it,
you
better,
do
it
quickly.
The
next
one
is
all
things
open.
Cfp
is
open,
that's
just
an
fyi.
We
can
talk
about
it
next
week.
If
we
want
to
talk
about
it
more,
I
really
sorry
to
just
jump
ahead.
I
really
wanted
to
hear
the
podcast
update
from
gayorg,
so
you
want
to
talk
about.
What's
going
on
with
chaos
cast.
D
Chaos
cast
is
about
to
turn
one
euro.
We
have
one
more
month
until
the
first
released
episode
was
released
and
yeah.
We
have
currently
for
more
than
4
000
downloads
across
all
of
our
31
episodes.
The
last
one
really
exploded
with
more
than
600
downloads
in
the
first
seven
days,
so
that
was
a
huge,
huge
jump.
B
D
B
A
Cool
okay:
we
are
at
time
anybody
have
any
final
quick
comments,
thoughts.
Anything
before
we
go.
E
All
right,
then,
oh
sorry,
while
we
were
talking,
I
outlined,
and
maybe
a
blog,
because
that's
where
my
head
is
right
now:
what
is
your
process
for
blogs
from
contributors.
H
It's
in
the
community
folder
and
inside
the
community
folder
the
the
news,
the
news
folder
within
the
community
folder.
I
can
give
you
a
link
if
you'd
like
okay.