[GRASS-dev] GSoC 2017 - SOS tools

Ondřej Pešek pesej.ondrek at gmail.com
Thu Mar 30 15:33:45 PDT 2017


Hi Massimo,

2017-03-30 14:50 GMT+02:00 massimo di stefano <massimodisasha at gmail.com>:
> Hi Ondrej,
> what about working on your gsoc 2016 idea?
>
> I guess we all want the GSOC be an “instrument” to involve students in the
> project they chose and “hopefully” have them continuing what they started …
> IMHO this “continuation” is very important and is a clear sign of how much
> the student cares about to the project itself.
>
> I’ve had bad experience with gsoc, I know the students are not obligated in
> continuing to contribute to the project after the GSOC period .. but I think
> that’s what we hope.
> It is a very bad feeling when a mentor spent the whole summer following a
> student which then literally disappear after the application period
>

Of course, I would like to continue in my 2016 GSoC project, but there
is a problem with my internship at the Norwegian Institute for Nature
Research (NINA), as mentioned in my proposal. I'm afraid that I won't
be able to handle working on two completely different projects.

But in NINA, I will be working on sensor data, especially with istSOS.
I (and potential co-mentors) can see quite significant overlap, so I
expect synergies and mutual benefits.

But my last year project is not dead, it's just... hmmm...
hibernating. I have done some small changes in November and I still
have some notes with what I would like to improve. The nearest
improvement is creating module from those scripts - I'm just playing
with pyGrass, so I hope that I have some time before the start of this
year project (or before my NINA internship, if not accepted).
Another nice goal should be using this code to GRASS plugin for QGIS,
because QGIS has PyQt based GUI, but it's the future.

> for your idea i can see the following improvements:
> - porting to qt5
> - porting to py3 (only task.py need some twiking)
> - complete the modules, I tried it and I found it incomplete.
>

Yes, I'm planning also py3. But I didn't contemplated about qt5, I
have to study it first.
Please, feel free to create an issue on the github page [1]. I welcome
your comments and opinions.

>
> Massimo.
>
>

[1] https://github.com/pesekon2/GRASS-Qt-based-GUI/issues

Ondrej<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /> <table
style="border-top: 1px solid #D3D4DE;">
	<tr>
      <td style="width: 55px; padding-top: 18px;"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail"
target="_blank"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"
width="46" height="29" style="width: 46px; height: 29px;" /></a></td>
		<td style="width: 470px; padding-top: 17px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica, sans-serif;
line-height: 18px;">Bez virů. <a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail"
target="_blank" style="color: #4453ea;">www.avast.com</a> 		</td>
	</tr>
</table>
<a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div>


More information about the grass-dev mailing list