►
From YouTube: Apache Cassandra Contributor Meeting - 2020-01-21
Description
Meeting Summary:
The community and contributors remain focussed on the 4.0 release. There was broad consensus that we want to keep working towards the 4.0 QA Test Plan and a call for contributors to sign up for major components. We also touched on a number of other process discussions and agreed to take a few discussions to the mailing list.
All meeting notes can be found here: https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Contributor+Meeting
A
A
So
all
the
the
recording
I'll
post
on
YouTube
I
have
a
couple
of
I,
think
I
still
have
access
to
the
Cassandra
or
the
planets
they
have
a
channel
which
seems
fine
if
there's
somewhere
else,
we
want
to
put
it
just.
Let
me
know:
I'll
have
a
mp4
file
at
the
end
of
this,
but
we
have
an
agenda
and,
at
this
point,
I
think
we
can
just
start
walking
through
it.
If
there's
any
any
technical
issues.
This
is
a
time
I
mean
this
is
my
disclaimer.
A
If
we
have
things
you
want
to
change,
take
note,
because
that
the
very
last
thing
on
the
agenda
is
okay.
We
did
this
now.
How
do
we
want
to
change
it
so
I'm
looking
at
the
agenda
and
it
looks
like
Jordan
added
something
the
4.0
status-
and
let
me
just
add
this
in
here:
if
you're
gonna
put
something
on
the
agenda,
I
think
it's
best
if
we
have
also
like
who
wants
to
lead
the
discussion.
So
just
so,
we
keep
it
from
being
a
free-for-all
which
maybe
I
beat
the
first.
B
B
B
E
Yeah
one
thing
that
I
think
would
also
be
useful
is
to
cover
some
of
the
work
that's
active,
some
of
which
is
represented
in
that
confluence
dock,
that
I
just
linked
and
slack
them
into
the
go.
We
have
a
few
areas
that
are
complete
I
know
of
some
contributors
who
are
working
on
a
couple
that
are
currently
in
progress,
and
there
are
also
several
areas
that
don't
currently
have
a
component
owner.
So
if
somebody
would
be
interested
to
step
up
to
lead
that
area
of
testing
validation
and
test
infrastructure,
that'd
be
fantastic
as
well.
C
Yeah
and
on
that
point,
one
of
the
things
I'm
planning
on
doing
is
actually
piloting
taking
the
stuff
from
the
confluent
and
getting
it
into
an
epic
and
0
with
verbatim
the
contents
that
entire
docket
and
just
experimenting
a
little
bit
with
subtasks
to
see
if
it
might
make
sense
to
unify
all
that
in
JIRA.
That's
very
much
gonna
be
a
try
it
out
and
if
we
hate
it,
nuke
it
from
orbit,
but
if
we
like
it
run
with
it
kind
of
thing.
E
E
Cool,
maybe
we
can
start
with
just
some
active
work,
that's
going
on
toward
testing
and
validation.
That's
that's
currently
in
progress.
If
we
partition
things
into
two
segments,
one
is
things
that
are
known
to
be
issues
that
need
to
be
resolved
have
a
fluoro
release.
Those
are
things
that
are
already
noted
in
JIRA
and
I
think
screen
to
the
other
alpha
beta
or
GA
release
versions,
but
there's
also
work.
That's
going
on
to
identify
issues
that
are
currently
unknown
or
things
that
we're
not
actually
sure.
E
If
there's
a
problem
or
not
I
think
the
latter
is
a
little
less
defined.
So
that
might
be
useful
to
talk
a
bit
about
a
moment
ago.
I
linked
a
confluence
dock
in
the
Cassandra
does
slack
channel
to
cover
some
of
those
there's
a
whole
lot
of
work.
That's
gone
into
testing
and
validating,
inter
in
the
messaging,
and
any
changes
that
were
made.
I
know
that
Joey
and
Renee
in
particular,
have
worked
a
lot
with
Alexi
and
Benedict
for
validating
a
lot
of
that
Marcus
and
others.
E
Marcus
Sam
and
a
few
other
people
also
released
a
tool
called
Cassandra
DIF.
That's
really
useful
for
doing
a
complete,
exhaustive,
read
of
Cassandra
clusters
and
identifying
any
differences
in
any
column
between
the
two,
which
is
a
really
useful
way
of
spotting
issues
that
could
be
on
the
coordination
or
a
local
refight
path.
I
think
Alexis
also
have
done
an
audit
of
systems,
tables
and
internal
schema
handling
to
work.
That's
currently
in
progress
that
I'm
aware
of
it
is
on
Harry
a
tool
for
model-based
testing
of
Cassandra.
E
The
model
is
the
legal
internal
state
of
the
database,
given
responses
to
queries
that
were
issued
against
it
and
continually
issues
new
queries
and
checks.
The
state
against
that
model
work
is
going
on
to
bring
that
to
a
degree
of
completion
that
would
be
appropriate
for
a
review
and
sharing
on
JIRA.
E
One
point
that
I'm
taking
in
advance
is
that
we
have
very
few
contributors
from
European
time
zones
on
this
call
right
now,
so
I
think
the
next
call
should
very
much
be
aligned
to
make
it
easier
for
those
folks
to
join
and
also
apologize
for
my
culpability
in
selection
of
the
time
our
proposal
over
time.
So
maybe
in
the
next
call.
E
B
Yeah
sure
I
was
just
looking
at
that
on
the
so
towards
the
end
of
last
year,
I
spent
some
time
just
rereading
the
11
to
a6
patch
testing
it
a
bit
more,
both
from
a
performance
and
correctness
perspective
from
a
performance
perspective.
We
ran
it
against
some
workloads
that
are
known
to
really
tax
the
system
with
large
partitions
and
some
awesome
really
encouraging
numbers
there,
seeing
three
nines
as
second
or
two
seconds
on
the
3o
branch
and
at
the
40
50
millisecond
range
on
trunk.
So
that
was
really
encouraging.
B
From
a
correctness
perspective,
there
was
a
new
binary
search
that
I
was
implemented
as
part
of
this,
so
I
used.
Harry
Harry
has
a
kind
of
quick
theories
like
library,
and
then
it
has
all
the
things
that
Scott
talked
about
so
I
used
Harry
to
write
a
test
to
McNally
at
that,
and
that
will
be
open
sourced
as
part
of
the
Harry
open
source
process,
so
that
all
looks
good,
they're
feeling
more
confident
that
patch
there
were
two
tickets
15
for
69
and
15
for
70.
That
came
out
of
those
that
are
currently
under
review.
F
E
Awesome
thanks
Jordan
a
couple
other
areas
were
upgrading
diff
tests,
that's
also
listed
under
that
in
the
confluence
doc.
This
is
a
good
thing.
I've
liked
mechanizing
Cassandra
dip
to
the
test,
upgrading
a
cluster
from
3x
to
Oro
and
then
validating
correctness.
Both
mid
upgrade
and
post
upgrade
when
I
say
for
correctness.
I
mean
identity
between
the
two,
but
there
are
also
several
areas
where
work
might
not
necessarily
be
active
or
where
there's
not
necessarily
someone
who
signed
up
to
either
leader
take
on
some
of
that
work.
G
Happy
to
so
that
that
list
is
just
by
going
down
and
looking
through,
who
has
a
Shepherd
assigned
to
them
or
not,
and
there
are
a
few
very
important
pieces.
The
database
bill
that
I
think
are
worth
having
to
look
at
particularly
the
coordinators
replication
and
lead
repair,
obviously,
the
functionality
and
making
sure
that
metrics
are
still
operational
and
or
at
least,
if
they've
changed
having
their
their
new
meanings
or
their
interpretations
documented.
G
Three
piece
notes
as
far
as
tooling
Sam's
going
to
take
the
JDK
11
internal
to
Lee,
but
I,
don't
think
he
has
much
cause
to
run
external
tooling
as
part
of
his
day-to-day
work.
So
it
would
be
much
nicer
if
somebody
who
does
regularly
learn
things
like
meet
other
and
some
of
the
other
tools
to
do
that.
G
C
When
they
asked
support
for
being
you
speaking
about
Windows
I
pinged
on
ticket
about
this,
not
really
sure
what
our
position
is
is
a
project
on
it
with
WSL
out
the
windows
subsystem
for
Linux,
which
is
actually
quite
terribly
named,
you
can
essentially
run
Cassandra
on
Windows
in
bash
on
an
Ubuntu
distribution.
So
there
really
isn't
a
hell
of
a
lot
of
pressure
in
terms
of
for
a
dev
environment
perspective
us
having
a
Windows
support
and
NTFS
is
bonkers.
Handling
of
hard
junctions
of
stuff
makes
it
so
supporting
it's
a
giant
pain
in
the
ass.
C
E
B
C
Yeah,
all
of
the
everything
all
the
tooling
all
the
startup
scripting.
Everything
is
different
between
the
two
platforms.
From
a
UX
perspective.
They
should
be
identical,
but
you
know
the
the
operative
word
in
that
statement
is
should
and
that's
not
something
I've
personally
taken
a
look
at
for
two
years
three
years
and
that
was
kind
of
my
Sisyphean
task.
C
So
somebody
would
definitely
need
to
take
a
look
at
that
and
figure
out
how
its
behaving
and
wsl
to
dotted
the
one
where
they're
actually
virtualizing
on
the
hypervisor
in
Windows,
which
gives
a
much
much
better
file
system
performance
that
hasn't
actually
gotten
off
the
faster
ring
yeah.
So
it's
not
part
of
the
standard,
Windows
distributions
so
depending
on
the
timing
of
4'o,
hitting
if
our
concern
is
people
running
Windows
and
production
with
Cassandra
and
wanted
to
give
them
an
upgrade
path
before.
E
To
the
medic,
when
I
brain
sounds
like
we
don't
have
a
volunteer
among
members
of
this
call
to
Warren
production
level
windows.
Support
at
this
point,
though,
it
may
be
that
someone
steps
up
or
that
a
contributor
appears,
but
the
patch
that
can
be
reviewed
and
then
included
to
achieve
that
which
would
be
a
step
but
is
possibly
different
from
like
a
warranty.
C
Yeah,
we
do
have
precedent
in
the
past,
in
the
project
of
a
release
hitting
and
in
a
window
support
for
that
release
hitting
at
a
later
date
as
well.
So
if
that's
something
we
wanted
to
go
ahead
and
just
formally
say
this
is
gonna,
be
our
approach
to
4'o
and
see
if
we
can
count
this
computer
or
figure
out
whether
or
not
that
be
interested
go
from
there.
B
B
I'm
super
stoked
to
work
out
windows
stuff.
You
know
my
dream:
I
am
happy
to
start
like
Cassandra
users,
mailing
list
threat,
saying
like
calling
all
Windows
users
we're
looking
for
help,
testing
etc.
If
that
is
something,
people
think
would
be
helpful
and
to
start
the
deprecation
discussion
out
of
that.
If,
if
also
helpful,
I
think.
A
E
E
Think
more
than
just
knowing,
if
there
are
people
the
the
thing
that
we
need
most
is
a
contributor
who
is
able
to
provide
that
support
or
complete
that
testing
themselves.
I
worry
about
disenfranchisement.
If
we
were
to
take
a
poll
and
people
would
say:
oh
I
care
so
much
about
it,
matters
more
than
anything
and
then
for
that
to
just
go
into
a
black
hole
and
grateful.
So,
okay.
B
E
Popping
the
stack
to
John's
earlier
point:
there
are
several
areas
that
are
in
that
dock
that
currently
don't
have
someone
who's
signed
up
to
to
be
testing
or
validation
effort
in
those
areas
of
the
areas
that
we
listed
out
earlier
or
additional
ones.
That
folks
haven't
thought
of.
Is
there
anybody
on
this
call?
It
would
be
willing
to
pick
one
of
those
up
and
work
to
define
what
validation
looks
like.
H
H
This
is
Joey
from
Joey,
so
I'm
I
think
that
the
Nash
is
already
kind
of
leading
the
way
on
documentation.
I'd
be
happy
that
I,
like
kind
of
work
with
him
on
that
like
so
we
could.
We
could
kind
of
I
know
that
we've
worked
with
the
Google
summer
of
documentation,
project
and
a
bunch
of
patches
just
went
out
so
now,
each
step
so
I
kind
of
like
review
them
and
get
them
merged.
E
I
I
J
H
H
E
J
H
Talk
about
it,
you
know
we
can
undo
the
hacks.
We
did
before
the
alpha
releases
and
just
belt
against
the
alpha,
the
Alpha
artifacts
now
so
so
we
can
always
validate
that,
like
it's
buildable
and
we
can
and
we're
actually
running
some
trunk
clusters
right
now
so
yeah
we
can
like
upgrade
those
and
make
sure
that
everything
works
yes
and
hide
this
insolent.
J
L
Know
Mik
simply
bet
and
Alex
in
the
process
of
doing
some
testing
and
just
getting
Reaper
ready
for
4.0.
We
will
probably
make
a
new
major
release
at
some
point
near
the
photo
release,
so
it's
solely
compatible
and
that's
sort
of
where
things
are
at
the
moment.
So
it's
just
still
ongoing
testing
and
with
the
backend
and
updates
to
the
UI
as
well.
L
E
If
you
can,
and
if
there
are
issues
that
you
identify
either
drop
a
note
on
the
Deaf
list
or
a
file
at
your
ticket
or
drop
something
in
slack
I'm
mentioning
that
primarily
because
if
there's
an
issue,
that's
impacting
non
repair
scheduler,
it's
probably
impacting
a
whole
bunch
of
people.
So
if
there's
a
small
change
that
we
can
make
as
contributors
to
the
project,
that
may
be
easier
for
everybody
that
might
make
more
sense
than
updating
every
tool
separately.
Yeah.
E
E
Cool
one
item
that
I'd
added
that
I
don't
have
a
particular
update
on
myself-
is
the
status
of
the
300
and
311
branches.
Periodically
somebody
raises
the
question:
should
we
be
cutting
a
release
and
usually
by
the
time,
somebody's
remember
to
ask
that
question?
The
answer
is
pretty
clear:
yes,
but
was
curious.
If
anybody
wanted
to
speak
to
that
directly.
C
Our
position
is
on
that,
and
we
probably
see
that
action
here
so
maybe
worth
having
a
discussion
on
the
dev
list
about
kind
of
our
position
to
do
with
it
and
in
terms
of
like
three
actively
dealing
with
where
we
are
in
the
moment
for
sure
which
to
deal
with
that.
But
you
know
eight
weeks
from
now
twelve
weeks
from
now
24
weeks
from
now
we're
gonna
be
in
the
same
boat
again.
History
would
indicate
that
probably
yeah.
D
Okay,
yes,
so
we
just
got
the
release.
Roomed
Apache
con
folks,
we're
gonna,
be
that
they're.
Looking
for
a
call
for
presentation,
it's
open
until
May
and
I
expected
to
see
like
one
or
two
more
housekeeping
items
from
them
in
terms
of
like
room
space
and
everything
before
they
pulled
the
trigger
on
that.
D
But
I
don't
have
that
much
more
information
than
what
we've
gotten
folks
on
a
PMC
on
the
private
list,
yet
I'm
going
to
still
let
and
send
it
around
in
a
day
or
two
once
I
know
a
little
bit
more
about
specifics
and
for
everyone
else
and
there's
a
lot
of
folks
trying
on
the
column.
Fortunately.
But
anyone
who
wants
to
get
involved
with
us,
certainly
on
the
PMC
to
review
conversations
I'm
just
going
to
add
everybody
this
year
and
let
him
jump
in
and
do
grading
fun
stuff.
It
seemed
it's
like.
D
We
got
some
miscommunication
on
that
last
year
with
the
Dinesh
and
myself
driving
that
a
couple
of
the
folks
who
jumped
in
to
reviews
so
we'll
open
that
up,
I,
don't
know
from
a
noise
factor
of
maybe
we
can
take
a
couple
other
people
for
review
stuff
independently,
but
that
generally
provides
more
of
like
operational
headache.
Just
that
you
know
verified
we
sue
and
what's
what
type
of
thing
so
it
might
just
be.
We
restricted
it
to
people
with
some
commit
rights
already
for
paper
reviews.
D
We
could
talk
about
that
to
bring
that
to
the
dev
list
and
herbs
and
users
will
shortly
look
and
a
little
bit
more
a
little
more
information,
but
we're
moving
forward
with
that.
That's
basically
what
I
wanted
to
say
again,
it's
this
kind
of
there,
this
not
anywhere
near
as
well
managed
to
do
think
it
is
and
for
conferences,
so
I'm
trying
to
just
provide
as
much
information
I
get
from
them.
It's
all
volunteer
effort,
and
it's
one
of
the
things
we're
just
kind
of
like
yeah,
get
involved
and
pay
attention.
D
M
D
Doing
that
again,
so
anybody
on
this
call
who
wants
to
get
ready
to
submit
a
talk.
You
know
we'd
like
to
see
it
would
be
great,
there's
more
submissions
we
can
get
the
better
and
for
folks
who
don't
know
we
had
the
the
most
users
and
people
specificity
specifically
attending
forward
the
Kisan
detract
in
any
other
track
at
batchi
last
year,.
E
Thanks
for
mentioning
the
more
interactive
piece
as
well,
I,
remember
from
talking
to
several
folks
that
some
felt
that
one
of
the
most
valuable
parts
of
the
summit
was
actually
toward
the
end,
where
many
of
us
were
just
hanging
out
in
an
open
space
on
the
carpet
in
a
circle
talking
and
doing
some
planning
around
who
could
work
on
what
toured
for
Oh?
Do
you
know
if
there
might
be
more
breakout
space
or
rooms
available
for
discussion
like
that,
rather
than
strictly
presentation?
D
So
I,
you
know
I
care,
but
I,
don't
care,
try
to
thing
and
so
I'll
try
to
push
on
that
to
get
as
much
of
like
that
breakout
space,
that's
what
we
used
to
do
and
a
lot
of
stuff
and
provide
room
as
much
as
possible,
but
no
guarantees
because
we
do
have
to
fit
within
the
rigid
confines
what
they
do
know.
Apparently
they're
gonna
relax
that
it
this
year
so.
A
A
Add
if
we
did
this
years
ago,
Dave
stack
sponsored
a
space
near
Apache
con
that,
if
that's
an
option
and
I
would
be
happy
to
talk
to
the
Apache
con
folks
about
that,
just
so
that
they
don't
have
to
go
crazy,
but
I,
agree,
I!
Think
it's
that
if
you
know
anybody
wasn't
there,
it
was
pretty
impressive.
I
mean
it
was
a
Casandra
conference
and
Friends.
D
Cool
yeah
again
as
soon
as
I
find
out
anything
I'll.
Let
everyone
know
it's
a
volunteer
process.
The
matter
you
know
make
a
strike,
filter,
holding
a
mail
and
watch
his
Lackey
and
all
type
of
thing
and
I
said
anyone
who
wants
to
subscribe
to
like
a
the
event
planner.
So
oh
I
can
do
that
too.
If
you
doesn't
I
think
you
can
just
join
without
attaching
ID,
but
you
may
need
attention
ID,
which
I,
but
this
is
you
can
join
this.
It's
not
kill.
Anyone
can
join,
get
the
planner
slap
channel.
E
That
point
I'm
planning
in
front,
like
several
of
us,
were
kind
of
running
around
realizing
very
basic
things.
At
the
last
minute
like
oh,
we
should
have
adapters
at
the
podium.
There
should
be
a
power
plug
bear,
whereas
people
who
have
formal
event
planning
expertise,
have
you
know
very
elaborate,
checklists
that
make
sure
things
go
super
spoon
some
of
that
was
learning
on
the
flight.
How.
B
D
Yeah
I'll
do
what
I
can
to
get
everything
we're
gonna,
have
it
rooms
ahead
of
time.
You
know
I'll,
create
a
document
and
just
have
some
checks
on
the
wiki
that
we
can
get
for
this
and
just
make
sure
we
have
everything
going
into
this
and
just
like
assume
no
like
material
support
from
BASF
other
than
like
here's.
The
space
with
a
mic
type
of
thing
to.
E
Clarify
that
was
a
really
great
surprise
and
I.
Don't
think
that
the
conference
would
have
happened
last
year
at
all
hadn't
not
been
very
SS
contribution
there
and
the
generous
offer
a
space
to
so
I'm
so
glad
that
worked
out.
Maybe
together
as
a
group,
we
can
start
the
doc
that
Nate
mentioned
and
then
crowdsource
improvements
that
we
make
this
year
and
see
how
we
can
make
it
more
successful
event
too.
E
Cool,
so
we
actually
just
raced
through
every
item
on
our
agenda
I'm,
not
going
to
pretend
that
there
are
more
things
that
are
there,
but
they're.
Also,
a
lot
of
people
who
haven't
spoken
and
shared.
Are
there
other
items
that
folks
had
interest
in
covering
or
questions
that
people
have
that
we
should
talk
about.
G
So
I
did
have
a
quick
just
for
Alaska
for
everyone.
That's
working
on
developing
and
testing
it
and
I
proposed,
but
now's
a
really
good
time
to
try
and
work
on
any
user-facing
features
that
will
affect
things
like
configuration
or
metrics
or
logging,
or
anything
that
anyone
who
has
a
dependency
on
us
needs
finalized.
So
they
can.
They
can
do
their
work.
G
It's
nice
to
polish
things
and
speed
things
up
and
optimize
memory
usage
those
kinds
of
things,
but
it
would
be
really
really
really
nice
if
we
could
close
our
reviews
that
we
have
in
progress
and
finish
up
anything
that
touches
conflicts,
metrics
protocol,
any
other
kind
of
stuff.
That's
all
absolutely.
N
Another
point
which
we
were
discussing
on
the
chat
was:
should
we
move
this
meeting
to
11:00
a.m.
Pacific,
which
will
be
two
hours
early,
then
what
we
are
starting
now?
The
advantage
of
that
is,
it
will
catch
more.
It
will
be
more
convenient
for
people
in
Europe
and
also
for
people
in
New
Zealand.
It
will
be
7:00
a.m.
so.
Those
have
a
name
sounds
earlier
right.
So
that's
why
either
we
move
it
back
by
one
hour
or
two
hours.
If
you
move
it
back
by
one
hour,
it
will
be
lunchtime,
but
it's
fun.
N
D
Let's,
let's
do
a
thread
on
it,
because
it's
one
of
those
things
like
this
somebody's
always
gonna
get
the
short
end
of
the
stick
and
we're
just
gonna
have
to
flip-flop,
like
the
best
practice
like
between
for
people
like
folks
on
the
u.s.
west
coast
will
be.
You
know
the
most
the
least
have
stressed
on
this,
but
like
we'll
just
have
to
go
back
and
forth
between
the
EU
and
back.
That's
the
only
way
to
do
this,
because.
A
D
A
Up
this
is
what
I
was
planning
on
doing
and
I'm
glad.
We
had
there's
a
good
discussion
going
in
the
chat
in,
but
that's
getting
lost
as
soon
as
I
hit
close,
but
what
I
think
would
probably
be
a
good
idea
is
some
sort
of
easy
poll
or
something
I
want
it.
I'll
do
a
summary
on
the
dev
list
of
you
know
what
we
talked
about.
I'll
take
that
and
then
just
to
follow
up
with
okay
time
zones.
Let's
talk
about
this
and
come
up
with
some
sort
of
basic
rotation.
A
I
think
that's
that
just
give
people
the
ability
to
plan
ahead.
So
if
you
know
it's
gonna
be
out
of
your
timezone,
you
don't
even
plan
ahead,
but
I
think
that
what
I've
seen
from
other
open-source
projects
that
do
this
sort
of
thing
is
you
try
to
get
as
planned
out
as
possible
just
so
that
everyone
can
work
around
schedules.
This
is
a
this
is
a
massive
coordination
issue.
A
You
know
everybody
has
different
different
jobs,
different
time
zones,
everything
so
the
more
we
can
put
out
ahead
of
you
know
things
and
try
to
be
as
common
dating
as
possible.
I
think
you'd,
the
more
participation,
that's
really
the
key.
How
do
we
get
more
people
to
participate
and
yeah,
so
I
just
look
out
for
that
email,
but
I
think
there's
the
the
conversation
here
he's
been
pretty
good.
A
Well,
before
we
get
further
down
there,
I
just
noticed
in
chat
as
well
and
I
want
to
flesh
this
out,
because
I'm
monitoring
the
chat,
Jeff
and
I'm,
assuming
this
is
Jeff
sure
so
Bob
brought
up
a
really
interesting
point.
It
says
anyone
want
to
touch
on
timing
to
unlock
trunk.
These
throws
a
grenade
is
tossed
there.
You
go
like
that.
Something
should
be
discussed
so.
N
What
I
would
say
on
that
front
is
I
think
like
when
we
are
close
to
beta
right.
That
is
the
time
we
should
be
thinking
about
unlocking
trunk,
and
we
can
always
have
a
discussion
on
the
dev
list
on
on
it,
because
I
think
like
this
might
not
be
the
best
place
to
discuss
it.
Considering
there
are
so
many
people
on
this
call,
so
we
should
definitely
start
a
thread
on
when
that.
When
is
the
right
time
to
do
it,
but
it
cannot
be
in
months
it
has
to
be
deliverable.
N
C
I
think
it
throw
the
mailing
lists
would
be
great
and
not
too
severe
anything
but
like
even
at
in
GCC.
Not
everybody
was
there,
and
this
is
the
whole
Apache
way
of.
If
it
doesn't
happen
on
the
mailing
list,
it
doesn't
happen.
That's
the
one
way
we
know
we
can
get
everybody
engaged
and
discussing
what's
going
on
with
things.
B
I
N
We
want
to
prioritize
work
done
to
stabilize
for
Otto
and
having
two
branches
makes
that
you
have
to
now
merge
onto
so
one
of
the
example
is,
let's
say:
if
we
branch
out
today,
then
oh
and
then
someone
merges
a
big
PR
on
that.
Then
any
work
which
is
happening
on
for
oh
now
have
to
get
rebased
or
two
branches,
which
means
we
are
in
a
way
hindering
the
amount
of
work
happening
on
stability.
That's
what
I
would
say
show
me
I'd
know
so
odd.
N
I
agree
with
that
point,
and
that's
probably
the
point
that
off
that
I'd
offer
as
well
it
probably
if
anyone
is
if
anyone
is
getting
restricted
right
now
not
to
work
on
it.
Show
me
the
branch
right.
You
can
always
show
us
the
branch
and
give
examples.
That's
the
best
way
of
showing
that
the
branching
is
not
working
out
is
about
telling
me
okay,
I
have
a
branch,
I
cannot
merge
and
it
is
5,000
lines
of
code
or
whatever,
and
that's
why
I
can't
basically
do
it.
E
Sounds
like
it'd
be
good
to
discuss
on
the
dead
list
and
it's
also
not
a
topic
that
is
settled.
One
time.
I
think
it's
fine
for
us
to
continue
revisiting
that
and
to
continue
assessing
completion
against
the
criteria
that
people
discuss
together.
So
it's
a
good
one
to
bring
up
and
a
good
one
for
us
to
talk
about
in
the
list.
A
Okay,
are
we
if
we
bottom
doubt
this
topic
sounds
like
we
have
the
really.
The
final
topic
which
I'm
hoping
we
can
put
a
nice
bookmark
on
is:
is
there
anything
that
we
need
to
talk
about
in
this
format?
I
mean
this
was
an
experiment.
Of
course
you
know
and
I
I
know
we're
gonna
get
better
at
these,
but
I
personally
am
I
love
it
because
we
are
able
to
talk,
and
we
were
able
to.
You
know,
get
some
get
some
things
out.
There
talked
about
a
bunch
of
stuff
on
the
dev
list.
B
I
think
I
think
for
our
specific
to
the
goal
of
getting
Feraud
done,
having
a
very
focused
that'ss
conversation
on
for
oh,
maybe
a
little
bit
more
prepared
for
than
today
and
I'm
happy
to
volunteer
to
help.
Whoever
with
that
would
be
beneficial
because,
like
again,
really
the
best
thing
to
getting
forward
on
the
song,
because
that
is
like
working
on
those
tickets
and
prioritizing
those
things
so
having
that
be
visible,
I
think
would
be
helpful.
A
Okay,
no,
that's
I,
think
that
one
of
the
things
I
mentioned
early
in
the
call-
and
this
is
just
me
trying
to
help-
put
some
order
into
this
chaos,
which
is
easy
to
do
right,
is
if
you're
gonna
put
it.
If
you
put
an
agenda
item
up
who
who
wants
to
who
wants
to
own
that
agenda
item,
so
you
can
drive
it
yeah,
I
think
awesome,
but
I'm
not
trying
to
call
y'all
Jordan.
B
N
B
L
A
E
That
feels
intuitive
to
me
too,
and
toward
the
energy
of
four
oh
I,
think
the
most
important
thing
isn't
so
much
talking
about
it
as
drawing
additional
contributors
into
the
project
to
work
on
those
items.
The
set
of
contributors
that
are
currently
working
toward
400
items
in
JIRA
and
on
that
list
are
pretty
small
and
aren't
terribly
diverse
in
terms
of
their
affiliation,
and
if
there
are
more
people
who
can
join
and
contribute
resources,
I
think
that's
one
of
the
most
important
things
that
could
happen
to
our
shipping
for
a
faster.
A
Okay,
I
will
again
just
as
to
get
maximum
input.
I'm
hearing
once
month
is
great,
but
I'll
pose
this
as
a
question
on
the
dead
list
as
well,
just
to
make
sure
we
have
good
coverage.
I'm
I,
like
the
reasoning
you
know,
this
is
good
to
have
reasons
for
it.
So
I'll
take
those
two
items:
the
time
zone,
trying
to
do
that
and
if
we're
going,
if
we
say
yeah
once
a
month,
then
I
will
chart
out
the
next
six
months
worth
of
times
where
we'll
meet
and
I'm
not
sure.
A
If
there's
a
calendar
out
there
that
we
can
use.
Maybe
that's
another
item.
I
need
to
figure
out
this
confluence
have
a
calendar
with
iCal.
You
can
subscribe
to
that's
probably
something
to
figure
out,
but
anyway,
if
we
could
chart
out
at
least
having
it
in
that
document.
Here's
the
next
six
meetings
and
calendar
appropriately,
but
at
least
we.
E
D
O
Am
I
at
the
end
I'm
kidding,
please
Patrick
I
talked
about
I
brought
up
tickets
about
this,
but
I
didn't
know
if
we're
finalizing
things
44.0,
if
it's
too
late
to
talk
about
this,
but
sometimes
I,
think
people
get
the
wrong
impression
about
certain
things
like
just
just
in
terms
of
like
defaults
for
a
variety
of
different
settings.
Is
it
okay
to
revisit
that
for
for
dotto
at
this
stage
in
the
game?
I'm,
just
wondering
and
I
can
start
a
deathless
thread
about
this,
but
I
mean
I
had
mentioned
specifically
compaction.
O
Throughput
is
kind
of
one
of
those
like,
but
I
think
token
ranges
is
another
good
candidate
just
because
people
have
been
saying.
Oh
yeah,
this
is
one
of
the
first
things
you
change
is
number
of
token
ranges
I'm,
trying
to
make
it
more
accessible
for
people
on
the
first
user
experience
and
didn't
know
if
Ford
otto
was
if
it
was
too
late
for
that
to
say
to
say,
let's
make
this
more
approachable
in
the
sense
of.
O
E
Absolutely
that
sounds
like
a
fine
thing
to
start
a
thread
about
I.
Think
the
standard
that
I've,
seen
or
heard
a
bunch
of
people
applying
for
whether
or
not
a
change
is
a
good
candidate
is
whether
including
it
either
violates
the
spirit
of
not
introducing
new
features
or
invalidates
existing
work.
That's
been
done
toward
testing
and
validation.
I,
don't
get
the
sense
that
some
of
the
property
changes
that
you
mentioned
would
risk
that
type
of
invalidation.
It
sounds
like
a
good
thing
to
bring
up.
Okay.
N
Out
of
the
box,
it's
cool
thanks
and
when
we
bring
it
up
on
the
dev
list,
whatever
we
decide,
we
should
move
it
actually
in
the
life
cycle
released
life
cycle
because
we
should
write
it
in
early.
I
was
just
watching
that
talk.
We
don't
have
anything
to
do
the
defaults,
I
think
we
should
face
it
and
like
when.
Is
it
too
early
or
too
late
to
change
the
defaults?
Like?
Can
we
change
the
faults
in
alpha
right?
N
M
O
And
that
would
be
another
thing
that
we
could
bring
up
to
is
just
to
say:
let's
make
it
because
of
this
disconnect,
say:
okay!
Well,
let's
review
specific
settings
and
if
we
override
those
for
testing,
then
that
might
be
a
good
candidate
as
well
to
say
you
know,
since
we're
already
testing
given
using
these
settings,
it
may
make
sense
to
say:
let's
go
ahead
and
migrate
to
that
for
the
default
so
that
people
aren't
caught
off
guard
when
they
put
it
in
put
alive,
not
that
people
shouldn't
test
themselves.
L
Yeah
I
mean
in
some
cases,
if
we're
testing
against
different
values
to
the
defaults.
We're
not
really
testing
the
release
because
we're
releasing
something
that
has
a
different
set
of
values
and
that
could
potentially
change
the
behavior.
So
that's
a
very
good
reason
to
actually
move
the
defaults
to
what
we're
testing
to.
A
All
right,
I
think
that
that
ends
it.
For
now
this
went
really
smooth
and
I'm
a
little
nervous
about
that.
We
went
to
well
waiting
for
the
where's.
The
explosion,
zoom
seems
to
work
I
also
I,
think
I'll
be
asking
folks
to
is
how
houses
him
working,
and
it
does
seem
that
this
is
one
one
that
works
well
for
most
people,
it
has
the
most
options
and
it
has
capacity
so
I
will
right
after
the
meeting
I'll
render
out
the
video
and
try
to
get
that
poster
right
away.
A
I
know
Joey's
been
taking
notes,
so
those
will
get
posted.
The
video
and
the
notes
will
be
posted
in
confluence.
I
will
send
an
email
out,
hopefully
by
tomorrow,
just
summarizing
hey.
This
happened,
here's
where
all
the
notes
are
and
I'll
put
in
a
couple
of
those
like
quick,
pulls
like
time
zone
and
pacing.
So
we
you
know
we
can
get
some
consensus
on
the
mailing
list.
That's
what
I
had
on
my
list.