Fwd: [Important] GSoC 2024 Project Ideas

[Paulo Motta]

See details below for submitting project ideas for GSoC 2024. This is a
good opportunity to attract/mentor new contributors.

I am not planning to mentor a project this year but would be happy to offer
support if someone wants to submit a proposal. Please message me if you are
interested or have any questions.

Please find below more details about previous participations in this
program:

* https://summerofcode.withgoogle.com/archive/2021/projects/5128135825162240
* https://summerofcode.withgoogle.com/archive/2016/projects/5429448547500032
*
https://cassandra.apache.org/_/blog/Join-Apache-Cassandras-GSoC-Program-2022.html
* https://cassandra.apache.org/_/blog/Join-Cassandra-GSoC-2021.html

-- Forwarded message -
From: Priya Sharma 
Date: Thu, 25 Jan 2024 at 07:21
Subject: [Important] GSoC 2024 Project Ideas

Google Summer of Code is the ideal opportunity for you to attract new
contributors to your projects and GSoC 2024 is here.

The ASF will be applying as a participating organization for GSoC 2024.
As a part of the application we need you all to *mandatorily* start
recording your ideas now [1] latest by 3rd Feb.

There is slight change in the rules this year, just reiterating here:
- For the 2024 program, there will be three options for project scope:
medium at ~175 hours, large at ~350 hours and a new size: small at ~90
hours.
  Please add "*full-time*" label to the JIRA for 350 hour project ,
"*part-time*" label for 175 hours project and “*small*” for a 90 hour
project.

Note: They are looking to bring more open source projects in the AI/ML
field into GSoC 2024, so we encourage more projects from this domain
to participate.

If you are a new mentor or your project is participating for the first
time, please read [2][3].

On behalf of the GSoC 2024 admins,
Please feel free to reach out to us in case of queries or concerns.

[1] https://s.apache.org/gsoc2024ideas
[2] https://community.apache.org/gsoc.html
[3] https://community.apache.org/guide-to-being-a-mentor.html

Re: [GSOC] Call for Mentors

[Dinesh Joshi]

I can help co-mentor if nobody else has already signed up.

> On Feb 14, 2022, at 7:46 AM, Joseph Lynch  wrote:
> 
> Hi Paulo!
> 
> Thanks for organizing this. I would like to propose CASSANDRA-17381
> [1] which will implement/verify BoundedReadCompactionStrategy for this
> year's GSOC and I can mentor (although I think we may need a
> co-mentor?). Please let me know if there is any further context I need
> to provide or jira tagging I need to do (I labeled it gsoc and
> gsoc2022).
> 
> [1] https://issues.apache.org/jira/browse/CASSANDRA-17381
> 
> -Joey
> 
> 
> On Fri, Feb 11, 2022 at 1:54 PM Paulo Motta  wrote:
>> 
>> Unfortunately we didn't, so far.
>> 
>> Em sex., 11 de fev. de 2022 às 15:32, Henrik Ingo  
>> escreveu:
>>> 
>>> Hi Paulo
>>> 
>>> Just checking, am I using Jira right: 
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20labels%20%3D%20gsoc%20and%20statusCategory%20!%3D%20Done%20
>>> 
>>> It looks like we ended up with no gsoc projects submitted? Or am I querying 
>>> wrong?
>>> 
>>> henrik
>>> 
>>> On Thu, Feb 3, 2022 at 12:26 AM Paulo Motta  
>>> wrote:
>>>> 
>>>> Hi Henrik,
>>>> 
>>>> I am happy to give feedback to project ideas - but they ultimately need to 
>>>> be registered by prospective mentors on JIRA with the "gsoc" tag to be 
>>>> considered a "subscribed idea".
>>>> 
>>>> The project idea JIRA should have a "high level" overview of what the 
>>>> project is:
>>>> - What is the problem statement?
>>>> - Rough plan on how to approach the problem.
>>>> - What are the main milestones/deliverables? (ie. 
>>>> code/benchmark/framework/blog post etc)
>>>> - What prior knowledge is required to complete the task?
>>>> - What warm-up tasks can the candidate do to ramp up for the project?
>>>> 
>>>> The mentor will work with potential participants to refine the high level 
>>>> description into smaller subtasks at a later stage (during candidate 
>>>> application period).
>>>> 
>>>> Cheers,
>>>> 
>>>> Paulo
>>>> 
>>>> Em qua., 2 de fev. de 2022 às 19:02, Henrik Ingo 
>>>>  escreveu:
>>>>> 
>>>>> Hi Paulo
>>>>> 
>>>>> I think Shaunak and Aleks V already pinged you on Slack about their 
>>>>> ideas. When you say we don't have any subscribed ideas, what is missing?
>>>>> 
>>>>> henrik
>>>>> 
>>>>> On Wed, Feb 2, 2022 at 4:03 PM Paulo Motta  
>>>>> wrote:
>>>>>> 
>>>>>> Hi everyone,
>>>>>> 
>>>>>> We need to tell ASF how many slots we will need for GSoC (if any) by 
>>>>>> February 20. So far we don't have any subscribed project ideas.
>>>>>> 
>>>>>> If you are interested in being a GSoC mentor, just ping me on slack and 
>>>>>> I will be happy to give you feedback on the project idea proposal. 
>>>>>> Please do so by no later than February 10 to allow sufficient time for 
>>>>>> follow-ups.
>>>>>> 
>>>>>> Cheers,
>>>>>> 
>>>>>> Paulo
>>>>>> 
>>>>>> Em qua., 19 de jan. de 2022 às 10:54, Paulo Motta  
>>>>>> escreveu:
>>>>>>> 
>>>>>>> Hi everyone,
>>>>>>> 
>>>>>>> Following up from the initial GSoC Kick-off thread [1] I would like to 
>>>>>>> invite contributors to submit GSoC project ideas. In order to submit a 
>>>>>>> project idea, just tag a JIRA ticket with the "gsoc" label and add 
>>>>>>> yourself to the "Mentor" field to indicate you're willing to mentor 
>>>>>>> this project.
>>>>>>> 
>>>>>>> Existing JIRA tickets can be repurposed as GSoC projects or new tickets 
>>>>>>> can be created with new features or improvements specifically for GSoC. 
>>>>>>> The best GSoC project ideas are those which are self-contained: have a 
>>>>>>> well defined scope, discrete milestones and definition of done. 
>>>>>>> Generally the areas which are easier for GSoC contributors to get 

Re: [GSOC] Call for Mentors

[Paulo Motta]

Thanks Benjamin and Joey for signing up these project ideas!

We're approaching the next period of the GSoC timeline from March 7 to
April 3, when mentoring organizations are announced and prospective GSoC
contributors reach out to communities to discuss and refine project ideas
before the GSoC application period starts on April 4.

Myself and Stefan used #cassandra-gsoc last year to discuss the project
with the GSoC contributor and we found it to be a great means to interact
and help with questions/mentoring during the project. I would like to
invite prospective mentors and anyone interested in helping out to join the
#cassandra-gsoc room on ASF Slack.

I'm working with Chris Thornett on a blog post to announce the Cassandra
Project Ideas on March 7 and will ask prospective GSoC contributors to join
#casandra-gsoc to discuss and refine project ideas.

If anyone else is interested in mentoring a GSoC project this year, it's
still possible to sign up a project idea by March 6 by tagging any Casandra
JIRA with the "gsoc2022" label.

Please let me know if you have any questions/comments.

Cheers,

Paulo

Em seg., 14 de fev. de 2022 às 12:53, Joseph Lynch 
escreveu:

> Hi Paulo!
>
> Thanks for organizing this. I would like to propose CASSANDRA-17381
> [1] which will implement/verify BoundedReadCompactionStrategy for this
> year's GSOC and I can mentor (although I think we may need a
> co-mentor?). Please let me know if there is any further context I need
> to provide or jira tagging I need to do (I labeled it gsoc and
> gsoc2022).
>
> [1] https://issues.apache.org/jira/browse/CASSANDRA-17381
>
> -Joey
>
>
> On Fri, Feb 11, 2022 at 1:54 PM Paulo Motta 
> wrote:
> >
> > Unfortunately we didn't, so far.
> >
> > Em sex., 11 de fev. de 2022 às 15:32, Henrik Ingo <
> henrik.i...@datastax.com> escreveu:
> >>
> >> Hi Paulo
> >>
> >> Just checking, am I using Jira right:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20labels%20%3D%20gsoc%20and%20statusCategory%20!%3D%20Done%20
> >>
> >> It looks like we ended up with no gsoc projects submitted? Or am I
> querying wrong?
> >>
> >> henrik
> >>
> >> On Thu, Feb 3, 2022 at 12:26 AM Paulo Motta 
> wrote:
> >>>
> >>> Hi Henrik,
> >>>
> >>> I am happy to give feedback to project ideas - but they ultimately
> need to be registered by prospective mentors on JIRA with the "gsoc" tag to
> be considered a "subscribed idea".
> >>>
> >>> The project idea JIRA should have a "high level" overview of what the
> project is:
> >>> - What is the problem statement?
> >>> - Rough plan on how to approach the problem.
> >>> - What are the main milestones/deliverables? (ie.
> code/benchmark/framework/blog post etc)
> >>> - What prior knowledge is required to complete the task?
> >>> - What warm-up tasks can the candidate do to ramp up for the project?
> >>>
> >>> The mentor will work with potential participants to refine the high
> level description into smaller subtasks at a later stage (during candidate
> application period).
> >>>
> >>> Cheers,
> >>>
> >>> Paulo
> >>>
> >>> Em qua., 2 de fev. de 2022 às 19:02, Henrik Ingo <
> henrik.i...@datastax.com> escreveu:
> >>>>
> >>>> Hi Paulo
> >>>>
> >>>> I think Shaunak and Aleks V already pinged you on Slack about their
> ideas. When you say we don't have any subscribed ideas, what is missing?
> >>>>
> >>>> henrik
> >>>>
> >>>> On Wed, Feb 2, 2022 at 4:03 PM Paulo Motta 
> wrote:
> >>>>>
> >>>>> Hi everyone,
> >>>>>
> >>>>> We need to tell ASF how many slots we will need for GSoC (if any) by
> February 20. So far we don't have any subscribed project ideas.
> >>>>>
> >>>>> If you are interested in being a GSoC mentor, just ping me on slack
> and I will be happy to give you feedback on the project idea proposal.
> Please do so by no later than February 10 to allow sufficient time for
> follow-ups.
> >>>>>
> >>>>> Cheers,
> >>>>>
> >>>>> Paulo
> >>>>>
> >>>>> Em qua., 19 de jan. de 2022 às 10:54, Paulo Motta 
> escreveu:
> >>>>>>
> >>>>>> Hi everyone,
> >>>>>>
> >>>>>> Following up from the initial GSoC Kick-off thread

Re: [GSOC] Call for Mentors

[Joseph Lynch]

Hi Paulo!

Thanks for organizing this. I would like to propose CASSANDRA-17381
[1] which will implement/verify BoundedReadCompactionStrategy for this
year's GSOC and I can mentor (although I think we may need a
co-mentor?). Please let me know if there is any further context I need
to provide or jira tagging I need to do (I labeled it gsoc and
gsoc2022).

[1] https://issues.apache.org/jira/browse/CASSANDRA-17381

-Joey


On Fri, Feb 11, 2022 at 1:54 PM Paulo Motta  wrote:
>
> Unfortunately we didn't, so far.
>
> Em sex., 11 de fev. de 2022 às 15:32, Henrik Ingo  
> escreveu:
>>
>> Hi Paulo
>>
>> Just checking, am I using Jira right: 
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20labels%20%3D%20gsoc%20and%20statusCategory%20!%3D%20Done%20
>>
>> It looks like we ended up with no gsoc projects submitted? Or am I querying 
>> wrong?
>>
>> henrik
>>
>> On Thu, Feb 3, 2022 at 12:26 AM Paulo Motta  wrote:
>>>
>>> Hi Henrik,
>>>
>>> I am happy to give feedback to project ideas - but they ultimately need to 
>>> be registered by prospective mentors on JIRA with the "gsoc" tag to be 
>>> considered a "subscribed idea".
>>>
>>> The project idea JIRA should have a "high level" overview of what the 
>>> project is:
>>> - What is the problem statement?
>>> - Rough plan on how to approach the problem.
>>> - What are the main milestones/deliverables? (ie. 
>>> code/benchmark/framework/blog post etc)
>>> - What prior knowledge is required to complete the task?
>>> - What warm-up tasks can the candidate do to ramp up for the project?
>>>
>>> The mentor will work with potential participants to refine the high level 
>>> description into smaller subtasks at a later stage (during candidate 
>>> application period).
>>>
>>> Cheers,
>>>
>>> Paulo
>>>
>>> Em qua., 2 de fev. de 2022 às 19:02, Henrik Ingo  
>>> escreveu:
>>>>
>>>> Hi Paulo
>>>>
>>>> I think Shaunak and Aleks V already pinged you on Slack about their ideas. 
>>>> When you say we don't have any subscribed ideas, what is missing?
>>>>
>>>> henrik
>>>>
>>>> On Wed, Feb 2, 2022 at 4:03 PM Paulo Motta  
>>>> wrote:
>>>>>
>>>>> Hi everyone,
>>>>>
>>>>> We need to tell ASF how many slots we will need for GSoC (if any) by 
>>>>> February 20. So far we don't have any subscribed project ideas.
>>>>>
>>>>> If you are interested in being a GSoC mentor, just ping me on slack and I 
>>>>> will be happy to give you feedback on the project idea proposal. Please 
>>>>> do so by no later than February 10 to allow sufficient time for 
>>>>> follow-ups.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Paulo
>>>>>
>>>>> Em qua., 19 de jan. de 2022 às 10:54, Paulo Motta  
>>>>> escreveu:
>>>>>>
>>>>>> Hi everyone,
>>>>>>
>>>>>> Following up from the initial GSoC Kick-off thread [1] I would like to 
>>>>>> invite contributors to submit GSoC project ideas. In order to submit a 
>>>>>> project idea, just tag a JIRA ticket with the "gsoc" label and add 
>>>>>> yourself to the "Mentor" field to indicate you're willing to mentor this 
>>>>>> project.
>>>>>>
>>>>>> Existing JIRA tickets can be repurposed as GSoC projects or new tickets 
>>>>>> can be created with new features or improvements specifically for GSoC. 
>>>>>> The best GSoC project ideas are those which are self-contained: have a 
>>>>>> well defined scope, discrete milestones and definition of done. 
>>>>>> Generally the areas which are easier for GSoC contributors to get 
>>>>>> started are:
>>>>>> - UX improvements
>>>>>> - Tools
>>>>>> - Benchmarking
>>>>>> - Refactoring and Modularization
>>>>>>
>>>>>> Non-committers are more than welcome to submit project ideas and mentor 
>>>>>> projects, as long as a committer is willing to co-mentor the project. As 
>>>>>> a matter of fact I was a GSoC mentor before becoming a committer, so I 
>>>>>> can say this i

Re: [GSOC] Call for Mentors

[Benjamin Lerer]

Hi Paulo,

I would like to propose CASSANDRA-17380 (Adds support for EXPLAIN
statements) as a project for this year's GSOC.

Le ven. 11 févr. 2022 à 19:54, Paulo Motta  a
écrit :

> Unfortunately we didn't, so far.
>
> Em sex., 11 de fev. de 2022 às 15:32, Henrik Ingo <
> henrik.i...@datastax.com> escreveu:
>
>> Hi Paulo
>>
>> Just checking, am I using Jira right:
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20labels%20%3D%20gsoc%20and%20statusCategory%20!%3D%20Done%20
>>
>> It looks like we ended up with no gsoc projects submitted? Or am I
>> querying wrong?
>>
>> henrik
>>
>> On Thu, Feb 3, 2022 at 12:26 AM Paulo Motta 
>> wrote:
>>
>>> Hi Henrik,
>>>
>>> I am happy to give feedback to project ideas - but they ultimately need
>>> to be registered by prospective mentors on JIRA with the "gsoc" tag to be
>>> considered a "subscribed idea".
>>>
>>> The project idea JIRA should have a "high level" overview of what the
>>> project is:
>>> - What is the problem statement?
>>> - Rough plan on how to approach the problem.
>>> - What are the main milestones/deliverables? (ie.
>>> code/benchmark/framework/blog post etc)
>>> - What prior knowledge is required to complete the task?
>>> - What warm-up tasks can the candidate do to ramp up for the project?
>>>
>>> The mentor will work with potential participants to refine the high
>>> level description into smaller subtasks at a later stage (during candidate
>>> application period).
>>>
>>> Cheers,
>>>
>>> Paulo
>>>
>>> Em qua., 2 de fev. de 2022 às 19:02, Henrik Ingo <
>>> henrik.i...@datastax.com> escreveu:
>>>
>>>> Hi Paulo
>>>>
>>>> I think Shaunak and Aleks V already pinged you on Slack about their
>>>> ideas. When you say we don't have any subscribed ideas, what is missing?
>>>>
>>>> henrik
>>>>
>>>> On Wed, Feb 2, 2022 at 4:03 PM Paulo Motta 
>>>> wrote:
>>>>
>>>>> Hi everyone,
>>>>>
>>>>> We need to tell ASF how many slots we will need for GSoC (if any) by
>>>>> February 20. So far we don't have any subscribed project ideas.
>>>>>
>>>>> If you are interested in being a GSoC mentor, just ping me on slack
>>>>> and I will be happy to give you feedback on the project idea proposal.
>>>>> Please do so by no later than February 10 to allow sufficient time for
>>>>> follow-ups.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Paulo
>>>>>
>>>>> Em qua., 19 de jan. de 2022 às 10:54, Paulo Motta 
>>>>> escreveu:
>>>>>
>>>>>> Hi everyone,
>>>>>>
>>>>>> Following up from the initial GSoC Kick-off thread [1] I would like
>>>>>> to invite contributors to submit GSoC project ideas. In order to submit a
>>>>>> project idea, just tag a JIRA ticket with the "gsoc" label and add 
>>>>>> yourself
>>>>>> to the "Mentor" field to indicate you're willing to mentor this project.
>>>>>>
>>>>>> Existing JIRA tickets can be repurposed as GSoC projects or new
>>>>>> tickets can be created with new features or improvements specifically for
>>>>>> GSoC. The best GSoC project ideas are those which are self-contained: 
>>>>>> have
>>>>>> a well defined scope, discrete milestones and definition of done. 
>>>>>> Generally
>>>>>> the areas which are easier for GSoC contributors to get started are:
>>>>>> - UX improvements
>>>>>> - Tools
>>>>>> - Benchmarking
>>>>>> - Refactoring and Modularization
>>>>>>
>>>>>> Non-committers are more than welcome to submit project ideas and
>>>>>> mentor projects, as long as a committer is willing to co-mentor the
>>>>>> project. As a matter of fact I was a GSoC mentor before becoming a
>>>>>> committer, so I can say this is a great way to pave your way to
>>>>>> committership. ;)
>>>>>>
>>>>>> Mentor tasks involve having 1 or 2 weekly meetings with the GSoC
>>>>>> participant to track the pr

Re: [GSOC] Call for Mentors

[Paulo Motta]

Unfortunately we didn't, so far.

Em sex., 11 de fev. de 2022 às 15:32, Henrik Ingo 
escreveu:

> Hi Paulo
>
> Just checking, am I using Jira right:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20labels%20%3D%20gsoc%20and%20statusCategory%20!%3D%20Done%20
>
> It looks like we ended up with no gsoc projects submitted? Or am I
> querying wrong?
>
> henrik
>
> On Thu, Feb 3, 2022 at 12:26 AM Paulo Motta 
> wrote:
>
>> Hi Henrik,
>>
>> I am happy to give feedback to project ideas - but they ultimately need
>> to be registered by prospective mentors on JIRA with the "gsoc" tag to be
>> considered a "subscribed idea".
>>
>> The project idea JIRA should have a "high level" overview of what the
>> project is:
>> - What is the problem statement?
>> - Rough plan on how to approach the problem.
>> - What are the main milestones/deliverables? (ie.
>> code/benchmark/framework/blog post etc)
>> - What prior knowledge is required to complete the task?
>> - What warm-up tasks can the candidate do to ramp up for the project?
>>
>> The mentor will work with potential participants to refine the high level
>> description into smaller subtasks at a later stage (during candidate
>> application period).
>>
>> Cheers,
>>
>> Paulo
>>
>> Em qua., 2 de fev. de 2022 às 19:02, Henrik Ingo <
>> henrik.i...@datastax.com> escreveu:
>>
>>> Hi Paulo
>>>
>>> I think Shaunak and Aleks V already pinged you on Slack about their
>>> ideas. When you say we don't have any subscribed ideas, what is missing?
>>>
>>> henrik
>>>
>>> On Wed, Feb 2, 2022 at 4:03 PM Paulo Motta 
>>> wrote:
>>>
>>>> Hi everyone,
>>>>
>>>> We need to tell ASF how many slots we will need for GSoC (if any) by
>>>> February 20. So far we don't have any subscribed project ideas.
>>>>
>>>> If you are interested in being a GSoC mentor, just ping me on slack and
>>>> I will be happy to give you feedback on the project idea proposal. Please
>>>> do so by no later than February 10 to allow sufficient time for follow-ups.
>>>>
>>>> Cheers,
>>>>
>>>> Paulo
>>>>
>>>> Em qua., 19 de jan. de 2022 às 10:54, Paulo Motta 
>>>> escreveu:
>>>>
>>>>> Hi everyone,
>>>>>
>>>>> Following up from the initial GSoC Kick-off thread [1] I would like to
>>>>> invite contributors to submit GSoC project ideas. In order to submit a
>>>>> project idea, just tag a JIRA ticket with the "gsoc" label and add 
>>>>> yourself
>>>>> to the "Mentor" field to indicate you're willing to mentor this project.
>>>>>
>>>>> Existing JIRA tickets can be repurposed as GSoC projects or new
>>>>> tickets can be created with new features or improvements specifically for
>>>>> GSoC. The best GSoC project ideas are those which are self-contained: have
>>>>> a well defined scope, discrete milestones and definition of done. 
>>>>> Generally
>>>>> the areas which are easier for GSoC contributors to get started are:
>>>>> - UX improvements
>>>>> - Tools
>>>>> - Benchmarking
>>>>> - Refactoring and Modularization
>>>>>
>>>>> Non-committers are more than welcome to submit project ideas and
>>>>> mentor projects, as long as a committer is willing to co-mentor the
>>>>> project. As a matter of fact I was a GSoC mentor before becoming a
>>>>> committer, so I can say this is a great way to pave your way to
>>>>> committership. ;)
>>>>>
>>>>> Mentor tasks involve having 1 or 2 weekly meetings with the GSoC
>>>>> participant to track the project status and give guidance to the
>>>>> participant towards the completion of the project, as well as reviewing
>>>>> code submissions.
>>>>>
>>>>> This year, GSoC is open to any participant over 18 years of age, no
>>>>> longer focusing solely on university students. GSoC projects can be of 
>>>>> ~175
>>>>> hour (medium) and 350 hour (large), and can range from 12 to 22 weeks
>>>>> starting in July.
>>>>>
>>>>> We have little less than 2 months until the start of the GSoC
>>>>>

Re: [GSOC] Call for Mentors

[Henrik Ingo]

Hi Paulo

Just checking, am I using Jira right:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20labels%20%3D%20gsoc%20and%20statusCategory%20!%3D%20Done%20

It looks like we ended up with no gsoc projects submitted? Or am I querying
wrong?

henrik

On Thu, Feb 3, 2022 at 12:26 AM Paulo Motta 
wrote:

> Hi Henrik,
>
> I am happy to give feedback to project ideas - but they ultimately need to
> be registered by prospective mentors on JIRA with the "gsoc" tag to be
> considered a "subscribed idea".
>
> The project idea JIRA should have a "high level" overview of what the
> project is:
> - What is the problem statement?
> - Rough plan on how to approach the problem.
> - What are the main milestones/deliverables? (ie.
> code/benchmark/framework/blog post etc)
> - What prior knowledge is required to complete the task?
> - What warm-up tasks can the candidate do to ramp up for the project?
>
> The mentor will work with potential participants to refine the high level
> description into smaller subtasks at a later stage (during candidate
> application period).
>
> Cheers,
>
> Paulo
>
> Em qua., 2 de fev. de 2022 às 19:02, Henrik Ingo 
> escreveu:
>
>> Hi Paulo
>>
>> I think Shaunak and Aleks V already pinged you on Slack about their
>> ideas. When you say we don't have any subscribed ideas, what is missing?
>>
>> henrik
>>
>> On Wed, Feb 2, 2022 at 4:03 PM Paulo Motta 
>> wrote:
>>
>>> Hi everyone,
>>>
>>> We need to tell ASF how many slots we will need for GSoC (if any) by
>>> February 20. So far we don't have any subscribed project ideas.
>>>
>>> If you are interested in being a GSoC mentor, just ping me on slack and
>>> I will be happy to give you feedback on the project idea proposal. Please
>>> do so by no later than February 10 to allow sufficient time for follow-ups.
>>>
>>> Cheers,
>>>
>>> Paulo
>>>
>>> Em qua., 19 de jan. de 2022 às 10:54, Paulo Motta 
>>> escreveu:
>>>
>>>> Hi everyone,
>>>>
>>>> Following up from the initial GSoC Kick-off thread [1] I would like to
>>>> invite contributors to submit GSoC project ideas. In order to submit a
>>>> project idea, just tag a JIRA ticket with the "gsoc" label and add yourself
>>>> to the "Mentor" field to indicate you're willing to mentor this project.
>>>>
>>>> Existing JIRA tickets can be repurposed as GSoC projects or new tickets
>>>> can be created with new features or improvements specifically for GSoC. The
>>>> best GSoC project ideas are those which are self-contained: have a well
>>>> defined scope, discrete milestones and definition of done. Generally the
>>>> areas which are easier for GSoC contributors to get started are:
>>>> - UX improvements
>>>> - Tools
>>>> - Benchmarking
>>>> - Refactoring and Modularization
>>>>
>>>> Non-committers are more than welcome to submit project ideas and mentor
>>>> projects, as long as a committer is willing to co-mentor the project. As a
>>>> matter of fact I was a GSoC mentor before becoming a committer, so I can
>>>> say this is a great way to pave your way to committership. ;)
>>>>
>>>> Mentor tasks involve having 1 or 2 weekly meetings with the GSoC
>>>> participant to track the project status and give guidance to the
>>>> participant towards the completion of the project, as well as reviewing
>>>> code submissions.
>>>>
>>>> This year, GSoC is open to any participant over 18 years of age, no
>>>> longer focusing solely on university students. GSoC projects can be of ~175
>>>> hour (medium) and 350 hour (large), and can range from 12 to 22 weeks
>>>> starting in July.
>>>>
>>>> We have little less than 2 months until the start of the GSoC
>>>> application period on March 7, but ideally we want to have an "Ideas List"
>>>> ready before that so prospective participants can start engaging with the
>>>> project and working with mentors to refine the project before submitting an
>>>> application.
>>>>
>>>> This year I will not be able to participate as a primary mentor but I
>>>> would be happy to co-mentor other projects as well as help with questions
>>>> and guidance.
>>>>
>>>> Kind regards,
>>>>
>>>> Paulo
>>&g

Re: [GSOC] Call for Mentors

[Paulo Motta]

Hi Henrik,

I am happy to give feedback to project ideas - but they ultimately need to
be registered by prospective mentors on JIRA with the "gsoc" tag to be
considered a "subscribed idea".

The project idea JIRA should have a "high level" overview of what the
project is:
- What is the problem statement?
- Rough plan on how to approach the problem.
- What are the main milestones/deliverables? (ie.
code/benchmark/framework/blog post etc)
- What prior knowledge is required to complete the task?
- What warm-up tasks can the candidate do to ramp up for the project?

The mentor will work with potential participants to refine the high level
description into smaller subtasks at a later stage (during candidate
application period).

Cheers,

Paulo

Em qua., 2 de fev. de 2022 às 19:02, Henrik Ingo 
escreveu:

> Hi Paulo
>
> I think Shaunak and Aleks V already pinged you on Slack about their ideas.
> When you say we don't have any subscribed ideas, what is missing?
>
> henrik
>
> On Wed, Feb 2, 2022 at 4:03 PM Paulo Motta 
> wrote:
>
>> Hi everyone,
>>
>> We need to tell ASF how many slots we will need for GSoC (if any) by
>> February 20. So far we don't have any subscribed project ideas.
>>
>> If you are interested in being a GSoC mentor, just ping me on slack and I
>> will be happy to give you feedback on the project idea proposal. Please do
>> so by no later than February 10 to allow sufficient time for follow-ups.
>>
>> Cheers,
>>
>> Paulo
>>
>> Em qua., 19 de jan. de 2022 às 10:54, Paulo Motta 
>> escreveu:
>>
>>> Hi everyone,
>>>
>>> Following up from the initial GSoC Kick-off thread [1] I would like to
>>> invite contributors to submit GSoC project ideas. In order to submit a
>>> project idea, just tag a JIRA ticket with the "gsoc" label and add yourself
>>> to the "Mentor" field to indicate you're willing to mentor this project.
>>>
>>> Existing JIRA tickets can be repurposed as GSoC projects or new tickets
>>> can be created with new features or improvements specifically for GSoC. The
>>> best GSoC project ideas are those which are self-contained: have a well
>>> defined scope, discrete milestones and definition of done. Generally the
>>> areas which are easier for GSoC contributors to get started are:
>>> - UX improvements
>>> - Tools
>>> - Benchmarking
>>> - Refactoring and Modularization
>>>
>>> Non-committers are more than welcome to submit project ideas and mentor
>>> projects, as long as a committer is willing to co-mentor the project. As a
>>> matter of fact I was a GSoC mentor before becoming a committer, so I can
>>> say this is a great way to pave your way to committership. ;)
>>>
>>> Mentor tasks involve having 1 or 2 weekly meetings with the GSoC
>>> participant to track the project status and give guidance to the
>>> participant towards the completion of the project, as well as reviewing
>>> code submissions.
>>>
>>> This year, GSoC is open to any participant over 18 years of age, no
>>> longer focusing solely on university students. GSoC projects can be of ~175
>>> hour (medium) and 350 hour (large), and can range from 12 to 22 weeks
>>> starting in July.
>>>
>>> We have little less than 2 months until the start of the GSoC
>>> application period on March 7, but ideally we want to have an "Ideas List"
>>> ready before that so prospective participants can start engaging with the
>>> project and working with mentors to refine the project before submitting an
>>> application.
>>>
>>> This year I will not be able to participate as a primary mentor but I
>>> would be happy to co-mentor other projects as well as help with questions
>>> and guidance.
>>>
>>> Kind regards,
>>>
>>> Paulo
>>>
>>> [1] https://lists.apache.org/thread/58v2bvfzwtfgqdx90qmm4tmyoqzsgtn4
>>>
>>
>
> --
>
> Henrik Ingo
>
> +358 40 569 7354 <358405697354>
>
> [image: Visit us online.] <https://www.datastax.com/>  [image: Visit us
> on Twitter.] <https://twitter.com/DataStaxEng>  [image: Visit us on
> YouTube.]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_channel_UCqA6zOSMpQ55vvguq4Y0jAg=DwMFaQ=adz96Xi0w1RHqtPMowiL2g=IFj3MdIKYLLXIUhYdUGB0cTzTlxyCb7_VUmICBaYilU=bmIfaie9O3fWJAu6lESvWj3HajV4VFwgwgVuKmxKZmE=16sY48_kvIb7sRQORknZrr3V8iLTfemFKbMVNZhdwgw=>
>   [image: Visit my LinkedIn profile.]
> <https://www.linkedin.com/in/heingo/>
>

Re: [GSOC] Call for Mentors

[Henrik Ingo]

Hi Paulo

I think Shaunak and Aleks V already pinged you on Slack about their ideas.
When you say we don't have any subscribed ideas, what is missing?

henrik

On Wed, Feb 2, 2022 at 4:03 PM Paulo Motta  wrote:

> Hi everyone,
>
> We need to tell ASF how many slots we will need for GSoC (if any) by
> February 20. So far we don't have any subscribed project ideas.
>
> If you are interested in being a GSoC mentor, just ping me on slack and I
> will be happy to give you feedback on the project idea proposal. Please do
> so by no later than February 10 to allow sufficient time for follow-ups.
>
> Cheers,
>
> Paulo
>
> Em qua., 19 de jan. de 2022 às 10:54, Paulo Motta 
> escreveu:
>
>> Hi everyone,
>>
>> Following up from the initial GSoC Kick-off thread [1] I would like to
>> invite contributors to submit GSoC project ideas. In order to submit a
>> project idea, just tag a JIRA ticket with the "gsoc" label and add yourself
>> to the "Mentor" field to indicate you're willing to mentor this project.
>>
>> Existing JIRA tickets can be repurposed as GSoC projects or new tickets
>> can be created with new features or improvements specifically for GSoC. The
>> best GSoC project ideas are those which are self-contained: have a well
>> defined scope, discrete milestones and definition of done. Generally the
>> areas which are easier for GSoC contributors to get started are:
>> - UX improvements
>> - Tools
>> - Benchmarking
>> - Refactoring and Modularization
>>
>> Non-committers are more than welcome to submit project ideas and mentor
>> projects, as long as a committer is willing to co-mentor the project. As a
>> matter of fact I was a GSoC mentor before becoming a committer, so I can
>> say this is a great way to pave your way to committership. ;)
>>
>> Mentor tasks involve having 1 or 2 weekly meetings with the GSoC
>> participant to track the project status and give guidance to the
>> participant towards the completion of the project, as well as reviewing
>> code submissions.
>>
>> This year, GSoC is open to any participant over 18 years of age, no
>> longer focusing solely on university students. GSoC projects can be of ~175
>> hour (medium) and 350 hour (large), and can range from 12 to 22 weeks
>> starting in July.
>>
>> We have little less than 2 months until the start of the GSoC application
>> period on March 7, but ideally we want to have an "Ideas List" ready before
>> that so prospective participants can start engaging with the project and
>> working with mentors to refine the project before submitting an application.
>>
>> This year I will not be able to participate as a primary mentor but I
>> would be happy to co-mentor other projects as well as help with questions
>> and guidance.
>>
>> Kind regards,
>>
>> Paulo
>>
>> [1] https://lists.apache.org/thread/58v2bvfzwtfgqdx90qmm4tmyoqzsgtn4
>>
>

-- 

Henrik Ingo

+358 40 569 7354 <358405697354>

[image: Visit us online.] <https://www.datastax.com/>  [image: Visit us on
Twitter.] <https://twitter.com/DataStaxEng>  [image: Visit us on YouTube.]
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_channel_UCqA6zOSMpQ55vvguq4Y0jAg=DwMFaQ=adz96Xi0w1RHqtPMowiL2g=IFj3MdIKYLLXIUhYdUGB0cTzTlxyCb7_VUmICBaYilU=bmIfaie9O3fWJAu6lESvWj3HajV4VFwgwgVuKmxKZmE=16sY48_kvIb7sRQORknZrr3V8iLTfemFKbMVNZhdwgw=>
  [image: Visit my LinkedIn profile.] <https://www.linkedin.com/in/heingo/>

Re: [GSOC] Call for Mentors

[Paulo Motta]

Hi everyone,

We need to tell ASF how many slots we will need for GSoC (if any) by
February 20. So far we don't have any subscribed project ideas.

If you are interested in being a GSoC mentor, just ping me on slack and I
will be happy to give you feedback on the project idea proposal. Please do
so by no later than February 10 to allow sufficient time for follow-ups.

Cheers,

Paulo

Em qua., 19 de jan. de 2022 às 10:54, Paulo Motta 
escreveu:

> Hi everyone,
>
> Following up from the initial GSoC Kick-off thread [1] I would like to
> invite contributors to submit GSoC project ideas. In order to submit a
> project idea, just tag a JIRA ticket with the "gsoc" label and add yourself
> to the "Mentor" field to indicate you're willing to mentor this project.
>
> Existing JIRA tickets can be repurposed as GSoC projects or new tickets
> can be created with new features or improvements specifically for GSoC. The
> best GSoC project ideas are those which are self-contained: have a well
> defined scope, discrete milestones and definition of done. Generally the
> areas which are easier for GSoC contributors to get started are:
> - UX improvements
> - Tools
> - Benchmarking
> - Refactoring and Modularization
>
> Non-committers are more than welcome to submit project ideas and mentor
> projects, as long as a committer is willing to co-mentor the project. As a
> matter of fact I was a GSoC mentor before becoming a committer, so I can
> say this is a great way to pave your way to committership. ;)
>
> Mentor tasks involve having 1 or 2 weekly meetings with the GSoC
> participant to track the project status and give guidance to the
> participant towards the completion of the project, as well as reviewing
> code submissions.
>
> This year, GSoC is open to any participant over 18 years of age, no longer
> focusing solely on university students. GSoC projects can be of ~175 hour
> (medium) and 350 hour (large), and can range from 12 to 22 weeks starting
> in July.
>
> We have little less than 2 months until the start of the GSoC application
> period on March 7, but ideally we want to have an "Ideas List" ready before
> that so prospective participants can start engaging with the project and
> working with mentors to refine the project before submitting an application.
>
> This year I will not be able to participate as a primary mentor but I
> would be happy to co-mentor other projects as well as help with questions
> and guidance.
>
> Kind regards,
>
> Paulo
>
> [1] https://lists.apache.org/thread/58v2bvfzwtfgqdx90qmm4tmyoqzsgtn4
>

Re: Is Cassandra going to be a part of GSoC 2022?

[Erick Ramirez]

Welcome! Yes, it is. Details in these threads --
https://lists.apache.org/thread/58v2bvfzwtfgqdx90qmm4tmyoqzsgtn4 and
https://lists.apache.org/thread/rht6py71z1f8cxjzpo22bhgzl3f60kdp. Cheers!

Is Cassandra going to be a part of GSoC 2022?

[Shreyan Budhouliya]

Hi, I found your email id from the list of ideas presented by Cassandra in
GSoC 2021 through this link :
*https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2021+Ideas+list#GSoC2021Ideaslist-Cassandra
<https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2021+Ideas+list#GSoC2021Ideaslist-Cassandra>*
*I'll like to know if Cassandra will be a part of GSoC 2022. If yes, then
what will be a good starting point? *
Thank you!

[GSOC] Call for Mentors

[Paulo Motta]

Hi everyone,

Following up from the initial GSoC Kick-off thread [1] I would like to
invite contributors to submit GSoC project ideas. In order to submit a
project idea, just tag a JIRA ticket with the "gsoc" label and add yourself
to the "Mentor" field to indicate you're willing to mentor this project.

Existing JIRA tickets can be repurposed as GSoC projects or new tickets can
be created with new features or improvements specifically for GSoC. The
best GSoC project ideas are those which are self-contained: have a well
defined scope, discrete milestones and definition of done. Generally the
areas which are easier for GSoC contributors to get started are:
- UX improvements
- Tools
- Benchmarking
- Refactoring and Modularization

Non-committers are more than welcome to submit project ideas and mentor
projects, as long as a committer is willing to co-mentor the project. As a
matter of fact I was a GSoC mentor before becoming a committer, so I can
say this is a great way to pave your way to committership. ;)

Mentor tasks involve having 1 or 2 weekly meetings with the GSoC
participant to track the project status and give guidance to the
participant towards the completion of the project, as well as reviewing
code submissions.

This year, GSoC is open to any participant over 18 years of age, no longer
focusing solely on university students. GSoC projects can be of ~175 hour
(medium) and 350 hour (large), and can range from 12 to 22 weeks starting
in July.

We have little less than 2 months until the start of the GSoC application
period on March 7, but ideally we want to have an "Ideas List" ready before
that so prospective participants can start engaging with the project and
working with mentors to refine the project before submitting an application.

This year I will not be able to participate as a primary mentor but I would
be happy to co-mentor other projects as well as help with questions and
guidance.

Kind regards,

Paulo

[1] https://lists.apache.org/thread/58v2bvfzwtfgqdx90qmm4tmyoqzsgtn4

Re: GSoC

[Paulo Motta]

Hi Isidoro,

This seems like a good start! The system.local table holds information
about the local node while the system.peers and system.peers_v2 tables hold
information about remote peers.

The issue is that the tables are being populated differently while they
must be consistent. While the systems.local table is populated locally via
DatabaseDescriptor.getRpcAddress() [1], the system.peers/system.peers_v2
table is populated from gossip here [3] on the sender end (which uses
DatabaseDescriptor.getBroadcastNativeAddressAndPort()) and here [2] on the
receiver end.

When broadcast_rpc_address is set, system.local.rpc_address is set to
DatabaseDescriptor.getRpcAddress(), while system.peers_v2.native_address
(which is the new name for system.peers.rpc_address in previous versions)
is set to DatabaseDescriptor.getBroadcastNativeAddressAndPort(), making
both tables show different values depending whether the query is made on
the local node or on a remote node.

We want these values to be consistent, so the value shown on
system.local.rpc_address must match the value on
system.peers_v2.native_address for the same node. It would be nice to add a
test reproducing the issue to help verify the fix.

If you have any follow-up questions or comments please communicate on the
JIRA ticket itself, so we can keep the discussion history there (and also
because this list is for general discussions).

Good luck!

Paulo

[1] -
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/SystemKeyspace.java#L496
[2] -
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StorageService.java#L952
[3] -
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StorageService.java#L2354

Em sex., 2 de abr. de 2021 às 15:13, Isidoro Garcia Gutierrez <
igarcia...@uoc.edu> escreveu:

> Thank you Paulo.
>
> I have started working on ticket 16386. After reading the problem, I have
> looked up information about the rpc_address, broadcast_rpc_address and
> other config variables, the system.local and system.peer tables. The
> variable rpc_address appears in both tables, so it seems that the controls
> to assign value to it in each table are different. I have located the
> variables rpc_address and broadcast_rpc_addres in the config / Config
> class, from there I have moved to the config / DatabaseDescriptor and
> service / StorageService classes.
>
> I don't know if this is the right way to work but all this is new for me,
> hence all the problems and doubts.
>
> Cheers.
>
> El mié, 31 mar 2021 a las 21:27, Paulo Motta ()
> escribió:
>
> > Hi Isidoro,
> >
> > Thanks for your interest in contributing to Apache Cassandra on GSoC.
> >
> > I think that CASSANDRA-14709 [1] and CASSANDRA-11511 [2] would be good
> > complimentary tasks for a GSoC project, because while the former
> provides a
> > global configuration knob to disable anti-compactions after repair, the
> > latter provides a per-operation flag to achieve the same effect which can
> > be useful for some users with little additional coding effort.
> >
> > A good way to strengthen your application is to work on a small ticket to
> > demonstrate your ability to dive on the codebase. A list of "low hanging
> > fruit" tickets can be found here [3]. From a quick glance CASSANDRA-16386
> > seems to be a good initial ticket since the scope seems to be small, the
> > hardest part is to understand the task context. Something that can help
> is
> > to request more details on the JIRA ticket itself.
> >
> > Feel free to reach here or on #cassandra-dev as Brandon suggested if you
> > have additional questions.
> >
> > Cheers,
> >
> > Paulo
> >
> > [1] - https://issues.apache.org/jira/browse/CASSANDRA-14709
> > [2] - https://issues.apache.org/jira/browse/CASSANDRA-11511
> > [3] -
> >
> >
> https://issues.apache.org/jira/browse/CASSANDRA-16528?jql=project%20%3D%20cassandra%20AND%20status%20%20%3D%20open%20and%20assignee%20%3D%20empty%20and%20type%20%3D%20bug%20and%20(complexity%20%3D%20%22LOW%20HANGING%20FRUIT%22%20or%20labels%20%3D%20lhf)
> >
> > Em qua., 31 de mar. de 2021 às 12:03, Isidoro Garcia Gutierrez <
> > igarcia...@uoc.edu> escreveu:
> >
> > > Thank you very much Brandon, this is what I needed to get started and
> try
> > > to make a decent application.
> > >
> > > Best regards.
> > >
> > > El mar, 30 mar 2021 a las 21:00, Brandon Williams ()
> > > escribió:
> > >
> > > > It probably seems a bit more complicated than it actually is if you
> > > > aren't familiar with the code base.  I can provide a quick high level
> > >

Re: GSoC

[Isidoro Garcia Gutierrez]

Thank you Paulo.

I have started working on ticket 16386. After reading the problem, I have
looked up information about the rpc_address, broadcast_rpc_address and
other config variables, the system.local and system.peer tables. The
variable rpc_address appears in both tables, so it seems that the controls
to assign value to it in each table are different. I have located the
variables rpc_address and broadcast_rpc_addres in the config / Config
class, from there I have moved to the config / DatabaseDescriptor and
service / StorageService classes.

I don't know if this is the right way to work but all this is new for me,
hence all the problems and doubts.

Cheers.

El mié, 31 mar 2021 a las 21:27, Paulo Motta ()
escribió:

> Hi Isidoro,
>
> Thanks for your interest in contributing to Apache Cassandra on GSoC.
>
> I think that CASSANDRA-14709 [1] and CASSANDRA-11511 [2] would be good
> complimentary tasks for a GSoC project, because while the former provides a
> global configuration knob to disable anti-compactions after repair, the
> latter provides a per-operation flag to achieve the same effect which can
> be useful for some users with little additional coding effort.
>
> A good way to strengthen your application is to work on a small ticket to
> demonstrate your ability to dive on the codebase. A list of "low hanging
> fruit" tickets can be found here [3]. From a quick glance CASSANDRA-16386
> seems to be a good initial ticket since the scope seems to be small, the
> hardest part is to understand the task context. Something that can help is
> to request more details on the JIRA ticket itself.
>
> Feel free to reach here or on #cassandra-dev as Brandon suggested if you
> have additional questions.
>
> Cheers,
>
> Paulo
>
> [1] - https://issues.apache.org/jira/browse/CASSANDRA-14709
> [2] - https://issues.apache.org/jira/browse/CASSANDRA-11511
> [3] -
>
> https://issues.apache.org/jira/browse/CASSANDRA-16528?jql=project%20%3D%20cassandra%20AND%20status%20%20%3D%20open%20and%20assignee%20%3D%20empty%20and%20type%20%3D%20bug%20and%20(complexity%20%3D%20%22LOW%20HANGING%20FRUIT%22%20or%20labels%20%3D%20lhf)
>
> Em qua., 31 de mar. de 2021 às 12:03, Isidoro Garcia Gutierrez <
> igarcia...@uoc.edu> escreveu:
>
> > Thank you very much Brandon, this is what I needed to get started and try
> > to make a decent application.
> >
> > Best regards.
> >
> > El mar, 30 mar 2021 a las 21:00, Brandon Williams ()
> > escribió:
> >
> > > It probably seems a bit more complicated than it actually is if you
> > > aren't familiar with the code base.  I can provide a quick high level
> > > overview of how this ticket would be accomplished:
> > >
> > > First, add the configuration parameter.  This would involve adding it
> > > to o.a.c.config.Config.java[0] with a default of being disabled, and
> > > then a getter and setter should be added to DatabaseDescriptor[1].
> > > From there it's a matter of having the system check this before
> > > invoking repairs.  We can see from nodetool's repair command[2] that
> > > this ends up calling repairAsync in StorageService[3] via JMX.
> > >
> > > Of course the devil is always in the details (and I've glossed over
> > > some here,) but that's what my initial plan of attack would be, and
> > > hopefully it's enough to give you an idea of what might be involved.
> > >
> > > If you want more interactive help, I recommend joining the
> > > #cassandra-dev slack channel.
> > >
> > > [0]
> > >
> >
> https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/config/Config.java
> > > [1]
> > >
> >
> https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/config/DatabaseDescriptor.java
> > > [2]
> > >
> >
> https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/tools/nodetool/Repair.java
> > > [3]
> > >
> >
> https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/service/StorageService.java
> > >
> > >
> > > On Tue, Mar 30, 2021 at 10:57 AM Isidoro Garcia Gutierrez
> > >  wrote:
> > > >
> > > > Hello everyone,
> > > > I would like to apply for the idea Global configuration parameter to
> > > reject
> > > > repairs with anti-compaction
> > > > <https://issues.apache.org/jira/browse/CASSANDRA-14709> but I don't
> > > know if
> > > > I have enough skill to do it right.
> > > > I read that the difficulty is normal 

Re: GSoC

[Paulo Motta]

Hi Isidoro,

Thanks for your interest in contributing to Apache Cassandra on GSoC.

I think that CASSANDRA-14709 [1] and CASSANDRA-11511 [2] would be good
complimentary tasks for a GSoC project, because while the former provides a
global configuration knob to disable anti-compactions after repair, the
latter provides a per-operation flag to achieve the same effect which can
be useful for some users with little additional coding effort.

A good way to strengthen your application is to work on a small ticket to
demonstrate your ability to dive on the codebase. A list of "low hanging
fruit" tickets can be found here [3]. From a quick glance CASSANDRA-16386
seems to be a good initial ticket since the scope seems to be small, the
hardest part is to understand the task context. Something that can help is
to request more details on the JIRA ticket itself.

Feel free to reach here or on #cassandra-dev as Brandon suggested if you
have additional questions.

Cheers,

Paulo

[1] - https://issues.apache.org/jira/browse/CASSANDRA-14709
[2] - https://issues.apache.org/jira/browse/CASSANDRA-11511
[3] -
https://issues.apache.org/jira/browse/CASSANDRA-16528?jql=project%20%3D%20cassandra%20AND%20status%20%20%3D%20open%20and%20assignee%20%3D%20empty%20and%20type%20%3D%20bug%20and%20(complexity%20%3D%20%22LOW%20HANGING%20FRUIT%22%20or%20labels%20%3D%20lhf)

Em qua., 31 de mar. de 2021 às 12:03, Isidoro Garcia Gutierrez <
igarcia...@uoc.edu> escreveu:

> Thank you very much Brandon, this is what I needed to get started and try
> to make a decent application.
>
> Best regards.
>
> El mar, 30 mar 2021 a las 21:00, Brandon Williams ()
> escribió:
>
> > It probably seems a bit more complicated than it actually is if you
> > aren't familiar with the code base.  I can provide a quick high level
> > overview of how this ticket would be accomplished:
> >
> > First, add the configuration parameter.  This would involve adding it
> > to o.a.c.config.Config.java[0] with a default of being disabled, and
> > then a getter and setter should be added to DatabaseDescriptor[1].
> > From there it's a matter of having the system check this before
> > invoking repairs.  We can see from nodetool's repair command[2] that
> > this ends up calling repairAsync in StorageService[3] via JMX.
> >
> > Of course the devil is always in the details (and I've glossed over
> > some here,) but that's what my initial plan of attack would be, and
> > hopefully it's enough to give you an idea of what might be involved.
> >
> > If you want more interactive help, I recommend joining the
> > #cassandra-dev slack channel.
> >
> > [0]
> >
> https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/config/Config.java
> > [1]
> >
> https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/config/DatabaseDescriptor.java
> > [2]
> >
> https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/tools/nodetool/Repair.java
> > [3]
> >
> https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/service/StorageService.java
> >
> >
> > On Tue, Mar 30, 2021 at 10:57 AM Isidoro Garcia Gutierrez
> >  wrote:
> > >
> > > Hello everyone,
> > > I would like to apply for the idea Global configuration parameter to
> > reject
> > > repairs with anti-compaction
> > > <https://issues.apache.org/jira/browse/CASSANDRA-14709> but I don't
> > know if
> > > I have enough skill to do it right.
> > > I read that the difficulty is normal but before applying I would like
> to
> > > know a little more about this topic before making the proposal for the
> > job.
> > > Can someone help me?
> > >
> > > Thanks.
> > >
> > > --
> > >
> > >
> > >
> > > INFORMACIÓ SOBRE PROTECCIÓ DE DADES DE LA UNIVERSITAT OBERTA DE
> > > CATALUNYA (UOC)
> > >
> > > Us informem que les vostres dades identificatives i les
> > > contingudes en els missatges electrònics i fitxers adjunts es poden
> > > incorporar a les nostres bases de dades amb la finalitat de gestionar
> les
> > > relacions i comunicacions vinculades a la UOC, i que es poden conservar
> > > mentre es mantingui la relació. Si ho voleu, podeu exercir el dret a
> > > accedir a les vostres dades, rectificar-les i suprimir-les i altres
> drets
> > > reconeguts normativament adreçant-vos a l'adreça de correu emissora o a
> > > fuoc...@uoc.edu <mailto:fuoc...@uoc.edu>.
> > >
> > > Aquest missatge i qualsevol
> > > fitxer que porti

Re: GSoC

[Isidoro Garcia Gutierrez]

Thank you very much Brandon, this is what I needed to get started and try
to make a decent application.

Best regards.

El mar, 30 mar 2021 a las 21:00, Brandon Williams ()
escribió:

> It probably seems a bit more complicated than it actually is if you
> aren't familiar with the code base.  I can provide a quick high level
> overview of how this ticket would be accomplished:
>
> First, add the configuration parameter.  This would involve adding it
> to o.a.c.config.Config.java[0] with a default of being disabled, and
> then a getter and setter should be added to DatabaseDescriptor[1].
> From there it's a matter of having the system check this before
> invoking repairs.  We can see from nodetool's repair command[2] that
> this ends up calling repairAsync in StorageService[3] via JMX.
>
> Of course the devil is always in the details (and I've glossed over
> some here,) but that's what my initial plan of attack would be, and
> hopefully it's enough to give you an idea of what might be involved.
>
> If you want more interactive help, I recommend joining the
> #cassandra-dev slack channel.
>
> [0]
> https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/config/Config.java
> [1]
> https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/config/DatabaseDescriptor.java
> [2]
> https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/tools/nodetool/Repair.java
> [3]
> https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/service/StorageService.java
>
>
> On Tue, Mar 30, 2021 at 10:57 AM Isidoro Garcia Gutierrez
>  wrote:
> >
> > Hello everyone,
> > I would like to apply for the idea Global configuration parameter to
> reject
> > repairs with anti-compaction
> >  but I don't
> know if
> > I have enough skill to do it right.
> > I read that the difficulty is normal but before applying I would like to
> > know a little more about this topic before making the proposal for the
> job.
> > Can someone help me?
> >
> > Thanks.
> >
> > --
> >
> >
> >
> > INFORMACIÓ SOBRE PROTECCIÓ DE DADES DE LA UNIVERSITAT OBERTA DE
> > CATALUNYA (UOC)
> >
> > Us informem que les vostres dades identificatives i les
> > contingudes en els missatges electrònics i fitxers adjunts es poden
> > incorporar a les nostres bases de dades amb la finalitat de gestionar les
> > relacions i comunicacions vinculades a la UOC, i que es poden conservar
> > mentre es mantingui la relació. Si ho voleu, podeu exercir el dret a
> > accedir a les vostres dades, rectificar-les i suprimir-les i altres drets
> > reconeguts normativament adreçant-vos a l'adreça de correu emissora o a
> > fuoc...@uoc.edu .
> >
> > Aquest missatge i qualsevol
> > fitxer que porti adjunt, si escau, tenen el caràcter de confidencials i
> > s'adrecen únicament a la persona o entitat a qui s'han enviat.
> >
> > Així
> > mateix, posem a la vostra disposició un delegat de protecció de dades que
> > no només s'encarregarà de supervisar tots els tractaments de dades de la
> > nostra entitat, sinó que us podrà atendre per a qualsevol qüestió
> > relacionada amb el tractament de dades. La seva adreça de contacte és
> > d...@uoc.edu .
> > INFORMACIÓN SOBRE PROTECCIÓN DE DATOS DE
> > LA UNIVERSITAT OBERTA DE CATALUNYA (UOC)
> > Os informamos de que vuestros
> > datos identificativos y los contenidos en los mensajes electrónicos y
> > ficheros adjuntos pueden incorporarse a nuestras bases de datos con el
> fin
> > de gestionar las relaciones y comunicaciones vinculadas a la UOC, y de
> que
> > pueden conservarse mientras se mantenga la relación. Si lo deseáis,
> podéis
> > ejercer el derecho a acceder a vuestros datos, rectificarlos y
> suprimirlos
> > y otros derechos reconocidos normativamente dirigiéndoos a la dirección
> de
> > correo emisora o a fuoc...@uoc.edu .
> > Este mensaje y
> > cualquier fichero que lleve adjunto, si procede, tienen el carácter de
> > confidenciales y se dirigen únicamente a la persona o entidad a quien se
> > han enviado.
> > Así mismo, ponemos a vuestra disposición a un delegado de
> > protección de datos que no solo se encargará de supervisar todos los
> > tratamientos de datos de nuestra entidad, sino que podrá atenderos para
> > cualquier cuestión relacionada con el tratamiento de datos. Su dirección
> de
> > contacto es d...@uoc.edu .
> >
> >
> > UNIVERSITAT OBERTA DE
> > CATALUNYA (UOC) DATA PROTECTION INFORMATION
> > Your personal data and the data
> > contained in your email messages and attached files may be stored in our
> > databases for the purpose of maintaining relations and communications
> > linked to the UOC, and the data may be stored for as long as these
> > relations and communications are maintained. If you so wish, you can
> > exercise your rights to access, rectification and erasure 

Re: GSoC

[Brandon Williams]

It probably seems a bit more complicated than it actually is if you
aren't familiar with the code base.  I can provide a quick high level
overview of how this ticket would be accomplished:

First, add the configuration parameter.  This would involve adding it
to o.a.c.config.Config.java[0] with a default of being disabled, and
then a getter and setter should be added to DatabaseDescriptor[1].
>From there it's a matter of having the system check this before
invoking repairs.  We can see from nodetool's repair command[2] that
this ends up calling repairAsync in StorageService[3] via JMX.

Of course the devil is always in the details (and I've glossed over
some here,) but that's what my initial plan of attack would be, and
hopefully it's enough to give you an idea of what might be involved.

If you want more interactive help, I recommend joining the
#cassandra-dev slack channel.

[0] 
https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/config/Config.java
[1] 
https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/config/DatabaseDescriptor.java
[2] 
https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/tools/nodetool/Repair.java
[3] 
https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/service/StorageService.java


On Tue, Mar 30, 2021 at 10:57 AM Isidoro Garcia Gutierrez
 wrote:
>
> Hello everyone,
> I would like to apply for the idea Global configuration parameter to reject
> repairs with anti-compaction
>  but I don't know if
> I have enough skill to do it right.
> I read that the difficulty is normal but before applying I would like to
> know a little more about this topic before making the proposal for the job.
> Can someone help me?
>
> Thanks.
>
> --
>
>
>
> INFORMACIÓ SOBRE PROTECCIÓ DE DADES DE LA UNIVERSITAT OBERTA DE
> CATALUNYA (UOC)
>
> Us informem que les vostres dades identificatives i les
> contingudes en els missatges electrònics i fitxers adjunts es poden
> incorporar a les nostres bases de dades amb la finalitat de gestionar les
> relacions i comunicacions vinculades a la UOC, i que es poden conservar
> mentre es mantingui la relació. Si ho voleu, podeu exercir el dret a
> accedir a les vostres dades, rectificar-les i suprimir-les i altres drets
> reconeguts normativament adreçant-vos a l'adreça de correu emissora o a
> fuoc...@uoc.edu .
>
> Aquest missatge i qualsevol
> fitxer que porti adjunt, si escau, tenen el caràcter de confidencials i
> s'adrecen únicament a la persona o entitat a qui s'han enviat.
>
> Així
> mateix, posem a la vostra disposició un delegat de protecció de dades que
> no només s'encarregarà de supervisar tots els tractaments de dades de la
> nostra entitat, sinó que us podrà atendre per a qualsevol qüestió
> relacionada amb el tractament de dades. La seva adreça de contacte és
> d...@uoc.edu .
> INFORMACIÓN SOBRE PROTECCIÓN DE DATOS DE
> LA UNIVERSITAT OBERTA DE CATALUNYA (UOC)
> Os informamos de que vuestros
> datos identificativos y los contenidos en los mensajes electrónicos y
> ficheros adjuntos pueden incorporarse a nuestras bases de datos con el fin
> de gestionar las relaciones y comunicaciones vinculadas a la UOC, y de que
> pueden conservarse mientras se mantenga la relación. Si lo deseáis, podéis
> ejercer el derecho a acceder a vuestros datos, rectificarlos y suprimirlos
> y otros derechos reconocidos normativamente dirigiéndoos a la dirección de
> correo emisora o a fuoc...@uoc.edu .
> Este mensaje y
> cualquier fichero que lleve adjunto, si procede, tienen el carácter de
> confidenciales y se dirigen únicamente a la persona o entidad a quien se
> han enviado.
> Así mismo, ponemos a vuestra disposición a un delegado de
> protección de datos que no solo se encargará de supervisar todos los
> tratamientos de datos de nuestra entidad, sino que podrá atenderos para
> cualquier cuestión relacionada con el tratamiento de datos. Su dirección de
> contacto es d...@uoc.edu .
>
>
> UNIVERSITAT OBERTA DE
> CATALUNYA (UOC) DATA PROTECTION INFORMATION
> Your personal data and the data
> contained in your email messages and attached files may be stored in our
> databases for the purpose of maintaining relations and communications
> linked to the UOC, and the data may be stored for as long as these
> relations and communications are maintained. If you so wish, you can
> exercise your rights to access, rectification and erasure of your data, and
> any other legally held rights, by writing to the sender’s email address or
> to fuoc...@uoc.edu .
> This message and, where
> applicable, any attachments are confidential and addressed solely to the
> individual or organization they were sent to.
> The UOC has a data protection
> officer who not only supervises the data processing carried 

GSoC

[Isidoro Garcia Gutierrez]

Hello everyone,
I would like to apply for the idea Global configuration parameter to reject
repairs with anti-compaction
 but I don't know if
I have enough skill to do it right.
I read that the difficulty is normal but before applying I would like to
know a little more about this topic before making the proposal for the job.
Can someone help me?

Thanks.

-- 



INFORMACIÓ SOBRE PROTECCIÓ DE DADES DE LA UNIVERSITAT OBERTA DE 
CATALUNYA (UOC)

Us informem que les vostres dades identificatives i les 
contingudes en els missatges electrònics i fitxers adjunts es poden 
incorporar a les nostres bases de dades amb la finalitat de gestionar les 
relacions i comunicacions vinculades a la UOC, i que es poden conservar 
mentre es mantingui la relació. Si ho voleu, podeu exercir el dret a 
accedir a les vostres dades, rectificar-les i suprimir-les i altres drets 
reconeguts normativament adreçant-vos a l'adreça de correu emissora o a 
fuoc...@uoc.edu .

Aquest missatge i qualsevol 
fitxer que porti adjunt, si escau, tenen el caràcter de confidencials i 
s'adrecen únicament a la persona o entitat a qui s'han enviat.

Així 
mateix, posem a la vostra disposició un delegat de protecció de dades que 
no només s'encarregarà de supervisar tots els tractaments de dades de la 
nostra entitat, sinó que us podrà atendre per a qualsevol qüestió 
relacionada amb el tractament de dades. La seva adreça de contacte és 
d...@uoc.edu .
INFORMACIÓN SOBRE PROTECCIÓN DE DATOS DE 
LA UNIVERSITAT OBERTA DE CATALUNYA (UOC)
Os informamos de que vuestros 
datos identificativos y los contenidos en los mensajes electrónicos y 
ficheros adjuntos pueden incorporarse a nuestras bases de datos con el fin 
de gestionar las relaciones y comunicaciones vinculadas a la UOC, y de que 
pueden conservarse mientras se mantenga la relación. Si lo deseáis, podéis 
ejercer el derecho a acceder a vuestros datos, rectificarlos y suprimirlos 
y otros derechos reconocidos normativamente dirigiéndoos a la dirección de 
correo emisora o a fuoc...@uoc.edu .
Este mensaje y 
cualquier fichero que lleve adjunto, si procede, tienen el carácter de 
confidenciales y se dirigen únicamente a la persona o entidad a quien se 
han enviado.
Así mismo, ponemos a vuestra disposición a un delegado de 
protección de datos que no solo se encargará de supervisar todos los 
tratamientos de datos de nuestra entidad, sino que podrá atenderos para 
cualquier cuestión relacionada con el tratamiento de datos. Su dirección de 
contacto es d...@uoc.edu .


UNIVERSITAT OBERTA DE 
CATALUNYA (UOC) DATA PROTECTION INFORMATION
Your personal data and the data 
contained in your email messages and attached files may be stored in our 
databases for the purpose of maintaining relations and communications 
linked to the UOC, and the data may be stored for as long as these 
relations and communications are maintained. If you so wish, you can 
exercise your rights to access, rectification and erasure of your data, and 
any other legally held rights, by writing to the sender’s email address or 
to fuoc...@uoc.edu .
This message and, where 
applicable, any attachments are confidential and addressed solely to the 
individual or organization they were sent to.
The UOC has a data protection 
officer who not only supervises the data processing carried out at the 
University, but who will also respond to any questions you may have about 
this data processing. You can contact our data protection officer by 
writing to d...@uoc.edu .

GSOC Project ideas

[Supun Kamburugamuva]

Hi all,

I would like to learn and contribute to cassandra project and would
really like to do a GSoc project in Cassandra. I'm a PHD student at
Indiana University and my research area is in Distributed Systems. I'm
also a committer to few Apache projects. Please let me know if you
have project ideas that I can look in to.

Regards,
-- 
Supun Kamburugamuva
Member, Apache Software Foundation; http://www.apache.org
E-mail: supu...@gmail.com;  Mobile: +1 812 369 6762
Blog: http://supunk.blogspot.com

Re: GSOC Project ideas

[Jonathan Ellis]

Hi Supun,

I recommend checking out the archives of this list for the roadmap
emails I sent recently.  GL!

On Thu, Mar 7, 2013 at 5:32 PM, Supun Kamburugamuva supu...@gmail.com wrote:
 Hi all,

 I would like to learn and contribute to cassandra project and would
 really like to do a GSoc project in Cassandra. I'm a PHD student at
 Indiana University and my research area is in Distributed Systems. I'm
 also a committer to few Apache projects. Please let me know if you
 have project ideas that I can look in to.

 Regards,
 --
 Supun Kamburugamuva
 Member, Apache Software Foundation; http://www.apache.org
 E-mail: supu...@gmail.com;  Mobile: +1 812 369 6762
 Blog: http://supunk.blogspot.com



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder, http://www.datastax.com
@spyced

Re: GSOC Project ideas

[Supun Kamburugamuva]

Thank you. I'll have a look.

Supun..

On Thu, Mar 7, 2013 at 4:02 PM, Jonathan Ellis jbel...@gmail.com wrote:
 Hi Supun,

 I recommend checking out the archives of this list for the roadmap
 emails I sent recently.  GL!

 On Thu, Mar 7, 2013 at 5:32 PM, Supun Kamburugamuva supu...@gmail.com wrote:
 Hi all,

 I would like to learn and contribute to cassandra project and would
 really like to do a GSoc project in Cassandra. I'm a PHD student at
 Indiana University and my research area is in Distributed Systems. I'm
 also a committer to few Apache projects. Please let me know if you
 have project ideas that I can look in to.

 Regards,
 --
 Supun Kamburugamuva
 Member, Apache Software Foundation; http://www.apache.org
 E-mail: supu...@gmail.com;  Mobile: +1 812 369 6762
 Blog: http://supunk.blogspot.com



 --
 Jonathan Ellis
 Project Chair, Apache Cassandra
 co-founder, http://www.datastax.com
 @spyced



-- 
Supun Kamburugamuva
Member, Apache Software Foundation; http://www.apache.org
E-mail: supu...@gmail.com;  Mobile: +1 812 369 6762
Blog: http://supunk.blogspot.com

Will Cassandra Propose Any Ideas for GSoC 2011?

[Zhijie Shen]

Hi developers,

I'm a graduate student from National University of Singapore, and I'm
interested in Cassandra project.  Cassandra proposed ideas in the last year.
So how about this year? I also found some of the issues proposed for last
year's GSoC are still open. Will they be valid for this year?

Regards,
Zhijie

-- 
Zhijie Shen
School of Computing
National University of Singapore
http://www.comp.nus.edu.sg/%7Ez-shen/

Re: GSOC - Cassandra

[Kishanthan]

Hi Eric,
Thanks for that quick reply,
I do have experience in coding in java.
I started studying about Thrift and Avro interface.Ill come up with any
question for which is unclear.

Thanks.

On Sat, Mar 20, 2010 at 12:02 AM, Eric Evans eev...@rackspace.com wrote:

 On Fri, 2010-03-19 at 23:17 +0530, Kishanthan wrote:
  Im an undergraduate student from University of Moratuwa, Sri Lanka.
  Im interested in participating the GSOC program for Apache-Cassandra.
  I went through the wiki page at
  http://wiki.apache.org/cassandra/GoogleSoc2010 and found some ideas
  for GSOC 2010.

 Excellent.

  I would like to know about the idea : *Finish creating an Avro
  interface alongside Thrift*
  Please give me some details on this idea on where to begin and what
  are the skills i need.

 You'll need to be able to code in Java (Cassandra is written in Java
 after all). Additionally, I think you'd need a firm understanding of the
 Thrift interface and how data is modeled in Cassandra (basically all the
 stuff you'd need to know to write applications against it).

 --
 Eric Evans
 eev...@rackspace.com




-- 
Kishanthan.T