| | 167 | === Add {your research idea} to GRASS GIS === |
| | 168 | |
| | 169 | * In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS GIS. |
| | 170 | * Requirements: |
| | 171 | * Language: |
| | 172 | * Depends on the project, often Python, sometimes C. |
| | 173 | * Adding your latest ecological analysis |
| | 174 | * Proposal: |
| | 175 | * Discuss relevance to GRASS GIS. |
| | 176 | * Describe technical steps needed for integration. |
| | 177 | * Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why. |
| | 178 | * Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer. |
| | 179 | * Specify who will provide the research expertise. |
| | 180 | * Mentors: |
| | 181 | * GRASS GIS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves. |
| | 182 | * Possible technical mentors: Vaclav Petras, Anna Petrasova |
| | 183 | * Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed). |
| | 184 | * Proposed by: Vaclav Petras |
| | 185 | * Test and training tasks: |
| | 186 | * Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository. |
