Sharing the workload (was: Chair motion)

[Markus Neteler-2]

On 12/9/06, Hamish <[hidden email]> 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

[HamishB]

Markus Neteler wrote:
> Here we go:
> http://grass.gdf-hannover.de/wiki/Project_jobs
>
> Feel free to extend and clarify or to add more job descriptions.

Shall we advertize for a graphic artist? e.g. for fancy GUI icons.


Hamish

[Markus Neteler-3]

On Mon, Dec 11, 2006 at 11:45:14PM +1300, Hamish wrote:
> Markus Neteler wrote:
> > Here we go:
> > http://grass.gdf-hannover.de/wiki/Project_jobs
> >
> > Feel free to extend and clarify or to add more job descriptions.
>
> Shall we advertize for a graphic artist? e.g. for fancy GUI icons.

Yes, please add this if you have time.
I already got the first interested person for one of the jobs!
For that I have started a list of interested people at bottom.

Markus

[Michael Barton]

On 12/11/06 3:45 AM, "Hamish" <[hidden email]> wrote:

> Markus Neteler wrote:
>> Here we go:
>> http://grass.gdf-hannover.de/wiki/Project_jobs
>>
>> Feel free to extend and clarify or to add more job descriptions.
>
> Shall we advertize for a graphic artist? e.g. for fancy GUI icons.
>
>
> Hamish
>
> _______________________________________________
> grass-psc mailing list
> [hidden email]
> http://grass.itc.it/mailman/listinfo/grass-psc

That would be great.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University

phone: [phone]
fax: [phone]
www: http://www.public.asu.edu/~cmbarton 

[Brad Douglas]

On Sat, 2006-12-09 at 14:27 +0100, Markus Neteler wrote:

> On 12/9/06, Hamish <[hidden email]> 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.

Excuses, excuses... ;-)

> > 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.

This is an excellent idea.  Would it be reasonable to add positions for
maintaining various parts of GRASS?  Someone to review code submissions
in a particular area (ie. raster, vector, imagery, database -- so four
separate, but similar positions)?  I'm not sure how useful it would be
at this point, but I thought I would suggest it.

Will this document be posted to the users and developer lists when
ratified?

I can co-habit the PR position.  I lack some of the fundamental skills
and time the position requires (ie. multi-lingual) so I can't handle it
alone at this early stage.


--
Brad Douglas <rez touchofmadness com>                    KB8UYR/6
Address: 37.493,-121.924 / WGS84    National Map Corps #TNMC-3785

[HamishB]

Markus Neteler wrote:

> On Mon, Dec 11, 2006 at 11:45:14PM +1300, Hamish wrote:
> > Markus Neteler wrote:
> > > Here we go:
> > > http://grass.gdf-hannover.de/wiki/Project_jobs
> > >
> > > Feel free to extend and clarify or to add more job descriptions.
> >
> > Shall we advertize for a graphic artist? e.g. for fancy GUI icons.
>
> Yes, please add this if you have time.

done.

> I already got the first interested person for one of the jobs!
> For that I have started a list of interested people at bottom.


should we add existing jobs already filled to the bottom of that page,
as a means of FYI, credit, guilt?

* bug tracker maintainer
* next-gen gui devel lead
* newsletter editor
* cvs maintainer
etc


Hamish

[Markus Neteler-3]

On Wed, Dec 13, 2006 at 06:54:59PM +1300, Hamish wrote:
> Markus Neteler wrote:
> > On Mon, Dec 11, 2006 at 11:45:14PM +1300, Hamish wrote:
> > > Markus Neteler wrote:
> > > > Here we go:
> > > > http://grass.gdf-hannover.de/wiki/Project_jobs
...
> should we add existing jobs already filled to the bottom of that page,
> as a means of FYI, credit, guilt?
>
> * bug tracker maintainer
> * next-gen gui devel lead
> * newsletter editor
> * cvs maintainer
> etc

Done. But please extend/prettify...

Markus

[Markus Neteler-3]

On Wed, Dec 13, 2006 at 04:57:09AM +0000, Brad Douglas wrote:
> On Sat, 2006-12-09 at 14:27 +0100, Markus Neteler wrote:
...

> > Here we go:
> > http://grass.gdf-hannover.de/wiki/Project_jobs
> >
> > Feel free to extend and clarify or to add more job descriptions.
>
> This is an excellent idea.  Would it be reasonable to add positions for
> maintaining various parts of GRASS?  Someone to review code submissions
> in a particular area (ie. raster, vector, imagery, database -- so four
> separate, but similar positions)?  I'm not sure how useful it would be
> at this point, but I thought I would suggest it.

I was recently giving a talk about
"Community based software development: The GRASS GIS project"
http://mpa.itc.it/markus/unitn2006/

where I talked about "code habitats". This is going into the
same direction, I think that we could try to describe that
(on a separate Wiki page maybe). Of course the related people
must agree to that to become sentinel for their area. It
already works like that, only that newcomers don't know about
it.
 
> Will this document be posted to the users and developer lists when
> ratified?

Yes (while I don't think that we need to formally ratify it).

> I can co-habit the PR position.  I lack some of the fundamental skills
> and time the position requires (ie. multi-lingual) so I can't handle it
> alone at this early stage.

Great - please add yourself.

Markus

[Markus Neteler-2]

On Wed, Dec 13, 2006 at 04:57:09AM +0000, Brad Douglas wrote:
> On Sat, 2006-12-09 at 14:27 +0100, Markus Neteler wrote:
...

> > Here we go:
> > http://grass.gdf-hannover.de/wiki/Project_jobs
> >
> > Feel free to extend and clarify or to add more job descriptions.
>
> This is an excellent idea.  Would it be reasonable to add positions for
> maintaining various parts of GRASS?  Someone to review code submissions
> in a particular area (ie. raster, vector, imagery, database -- so four
> separate, but similar positions)?  I'm not sure how useful it would be
> at this point, but I thought I would suggest it.

I was recently giving a talk about
"Community based software development: The GRASS GIS project"
http://mpa.itc.it/markus/unitn2006/

where I talked about "code habitats". This is going into the
same direction, I think that we could try to describe that
(on a separate Wiki page maybe). Of course the related people
must agree to that to become sentinel for their area. It
already works like that, only that newcomers don't know
about it.

> Will this document be posted to the users and developer lists when
> ratified?

Yes (while I don't think that we need to formally ratify it).

> I can co-habit the PR position.  I lack some of the fundamental skills
> and time the position requires (ie. multi-lingual) so I can't handle it
> alone at this early stage.

Great - please add yourself.

Markus

[Michael Barton]

I agree that this is a good idea. Things are kind of evolving in that way.
But it would be helpful to make it a bit more formal. Not only would people
have a better sense of responsibility, but could feel less guilty about not
responding to everything. Also, it would give us a better idea of any gaps
in development coverage.

Michael


On 12/12/06 9:57 PM, "Brad Douglas" <[hidden email]> wrote:

> This is an excellent idea.  Would it be reasonable to add positions for
> maintaining various parts of GRASS?  Someone to review code submissions
> in a particular area (ie. raster, vector, imagery, database -- so four
> separate, but similar positions)?  I'm not sure how useful it would be
> at this point, but I thought I would suggest it.
>

__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University

phone: [phone]
fax: [phone]
www: http://www.public.asu.edu/~cmbarton 

[Markus Neteler-2]

(I take liberty to cc to PSC)

Yes, that's fine, but we should really do this on a separate
page to not make the jobs page too long.

Maybe called "Code supervisors"?

Markus

On 12/13/06, Michael Barton <[hidden email]> wrote:

> Should I add myself as something with the GUI?
>
> Michael
>
>
> On 12/12/06 11:45 PM, "Markus Neteler" <[hidden email]> wrote:
>
> > On Wed, Dec 13, 2006 at 04:57:09AM +0000, Brad Douglas wrote:
> >> On Sat, 2006-12-09 at 14:27 +0100, Markus Neteler wrote:
> > ...
> >>> Here we go:
> >>> http://grass.gdf-hannover.de/wiki/Project_jobs
> >>>
> >>> Feel free to extend and clarify or to add more job descriptions.
> >>
> >> This is an excellent idea.  Would it be reasonable to add positions for
> >> maintaining various parts of GRASS?  Someone to review code submissions
> >> in a particular area (ie. raster, vector, imagery, database -- so four
> >> separate, but similar positions)?  I'm not sure how useful it would be
> >> at this point, but I thought I would suggest it.
> >
> > I was recently giving a talk about
> > "Community based software development: The GRASS GIS project"
> > http://mpa.itc.it/markus/unitn2006/
> >
> > where I talked about "code habitats". This is going into the
> > same direction, I think that we could try to describe that
> > (on a separate Wiki page maybe). Of course the related people
> > must agree to that to become sentinel for their area. It
> > already works like that, only that newcomers don't know
> > about it.
> >
> >> Will this document be posted to the users and developer lists when
> >> ratified?
> >
> > Yes (while I don't think that we need to formally ratify it).
> >
> >> I can co-habit the PR position.  I lack some of the fundamental skills
> >> and time the position requires (ie. multi-lingual) so I can't handle it
> >> alone at this early stage.
> >
> > Great - please add yourself.
> >
> > Markus
> >
> > _______________________________________________
> > grass-psc mailing list
> > [hidden email]
> > http://grass.itc.it/mailman/listinfo/grass-psc
>
> __________________________________________
> Michael Barton, Professor of Anthropology
> School of Human Evolution & Social Change
> Center for Social Dynamics and Complexity
> Arizona State University
>
> phone: [phone]
> fax: [phone]
> www: http://www.public.asu.edu/~cmbarton
>
>

--
Open Source Geospatial Foundation
http://www.osgeo.org/
http://grass.osgeo.org/

[Michael Barton]

I'll wait for that then.

Michael


On 12/14/06 1:53 PM, "Markus Neteler" <[hidden email]> wrote:

> (I take liberty to cc to PSC)
>
> Yes, that's fine, but we should really do this on a separate
> page to not make the jobs page too long.
>
> Maybe called "Code supervisors"?
>
> Markus
>
> On 12/13/06, Michael Barton <[hidden email]> wrote:
>> Should I add myself as something with the GUI?
>>
>> Michael
>>
>>
>> On 12/12/06 11:45 PM, "Markus Neteler" <[hidden email]> wrote:
>>
>>> On Wed, Dec 13, 2006 at 04:57:09AM +0000, Brad Douglas wrote:
>>>> On Sat, 2006-12-09 at 14:27 +0100, Markus Neteler wrote:
>>> ...
>>>>> Here we go:
>>>>> http://grass.gdf-hannover.de/wiki/Project_jobs
>>>>>
>>>>> Feel free to extend and clarify or to add more job descriptions.
>>>>
>>>> This is an excellent idea.  Would it be reasonable to add positions for
>>>> maintaining various parts of GRASS?  Someone to review code submissions
>>>> in a particular area (ie. raster, vector, imagery, database -- so four
>>>> separate, but similar positions)?  I'm not sure how useful it would be
>>>> at this point, but I thought I would suggest it.
>>>
>>> I was recently giving a talk about
>>> "Community based software development: The GRASS GIS project"
>>> http://mpa.itc.it/markus/unitn2006/
>>>
>>> where I talked about "code habitats". This is going into the
>>> same direction, I think that we could try to describe that
>>> (on a separate Wiki page maybe). Of course the related people
>>> must agree to that to become sentinel for their area. It
>>> already works like that, only that newcomers don't know
>>> about it.
>>>
>>>> Will this document be posted to the users and developer lists when
>>>> ratified?
>>>
>>> Yes (while I don't think that we need to formally ratify it).
>>>
>>>> I can co-habit the PR position.  I lack some of the fundamental skills
>>>> and time the position requires (ie. multi-lingual) so I can't handle it
>>>> alone at this early stage.
>>>
>>> Great - please add yourself.
>>>
>>> Markus
>>>
>>> _______________________________________________
>>> grass-psc mailing list
>>> [hidden email]
>>> http://grass.itc.it/mailman/listinfo/grass-psc
>>
>> __________________________________________
>> Michael Barton, Professor of Anthropology
>> School of Human Evolution & Social Change
>> Center for Social Dynamics and Complexity
>> Arizona State University
>>
>> phone: [phone]
>> fax: [phone]
>> www: http://www.public.asu.edu/~cmbarton
>>
>>
>

__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University

phone: [phone]
fax: [phone]
www: http://www.public.asu.edu/~cmbarton