►
From YouTube: CHAOSS.Community.May.12.2020
Description
CHAOSS.Community.May.12.2020
A
Everybody
today
is
Tuesday
May
12th.
It's
the
chaos
weekly
caste
community
called
I
jotted
down
a
few
things.
Other
people
can
bring
things
they
like.
So
if
you
could
add
yourself
to
the
minutes,
tell
us
how
you're
doing
or
I
think
ahead
in
there.
You
could
include
something
that
you
have
on
your
desk,
that
we
can't
see
as
well,
if
you'd
like
to
show
anybody
on
this
call
something
I
hear
something
for
everybody:
I
have
an
Auslan
2016
wooden
token.
A
C
A
All
right
so
yeah,
so
as
people
are
adding
themselves
I
think
the
few
things
that
I
had
on
here
is
the
the
first
thing
I
had
on
here
that
I'd
like
to
talk
about
a
little
bit
here
is
the
github
migration.
So
this
was
brought
forward
to
kind
of
talk
about
and
I
have
the
document
there
and
I
do
think
we
need
to
get
probably
some
just
finality
on
this,
so
I
had
put
in
there
whether
or
not
we
should
have
a
board
vote
on
this.
A
So
if
you
take
a
look
at
the
document
which
is
available
for
anybody,
who's
been
available
for
a
while,
there
are
still
a
number
of
outstanding
issues
here.
The
concerns
I,
don't
know
page
2
or
3,
or
something
along
those
lines
and
I
think
I
had
said
in
the
email
to
the
list.
Just
simply
voicing
the
concerns,
probably
isn't
enough,
it's
not
the
same
as
addressing
those
concerns,
so
it
does
seem
like
there's
a
number
of
issues
that
need
to
be
addressed,
probably
a
bit
more
formally
right.
D
I
think
the
biggest
one
I've
heard
recently
is
just
sort
of
trying
to
assess
the
cost
of
doing
this,
both
in
terms
of
labor,
I,
think
I.
Think
we've
addressed
that
the
cost
in
terms
of
how
people
find
chaos
I
think
we
have
a
way
of
doing
that
and
get
lab,
but
I
don't
think
we've
done
any
work
to
assess
the
cost.
E
Yeah,
that's
my
concern,
not
necessarily
from
a
financial
standpoint
unless
you're
talking
about
like
people's
time
I'm
concerned
about
I'm
concerned
about
lost
momentum,
so
I
feel
like
we
made
the
decision
without
knowing
how
much
time
it
was
gonna
take
to
actually
implement
it.
And
if
it's
you
know,
I,
don't
know
a
few
man-hours.
Then
it's
not
a
big
deal.
If
it's
hundreds,
then
that's
gonna
be
a
significant
loss
to
the
momentum
that
we
have
right
now,
both
on
the
software
side
on
the
metrics
definition,
side
and
I.
A
D
Haven't
taken
the
time
to
actually
assess
at
all
how
much
I
think
it'll
cost
the
augur
team
to
Tim
move
it
over
and
and
I
don't
have
an
assess
what
it's
gonna
cost
risk
in
terms
of
risk
has
more
software
sort
of
coupled
with
it
than
some
of
the
other
working
groups
in
terms
of
a
complex
piece
of
software,
so
I
haven't
even
done
anything
to
assess
that
cost
or
at
the
working
group
level
or
at
the
software
level.
A
So
I
personally
my
biggest
concern
mostly
because
I
don't
spend
a
ton
of
time
in
the
software
is
I,
think
largely
to
Don's
point.
It's
just
it's
a
community
thing
right
and
we
have
people
we're
doing
really
good
work
in
in
the
environment
were
in
now
in
just
any
time
and
effort
that
it
takes
to
do
that.
Move
is,
is
lost
on
that
work
over
the
summer
and
that's
that's
just
a
concern
that
is
from.
A
I
didn't
mention,
but
whenever,
whenever
that
might
be
so
one
of
the
things
I
put
in
there
is,
is
it
completely
so
one
of
the
reasons
that
this
came
up
and
really
in
the
first
place
from
what
I
understand
was,
were
more
labs
perspective
because
they
have
so
many
different
repositories
on
github.
They
were
having
a
hard
time
with
issue
tracking
so
that
each
repository
would
have
its
own
set
of
issue
and
developers
would
have
to
go
through
each
one
of
those
repositories
and
really
triage.
F
A
C
F
G
It's
it's
what
you
were
saying
Matt
my
opinion.
That
was
our
first,
but
that
was
our
first
interest
to
move
to
gridlock
was
because
what
you
said,
but
we
can
explore
different
options
in
github.
It's
not
it's,
not
a
problem.
In
any
case,
I've
been
checking
today
the
numbers
about,
because
another
concern
is
the
cost
in
continuous
integration,
because
we.
G
G
I've
been
checking
the
what
how
many
minutes
we
have
been
doing
that
for
the
last
month
and
we
passed
by
far
the
2000
minutes,
which
means
that
we
will
have
to
pay
probably
and
if
we
have
to
pay
at
least
it's
like
20,
to
get
9000
9000
minutes.
We
need
to
pay
twenty
dollars
per
user
month,
which
I
think
for
us
is
unaffordable.
G
F
D
G
D
D
F
D
A
G
D
C
F
C
G
B
It's
it's
part
of
this
standard
offering
for
open
source
programs
and
I'm
I'm
gonna,
like
a
make
a
suggestion
here,
I
mean
I've
been
trying
to
abstain
from
the
conversation
for
obvious
reasons.
I
have
an
obvious
conflict
of
interest,
but
I
mean
I
do
agree
with
both
Don
and
and
Shawn
in
terms.
I
think
we
need
to
figure
out
the
I
mean,
even
if
it's
like
number
of
person
hours
how
many
hours
is
going
to
take
to
through
the
transition,
even
just
a
code
repository
like
unless
and
then
you
know
whatever
the
number
is.
B
Let's
say
we
come
up
with
a
number
like
a
50
hours,
I
think
Shawn,
especially
for
argue,
you
need
to
make
a
decision.
Is
it
worth
it
and
I
think
the
Santi
is
your
point:
I
mean
you
can
keep
this
keep
the
Travis
ei4
for
a
while,
and
then
you
know
if
you
want
to
transition
later
to
to
get
lap
CI
CD.
You
can
do
that
later
on,
but
I
I
know
like
from
a
lot
of
people's
experience.
D
Yeah,
you
know
I
think
just
this
spring.
We
made
some
changes
this
spring
using
docker
containers
instead
of
the
old
server
setups
that
we
were
using
and
I
mean
just
that
effort
alone
took
us
about
a
hundred
hours.
Ish
I
would
estimate
without
talking
to
Carter
who's,
the
one
who
did
it
I
mean
it
was.
It
was
months
of
working
on
all
the
little
glitches
and
the
first
time
we
did
it
without
the
docker
containers.
B
There
needs
to
be
a
consensus
from
the
technical
community
that
this
is
the
right
thing
to
do
or
not,
and
then
boards
just
get
simple,
informed
and
I.
Don't
know
if
a
lot
of
the
board
member
is
you
know
why
the
board
members
would
have
to
get
involved
in
like
even
improving
this
thing,
whether
to
do
it
or
not,
but
that's
just
my
take.
E
I
guess
I
was
thinking
that
maybe
the
board
should
approve
it,
because,
just
mostly
mostly
approving
that
trade
off
the
the
time
that
it's
going
to
take
to
make
this
to
make
this
change
versus
what
we're
gonna
lose
and
in
momentum
on
the
project
that
was.
That
was
the
bit.
That
feels
to
me
like
a
like
a
board
decision,
less
about
the
technical
ins
and
outs
of
what
it
is
that
we're
doing,
but
just
the
kind
of
the
effort
and
what
we're
giving
up
to
do.
It.
A
B
A
A
Just
it
seems
really
like
nebulous
to
me
so
whether
it's
the
board
or
it's
an
assigned
technical
committee
or
an
assigned
committee
that
actually
makes
the
recommendation
I
would
love
to
put
a
penny
like
some
sort
of
final
point
on
this,
that
we
are
doing
this
or
we
are
not
doing
this
because
from
a
governance
perspective,
that
just
seems
a
lot
cleaner
to
me
because,
as
it
stands
right
now
and
I've
been
on.
All
of
these
calls
and
taking
a
look
at
this
document,
it
seems
still
very
nebulous
to
me
it
does.
A
H
To
send
I'm
on
the
board
and
I'm,
not
I,
haven't
been
following
this
very
closely,
so
I
I
wouldn't
want
to
make
the
technical
decision.
However,
if
it
helps
the
community
to
say
that
okay,
let's
prepare
a
material
for
the
board,
so
that
they
have
a
really
good
understanding
of
why
we
are
doing
what
we
are
doing,
how
we
are
doing
what
the
trade-offs
and
then
the
board
can
vote
on
it,
not
from
technical
perspective,
but
kind
of
putting
that
stamp
based
on
the
material
that
has
all
the
factors
and
the
decision
points
outlined.
H
If
that
helps,
I
think
it
would
make
sense
to
to
sort
of
formalize
the,
and
then
we
can
say
that.
Okay,
it
was
said
it
was
presented,
there's
the
material
and
we
made
the
decision
because
of
this
and
this
and
that
and
then
it
will
be
clear
for
everyone.
So
if
that
from
process
perspective
is
not
a
too
big
overhead,
I
think
we
could
probably
do
that,
because
I
assume
that
it
also
can
help
to
people.
A
H
Yes,
but
again,
I
don't
want
to
force
it
if
we
all
feel
that
this
is
reasonable.
I
think
this
could
work,
because
I
also
think
that
it
could
put
an
end
to
the
kind
of
fuzzy
feeling
of
well.
We
kind
of
want
to
do
this,
but
but
we
have
some
cons
that
we
are
not
sure
about
so
just
kind
of
formalize
it.
Okay,
don't
want
to
create
too
much
overhead
either,
but
again,
I
think
this
could
work.
D
D
They're
like
so,
the
costs
are
easy,
it's
the
human
time
costs
of
what
we've
already
done,
with
Travis
CI
and
from
from
a
benefits
perspective.
It's
I
understand
from
an
issue
tracking
point
of
view.
Ger
more
lab
also
see
some
benefits,
so
I
think
just
listing
costs
doesn't
provide
the
full
picture.
Listing
benefits,
provides
the
whole
sort
of
complete
financial
ish
trade-off.
D
C
D
G
Project
strong
it
hard
to
give
up.
This
is
automatically
so
just
to
paste
a
URL,
the
name
of
the
group
on
any
more
than
repository,
and
it
does
everything
but
I.
Don't
think
that
me
creates
wiki
pages,
I'm,
pretty
sure,
immigrants,
the
source
code,
the
issues
because
for
sure
not
but
I'm,
not
sure
about
all
that
documentation
that
you
might
have
there.
It.
D
G
G
G
D
E
Yeah
at
the
bit
that
I'm
worried
about
is
more
on
the
integrations
and
automation,
so
anything
that
we
have
automated
and
github
any
integrations.
We
have
with
continuous.
You
know:
CI
system
CT
systems,
whatever
whatever
we
have.
That's
automated
and
kind
of
you
know
tied
into
github
in
some
way.
All
of
that
is
gonna
have
to
be
migrated
as
well.
I'm
not
actually
worried
about
clicking
that
button
that
migrates
the
stuff
from
github
to.
F
E
G
Very
easy
what
we
have
in
Chaves
is
very
simple,
so
it
will
be
really
easy
to
do
to
incorporated
in
in
good
luck,
but
I
I
understand
that
maybe,
like
a
soul
holy,
they
might
have
waterings
done
so
yeah
I'm,
not
sure
about
that,
especially
when
someone
said
that
they
have
been
spending
like
months,
creating
their
by
them.
So
I.
A
Am
can
I
make
a
recommendation,
then
kind
of
based
on
this
and
see
how
people
react
to
it
that
we
do
actually
establish
a
group
of
people,
a
committee
of
folks
who
are
either
interested
in
or
will
be
affected
by
this
change.
So
that
would
be
it's
not
the
board
initially.
But
it's
a
group
of
people
with
an
interest
or
who
would
be
affected
most
closely
by
this
change
to
form
a
committee
and
we
put
together
a
formal
document
that
would
represent
everything
with
respect
to
estimated
time
estimated
effort
and
estimated
cost.
A
So
the
estimated
time
it
would
take
to
move
the
working
groups-
yes,
but
made
time
it
would
take
to
move
the
the
software.
The
effort
in
doing
that.
So
you
know
some
may
be
an
hour
of
time
and
it's
not
a
lot
of
effort
either
so
maybe
an
hour
of
time
and
it's
a
very
challenging
effort
and
then
any
financial
cost
that
might
be
incurred
in
making
this
move
so
so
I'm
sort
of
where
everything
gets
represented,
whether
it's
a
cost
or
a
benefit.
A
A
One
option
that
I've
been
thinking
about
would
be
that
people
may
tell
me
I'm
crazy
but
say
we're
more
lab,
would
sit
down,
get
lab
and
be
mirrored
on.
Github
and
the
rest
of
chaos
would
stay
on
github,
I,
don't
know
if
that's
even
a
thought.
You
know
that
you
would
actually
have
your
community
split
like
that,
and
then
this
has
brought
forward
to
vote
on
by
the
board.
A
D
Yeah
and
I
think
obviously
you're
more
lab,
won't
and
I.
Think
there
needs
to
be
a
couple
working
groups,
I
think
augur
should
commit,
I,
think
augur
and
guram
or
lab
should
commit
X
number
of
hours
to
a
pilot
for
for
us,
we've
got
one
repository,
so
that's
easy,
I
mean
for
us.
A
pilot
would
be
doing
the
whole
thing.
D
My
back-channel,
with
Carter
is
approximately
what
that
would
cost.
So
we
can't
pilot
the
whole
thing,
but
we
could
pilot
getting
started
and
seeing
which
of
our
assumptions
are
valid
and
update
our
estimates
based
on
trying
to
do
it
a
little
bit
and
then
project
out
actual
costs
based
on
what
we
learned
in
the
pilot.
But
we
won't
finish
the
migration
in
the
pilot
phase.
G
D
I
think
we
should
pick
a
couple
two
to
three
work:
yeah
I
guess,
I'm
gonna
have
that
my
workers
maybe
pick
two
of
the
working
groups.
I
suggest
to
risk,
be
one
of
them
and
that
that
it
doesn't
change
the
public
facing
nature
like
this
is
something
we're
doing
behind
the
scenes,
not
promoting
as
something
we're
doing,
but
just
we
separately
without
announcement,
try
it
so
that
we
understand
better
what
it
is.
We're
talking
about
doing.
A
Could
we
are
people
do
what
people
want
to
form
a
committee
on
this?
That's
not
done
here
in
the
community
calls
we
actually
talked
about
how
we
would
take
a
look
at
the
costs
and
then
what
the
proposal
would
be
to
me.
That
makes
more
sense
that
we
take
the
document
that
georg
started
and
really
start
kind
of
looking
at
the
costs
associated
with
that
document
right,
but
that
wouldn't
occur
here.
A
A
A
A
I
D
D
A
Any
other
thoughts,
this
is
super
good
conversation.
Thank
you
everybody
for
this.
This
is
crazy
important
for
the
project.
So
all
right.
Well,
that's
that
took
time,
but
that's
okay
and
a
few
more
updates
one
is.
We
got
accepted
for
rule
season
of
Docs,
so
venue
is
on
thanks
venue
for
your
hurting
that
so
that's
great.
Take
a
look
at
now,
he's
been
sending
out
a
few
email
for
folks
that
are
gonna,
be
mentoring
for
google
season
of
backs.
There's
a
little
bit
of
forum
stuff.
F
A
This
is
great.
This
we're
working
under
the
umbrella
of
the
Linux
Foundation
we
do
have
is
it
Georg
is
a
nine
google
Summer
of
Code
students.
H
A
Now
treaty
statement
and
then
will
yet
to
be
determined,
google
season
of
Docs
I'm,
one
of
the
things
that
we
did
just
chat
about
between
Matt
Snell
have
the
idea.
Georg
and
Ray
is
we're
gonna
offer
to
all
of
the
google
Summer
of
Code
and
outreach
II
students
registration
for
OSS
na
in
virtual.
So
it's
fifty
dollars
and
I.
It's
a
nice
way
to
get
all
of
the
students
kind
of
involved
in
a
in
open-source.
F
D
F
F
A
So
one
of
the
things
that
we
do
ask
is
that
the
students
introduce
themselves
on
their
the
mentees
and
introduce
themselves
on
the
mailing
list.
So
if
you
could,
please
say
hi
back,
that
would
be
great
and
they're
also
going
to
be
doing
blogging,
so
Kevin
I
think
Toula
had
reached
out
to
you
with
respect
to
some
blogs
on
the
web
page.
That's
all
worked
out.
Yep.
I
I
have
a
we
have
the
first
pull
request
for
I.
Think
it's
an
outreach
blog
okay
yeah,
that's
told
so
it
is
I-
think
it's
ready
to
be
merged
as
soon
as
it's
merged.
I
will
put
it
on
the
website.
A
Right
now,
Thanks
all
right,
I'm,
moving
down
a
list
kiosk
on
North
America
we're
still
moving
forward
with
this.
So
thanks
for
everybody
kind
of
on
the
events
team,
so
we
had
gotten
some.
Some
quote:
some
some
dollar
quotes
from
the
Linux
Foundation
we're
slowly
working
through
kind
of
what
it
would
cost
to
run
cask
on
an
a
we're.
Looking
if
I
have
a
few
notes
on
there,
it
looks
like
it's
late.
A
A
E
C
E
A
F
E
F
A
I
A
E
We
have
to
have
some
hours,
I
mean
we
could
I
I
feel
like
I
feel
like
we
should
step
back
a
bit
and
I've
been
saying
this
a
lot
and
calls
about
organizing
virtual
events.
I
think
we
should
step
back
and
think
about
what
we
really
want
to
accomplish
out
of
chaos,
kaan
and
what's
the
best
way
to
accomplish
that
in
a
virtual
format.
And
how
important
is
it
that
we
accomplish
this
in
the
first
place?
I'll
be
honest:
we
decided
to
just
cancel
the
contribs
summit
for
Amsterdam.
E
C
A
In
favor
of
cancelling
it
personally,
personally,
that's
just
me
altogether.
That's
me
speaking
on
my
behalf,
I
think
we
should
focus
on
FOSDEM
in
2021.
I
think
the
time
the
summer
would
be
better
spent
with
google
Summer
of
Code
and
outreach
he
and
Google
season
of
Docs
and
advancing
the
metrics
and
doing
what
we
can
otherwise
outreach
wise
I
agree
that
I
think
people
are
burned
out
on
some
calls,
and
that's
my
take
so
everything
I
have
here
was
mostly
just
trying
to
capture
what
I
was
kind
of
hearing.
E
I
I
would
100%
agree
with
that.
I
actually,
actually
don't
think
we
should
do
a
kiosk
on
North,
America
I
think
we
should
focus
on
pasta,
but
we
have
some.
We
have
a
couple
of
other
things
that
you
know
the,
so
we
have
the
podcast,
so
that's
new.
So
that's
something
that
I
think
is
fantastic,
that
we
can
create.
F
E
Content
out
there
that
we
weren't
getting
out
before
the
other
thing
that
I
really
think
needs
some
love.
That
I
contributed
to
this
last
week
is
the
blog
we
could
be.
If
you
have
something
that
you
want
to
get
out
to
the
Kaos
audience,
you
could
record
a
5-10
minute,
video
about
it
and
do
a
little
blog
post
and
upload
the
upload
video
to
YouTube,
and
we
could
get
our
blog
kind
of
back
up
onto
sort
of
our
regular
cadence
of
something
you
know
post
a
week
few
posts
a
month,
something
and
we
could.
E
D
D
D
My
personal
assessment
is
I'm,
not
sure
the
globe
will
be
open
when
FOSDEM
occurs,
and
so
I
think
we
might
need
to
plan
for
a
longer
term,
absence
of
physically
being
with
each
other,
and
maybe
something
like
an
occasional
chaos.
Con
scheduled
cadence
a
couple
hours
in
the
chaos
hallway
meeting,
other
chaos,
people
and
talking
to
them.
E
Yeah
I've
seen
more
and
more
people
doing
that.
Actually,
so
our
organization
that
arts
program
office
within
VMware
has
a
weekly
social
hour
now,
where
we
it's
like
a
different
topic
every
time
once
it
was
like
crazy
shirts
or
something
or
pandemic
pizza,
and
so
we
have
like
you,
know
cuz.
We
do
this
weekly
and
it's
a
team
thing,
but
but
we
could
easily
like
the
to
do.
Group
is
also
doing
this,
where
they're
doing
more
frequent
kind
of
social
calls
where
it's
just
like
30
minutes.
E
B
Yeah
I
think
the
challenge
is
like
getting
like.
I
mean
what
was
great
about
the
chaos
con
we
just
had
in
Brussels
was
like.
We
had
I
think
a
lot
of
new
people
show
up,
which
is
great
I
mean
that's.
That's
like
I
mean
I
agree
with
Sean
like
I'm,
not
even
optimistic
about
events.
Next
year,
like
you
know
like,
even
if,
like
four
miraculously
somebody
decides
all
the
event
like
who's
gonna
show
up,
is
it's
a
big
concern?
B
So
I
agree
if
we
like
I,
mean
I
think
like
we're
like
really
too
close
to
July
and
August,
it's
probably
makes
sense
to
cancel
it,
but
we
probably
need
to
have
a
separate
discussion
about
how
do
we
engage
with
people
in
a
more
creative
fashion
like
outside
of
it?
That's
like
I
mean
I'm,
pretty
convinced
that
events
are
not
gonna
happen
rest
of
the
year.
It's
questionable
I've,
even
about
q1.
Next
year,
yeah.
E
And
that's
one
of
the
things
that
you
know,
I
feel
like
I
feel,
like
we've
done
too
facility
with
chaos
con
by
partnering.
Up
with
with
some
other
events.
Is
that
you,
you
do
get
a
lot
of
sort
of
fall
over
from
from
paws
down
and
from
soar
summit,
North
America,
and
so
you
get
some
attendees
that
are
interested
in
metrics,
but
wouldn't
have
thought
to
come
to
this
as
a
standalone
thing
and
I'm,
not
sure
I'm,
not
sure
how
we
replicate
that
in
the
virtual
environment.
E
That's
something
that's
really
really
difficult,
and
it's
something
that
I
think
a
lot
of
the
conference's
are
struggling
with
right
now,
because
there
are
so
many
of
these
like
kind
of
fringe
events
that
happen
around
conferences,
because
all
the
people
are
physically
located
in
the
space
anyways
and
that
I
don't
think.
We've
figured
out
how
to
replicate
that
Jared,
dippity
I
think.
D
D
C
I
also
agree
with
canceling
and
I.
Also,
second
other
ways
of
outreach.
One
of
the
just
talking
about
the
podcast
I
would
like
to
move
to
a
much
faster
schedule.
Right
now.
It's
once
per
month
is
releasing
it
I
would
like
more
help
from
the
communities
or
more
organizers.
If
we
can
get
one
more
person
to
help
with
organizing,
then
we
will
attack
for
people
organizing
so
right
now
it's
Matt
Roberge
me
Vania
volunteered.
D
Is
is
organizing
effectively
finding
who
the
people
to
interview
that
week
are
and
who
the
panelists
that
we
car
and
getting
a
time
scheduled
across
that
universe,
doing
all
the
sound
checks
and
then
you'll
tell
us
how
to
pass
it
on
to
our
producer?
Yes,
its
own
okay,
I
I,
can
do
that.
I
can
I
can
take
that
on
once
a
month,
because
it's
it's
really
important
and
I
can
handle
getting
people
together
is.
Is
there
a
public
list
of
who's
been
on
already
so
that
we
don't
repeat,
accidently,
have.