►
From YouTube: CHAOSS.Community.May.14.2019
Description
CHAOSS.Community.May.14.2019
A
C
C
A
A
A
A
B
B
A
B
D
A
Then
the
day
prior
to
open
source
in
North
America
is
chaos.
Con.
A
From
my
end,
I
put
together
a
with
the
help
of
other
people,
a
sponsorship,
prospectus,
I
think
Georg
actually
put
together
the
draft,
and
then
we
just
kind
of
worked
it
down.
So
thanks
scared,
yeah
I,
sent
it
out
to
a
variety
of
people
at
this
point,
so
we're
really
just
the
Linux
Foundation
provides
the
venue
at
no
cost,
but
then
we
need
to
find
some
money
for
coffee
and
stuff,
like
that.
You
know
just
to
keep
people
happy
during
the
day.
So
anyway,
those
have
been
sent
out.
A
A
Okay,
not
a
problem
like
I
said:
I,
don't
think
it's
gonna
be
a
huge
concern,
so
that's
moving
forward
and
then
I
know.
Georg
has
put
together
a
call
for
proposals.
A
B
Muted
Gary,
thank
you.
Yeah
I
can
show
that
you
in
the
chat
real
quick.
This
is
an
email
that
I'm
planning
to
send
out
to
the
mailing
list.
If
you
have
any
edits
and
thank
you
Matt
and
Daniel
for
already
revising
it
and
making
suggestions
the
Kaufer
proposal
this
year
is
very
short
time
wise.
You
only
have
two
weeks
because
we
were
late
in
the
game,
but
that's
okay,
we'll
still
manage
if
we
just
advertise
it
enough.
If.
B
A
A
E
Cfb
as
a
attachment
or
a
PDF
document,
but
the
email
instead
of
wasting
their
time
and
PDF,
would
be
good.
I,
don't
know
how
well
that
comes
off
of
the
web
page
as
a
PDF
PDF
can
be,
can
have
a
piece
can
be
converted
into
PDF
pretty
easily
yeah,
or
we
can
copy-paste
and
format
it
in
the
PDF.
Okay,
yeah.
B
A
B
B
B
A
A
B
A
So
then
I
guess
I'll,
ask
I'll
shoot
I
have
an
action
wants
to
do
I'm
gonna
put
together
a
document
called
releasing.
That
can
be
that
markdown
and
I'm
gonna
put
it
in
the
Church
repository
and
it's
gonna
be
a
document
that
describes
kind
of
what
the
criteria
are
for
releasing
a
metric
on
that
virgin,
whatever
virgin
almost
with
version
one
on
a
release
and
it's
it's
not
a
complicated
document,
so
I'll
I'll
put
that
together
and
then
let
folks
know.
A
So
you
can
make
comments
on
it,
but
basically
the
premise
is
that
if
you're
gonna
release
a
metric
as
part
of
the
release
schedule,
the
there
is
a
focus
group
or
focus
area.
Sorry,
there's
a
focus
area
which
everybody
is
following
anyway.
The
metric
is
within
a
particular
focus
area
and
is
addressing
a
particular
question,
which
is
what
everybody
is
doing
anyway
and
then
there's
a
detail
page
behind
that
metric.
That
gives
a
little
bit
richer
description
about
the
metric
itself.
A
I
still
have
to
do
that.
I
should
take
care
of
that
sooner
rather
than
later
in
garrard.
We
could
probably
put
that
in
that
really
sing
markdown
document.
Maybe
the
timing
of
one
we're
looking
for
these
and
then
probably
also
in
that
document,
a
link
to
that
spreadsheet
that
people
can
identify
what
is
to
be
released
and.
A
B
That's
around
the
topic
of
the
community
handbook
I
started
a
tribe
or
I'll,
be
organized
chaos
calm.
This
is
a
very
rough
draft
right
now,
I'm
gonna
point
the
link
here:
real
quick,
where
I
thought
about
okay,
what
are
all
the
things
that
you're
doing
and
I
wrote
a
sentence
or
two
about
how
you've
done
it
in
the
past.
You
know
this
is
still
early
very
rough
draft
I
just
wanted
to.
Let
you
all
know
that
this
is
in
the
woods.
B
A
B
A
B
A
B
B
B
C
A
A
D
Or
lab
couple
of
updates,
so
we
we've
had
in
the
last
couple
of
weeks
new
information
there,
so
we
are
now
tracking
who
is
reviewing
and
what
type
of
review
that
people
are
doing
in
Garrett
same
for
github.
So
we
have
a
code
review
information,
all
the
information,
so
people's
aquitine
people
reviewing
that
pleaded
after
countries
and
Ramallah.
D
D
Yeah,
well
mainly
so
in
character,
Gareth,
technical
terminology.
What
we
have
our
chain
sets,
which
is
the
whole
code
review
process-
let's
say
a
change
that
is
you
see
in
iteration,
so
then
you
have
cuts,
it's
one.
Iteration
is
one
touch
yet
and
then
for
each
of
them
you
have
approvals.
Like
all
people,
both
teams,
we
have
plus
1
minus
1,
plus
2
minus
2.
If
you
are
doing
plus
2
or
minus
2.
D
That
means
that
you
are
a
code
reviewer,
then,
would
you
have
some
policy
that
the
end
you
access
to
to
this
piece
of
code
to
the
source
code?
So
this
can
be
March
the
ambition,
then
the
comments
and
so
on
and
well.
We
do
have
as
well
see
I
information
as
well
box,
verifying
that
this
is
passing
all
of
the
tests
and
blog,
which
is
part
of
the
approval
section
kind
of
this
in
in
github.
D
What
we
have
now
is
all
of
the
review
process,
someone
asking
for
new
things
and
so
on
and
in
the
case
of
JIRA.
This
is
related
to
the
comments
in
more,
basically,
all
of
the
all
of
the
comments
time
in
an
issue
that
we
typically
aggregated
in
certain
metrics
like
number
of
comments
or
similar
stuff.
But
now
we
have
that
info
choppy
for
tomorrow.
Ok
is.
D
Personal,
so,
first
of
all
is
a
tool,
retrieving
the
information,
so
that
means
that
for
the
back
end
of
carotene,
first
of
all,
this
has
new
code
for
the
back
end
of
github
in
Perceval.
This
has
new
code
same
for
JIRA
and
then
the
same
for
the
rest
of
the
infrastructure.
Severe
and
reaching
those
pro
index
is
produced
by
and
then
heavy
neither
new
panels
or
widgets
depend
on
okay.
A
D
A
D
Is
easy
stored
as
a
JSON
document,
so
what
we
have
now
is
a
new
JSON
entry
for
each
of
the
code
review
axioms
events.
So
then,
if,
for
instance,
if
you
look
for
Dave
and
for
the
code
review
for
the
change
set,
ten
thousand
fifteen,
for
instance,
then
you
will
see
all
of
the
axioms
on
basic
change
Center.
So
then
this
depends
on
how
you
want
to
visualize
information
capture.
D
A
D
D
A
B
A
A
B
A
A
D
A
If
I'm
in
in
this
meeting,
we
don't
have
to
do
it
right
now,
but
like
on
the
like
every
two
weeks.
Kind
of
thing
actually
spend
some
time
in
this
meeting,
asking
for
folks
from
groom
or
lab
Patricia
and
auger
to
just
spell
out
what
kind
of
like
what
exactly
what
you
had
just
done
Daniel
and
then
we
can
not
only
send
the
notes
from
the
meeting
like
we
do
every
every
week,
but
we
could
also
send
an
independent,
a
separate
email.
It
was
just
kind
of
pulling
out
the
software
components,
I
mean
I.
D
A
A
A
A
D
So,
for
instance,
malaria
from
it
earlier
he
was
during
the
last
week
here
it
was
a
bit
like
what
can
I
say
what
I
cannot
say,
because
you
were
discussing
about
other
things.
He
was
not
sure
about
how
to
proceed
but
having,
for
instance,
this
specific
third
Tuesday.
It
small,
it's
much
easier
for
me
to
say:
hey
we
have
this
day,
so
you
have
to
come.