►
From YouTube: Apache Cassandra Contributor Meeting 2020-02-18
Description
ApacheCon is coming in September and we need good Cassandra talks. CFP is open and ready. Progress on issues has been moving faster with an Alpha3 release. There was a proposal to outline what’s needed to move to Beta. Look to the mailing list for that. Discussion about inviting more contributors to participate in the sidecar project. Docs project is moving along nicely with some big contributions being committed.
A
A
B
You
can
go
TV
in
here,
so
yes,
I
see
a
thumbs
up
good
stuff,
alright.
So
this
is
just
a
quick
recap
of
what
I
sent
down
to
the
mailing
list.
Josh
Mackenzie,
Jordan
I've,
been
trying
to
take
turns
to
give
a
little
more
concise
summary
of
activity
in
JIRA
and
just
try
and
get
a
pulse
on
how
product
project
activities
going.
B
B
So
the
great
news
is
that
things
seem
to
be
moving
and
we
are
closing
one
tickets,
the
link
which
is
nice
at
this
point.
A
lot
of
the
tickets
that
we
have
opened
against
the
400
alpha
are
testing
tickets.
Now
I
just
did
a
quick,
quick
tally
beforehand
of
the
testing
tickets,
I
would
say,
15
or
so
flaky
test
tickets
that
we
have
that
they
would.
B
Cap
was
opened
up,
which
we
great
to
resolve
as
far
as
getting
the
CI
infrastructure
getting
green
as
soon
as
possible,
so
that
we
can
start
finding
real
real
problems
with
the
CI
rather
than
having
to
wade
through
all
the
noise
that
you
get
if
you've
got
flaky
tests,
so
I
cover,
if
I
said,
but
there
are
only
two
new
tickets
opened
this
week.
Book
amount
against
the
4.0.
B
Now
I
didn't
go
through
and
do
a
triage
of
all
you
tickets
open
to
just
check
whether
that's
disciplined
on
tagging,
new
tickets
or
whether
it's
it's
truly
that
we
own
a
continuance.
But
the
good
news
is
that
we
closed
11
of
them,
including
one
of
the
newly
opened
one,
so
we're
identifying
issues
and
closing
quickly
and
thirty
nine
tickets
received
updates
in
the
last
week.
So
that's
obviously
people
touching
things
and
commenting
categorizing,
which
is
good.
B
Some
notable
things
that
landed
the
Python
3
support
for
sequel
SH
has
been
committed.
So
thanks
to
everybody
who
fought
a
long,
hard
fight
to
get
that
to
happen,
I've
been
at
for
a
long
time.
There
was
some
activity
on
the
Windows
port
which,
given
the
questions
in
the
last
community
meeting
on
the
mailing
list
about
whether
Windows
is
actually
in
use,
there
are
at
least
people
alive
there
very
excitingly.
The
documentation
was
moving
as
well,
so
that
that's
a
huge
piece
for
people
being
ready
to
adopt
full
row.
B
The
significant
changes
they're
in-
and
it's
really
nice
to
have
some
of
those
pieces
in
place
ahead
of
the
release
candidate,
so
that
you
can
point
back
to
people
put
people
to
that.
So
they
can
actually
have
more
chance
of
success.
Deploying
things
and,
like
I,
said
lots
of
activity
on
the
flaky
test.
So
I
would
encourage
people
if
you
have
spare
spare
moment
and
your
masochist
try
and
fix
a
flaky
test,
because
everyone
will
thank
you
for
it.
B
So
I
guess
that
leads
me
on
to
the
final
thing,
which
is
that
it
was
a
very
old
ticket
on
a
patch
for
which
was
28:58,
which
adds
clients,
API
support
for
passing
down
timeout,
and
there
were
some
questions
on
the
mailing
list
as
to
whether
or
not
we
should
be
landing
stuff
like
that
now
and
they're
just
heavy
thinking
about
the
actual
release
process
itself.
When
people
are
at
pentacon.
B
Last
year
there
was
no
I
wouldn't
say
there
was
complete
agreement
on
what
it
means
to
go
through
the
next
few
phases
with
different
opinions,
but
we're
currently
in
what
we're
calling
alpha
we'd
like
to
get
to
a
beta
and
I
personally
think
it
would
be
good
to
get
that
done
in
the
next
couple
of
months,
good
country
office
now
and
there's
nothing.
That
seems
truly
egregious.
That
will
be
stopping
that
from
happening.
But
obviously
that's
just
one
person's
opinion
we're
an
Apache
project.
B
So
we
have
to
find
some
way
of
getting
consensus
on
or
we
get
to
call
things
beta
and
when
we
get
to
call
these
candidates,
I
don't
really
have
a
proposal
at
the
moment.
But
if
this
were
a
commercial
software
project
being
aggressively
project
managed
as
we
go
through
these
phases,
you
would
start
aggressively
cutting
anything
that
was
non-essential
and
you
would
be
trying
to
hit
early
state
and
obviously
we
have
different
drivers
than
the
commercial
enterprises
and
will.
B
C
I
think
one
thing
that
can
help
us.
There
is
the
work
that
several
folks
have
done
toward
defining
the
release
cycle
document
that
we
published
on
confluence
a
few
months
ago.
I
think
that
can
provide
a
useful
template
for
some
of
the
discussions
on
scope,
along
with
some
of
the
previous
discussions
about
the
focus
on
quality
and
breeze.
So
that
might
be
a
good
starting
point
for
work
toward
defining
those.
E
E
Able
not
so
much
not
so
much
a
concern,
I
think
an
area
that
would
be
interesting
for
me
from
like
an
education
standpoint
so
that
we
all
don't
have
to
go
read
the
code
is
an
area
of
a
bunch
of
work
and
it's
well
came
up
on
the
mailing
list.
Sorry
one
second
I'm
gonna
have
my
dog
stop
moving
stuff
in
a
bit?
E
Line
list
about,
like
certain
changes
that
affect
the
protocol,
I'm,
not
sure
it's
clear
to
like
all
of
us
again
without,
like
saying,
like
all
of
us,
go
read
the
tone
which
is
fine,
but
if
someone
can
sort
of
describe
very
clearly
why
certain
changes
need
to
be
made
like
in
the
major
release
to
the
protocol,
because
it's
that's
often
a
reason.
There's
like
oh
we're,
gonna
have
to
change
the
protocol
specs.
So
we
have
to
change
this
for
four,
oh
and
so
I'd
love.
E
E
C
It
also
kind
of
raises
one
of
the
discussions.
They
came
up
in
SF
slack
yesterday,
along
the
lines
of
a
potential
rush
to
get
a
raft
of
changes
into
the
build
because
the
trains
about
to
leave
the
station
and
the
next
one
might
be
some
time
out
with
an
alternate
view
being
that
it's
useful
for
us
to
have
a
good
conversation
on
scope.
Decide
what's
in
and
what's
out
and
be
able
to
deliver
more
frequent
releases
to
incorporate
those
changes
later.
A
H
G
A
I
I
pop
something
up
here,
and
this
is
just
an
Vinay
I'm.
Sorry,
you
and
I
talked
about
this
briefly,
but
I
thought
this
is
open.
A
A
Well
and
I,
you
know
if
we're
looking
for
more
contributions
to
the
Apache
Cassandra
project.
I
think
this
is
a
great
opportunity
to
bring
some
new
people
into
the
fold
and
I
just
saw
this
as
an
awesome
opportunity,
but
it
was
just
really
interesting,
as
I
saw
it
and
I
know.
This
has
been
something
that's
going
in
it's
it's
a
sub
project
right
now
and
almost
like
a
special
interest
group,
but
I
just
thought
I
would
open.
A
Yes
and
it's
it's
because
I
think
everyone
has
an
itch
to
scratch
right,
but
as
you
noted
when
you,
when
you
look
around
I
I'm
seeing
this
is
like
how
like
the
early
thrift
days
were
with
drivers,
there's
just
everyone
has
one
sorry
Danny
Laconia,
but
there
was
just
a
lot
of
them
because
they
were
different
opinions
on
it
and
then
there
started
colas.
So
we
may
be
in
that
mode
right
now,
but
I
don't
know
how
that
how
well
that's
received
I
mean.
C
D
A
F
Patrick,
this
is
the
nature,
so
I
just
wanted
to
add
that
there
are
a
bunch
of
ideas
that
we
would
like
to
implement
and
we
would
definitely
like
more
contributors
to
help
build
the
sidecar.
The
that
the
thing
is
that,
since
the
project
is
currently
focused
on
testing
and
getting
four
out,
it's
less
of
a
focus
for
folks
in
the
community.
A
C
F
So,
while
John
fixes
audio
yeah,
so
we've
been,
we've
been
working
with
Deepak
who's,
the
debt
writer
as
part
of
the
google
Summer
of
Code
and
I
believe
Joey
and
John
merged.
A
bulk
of
those
Gira's.
There
are
quite
a
few
still
to
go.
I
did
send
out
an
email
with
a
few
of
the
links
with
before
and
after
so
I.
Think,
a
bunch
of
our
tohru's
from
the
documentation
have
been
eliminated.
There's
still
a
lot
that
needs
to
be
updated,
but
there
are
four
there
are.
There
is
documentation
about
specific
for
our
features.
C
Thanks
Denise
yeah
and
as
part
of
that
I
wanted
to
echo
the
public
thanks
to
Deepak
Bora
as
part
of
his
work
on
google
Summer
of
Docs,
to
produce
this
incredible
body
of
documentation
to
Jeff
for
donating
that
chapter
as
well.
These
are
huge
contributions
to
the
project
and
address
giant
unmet
need
I,
particularly
appreciated
the.
Before
and
after
links
that
were
sent
around
that
go
from
having
to
do
on
the
site
to
a
huge
body
of
documentation.
That's
awesome.
C
K
J
J
K
J
I
A
All
right
is
there
anything
else.
Anyone
there
was
a
bonus
section
thanks
sky
and
it
is
really
cool
to
see
that
how
the
docs
are
are
really
growing
out
there
it's
summer
code
and
then
I
really
I
really
appreciate
what
a
Riley
just
stepped
right
up
to
do
that.
That's
pretty
amazing,
but
I
can
tell
you,
through
my
conversations
with
Riley,
they're,
being
buried,
they're,
being
super
cool
with
the
open
source
projects
right
now
and
I.
Think
they
see
this
as
a
just
an
easy
one
for
them.
So
that's,
hopefully
more
to
come
all
right.