[GRASS-dev] [OSGeo-Discuss] OSGeo Google Summer of Code 2014 - ideas needed!

neteler · February 7, 2014, 10:30am

FYI

Please modify the (trac) Wiki!
https://trac.osgeo.org/grass/wiki/GSoC/2014

thanks
Markus

---------- Forwarded message ----------
From: Anne Ghisla <a.ghisla@gmail.com>
Date: Thu, Feb 6, 2014 at 10:34 PM
Subject: [OSGeo-Discuss] OSGeo Google Summer of Code 2014 - ideas needed!
To: OSGeo Google Summer of Code list <soc@lists.osgeo.org>, OSGeo
Discuss list <discuss@lists.osgeo.org>, OSGeo Education List
<edu_discuss@lists.osgeo.org>, ICA OSGeo Labs list
<ica-osgeo-labs@lists.osgeo.org>, OSGeo Local Chapters
<local-chapters@lists.osgeo.org>

Hello all, and sorry for cross posting,

this year, Google Summer of Code starts earlier than usual: the
applications for mentoring organisations are already open, and will
close on February 14th.

For who is new to Summer of Code, it is a global program that offers
students stipends to write code for open source projects. See more at
http://www.google-melange.com/gsoc/homepage/google/gsoc2014

OSGeo is going to apply for GSoC 2014, and the first task is to set up
Ideas pages for all projects, before February, 14th. It is a little
more than a week!

The Ideas page is being built here, and shall contain links to all
the geospatial projects involved:
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2014_Ideas
The links from past year are commented in the wiki page. If you have
trouble editing the wiki let me or Hamish know.

I encourage developers, teachers and students to start working on ideas
for GSoC and populate the Ideas pages of the related project.
Please forward this mail, or the link to OSGeo GSoC wiki pages, to all
the interested people and projects.

If you have questions, please send a mail to the dedicated mailing list
soc@lists.osgeo.org .

Thanks everyone in advance for your contribution to the Ideas pages -
let's do our best to get OSGeo accepted in GSoC 2014!

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2014

Best regards,

Anne and Hamish
OSGeo GSoC Admins

_______________________________________________
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

wenzeslaus · February 7, 2014, 8:30pm

Hi,

in past days I added several ideas from mailing list, derived from previous years or my own. I tried to make one idea in the way that it can be turned into a GSoC proposal/application and I tried to avoid long unordered todo lists which were at some older pages.

Here is the current list of ideas:

Metadata for GRASS GIS maps and datasets
Compiling GRASS GIS on Android
Testing framework for GRASS GIS
Vector legend for GRASS GIS
Visualization of large point clouds in 3D in GRASS GIS wxGUI
Color table management GRASS GIS wxGUI
Path sampling library for GRASS
GRASS GIS locations created from public data
GRASS GIS raster attribute tables

http://trac.osgeo.org/grass/wiki/GSoC/2014

Vaclav

···

On Fri, Feb 7, 2014 at 5:30 AM, Markus Neteler <neteler@osgeo.org> wrote:

FYI

Please modify the (trac) Wiki!
https://trac.osgeo.org/grass/wiki/GSoC/2014

thanks
Markus

---------- Forwarded message ----------
From: Anne Ghisla <a.ghisla@gmail.com>
Date: Thu, Feb 6, 2014 at 10:34 PM
Subject: [OSGeo-Discuss] OSGeo Google Summer of Code 2014 - ideas needed!
To: OSGeo Google Summer of Code list <soc@lists.osgeo.org>, OSGeo
Discuss list <discuss@lists.osgeo.org>, OSGeo Education List
<edu_discuss@lists.osgeo.org>, ICA OSGeo Labs list
<ica-osgeo-labs@lists.osgeo.org>, OSGeo Local Chapters
<local-chapters@lists.osgeo.org>

Hello all, and sorry for cross posting,

this year, Google Summer of Code starts earlier than usual: the
applications for mentoring organisations are already open, and will
close on February 14th.

For who is new to Summer of Code, it is a global program that offers
students stipends to write code for open source projects. See more at
http://www.google-melange.com/gsoc/homepage/google/gsoc2014

OSGeo is going to apply for GSoC 2014, and the first task is to set up
Ideas pages for all projects, before February, 14th. It is a little
more than a week!

The Ideas page is being built here, and shall contain links to all
the geospatial projects involved:
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2014_Ideas
The links from past year are commented in the wiki page. If you have
trouble editing the wiki let me or Hamish know.

I encourage developers, teachers and students to start working on ideas
for GSoC and populate the Ideas pages of the related project.
Please forward this mail, or the link to OSGeo GSoC wiki pages, to all
the interested people and projects.

If you have questions, please send a mail to the dedicated mailing list
soc@lists.osgeo.org .

Thanks everyone in advance for your contribution to the Ideas pages -
let’s do our best to get OSGeo accepted in GSoC 2014!

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2014

Best regards,

Anne and Hamish
OSGeo GSoC Admins

Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

martinl · February 7, 2014, 8:52pm

Hi Vaclav,

2014-02-07 21:30 GMT+01:00 Vaclav Petras <wenzeslaus@gmail.com>:

Here is the current list of ideas:

Metadata for GRASS GIS maps and datasets
Compiling GRASS GIS on Android
Testing framework for GRASS GIS
Vector legend for GRASS GIS
Visualization of large point clouds in 3D in GRASS GIS wxGUI
Color table management GRASS GIS wxGUI
Path sampling library for GRASS
GRASS GIS locations created from public data
GRASS GIS raster attribute tables

thanks for hard work collecting the ideas. Dear members of this ML,
feel free to add new ideas if you miss anything...

Martin

Hamish · February 8, 2014, 3:32am

Martin wrote:

thanks for hard work collecting the ideas.

agreed! thank you Vaclav (and Helena and Yann).

We have about one week before our ideas pages are reviewed by Google and they decide if they want to accept us as an org again or not, so everything must be ready by then.

a "willing to mentor: <name1>, <name2>" at the end of each idea is important for demonstrating interest from the dev pool.

my personal wish is again for a project to add SVG support to the d.* system and ps.map. In thinking about what projects to do, I'd be careful and reserve deep structural or architectural projects for existing student-devs with a deep knowledge of the code and existing community buy-in/flameproof clothing, and have new users to grass work on stand-alone modules or gui tools in the sandbox or addons svn.

thanks,
Hamish

wenzeslaus · February 8, 2014, 4:04am

On Fri, Feb 7, 2014 at 10:32 PM, Hamish <hamish_b@yahoo.com> wrote:

Martin wrote:

> thanks for hard work collecting the ideas.

agreed! thank you Vaclav (and Helena and Yann).

We have about one week before our ideas pages are reviewed by Google and
they decide if they want to accept us as an org again or not, so everything
must be ready by then.

a "willing to mentor: <name1>, <name2>" at the end of each idea is
important for demonstrating interest from the dev pool.

I just suggested only "Mentor" and not "Willing to mentor", I would say

that at the end, they mean the same.

my personal wish is again for a project to add SVG support to the d.*
system and ps.map.

This definitively sounds useful. I still don't understand why cairo does
not solve it for d.* system. As for the GSoC idea, you should be more
specific about relation to ps.map and which advantages it would have over
ps to pdf conversion (which is done g.gui.psmap) and than something like
pdf2svg tool (cleanness?).

In thinking about what projects to do, I'd be careful and reserve deep

structural or architectural projects for existing student-devs with a deep
knowledge of the code and existing community buy-in/flameproof clothing,
and have new users to grass work on stand-alone modules or gui tools in the
sandbox or addons svn.

I specified in "Requirements on student" bullet of "Metadata for GRASS GIS
maps and datasets" and "GRASS GIS locations created from public data"
that they are for suitable for experienced GRASSers.

Perhaps also "Compiling GRASS GIS on Android" falls into this category.

Vaclav

thanks,

Hamish

Hamish · February 8, 2014, 5:07am

Vaclav wrote:

This definitively sounds useful. I still don't understand why cairo
does not solve it for d.* system. As for the GSoC idea, you should
be more specific about relation to ps.map and which advantages it
would have over ps to pdf conversion (which is done g.gui.psmap)
and than something like pdf2svg tool (cleanness?).

the idea is to allow the user to import SVG graphics to use as icons and decorations within GRASS cartography, in a similar manner to how eps files can be used in ps.map already.

I didn't mean about SVG output, which as you mention the cairo driver and ps2{foo} tools (e.g. inkscape from the command line) can theoretically do.

wrt student experience & the Android + meta-data systems, I wouldn't totally rule out students who bring other talents to the table but have no previous experience with GRASS, or make it sound so hard that
a good student decides not to apply. I'm sure it will work itself out, I just don't want to put a new student in a rough
position.

cheers,
Hamish

wenzeslaus · February 8, 2014, 5:21am

On Fri, Feb 7, 2014 at 11:04 PM, Vaclav Petras <wenzeslaus@gmail.com> wrote:

I specified in "Requirements on student" bullet of "Metadata for GRASS GIS
maps and datasets" and "GRASS GIS locations created from public data"
that they are for suitable for experienced GRASSers.

Oh, I meant non-experienced GRASSers. See the wiki page.

On Sat, Feb 8, 2014 at 12:07 AM, Hamish <hamish_b@yahoo.com> wrote:

wrt student experience & the Android + meta-data systems, I wouldn't
totally rule out students who bring other talents to the table but have no
previous experience with GRASS, or make it sound so hard that
a good student decides not to apply.

I hope that it is not how my requirements sound, if so, feel free to change
it (e.g. to No GRASS knowledge needed).

Hamish · February 13, 2014, 11:04am

Hi all,

Thanks for making the GRASS GSoC ideas page come to life.
It bodes well. Further tips about what is being looked for
in the ideas pages:

http://en.flossmanuals.net/GSoCMentoring/making-your-ideas-page/

Remember that Google will assess our application in large part
on the ideas page(s), and that review will happen early next week.

thanks,
Hamish