[DISCUSS] Seeking Guidance on Next Task and Areas to Contribute
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
Thanks Caleb! *Thanks and Regards* *Pranav* On Mon, Jul 7, 2025 at 8:49 PM Caleb Rackliffe wrote: > >1. CASSANDRA-19224 ><https://issues.apache.org/jira/browse/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 >>> <https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-37%3A+Apache+Cassandra+Unified+Repair+Solution>. >>> 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 >>> <https://issues.apache.org/jira/browse/CASSANDRA-19918>) >>> >>>- CASSANDRA-20414 >>><https://issues.apache.org/jira/browse/CASSANDRA-20414> >>>- CASSANDRA-20582 >>><https://issues.apache.org/jira/browse/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
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 > <https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-37%3A+Apache+Cassandra+Unified+Repair+Solution>. > 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 > <https://issues.apache.org/jira/browse/CASSANDRA-19918>) > >- CASSANDRA-20414 ><https://issues.apache.org/jira/browse/CASSANDRA-20414> >- CASSANDRA-20582 ><https://issues.apache.org/jira/browse/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 > > >
