[gdal-dev] GSOC 2016

[Dmitry Baryshnikov]

Hello GSoC students!

Many of you wrote to different lists and directly for me. I tried to 
systematize your questions.

1. First of all each student need to subscribe to soc at lists.osgeo.org 
(the themes connected with organizing moments) and 
gdal-dev at lists.osgeo.org (the themes about ideas, tickets, coding and 
community). Please don't flood both lists the same letters.

2. Next - I dig the GDAL tracker and found some tickets worth to be 
fixed. This work help you to understand the project structure and how it 
works (building, testing and so on) and help project to became better.
The expected result is applied pool request in GDAL main repository at 
github (https://github.com/OSGeo/gdal).
By the way, after pool request to this repository, the provided fixes 
are tested via TravisC and over test utilities.
Before making pool request please test it yourself (ubuntu and windows 
is enough, virtualbox or preferable virtualization soft may help here).
Here is the tickets I think is good for you (it's welcome if community 
fix this list - maybe some tickets need to be excluded or some included):

- https://trac.osgeo.org/gdal/ticket/2773
- https://trac.osgeo.org/gdal/ticket/5035 - Alex
- https://trac.osgeo.org/gdal/ticket/5347
- https://trac.osgeo.org/gdal/ticket/5592
- https://trac.osgeo.org/gdal/ticket/5681
- https://trac.osgeo.org/gdal/ticket/5705
- https://trac.osgeo.org/gdal/ticket/6185 - Tanuj
- https://trac.osgeo.org/gdal/ticket/6222
- https://trac.osgeo.org/gdal/ticket/6246
- https://trac.osgeo.org/gdal/ticket/6304
- https://trac.osgeo.org/gdal/ticket/6316
- https://trac.osgeo.org/gdal/ticket/6385

I checked tickets already get by students. It's good to discuss with 
community how you plan to fix the tickets before start coding. Also, 
choose tickets carefully, we need students with good skills, so the 
ticket should show your potential. Some of you already choose another 
tickets, and this is normal too, but they need to be discussed too. For 
example the ticket https://trac.osgeo.org/gdal/ticket/6294 is rather 
controversial.

3. We need to see which ideas each of student choose, and what is a plan 
how to release them. You need some discussion with the community what is 
best way or some directions to do it. This is not spoil of the time as 
your ideas come as background for your project announces.

It'll be nice have more details for some ideas from list 
https://trac.osgeo.org/gdal/wiki/SummerOfCode. The ideas #7,8,9 are very 
briefly.

-- 
Best regards,
     Dmitry