| Version 1 (modified by , 6 years ago) ( diff ) |
|---|
@
@
GRASS Google Summer of Code 2018
Table of Contents
About
Ideas
Post your ideas here or to the grass-dev mailing list if you want to discuss them more. To edit this wiki, you need to login with an OSGeo Userid; read also some help for using trac.
If you are a student you can suggest an new idea or pick up an existing one in any case write about it to grass-dev mailing list.
You are invited as well to have a close look at (and re-suggest!) ideas from previous years (2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018) which have not yet been implemented. You can also look at accepted GRASS GSoC projects from previous years for an idea of scope.
Include "GRASS GIS" in the title of our idea to easily distinguish ideas and projects inside OSGeo.
Some bigger ideas may have their own pages, so you can link them here. The pages can be either independent if the page already exists (e.g. wxGUIDevelopment/SingleWindow), or more preferably subpages of this page if the idea is (re-)developed for this GSoC. In the later case, use the word "idea" in the page name to distinguish the idea page (e.g. GSoC/2017/CoolGRASSProjectIdea) from the possible student project page (e.g. GSoC/2017/CoolGRASSProject).
Title of idea
Description here
- Requirements:
- Mentor:
- Rating:
- Expected Outcomes:
- Test of skills:
- Other:
Tips for students
- If you have your own ideas we encourage you to propose them. Explain them on the grass-dev mailing list.
- If you like some idea here or from previous yeas, write about it on grass-dev mailing list and any ideas of your own which could improve it.
- Follow some good practices in your ideas and proposals:
- Stress why the project would be useful.
- Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
- Be specific in the implementation (or at least as specific as you can).
- Explain what the final product will look like and how it will work. Perhaps you can add some drawings or mock-ups. (here in a wiki page)
- Explain how the idea relates to existing GRASS GIS functions, features, and needs.
- Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
- Compile GRASS GIS 7 (trunk) from source and prepare environment for development:
- See links appropriate for you at http://grass.osgeo.org/development/how-to-start/.
- If you get stuck with the setup, feel free to consult the grass-user mailing list.
- Familiarize yourself with wiki:Submitting rules.
- Prove your worth by being active on the GRASS mailing lists (grass-user, grass-dev), fix some bugs, and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. You should start even before you apply to GSoC.
- Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.
- Every year GRASS GIS hopes to participate and participates in GSoC as part of the OSGeo Foundation's GSoC program umbrella. See the official OSGeo template for application details and other important information at the OSGeo GSoc Ideas page.
