From: Anthony Sorace <email@example.com> To: 9fans <firstname.lastname@example.org>, inferno-os <email@example.com> Subject: [9fans] Plan 9 applying to GSoC Date: Fri, 18 Feb 2022 12:03:26 -0800 [thread overview] Message-ID: <33881A44-3016-432E-AA81-54ED41E32000@9srv.net> (raw) Plan 9 is applying to GSoC again! The application period closes on Monday, and our formal application is in. As is the case every year, the most critical part of an application is the org's ideas page. We'd love additional fleshed-out contributions for that. Since we had a little confusion on this last year, please note that we're looking specifically for well-developed ideas that would be good summer-sized projects for new contributors, from folks willing to mentor those projects (rather than "it'd be neat if someone would do X"); see the existing ideas page for examples (some of which are more developed than others, certainly!). If you're interested in mentoring, please let me know! Bringing your own project idea is great, but we can also use more experienced, eager folks to pair up with new contributors on other projects. We've got an overview page, and all the program details are on Google's GSoC page, and you might be interested in the program timeline in particular. One other note, for those of you who're familiar with the program, there are a few notable changes, which Google goes into in a post about them. In brief, though: - The program is now open to a lot more than just formal students - There are two project sizes: large ("traditional") and medium (like last year's) - The timing of the work is more flexible. I think these are all great (even if they make a little more work for admins and mentors!) and should be nice additions to the program. Your friendly neighborhood org admin, Anthony  https://p9f.org/wiki/gsoc-2022-ideas/index.html  http://p9f.org/wiki/gsoc/index.html  https://summerofcode.withgoogle.com  https://developers.google.com/open-source/gsoc/timeline  https://opensource.googleblog.com/2021/11/expanding-google-summer-of-code-in-2022.html ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Td4449edc4863e16e-M45b7473d430aea7c8b74b8ab Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next reply other threads:[~2022-02-18 20:04 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-18 20:03 Anthony Sorace [this message] 2022-02-18 22:43 ` [9fans] " adventuresin9 2022-02-19 0:19 ` hiro 2022-02-19 3:56 ` adventuresin9 2022-02-19 10:21 ` [9fans] " Lucio De Re 2022-02-19 11:00 ` sirjofri 2022-02-19 16:16 ` [9fans] " cigar562hfsp952fans 2022-02-19 17:18 ` Marshall Conover 2022-02-19 18:06 ` [9fans] Omero/UI filesystem (was: Plan 9 applying to GSoC) sirjofri 2022-02-20 17:45 ` [9fans] Plan 9 applying to GSoC ori 2022-02-19 19:33 Bakul Shah 2022-02-19 20:01 ` ori
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=33881A44-3016-432E-AA81-54ED41E32000@9srv.net \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [9fans] Plan 9 applying to GSoC' \ /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
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 NNTP newsgroup(s).