Python Sub-org Ideas Template
There are not very many strict requirements for Google Summer of Code Ideas pages, but
there are some things that GSoC contributors often ask us for. This page is intended as a starting
template for organizations so you don't forget those things.
Warning: In 2014, many orgs got rejected because their ideas pages were offline when
Google checked. Make sure your ideas page is hosted somewhere that Google's Open
Programs Office will be able to access when they check!
Tell the prospective contributors a bit about your organization. Here's some questions you might want to
- What software are you creating?
- Why is it interesting?
- Who uses it?
- What languages is it written in?
- How is it going to change the world?
- IRC channel:
- Mailing list(s):
- List contact methods you actually use and will have mentors monitoring!
Include any special instructions/info about communicating: e.g. what time zones are
mentors in? do you prefer it if GSoC contributors introduce themselves first or just
are there any common mistakes contributors make when making a first impression?
Links to setup instructions go here. Some suggested things to answer:
- Where is the link to a setup guide for new developers?
- Are there any unusual libraries/applications that need to be installed
- What type of source control do you use? (include links to help and
- What's the process for submitting your first bug fix?
- Where should new contributors look to find easy bugs to try out?
Writing your GSoC application
Links to advice about applications and the application template goes here.
You should usually have a couple of project ideas, ranging in difficulty
from beginner to
expert. Please do try to have at least one, preferably several beginner
tasks: GSoC gets a
lot of new contributors with minimal open source experience who feel very
sometimes even complain to Google) if orgs don't any have projects at
1. Project name
- Project description: Make sure you have a
high-level description that any new GSoC contributor can
understand, as well as deeper details
- Skills: programming languages? specific domain
- Difficulty level: Easy/Intermediate/Hard
classification (contributors ask for this info
frequently to help them narrow down their choices. Difficulty
levels are something Google
wants to see, so they aren't optional; make your best guess.)
- Related Readings/Links: was there a mailing
discussion about this topic?
standards you want new contributors to read first? bugs/feature
- Potential mentors: A list of mentors likely to
involved with this project, so
GSoC contributors know who to look for on IRC/mailing lists if they have
questions. (If you've had
trouble with GSoC contributors overwhelming specific mentors, feel free
re-iterate here if
GSoC contributors should contact the mailing list to reach all mentors.)
- Project Length: Medium size projects should take about
175 hours to complete while large projects should take about 350 hours to
complete, you should put if the project idea would be a medium or a large
2. Project name
As above. etc. Unless there's a compelling reason to sort in some
should be ordered approximately from easiest to hardest.
If you're open to other
project ideas from contributors, say so and make sure there's a clear path for
contributors to discuss ideas with mentors before submitting an application.
Otherwise, we've found that you'll get a lot of project ideas that aren't
suitable for GSoC: too small, too large, bad fit for the project, no mentors
interested in taking them on, etc. You may have an open discussion thread in
your bug tracker/forums, a chat channel or mailing list, or contact info for a
mentor who's open to discussing new ideas in private.