►
From YouTube: CHAOSS.Weekly.February.26.2019
Description
CHAOSS.Weekly.February.26.2019
A
Including
our
Kaos
hangouts
On,
February
26,
the
update
on
google
Summer
of
Code
is
that
Google
accepted
us
as
organization.
So
now
the
students
are
going
to
storm
all
the
projects,
including
ours
in
the
mainland.
Listen
I
already
saw
the
first
email
comes
through
it,
so
it
would
be
great
if
the
mentors
could
take
it
upon
themselves
to
respond
to
these
emails
and
birthday
emails
coming
into
year.
B
D
Detects
that
Miss
Marron
disappearing
force
any
metric
system
and
the
Middle
East,
and
to
mention
on
the
issues
of
me
open
with
America
and
all
of
them,
because
it's
like
every
member
wall,
video
was
to
include
events
and
communities
and
document
any
issue
that
they
may
have
in
the
issue.
With
respect
to
the
idea.
A
Yes,
that
is
how
we
are
doing
it,
and
so
the
students
are
messaging
us
to
let
them
know
they
are
interested.
They
will
pick
up
a
micro
task,
create
a
repository
to
work
on
it
and
then
create
a
pull
request
against
document
in
our
governance
repository
where
we
keep
track
of
everyone
interested
in
being
student
with
us,
I,
don't
know
how
many
spots
we
got
last
time.
I
checked.
A
D
E
Was
thinking
about
this
too
I
know
we
have
a
variety
of
different
projects.
I
just
was
wondering
this
morning.
If
there
would
be
any
way
for
let's
say
we
got
to
to
connect
with
the
work
that
the
common
group
is
doing,
it
would
just.
It
would
be
really
cool
to
try
to
make
some
points
of
connection
across
the
work
groups.
That's
all
so
I,
don't
think
we
ever
specify
like
the
metrics.
That
would
be
worked
on
if
I
recall
in
the
like
the
descriptions.
Okay
or
you
could
check
me
if
I'm
wrong,
the.
B
B
E
Moving
forward,
that's
just
that
was
a
thought.
I,
don't
know
how
other
people
feel
about
that.
I
would
agree
with
this.
Okay,
I
think
it's
something
that
can
be
worked
into
projects
I,
think
so
too.
Okay,
cool,
I,
guess
don't
with
dawn
on
the
line.
We
need
to
see
any
potential
work
with
common
or
is
it
just?
Is
it
still
too
early?
Perhaps.
A
C
A
G
E
E
E
F
A
B
E
Had
two
other
things
that
I
wanted
to
bring
up.
That's
why
I
forced
myself
to
be
here
today,
one
was
I
would
just
kind
of
like
to
point
out
an
observation
that
I
made
Georg
yesterday
that
it's
really
to
me,
it's
really
great
on
the
DNI
calls
seeing
the
number
of
different
people
who
are
there
on
a
weekly
basis.
Now
the
it
really
feels
like
the
group
of
people
is
expanding
really
positively,
so
I
just
I
wanted
to
say
that
kind
of
more
broadly.
Just
if
you
take
a
look
at
who's
on
the
calls.
B
B
F
A
F
E
So,
as
part
of
the
coming
open
source,
Leadership
Summit
we're
taking
a
look
at
the
Charter
right,
so
we're
looking
at
changing
the
charter
honestly
just
to
reflect
the
structure
of
the
community
more
appropriately.
It's
not
to
really
change
the
direction
of
anything
it's
just
when
the
Charter
was
written.
E
It
was
aimed
around
software
and
technical,
but
obviously-
and
it
didn't
account
for
the
working
groups,
and
now
we
obviously
have
working
groups
and
just
trying
to
update
the
Charter
there.
But
one
of
the
things
that's
in
the
Charter
is
this
point
all
new
inbound
code.
Contributions
must
be
accompanied
by
a
developer
certificate
of
origin
sign-off
and
we're
not
doing
that.
So
any
work
working
group
is
doing
this.
No.
F
H
F
G
F
E
E
F
E
E
H
I
I
mean
I
had
a
similar
issue
that
came
up
within,
like
it
laughs
I'm,
you
know.
Apparently,
that's
like
you,
don't
have
to
do
them
in
command
line,
but
if
there's
an
easy
way
to
do
that
in
github
and
make
sure
that
it's
kind
of
spelled
out
in
the
contributing
doc
that
you
know
when
you're
doing
this
through
github
like
you're
signing
off
what
you're
signing
off
on
DCL,
there
might
be
an
easiest
thing
to
do,
but
that's
just
my
thought.
I
know.
E
F
G
E
I
F
I
A
H
Way
around
that
woods,
I've
worked
on
projects
that
have
put
specific
templates
in
to
pull
requests.
So
when
you
create
a
new
one,
there
is
a
specified
template
on
what
you
have
to
do.
Yes,
it
will
be
rejected.
If
that
you
try
to
put
something
in
without
the
template.
So
in
the
template,
you
could
have
whatever
words
you
need
to
make
it
a
legitimate
DCO
like
I
so
and
so
hereby
verify
you
know
whatever.
Whatever
words
you
need
and
it
would
just
be
transparent.
H
H
F
E
I
C
H
H
H
H
E
D
The
main
particle
form
of
a
seafood
dish:
is
there
that's
what
you
now
have.
You
cannot
do
this,
not
in
their
community
from
there
working
to
do
you
need
to
do
with
that
engine,
and
that
means
that
you
cannot
use
the
online
I
did
all
of
that
it
provides,
for
instance,
between
you
know
the
name
of
measurable
some
people
have
that
some
people
are
doing
that,
maybe
with
each
may
continue.
So
it's
the
only
implication.
I've
been
working,
the
practical
thing
to
do
that.
E
D
What
I
mean
what
I
mean
is
that
when
you
are
making
that
change
the
the
other
working,
the
page
indeed
have.
As
far
as
you
know,
your
decision
making
means
that
that
to
me
can
cannot
be
single.
You
need
to
do
that
from
there
get
entities,
click
male,
which
means
that
I'm
right
people
cannot
do
conditions
that
by
clicking
on
the
heat
on
any
file
and
the
word
interface
and
changing
something
simple
that
doesn't
really
give
to
poor,
King
and
I'm
sorry
to
loan
their
the
food
of
the
story.
That's
my
convenience
management.
A
A
D
D
F
D
D
H
F
Basically,
a
summary
of
what,
if
you
go
to
that
developer,
certificate
of
origin,
org,
that's
kind
of
a
summary
of
what
that
says.
Basically,
basically
you're
saying
I,
Don
Foster
I'm
allowed
to
contribute
this
code
to
this
project
and
I'm,
not
you
know,
I'm,
not
contributing
something
that
I
shouldn't
that's
under
a
different
license,
for
example,
and.
F
E
F
J
D
F
So
this
is
this
is
the
example
of
how
we're
doing
it,
and
this
is
what
the
commit
looks
like,
and
this
is
the
command
that
you
used
to
to
add
to
add
this
to
the
bottom
of
your
commit
message:
I
mean
I'm.
Guessing
you
type
that
right
into
the
into
the
commit
message.
I
mean
it's
easier
to
do
it.
Yes,
because
it
pulls
it
right
from
your
get
config.
C
F
C
F
D
Know
there
is
an
opening
bid
for
that,
but
I
don't
know
if
that's
only
a
helper
so
that
we
can
also
write
it
here
under
field
or,
if
you
think,
that's
something
else
that
can
be
somehow
verified
or
something
I.
Don't
know.
Iii
thought
that
it
was
doing.
Some
kind
of
digital
thing
is
over.
Then
we
dinner
and
it
doesn't.
F
D
D
E
D
I
I
As
I
said
of
like
a
quick
question
at
the
end
I'm,
because
I
think
a
lot
of
us
are
been
in
this
for
a
while,
so
I
mean
I
want
to
know
from
from
an
outsider
perspective,
if
somebody's
like
approaching
in
chaos
for
the
first
time,
is
there
like
a
huge
benefit
over
having
a
version
like
metrics?
Would
people
even
want
to
like
look
at
what
was
released
like
six
months
ago,
but
that's
just
a
question
like
I
love
to
hear
people's
feedback?
I
D
Think
that
one
of
the
comments
by
a
talking
parrot
is
a
real
difference,
because
it
sends
up
north
it
now
to
the
default.
What
I
was
versioning
the
global
level?
Let's
say
all
the
metrics
person,
something
wine,
some
other
people,
you
know
versioning
everything
they
live.
We
have
devotion
to
this
material,
so
I
was
more
at
level
of
religion.
D
D
B
B
And
I
think
Toby's
point
is
more
about
releases
having
the
releases
or
a
release
in
general
lets.
People
know
that
there's
something
that
they
can
reference
and
apply.
That
is,
you
know,
complete,
like
I,
think
implied
by
the
idea
of
a
release
from
Toby
I.
Think
is
the
idea
that
whatever
we
are
releasing
is
reasonably
complete
by
some
measure,
so
we
wouldn't
release
metrics
that
are
not
fully
fleshed
out.
B
D
F
Getting
at
Toby's
last
last
in
there
he
says
basically
that
he
doesn't
think
there's
consensus
as
to
what's
needed,
which
is
absolutely
true
and
I.
Think
that's
what
we
have
teed
up
for
a
decision
at
the
governing
board
meeting
it
that
open
source
Leadership
Summit,
because
we
can't
decide
what
technical
solution
we
want
until
we
decide
whether
or
not
we
need
version
2
metrics,
and
that
needs
to
be
a
decision.
That's
made
now.
D
That,
if
we,
if
we
can
find
a
consensus
in
the
community,
it
would
be
nice
because
I
think
that's
very
likely
the
board.
It
just
means
it
with
it.
If
we
don't
have
a
consensus,
then
we
need
to
be
very
specific
on
how
to
explain
it
to
the
board,
because
many
of
the
people
that
maybe
don't
have
the
components
and
it
can
be
lengthy
discussion-
we
won't
have
to
rob
him
and
with
operational
today,
this
kicad
was
trying
to
basically
beat
cancer
I.
Think.
D
I'm
still
thinking
that
you
need
Beauchemin
and
I
think
that
it's
very
working
at
the
school
or
they
all
matrix,
legal,
not
legitimate
and
and
the
venetie's
they
are
simplify
things
from
the
point
of
view.
It's
the
only
moment
where
you
need
to
do
everything
coordinated
so
that
we
three
months,
for
instance,
you
can
advance
before
the
metrics
independently
and
before
we
need
you
need
to
basically
coordinated,
and
only
once
every
3-4
months
but
I'm
open
to
other
okay.
E
It's
it
is
interesting
to
me
how
much
and
how
many
different
opinions
there
are
on
this.
This
has
been
interesting
to
me
just
in
terms
of
versioning
in
general,
I
didn't
I,
didn't
think
it
was
that
thorny
of
an
issue,
but
apparently
it
is
in
good
for
a
good
or
bad
I
don't
mean
I,
don't
mean
to
say
people
are
right
or
wrong.
I
just
found
it
interesting
that
there's
so
many
different
thoughts
on
this
I
am
a
little
concerned
that
we're
just
gonna
go
in
circles
forever.
What
dumb
I
guess.
B
I
Yeah
and
my
concern
is
I
mean
if
there's
real
bill,
you
know
demand
for
because
I
mean
there's
a
certain
amount
of
work
that
needs
to
be
done.
Infrequent
have
version
metrics
right,
I
mean.
If
there's
no
demand
for
it,
then
then,
why
go
through
the
pain
like
having
like
different
versions?
I
coming,
however,
many
times
you
release.
So
that's
that's
sort
of
my
concern
and
if,
if
there
is
real,
though
outcry
for
doing
this,
then
why
take
on
an
additional
word?
Cord
I
mean
this.
Somebody
will
have
to
do
this.
D
Delivery
is
fine
as
long
as
you
can
tag
a
specific
point
home
we
want
to.
Let's
say
we
leave
beta
and
that's
mainly
for
reference.
It's
not
only
for
saying
this
is
better
than
anything
else,
or
simply
that
is
yes.
This
is
the
release
so
that
in
the
future,
if
I'm,
a
parent
and
I
know
what
I'm
implemented,
because
usually
this
is
going
to
be
a
moving
target
even
for
the
metrics
that
we
can
find
more
conciliated,
maybe
one
year
from
now,
we
need
to
change
things
in
there
and
and
even
for
the
discussion
itself.
D
F
F
Opinions
either
way,
but
I
do
think
that
someone
needs,
like
you,
said:
Sean.
Someone
needs
to
synthesize
this
and
put
together
a
pros
and
the
cons
document,
and
we
need
to
get
some
clarity
for
for
the
board
to
make
a
decision
on,
because
every
time
we
talk
about
this
in
this
meeting,
we
just
go
in
circles
and
don't
get
any
kind
of
any
kind
of
a
consensus
and.
A
I
D
That
name
and
that's
what
we
mean
for
say
whatever
time
to
close
an
issue
time
to
finish
code
review
number
of
innumerable,
very
wearable
and
an
either
we
had
proceeds
or
all
the
effort.
There
is
no
sense
because
of
you.
If
we,
if
we
are
discussing
a
lot
about
who
do
we
count,
March,
teammates
or
not,
we
cannot
don't
do
requests
or
only
those
that
are
close
whatever.
H
I
Maybe
I'm
making
things
too
complicated,
but
you
know:
does
it
like
there's
a
vendor
that
wants
to
implement
specific
aspects
of
version,
2
or
chaos
like?
Do
they
need
to
implement
everything
or
you
know,
do
they?
You
know
Kenda
is
a
simple
man,
98%
of
it
and
2%
of
it.
They
just
you
know,
create
their
own
implementation
of
it.
So.
D
That's
something
that
we
didn't
define
there,
but
they
think
that
at
least
they
should
be
evolved
of
saying
something
like
we
are
implementing
decent,
decent,
decent.
These
metrics
of
all
these
program
asks
of
cows
to
version
of
version
2,
for
instance,
and
then
maybe
we
can
lay
that
aside,
while
either
you
implement
everything
or
you
cannot
change
cows
or
whatever,
that's
something
that
we
can't
effect
in
the
future.
But
at
least
for
now
I
would
like
to
know
this.
Software
is
implementing
universe
into
this
business
of
metrics.
It's
exactly
what
fortune
to
change.
E
Ray
my
thought
on,
and
that
is
in
terms
of
versioning
that
I
think
it's
possible
that
the
way
that
the
metrics
are
determined
might
change
over
time
right.
So
I
think
that
the
versioning
it
just
at
least
specifies
that
whatever
I'll
just
pick
version
2
versus
version
1
version
2
is
a
finer
grain
specification
of
a
particular
metric.
D
Be
all
so
that
we
move
on
to
make
changes
so,
for
instance,
consider
time
to
close
the
full
breakfast.
Imagine
that,
right
now
we
decide
that
we
are
having
this
metric
and
we
call
chuckling
ladies
time
to
close,
put
records
and
we
decide
that
all
the
food
record
should
be
in
key,
but
we
discuss
for
one
year
or
whatever,
and
somebody
comes
with
a
nice
use
case
and
they
say
well.
That
number
is
really
not
useful.
It's
much.
D
It
is
much
better
to
consider
only
those
who
report
that
we're
pretty
closed
and
forget
about
those
that
were
a
module,
because
in
github
Geneva,
now
and
whatever,
and
then
with
this
okay,
let's
move
the
definition
to
say
when
we
say
time
to
close
requires
we
say
only
those
that
were
actually
close.
That's
going
to
change
the
numbers
in
a
lot
of
repositories
and
you
need
to
be
able
of
saying
I'm
supporting
this
or
this
over
version
because
they
are
different
and
they
taken
to
have
different
results.
D
And
you
cannot
really
say
this
is
better
than
the
other
or
even
this
is
more
vibrant
than
the
other.
They
are
just
different
and
maybe
for
any
reason
we
decide.
The
second
one
is
more
useful
and
we
think
too,
that
that's
something
that
shouldn't
shouldn't
happen
a
lot,
because
we
also
pause
it
usually
set
of
metrics
from
the
beginning.
But
who
knows
we
don't
really
have
a
lot
of
experience.
More
people
are
going
to
join.
D
Maybe
they
have
new
opinions,
new
ideas,
new
use
cases
of
weeded
approachable,
so
I
foresee
that
in
the
next
few
years,
very
likely
some
of
our
core
metrics
are
going
to
change
the
minute.
If
we
are
I
mean
if
we
get
the
feedback
from
the
community-
and
we
heard-
and
we
listened
to
the
feedback
from
the
community
that
may.
H
D
Or
not,
but
my
my
impression
is
which
would
be
prepared
for
that
and
that's
like
in
any
a
standard.
So
things
change
with
time
and
Uniqlo
just
to
go
to
that
and
you
need
to
say
this
is
a
standard
version,
something
and
maybe
in
three
years
from
now
it
will
offend
the
person
of
the
standard
but
but
again
I'm
happy
to
try
any
approach,
even
continuous
delivery
or
forgetting
about
or
Shannon.
Let's
try
that
for
six
months
or
whatever
and
then
we'll
discuss
gain
so
I'm
happy
with
an
additional
decision
the
board
may
take
so.
E
D
I
think
that
the
main
advantage
for
my
particular
continuous
delivery
and
not
dodging
not
taking
it
in
action
or
something
is
that
first
of
all,
we
can
always
say.
Well,
you
need
to
support
the
latest
version,
which
is
nice,
but
they
don't
know
if
that's
be
able
and
unshaken
didn't
need
to
care
about
versioning.
So
you
don't
need
to
do
cleaning
over
time
with
women,
for
whatever
your
guests
say.
This
is
the
version
go
to
the
website,
and
this
is
always
the
latest
version,
and
that's
it
and
and
let's
forget
about
the
story,
I
think.
F
F
B
D
D
To
a
specific
point
in
the
past
history
with
versioning,
you
can
point
attacks
in
the
in
the
past
history,
but
you
cannot
just
say:
go
to
your
party
to
me
about
the
latest
person,
because
we
are,
you
need
to
wait
at
delivery,
so
maybe
frame
in
this
way.
What
can
you
do
on?
What
you
cannot
do
with
this
model
could
be
all
too
easy,
and
it's
not
saying
this
is
better.
Wars
depends
on
your
scenario.
I
just.
E
E
E
And
so
with
respect
to
s
P
D
X,
if
you
are
on
their
license,
email
list,
there's
a
lot
of
conversation
that
goes
on
about
including
new
licenses
on
this
license
list
and
how
how
to
go
about
doing
that.
But
those
conversations
aren't
necessarily
reflected
in
this
list.
It's
only
post
release,
but
something
is
approved.
It's
only
after
something
is
approved,
and
then
at
that
point
in
time
that
this
license
list
gets
about.
D
The
same
time-
and
you
can
save
my
soul-
Brewer
is
reporting
with
PDF
version
3,
for
instance,
which
is
the
one
we
are
seeing
right
now,
and
that's
that's
quite
important
because
in
that
case,
I
know
that
all
the
licenses
in
this
list
are
supported
on
all
over
and
the
names
and
the
banks
and
everything
that
went
to.
You
is
exactly
what
this
petition
yep.
A
So
I
have
a
question
based
on
what
Ray
was
asking
earlier
and
looking
at
this
list,
and
is
it
important
to
have
past
releases
on
the
website?
Is
it
enough
for
you,
hey
sis,
to
have
here
what
the
current
version
is
and
if
someone
wants
to
talk
about
the
older
version
to
point
into
the
github
repository
or
do
we
need
all
versions
on
the
website.
D
So
I
really
don't
know
how
important
thing
we
got.
You
can't
recover
that
if
they're,
what
we
use
it,
the
most
is
the
most
easiest
to
see
them.
It
is
the
better
so
that
between,
let's
use
the
website,
if
only
a
few
people
are
going
to
use
them
and
then
now
that
you
won't
go
through,
they
were
straight
up.
Also
good
enough.
D
So
I'm
here
I
think
that
the
idea
from
the
fighting
between
based
on,
for
instance,
do
you
know
that
released
chainsaw
and
the
meaning
of
different
rankings
and
the
parameters
and
everything
may
change
from
version
to
the
next
part.
Most
of
the
people
are
working
within
a
specific
version
of
Python
and
they
need
now
for
my
specific
person.
J
J
A
D
In
any
case,
I
suggested
that
we
take
3
discussions,
which
happened
in
parallel,
but
I
think
they
are
different.
The
first
one
is
whether
we
want
to
do
released
in
mono
continued
delivery
or
religion.
The
second
one
is
whether
we
want
to
do
releases
at
the
level
of
all
the
metrics,
the
war
or
at
the
level
of
a
specific,
metrics
and
I
think
we
have
a
certain
consensus
that
there
is
to
do
it
at
the
level
of
program.
D
But
still
this
is
another
discussion,
and
the
third
one
is
how
to
implementing
whichever
the
decision
would
take.
What
goes
to
the
repository?
What
goes
to
the
website
on
how
we
tax
and
that
the
three
discussions
I
think
are
different,
sometimes
when
we
are
mixing
them,
and
that
makes
more
the
people
to
dignity.
F
I'm,
a
completely
separate
note,
I,
you
know,
I
know
these
are
informal
meetings,
but
we
have
a
lot
of
really
good
discussions
and
you
know:
Georg
makes
a
point
about
going
back
and
and
having
to
watch
the
videos
to
synthesize
the
discussions.
Have
we
and
we
thought
about
maybe
having
notes
for
this
meeting
and
just
assigning
a
note-taker
at
the
beginning
of
each
one.
Oh.
F
E
E
E
K
George,
do
we
also
have
link
of
this
conversation
like
the
recordings
to
the
github
page,
because
we
specify
like
a
section
where
the
meetings
and
things
like
that
in
that
case,
maybe
somebody
joining.
You
could
also
like
backwards
to
see
some
of
the
things
that
we
discussed
like
at
least
the
notes
and
things
like
that.
We
should
have
a
pointer
to
some
of
these
meetings.
Like
the
previous
me,
yeah.