►
From YouTube: CHAOSS.Community.December.17.2019
Description
CHAOSS.Community.December.17.2019
A
A
I
had
a
couple
of
things:
I
guess
I'll
start
and
obviously
anybody
can
add
anything
they
like
so
I
had
a
few
things
on
events
here,
the
oh
hey,
John,
the
open-source
member
summit
submissions,
those
are
do
kind
of
like
in
the
middle
of
January
I,
certainly
plan
on
going
and
I
plan
on
submitting,
but
I
don't
know
if
others
do
as
well.
Just
so
we're
not
so
we're
trying
to
coordinate
efforts
a
little
bit.
A
B
C
B
A
A
B
A
B
D
B
A
Cool
alright
great,
thank
you
anything
else.
On
of
events.
I
know,
open
compliance
summit
was
just
happening
or
is
happening
today.
Yesterday,
Sean
is
over
there
and
I
think
getting
some
good
feedback
on
a
lot
of
risk.
Metrics,
so
that's
been
pretty
cool.
I
actually
think
some
other
from
what
I
understand.
Some
of
the
risk
metrics
were
actually
in
someone's
keynote
at
the
open
compliance
summit
as
well.
So
pretty
happy
at
all
yeah
pretty
happy
to
continue
to
see
those
things
show
up
in
in
the
keynotes.
I
haven't
seen
the
keynote.
A
A
But
what's
basically
on
the
releases
mentions
of
moving
to
the
new
template,
mentions
of
any
fundamental
changes
that
may
have
occurred
on
a
metric
that
was
released
in
the
first
release.
Any
new
metrics
that
are
coming
forward
and,
in
particular
the
common
working
group,
had
identified
a
restructure
of
focus
areas.
Is
that
about
right,
yeah.
C
B
A
E
E
D
Being
part
of
you
know
the
workflow
today
that
that
kind
of
closes
the
it
eliminates
a
lot
of
issues,
people
filing
trying
to
actually
make
a
very
concrete
contribution
in
a
very
particular
spot,
and
it
gives
the
authors
of
the
project.
You
know
complete
control
over
whether
or
not
they
want
to
accept
something
or
if
there's
needs
to
be
discussion,
so
that
workflow
just
separates
all
that
work
of
trying
to
triage
issues
and
just
keeps
editorial
related
feedback
and
improvements.
D
Is
there
chance?
We
can
have
that
you
like
view
on
github
or
makeup,
you
know
just
a
link
that
opens
the
relevant
markdown.
Is
this
relate
it
to
the
release
so
yeah,
because
work
or
glow
in
general?
Well
I
mean,
if
you
have
those
part
of
the
release.
Has
that
kind
of
mechanism
in
the
rendering,
then
you
don't
have
to
change
how
you
go
about
putting
that
content
from
WordPress.
So
so
it
kind.
C
D
E
As
far
as
the
as
far
as
the
the
metrics
detailed
pages
go,
we
actually
in
the
in
the
past
release.
We
could
do
that,
so
we
we
link
to
an
issue
that
was
created
specifically
for
that
that
detail,
page
and
then
I
believe.
We
also
link
to
the
github
markdown
page
that
that
existed
on
a
mic
and
like
am
I
remembering
that
correctly
Garrick
yeah
during.
D
Yeah,
it's
usually
the
static
site
generator
when
it's
picking
pulling
in
the
markdown
that
it's
actually
saying.
Okay,
the
metadata
for
that
markdown
is
that
it
originated
in
this
particular
gate:
source
yep
and
then
the
renderer
sees
that
metadata
and
puts
the
okay
edit
on
github
button.
So
it's
more
like
a
I'm
Connie.
We
can
do
that.
There.
B
Are
what
I'm
thinking
right
now,
just
to
give
you
a
background
right
now?
What
we
do
is
be
freeze
the
repositories,
the
working
group
repositories,
we
create
release
tags
and
then
in
WordPress
we
pull
in
the
release
tag
version
of
the
markdown
pages,
the
way
to
their
for
one.
That
means
we
do
not
update
the
pages.
So
even
if
you
go
back
to
the
original
markdown
and
update
the
master
branch,
the
release
tag
does
not
change.
Oh
yeah,
so.
D
B
B
D
Directly
from
master
or
not
so,
I
didn't
make
that
particular
claim,
but
but
here
we're
saying
that
this
branch
that
will
be
contributed
to
words
since
it's
a
process
of
editorial,
probably
to
fix
a
typo,
then
you
would
assume
that
okay,
this
lands,
after
the
pull
request,
goes
through
the
usual
process,
being
a
a
correction
to
the
white
content,
not
to
be
make
content
at
this
time.
Initially,
okay,.
B
D
Found
error,
III
suppose
you're
talking
about
future
edit
for
the
next
release.
Those
happen
on
a
separate
branch
like
on
the
develop
branch,
if
you're
doing
using
on
the
master
branch.
Those
all
happens
on
the
master
I
mean
the
master
branch
is,
is
what
you
want
to
keep
on
your
site.
So
any
changes
you
do
there
change
your
site,
but
if
you're
going
to
be
so
so
sorry,
why
would
you
change
the
file
name?
Just
because
I
mean
I
missed
that
context?
Well,.
C
D
Edits,
though,
we're
editing
for
next
release
and
they
should
really
not
be
happening
on
master
if
we're
using
that
workflow,
our
master
is
what
is
lie,
then
you
know
I,
don't
want
to
call
it
master,
but
most
people
keep
it
as
master.
But
what
you're
doing
to
revise
master
in
the
next
release
happens
on
a
secondary
range.
They
used
to
call
them
develop
and
now
some
call
it
staging
when
it's
web
hua
made
it,
and
it's
basically.
E
Like
I
would
say,
I
think
one
of
the
I
think
one
of
the
issues
we
have
here
is
that
the
the
github
repositories
for
these
working
groups
are
they're,
not
primarily
there
to
create
output
to
the
website.
They're
they're,
primarily
there
to
just
for
a
workspace
right.
So
the
website
just
kind
of
grabs,
a
snapshot
of
them
at
a
time,
yes,
and
and
it's
grabbing
a
snapshot
from
different
repositories
as
well.
D
A
V3,
so
maybe
one
maybe
I
mean
I
I
think
these
are
good
discussions,
maybe
the
instead
of
like
trying
to
do
everything
all
at
once.
Maybe
a
first
recommendation
would
be
on
the
the
release.
That's
occurring
January
3rd
yeah,
January
30th
is
for
that
release
to
provide
at
least
a
backlink
to
the
to
the
repository,
or
this
work
is
occurring
so
that
people
who
want
to
participate
in
modifying
any
of
the
metrics
or
even
propose
new
metrics
know
where
that
that
work
is
occurring.
I
think.
E
A
D
B
So
we
don't
have
such
a
generator
and
what
they
did
last
release,
and
maybe
maybe
this
already
we
can
continue
doing.
That
is
when
you
go
to
the
metrics
release
page
in
each
working
group,
and
we
do
have
the
repository
linked,
not
within
each
metrics
but
just
within
the
metrics
page.
The
list
of
metrics
to
any
of
those
you
can
go
to
the
repository
is
that
from
a
workflow,
clear
enough
to
know
where
to
go
to
edit
I.
D
C
D
Would
be
just
a
click
like
go
to
the
markdown
file,
see
I
I,
know
it's
not
as
obvious
but
figuring
out
which
markdown
file
you
want
to
reference
when
you're
trying
to
bring
the
attention
of
you
know
the
project
about
something
in
a
particular
place.
They've
read
having
that
link
that
eliminates
them
having
to
search
through
a
conventional
structure
of
a
project
that
is
already
accustomed
to
it.
D
A
A
Why
don't
we?
What
some
here
I
have
a
proposal,
then
I
mean
I
like
the
idea
right
of
trying
to
trying
to
lower
lower
the
barriers
by
which
people
can
contribute
right.
You
know
if
we
can
take
them
directly
where
they
need
to
be
that's
great.
So
maybe
we
have.
Our
next
meeting
is
on
the
7th
of
January
because
of
the
holidays
and
stuff
like
that,
I
mean
and
maybe
Kevin
like
over
the
course
of
January.
A
E
A
A
I
forget
what
working
group
it
came
out
of
that
we
add
another
column
to
this
spreadsheet,
which
is
about
target
release,
because
right
now
we
have
things
can
be
marked
as
like
in
progress
or
something
like
that.
I'm
not
actually
looking
at
the
spreadsheet
I
should
suppose
I
should
but
like
in
progress
yeah,
we
have
in
progress,
you
know
the
yellow
row,
but
it
might
provide
a
little
clearing
like
in
progress
for
the
15th
version
like
this
is
a
really
long
arc.
We
don't
really
plan
on
verses
in
progress
for
version
2.
D
A
D
A
A
C
A
Okay,
metrics,
so
I
went
through
the
I,
went
through
the
spreadsheet,
from
what
I
could
understand.
So
these
are
metrics
and
development.
So
everything
that's
purple
at
the
moment
in
there,
I've
marked
as
ready
for
release
and
the
reason
I
marked
them
already
for
release
is
because
actually
every
metric
changed
this
round
either
it
was
a
new
metric,
it's
ready
for
a
release
or
it
was
updated
to
the
new
template,
meaning
it's
ready
for
release,
so
I
just
marked.
All
of
them
is
ready
for
release
all
right.
A
The
what
you're
seeing
here
is
me
going
through
the
spreadsheet,
trying
to
identify
so,
for
example,
documentation,
accessibility.
The
conversation
that's
going
on
right
now,
out
of
DNI
I,
think
that's
a
metric.
That's
still
in
development.
You
could
correct
me
if
I'm
wrong
same
with
with
risk,
there's
one
same
with
evolution.
There
were
two
and
so
on
and
so
forth.
So
I
don't
know.
This
is
mostly
just
to
kind
of
put
these
on
people's
radar.
The
hope
is,
as
these
can
move
forward.
They're
gonna
have
to
move
forward
asynchronously.
A
We
don't
have
to
solve
these
now,
but,
if
you're
part
of
say,
DNI
and
bringing
forward
documentation,
accessibility
I
do
encourage
you
to
just
kind
of
continue
to
push
that
asynchronously
same
for
the
rest
of
the
working
group.
So
I
don't
know.
If
anybody
has
a
comment
on
there,
that
was
just
mostly
a
visibility
issue.
I'm
trying
to
provide
here.
A
And
this
this
would
be
it
I'm
guessing
right.
This
will
be
these
whatever
two,
four
five
that
we
have
here.
This
will
call
an
end
to
this
to
this
version
so
again
for
the
working
it's
there
is
no
set
number
of
metrics
that
need
to
be
released,
so
I
mean
if,
if
I'll
just
because
I
know
documentation,
accessibility
is
being
talked
about
right
now.
If
that
just
doesn't
hit
a
forum
that
you're
comfortable
with
there's
the
that's
okay,
it's
totally
okay
and
this
can
hold
off
until
the
next
the
next
release
that
would
occur.
A
You
know
six
months
in
the
future
after
that,
so
don't
don't
feel
that
there's
any
pressure
to
get
these
done.
I
think
doing
the
quality
work
is
far
more
important
than
doing
rushed,
work
and
I'm,
not
saying
you're.
Rushing
through
it
I
just
I,
don't
want
to
give
anybody
a
sense
that
you
absolutely
must,
because
we've
really
done
great
I.
Think
to
this
point
in
terms
of
I.
D
Feel
I
feel
like
feedback
as
me
that
don't
worry,
we
got
it
like
we
kind
of
look
at
it
when
we
were
working
and
yeah
like
there
are
places
where.
Obviously
there
are
improvements,
it's
good
to
you
know
give
this
particular
topic,
in
my
opinion,
yeah
a
fair
shake,
because
it's
mystical
to
a
lot
of
people,
yeah
I.
B
A
D
D
You
know
always
complain
about
what
I
you
know,
I
struggle
with
and
I'm
sure
other
people
have
documentation
accessibility,
but
yesterday
there
was
a
like
rude
awakening
moment
because
we
weren't
looking
at
okay.
So
how
do
you
measure
it?
Documentation
is
accessible
if
documentation
itself
is
written.
Markdown
that
is
in
a
repo
and
markdown
has
no
length
concept
of
accessibility,
but
it
depends
how
your
documentation
is
presented,
so
the
style
of
writing
can
be
disabling.
D
D
Yes,
you
definitely
can
measure
on
markdown
there's
no
tool
that
will
tell
you
this
particular
statement
is
kind
of
like
confusing
to
some
people
that
most
people
don't
even
realize
that
it
is,
but
but
other
than
that
ain't
of
accessibility
fallback
to
whether
or
not
get
out
in
90%
of
the
times
he
is
accessible
and
to
be
entirely
honest,
I'm,
not
sure
it's
three
meters
or
whatever
like
is
not
my.
You
know,
kind
of
accessibility,
but
for
me,
like
I,
have
a
separate
screen,
because
github
has
so
much
eye.
Contact
like
hi-yah
at
stimulation.
D
B
A
It
was
hard
for
me
to
to
categorize
them.
So
in
the
implementation
you
say
you
can
run
like
a
survey
or
you
can
run.
You
can
look
for
certain
criteria
and
it
was
hard
for
me
to
know
in
the
data
collection
strategies
which
of
those
were
survey,
items
which
might
be
items
that
I
as
a
person
might
have
to
personally
go
out
and
collect.
A
A
A
D
We're
here,
just
just
to
clarify
we're
keeping
the
commented
segment
at
the
end
of
the
I
know:
there's
not
a
time
for
this.
That's
just
a
at
the
bottom.
He
says
this
metric
seems
to
be
too
complex,
and
then
we
have
like
rough
notes,
so
it'll
be
pulled
out.
Yeah.
The
PR
should
not
have
that
kind
of
thing
in
the
future.
Little.
A
A
All
right
well,
thank
you
so
anyway,
if
you're,
if
you're
part
of
those
working
in
groups
just
kind
of
know
that
we're
gonna
have
to
put
closure
to
these
at
some
point,
I
copied
the
timeline
from
below.
So
there
it
is
I
mean
it
just
is
what
it
is.
The
timeline
I'm
back
in
the
chaos
weekly
minutes
I'm
at
the
bottom
of
page,
whatever
I
suppose
we
should
put
page
numbers
on
here.
Community
reports-
I,
don't
know
if
there's
anything
that
the
gay
or
you
want
to
bring
up
Sean's,
not
here
so.
B
So
we
had
a
meeting
with
the
Jenkins
ex
community
manager
Kara.
Last
week
we
talked
through
the
metrics
that
we
were
able
to
produce
from
Holdren,
and
it's
on
my
to-do
to
deploy
traditional
form
or
lab
instance
to
get
some
additional
metrics
and
we
did
decided
to
get
the
risk
metrics
from
otter,
because
Agra
has
the
more
complete
implementation
of
risk.
Metrics.
B
B
A
D
C
D
Very
very
helpful
when
you're
intent
and
the
action
that
follows
from
that
intent
are
one
step.
You
know
it
eliminates
the
need
for
clarification,
because
if
there's
any
chance
for
clarification,
I'll
be
it
I'll,
be
like
you
guys
mean
this
and
end
biii
me
like
the
like
the
vibe,
but
may
more
frequently
need
to
be
upside
down
thing.
So
can
we
can
we
try
to
consider
using
suggestions?
Is
that
something
everybody
willing
to
III
mean
the
deeps
label
eyes?
D
B
D
So
it's
it's
when
you
click
on
the
plus
and
then
that
opens
that
common
thing.
If
you
do
three
back
takes
and
write
suggestion,
it's
basically
starting
a
committable
edit
that
that
that
relates
to
that
particular
in
mind.
So
if
you,
if
you
want
to
change
on
the
plus
and
then
three,
what
dream
like
three
back
takes
like
offense
code
block,
like
you
know
how
you
do
code
blocks
and
and
there
so
three
backticks
to
open
the
block,
followed
by
the
word
suggestion
and
tells
github
that
this
is
code.
D
That
is
meant
to
replace
starting
from
that
line
and
and
it
will
be
adding
lines
if
you
go
beyond
a
single
mine
in
that
particular
block.
So
let's
say
I
wanted
to
add
a
line.
I
would
click
the
plus
button
on
the
line
before
it
yep
I'm
copying,
literally
like
a
half
his
the
line
and
followed
by
a
new
line.
I
believe
this.