From: Daniele Nicolodi <firstname.lastname@example.org> To: email@example.com Subject: Re: Google SoC organisation application Date: Tue, 2 Feb 2021 12:58:40 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On 02/02/2021 10:54, TEC wrote: > Hello All, > > Google's SoC organisation applications are currently open, and close on > <2020-02-20>. I know that Org participated once, in 2012. > > Would it be a good idea to submit an application to do so again? > With the rise in interest in computational notebooks, blogging tools, > and other features that Org possesses I'd imagine we have a decent shot. Applying only makes sense if there are concrete ideas about projects suitable for GSoC participants and if only if there are Org contributors that can work as mentors. Suitable projects should be of the right level of complexity for the students to have a chance to have them implemented in the allotted time, which this year is not much, and have a clear design approved by the Org maintainers, so that most of the time available to the students will not be spent discussing it. Do you have any idea about suitable projects? However, I I think the availability of mentors can be the hardest requirement. I think that it would not be fair for the students if the code they would produce does not have good chances to entering the code base in a timely fashion. Thus, mentors (or, at least, co-mentors) should be among the Org maintainers. Is anyone available? Please understand that the GSoC is not a way to get labor for the project sponsored by Google: it is very likely that the time investment required to the mentors would be more than enough to implement what the students will do during the GSoC. The GSoC is more an opportunity to form a possible future long term contributor to the project. Cheers, Dan
next prev parent reply other threads:[~2021-02-02 11:59 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-02 9:54 TEC 2021-02-02 11:34 ` Jose E. Marchesi 2021-02-02 11:50 ` TEC 2021-02-02 12:12 ` Jose E. Marchesi 2021-02-02 11:58 ` Daniele Nicolodi [this message] 2021-02-02 12:00 ` TEC
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Google SoC organisation application' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).