Thanks Henrik. I will send another thread shortly with more details on how to volunteer to be a GSoC mentor as well as submit project ideas.
Em dom., 16 de jan. de 2022 às 19:13, Henrik Ingo <henrik.i...@datastax.com> escreveu: > Hi Paulo > > In my experience, it works best when the mentoring organization is clear > about who is the mentor, and what is the project each mentor will be > mentoring. > > Tomorrow is MLK day in the US, but let me talk to some people and get back > to you around Wednesday. GSoC is a great opportunity to get new > contributors to a project. I'll talk to a few people to figure out how we > could prioritize this during January. > > henrik > > On Fri, Jan 14, 2022 at 2:52 PM Paulo Motta <pauloricard...@gmail.com> > wrote: > >> Hi everyone, >> >> I'd like to follow-up on this as GSoC timeline starts soon in February >> [1]. >> >> We didn't get any project ideas tagged with the 'gsoc' label in the past >> 2 months, except Aleksandr Sorokoumov which sent me some tickets for >> offline triaging. This may indicate this model of having potential mentors >> register project ideas may not be working too well. >> >> I'd like to propose having students triage unassigned tickets and propose >> projects to potential mentors in the mailing list. >> >> We could create a blog post with a "Call for GSoC Projects" with >> instructions on how to triage tickets on JIRA and propose project ideas in >> the mailing list, and a twitter campaign pointing to the blog post. >> >> What do you think? >> >> Paulo >> >> [1] - https://developers.google.com/open-source/gsoc/timeline >> >> Em sex., 12 de nov. de 2021 às 11:30, Paulo Motta < >> pauloricard...@gmail.com> escreveu: >> >>> We made an announcement about GSoC on our twitter account (@cassandra) >>> with a call to action for potentially interested people to reach out on >>> #cassandra-dev. >>> >>> I kindly ask everyone to refer prospective GSoC contributors to LHF >>> tickets and getting started pages so they can get involved with the project >>> before the official project ideas are released. >>> >>> Also, please retweet this to get the word out: >>> https://twitter.com/cassandra/status/1459163741002645507 >>> >>> Chers, >>> >>> Paulo >>> >>> Em sex., 12 de nov. de 2021 às 08:24, Berenguer Blasi < >>> berenguerbl...@gmail.com> escreveu: >>> >>>> Agreed thx a lot. >>>> >>>> On 12/11/21 10:02, Benjamin Lerer wrote: >>>> > Thanks a lot Paulo for pushing that forward. That is a great way to >>>> grow >>>> > our community. >>>> > >>>> > Le jeu. 11 nov. 2021 à 14:32, Paulo Motta <pauloricard...@gmail.com> >>>> a >>>> > écrit : >>>> > >>>> >> Hi, >>>> >> >>>> >> The Google Summer of Code organization announced some exciting >>>> changes to >>>> >> the program next year [1]: >>>> >> (1) Starting in 2022, the program will be open to all newcomers of >>>> open >>>> >> source that are 18 years and older, no longer focusing solely on >>>> university >>>> >> students. >>>> >> (2) GSoC Contributors will be able to choose from multiple size >>>> projects >>>> >> ~175 hour (medium) and 350 hour (large). >>>> >> (3) We are building increased flexibility around the timing of >>>> projects - >>>> >> there is an option to extend the standard 12 week coding time frame >>>> to a >>>> >> maximum of 22 weeks. >>>> >> >>>> >> I wanted to take this announcement to kick-off the preparation for >>>> our >>>> >> participation in the program next year as a means of attracting and >>>> >> mentoring new contributors to our community. >>>> >> >>>> >> The earlier we attract prospective "GSoC Contributors" the higher the >>>> >> chances of a successful project and retaining the contributors after >>>> the >>>> >> program. >>>> >> >>>> >> The best GSoC project ideas are those which are self-contained: have >>>> a well >>>> >> defined scope, discreet 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 >>>> >> >>>> >> I would like to invite contributors to start tagging issues in JIRA >>>> with >>>> >> the "gsoc" tag as a means of indicating that particular task can be >>>> >> potentially turned into a GSoC project. >>>> >> >>>> >> With the large volume of CEPs being voted and approved recently, it >>>> would >>>> >> be great if a portion of the "nice-to-have" subtasks which are not a >>>> strict >>>> >> requirement of the CEP to be created with GSoC mentoring in mind. Ie. >>>> >> benchmark CEP, extend CEP with some additional but not-core >>>> functionality, >>>> >> CEP UX improvements, etc. With this in mind I'd like to ask CEP >>>> shepherds >>>> >> to create and tag these tasks with the "gsoc" tag. >>>> >> >>>> >> Please note that mentoring a GSoC project is not only a good way to >>>> attract >>>> >> new members to the community but also a great way of recruiting new >>>> members >>>> >> to your professional teams, so there's great personal, professional >>>> and >>>> >> community benefits to mentoring a GSoC project. >>>> >> >>>> >> Once we have a good amount of tasks with the "gsoc" tag I will work >>>> with >>>> >> prospective mentor to refine the tasks and create a "GSoC Project >>>> Ideas" >>>> >> page and we can write a blog post to announce the project ideas to >>>> >> prospective GSoC contributors. >>>> >> >>>> >> Please let me know what do you think. >>>> >> >>>> >> Paulo >>>> >> >>>> >> [1] >>>> >> >>>> >> >>>> https://opensource.googleblog.com/2021/11/expanding-google-summer-of-code-in-2022.html >>>> <https://urldefense.com/v3/__https://opensource.googleblog.com/2021/11/expanding-google-summer-of-code-in-2022.html__;!!PbtH5S7Ebw!d-LyAzADOf46Mk3mWpGP6v-7fdm2xlnB_dZ1K7cZACiPGSYx8e8_qeJdHvXcPXPBgJntHEvsi8uX-eGvPtsuCAyr7UE$> >>>> >> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org >>>> For additional commands, e-mail: dev-h...@cassandra.apache.org >>>> >>>> > > -- > > 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&d=DwMFaQ&c=adz96Xi0w1RHqtPMowiL2g&r=IFj3MdIKYLLXIUhYdUGB0cTzTlxyCb7_VUmICBaYilU&m=bmIfaie9O3fWJAu6lESvWj3HajV4VFwgwgVuKmxKZmE&s=16sY48_kvIb7sRQORknZrr3V8iLTfemFKbMVNZhdwgw&e=> > [image: Visit my LinkedIn profile.] > <https://www.linkedin.com/in/heingo/> >
