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 <pauloricard...@gmail.com> 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 <pauloricard...@gmail.com> 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 <pauloricard...@gmail.com> >>>> 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 <pa...@apache.org> >>>>> 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 >>>> >>>> >> >> >> >> -- >> >> Henrik Ingo >> >> +358 40 569 7354 >> >>
