►
From YouTube: CHAOSS.D&I.May.13.2020
Description
CHAOSS.D&I.May.13.2020
A
B
C
B
A
B
A
You
can
continue
on
or
not
we
can
yeah
I'll
come
back
to
that
one.
So
last
week
we
had
some
recommendations
for
denied
badging
about
automation,
to
take
score
on
for
requests,
which
I
think
is
a
great
idea
and
having
other
ways
to
issue
a
PR,
then
using
github,
which
is
also
a
great
idea
and
I'll
start
with
the
bots.
So
we
haven't
had
a
lot
of
movement
on
this
last
week,
but
it's
something
I've
been
looking
at
myself
and
it
wouldn't
be
the
hardest
thing.
A
Well,
there
might
be
something
that
we
can
do
with
her
with
their
students,
also,
until
though,
specifically
also
for
this
one
but
I
have
to
I'd,
have
to
wait
for
next
week
or
maybe
a
later
week
to
get
more
information
on
that,
because
it
would
be
later
in
the
project
for
the
summer.
What
is
the
request.
A
A
That's
what
I
was
kind
of
looking
into
was
how
to
count
up
values
or
that's
kind
of
related
to
our
other
recommendation
that
people
might
be
intimidated
using
github
issue
a
pull
request
and
get
the
project
get
information
to
the
project.
We
looked
at
this
in
our
Sunday
meeting
for
badging
and
decided
it
was
out
of
out
of
scope
for
the
internship
projects
for
a
scintilla,
but
we
but
Saul
and
I
are
going
to
look
into
that
ourselves
as
I
had
made.
You
can
share
this.
A
A
We've
done
this
global
consent
manager
past
project,
and
it
was
not
the
hardest
thing
to
do,
but
it
would
take
maintenance
every
time
it
would
update
and
it
requires
a
github
login
to
create
the
full
request
anyway.
So
we're
looking
into
our
other
options
for
that.
So
on
IR,
for
that
one
I'm
sorry
can
determine
quickly.
C
Yeah,
of
course,
I
so
yeah,
no
I,
guess
what
we
can
do
with
a
query
parameter
like
a
search
query
and
the
URL
is
open
an
issue.
What
is
what
is
proven,
more
challenging
to
I,
guess
kind
of
like
abstract
in
a
way
that
is
not
github
intertwined
is
how
do
you
go
about
not
opening
an
issue,
but
rather
opening
a
pull
request,
which
is
a
commit
against
repo
that
is
in
the
public
domain?
C
So
so
the
idea
that
you
make
commits
in
the
public
domain
it
takes
that
you
fork
with
your
identity
and-
and
it
takes
that
you
also
have
that
discussion
track
before
it
lands,
and
it
contributes
to
the
repository
with
with
all
parties
identified
for
their
contribution
in
their
stake.
That
workflow
doesn't
happen
with
a
search
query
and
it
will
be
very
API
heavy,
so
we
don't
mind
learning
the
API,
but
we
don't
want
to
abstract
it
in
a
way
that
it's
like
okay,
this
is
where
it's
on
github
never
lost,
because
it
won't
work
elsewhere.
C
B
E
E
Too
often
we
put
documentation
into
a
coding
style
format
with
the
MVS
right
with
the
markdowns,
and
that's
okay
and
I.
Get
it
and
I
understand
why
people
do
it,
but
it
creates
a
pretty
big
barrier
in
regards
to
those
PRS
and
so
I
find
that
you
know
you
really
do
have
to
put
the
documentation
in
to
either
a
wiki
or
pages
paradigm.
So
that
way
the
people
like
get
it
and
they
can
come
in.
E
They
don't
have
this
huge
barrier,
but
with
PRS
and
that's
kind
of
how
I'm
structuring
my
stuff
as
much
as
I
can
going
forward.
I
sit
there
saying.
No,
this
is
the
coding
pieces
and
these
are
the
documentation
pieces,
and
you
know
we're
gonna
have
to
look
at
some
other
assets
to
that.
We're
gonna
start
entering
into
our
stuff
right.
What
am
I
gonna
do
with
graphical
assets.
What
am
I
going
to
do
with
you
know
architectural
assets.
E
How
are
those
all
going
to
work
in
regards
to
get
a
format,
because
once
again,
don't
want
to
do
PRS
for
that,
so
I
totally
get
what
you're
saying
it's
just
one
of
those
things
as
to
where
I
think
we
need
to
start
being
careful
about
our
vocabulary
as
to
what
which
each
of
those
things
mean
you
know,
PR
is
issues
you
know
using
the
wiki's
or
the
pages
instead
and
when
all
that
should
be
done
properly.
So
that's
just
what
I
was
trying
to
toss
in.
Thank
you.
B
Okay,
however,
that
request
comes
in
and
the
request
is
for
a
badge
for
an
event
right
and
so
in
this
scenario,
just
pretend
you
would
be
assigned
a
reviewer
to
review
what
they
have
proposed
in
order
to
receive
the
badge
you
know,
so
they
I'm
the
submitter
and
I
say
our
event
should
give
it
DNI
badge
because
we're
family-friendly,
because
we
have
a
code
of
conduct
and
because
we
do
you
know
we
do.
We
do
these
things
and
then
you're
and
you're,
like
no.
B
You'd,
you
don't
have
any
indication
that
your
family-friendly,
so
so.
There's
this
open
and
transparent
review
that
somebody
like
your
solved,
review
or
robot,
and
the
intention
is,
is
that
that
review
process
is,
is
open
completely
open
and
transparent,
so
that,
if,
if
you
as
a
reviewer
having
more
finding
the
code
of
conduct,
you
can.
B
E
E
You
need
to
have
that
kind
of
guidance
that
you're
talking
about
drug,
and
so
it's
like.
How
do
we
start
to
put
some
of
that
in
there
and
right
now,
what
we
have
doesn't
exist
from
what
I've
seen,
and
so
that
is
one
of
the
things
that
we're
prioritizing
is
working
on.
Something
like
that,
so
that
we
can
actually
have
that.
But
I
guess
like
with
those
kind
of
constraints
what
you're
talking
about,
then
you
basically
have
to
fall
into
a
PRA
that
sucks,
because
then.
F
E
Basically,
working
off
of
this
maintainer
model
again
and
it's
not
a
full
vote
right.
You
know
it's
not
like
you
know.
For
us,
we
do
a
lot
of
stuff
based
off
of
majority,
and
so
you
have
to
have
like
three
quarters
or
something
along
those
lines,
and
you
have
none
of
that
option.
You
just
have
someone
you
know
with
those
permissions
says
yes
yeah,
which
makes
it
tougher,
but
yeah
no
I
see
what
you're
saying.
If
you
need
that
gating
function,
we.
B
E
Well,
one
weird
thing
that
I
did
at
PayPal
that
was
cut
you
know,
is
all
internal.
That
I
did.
That
was
kind
of
interesting
is
I.
Let
them
give
each
other
emojis
and
they
were
specifically
tagged
emojis,
so
that
I
could
have
a
bottom.
It
goes
back
later
and
like
looks
at
it
and
when
they
went
and
did
that,
that
was
like
one
of
funny.
Things
is
that
they
could
go
in
and
they
can
test
them
afterwards,
but
that
wasn't
pretty
so
and
to
be
quite
honest,
because
everything
was
so
transparent,
they
gated
themselves.
E
But
it
doesn't
work
once
you
get
over
150
right
and
when
you
get
over
150,
then
you
get
too
many
trolls
and
every,
but
because
everybody
doesn't
know
everybody
but
ya
know
if
you're
needing
that,
then
yeah
I
get
it
it's
unfortunate.
But
when
we
start
working
on
it,
I'll
ping,
everyone
and
let
him
know
so.
Y'all
can
come
in
and
say
a
bunch
of
different
objects.
E
A
Thank
you
and
something
we've
learned
from
working
with
issues.
Employer
requests
specifically
almost
in
a
vacuum
sometimes,
but
we've
we've
learned
that
the
issues
and
pull
requests
both
have
their
pros
and
cons
as
far
as
like
automation
or
usability
goes
in
all
kinds
of
different
situations,
so
we're
still
or
maybe
even
thinking
about
moving
back
to
the
issue
side
of
things,
because
it
works
better
for
what
we
need.
But
that's
I,
guess
that's
what
we
have
to
consider
in
this
situation.
A
C
C
B
Can
you,
if
somebody
if,
if
I,
understand
solid
that
you're
looking
at
a
variety
of
options,
but
if
somebody
was
to
to
come
to
the
website
in
an
effort
to
give
a
badge
and
the
application
through
the
website
created
an
issue,
I
think
I'm
understanding
this
so
far,
can
can
you
actually
automate
an
issue
such
that
it
makes
a
contribution
to
the
codebase
I
print
out
quite
saying
that
right
at
the
end
properly
there,
but
obviously
a
pull
request
modifies
the
codebase.
That
makes
sense.
But
can
you
do
through
an
issue
well.
C
Ways
where
you
can
do
that
thing
on
web
hooks
or
github
actions
I
think
are
now
becoming
this
standard
for
github
things.
So
we
want
a
parallel
like
we
want
a
none,
github
parallel
of
actions,
and
we
want
to
make
sure
it
ties
to
the
issues
or
they're
parallel
elsewhere
and
we
can
be
as
abstract
or
generic
as
possible.
Okay,.
C
B
B
A
A
E
No
I
was
just
talking
about
how
we're
actually
backwards
in
doing
it
right
now
at
I,
Triple
E,
because
we've
got
about
15
standards
that
are
coming
through
the
open
source
portion
and
so
we're
putting
it
in
there
and
some
of
the
open
source
coding
or
data
or
other
different
people
or
other
different
artifacts
are
part
of
the
actual
standard.
So
it's
a
badge,
but
it's
like
the
hardest
core
bad
you've
ever
imagined.
E
E
But
it's
like
really
hard
coded
right
now
and
we
are
using
shoes
and
we
are
using
labels
and
it
is
monitored
by
staff
and
there's
a
whole
bunch
of
different
things.
That
happens
in
regards
that,
where
we
have
to
be
hardcore
but
yeah,
that's
that's!
That's
how
we're
doing
it
right
now
is
we're
being
we're
managing
it
stock
wise,
but
that's
one
of
the
things
we're
looking
at
automating
kind,.
E
Is
very
heavy
yeah
josh
is
doing
way
too
much
work
on
it,
but
right
now
we're
also
getting
through
all
of
our
use
cases.
Thankfully,
since
we
weren't
heavy
at
the
beginning,
we
were
able
to
do
things
like.
Oh
you
realize
we
realized.
Oh
data
could
be
part
of
a
standard,
that's
cool.
We
have
that
example
now
which
I
don't
think
we
would
have
gotten
to
had
we
not
been
so
organic
at
the
beginning.
E
F
In
the
chat
versus
in
the
meeting
itself,
because
I'm
just
curious,
where
you're
coming
from
that
on
Saloon
so
cilona,
because
we
worked
really
hard
to
make
them
the
same
so
totally
off
track.
Please
answer
in
the
chat,
so
we
can
go
back
to
their
normal
agenda
and
I
don't
disturb
the
meeting
as
normal.
The
only
real,
usually
Amy
is
user
experience.
We.
E
Have
a
lot
of
much
older
people
that
are
not
coders,
and
since
we
are
doing
things
like
open
science
and
open
hardware
and
a
bunch
of
different
groups
that
aren't
used
to
github
or
get
lab.
They
don't
understand
the
paradigm
and
they
are
only
working
on
documentation.
And
so
it
ends
up
being
kind
of
a
significant
lift
to
get
them
to
go
in
there
and
do
that.
And
it
makes
it
way
too
slow
and
they
get
really
frustrated.
Getting.
E
Yeah,
no,
it's
just
it's
just
one
of
those
things
where
it's
much
easier.
Just
to
have
them,
you
know,
I
can
I
can
get
them
over
to
a
wiki,
because
they're
used
to
Google
Docs
now,
but
I
can't
get
them.
I
mean
I'm
dealing
with
people
who
are
used
to
still
dealing
with
pass
around
Word
documents.
Yes,
Arenado.
F
E
F
A
B
B
A
B
B
Say
one
thing:
I,
just
I
didn't
want
to
congratulate
Tola
and
hasta
for
hasta
was
accepted
for
a
google
Summer
of
Code
to
be
part
of
the
badging
program.
So
it's
official
and
Tola
was
accepted
as
an
outreach,
D
student
also
working
on
the
DNI
badging
program.
So
it
is
absolutely
wonderful
to
have
both
both
of
you
participating
in
this
project
under
both
of
those
really
great
programs.
B
A
A
A
A
B
Yeah
I
guess
one
of
the
can
ask
a
question
for
people,
so
this
is
so
for
those
of
you
that
kind
of
don't
know
the
history
right.
So
this
was
all
one
metric
at
one
point
around
documentation,
issues
of
accessibility
and
discoverability
seem
to
be
confounded
on
the
single
metric,
so
the
proposal
was
to
break
it
out
into
three
metrics.
The
the
single.
B
B
B
On
the
number
three-
and
it's
like
an
accordion
right,
so
we
we
expanded
the
first
one
I
would
really
like
to
three
and
then
we're
trying
to
bring
them
together
and
off.
I,
don't
know
if
this
is
making
any
sense,
but
these
are
very,
very
hard,
they're,
very
nuanced,
to
separate
out.
That's
all
and
personally
I
have
a
really
hard
time.
Yeah.
C
So
so
you
you're
you're,
trying
to
take
one
one
big
problem,
documentation
and
you're
trying
to
divide
it
in
such
a
way
so
that
people
know
where
to
look
if
they
had
not
looked
I,
don't
know
that
makes
and
well
said,
I
think
the
pie
metaphor
was
was
good,
though
so
you
know
it
come.
It
boils
down
to
agreeing
on
terminology,
and
you
know
once
you
have
to
agree
on
many
terminologies.
C
I've
done
terminology-
and
you
know
great,
you
know
honestly
for
for
my
thesis
and
for
the
work
I
do,
but
I
could
tell
people
like
here's
the
terminology,
you
know
just
live
with
it.
You
know,
but
once
you
want
people
to
agree
on
the
same
terminology,
it
takes
time
for
everyone
to
appreciate
the
importance
of
every
single
piece
of
that.
So
that
takes
time.
B
C
B
C
F
B
C
C
B
A
The
information
overload
is
apart.
There
I
didn't
want
to
mention
those
in
the
resources
of
the
usability
section.
We
are
three
sections
for
resources
which
are
accessibility
to
discoverability
and
accessibility,
so
we
may
need
to
update
the
resources
there
and
whichever
one
is
pertinent
to
our
discussion
in
that
metric
yeah.
C
B
F
B
B
B
C
B
C
A
And
if
you're
not
have
any
more
comments,
we
may
differ
updates
to
this
metric
system
until
next
time
when
we
get
those
who
views-
and
we
also
have
another
item
in
there
and
we
have
about
10
minutes
or
eight
minutes
left
so
time
to
move
on
so
there.
The
entry
to
issue
tracker
inclusivity,
metric,
looks
like
someone
put
this
in
here
and
opening
up.
The
document
looks
like
a
lot
of
people
already
here.
D
D
D
Is
a
way
to
almost
like
quantify
how
affordable
the
issue
attractor
is
to
multiple
types
of
contributors,
and
this
really
could
be
whether
you're
a
newcomer,
whether
you're,
just
like
an
occasional
contributor
or
a
core
contributor,
you'd,
find
something
to
work
on,
and
that
being
said,
it
would
be
with
also
being
able
to
differentiate
issues
with
different
skill
sets
like
what
would
you
need
to
work
on
this
issue
in
language-wise
framework?
Is
a
front-end
or
back-end
or
documentation?
D
Some
wording
like
that
one
other
thing
I
just
heard
about
recently-
is
that
there's
mentor
available,
dag
or
label,
which
would
be
pretty
interesting
for
suggesting
issues
for
newcomers
that
have
a
mentor
attached
to
them.
So
you
can
ask
them
questions
you.
They
would
be
processing
the
PR,
so
they're,
basically
there
to
walk
you
through
the
process.
D
If
you
lease
diversity
would
be
more
like
having
issues
are
different,
they
could
be
documentation
or
code
useable,
title
and
description,
basically,
a
way
of
of
making
sure
that
I,
don't
like
the
description,
are
well
structured,
readable
and
I
feel
like
they're
gonna,
just
follow
the
guidelines
of
documentation,
usability
and
a
consistent
usage
of
tags
or
of
labels.
Maybe
I
should
stick
without
wording,
meaning
tags.
If
the
same
family,
you
should
have
the
same
color.
D
E
E
The
only
thing
that
I
would
add
or
that
we're
adding
to
y'all
don't
have
to
obviously
is
we
are
looking
at
the
other
types
of
world
diversity.
In
regards
to
that,
so
we
are
look
at
things
like
brand
ambassadorship.
You
know
for
these
people
going
and
speaking
on
our
behalf,
we
are
looking
at
things
like
design
and
architecture.
E
So,
if
they're
going
through
and
adding
some
assets
in
regards
to
like
road
mapping
or
the
API
constructs-
or
you
know
anything
along
those
lines
were
like
figuring
out
how
to
come
in
and
give
more
credit
than
they've
ever
gotten
in
the
past,
because
one
of
the
difficulties
I
see
that
happens
in
open
sources.
If
it's
not
a
line
of
code,
we
don't
count
it
right
if
it's
not
if
it's
not
a
line
of
since
and
documentation
at
least
now
we're
starting
to
count.
E
F
E
One
things
we
are
looking
at
Amy
is
measuring
those
the
pages
and
the
other
ones
as
well
right,
so
not
just
limiting
our
measurement
to
the
other
tools.
It's
like,
yes,
the
measurements
easier
than
the
other
tools,
but
it's
not
always
where
we
want
people
to
be
because
trying
to
draft
a
document
in
that
from
the
start
is
really
hard
and
basically
they've
rebelled
against
me.
E
E
A
B
Just
I
did
post
one
thing
in
the
issue:
tracker
inclusivity,
premiere,
iam,
just
as
you're
thinking
about
this
metric
kind
of
where
you
think
it
might
be
positioned.
So
we
have
a
spreadsheet
that
kind
of
tracks
our
metrics.
So
if
you
could
take
a
look
at
that,
that
would
be
great
so
then,
and
listening
to
you
talk
and
listen
to
cilona
talk.
B
This
is
this:
is
a
lot
about
kind
of
tagging
or
labeling
the
issues
themselves
and
in
thinking
about
that
not
necessarily
the
tool
of
issues,
but
the
process
by
which
you
create
issues
to
recognize
good
work,
I
think
is
what
someone
was
talking
about
as
well,
but
also
great
a
place,
that's
approachable
for
others.
If
I
was
understanding
it
correctly.
Okay,
that's
super
interesting
yeah.
E
Cuz
we're
even
talking
about
doing
a
special
instance
that
would
focus
completely
on
academia,
yes
and
understand
them
in
their
processes
and
make
it
easy
and
usable
for
them
I'm
still
having
you
know
that
granularity
that
code
has
and
its
code
versioning
and
all
the
wonderful
stuff
to
get
lab
has
in
regards
to
that.
So
yeah
I
totally
understand
that
what
I'm
talking
about
like.