Re: [GRASS-PSC] Sponsoring program

2014-04-01 Thread Margherita Di Leo
Hi,

On Tue, Apr 1, 2014 at 9:16 AM, Moritz Lennert mlenn...@club.worldonline.be
 wrote:



 I suggest to create a section in the website for long term/historical
 sponsors, and list the new sponsors in the web page only if they donate
 / contribute regularly (Say, once a year - I would indicate a certain
 lower threshold for the amount). Event-based donors and micro-donors
 will be listed into the wiki page of the event.


 That would mean that someone who gives a large amount, but only once, will
 not be mentioned anywhere ? I think that sometimes companies might want to
 pay back in a one-shot for the use they made of a free software, but
 without committing for long term sponsorship. I think that they should also
 be mentioned somewhere.


I agree that they should be mentioned somewhere, but probably keeping them
in the page of the sponsors for ever is not the best choice. Maybe in a
separate section?

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] applying for svn writing access

2014-04-01 Thread Markus Neteler
On Tue, Apr 1, 2014 at 9:10 AM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
 P.S. Do we really have to wait for a vote by all PSC members for granting
 write access ?

To my knowledge
- for trunk/branch write access yes (at least we handled it like this
in the past)
- for Addons no.

We should really adopt (maybe in modified form):
  RFC3: PSC Voting Procedures
  http://grass.osgeo.org/programming6/rfc3_psc.html

Also related:
- http://grass.osgeo.org/programming7/psc_motions.html
- http://grasswiki.osgeo.org/wiki/PSC_Agenda

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


Re: [GRASS-PSC] Sponsoring program

2014-04-01 Thread Moritz Lennert

On 01/04/14 09:24, Margherita Di Leo wrote:


Hi,

On Tue, Apr 1, 2014 at 9:16 AM, Moritz Lennert
mlenn...@club.worldonline.be mailto:mlenn...@club.worldonline.be wrote:



I suggest to create a section in the website for long
term/historical
sponsors, and list the new sponsors in the web page only if they
donate
/ contribute regularly (Say, once a year - I would indicate a
certain
lower threshold for the amount). Event-based donors and micro-donors
will be listed into the wiki page of the event.


That would mean that someone who gives a large amount, but only
once, will not be mentioned anywhere ? I think that sometimes
companies might want to pay back in a one-shot for the use they made
of a free software, but without committing for long term
sponsorship. I think that they should also be mentioned somewhere.


I agree that they should be mentioned somewhere, but probably keeping
them in the page of the sponsors for ever is not the best choice. Maybe
in a separate section?


I guess a yearly revision of the list of sponsors would not be too much 
work, or ?


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


Re: [GRASS-PSC] Sponsoring program

2014-04-01 Thread Yann Chemin
I am OK with the former donors page, with a (past years) date of funding
and a thank you note from GRASS.


On 1 April 2014 13:21, Margherita Di Leo direg...@gmail.com wrote:




 On Tue, Apr 1, 2014 at 9:45 AM, Moritz Lennert 
 mlenn...@club.worldonline.be wrote:

 On 01/04/14 09:24, Margherita Di Leo wrote:




 On Tue, Apr 1, 2014 at 9:16 AM, Moritz Lennert
 mlenn...@club.worldonline.be mailto:mlenn...@club.worldonline.be
 wrote:



 I suggest to create a section in the website for long
 term/historical
 sponsors, and list the new sponsors in the web page only if they
 donate
 / contribute regularly (Say, once a year - I would indicate a
 certain
 lower threshold for the amount). Event-based donors and
 micro-donors
 will be listed into the wiki page of the event.


 That would mean that someone who gives a large amount, but only
 once, will not be mentioned anywhere ? I think that sometimes
 companies might want to pay back in a one-shot for the use they made
 of a free software, but without committing for long term
 sponsorship. I think that they should also be mentioned somewhere.


 I agree that they should be mentioned somewhere, but probably keeping
 them in the page of the sponsors for ever is not the best choice. Maybe
 in a separate section?


 I guess a yearly revision of the list of sponsors would not be too much
 work, or ?


 Thus that's more or less what I meant in the first place: a donor remains
 in the sponsors page only if donates regularly (eg. every year),
 otherwise it's moved to a list of former donors (which I believe is
 necessary to keep track of, for transparency and history).





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




-- 

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

Re: [GRASS-PSC] PSC management

2014-04-01 Thread 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] releases schedule

2014-04-01 Thread Vaclav Petras
On Mon, Mar 31, 2014 at 11:40 AM, Vaclav Petras wenzesl...@gmail.com
 wrote:


 I find that 6 months is a fairly long period to maintain a bugfix-only
 branch. I would rather propose to either branch later, or to allow more
 than just bugfixes into the release branch for 4-5 months before going into
 bugfix-only phase for the last month or two. During the first period new
 features can be ported to the release branch once they have had some
 testing in trunk.


 Moritz, I believe that these are two different things.

 ...

 Second, committing features to both branches is what is taking the time
 from us and creating uncertainty about what is where and what are the
 branches for. I think that this is crucial point and the lengths of time
 periods above should be decided based on this, not the other way around.

 On Mon, Mar 31, 2014 at 11:09 PM, Yann Chemin yche...@gmail.com wrote:

 It looks like we all want to see version numbers move on a yearly basis
 with periods of branching and periods of releasing...


We need to agree on the policy of committing to release branch(es). See my
proposal [1] for details.

[1] http://lists.osgeo.org/pipermail/grass-psc/2014-March/001150.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] releases schedule

2014-04-01 Thread Vaclav Petras
On Mon, Mar 31, 2014 at 11:09 PM, Yann Chemin yche...@gmail.com wrote:

 Should we finalize this policy and implement it?


Probably yes. Does PSC have to vote on this?

We put the proposal to Trac wiki (1), so we can track changes into it. In
future it can go to (Doxygen) documentation but not now.

(1) It does not completely fit into what I think Trac should be used for
but all other things about releases are there anyway.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc