Re: [GRASS-PSC] PSC management

[Markus Neteler]

Happy New Year, PSC,

Besides the PSC elections which I'd propose for this year, I'd like to warm
up an old topic:

Markus Neteler  schrieb am Do., 17. Nov. 2016, 12:15:

[...]

https://trac.osgeo.org/grass/wiki/PSC/Roles


Please let's revisit this page these days.

Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Moritz Lennert]

On 18/11/16 01:55, Anna Petrášová wrote:

On Thu, Nov 17, 2016 at 10:54 AM, Markus Neteler  wrote:

On Thu, Nov 17, 2016 at 2:53 PM, Margherita Di Leo  wrote:

On Thu, Nov 17, 2016 at 12:15 PM, Markus Neteler  wrote:

...

https://trac.osgeo.org/grass/wiki/PSC/Roles

Now I think that all new and confirmed members may contribute to this
question and edit the trac page directly (and report here)
 :-)



The first email in this thread dates back to 2014 and no action has been
taken,


Right. Howver, we have a new PSC in place now.


from my POV we would need to discuss this thread, as well as other
threads that were posed by members of the community, in a more interactive
way, perhaps via IRC.


Sounds good to me.


Regarding the roles, I am sure other important roles
can be individuated as well (e.g. GSoC coordinator/mentors).


It is a draft wiki page which could be extended.
Regarding the GSoC mentors, I think that this works ok. If we really
need a designated GRASS GIS GSoC coordinator, I don't know.


At the same
time, I'm not sure that these roles must be necessarily found withing the
PSC.


As I wrote in the trac wiki page

"Note: a PSC member with a certain role can also delegate another
community member to share the workload "


Besides the activities that clearly fall currently on the shoulders of
Markus and few others, I don't understand why we need a coordinator at all,
since some activities seem to flow well without a designated coordinator, as
Moritz pointed out. But I'm sure that to propose this, Markus, you must have
your reasons.


Yes: I want a more active PSC. Not sporadically but constantly.


Could we make a quick check of the situation, individuate the
current issues and what are we trying to achieve (or which problems are we
trying to solve) with this proposal? Thanks


Here you go - the current situation (of course my completely biased
private view):

* treasurer: done by Martin Landa and Markus Neteler
* release manager: done by Markus Neteler
* translation manager: done by Markus Neteler
* education manager: vacant
* press and marketing manager: : done by Markus Neteler
* documentation manager: : mainly done by Markus Neteler, with
contributions by Vero, Vaclav and others
* designer: Vincent Bain for flyer, Web site mainly done by Markus
Neteler lacking the migration to a new CMS
* trac bug report manager: mainly done by Markus Neteler with major
support by core developers
* testing manager: vacant? major efforts done by Sören and Vaclav
* GUI design manager: vacant? major efforts done by Anna, Vaclav, Martin

This and that name appears too often :-)



We suggest 'working groups' instead of managers, for some tasks it
fits better and might put the pressure off if people want to join. I
also added additional groups, which would be focused on specific
tasks, such as Python 3.


I also added the task of moving from svn to git.

However, as sorry as I am about this, at this stage, I would not want to 
take on any of these responsibilities, as I'm afraid I wouldn't do them 
any justice currently. Obviously, I'll continue to work on the code, 
and, as always, am available for short term support on any issue. I hope 
this will change by the end of next year. Or maybe Anna's suggestion of 
collectivizing responsibilities on 2-3 developers per task could be a way.


I would strongly plead for some of the power-users to take over some of 
the non-coding responsibilities (i.e. translation, education, marketing, 
documentation, designer) !


Maybe we could send the list around on grass-dev/grass-user and invite 
non-PSC members to take over some these jobs ?


Moritz
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Anna Petrášová]

On Thu, Nov 17, 2016 at 10:54 AM, Markus Neteler  wrote:
> On Thu, Nov 17, 2016 at 2:53 PM, Margherita Di Leo  wrote:
>> On Thu, Nov 17, 2016 at 12:15 PM, Markus Neteler  wrote:
> ...
>>> https://trac.osgeo.org/grass/wiki/PSC/Roles
>>>
>>> Now I think that all new and confirmed members may contribute to this
>>> question and edit the trac page directly (and report here)
>>>  :-)
>>
>>
>> The first email in this thread dates back to 2014 and no action has been
>> taken,
>
> Right. Howver, we have a new PSC in place now.
>
>> from my POV we would need to discuss this thread, as well as other
>> threads that were posed by members of the community, in a more interactive
>> way, perhaps via IRC.
>
> Sounds good to me.
>
>> Regarding the roles, I am sure other important roles
>> can be individuated as well (e.g. GSoC coordinator/mentors).
>
> It is a draft wiki page which could be extended.
> Regarding the GSoC mentors, I think that this works ok. If we really
> need a designated GRASS GIS GSoC coordinator, I don't know.
>
>> At the same
>> time, I'm not sure that these roles must be necessarily found withing the
>> PSC.
>
> As I wrote in the trac wiki page
>
> "Note: a PSC member with a certain role can also delegate another
> community member to share the workload "
>
>> Besides the activities that clearly fall currently on the shoulders of
>> Markus and few others, I don't understand why we need a coordinator at all,
>> since some activities seem to flow well without a designated coordinator, as
>> Moritz pointed out. But I'm sure that to propose this, Markus, you must have
>> your reasons.
>
> Yes: I want a more active PSC. Not sporadically but constantly.
>
>> Could we make a quick check of the situation, individuate the
>> current issues and what are we trying to achieve (or which problems are we
>> trying to solve) with this proposal? Thanks
>
> Here you go - the current situation (of course my completely biased
> private view):
>
> * treasurer: done by Martin Landa and Markus Neteler
> * release manager: done by Markus Neteler
> * translation manager: done by Markus Neteler
> * education manager: vacant
> * press and marketing manager: : done by Markus Neteler
> * documentation manager: : mainly done by Markus Neteler, with
> contributions by Vero, Vaclav and others
> * designer: Vincent Bain for flyer, Web site mainly done by Markus
> Neteler lacking the migration to a new CMS
> * trac bug report manager: mainly done by Markus Neteler with major
> support by core developers
> * testing manager: vacant? major efforts done by Sören and Vaclav
> * GUI design manager: vacant? major efforts done by Anna, Vaclav, Martin
>
> This and that name appears too often :-)


We suggest 'working groups' instead of managers, for some tasks it
fits better and might put the pressure off if people want to join. I
also added additional groups, which would be focused on specific
tasks, such as Python 3.

A + V

>
> HTH,
> Markus
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Markus Neteler]

On Thu, Nov 17, 2016 at 2:53 PM, Margherita Di Leo  wrote:
> On Thu, Nov 17, 2016 at 12:15 PM, Markus Neteler  wrote:
...
>> https://trac.osgeo.org/grass/wiki/PSC/Roles
>>
>> Now I think that all new and confirmed members may contribute to this
>> question and edit the trac page directly (and report here)
>>  :-)
>
>
> The first email in this thread dates back to 2014 and no action has been
> taken,

Right. Howver, we have a new PSC in place now.

> from my POV we would need to discuss this thread, as well as other
> threads that were posed by members of the community, in a more interactive
> way, perhaps via IRC.

Sounds good to me.

> Regarding the roles, I am sure other important roles
> can be individuated as well (e.g. GSoC coordinator/mentors).

It is a draft wiki page which could be extended.
Regarding the GSoC mentors, I think that this works ok. If we really
need a designated GRASS GIS GSoC coordinator, I don't know.

> At the same
> time, I'm not sure that these roles must be necessarily found withing the
> PSC.

As I wrote in the trac wiki page

"Note: a PSC member with a certain role can also delegate another
community member to share the workload "

> Besides the activities that clearly fall currently on the shoulders of
> Markus and few others, I don't understand why we need a coordinator at all,
> since some activities seem to flow well without a designated coordinator, as
> Moritz pointed out. But I'm sure that to propose this, Markus, you must have
> your reasons.

Yes: I want a more active PSC. Not sporadically but constantly.

> Could we make a quick check of the situation, individuate the
> current issues and what are we trying to achieve (or which problems are we
> trying to solve) with this proposal? Thanks

Here you go - the current situation (of course my completely biased
private view):

* treasurer: done by Martin Landa and Markus Neteler
* release manager: done by Markus Neteler
* translation manager: done by Markus Neteler
* education manager: vacant
* press and marketing manager: : done by Markus Neteler
* documentation manager: : mainly done by Markus Neteler, with
contributions by Vero, Vaclav and others
* designer: Vincent Bain for flyer, Web site mainly done by Markus
Neteler lacking the migration to a new CMS
* trac bug report manager: mainly done by Markus Neteler with major
support by core developers
* testing manager: vacant? major efforts done by Sören and Vaclav
* GUI design manager: vacant? major efforts done by Anna, Vaclav, Martin

This and that name appears too often :-)

HTH,
Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Margherita Di Leo]

Hi,

On Thu, Nov 17, 2016 at 12:15 PM, Markus Neteler  wrote:

> Dear PSC,
>
> I would like to restart the discussion on "PSC member roles" to be
> assigned:
>
> On Thu, May 21, 2015 at 2:39 PM, Moritz Lennert
>  wrote:
> > On 17/05/15 12:43, Markus Neteler wrote:
> >>
> >> Hi PSC,
> >>
> >> ... back to this topic of management, I have updated
> >>
> >> https://trac.osgeo.org/grass/wiki/PSC/Agenda#Openissues
> >>
> >> Important are
> >> 1) PSC: assign roles to the PSC members (see there)
> >
> >
> > Looking at the list, I have the feeling that the following are the most
> > important:
> >
> > - treasurer/financial manager: the issue of how to collect funds from
> > sponsors for code sprints comes up regularly
> >
> > - release manager: Markus shouldn't have to handle this on his own any
> > longer
> >
> > - documentation manager / education outreach: these can actually go
> > together. I think that the manual page system works relatively well (some
> > more detailed descriptions and notes and possibly some more examples
> might
> > be nice), but that we lack a coherent body of up-to-date tutorial-like
> > documentation. Such documentation could be very useful for educational
> > purposes as well
> >
> > - translation manager: although I think that the translations system
> seems
> > to work.
> >
> > But even if we designate documentation and translation managers we cannot
> > expect them to do all the work, so the real question is whether having
> such
> > managers will bring in more volunteers...
> >
> > For the first two roles (financial and release) one person to support
> Markus
> > in these tasks would already make a big difference.
> >
> > Markus, could you maybe list the different things that need to be done in
> > these roles ?
>
> Yes:
> https://trac.osgeo.org/grass/wiki/PSC/Roles
>
> Now I think that all new and confirmed members may contribute to this
> question and edit the trac page directly (and report here)
>  :-)
>

The first email in this thread dates back to 2014 and no action has been
taken, from my POV we would need to discuss this thread, as well as other
threads that were posed by members of the community, in a more interactive
way, perhaps via IRC. Regarding the roles, I am sure other important roles
can be individuated as well (e.g. GSoC coordinator/mentors). At the same
time, I'm not sure that these roles must be necessarily found withing the
PSC. Besides the activities that clearly fall currently on the shoulders of
Markus and few others, I don't understand why we need a coordinator at all,
since some activities seem to flow well without a designated coordinator,
as Moritz pointed out. But I'm sure that to propose this, Markus, you must
have your reasons. Could we make a quick check of the situation,
individuate the current issues and what are we trying to achieve (or which
problems are we trying to solve) with this proposal? Thanks

-- 
Margherita Di Leo
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Markus Neteler]

Dear PSC,

I would like to restart the discussion on "PSC member roles" to be assigned:

On Thu, May 21, 2015 at 2:39 PM, Moritz Lennert
 wrote:
> On 17/05/15 12:43, Markus Neteler wrote:
>>
>> Hi PSC,
>>
>> ... back to this topic of management, I have updated
>>
>> https://trac.osgeo.org/grass/wiki/PSC/Agenda#Openissues
>>
>> Important are
>> 1) PSC: assign roles to the PSC members (see there)
>
>
> Looking at the list, I have the feeling that the following are the most
> important:
>
> - treasurer/financial manager: the issue of how to collect funds from
> sponsors for code sprints comes up regularly
>
> - release manager: Markus shouldn't have to handle this on his own any
> longer
>
> - documentation manager / education outreach: these can actually go
> together. I think that the manual page system works relatively well (some
> more detailed descriptions and notes and possibly some more examples might
> be nice), but that we lack a coherent body of up-to-date tutorial-like
> documentation. Such documentation could be very useful for educational
> purposes as well
>
> - translation manager: although I think that the translations system seems
> to work.
>
> But even if we designate documentation and translation managers we cannot
> expect them to do all the work, so the real question is whether having such
> managers will bring in more volunteers...
>
> For the first two roles (financial and release) one person to support Markus
> in these tasks would already make a big difference.
>
> Markus, could you maybe list the different things that need to be done in
> these roles ?

Yes:
https://trac.osgeo.org/grass/wiki/PSC/Roles

Now I think that all new and confirmed members may contribute to this
question and edit the trac page directly (and report here)
 :-)

Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Moritz Lennert]

On 17/05/15 12:43, Markus Neteler wrote:

Hi PSC,

... back to this topic of management, I have updated

https://trac.osgeo.org/grass/wiki/PSC/Agenda#Openissues

Important are
1) PSC: assign roles to the PSC members (see there)


Looking at the list, I have the feeling that the following are the most 
important:


- treasurer/financial manager: the issue of how to collect funds from 
sponsors for code sprints comes up regularly


- release manager: Markus shouldn't have to handle this on his own any 
longer


- documentation manager / education outreach: these can actually go 
together. I think that the manual page system works relatively well 
(some more detailed descriptions and notes and possibly some more 
examples might be nice), but that we lack a coherent body of up-to-date 
tutorial-like documentation. Such documentation could be very useful for 
educational purposes as well


- translation manager: although I think that the translations system 
seems to work.


But even if we designate documentation and translation managers we 
cannot expect them to do all the work, so the real question is whether 
having such managers will bring in more volunteers...


For the first two roles (financial and release) one person to support 
Markus in these tasks would already make a big difference.


Markus, could you maybe list the different things that need to be done 
in these roles ?


Moritz
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Markus Neteler]

Hi PSC,

... back to this topic of management, I have updated

https://trac.osgeo.org/grass/wiki/PSC/Agenda#Openissues

Important are
1) PSC: assign roles to the PSC members (see there)
2) Revisit PSC renewal: we have to define
  * Future PSC members
  * Stepping Down
  * Dissolution of PSC

In my view,

Point 1) would be a way to get more PSC members actively involved;

Point 2) may lead to an amendment of RFC 1 Project Steering Committee
Guidelines.

Please comment on this.

Best,
Markus

--
GRASS PSC Chair
http://grass.osgeo.org/
http://courses.neteler.org/
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Margherita Di Leo]

Hi,

On Tue, Apr 1, 2014 at 9:56 AM, Markus Neteler nete...@osgeo.org wrote:

 PSC,

 in my view a few management issues should be revisited:

 * assign roles to the members: e.g.
   - communication and marketing manager (incl case studies, etc)
   - financial manager
   - translation manager
   - Web designer
   - Testing manager (incl. overseeing new testing framework)
   - Documentation manager


 * have clear voting rules (see
 http://grass.osgeo.org/programming6/rfc3_psc.html - to be rewritten)


 * get issues done from http://grasswiki.osgeo.org/wiki/PSC_Agenda

 * otther issues which may be important

 Please comment on this.


I have the feeling that defining new voting rules has priority. Once the
voting rules are set so that decisions can be handled within a week, the
other issues would go smoothly..

cheers,
madi


-- 
Best regards,

Dr. Margherita DI LEO
Scientific / technical project officer

European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-...@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not
in any circumstance be regarded as stating an official position of the
European Commission.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Markus Neteler]

Dear PSC,

I believe that we need to go on and start the process to
renew parts of the PSC.

List of current PSC members:
- Hamish Bowman
- Helena Mitasova
- Markus Neteler (chair)
- Massimiliano Cannata
- Michael Barton
- Scott Mitchell

Former PSC members:
- Brad Douglas
- Dylan Beaudette
- Paul Kelly
- Maciej Sieczka

In essence we have 4 slots available.

Now it is time to post a call for nomination to obtain a list of
people with recognized contribution to the GRASS project.
The proposer should nominate along with a small paragraph
describing why the candidate is proposed as PSC member.

I'll do so now.

Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Massimiliano Cannata]

Please, go on with the call for nomination.

Thanks,
Massimiliano

On Mon, Oct 8, 2012 at 11:03 AM, Markus Neteler nete...@osgeo.org wrote:

 Dear PSC,

 I believe that we need to go on and start the process to
 renew parts of the PSC.

 List of current PSC members:
 - Hamish Bowman
 - Helena Mitasova
 - Markus Neteler (chair)
 - Massimiliano Cannata
 - Michael Barton
 - Scott Mitchell

 Former PSC members:
 - Brad Douglas
 - Dylan Beaudette
 - Paul Kelly
 - Maciej Sieczka

 In essence we have 4 slots available.

 Now it is time to post a call for nomination to obtain a list of
 people with recognized contribution to the GRASS project.
 The proposer should nominate along with a small paragraph
 describing why the candidate is proposed as PSC member.

 I'll do so now.

 Markus
 ___
 grass-psc mailing list
 grass-psc@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-psc




-- 
-- 

Dr. Eng. Massimiliano Cannata
Responsabile Area Geomatica
Istituto Scienze della Terra
Scuola Universitaria Professionale della Svizzera Italiana
Via Trevano, c.p. 72
CH-6952 Canobbio-Lugano
Tel: +41 (0)58 666 62 14
Fax +41 (0)58 666 62 09
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Paul Kelly]

Markus Neteler wrote:


On Mon, May 28, 2012 at 11:15 AM, Paul Kelly  paul-gr...@stjohnspoint.co.uk 
wrote:


I'm not sure this really needs any changes to RFC 1 either - if desired, it
could simply be an informal rule.


I believe that an addition is needed, especially to fix the currently broken
reference to above in the text.


I don't see any inconsistency there - as I see it above refers to the 
previous paragraph entitled Operation of the PSC, where it describes how 
a proposal is put to the PSC. Looks OK to me.



If any PSC members aren't willing to
continue, then their removal from the PSC can be put forward as a proposal
by the chair.


I dunno, this sounds much like the chair kicks the sleepy members out.


I guess so, but I just feel kind of uncomfortable with the idea that 
people could be somehow automatically removed from the committee without 
any discussion on the list. Note that addition or removal of members 
doesn't appear to require a formal vote, simply to be put forward as 
proposal for discussion until consensus is reached.


All it should need is an e-mail (from anyone who feels comfortable sending 
it; it needn't be the chair) saying I propose that the following members 
be removed from the PSC committee with effect from XX June 2012 - and if 
there are no objections (no need to call a vote, unless anyone wants to) 
then consensus has been reached and the members are removed.


Hamish wrote:


I would simplify as much as possible, add the reasoning, and leave off
the the fine-detail procedural stuff:

In order to keep the PSC fresh, members will annually confirm their
continued involvement. This should happen by June 1st of each year,
afterwhich nominations for their replacement may commence at the
discretion of the chair. They are not replaced, and retain voting rights,
until such point as their replacement member is formally accepted.


I think this sounds very good; I like the idea that nothing happens 
automatically without being proposed to the committee and I also like the 
idea that there has to be a replacement (otherwise a two-week e-mail 
outage could theoretically lead to all PSC members being booted out and 
there being nobody left!).


Best regards

Paul
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Hamish]

 Quoth Markus N.: 
 The PSC members are requested to annually confirm (via email to the
 PSC mailing list) the continuation of their active involvement in the PSC.
 This confirmation is expected by 1 June of each year. In case of lack
 of this confirmation the member will be replaced.

Dylan:
 That sounds just about right. Here is a slightly altered
 version:
 
 Members are requested to annually confirm (via email to the
 PSC mailing list) the continuation of their active
 involvement in the PSC. This confirmation is expected annually,
 by June 1st. In the absence of such confirmation, nominations
 will open for a replacement by XXX (June 15th?).


I would simplify as much as possible, add the reasoning, and leave off
the the fine-detail procedural stuff:

In order to keep the PSC fresh, members will annually confirm their
continued involvement. This should happen by June 1st of each year,
afterwhich nominations for their replacement may commence at the
discretion of the chair. They are not replaced, and retain voting rights,
until such point as their replacement member is formally accepted.


Overly-automatic timeouts are poor management IMO, it puts the burden onto
the ruleset instead of the humans. Maybe that avoids some personal
confrontation, but is a bit of a cop-out of our responsibilities IMO.



best,
Hamish
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Markus Neteler]

Hi Paul, all,

On Mon, May 28, 2012 at 11:15 AM, Paul Kelly
paul-gr...@stjohnspoint.co.uk wrote:
 Hi Markus,
 Great that we're talking about this - definitely something needs to be done.

Thanks for your immediate reply.

 RFC 1 says in regard to the composition of the PSC:

 Addition and removal of members from the committee, as well as selection of
 Chair is handled as a proposal to the committee as described above.

Yes, amusingly this described above points to nowhere. So one new
phrase is needed closing the gap.

 I unfortunately haven't had the time to contribute to GRASS for a few years
 now, primarily because my work has taken me away from the field of GIS - so
 I would be happy to propose myself to be removed from the PSC at any time.

It does not mean to be kicked of this open list!

General comment:
I just want to be the PSC a bit more active, i.e. proposing new ideas,
implementing more at outreach and so forth. May I felt a bit too much
talking to myself here in the past :)

 It's very easy to let these things drift, so I think a specific date every
 year at which PSC members can confirm their intention to continue is a great
 idea.

Agreed. Like this we get a rhythm.

 I'm not sure this really needs any changes to RFC 1 either - if desired, it
 could simply be an informal rule.

I believe that an addition is needed, especially to fix the currently broken
reference to above in the text.

 If any PSC members aren't willing to
 continue, then their removal from the PSC can be put forward as a proposal
 by the chair.

I dunno, this sounds much like the chair kicks the sleepy members out.
See below for a proposal.

 I do think it's important to have a specific date every year
 that everyone knows about though, as five working days is quite short and
 someone might be away on holiday for example.

Sure - I put it this time to get something rolling :)

 To make it convenient for the changes you're proposing right now, I would
 suggest 1 June could be the annual renewal date.

I would propose to add something like this phrase to RFC1:

The PSC members are requested to annually confirm (via email to the
PSC mailing list) the continuation of their active involvement in the PSC.
This confirmation is expected by 1 June of each year. In case of lack
of this confirmation the member will be replaced.

[please put into real English, thanks]

 Apart from that, great work.

Great work of a great community!

Best
Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Markus Neteler]

On Mon, May 28, 2012 at 7:23 PM, Massimiliano Cannata
massimiliano.cann...@supsi.ch wrote:
 I'm interested in continue.
 Even though I'm not a core developer I feel I have demonstrated a
 substantial involvement in GRASS GIS (I) giving courses for engineers,
 architects and professionals (II) conducting research in natural hazards
 using grass (see foss4g presentations from Bangkok to Denver).
 In any case if you think someone else is more appropriate I'm ready to make
 a step back.

Please don't since all kinds of contributions are important, not only coding.

Thanks also to Scott, Michael and Dylan for their replies.
(Helena is on the road but was in Prague discussing this topic).
Yann replied offlist to me that he is stepping back but also that he
hopes to come back.

Some members didn't answer yet:
http://grass.osgeo.org/wiki/PSC

Best
Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Markus Neteler]

On Wed, May 30, 2012 at 10:30 PM, Michael Barton michael.bar...@asu.edu wrote:
 I also agree. All of us have other lives and cannot contribute full time to 
 GRASS.
 And our availability varies a lot over time.

Sure, but there is still much space between essentially doing nothing and doing
something... :)

 But it is the diversity of expertise and activities that makes this community 
 successful.

I fully agree.

Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Michael Barton]

This all sounds reasonable to me. Here is some editing of the clause you 
proposed. I gave a two week grace period, but you can eliminate it or extend it 
as seems best.

PSC members are requested to confirm annually (via email to the PSC mailing 
list) their interest in continuing active involvement in the PSC. This 
confirmation of continuation of PSC membership should be sent to the Chair of 
the PSC by 1 June of each year. If a PSC member does not confirm his/her desire 
to continue on the PSC within two weeks of 1 June, that member will be 
replaced.

Michael


On May 30, 2012, at 11:54 AM, Markus Neteler wrote:

 Hi Paul, all,
 
 On Mon, May 28, 2012 at 11:15 AM, Paul Kelly
 paul-gr...@stjohnspoint.co.uk wrote:
 Hi Markus,
 Great that we're talking about this - definitely something needs to be done.
 
 Thanks for your immediate reply.
 
 RFC 1 says in regard to the composition of the PSC:
 
 Addition and removal of members from the committee, as well as selection of
 Chair is handled as a proposal to the committee as described above.
 
 Yes, amusingly this described above points to nowhere. So one new
 phrase is needed closing the gap.
 
 I unfortunately haven't had the time to contribute to GRASS for a few years
 now, primarily because my work has taken me away from the field of GIS - so
 I would be happy to propose myself to be removed from the PSC at any time.
 
 It does not mean to be kicked of this open list!
 
 General comment:
 I just want to be the PSC a bit more active, i.e. proposing new ideas,
 implementing more at outreach and so forth. May I felt a bit too much
 talking to myself here in the past :)
 
 It's very easy to let these things drift, so I think a specific date every
 year at which PSC members can confirm their intention to continue is a great
 idea.
 
 Agreed. Like this we get a rhythm.
 
 I'm not sure this really needs any changes to RFC 1 either - if desired, it
 could simply be an informal rule.
 
 I believe that an addition is needed, especially to fix the currently broken
 reference to above in the text.
 
 If any PSC members aren't willing to
 continue, then their removal from the PSC can be put forward as a proposal
 by the chair.
 
 I dunno, this sounds much like the chair kicks the sleepy members out.
 See below for a proposal.
 
 I do think it's important to have a specific date every year
 that everyone knows about though, as five working days is quite short and
 someone might be away on holiday for example.
 
 Sure - I put it this time to get something rolling :)
 
 To make it convenient for the changes you're proposing right now, I would
 suggest 1 June could be the annual renewal date.
 
 I would propose to add something like this phrase to RFC1:
 
 The PSC members are requested to annually confirm (via email to the
 PSC mailing list) the continuation of their active involvement in the PSC.
 This confirmation is expected by 1 June of each year. In case of lack
 of this confirmation the member will be replaced.
 
 [please put into real English, thanks]
 
 Apart from that, great work.
 
 Great work of a great community!
 
 Best
 Markus
 ___
 grass-psc mailing list
 grass-psc@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-psc

_
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research 
University Consortium for Atmospheric Research
303-497-2889 (voice)

Director, Center for Social Dynamics  Complexity 
Professor of Anthropology, School of Human Evolution  Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu





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

Re: [GRASS-PSC] PSC management

[Dylan Beaudette]

On Mon, May 28, 2012 at 2:15 AM, Paul Kelly
paul-gr...@stjohnspoint.co.uk wrote:
 Hi Markus,
 Great that we're talking about this - definitely something needs to be done.
 RFC 1 says in regard to the composition of the PSC:

 Addition and removal of members from the committee, as well as selection of
 Chair is handled as a proposal to the committee as described above.

 I unfortunately haven't had the time to contribute to GRASS for a few years
 now, primarily because my work has taken me away from the field of GIS - so
 I would be happy to propose myself to be removed from the PSC at any time.
 It's very easy to let these things drift, so I think a specific date every
 year at which PSC members can confirm their intention to continue is a great
 idea.

 I'm not sure this really needs any changes to RFC 1 either - if desired, it
 could simply be an informal rule. If any PSC members aren't willing to
 continue, then their removal from the PSC can be put forward as a proposal
 by the chair. I do think it's important to have a specific date every year
 that everyone knows about though, as five working days is quite short and
 someone might be away on holiday for example.

 To make it convenient for the changes you're proposing right now, I would
 suggest 1 June could be the annual renewal date.

 Apart from that, great work.

 Best regards

 Paul


I agree with Paul. Unfortunately I am in a similar situation, and
cannot really dedicate enough time to GRASS to justify being on the
PSC. I can see this situation changing in the near future, but I am
sure that there are others out there who have more time to dedicate to
the project. I'll continue to lurk on the mailing list and eventually
get back into GRASS development.

Thanks for all of the hard work!

Dylan
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Michael Barton]

I am interested in continuing.

Michael

On May 28, 2012, at 12:01 AM, Markus Neteler wrote:

 Dear PSC members,
 
 we discussed the GRASS PSC at the current GRASS GIS Community Sprint here
 in Prague (Helena, me, some community members) and decided that we need
 to moderize the PSC and the way of management while keeping the overhead low.
 
 For sure every year the PSC members are requested to confirm/decline
 to continue their
 work in the PSC.
 
 I (being the current PSC chair) would like to request you to suggest
 updates to the
 RFC1. In order to see the interest, please answer within five business
 days to this
 email.
 
 In case of no interest of continuation or no answer, the member will
 be replaced in order
 to refresh the GRASS PSC.
 
 In Prague it was discussed how to identify community members eligible for
 PSC membership. We came to the conclusion that such a person should have a
 demonstrated and substantial involvement in GRASS GIS.
 
 Please post your comments within five business days, i.e. end of the upcoming
 week.
 
 Thanks and greetings from a great Community Sprint,
 Markus
 
 PS: See
 http://grass.osgeo.org/wiki/Talk:GRASS_Community_Sprint_Prague_2012
 
 PPS: Special thanks to Martin Landa for organizing it (again)
 ___
 grass-psc mailing list
 grass-psc@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-psc

_
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research 
University Consortium for Atmospheric Research
303-497-2889 (voice)

Director, Center for Social Dynamics  Complexity 
Professor of Anthropology, School of Human Evolution  Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu





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

Re: [GRASS-PSC] PSC management

[Paul Kelly]

Hi Markus,
Great that we're talking about this - definitely something needs to be 
done. RFC 1 says in regard to the composition of the PSC:


Addition and removal of members from the committee, as well as selection 
of Chair is handled as a proposal to the committee as described above.


I unfortunately haven't had the time to contribute to GRASS for a few 
years now, primarily because my work has taken me away from the field of 
GIS - so I would be happy to propose myself to be removed from the PSC at 
any time. It's very easy to let these things drift, so I think a specific 
date every year at which PSC members can confirm their intention to 
continue is a great idea.


I'm not sure this really needs any changes to RFC 1 either - if desired, 
it could simply be an informal rule. If any PSC members aren't willing to 
continue, then their removal from the PSC can be put forward as a proposal 
by the chair. I do think it's important to have a specific date every year 
that everyone knows about though, as five working days is quite short and 
someone might be away on holiday for example.


To make it convenient for the changes you're proposing right now, I would 
suggest 1 June could be the annual renewal date.


Apart from that, great work.

Best regards

Paul

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

Re: [GRASS-PSC] PSC management

[Michael Barton]

Same here.

Michael

On May 28, 2012, at 1:50 PM, Scott Mitchell wrote:

 Paul's suggestions make sense to me, since they are low
 maintenance. 
 
 I am interested in continuing. 
 
 
 Scott Mitchell (mobile)
 +1 613 882 3843
 smi...@me.com
 
 
 On 2012-05-28, at 5:15, Paul Kelly paul-gr...@stjohnspoint.co.uk wrote:
 
 Hi Markus,
 Great that we're talking about this - definitely something needs to be done. 
 RFC 1 says in regard to the composition of the PSC:
 
 Addition and removal of members from the committee, as well as selection of 
 Chair is handled as a proposal to the committee as described above.
 
 I unfortunately haven't had the time to contribute to GRASS for a few years 
 now, primarily because my work has taken me away from the field of GIS - so 
 I would be happy to propose myself to be removed from the PSC at any time. 
 It's very easy to let these things drift, so I think a specific date every 
 year at which PSC members can confirm their intention to continue is a great 
 idea.
 
 I'm not sure this really needs any changes to RFC 1 either - if desired, it 
 could simply be an informal rule. If any PSC members aren't willing to 
 continue, then their removal from the PSC can be put forward as a proposal 
 by the chair. I do think it's important to have a specific date every year 
 that everyone knows about though, as five working days is quite short and 
 someone might be away on holiday for example.
 
 To make it convenient for the changes you're proposing right now, I would 
 suggest 1 June could be the annual renewal date.
 
 Apart from that, great work.
 
 Best regards
 
 Paul
 
 ___
 grass-psc mailing list
 grass-psc@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-psc
 ___
 grass-psc mailing list
 grass-psc@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-psc

_
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research 
University Consortium for Atmospheric Research
303-497-2889 (voice)

Director, Center for Social Dynamics  Complexity 
Professor of Anthropology, School of Human Evolution  Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu





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

Re: [GRASS-PSC] PSC management

[Massimiliano Cannata]

I'm interested in continue.
Even though I'm not a core developer I feel I have demonstrated a
substantial involvement in GRASS GIS (I) giving courses for engineers,
architects and professionals (II) conducting research in natural hazards
using grass (see foss4g presentations from Bangkok to Denver).
In any case if you think someone else is more appropriate I'm ready to make
a step back.

Maxi
Il giorno 28/mag/2012 00:01, Markus Neteler nete...@osgeo.org ha
scritto:

 Dear PSC members,

 we discussed the GRASS PSC at the current GRASS GIS Community Sprint here
 in Prague (Helena, me, some community members) and decided that we need
 to moderize the PSC and the way of management while keeping the overhead
 low.

 For sure every year the PSC members are requested to confirm/decline
 to continue their
 work in the PSC.

 I (being the current PSC chair) would like to request you to suggest
 updates to the
 RFC1. In order to see the interest, please answer within five business
 days to this
 email.

 In case of no interest of continuation or no answer, the member will
 be replaced in order
 to refresh the GRASS PSC.

 In Prague it was discussed how to identify community members eligible for
 PSC membership. We came to the conclusion that such a person should have a
 demonstrated and substantial involvement in GRASS GIS.

 Please post your comments within five business days, i.e. end of the
 upcoming
 week.

 Thanks and greetings from a great Community Sprint,
 Markus

 PS: See
 http://grass.osgeo.org/wiki/Talk:GRASS_Community_Sprint_Prague_2012

 PPS: Special thanks to Martin Landa for organizing it (again)
 ___
 grass-psc mailing list
 grass-psc@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-psc

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