Re: [DISCUSS] Seeking Guidance on Next Task and Areas to Contribute

[Caleb Rackliffe]

   1. CASSANDRA-19224
    has some open
   issues for someone interested in working on SAI (storage-attached indexes).
   Feel free to drop any questions in the *#cassandra-sai* channel in ASF
   Slack.


On Mon, Jul 7, 2025 at 8:19 PM pranav shenoy 
wrote:

> Thanks Jaydeep & Josh for your inputs.
>
> Let me go through the *repair-scheduling-cep37 and would be happy to get
> on a call to know more. *
>
> *Will go through the "Starter Tickets" as well but was looking at
> something beyond starter bugs. *
>
>
> *Thanks and Regards*
> *Pranav*
>
>
> On Mon, Jul 7, 2025 at 10:59 AM Josh McKenzie 
> wrote:
>
>> Pranav,
>>
>> Here's a link to a list of tickets that are unassigned and have been
>> designated good "Starter Tickets":
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2162&quickFilter=2160
>>
>> On Sun, Jul 6, 2025, at 7:44 PM, Jaydeep Chovatia wrote:
>>
>>
>> Hey Pranav,
>>
>> Recently, the repair framework has been automated as part of CEP-37
>> .
>> But many improvements need to be made to cover other aspects of Apache
>> Cassandra cluster lifecycle, such as automatically stopping the scheduler
>> if a new DC is added, triggering the framework if the keyspace's
>> replication factor changes, etc. Here are some of the unassigned tickets
>> under epic (CASSANDRA-19918
>> )
>>
>>- CASSANDRA-20414
>>
>>- CASSANDRA-20582
>>
>>
>> There is also a dedicated ASF Slack channel (
>> *#cassandra-repair-scheduling-cep37*) where we discuss some of the
>> tasks. I'd be happy to hop on a call to update you on our current status
>> and outline our plans for the next few months. Let me know!
>>
>> Jaydeep
>>
>> On Sat, Jul 5, 2025 at 11:27 PM pranav shenoy 
>> wrote:
>>
>> Hi all,
>>
>>
>> I've recently been contributing to Cassandra by working on some bugs in
>> Accord, and I’m now looking to pick up my next tasks.
>>
>>
>> While I’ve been browsing through JIRA, I find it a bit challenging to
>> identify suitable tasks just based on the brief descriptions, as I’m still
>> getting up to speed with the project. I was wondering if anyone could
>> kindly point me toward tasks that I can pick - possibly beyond bug fixes.
>>
>>
>> Also, I’d love to get a better understanding of the ongoing feature work
>> or broader efforts that contributors are currently focusing on, in case
>> there’s an opportunity to get involved.
>>
>>
>> Thanks in advance for your guidance!
>>
>>
>> Best regards,
>>
>> Pranav Shenoy
>>
>>
>>

Re: [VOTE] Release Apache Cassandra GoCQL Driver 2.0.0-rc1 (2nd attempt)

[Štefan Miklošovič]

+1

On Thu, Jul 3, 2025 at 6:07 PM João Reis  wrote:

> Hey folks,
>
> I’m proposing the Apache Cassandra GoCQL Driver 2.0.0-rc1 for release (2nd
> attempt).
>
> sha1: 722707e3df954a43c5aa708de8569fff38f1d5a7
> git:
> https://github.com/apache/cassandra-gocql-driver/tree/v2.0.0-rc1-tentative
>
> The Source release is available here (r77919):
>
> https://dist.apache.org/repos/dist/dev/cassandra/cassandra-gocql-driver/2.0.0-rc1/
>
> This is the second vote being called for this release after the previous
> vote was stopped due to a critical bug [1] that was found (it's fixed now).
>
> The vote will be open for 72 hours (longer if needed). Everyone who has
> tested the build is invited to vote. Votes by PMC members are considered
> binding. A vote passes if there are at least three binding +1s and no -1's.
>
> Thanks,
> João
>
> [1] https://issues.apache.org/jira/browse/CASSGO-82
>
>

Re: [DISCUSS] Seeking Guidance on Next Task and Areas to Contribute

[Josh McKenzie]

Pranav,

Here's a link to a list of tickets that are unassigned and have been designated 
good "Starter Tickets": 
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2162&quickFilter=2160

On Sun, Jul 6, 2025, at 7:44 PM, Jaydeep Chovatia wrote:
> 
> Hey Pranav,
> 
> Recently, the repair framework has been automated as part of CEP-37 
> .
>  But many improvements need to be made to cover other aspects of Apache 
> Cassandra cluster lifecycle, such as automatically stopping the scheduler if 
> a new DC is added, triggering the framework if the keyspace's replication 
> factor changes, etc. Here are some of the unassigned tickets under epic 
> (CASSANDRA-19918 )
>  • CASSANDRA-20414 
>  • CASSANDRA-20582 
> There is also a dedicated ASF Slack channel 
> (*#cassandra-repair-scheduling-cep37*) where we discuss some of the tasks. 
> I'd be happy to hop on a call to update you on our current status and outline 
> our plans for the next few months. Let me know!
> 
> Jaydeep
> 
> On Sat, Jul 5, 2025 at 11:27 PM pranav shenoy  
> wrote:
>> Hi all,
>> 
>> 
>> 
>> I've recently been contributing to Cassandra by working on some bugs in 
>> Accord, and I’m now looking to pick up my next tasks.
>> 
>> 
>> 
>> While I’ve been browsing through JIRA, I find it a bit challenging to 
>> identify suitable tasks just based on the brief descriptions, as I’m still 
>> getting up to speed with the project. I was wondering if anyone could kindly 
>> point me toward tasks that I can pick - possibly beyond bug fixes.
>> 
>> 
>> 
>> Also, I’d love to get a better understanding of the ongoing feature work or 
>> broader efforts that contributors are currently focusing on, in case there’s 
>> an opportunity to get involved.
>> 
>> 
>> 
>> Thanks in advance for your guidance!
>> 
>> 
>> 
>> Best regards,
>> 
>> Pranav Shenoy
>> 

Re: [DISCUSS] Seeking Guidance on Next Task and Areas to Contribute

[pranav shenoy]

Thanks Jaydeep & Josh for your inputs.

Let me go through the *repair-scheduling-cep37 and would be happy to get on
a call to know more. *

*Will go through the "Starter Tickets" as well but was looking at something
beyond starter bugs. *


*Thanks and Regards*
*Pranav*


On Mon, Jul 7, 2025 at 10:59 AM Josh McKenzie  wrote:

> Pranav,
>
> Here's a link to a list of tickets that are unassigned and have been
> designated good "Starter Tickets":
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2162&quickFilter=2160
>
> On Sun, Jul 6, 2025, at 7:44 PM, Jaydeep Chovatia wrote:
>
>
> Hey Pranav,
>
> Recently, the repair framework has been automated as part of CEP-37
> .
> But many improvements need to be made to cover other aspects of Apache
> Cassandra cluster lifecycle, such as automatically stopping the scheduler
> if a new DC is added, triggering the framework if the keyspace's
> replication factor changes, etc. Here are some of the unassigned tickets
> under epic (CASSANDRA-19918
> )
>
>- CASSANDRA-20414
>
>- CASSANDRA-20582
>
>
> There is also a dedicated ASF Slack channel (
> *#cassandra-repair-scheduling-cep37*) where we discuss some of the tasks.
> I'd be happy to hop on a call to update you on our current status and
> outline our plans for the next few months. Let me know!
>
> Jaydeep
>
> On Sat, Jul 5, 2025 at 11:27 PM pranav shenoy 
> wrote:
>
> Hi all,
>
>
> I've recently been contributing to Cassandra by working on some bugs in
> Accord, and I’m now looking to pick up my next tasks.
>
>
> While I’ve been browsing through JIRA, I find it a bit challenging to
> identify suitable tasks just based on the brief descriptions, as I’m still
> getting up to speed with the project. I was wondering if anyone could
> kindly point me toward tasks that I can pick - possibly beyond bug fixes.
>
>
> Also, I’d love to get a better understanding of the ongoing feature work
> or broader efforts that contributors are currently focusing on, in case
> there’s an opportunity to get involved.
>
>
> Thanks in advance for your guidance!
>
>
> Best regards,
>
> Pranav Shenoy
>
>
>