Difference between revisions of "Google Summer of Code"
m (fixed link to our socghop homepage) |
(copied application template over from socghop.appspot.com) |
||
| Line 51: | Line 51: | ||
or use [http://www.geeklog.net/profiles.php?uid=2&subject=Google%20Summer%20of%20Code%202010 this web form]. This is a private mailing list which is read only by the GSoC mentors. | or use [http://www.geeklog.net/profiles.php?uid=2&subject=Google%20Summer%20of%20Code%202010 this web form]. This is a private mailing list which is read only by the GSoC mentors. | ||
| − | + | ||
| + | == Application Template == | ||
| + | |||
| + | When applying for a project with Geeklog (applications for students open on '''March 29'''), please use this application template, i.e. please answer the following questions. | ||
| + | |||
| + | * Please tell us something about yourself (experience, interests, why you are applying for this project). | ||
| + | * Please include contact information (an email address, at the very least), as we won't have access to the contact information that you entered as part of your application. | ||
| + | * Please explain, in your own words, what the project is about and what the goals are. | ||
| + | * Then, please provide a (rough) schedule for your project: The order in which you plan to implement features and an estimate how long it will take and when they will be finished. Don't forget to factor some time for tests and documentation into your plans. | ||
| + | * If there are any periods during the Summer where you will not be able to work on your project (e.g. due to exams or planned vacations), then please also include this information. | ||
| + | * We would like to ask GSoC applicants to submit a patch for Geeklog as part of your application. You can find our project tracker here: http://project.geeklog.net/tracking/. Try looking for issues that are tagged "[http://project.geeklog.net/tracking/search.php?hide_status_id=90&tag_string=beginner beginner]" (but feel free to tackle any other issue). This will give us an opportunity to see your coding skills in practice. | ||
| + | |||
| + | Thank you! | ||
Revision as of 19:34, 27 March 2010
Contents
What is it?
Project Ideas
This is a list of ideas for projects that we feel would add useful functionality to Geeklog:
- Social Networking Support (SocNet)
- New Calendar Plugin
- Add Support for Dynamic Feeds with Access Control
- Improve the Configuration GUI
- New modules for our Spam filter
- Cross Site Alerting and Publication API
- Core Notification Service
- more (mostly unfinished) ideas: GSoC Brainstorming (for your inspiration)
We are also willing to accept new ideas from students. In that case, please check that what you're proposing is not already available (e.g. with some existing add-on) or has been rejected in the past.
Notes for Students
We have collected some information for students here. Please take a moment to read them. Thanks.
Recommended reading
Google provides an extensive FAQ. There's also a very informative Advice for Students page. We recommend reading those first.
Required skills
Students interested in any of the above projects should have reasonable experience with PHP and some basic SQL knowledge. Being able to set up your own LAMP server (Linux, Apache, MySQL, PHP) would probably help but isn't a prerequisite.
Geeklog uses Mercurial for revision control (aka version control aka source code management). Students should have a basic grasp of revision control - we can help you with the specifics of Using Mercurial.
What we expect from our students during the course of the Summer.
Background information
Geeklog (current version: 1.6.1) is the software you may have seen running websites such as Groklaw.
Contact
We suggest that you join our Development Mailing List, introduce yourself and the project(s) you are interested in. This list is the best place for any questions or discussions related to the projects and their development.
Or you can hop on our IRC channel, #geeklog at irc.freenode.net and talk to us directly (some patience required - not everyone may be online there all the time).
If you need a more private communication channel, you can also email us at
- contact-us(AT)lists.geeklog.net
or use this web form. This is a private mailing list which is read only by the GSoC mentors.
Application Template
When applying for a project with Geeklog (applications for students open on March 29), please use this application template, i.e. please answer the following questions.
- Please tell us something about yourself (experience, interests, why you are applying for this project).
- Please include contact information (an email address, at the very least), as we won't have access to the contact information that you entered as part of your application.
- Please explain, in your own words, what the project is about and what the goals are.
- Then, please provide a (rough) schedule for your project: The order in which you plan to implement features and an estimate how long it will take and when they will be finished. Don't forget to factor some time for tests and documentation into your plans.
- If there are any periods during the Summer where you will not be able to work on your project (e.g. due to exams or planned vacations), then please also include this information.
- We would like to ask GSoC applicants to submit a patch for Geeklog as part of your application. You can find our project tracker here: http://project.geeklog.net/tracking/. Try looking for issues that are tagged "beginner" (but feel free to tackle any other issue). This will give us an opportunity to see your coding skills in practice.
Thank you!
Further Reading
- Getting Started with Geeklog development
- The Summer of Code topic on geeklog.net provides coverage of our previous participation in the Google Summer of Code.
