►
From YouTube: CHAOSS.Community.December.10.2019
Description
CHAOSS.Community.December.10.2019
D
A
D
A
A
B
A
B
Because
don't
we,
if
our
next
our
next
meeting
after
after
the
deadline,
is
Tuesday
the
7th,
then
don't
we
need
to
do?
We
need
this
meeting
to
say
yep
bingo.
This
is
the
set
that
we're
gonna
release
for
review,
or
are
we
trying
to
have
a,
but
we
are
trying
to
have
the
full
release,
the
most
biggest
return
of
the
month
of
you
period,
completed
before
FOSDEM
as
well.
Right,
yes,.
B
I
mean
I,
guess
the
scenario
that
I'm
thinking
of
is,
if
a
last
time
this
happened,
then
I
expect
it
to
happen
this
time.
They'll
be
groups
that
have
or
metrics
that
they
think
oughta
be
really
I.
Guess
that's
what
the
review
period
is
for
I'll
shut
up
if
metrics
needed
to
be
iterated
out
and
they
could
be
iterated
on
during
the
review
period.
That's
the
whole
point:
I'm
just
gonna
be
quiet.
Now.
B
B
A
B
F
Yes,
yeah
I
was
actually
just
when
you
brought
that
up.
I
was
thinking
the
same
thing.
It's
just
I
think
we
just
have
to
add
another
page,
so
one
of
them
is
the
the
current
release
and
the
other
one
is
the
release
candidate
age
and
after
the
after
the
review
period,
we
can
make
one
of
them
go
away,
I
suppose
so
or
we
can
we
can
archive.
We
could
have
an
archive
page,
I
suppose
as
well.
A
B
F
C
B
A
Well
and
I
like
the
idea
of
just
providing
a
PDF
of
the
release,
I
put
in
the
minutes,
the
PDF
we
have
for
the
version,
one
release
and
it's
listed
on
the
metrics
page.
We
just
add
a
new
item
basically
and
then
have
two
pdfs
one
for
the
first
for
any
one
for
the
second.
But
the
website
itself
has
always
the
most
current
release
version.
A
B
Think
one
page
that
is
a
link
to
all
the
metrics
would
be
easier
for
people
to
navigate
and
I.
Think
that's
what
we
did
before
right
or
did
we
create?
We
actually
create
because
they're
the
one
page
and
then
you
just
would
click
on
the
on
the
focus
group
or
the
working
group,
and
then
it
would
scroll
down
that
page
to
the
release
metrics
for
that
group.
But
it
was
all
on
one
page
and
I
think
that's
still
the
case
for
the
released
metrics
even
am
I
wrong.
Kevin.
F
A
What
do
you
think
well.
F
You
know
the
website,
it's
a
wordpress
website
and
you
know
page
management
is
kind
of
weird
yeah
WordPress,
so
you
know
right
now.
If
we
go
and
we
look
at
our
at
the
way,
it's
the
the
file
structure
within
that
WordPress
website.
You
know
we
probably
have
like
50
pages
right
and
if
a
detail
page
adds
another
page
to
it.
You
know
that,
as
far
as
the
website
is
concerned,
it's
you
know
we're
gonna
get
up
to
a
hundred
and
fifty
pages,
probably
pretty
quick
and
WordPress
does
not
really
manage
that
structure.
All
that.
B
F
A
B
Ask
one
more
question
about
that:
if
there
are
metrics
that
have
changed
and
I
think
there's
a
few
that
have
all
of
the
metrics
that
we
published
have
been
reorganized
to
the
standard
template,
so
we
should
put
that
in
there
release
notes
like
we
should
have
a
release,
notes
page
for
this
metrics
release
and
I.
Don't
think
it
needs
to
be
more
detailed
than
version.
1
metrics
are
restructured
to
a
common
format
and
then
I
think,
if
anyone's
aware
of
any
fundamental
changes
to
what
a
metric
is,
which
I
don't
think
we've
made
any.
B
We
should
note
that
in
the
release
notes
as
well,
so
that
when
people
go
to
the
version
one
of
our
metrics
and
they
see
that
the
version
two
looks
different
like
really
different
structurally,
that
they
can
see
in
a
release,
notes
document
somewhere
what
that's
about.
So
they
don't
think
that
the
whole
the
whole
commute.
The
whole
ecosystem
of
metrics
is
fundamentally
going
to
change.
Every
released.
D
A
Okay,
I
I.
Second,
the
idea
of
release
notes
in
the
Google
Doc
in
our
minutes,
I
started
to
outline
them
how
we
could
structure
them.
So
we
could
say
something
like
we
change
all
metrics
plate.
Then
we
moved
or
renamed
the
following:
metrics
I'm
gonna
be
list
the
original
name
and
the
Union,
and
then
we
can
also
talk
about
we've
restructured
the
focus
areas
and
we
talked
about
how
they
are
restructured.
A
B
F
B
F
B
There
there's
a
well
as
a
side
note,
should
I
mention
this
town
in
augur,
we're
using
a
little
github
plugin
that
just
every
time
you
do
a
release.
It
actually
creates
a
summary
of
all
the
pull
requests
and
commits
that
are
included
in
that
release,
which
is
helpful
for
going
back
and
trying
to
describe
in
plain
English
what
it
is
we
changed.
E
Sir
yeah
and
then
I,
usually
rudely
interrupt
so
just
just
the
problem.
I'm.
Seeing
with
the
commits
is
that
you,
you
have
to
really
use
a
tool
that
will
sort
of
based
on
file
most
tools,
look
at
a
repo
as
a
project
and
they
cater
those
tools
to
create
a
change
lock,
dot
MV
in
the
root
of
the
repo
yep,
as
opposed
to
you
know.
We
changed
this
document
by
this
because
we're
not
really
using
like
we're
easing
repos,
but
we're
working
on
talking
about
units
yeah,
so
so
I.
B
B
D
D
D
D
E
E
Did
not
have
my
mind
as
I
posted
the
link,
but
basically
I.
Think
if
we're
going
to
do
this
idea
of
a
markdown
file
that
has
release
notes,
keep
keep
it
change.
Long
calm
talks
about
this
again
being
the
change
log
of
the
product,
so
we
want
to
go
close
to
convention,
but
but
account
for
the
fact
that
we're
talking
about
documents
then
I
think
you
know
we
can.
We
can
just
add
a
header
level
under
each
release.
E
There's
the
first
header
talks
about
which
document,
and
then
you
know
under
it
you
can
help
clean
jewelry
or
you
can
ask
bulletin
items
because
they
divide
each
each
version
by
the
kind
of
change
is
that,
in
addition,
a
change
of
that
vacationing
text,
security
and
so
forth.
So
seeing
that
change
logs
here
would
be
almost
always
revisions
or
additions
or
yeah
I
mean
everything,
but
security
and
I,
don't
know
fix.
Maybe
so
so
it's
just
trying
to
any
this
as
a
base
template
and
see
how
we're
gonna
further
divide
in
documents
level
so
yeah.
A
A
So
then,
for
the
during
the
review
period,
we
have
two
pages
that
we
have
to
add
to
the
website.
One
is
for
the
change
law
and
one
is
for
the
new
metrics
candidate,
yes
candidate,
but
then
from
that
metrics
are
seen
page.
We
linked
out
to
the
original
markdown
files
in
the
repository.
So
during
the
review
period
we
don't
see
any
issues
with
markdown
being
rendered
on
WordPress.
B
A
A
After
once,
we
finished
the
review
period,
we
remove
that
reference
to
the
issue.
We
close
the
issues
and
then
we
create
a
new
tag,
release
tag
in
the
repositories
and
then
Kevin
goes
into
the
metrics
pages
on
WordPress
updates
the
version
tag
that
it
pulls
the
markdown
from
and
create
new
pages
for,
the
new
metrics
or
changes
names
for
metrics
that
change
names
and
that
moves
the.
B
A
A
A
B
D
B
E
I
think
go
from
a
changelog
and
your
right
to
release
notes
so
changelog.
This
way
you
keep
internally
to
to
have
all
the
notes
generated
as
you
are
making
changes
so
that
when
centralized,
you
leave
notes,
you
just
have
everything
you
can
reflect
on,
but
certainly
this
has
to
be
addressed
as
a
document
of
release
you
know
like
like
it
has
to
be
authored
and
not
not
just
generated
or
renamed
yeah.
A
B
B
F
I
wonder
if
that
that
task
should
actually
be
left
to
each
working
group
to
and
then
you
consolidate
by
their
release,
notes
and
then
I
can
consolidate
into
one
I.
Think.
B
So
I
think
I
think
maybe
we
asked
them
to
supply
release,
notes
with
the
specifications
that
we
described
and
then
I
still
think
after
that
Kevin
before
we
released
the
release,
notes
you
and
I
are
you
and
somebody
with
familiarity
with
that
process
in
software
needs
to
go
through
and
like
so
I
was
suggesting.
You
know
create
a
human-readable
set
of
release,
notes
because
they'll
they'll
vary
as
much
as
the
metrics.
Well,
I!
Guess
again
that
could
happen
during
the
review
period
right
yeah,
so
we
can
have
candidate
early
snip.
B
D
B
And
it's
a
it's
a
it's
a
good
idea.
I
think
from
I
mean
there
may
be
small
changes
that
got
made
to
previously
release
metrics
that
don't
seem
like
a
big
deal
that
somebody
notices
actually
are
so
that
would
that
would
give
people
a
chance
to
make
sure
that's
in
there.
So.
E
There's
no
further
people.
Sorry
there's
also
an
example
link
that
shows
how
they
went
from
changelogs
to
structured
by
topic.
I
added
that
link.
It's
like
the
WebKit
Safari
has
released
notes
and
they
look
very
much
like
the
opposite
of
the
changelog
format,
where
they
sorted
everything
by
topic,
not
not
necessarily
by
what
kind
of
change
it
was
so
I
figure
every
header
here
like
web
animations
and
so
forth.
Those
would
be
the
different
working
groups.
E
B
And
I
think
I
think
it's
important
when
we
communicate
with
the
working
groups
that
we
emphasize
that
fervor
already
released
metrics
the
changelog
is
not,
and
he
doesn't
need
to
describe
everything
it
just
to
describe
anything
that
has
changed
about
Metro
about
a
metric,
so
they
don't
feel
like.
You
need
to
go
back
and
do
a
change.
If
you
don't
do
a
change
like
for
your
first
release.
B
B
E
Guess
there's
one
question
that
should
be
articulated
to
everyone:
how
much
traceability
do
you
want
to
involve
in
all
aspects
of
the
process?
So
when
you're,
when
you're
documenting,
do
you
want
people
to
say
issue
number
whatever,
like
do
you
want
to
go,
relate
every
single
thought
that
is
in
release,
notes
and
stuff
like
that
to
where
people
can
go
back
and
say:
hey,
that's
why
they
made
it
that
way.
No
I
think.
B
D
E
A
Yeah,
no
thanks
for
bringing
that
up.
Solly,
that's
a
really
good
point
and
I
was
vigorously
shaking
my
head
because
I
know
we
are
making
changes
without
documenting.
Why
and
when
and
where
and
the
issues
that
we
have
are
not
prescriptive
and
so
I
don't
think
trying
to
reach
that
level
of
detail
in
the
release.
Notes
would
not
serve
anyone.
B
Well,
I
think
those
I
think
we
should
share
those
two
links
prominently
with
the
working
group
leaders
in
some
fashion,
so
that,
because
I
think
those
two
leases
that
those
links
that
Salah
shared
are
extremely
help
like.
For
me.
I
learned
best
from
some
examples,
and
these
are
two
really
clear,
specific
examples
and
we
can
wrap
it
around.
What
we're
trying
to
do.
What
we
just
discussed.
A
D
A
A
B
A
F
A
A
F
A
F
D
F
B
D
B
D
B
D
B
D
So
there's
a
column
AC
has
the
attendance
confirmed,
so
we
do
have.
Some
of
them
have
been
confirmed
already,
so
we
can
add
those
to
the
website,
the
other
there,
the
one
that
we
need
to
add
to
the
website.
Garriga's,
your
whatever
we
decide
to
call
your
kind
of
welcome,
slash
state
of
chaos.
Community
talked
at
the
very
beginning.
A
B
D
B
A
D
D
D
This
we
do,
we
do
want
to
get.
We
do
want
to
get
scheduled
announced
because
that's
gonna
drive
registration
and
we
need
to
get
that
out
before
people
start
disappearing
for
Christmas
and
if
any
people
are
like
me,
some
of
us
are
starting
to
disappear
on
the
16th.
So
so
that's
kind
of
designed
to
sort
of
head
off
the
holidays
and
get
people
thinking
about
it
before
the
holidays,
because
we
do
want
to
get
people
registered
and
make
sure
that
it's
in
their
travel
plans
for
fosston
I've.
D
A
A
A
A
D
A
So,
every
time
the
Matt
sends
them
an
email,
they're
gonna
tweet
about
it
and
he
did
after
the
last
time
we
talked
and
they
tweeted
about
it.
But
that's
the
extent
what's
happening
at
least
I.
Don't
see
anything
else
happening.
It's
Amanda.
You
probably
have
a
lot
more
ideas
about
how
to
market
the
event.
I.
G
A
G
D
They
should
probably
I
think
it
would
be
good
for
you
maybe
to
have
a
conversation
with
Matt
to
talk
about
what
we've
done
so
far
and
and
there
yeah
it's
almost
nothing.
We
need
help
desperately
so
I
think
Matt
can
maybe
help
provide
the
context
or,
if
he's
not
around,
probably
any
any
of
the
rest
of
us
could
as
well,
but
I
think
I'm,
not
sure
what
you
exactly
what
you
meant
by
affiliate,
but
I
do
think
that
we,
we
should
be
asking
some
of
the
speakers
to
do
some
additional
promotions
for
us.
D
So,
like
Deb,
Nicholson
who's
part
of
the
software
freedom
Conservancy,
she
can
help
maybe
do
some
promotions
to
some
of
their
channels
and
get
some
of
the
other.
Like
yeah.
We
have
a
speak
here
from
Apache.
Maybe
we
can
get
some
some
stuff
promoted
through
some
of
these
other
other
channels
and
we
haven't
really
yeah.
We
haven't
made
a
concerted
effort
to
do
that
in
the
past.
We
probably
should
the.