►
From YouTube: CHAOSS Weekly Community Call 10-13-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
Hey
everyone
welcome
to
october
12th
tuesday
edition
of
our
community
call
for
chaos.
I'm
elizabeth,
I'm
the
community
manager
and
I
have
enabled
the
live
transcription,
but
you
can
so
you
may
have
to
do
that.
Personally,
I
don't
know
if
it
shows
up
for
everybody
or
if
you
have
to
go
in
and
do
that.
But
if
you
want
that
that's
available
to
you,
I
will
type
the
agenda
and
minutes
here,
one
more
time
and.
A
A
So
what
is
that
better
to
ask
for
forgiveness
than
permission
or
something
like
that,
so
yeah
we'll
see
how
that
how
that
all
turns
transcribes
or
transpires?
I
should
say
okay,
so,
let's
get
started.
Let
me
just
share
my
screen.
A
And
we
can
go
from
here,
so
the
first
thing
is:
there's
some
of
the
chat
went
over.
The
first
thing
is
just
in
case
anyone
missed
it.
They
did
announce,
I
should
say
demetrius
from
github
announced
at
one
of
the
keynotes
at
ossna.
A
That
all-in
is
now
open
and
if
you've
not
heard,
chaos
is
one
of
the
founding
partners
of
this
project.
So
we're
super
excited
I
was
really
well
received
and
if
you're
not
familiar
with
it,
it's
it.
The
aim
of
it
is
to
open
source
quote:
unquote:
diversity,
equity
inclusion
in
open
source,
so
there's
a
bunch
of
different
companies
and
organizations,
universities
that
are
all
coming
together
to
try
to
work
on
this
work
on
these
issues
together
in
a
transparent
and
iterative
and
collaborative
way.
So
chaos
is
really
happy
to
be
part
of
that.
A
For
obvious
reasons,
we
care
a
lot
about
diversity,
equity,
inclusion
here,
but
also
open
source
health
in
general,
so
that
it's
really
great
there's
two
sides
of
this
there's
an
all-in
for
maintainers
and
then
all
in
for
students.
Chaos
is
mostly
going
to
be
helping
out
with
the
all-in
for
maintainers.
A
So,
there's
that
right
now
they're
doing
a
maintainers
listening
tour,
so
listening
to
open
source
maintainers
on
what
challenges
they
have
trying
to
improve
diversity,
equity,
inclusion
in
their
projects,
things
that
they're
doing
well
things
that
they've
tried
and
haven't
worked
or
have
worked.
So
it's
just
a
really.
It
is
what
it
says:
it's
just
a
listening
tour,
so
just
listening
to
what
maintainers
have
to
say
and
then
from
there
that
will
kind
of
guide
the
rest
of
the
project.
So
I
think
it's
overall
there's
a.
A
I
dropped
the
link
in
here
in
the
minutes
right
here,
if
you're
interested
in
reading
more
about
it.
It's
it's
all
right
there.
So
does
anybody
have
any
questions
or
something
to
add
to
that?
I'm
looking
at
you
matt
and
sean
for
that,
but.
A
Okay,
then
we'll
just
move
on
okay,
so
I
was
getting
ready,
so
josh
had
submitted
a
pr
to
add
this
reference
to
the
readmes
for
all
the
working
groups
and
if
you
were
not
present
when
we
had
this
conversation
a
few
weeks
ago
months
ago,
I
don't
know
when
about
this
new
thing
that
github
has
called
the
citation.cff
file.
A
We
did
talk
about
that
in
the
value
working
group
and
then
as
well
in
the
community
group,
but
as
I
was
going
to
merge
in
yash's
pr
to
add
that
there
were
some
questions
that
came
up,
so
we
just
wanted
to
kind
of
revise
this
or
revive.
A
I
should
say
I
can
talk,
revive
this
conversation
and
allow
those
who
have
not
had
a
chance
to
participate
in
the
conversations
before
to
to
express
their
concerns
and
I'm
looking
for
kevin-
and
I
don't
see
him
here-
he
was
kind
of
the
one
that
wanted
to
I'm
here.
D
So
I
I
see
that
sean
had
put
a
put
a
question
in
too
and
that
that's
actually
very
similar
to
my
question,
so
it
looks
like
right
now
this
we're
set
up
to-
or
I
should
one
of
my
questions.
It
looks
like
right
now
we're
set
up
to
cite
the
working
group
repository
and
the
question
I
have
is
why
why
are
we
going
at
that
level?
So
the
the
the
metrics,
the
metrics
that
we're
releasing
they're,
not
software
they're
documents.
D
So
would
we
be
better
off
using
a
some
sort
of
documentation,
citation
format
rather
than
this,
this
software
citation
format
that
we're
using,
and
by
that
I
mean,
should
we
be
citing
the
individual
metrics
rather
than
the
working
group
repo
and
then
the
the
other
question
that
you
have
here
is
or
or
should
we
just
or
do
we
just
want
to
have
a
blanket
citation
for
chaos
in
general.
D
So
I'm
not
sure
so
I
know
I
know.
Github
has
given
us
the
ability
to
do
the
the
citation
citation.cff
file,
but
that
that
really
is
designed
for
software,
and
I
I
don't.
I
don't
think
it
fits
as
well
for
individual
documents.
C
Do
we
want
that
to
be?
At
the
I
mean,
I
think,
the
repo
level
or
the
all
of
chaos
level
are
the
two
ways
that
we
could
cite
it
using
this
kind
of
file,
and
that
would
make
that
would
make
sense
and
it
would
be
less
maintenance
work
than
if
we
created
citation
files
for
every
single
metric,
which
seems
a
bit
too
granular
for
what
we're
working
on.
D
Alternatively,
we
could
just
provide
a
recommended
citation
for
the
individual
metric
at
the
bottom
of
the
metric
page,
similar
to
what
we're
doing
now
and
not
link
out
to
a
cff
file.
It's
just
like
this
is
our
recommended
citation
which
would
be.
It
would
be
fairly
easy
for
us
to
create
and
keep
maintained,
because
it
would
be
part
of
the
metric.
D
So
when
we,
if
we
were
to
do
if
we
were
to
try
to
do
an
individual
metric,
cff
file
or
even
a
repo
cff
file,
that's
one
more
file
that
we
need
to
keep
updated
and
maintained.
E
Update
like
the
contributor
list.
B
D
And
those
contributor
lists
are
opt-in
lists,
so
you,
basically
you
have
to
add
your
own
name
to
them
as
we're
as
we're,
creating
them
or
editing
them,
and
we
do
not.
We
don't
really
go
out
of
our
way
to
add
people
to.
G
Them
yeah,
in
any
case,
I
think
doing
the
citation
at
a
repo
level
makes
the
work
much
more
consistent
with
the
works
that
are
already
available,
because
if
somebody
is
signing,
let's
say
at
the
evolution
or
rakes,
you
might
be
talking
about
something
specific
and
you
want
to
cite
the
entire
thing.
Just
as
when
we
cite
papers,
we
don't
cite
the
particular
chapter
or
the
page.
G
If
you
are
using
the
ieee
beside
the
paper,
I
I
know
there
are
other
citations
like
the
epa
that
can
do
something
different,
but
if
we
go
at
the
ripple
level,
I
mean
it's
easy,
like
even
suggested
it's
easy
for
me
nuns.
It's
easy
for
things,
then
notwithstanding
we
can
have
one
bigger
thing,
let's
say
for
the
kiosk
project,
because
sometimes
people
are
referencing
the
kiosk
project
and
they
know
we
handle
metrics
for
community
health.
G
I
Yeah
my
analogy
for
citation
was
for
yours
as
a
like
chaos
is
a
book
and
each
repo
is
a
chapter.
So
if
you
cite
a
chapter,
there's
a
way
to
cite
a
chapter,
if
you
cite
a
book
in
entirety,
there's
a
way
to
cite
it
so
providing
a
citation
to
each
repo
is
just
like
similar
to
providing
a
citation
for
a
chapter
and
just
writing.
The
entire
book
is
a
you
can
just
do
that.
So
for
me,
like
my
two
cent,
suggestion
is
for
a
repo
level.
D
So
the
the
working
group
categorizations
are
a
little
bit
arbitrary
right,
so
it's
just
it's
wherever
the
metrics
are
being
worked
on,
sometimes
the
sometimes
that
categorization
makes
sense,
and
and
sometimes
it
doesn't
so
I
I
don't-
I
don't
think
citing
it
by
the
working
group.
Is
that
helpful?
Actually,
I
think
I
would
prefer
to
see
it
cited
at
that
high
level
chaos
level
using
the
c
ff
file
and
then
maybe
have
a
recommended
citation
at
the
bottom
of
each
individual
metric.
E
B
B
You
know
kind
of
move
across
chapters
or
working
groups,
so
to
speak,
but
I
I
don't
know
I
think
it's
okay
to
at
least
we're
just
trying
to
locate
people
to
a
spot.
B
That's
all,
and
I
just
think
the
easiest,
whatever
the
easiest
way
to
do.
This
first
is
probably
best.
So
even
I
mean
my
inclination
is
maybe
just
to
do
it
at
the
chaos
project.
Full
stop
and
just
see
what
the
uptake
is
on
that
before
we
over
complicate
and
put
things
even
at
lower
levels.
So
I
don't
even
I
don't
even
know
how
well
people
will
say
just
the
chaos
project.
G
G
We
we
had
this
citation
from
for
for
exe
and
the
people
went
through
the
working
group.
I
think
at
that
moment
there
was
some
broken
links
or
things
something
like
that,
but
they
actually
had
to
look
at
other
metrics
that
we
did
not
really
mention
just
commenting
on
those
gave
us
some
kind
of
insight
that
they
are
taking
it
seriously
because
they
were
actually
saying:
okay
yeah.
These
people
cited
this
kiosk
project.
They
work
on
this
and
we
saw
you
know
they
looked
the
kiosk
project
as
we
are
having
some
important
discussion
around
this
metrics.
G
So
for
that
working,
I
just
think
it's
an
indicator
like
a
pointer,
then
I
still
strongly
suggest.
Chaos
is
just
the
way
the
bigger
discussion
happens.
Going
down
at
the
lower
level
of
granularity
might
be
too
much
work
which
cannot
really
impact
more
than
because
I
mean
there
are
tons
of
metrics
and
when
those
citations
are
so
many.
If
you
have
to
cite
let's
say
four
metrics,
then
just
imagine
the
bulk
of
work,
but
one
citation
can
work
for.
D
G
That
I.
D
Think
that
kind
of,
I
think,
that's
kind
of-
would
resolve.
Maybe
all
of
the
discussions
we're
having.
I
We
keep
the
same
cff
file
and
all
the
repos
just
for
a
access
purpose
like
sometimes
people
are
just
looking
at
a
particular
repo
and
easy
to
find
the
cff
file
within
that
repo.
That's
just
one
maintenance
asset.
I
B
A
I
was
gonna
strike
through
that,
but
I
couldn't
figure
out
how
to
do
that.
So
I
just
deleted
that
part
about
the
putting
the
cff
file
in
the
in
each
metric.
So
it
sounds
like
we've
come
to
kind
of
an
agreement
to
put
have
people
cite
chaos
in
general,
we'll
put
a
link
to
the
cff
file
and
then
create
a
pointer
to
it
in
the
community,
repo
everybody
cool.
With
that
do
we
have
any
other
comments,
questions!
A
Okay,
I
will
do
that.
A
There
we
go
boom
done
moving
along
a
sign.
Okay,
let's
talk
about
the
metrics
release.
I
believe
this
is
going
to
be
kevin
as
well
put
that
in
there.
D
Yep,
this
is
just
me
repeating
what
I
had
said
last
week,
so
just
a
request
that
all
the
working
groups
go
in
and
review
their
metrics
and
edit
them
and
the
the
target
that
I
would
would
like
them
to
shoot
for
is
october
15th,
so
that
we
can
get
the
release
ready.
For
I
think
october.
18Th
is
the
target
date
and
then
also
make
sure
you're
updating
the
translation
repo
when
you're,
when
you're
making
those
edits
so.
D
And
then
we
do
have
we
we,
we
have
come
across
an
issue
with
the
with
the
metrics
release
and
the
standard
template.
Currently
the
the
way
we
the
way
the.
D
The
way
the
website
is
generated
currently
we're,
we
pull
markdown
files
into
the
website
and
then
it's
converted
into
html
and
in
that
process
some
of
our
relative
links
are
being
destroyed.
So
we're
we're
trying
to
figure
that
out
currently
and
it
does.
This
issue
is
affecting
the
mars
automated
metrics
release
as
well.
So
we
have
some
possible
fixes.
D
D
K
Yeah,
I
would
like
to
add
in
comment,
even
if
we
are
using
the
absolute
links
instead
of
relative
links,
I
think
we
have.
We
have
found
a
way
to
adapt
mars
to
use
the
absolute
links,
so
you
can
find
the
link
for
the
possible
fix
that
contains
the
fix
for
converting
absolute
to
relative
links,
while
using
mars.
K
A
B
Oh
okay,
like
just
in
terms
of
like
for
the
metrics
release
lucas.
B
D
Is
that
just
removing
the
the
disclaimer
header
text.
I
A
That
way,
we
can
get
that
sorted
for
kevin
and
the
team
by
whatever
day
the
15th
is
friday.
I
guess.
D
So
when
we,
when
we
go
through
to
start
doing
the
release,
if
I,
if
we
find
some
that
that
still
need
to
be
looked
at,
I
will
start
tagging
people.
D
So
so
maybe
maybe
another
request
I
would
have
is
that
if
during
this
process,
if
I,
if
I
tag
you
in
a
pull
request
or
an
issue,
if
you
could
try
to
be
responsive,
that
would
be
very
helpful.
A
Okay,
let's
move
on
then
so
it
occurred
to
me
that
we
never
in
the
confusion
of
chaos,
con
os,
sna
metrics
release.
We
never
really
talked
about
hacktoberfest
which,
if
you're
not
familiar
with
it,
runs
through
the
month
of
october
and
it's
supposed
to
bring
people
in
to
open
source
who
have
never
maybe
submitted
a
pull
request
before
so
we
have
participated
in
the
past
with
varying
results
just
wanted
to
bring
that
up.
If
we
want
to
participate
like
it's
already,
the
12th
so
yeah.
A
I
don't
know
what
do
y'all
think.
C
A
A
D
Now
it
seems
like
it's,
it's
become
a
little.
I
suppose
you
could
it's
gamified
right,
so
they're
people
are
doing
minimum
effort
to
get
the
t-shirt
or
to
say
that
they've
participated.
I'm
not
I'm
not
sure.
Hacktoberfest
has
a
great
reputation
with
open
source
projects
over
the
over
the
past
couple
years.
I
know.
A
Okay,
so
I'm
just
gonna
say
probably
a
thumbs
down
then,
for
that.
B
H
B
C
I
mean
I
think,
in
the
past
we've
we've
not
had
quite
enough
money
to
invest
in
things
or
people
that
we
wanted
to
invest
in.
So
what's
our
total?
Do
we
know
it's
roundly
roughly
over
10
000,
okay.
I
C
B
Probably
would
cover
an
outreachy
person
or
come
pretty
close
that
wasn't.
I
was
just
asking
if
we
wanted
to
invest
the
money,
that's
like
right,
well,
spend
it
like
if
we
wanted
to
support
other
projects
or
do
our
reaching,
but
I
mean
these
are
good
investments.
We've
made
before
this
way.
Why
not
like
invested
in
the
stock
market?
B
I
meant
like,
invest
it
like
in
a
mutual
fund,
and
we
that
was
like,
quite
literally,
I
just
meant
like
take
like
two
thousand
dollars
and
we,
but
I
I
we're
not
really
set
up
to
do
this.
I
don't
know
if
we
can
do
it.
I
it
was
just
something
I
thought
that
came
to
my
mind.
I
just
kind
of
hate
looking
at
dollars
just
sit
there
as
cash.
E
D
I
mean
if
we
were,
if
we
were
to
in
invested,
we
probably
would
probably
need
to
decide
how
much
money
we
would
want
to
keep
in
an
operations
account
and-
and
my
guess
is
I
mean
10
000-
is
probably
a
pretty
good
number
for
an
operations
account
for
us,
because
our
we
don't
have
a
ton
of
costs.
D
I
mean
this.
This
money
is
primarily
used
to
run
chaos,
cons
and
possibly
mentorship.
O
I
I
would
be
inclined
if
you
want
to
invest
the
money,
to
invest
it
in
something
that
advances
the
chaos
community,
sponsoring
travel
for
chaos,
con
speakers
or
something
like
that
or
having
swag
that
we
give
to
all
chaos,
members
or
yeah.
I
agree
paying
an
agency
to
redo
our
website
or
paying
for
outreachy
students.
These
are
all
things
that
invest
in
the
community
itself.
B
This
wouldn't
be
like
against
that
I
mean
that
could
still
occur.
This
is
just
I've
been
looking
at
these
accounts
sitting
as
cash
accounts
ever
since
we've
kind
of
started
this
project.
That's
all
the
money's
not
working
like
it's
not
doing
anything.
That's
all
and
I'm
not
saying
like
take
the
entirety
out
and
we
have
no
operating
ability.
It
was
again
it's
just
a
thought
and
it
doesn't
sound
like
it's
being
picked
up
super
well.
So
that's!
Okay!.
O
With
the
I
don't
know
what
what
the
current
rates
are,
but
last
I
checked
they
were
small,
and
so
it
would
be
adding.
I
don't
know
100
per
year
or
so.
O
D
I
would
like
to
I
would
like
to
have
more
conversations
about
how
we
can
invest
that
money
in
the
community
to
what
to
what
george
was
saying,
rather
than
rather
than
just
having
it
sit
there.
What
are
what
are
some
other
things
that
we
can
do
to
help
build
our
community.
H
A
Yeah,
okay,
I
think
we
kind
of
can
probably
move
on
then,
since
we
kind
of
okay,
awesome
and-
and
maybe
it'll
come
back
up,
you
know
it'll
resurface,
maybe
later
on
so
we'll
see
how
it
goes.
But
for
now
we'll
put
that
on
hold
the
next
one.
Is
the
operations
team?
How
should
we
start
organizing
this
work.
B
B
We
might
want
to
think
about
how
we
probably
just
need
to
start
meeting
at
some
at
some
point
and
talk
about
like
what
needs
to
be
done
across
the
project
across
the
chaos
project,
to
kind
of
normalize
work
for
all
or,
for
example,
we
have
the
dei
audit
like
how
we
think
about
rolling
these
kind
of
things
out.
B
A
So
the
action
item
here
is
a
meeting.
B
B
We
think
about
how
that
work
gets
done
and
then
we'd
have
a
team
that
could
kind
of
oh
kind
of
like
what
josh
and
rotek
had
done
over
the
summer.
With
the
release
you
know
kind
of
always
expressing
like
hey
we're
going
to
be
hanging
out
in
your
working
group
for
a
little
while,
and
we
need
to
update
your
readme
files
and
just
so
when
you
see
some
pr's,
that's
what
those
things
are.
A
Do
we
need
to
figure
out
who's
on
this
team?
Do
we
know
who's
on
this
team
already.
C
No,
we
don't
kevin
josh
and
riddick.
I
think.
A
I
L
C
C
D
But
I,
but
I
don't
know
that
it's
necessarily
it
doesn't
necessarily
have
to.
D
A
Okay,
we
have
about
10
minutes
left
and
we
have
a
few
other
things
to
talk
about.
So
let's
go
ahead
and
move
forward.
If
that's
cool
with
everybody,
the
next
one
on
there
is
the
dco
sign
off.
B
So
I
also
put
that
on
there
there
is
an
issue,
and
so
the
the
question
that
had
come
up
and
folks
can
correct
me
if
I'm
not
getting
it
quite
right,
but
the
dco
sign
off
there
it
is
from
matt
cantu
is,
can
really
actually
cause
some
complications
with
people
on
their
pull
requests,
possibly
leading
to
attrition
in
pull
requests
number
one,
and
in
fact
I
think,
if
I
don't
remember
which
one
which
working
group
it
is,
but
I
mean
there's
a
pr
that's
sitting
in
there
that
doesn't
have
dco
sign
off
and
we
really
can't
technically
do
anything
with
it
until
it
has
a
dco
sign
off.
B
But
then
the
other
thing
is
is
that
I
think
dco
requires
that
you
put
your
full
name
and
your
email
address
in
there
that
some
people
may
not
want
to
put
for
a
pr.
B
B
So
anyway,
that's
that's
the
point.
I
thought
we
it
would
be
worth
bringing
it
up
here
see
if
other
people
have
comments.
I
mean
I
followed
the
discussion.
C
On
the
issue
it
seems
it
seems
like
we
have
to
have
it,
so
it's
just
something
we
have
to
work
with.
E
I
want
to
plus
one
that
getting
rid
of
it
or
modifying
it,
find
some
finding
some
other
way
to
do
it.
I
found
that
the
dco
request
can
be
more
work
than
all
the
last
level
project,
so
it
discourages
me
from
doing
stuff.
H
M
I
think
the
the
article
that
was
that
I
shared
in
the
last
section
of
that
issue,
if
you
could
click
on
that,
it
basically
just
says
like
it's,
not
a
cla
and
it
does.
It
does
not
have
it's
just
one
argument
towards
this,
but
that's
kind
of
what
I
agree
with
at
this
point
like
putting
your
name
on
something
does
not
necessarily
mean
you're
signing
anything.
That's
what
I'm
kind
of
trying
to
say
here
is
that
there's
no
context
for
the
agreement.
M
I
don't
know
just
food
for
thought.
I
think
that's.
The
best
argument
we
can
make
towards
the
lf
is
the
legal
aspect
of
it.
O
And
then
now
is
a
good
time
to
check
this
and
review
it,
because
we
need
to
change
the
charter
of
the
chaos
project
where
it's
required,
and
so
that
is
something
the
governing
board
when
we
meet
next
month
no
this
month,
we
can
talk
about
that
and
vote
on
that,
and
then
we
can.
O
If
we
already,
I
know
we
need
to
work
with
the
linux
foundation
when
we
change
the
charter,
so
that
conversation
needs
to
happen
so
matt.
Thank
you
for
checking
on
that.
B
P
Github
what
I
what
I've
seen
happen,
a
lot
is
it's
really
easy
to
get
around
it
and
it
breaks
often,
and
so
sometimes
you'll
get
stuff
in
that's
not
actually
been
done
correctly
and
so
periodically.
P
You
have
to
go
through
and
make
sure
that
everything
was
actually
signed,
and
so
I
suggest
either
monitoring
it
or
doing
a
a
monthly
check
and
going
and
reminding
people
who
put
things
in
that
it
wasn't
done
correctly
to
go
back
in
and
fix
it.
O
P
Yeah
and
it's
and
it's
one
of
those
things
where
there
are
some
weird
things
happening
where
I
think
it
was
breaking
a
lot
on
the
web
interface.
So
basically
anyone
who
is
doing
web-based
was
definitely
not
getting
them
through
for
a
while.
P
I
don't
know
if
that's
still
true,
I
just
know
that
I've
watched
it
break
multiple
times,
and
so
the
command
line
seems
to
do
better,
but
there
were
times
where
we
couldn't
get
things
we
couldn't
get
builds
done
because
of
it,
and
so
they
would
turn
it
off
and
then
forget
to
turn
it
back
on
or
things
of
that
nature.
I
P
P
A
I
have
a
super
quick
question.
Is
this
is
dco?
This
is
just
my
own
ignorance.
Is
it
something
that's
pretty
prevalent
across
open
source,
so
one?
If
that's
the
case,
then
one
thing
we
might
consider
ourselves
is
like
helping
people
figure
that
out,
even
though
it's
a
barrier
to
us,
but
like
maybe
we
can
assist
other
people
in
figuring
it
out,
so
that
it's
not
a
barrier
to
another
open
source
project
that
they
want
to
participate
in.
That
could
be
kind
of
something
we
help
with.
I
don't
know.
P
There
liz
there
is
like
github
knows
and
I've.
This
has
been
a
mini
year's
journey
for
me
of
complaining.
So
yes,
more
people
complaining
on
it
would
be
great,
but
I
don't
know
why
the
hell
they
don't
do
this.
So
I'm
yeah,
it's
it's
been
the
bane
of
my
existence
as
you
can
imagine,
because
I
even
had
problems
with
it
at
paypal.
P
So
yeah,
it's
it's
it's
an
issue
and
github
knows
it's
an
issue,
and
so
I
don't
know
why
they
refuse
to
prioritize
it
because
it's
a
pretty
serious
issue,
but
maybe
more
people
bringing
it
up
will
help.
So
please,
please
also
go
go
hit
him
over
the
head,
like
I
did
for
a
while.
A
I
was
thinking
more
of
like
help
like
documenting
how
to
do
it
through
the
the
command
line
since
that
one's
broken
I
was
thinking
like.
Maybe
we
could
help
people
who
are
new
to
open
source,
you
know
or
new
to
our
project.
Here's
how
you
do
it,
but
I
totally
agree
like
it
should
be
fixed.
P
And
it
still
sometimes
breaks
on
the
command
line
too,
with
a
really
complex
one.
Sometimes
it'll
still
break
there
as
well,
especially
we
had
that
hyperledger,
because
we
had
some
really
complex
things
that
came
through
and
it
would
just
go
and
explode
all
over
the
place,
but
it's
definitely
an
ongoing
thing
with
the
graphical
user
interface.
So,
yes,
most
definitely
and
the.
P
Yeah,
I
know
I
know
it's
like
one
of
those
things
where
I
call
it
one
of
the
dirty
little
secrets
of
github
honestly
at
this
point,
because
I'm
just
like
seriously
guys
come
on
so
yeah.
E
So
I've
seen
a
bunch
of
projects
using
a
cla
checker,
but
the
dco
checkers
is
less
frequent
because
it's
so
and
you
know,
developers
are
as
lazy
as
they
could
possibly
get
away
with
for
good
reason.
P
Yeah
the
cla
checker
that
I've
been
looking
at
is
a
little
bit
different.
It's
basically
making
sure
I
think
mostly
that,
like
it's,
it's
referential
it's
going
through
and
making
sure
that
all
the
people
who
are
doing
the
different
things
are
doing
it,
but
I
don't
know
that
it's
live
so.
E
Well,
I
have
seen
it
used
a
lot.
Okay,.
P
Sorry,
cool
cool
because
the
one
that
I
was
looking
at
it
was
like
something
that
I'd
like
run
periodically
and
then
it
would
tell
me:
oh
yes,
all
of
your
maintainers
are
on
there
and
then
and
then
they
upgraded
it
to
being.
Oh,
yes,
all
of
your
maintainers
and
anyone
who's
done.
A
contribution
has
done
it
and
things
of
that
nature,
but
I
didn't
know
if
it
had
actually
gone
live
yet
I
just
knew
that
it
was
something
that
I
it
was
some
scripts.
P
O
P
Sorry,
sorry
and
it's
harder
to
get
corporate
employees
to
do
the
clas,
it's
and
so
sometimes
that's
why
they
hide
their
work
is
so
that
they
don't
have
to
deal
with
the
corporate
cla
and
so
they'll
go
and
like
be
sneaky
and
sit
down
and
go.
This
means
an
individual
so
that
they
don't
have
to
worry
about.
All
of
that,
because
you
know.
A
Okay,
sorry
to
cut
this
short,
but
we
are
out
of
time,
and
we
had
two
items
left
on
our
agenda
is
that
okay,
matt
c
and
nicole.
This
was
yours.
Your
brand
kit
is
that.
L
A
To
postpone
those
yep
yeah,
okay.
Okay,
thank
you,
sorry
about
that.
We
will
talk
about
those
things
very
first
thing
next
next
week
and
otherwise
we're
good
to
go
thanks.
Everybody
for
coming.
I
will
stop
sharing
thanks.