[GRASS-PSC] Sharing the workload (was: Chair motion)

[Markus Neteler]

On 12/9/06, Hamish <hamish_nospam at yahoo.com> wrote:
...
> WRT Markus's work load:
>
> Sheparding in new modules etc takes a very strong knowledge of the code,
> history, good C, the GRASS libraries, etc. (eg what's in the other 300+
> modules and countless former GRASS 4/5 modules) This ends up being a
> very short list of people to draw from. It, along with auditing
> modifications to the libraries, is probably the most important task in
> the project IMO. Maybe Frank can relate some GDAL/PROJ wisdom here.
>
> To help spread the load, hopefully other devels can adopt a handful of
> modules each (ie the ones they use/know about), and act as liaisons for
> the modules' external developers.

This would be pretty helpful.

> On the other hand, (from my uninformed position) committing new
> translations seems like something that any of us could do and not
> requiring the breadth of experience. If that is so, maybe we could move
> that job to someone else as an easy way to lessen what we ask of Markus.
> (perhaps a european type who speaks lots of languages :)
> Or maybe he enjoys that job?

Most jobs in the GRASS project are nice but life time is limited and
payed work (employer) has to be done as well.

> Same goes for the website, lots of people can help there. I think the
> wiki is helping.
>
> Markus: It would help if you could make a list of jobs you'd rather were
> passed on to others?

Here we go:
http://grass.gdf-hannover.de/wiki/Project_jobs

Feel free to extend and clarify or to add more job descriptions.

Markus