Google Summer of Code 2010 Ideas

From OSGeo
Revision as of 13:45, 7 March 2010 by Wiki-Wolf (talk | contribs) (→‎The ideas pages: Removed all projects with no GSoC 2010 Ideas page)
Jump to navigation Jump to search
Google soc 2010 logo.jpg

OSGeo Google Summer of Code 2010

  • PRELIMINARY - WE HAVEN'T EVEN APPLIED TO BE IN THE PROGRAM YET THIS YEAR

The Open Source Geospatial Foundation would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.

These ideas are *only* to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.

If you need more information on how to apply you can contact all the mentoring organisations via soc at lists.osgeo.org

What to expect during the summer?

Be prepared to be in constant communication with your mentors and project

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to intergrate you into the developer community, so you should get involved from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you, in case of problems.

Weekly reports

Yes, every week we expect to see a report posted to the soc@osgeo mailing list that at least answers the following questions:

  1. What did you get done this week?
  2. What do you plan on doing next week?
  3. Are you blocked on anything?

If you want, feel free to write *more*. But three sentences is the bare minimum. *IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME*, if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you in IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's cool. We have all studied at some point, just tell us about it, be honest. If you don't know how to proceed and your mentor isn't answering *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

Last year this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

Wiki page and blogs

In addition to weekly reports we ask you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info. Wiki or blog space can be provided by OSGeo if your project doesn't have anything already set up for this.


Timeline

http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline

  • March 18th 2010: Google announces accepted organizations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
  • April 9th 2010: Student application deadline. The earlier you start the more probable it is that you will be accepted! There is two way feedback during the application process which really helps you improve and clarify your application before this final deadline.
  • April 26th 2010: Accepted student proposals are announced.
  • May 24th 2010: Coding begins!
  • July 12-16th: Mid-term evaluation.
  • August 9th: Pencils down!

The ideas pages

Each participating project's list of ideas is here, with a short description of the project and what type of students would be interested in it:

  • GDAL SoC Ideas: GDAL is the Geographic Data Abstraction Library, a library which provides access to spatial data in all kinds of formats via a uniform API.
  • GRASS SoC Ideas: GRASS GIS is an open source GIS focusing mainly on analysis. It is written as a collection of stand-alone C programs and has a new GUI written in Python. If you know Python, or want to implement algorithms in C take a look!
  • Mapbender SoC ideas 2010: Mapbender is a server and client side geographic data management tool, programmed in PHP and JavaScript, using the jQuery library.
  • Quantum GIS SoC Ideas Quantum GIS (QGIS) is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats.
  • uDig SoC 2009: User-friendly Desktop GIS is a Java application written with the Eclipse RCP framework. The project has a community svn area to host student plug-ins, tutorials cover how to package up a custom application to show off your work.
  • OpenJUMP/deegree Ideas List: deegree and OpenJUMP share code derived from the original JUMP. Both programs maintain separate development lists and source code repositories but look for opportunities to collaborate.

What is the main public mailing list for your organization?

Since OSGeo is an umbrella organisation for multiple projects, each project has their own discussion and development mailing lists.

Main OSGeo mailing lists of interest to students.

Please start here, when contacting us for the first time with questions about Google Summer of Code.

Also see the Mailing Lists page for project specific lists.

What is the main IRC channel for your organization?

irc://irc.freenode.net/#osgeo (Web based IRC client)

Project irc channels:

Retrieved from "http://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2010_Ideas&oldid=45962"