[GRASS-PSC] ESA Summer of Code in Space

[Moritz Lennert]

Just stumbled upon this:

http://sophia.estec.esa.int/socis2012/

It is only open to students enrolled in European universities, but it 
might be an interesting addition to GSoC for developing remote sensing 
modules for GRASS.


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

Re: [GRASS-PSC] ESA Summer of Code in Space

[Moritz Lennert]

On 14/01/13 18:28, Luca Delucchi wrote:

Hi Moritz

2013/1/14 Moritz Lennertmlenn...@club.worldonline.be:

Just stumbled upon this:

http://sophia.estec.esa.int/socis2012/

It is only open to students enrolled in European universities, but it might
be an interesting addition to GSoC for developing remote sensing modules for
GRASS.



Yes, I think this is a good idea. This is the last year edition.
Please look for update.


I did, but couldn't find anything. I just subscribed to their mailing 
list so I'll get the news when the 2013 edition is launched.


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

[GRASS-PSC] Grass7 tech-preview release [was Re: [GRASS-user] to move or not move ? grass64 - ? - 7.0]

[Moritz Lennert]

On 18/03/13 23:04, Markus Neteler wrote:

On Fri, Jan 11, 2013 at 9:53 AM, Rainer M Krugr.m.k...@gmail.com  wrote:
...

Following the discussion, I would like to install GRASS 7 weekly snapshot. I relized the 
Binary
link (http://grass.osgeo.org/download/software/) but it points back to the 
Linux Download page,
but I could not find any binaries there for GRASS 7? Maybe this link should be 
removed?

Just wondering, but not a problem, as I am going to install from source anyway.


In the past days I have cleaned up several of the Web pages.
I hope they are much clearer now. GRASS 7 downloads are now properly
mentioned as well.


Much clearer now !

I would like to take this debate as an opportunity to touch upon the 
question of a possible tech-preview release of GRASS7.


Several reasons for that:

- More and more people are using it (and we are pushing more and more 
people toward using it). Binaries are available for windows and mac, but 
not for most Linux distributions. A preview release might make it easier 
for these distributions to package grass7 and make it available to a 
larger audience.


- In many institutions it is (understandably) not easy to convince 
IT-managers to install development snapshots instead of released 
software. Having an official release (even if it is only a tech-preview 
release) should make it easier to install grass7 in institutional settings.


- I think that grass7 is in a form where we can start advertising it 
more widely and more officially. In terms of timing, it would be great 
to be able to get this out before FOSS4G.


- From my own egotistical viewpoint, I would love to be able to use 
grass7 in my classes next school year, and having a release would make 
it much easier for me to do that.


Concretely, I see the following type of procedure to make it possible:

- Freeze the svn repository for any direct new commits for a short 
period (I'd say max 1-2 weeks). Only a few release managers should 
still have direct commit access at this point. (Another way to do it 
would be to keep commit rights open to anyone, and the role of the 
release managers would be to control all commits and revert those that 
aren't simple bug fixes during the freeze).


- Publish the state of the code at the beginning of the freeze as RC1 
with a wide call for testing.


- Only bug fix* commits.

- Publish RC2 after some bug fixing (possibly after one week).

- Continue bug fixing*.

- Release tech-preview (possibly at the end of week 2) with a huge 
disclaimer that this is a tech-preview release and not considered final 
and stable.


- Open repository again for more general development.


I don't think we should create a release branch as this would just be a 
tech-preview snaphot of the ongoing development.


This obviously implies that we plan ahead and that all developers know 
when this freeze will happen, thus avoiding to commit any large and 
fundamental changes just before the freeze. And that we all put aside 
time during that freeze for testing and bug fixing.


What do you think ?

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

Re: [GRASS-PSC] [GRASS-dev] Grass7 tech-preview release [was Re: [GRASS-user] to move or not move ? grass64 - ? - 7.0]

[Moritz Lennert]

On 19/03/13 20:57, Markus Neteler wrote:

If you accept me to manage the release and related stuff, I am happy
to prepare things as needed with your help.


Great ! And yes, I'm willing to help on this.

No need to rush, though. I think the secret of success of the schedule 
is preparation and planning. So, we could fix a release date and then 
work the schedule backwards.


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

Re: [GRASS-PSC] Permission request for using the Dev ML for a MSc thesis project

[Moritz Lennert]

On 15/11/13 12:31, Marco Foi wrote:

Dear ML Administrators/PSC,


I am a GIS enthusiast and Computer Science student and I am writing you
to seek for your preliminary consensus to use the
grass-...@lists.osgeo.org mailto:grass-...@lists.osgeo.org mailing
list for the purposes of my MSc thesis.


Specifically I am trying to directly collect the developers’ opinions
about a number of features that might characterize a good desktop
geo-processing framework.

The final goal is going a step beyond the usual Desktop GIS round-up to
attempt a review of all those open-source desktop environments that
attract developers and spatial-scientist by allowing them to efficiently
create new tools to process spatial information.


My plan is administering a simple questionnaire trough the ML and
collect voluntary contributes from the subscribers.

The synthesis of the results from this survey and from all the analogous
performed inside other Communities will be made publicly available at
the end of the study (February 2014) through a post on this ML (and
perhaps in a subsequent open-access paper).


All contributes from the ML will be managed complying to University
Ethical Committee (EC) regulations to ensure no leakage of personal
information will occur. This study has been approved by the EC with
protocol number COM/PG/UH/00034.

Looking forward to hearing from you.


I have no objections to this request, so +1 from me.

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

Re: [GRASS-PSC] too many branches

[Moritz Lennert]

On 29/03/14 07:04, Luca Delucchi wrote:

Hi PSC,

with the upcoming GRASS 7 release we have to many branches to maintain
(releasebranch6, devbranch6, releasebranch7 and trunk).
Can I ask you to take a decision about the future of all this branches?

I could suggest something like:
- keep releasebranch6 only for important bugfixes, no new feature and
starting to forget it
- put in reading mode or remove (after backport the differences with
grass64) devbranch6
- releasebranch7 is the new stable release branch, so new features
only when we are far from release a new version
- trunk for new feature

what do you think?


The initial idea was to create a tech-preview release of grass7, not an 
official 7.0 release. Has that changed during the sprint ?


If we only do a tech release, I don't think we really need a 
releasebranch. Just a short (max 2 weeks) commit freeze to trunk to make 
sure everything compiles and runs as expected (with known bugs) and then 
release.


Concerning grass6, I agree that we should probably merge release and 
dev. Maybe


- backport anything from dev to release that is stable enough for 
release (if there is anything left to backport)

- publish grass6.4.4
- if there is anything in 6-dev which is not in trunk, then forward-port 
that if necessary/feasible

- then, as you propose, abandon 6-dev and keep 6-release in maintenance mode

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

Re: [GRASS-PSC] releases schedule

[Moritz Lennert]

On 29/03/14 21:56, Vaclav Petras wrote:

Inspired by what code sprint people were saying, I put together my
proposal. It counts with release once a year and a half year bugfixing
(feature freeze) period before the release. I expect comments and
criticism and I would be glad to compare this proposal with some other
proposal.

Vaclav


Releasing and branch management should follow these steps:

 1. have trunk
 2. fork release branch , e.g. release_7_1
 3. only bugfixes to release branch, new features (additions,
refactoring, documentation) only to trunk
 4. release new version based on release branch, , e.g. 7.1.0
 5. only critical bugfixes go to release branch, release patched version
if needed, e.g. 7.1.1, .7.1.2
 6. fork a new release branch (e.g. release_7_2), set old release branch
to readonly and continue with point 3.

It seems that release should be done every year. A new release branch
should be forked half a year before planned release.


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
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] too many branches

[Moritz Lennert]

On 31/03/14 10:34, Markus Neteler wrote:

On Mon, Mar 31, 2014 at 10:24 AM, Moritz Lennert
mlenn...@club.worldonline.be wrote:

The initial idea was to create a tech-preview release of grass7, not an
official 7.0 release. Has that changed during the sprint ?


No, this is what happened: beta1 (called like this to maintain
consistency with previous pre-releases).


I did see that, but for me a beta release is a first version of what 
will be a final grass7.0 release. A tech-preview, in my understanding, 
is more of a snapshot of an ongoing development branch.


But if the general feeling is that we can actually release a grass7.0 by 
the summer or early autumn, then let's do it.




See also (pls improve that page!):
http://trac.osgeo.org/grass/wiki/Release/7.0.0beta-News


If we only do a tech release, I don't think we really need a releasebranch.
Just a short (max 2 weeks) commit freeze to trunk to make sure everything
compiles and runs as expected (with known bugs) and then release.


This is likely causing more work than it helps. but we can see how it evolves.


I think it creates more work during the short freeze, but avoids the 
need of multiplying branches.


If the procedure is clear and the calendar is agreed upon and all devs 
collaborate then it shouldn't be too much trouble.


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

Re: [GRASS-PSC] Sponsoring program

[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] too many branches = retirement GRASS6.5.svn (=develbranch6)

[Moritz Lennert]

On 06/04/14 13:46, Hamish wrote:


First of all, I believe this discussion belongs on the grass-dev list, not PSC. 
See RFC1.


CC'in to dev-list



releasebranch70 should not have been branched until 7.0RC1. Until RC1
it is just wasted effort to keep the two of them as a 1:1 mirror, so
what's the point? If anyone wants to talk about unnecessary developer
burden, start there.


As already mentioned I was also a bit surprised by this. I'm not sure we 
are really ready for something more than a tech-preview (and not a real 
release), but maybe it could be the kick in the behind that we need to 
once and for all move over to GRASS7 as the main official branch...


I also think that voting on Martin's proposal as such is a bit 
premature. I think we should discuss the pros and cons of different 
approaches a bit more before calling a vote.


I think that experience has shown that the lack of clear policy on 
release management has caused frustration among developers. Personally, 
I'm somewhere between the two approaches. On the one hand what I 
understand to be Hamish' wish of having a debian-like system of unstable 
for ongoing cutting-edge development, testing as a staging area for more 
stabilized code and stable as rock-solid, albeit a bit outdated, On the 
other hand, I just haven't seen this work in GRASS up to now and I see a 
lot of frustration from those who find this system too heavy to carry. I 
don't know if that is because the procedure never was clear or whether 
we lack the equivalent of the debian ftp-managers to oversee the 
process, whether we just lack the discipline (which could be linked to 
the previous point) or whether the GRASS development team is just too 
small for such a process. One of the big differences, IMHO, is that a 
user of debian testing just has to apt-get update  apt-get upgrade to 
get the lasted developments, whereas users of grass6dev has to compile 
it themselves (at least on GNU/Linux) as no distribution offers packages 
for that. This means that using testing is a much more involved process.


So, before we start voting of release procedures, maybe we have to first 
clarify and agree upon our goals. I.e. decide on the ends before we 
decide on the means.


Here is my attempt on some of the goals:

- provide a rock-solid, just works, version of GRASS
- provide easy access for users to new developments in GRASS
- keep the burden on the dev-team as low as possible
- make the whole development and release process very clear and explicit 
with defined procedures and (at least relative) timetables
- enforce a certain level of discipline in the respect of these rules 
and procedures



As mentioned before, I wish to use the bulk of my grass dev time
maintaining the grass 6 line. To do that properly I need a staging
area, and devbr6 is it. Hosting a clone on github for that is too
ridiculous and broken a situation to begin to contemplate.

If devbr6 is removed I simply can not do the stable grass 6
maintenance job properly. So without that there is really very little
for me to contribute in future. It will not translate to me spending
more time working on grass 7, only drive me away from the project.


I think that seen Hamish' continued effort for this project this a 
serious enough situation to demand a solution.


But maybe the idea to actually release a first version of grass7 in a 
not to far future is a way out.


Hamish, maybe you could be the official grass6 maintainer, managing the 
whole grass6 development in the way you propose, i.e. any new 
development and bugfixes first go into grass6dev for a period of 
testing, before _you_ make the decision that something can be backported 
to grass6release. I do think however, that for this to work, we would 
need to regularly publish snapshots of grass6dev for easy testing.


All other devs only commit to grass6dev, never to grass6release.

Just my 2¢,

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

Re: [GRASS-PSC] RFC3: New voting rules

[Moritz Lennert]

On 06/04/14 12:48, Markus Neteler wrote:

PSC;

since the voting discussion is scattered around in various email
threads, I start a new one to separate it from ongoing motions. Please
re-express your comments as answer to this email.

   RFC3: PSC Voting Procedures
   http://grass.osgeo.org/programming7/rfc3_psc.html



Thank you for this revised version !

I agree with Madi on the way the delay is expressed.

I have two major remarks, though:

- We should define more clearly what should be subject to voting. At 
this stage we only have this in the PSC guidelines:


The following issue(s) must have a vote called before a decision is 
reached:


Granting source code repository write access for new developers
Selection of a committee Chair


Maybe we need to amend this a bit in the light of the current votes 
being put onto this list ?


- Proposals are written up and submitted on the mailing list for 
discussion. Any committee member may call a vote on any proposal, 
although it is normal practice for the proposer to call the vote.


I would propose that in order to avoid vote inflation, any proposal 
should be submitted by at least three members of the PSC, not just one. 
This should ensure a bit of discussion and peer review before 
submission, thus avoiding long debates on proposals that just are not 
ripe for vote, yet.


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

Re: [GRASS-PSC] [GRASS-dev] [GRASS GIS] #2031: G_legal_filename() cleanup patch for GRASS 6

[Moritz Lennert]

On 19/05/14 05:30, GRASS GIS wrote:


  And again, even if this were a valid candidate for G6, backporting stuff
  directly to 6.4 without going into devbr6 for at least light/any testing
  first, especially anything which touches core libgis, especially a time
  right before RC release, is incredibly risky for anything which is not a
  critical bug fix, and not an environment I can justify contributing my
  time to.


  sorry if I'm grumpy, but I'm at the end of my rope about this.

  regards,
  Hamish


How about my proposal from a few weeks ago: Nobody commits to 
grass64release, only to grass6dev, and Hamish is the official maintainer 
of grass64release and decides what can be backported ?


This obviously can only work if Hamish has the time, so that 6.4.4 is 
not stalled for lack of manpower.


Moritz

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

[GRASS-PSC] GRASS6.4.4 release [was: Re: [GRASS-dev] GRASS 7 release planning]

[Moritz Lennert]

On 23/06/14 17:35, Martin Landa wrote:

Hi,

2014-06-23 10:56 GMT+02:00 Moritz Lennert mlenn...@club.worldonline.be:



But, even though, I know you are in a hurry to get a grass7 release out of
the door, don't you think that we should finish 6.4.4 first ?

To be honest I think we will have to accept shipping OSGEOLive with 6.4.4...


Right, as far as I know Markus is off-line since 27/6. So let's start
with idea to mark RC2 as a final and release it _this_week_! I don't
know about any blockers. Any opinion? If you know about blockers let
us know about that ASAP!


I launched a new thread with an evaluation of current bugs and last call 
for fixes.


Two tickets seem to warrant a backport, but I'm not familiar enough with 
them to judge. Maybe we should just go ahead and backport, then release 
RC2, test that with a special focus on these two backports, and then 
release by the end of the week ?


Moritz

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

Re: [GRASS-PSC] RFC3: New voting rules

[Moritz Lennert]

I would consider this sufficient seconds to the idea of putting the text 
to vote ;-).


On 24/08/14 23:18, Michael Barton wrote:

Me too

C. Michael Barton
Director, Center for Social Dynamics  Complexity
Professor of Anthropology, School of Human Evolution  Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu















On Aug 24, 2014, at 11:07 AM, Scott Mitchell smi...@me.com wrote:


On Aug 23, 2014, at 19:09 , Helena Mitasova hmit...@ncsu.edu wrote:


On Aug 23, 2014, at 10:01 AM, Markus Neteler wrote:


On Sat, Aug 23, 2014 at 3:49 PM, Martin Landa landa.mar...@gmail.com wrote:

Dear PSC,

2014-08-17 21:37 GMT+02:00 Markus Neteler nete...@osgeo.org:

[...]


If I understood this correctly then I assume other understand it as well and no 
modification is needed.


Well, better be clear in the first place. To avoid future discussions
I have done some finetuning in the wording. For the changes, see
http://trac.osgeo.org/grass/wiki/RFC/3_PSCVotingProcedures?action=diffversion=10old_version=9

Hope it is more clear now.


thanks Markus for modifications.

It's not clear to me if we can start voting procedure or not (any
feedback from Helena and others?), what do you think?


I am fine with the current text, Helena


Same here.

Scott


___
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




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

Re: [GRASS-PSC] [MOTION] Approve RFC 3: PSC Voting Procedures

[Moritz Lennert]

On 25/08/14 11:50, Markus Neteler wrote:

PSC,

I hereby move to approve RFC 3: PSC Voting Procedures
http://trac.osgeo.org/grass/wiki/RFC/3_PSCVotingProcedures

I start with a +1.


+1

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

Re: [GRASS-PSC] RFC4 discussion call

[Moritz Lennert]

On 24/11/14 14:38, Martin Landa wrote:

Dear all,

as we are closer and closer to GRASS 7 release I would like to open
discussion related to Release procedure - RFC4 [1]. Ideally (I would
say) it would make sense to find a way how accept such procedure
before we start with GRASS RCs...

Thanks for your feedback in advance! Martin

[1] http://trac.osgeo.org/grass/wiki/RFC/4_ReleaseProcedure


Rereading it I found parts that didn't seem clear, so I reordered the 
sentences slightly to make the meaning clearer.


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

Re: [GRASS-PSC] [GRASS-dev] RFC4 discussion call

[Moritz Lennert]

On 06/01/15 11:25, Martin Landa wrote:

Hi all,

2014-12-30 0:29 GMT+01:00 Markus Neteler nete...@osgeo.org:


I agree with Maris that no feedback should be interpreted as agreement.


I would also agree with that. It would be reasonable also to set some
deadline for discussion and then to propose voting. What do you think?

http://trac.osgeo.org/grass/wiki/RFC/4_ReleaseProcedure?action=diffversion=7old_version=6


I did cosmetics changes [1].


I found that a tbd is still there.


I would suggest to simply delete this sentence. Creating extra branch
for such purpose seems to be not necessary to me. Any opinion on that?


+1

Moritz

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

Re: [GRASS-PSC] [GRASS-dev] RFC 4: Release procedure

[Moritz Lennert]

On 01/03/15 19:02, Markus Neteler wrote:

Hi,

On Tue, Feb 17, 2015 at 1:54 PM, Markus Neteler nete...@osgeo.org wrote:

On Fri, Jun 20, 2014 at 3:39 AM, Scott Mitchell smi...@me.com wrote:

Agreed, and I like Markus’ idea of testing it on an upcoming release.


(just a low priority comment here)

While doing so it turns out that one week between RC2 and final is a bit short.
And some urgent fixes came in only during the RC procedure. We need to
[add] a phrase if this requires a new RC (not this time though!) or not
or depends.


Overall, we got the release out :-)
Any opinions on above remaining issue?


I think that with time we will get better at this procedure and the one 
week limit should be ok, but I have no objections to add a phrase to 
step 6 such as


A final, concerted bug squashing effort by all developers of no more 
than one week. During that same time the release announcement is 
drafted. If an important bug is discovered for which a fix needs some 
more testing, an RC3 can exceptionally be published, with another week 
of testing before final release.


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

Re: [GRASS-PSC] [GRASS-dev] RFC 4: Release procedure

[Moritz Lennert]

On 04/03/15 09:19, Martin Landa wrote:

Hi,

2015-03-03 9:31 GMT+01:00 Moritz Lennert mlenn...@club.worldonline.be:

A final, concerted bug squashing effort by all developers of no more than
one week. During that same time the release announcement is drafted. If an
important bug is discovered for which a fix needs some more testing, an RC3
can exceptionally be published, with another week of testing before final
release.


make sense to me, Martin



Ok, I've added the change. In any case we are a small enough team to 
handle things flexibly if needed. For me, the idea of elaborating a 
release procedure is mostly to make the process more explicit and thus 
ease communication, not to hammer laws into stone


Moritz

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

Re: [GRASS-PSC] Proposal: Logo variant to include GRASS GIS as name

[Moritz Lennert]

On 08/04/15 09:20, Markus Neteler wrote:

Hi PSC,

for a better communication, I would suggest to add the string GRASS
GIS under the horizontal line in the logo as a variant of it (so,
e.g. on the main Web site, upper left logo it is not needed).


i.e. something like the central image on the top of:

http://grasswiki.osgeo.org/w/images/GRASSGIS_splash_synthesis.jpg

but without the tag line ?


Any objections?


None.



Which font to use?


I'll leave this to graphically more competent people.

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

Re: [GRASS-PSC] How to modify module folder content in SVN

[Moritz Lennert]

On 22/06/15 11:21, Eva Stopková wrote:

Hi Vasek,

thank you for the advices.

Great news! This means that both are now easily usable for all users
without any special effort. Would you like to do the announcement on
grass-user mailing list? (In case you are not subscribed, I can send
it for you.)

Well, I would prefer to wait with announcement until I will update also
PCL versions (C++). I have done some other changes in the C versions
(e.g. in C kriging also 2D interpolation is available, in C++ not yet).
My first idea was to completely replace PCL version, so I did not modify
them. But then I realized it would be better to save both versions, so
at first I would like to make them as much identical as possible
(funcionality, layout). I intend to do this in the coming days.



Any specific reason why you want to maintain two parallel versions ? 
What is the advantage of the PCL version ?


Generally, I would suggest to maintain only one version...

Thanks for your work on these two very important modules !

Moritz
___
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] [GRASS-dev] RFC 4: Release procedure

[Moritz Lennert]

On 20/10/15 09:18, Martin Landa wrote:

2015-10-20 9:12 GMT+02:00 Martin Landa :

Great, so I'll make a motion on this in the next days unless any
objection pops up before.


it seems that there are no objections :-) Martin


reading it again, I would say that in some cases upcoming RC2 could be
released as final. Eg. for upcoming 7.0.2 we have RC1 released. In two
weeks should become RC2, in this case I can image to release final
instead of RC2. So alternative roadmap could be:

Step 3 (X+30 days) - Hard freeze & RC1
Step 4 - Bug squashing
Step 5 (X+44 days) - Final.

In other words I would make RC2 as optional step only we will need it.
It can happen that two RCs could be overkill. What do you think?


The idea of the RC2 was to provoke some more last-minute testing as some 
fixes might have been introduced after RC1 and I'm not sure how many 
people test the release branch between RC's. This way we make it more 
prominent and can send out a call to everyone to please test RC2. This 
does not mean that RC2 cannot be identical to final. It's just a last 
chance to spot any serious issues.


So, I would plead for leaving it in. 5 days more or less is not that 
much, or ?


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

[GRASS-PSC] relation between GRASS modules and GUI wizards

[Moritz Lennert]

Dear all,

In light of the debate linked to #2402 [1] on the relation between the 
r.in.gdal/v.in.ogr modules and the GUI import wizards, I would like to 
raise this as a fundamental question (and decision) for GRASS.


In my eyes (and I don't think anyone has ever questioned this) one of 
GRASS' major strengths is its modular structure, with GRASS modules as 
basic building blocks that allow to elaborate complex workflows and 
applications. At the same time, this modular structure can be 
intimidating for new users, especially those coming from a GUI environment.


The automatically generated GUIs for each module are already a big step 
towards taking away the fear of using command line.


The wxGUI goes even further and provides a beautiful entry point to 
GRASS modules, adding several, extremely useful, specific GUI elements. 
In order to respect the modular GRASS philosophy, most of these exist as 
standalone gui modules (g.gui.*).


However, in my eyes, the GUI and its tools should be a way to ease 
people in towards the core of GRASS, i.e. its modules, and not a way to 
hide this core. In the case of the import (and export) wizards this is 
the unfortunate effect that we have now: new users are held afar from 
the actual modules, with no easy transition. You either are a power 
user, and you learn about obscure --ui tricks to see the GUI of the 
module, or you are not and then you are not even really supposed to know 
about the modules (and their logic) underlying the wizards.


I find that an unfortunate development.

Yes, some people might sometimes get confused, and some people sometimes 
might be intimidated by some 'advanced' feature, but not all. I teach 
with GRASS every day and I have seen so many different responses that I 
would never categorize new users into one clearly defined group, and so 
I do not think that we should make fundamental interface choices with 
only one specific group of users in mind.


To make a long discussion short:

I propose that we decide once and for all that calling a module by name, 
be it in the terminal window, or in the GUI console or via the menu, 
launches the actual module GUI. If we want to propose specific wizards 
to ease the use of these modules, these should be called as such, and 
not via the module name. _That_ causes confusion for many people in my 
experience. And wizards should not be complete replacements of the GUI 
modules, but offer specific simplifications or added value (such as the 
looping through import calls when importing a directory of files). And 
IMHO, wizards should always offer a path to the original modules behind 
them, in the form of buttons, or at least information.


In the concrete case of the import modules this would mean having the 
entries such as the following in the File menu (example given for raster 
only):


- Import wizard for raster maps (with a button to launch the module GUI)
- Import common formats (r.in.gdal)
- Import common formats with reprojection (r.in.import)

Any thoughts ?

Moritz

[1] https://trac.osgeo.org/grass/ticket/2042
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] GRASS PSC elections in 2016

[Moritz Lennert]

On 03/06/16 12:36, Markus Neteler wrote:

On Fri, Jun 3, 2016 at 11:24 AM, Moritz Lennert
<mlenn...@club.worldonline.be> wrote:
[...]

I would announce the vote (and the procedure) via the mailing lists. That
way completely inactive contributors might not be informed, but that sounds
fine to me.


Yes, makes sense.

As time permits I'll draft an announcement and would like to receive
some proof reading support to avoid that I overlook something.

Still TODO: the number of slots to fill.
We have 3 current PSC members not standing for election and apparently
7 remaining/standing for election.

Do we want another how many being randomly selected? Or 3 is fine for
now and at the next round in 3 years randomly pick 50% or any other
mechanism?


Can't we just have a system where every 3 years we reelect the complete 
PSC, but people can be candidates for their own succession ? I'm not 
sure that there is such a rush of people for this job, but if there is, 
great. Then the election will actually be a real election ;-)


And I think that the risk that the entire PSC will be changed and that 
we find ourselves with a PSC full of newbies is quite low.


So, to summarize, my proposal would be:

- Election of the entire PSC every three years
- All people with SVN access have the right to vote
- Elections are announced on grass-dev and grass-user with a clear 
definition of procedure:
	- Anyone (or anyone with voting right ?) can nominate someone during a 
period of a few (4?) weeks
	- Possibly: those who are already in the PSC and stand for elections 
again do not need a nomination / can nominate themselves ?

- Voting during 1 week
- The ten candidates with the most votes make up the new PSC

Moritz

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

Re: [GRASS-PSC] local community sprint funding

[Moritz Lennert]

On 19/01/16 19:10, Martin Landa wrote:

Dear PSC,

so time ago I started to organize small unofficial GRASS Community
Sprints at my cottage [1,2]. Recently I got idea to make this event
public, see announcement of the next meeting in January 2016 [3,4].

At this point I would like to hear your option whether such events can
be sponzored from our Community Sprint budget. Here is my request [5]
(approx 75EUR).

Waiting for your feedback.


+1
Moritz

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

Re: [GRASS-PSC] local community sprint funding

[Moritz Lennert]

On 15/02/16 15:14, Martin Landa wrote:

Dear all,

2016-01-22 19:58 GMT+01:00 Martin Landa :

Unfortunately we were forced due to health/logistic problems to move
our meeting from January 22-25 to February 5-8. So the request now
lives at [1]. Best regards, Martin


first of all, thanks all of you for the positive feedback! The third
GRASS collaborators meeting in Solany was held in Feb 5-8. The event
has it's own wiki page [1], see participants reports for details [2].
I have prepared spreadsheet similar to past events [3]. The bills are
also attached [4]. The final expenses are a little bit higher that
planned. Approximate was 75EUR, the real expenses: 96.30EUR (three
days for three people). I hope it's OK.



+1 from me.

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

Re: [GRASS-PSC] Procedure to request Community Sprint funding now documented

[Moritz Lennert]

On 17/02/16 00:03, Markus Neteler wrote:

Hi PSC,

here at the current community sprint in S. Michele, Italy, we
discussed a more formal procedure (adopted frrom the FOSSGIS e.V,
www.fossgis.de) approach:

In essence, a written request for funding is needed by compiling a
Wiki page following a template which is then to be sent to the PSC
list for approval or not. For details, see

https://grasswiki.osgeo.org/wiki/Community_Sprint_Funding#Procedure_to_request_Community_Sprint_funding

Comments are of course welcome.


I think it would be necessary to have someoe with overview of the state 
of our finances (who does ?) to give a thumbs up on the request before 
the PSC can vote. Otherwise, we risk voting yes on too many proposals...


Maybe this thumbs up should be noted on the wiki page before the request 
is sent to the list ? Or the people requesting the funding should send 
the request to the financial responsible who then sends on the request 
to the PSC list with additional info about the state of finances.


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

Re: [GRASS-PSC] Procedure to request Community Sprint funding now documented

[Moritz Lennert]

On 18/02/16 11:33, Markus Neteler wrote:

On Thu, Feb 18, 2016 at 10:32 AM, Moritz Lennert
<mlenn...@club.worldonline.be> wrote:
...

I think it would be necessary to have someoe with overview of the state of
our finances (who does ?)


At time everybody :-)

Martin posted the link to the budget table:
https://lists.osgeo.org/pipermail/grass-psc/2016-February/001430.html


to give a thumbs up on the request before the PSC
can vote. Otherwise, we risk voting yes on too many proposals...


OK, I think Martin and me can do that, we check finances regularly anyway.


Maybe this thumbs up should be noted on the wiki page before the request is
sent to the list ?
Or the people requesting the funding should send the
request to the financial responsible who then sends on the request to the
PSC list with additional info about the state of finances.


Well, I get your point.

I could generate a new email alias like e.g. grass-treasu...@osgeo.org
pointing the PSC chair (currently me) and Martin Landa (account
holder) and any other interested PSC member.
Makes sense?


+1

Moritz

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

Re: [GRASS-PSC] funding community meeting in San Michele February 2016

[Moritz Lennert]

On 18/02/16 10:02, Luca Delucchi wrote:

Hi PSC,

I would request funds to support the ongoing community meeting in San
Michele [0].


+1

Moritz

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

Re: [GRASS-PSC] [voting] financial support contributors meeting in San Michele (Feb 2016)

[Moritz Lennert]

On 24/03/16 14:55, Markus Neteler wrote:

Dear PSC,

sorry for the delay on this topic.

On Fri, Mar 11, 2016 at 11:57 PM, Helmut Kudrnovsky  wrote:

Martin Landa wrote

Dear PSC,

I would like to open request to financially support of contributors
meeting (as discussed [1]) held in San Michele in Feb 2016 [2]. The
collected bills [3] covers travel expenses (petrol) and lunch on
Monday 15/2, see overview [4].

I would like to ask the chair (Markus) to officially launch this
voting if possible.

Thanks! Martin

[1] http://lists.osgeo.org/pipermail/grass-psc/2016-February/001442.html
[2] 
http://grasswiki.osgeo.org/wiki/GRASS_GIS_contributors_meetings_in_San_Michele/February_2016
[3] https://drive.google.com/open?id=0B9xu5EldorOPTVlCMng0WXN5VmM
[4] 
https://docs.google.com/spreadsheets/d/1hfSw38SYuY-qb4QllHEql2P4e5CKtedAGY6lA07GWpM/edit?usp=sharing

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa


To me the provided overview looks fine.


I'm no PSC member, I'm 1+.

but I 'm also for communicating early and loudly enough for such events to
attract interested people around nearby the event location.



Of course.
That's why we developed during *this* meeting exactly this Procedure
to request Community Sprint funding
https://grasswiki.osgeo.org/wiki/Community_Sprint_Funding
in order to make it more visible, transparent, organized.

Voting:

+1 for funding the requested expenses of
https://grasswiki.osgeo.org/wiki/GRASS_GIS_contributors_meetings_in_San_Michele/February_2016


+1

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

Re: [GRASS-PSC] [GRASS-dev] Comment regarding PSC election

[Moritz Lennert]

On 26/07/16 00:05, Markus Neteler wrote:

On Mon, Jul 25, 2016 at 11:33 PM, Michael Barton  wrote:

My perspective is that active contributors to the project should vote. How to 
define them is a
more complicated issue and one of the things that prompted the long email chain 
in the PCS IIRC.


Indeed
Additionally, it is *very* complicated to define who is a community member.

Two options yet to consider:

- the ChangeLog contains some references to code contributors without
SVN core access, e.g.

# incomplete "grep":
zgrep -i contributed ChangeLog.gz
  manual: example update (contributed by Vero Andreo)
  (contributed by Paul Kelly, trunk r68308)
  example added (contributed by Vero Andreo) (trunk, r68187)
  (trunk, r67581; contributed by Vero Andreo)
  r67571, r67572 (contributed by Vero Andreo)
  v.krige: updated to rgrass7 - sync to trunk (contributed by
  manual: more examples (contributed by Veronica Andreo)
  of NC example added (contributed by Carol X Garzon-Lopez)
  semi-synthetic NC example added (contributed by Carol X
  example added (contributed by Vero Andreo); msg enhancement
  manual: example expanded (contributed by Vero Andreo)
  (contributed by Aldo Clerici)
  vector/v.to.3d/trans3.c: fix compiler warnings (contributed by
* r.mapcalc/r3.mapcalc: graph2() function added (contributed by
* v.split/segment/parallel manuals: improvements (contributed by
* v.split manual: new NC examples (contributed by Milena
* area_poly1.c function documentation improved (contributed by
  contributed by Martin Landa 
* help page contributed by Trevor Wiens 
* help page contributed by Trevor Wiens 
* EPS output added (contributed by Bruno Caprile, ITC-irst)

In fact, all should have been added here:
https://trac.osgeo.org/grass/browser/grass/trunk/contributors.csv
but that file didn't get updated lately.

Suggestion: updated this file from the ChangeLog and add to the list
of eligible voters. The next PSC may improve the process then.



+ for this as an intermediate solution for now (although for some people 
on the contributors list, I'm not even sure they have svn access as some 
of the names sound like memories from CVS times ;-). I also don't know 
how systematic these mentions of contributors are in the svn logs...


I actually don't think that we are in so much danger of a "hostile 
takeover", so having everyone subscribed to the mailing lists eligible 
to vote does not sound that bad either (possibly with Nikos' suggestion 
of an additional step of having to register as a voter).


If we mirror the way it works in OSGeo, then we would have to define a 
"charter membership" equivalent for the GRASS community which would 
allow to distinguish those that are active in the community, be it as 
developers, documenters, translators, or general advocates.


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

Re: [GRASS-PSC] [GRASS-user] [GRASS-dev] GRASS-GIS PSC-2016 Nominations

[Moritz Lennert]

Dear Nikos,

Thanks for the fine work organizing these elections.

On 16/08/16 14:32, Nikos Alexandris wrote:

Final Update,

the list of candidates consists of 6 ex-PSC members and 7 community
members, developers and power-users as well.


It might be helpful to remind people of the number of slots available. 
On the wiki it says 9. Does that include the chair, or not ?


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

Re: [GRASS-PSC] next PSC task

[Moritz Lennert]

On 18/09/16 20:50, Markus Neteler wrote:

On Sun, Sep 18, 2016 at 8:42 PM, Vaclav Petras  wrote:

On Sun, Sep 18, 2016 at 2:04 PM, Martin Landa 
wrote:


2016-09-18 18:51 GMT+02:00 Markus Neteler :

It was on the recent community sprint agenda, with no real outcome.
We do need a git *expert* for this. Anyone?
However, I believe that this topic is more a technical rather than a
political one which belongs to grass-dev.


I am willing to help with this issue. Probably others will be
interested too, Vaclav? Ma



Yes, to certain extent. However, I think it is not purely technical and it
is coupled with OSGeo and other OSGeo projects.


Right- But the PSC is only involved once the technical aspects are clear.


One of the questions I would think we should think about from the 
beginning is whether we really want to run with a double system (svn and 
git) or whether it might be easier in the long run, to completely switch 
over to git...


Moritz
___
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 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] Jim Westervelt to retire in April: Recognition by PSC / GRASS community ?

[Moritz Lennert]

Le 24 mars 2017 12:40:09 GMT+01:00, "Peter Löwe"  a écrit :
>Dear PSC,
>
>I just learned from Bob Lozar (producer of the GRASS video from 1987)
>that Jim Westervelt has applied to retire. The target is said to be
>April. What could be an appropriate action by the current GRASS
>community and the PSC to acknowledge Jims role as originator of the
>GRASS ?


Brainstorming here:

- honorary member of the grass PSC
- dedicating 7.4 release to him
- all current developers send a picture and we give him a big thank you poster 
with all those pictures

- add your idea here

Moritz

>
>Best,
>Peter
>
>
>___
>grass-psc mailing list
>grass-psc@lists.osgeo.org
>https://lists.osgeo.org/mailman/listinfo/grass-psc
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Genova Community Sprint funding

[Moritz Lennert]

On 27/03/17 00:59, Luca Delucchi wrote:

Dear PSC,

In February there was Genova Community Sprint, I'm sorry the event was
not really a success, with this mail I'm going to ask you the funding
for food, transport and Martin plane.

 Here is our expenses [0]. If you need scanned tickets please let me know

Waiting for your feedback.


I understand that with "not really a success" you mean lack of 
developers present, but in terms of work done by those who were there I 
think it was a success :-)


+1 for funding this, if the our finances allow it.

In the future, we might want to think about a procedure where funding is 
approved before the event based on an approximate budget, so as not to 
have people take the risk of financing an event and then see its funding 
refused afterward...


Moritz


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

Re: [GRASS-PSC] Jim Westervelt to retire in April: Recognition by PSC / GRASS community ?

[Moritz Lennert]

On 24/03/17 13:51, Jeff McKenna wrote:

On 2017-03-24 8:40 AM, "Peter Löwe" wrote:

Dear PSC,

I just learned from Bob Lozar (producer of the GRASS video from 1987) that Jim 
Westervelt has applied to retire. The target is said to be April. What could be 
an appropriate action by the current GRASS community and the PSC to acknowledge 
Jims role as originator of the GRASS ?

What about proposing Jim for the 2017 Sol Katz Award, he is certainly
deserving.



+1

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

Re: [GRASS-PSC] [voting] printing of stickers and flyers for FOSS4G Europe

[Moritz Lennert]

Le 22 juillet 2017 17:14:31 GMT+02:00, Markus Neteler  a 
écrit :
>Dear PSC,
>
>I take liberty to open the voting about reimbursement of Vero Andreo
>for the printing of stickers and flyers for FOSS4G Europe 2017.
>See below for details.
>
>I will start with +1.

+1
Moritz



>-- Forwarded message --
>From: Veronica Andreo 
>Date: Sat, Jul 22, 2017 at 2:42 PM
>Subject: [GRASS-PSC] printing of stickers and flyers for FOSS4G Europe
>To: GRASS-PSC 
>
>
>Dear PSC,
>
>Following Milena's request, I would also like to ask for reimbursement
>of 123 euros for the printing of stickers and flyers for FOSS4G
>Europe. I attach the corresponding invoices.
>
>Some remaining flyers and few remaining stickers were given to Jachym,
>so he takes them to Boston.
>
>Thanks a lot in advance.
>
>Best,
>Vero
>
>___
>grass-psc mailing list
>grass-psc@lists.osgeo.org
>https://lists.osgeo.org/mailman/listinfo/grass-psc
>___
>grass-psc mailing list
>grass-psc@lists.osgeo.org
>https://lists.osgeo.org/mailman/listinfo/grass-psc
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [voting] T-shirts for GRASS GIS Community Sprint at FOSS4G-Europe

[Moritz Lennert]

On 22/07/17 12:39, Martin Landa wrote:

Dear PSC,

I am taking liberty to open voting about reimbursement for the
t-shirts printed for the GRASS GIS Community Sprint which is held
today at FOSS4G-Europe conference. See [1] for details.

I will start with +0 (since I have this t-shirt).


+1

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

Re: [GRASS-PSC] T-shirts for GRASS GIS Community Sprint at FOSS4G-Europe

[Moritz Lennert]

Please all note that Martin has opened a separate thread with [voting] 
in the subject line. I think it would make things easier if everyone 
responded to that thread.


Moritz

On 22/07/17 14:02, Vaclav Petras wrote:

+1 from Vaclav

On Sat, Jul 22, 2017 at 8:00 AM, Anna Petrášová 
> wrote:


+1 from Anna

On Sat, Jul 22, 2017 at 6:47 AM, "Peter Löwe" > wrote:
 > +1
 > Peter
 > --
 > Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX
Mail gesendet.
 > Am 22.07.17, 12:40, Martin Landa > schrieb:
 >>
 >> Hi,
 >>
 >> 2017-07-22 11:43 GMT+02:00 Milena Nowotarska
>:
 >> > I would like to ask you for reimbursement for the t-shirts
printed for
 >> > the
 >> > GRASS GIS Community Sprint which will be held today at
FOSS4G-Europe
 >> > conference. I have printed 10 t-shirts for 466,50 PLN and
there is a
 >> > need to
 >>
 >> it's about 110EUR [1], right? I have started voting thread [2].
 >>
 >> Ma
 >>
 >> [1] https://themoneyconverter.com/PLN/EUR.aspx

 >> [2]
https://lists.osgeo.org/pipermail/grass-psc/2017-July/001737.html

 >>
 >> --
 >> Martin Landa
 >> http://geo.fsv.cvut.cz/gwiki/Landa

 >> http://gismentors.cz/mentors/landa

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

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

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





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



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

Re: [GRASS-PSC] Let's approve new core developers

[Moritz Lennert]

On 21/06/17 14:58, Markus Neteler wrote:

On Fri, Jun 16, 2017 at 8:38 AM, Markus Neteler <nete...@osgeo.org> wrote:

On Thu, Jun 15, 2017 at 6:31 PM, Moritz Lennert
<mlenn...@club.worldonline.be> wrote:
...

Does anyone have someone they want to propose as core developer ?


Yes: I would like to propose Veronica Andreo
(https://veroandreo.wordpress.com ;
https://www.researchgate.net/profile/Veronica_Andreo2).

For a long time, she is continuously contributing to GRASS GIS, a
great (T)GRASS power user and likely to contribute a better
documentation and more.
Granting core write access to her would enables her to collect
contribution related "credits" directly rather than through indirect
"on behalf of someone" commit messages.
I am sure that she'd be careful when committing and, thanks to the
revision system things are peer reviewed (via
https://lists.osgeo.org/pipermail/grass-commit/) and adjustable
anyway.


Since yet missing, I vote myself with a +1.

Result:

* Anna Petrasova +1
* Helena Mitasova +1
* Margherita Di Leo +1
* Markus Neteler +1
* Martin Landa +1
* Michael Barton  +1
* Moritz Lennert +1
* Peter Löwe +1
* Vaclav Petras +1

I hereby declare the motion as passed.

@Vero: I'll activate your account in SVN for GRASS GIS core.


"Welcome" Vero !!! :-)

I have one question concerning procedure: I don't think it mattered for 
this vote, but in general wouldn't it be more appropriate use some form 
of "secret" ballots for votes concerning persons ?


Moritz


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

Re: [GRASS-PSC] [voting] T-shirts funding

[Moritz Lennert]

Le 5 juin 2017 02:58:20 GMT+02:00, "Anna Petrášová"  a 
écrit :
>Hi PSC,
>
>As discussed offlist, we would like to get funding for the T-shirts
>given as a present to GRASS GIS original founders. We purchased 12
>T-shirts for $131.50, we gave them 3 and we plan to sell the rest for
>$10 to whomever we meet at conferences. Therefore we would like to
>request $41.50 from GRASS budget [1], 


+1

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

Re: [GRASS-PSC] Let's approve new core developers

[Moritz Lennert]

On 15/06/17 10:54, Markus Neteler wrote:

HI PSC,

On Tue, Jun 13, 2017 at 8:59 AM, Markus Neteler  wrote:

PSC,

we didn't invite new core developers for a while, I think this should
be done asap.

Again a somewhat sensitive topic, how shall we proceed? I have some
ideas but did not approach those people yet.

Open discussion without names :-)


ok.. given the "wild" discussion, perhaps a different procedure is desired?


I don't really think so. I think we should make this much more concrete. 
Does anyone have someone they want to propose as core developer ? 
Personally, I think that this should just happen naturally, with 
possibly a more proactive call (like yours) once in a while.


Do you have anyone specific in mind ? Who are the people who have 
contributed much in the form of addons ?


I think that anyone who has a candidate should just propose to the PSC, or ?


Like:
- propose and go for voting? Note that according to RFC1 [1] + the
HwoToContribute [2] we need to vote for a new core developer;
- migrate to git and no more need to use this procedure?


That will probably still take some time, so I think that if there are 
candidates we should invite them now.


But as you say, git might help incite more people to "just" contribute...

Moritz

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

Re: [GRASS-PSC] Let's approve new core developers

[Moritz Lennert]

Le 16 juin 2017 08:41:59 GMT+02:00, Martin Landa  a 
écrit :
>Hi,
>
>2017-06-16 8:38 GMT+02:00 Markus Neteler :
>> Yes: I would like to propose Veronica Andreo
>> (https://veroandreo.wordpress.com ;
>> https://www.researchgate.net/profile/Veronica_Andreo2).
>
>+1 Martin

+1 

Moritz

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

Re: [GRASS-PSC] Again: Jim Westervelt retirement: May 2017

[Moritz Lennert]

On 01/05/17 17:07, Vaclav Petras wrote:


On Mon, May 1, 2017 at 10:00 AM, Anna Petrášová
> wrote:


Vaclav and I are going to be at the University of Illinois at
Urbana-Champaign between 15-20th of May, so we could potentially
deliver it in person.  T-shirt with the GRASS ASCII logo would look
great I think, the problem is we would have to order it now and it
might be quite costly, because they usually require minimum number of
T-shirts, and we are not sure about the right size. It would be great
though to have those T-shirts for conferences, so we can look into
some options.


The T-shirts are usually around $20, but Allied Shirts have a sale right
now. I don't recall seeing T-shirt of this brand, so I can't comment on
it. Anyway, with the ASCII design (which has just one color) we get to
$101.15 total when ordering 12 of them ($8.43 per T-shirt). For one
T-shirt it is $20 (it seems one can order it this way, but I'm not sure)
and $15 ea for 4 T-shirts. All T-shirts must be one color (and there is
limited selection), but they can be different sizes and for the lower
prices per T-shirt still apply. Also all T-shirts must be one type -
Budget (friendly) Unisex in this case. The size chart is available [1].
A screenshot of the design is attached (created at alliedshirts.com
). We may need to pay extra for rush delivery.
Â

We could also do something smaller, e.g., collect signatures and put
them on a card.


This is nice. It is personal and it has no potential collisions with
ones fashion style. If somebody creates the design and collects the
signatures, we can print it (although I don't know where yet) and
deliver it.


I really like this t-shirt proposal. I think that $20 for one t-shirt is 
great, and think that having a single edition just for him would be a 
nice gesture, but I would be willing to buy a t-shirt if you decide to 
make more.


Just a reminder: this is a publicly archived maling list, so not sure if 
we should discuss all this here ;-)


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

Re: [GRASS-PSC] Let's approve new core developers

[Moritz Lennert]

On 30/09/17 21:23, Markus Neteler wrote:

PSC,

On Tue, Jun 13, 2017 at 8:59 AM, Markus Neteler  wrote:

PSC,

we didn't invite new core developers for a while, I think this should
be done asap.

Again a somewhat sensitive topic, how shall we proceed? I have some
ideas but did not approach those people yet.

Open discussion without names :-)


Time for a new round!
We have great Addon developers, power users and more.

Let's get more people directly involved, i.e. grant write access to trunk.

Opinions?


It would be great to have some more C developers. I have the feeling 
that the balance is tipping more and more towards Python expertise, 
while most of the code is C...


Moritz

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

Re: [GRASS-PSC] sponsorship by stickermule

[Moritz Lennert]

On 24/08/17 17:32, Veronica Andreo wrote:

Dear PSC,

Following up with promotional material printing (esp. stickers), Vashek 
found that stickermule [0] has a sponsorship "program" for Open Source 
projects [1]. Since along with Vincent and Brendan [in cc], we were 
discussing about stickers, different options available and 
possibilities, I wrote to stickermule people on behalf of GRASS GIS 
asking what did this sponsorship consisted of and if they were 
interested to sponsor us. They offered to give us 1000 stickersheets (4" 
x 6") [2] in exchange of adding their name in grass sponsors page [3] 
(btw, maybe that page needs update).


Anyway, I told them we would bring the issue to PSC and then contact 
them back. If we go for yes, we still need to decide what we will put in 
those stickersheets [2]. Brendan had some "powered by GRASS GIS" 
designs, as well as Vincent, but both agreed to work on new ideas (guys, 
please correct me if I'm wrong, and add any info I migth be missing :))


What do you think?


Generally +1 from my side.

But I agree that we have to rework our sponsorship page (possibly in 
link with the current osgeo web site update ?).


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

Re: [GRASS-PSC] GRASS add-on sharing and write access

[Moritz Lennert]

[CC'ing grass-dev where such discussion should be happening]

On 17/12/17 22:37, Markus Neteler wrote:

On Sun, Dec 17, 2017 at 9:14 PM, Markus Metz
 wrote:
...

Right now, r.drain is somewhat overloaded: it creates directions for a DEM
same way r.fill.dir does it, or it uses supplied directions, then the module
extracts least costly paths. I suggest to have a new module r.path that
extracts extract least costly paths from input directions and start points
and mark r.drain as deprecated.


Sounds interesting! At time it is a bit confusing.


+1

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

Re: [GRASS-PSC] Some Web page updates

[Moritz Lennert]

On 21/05/18 16:57, Markus Neteler wrote:

Hi PSC,

given the new EU GDPR [1] coming into force on 25th of May 2018 I have
updated the privacy statements in the main GRASS GIS web site and in
the Wiki (the latter inspired by the respective Wikipedia pages). I
have also changed all mailman list admin entries from myself to
"grass-admin at osgeo.org" reflector. Whom else than me may I add to
this reflector?



You can put me, but what does this entail ?

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

Re: [GRASS-PSC] [motion] Bonn Community Sprint funding

[Moritz Lennert]

+1

Moritz

Am 18. Mai 2018 18:02:06 MESZ schrieb Helena Mitasova :
>+1
>
>Helena
>
>> On May 18, 2018, at 11:11 AM, Martin Landa 
>wrote:
>> 
>> Hi,
>> 
>> I am taking liberty to start motion thread related to GRASS Community
>> Sprint in Bonn [0,1] organized as part of the OSGeo Code Sprint [2].
>> Our goal is to cover at best all participants travel and
>accommodation
>> expenses expressed in [3] from our GRASS Budget [4].
>> 
>> I will start with +0 since I am also asking for funding as one of
>participants.
>> 
>> Thanks for your feedback, Ma
>> 
>> [0]
>https://grass.osgeo.org/news/75/15/Recap-from-the-OSGeo-Code-Sprint-in-Bonn-2018/
>> [1]
>https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Bonn_2018
>> [2] https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018
>> [3]
>https://docs.google.com/spreadsheets/d/1BgFMiYlLosFjsVUlUCWwssoxiQB_G7gpkVFgG29gZBM/edit?usp=sharing#gid=5
>> [4] https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2018
>> 
>> -- 
>> Martin Landa
>> http://geo.fsv.cvut.cz/gwiki/Landa
>> http://gismentors.cz/mentors/landa
>> ___
>> grass-psc mailing list
>> grass-psc@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-psc
>
>Helena Mitasova
>Professor at the Department of Marine, 
>Earth, and Atmospheric Sciences
>Associate director and faculty fellow at the Center for Geospatial
>Analytics
>North Carolina State University
>Raleigh, NC 27695-8208
>hmit...@ncsu.edu
>http://geospatial.ncsu.edu/osgeorel/publications.html
>
>
>"All electronic mail messages in connection with State business which
>are sent to or received by this account are subject to the NC Public
>Records Law and may be disclosed to third parties.” 
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Fwd: Write access request to the GRASS-Addons-SVN repository

[Moritz Lennert]

On 07/06/18 10:42, Anika Bettge wrote:

Hi,

I am Anika Bettge,
I'm working by mundialis for Markus Neteler.
Since r.in.lidar does not work on my maschnie, I wrote the
GRASS GIS addon r.in.pdal which is desired by ticket
#3515 Wish: Raster binning of lidar data using PDAL -r.in.pdal
(https://trac.osgeo.org/grass/ticket/3515).


Cool ! Looking forward to trying it out.

Thanks, Anika !

Moritz

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

Re: [GRASS-PSC] Fwd: [Board] Budgeting project event support for 2018

[Moritz Lennert]

Le 20 octobre 2017 17:11:51 GMT+02:00, Markus Neteler  a 
écrit :
>Hi PSC,
>
>I think we should ask for more for 2018 which implies that we develop a
>spending plan. This is a bit overdue :)
>
>Your comments are welcome!

I think it might be good to plan at least one developer meeting per year, like 
the one Vero just proposed and to be able to pay some of the accommodation/food 
costs (obviously trying to find free or cheap solutions if possible) and maybe 
help one or two developers from further away to pay the trip. 

Plus participation in one OSGEO code sprint, again trip / accommodation. So 
maybe we should aim for +/- 3000 ?

Moritz


>
>Markus
>-- Forwarded message --
>From: "Anita Graser" 
>Date: Sep 26, 2017 10:32 PM
>Subject: [Board] Budgeting project event support for 2018
>To: "OSGeo-Board" 
>Cc:
>
>Hi,
>>
>> Last year, we asked the all projects to help us budget for
>preject-related
>> events. The feedback (before consolidation) was (
>> https://wiki.osgeo.org/index.php?title=OSGeo_Budget_2017=104525
>> ​)​
>> GRASS 1,500 code sprint
>> QGIS 2,000 3,000 1x developer meeting & 1x user conference
>> GeoServer 1,500 2,000 1x developer meeting / sprint
>> ZOO-Project 2,000 code sprint
>> OpenLayers 2,000 code sprint
>> MapServer 5,000 code sprint (and possibly assist in travel)
>> PyWPS code sprint, see request details http://osgeo-org.1560.
>> x6.nabble.com/PyWPS-winter-code-sprint-td5283188.html
>> GeoMOOSE 3,000 GeoMOOSE presence in at least three regional
>conferences,
>> generation of OSGeo-Live USB Thumbdrives for handout at conferences
>and
>> other project participation events, seed funding for at least one
>GeoMOOSE
>> code Sprint and at least one GeoMOOSE workshop
>> pycsw 2,000 code sprint
>>
>> We finally budgeted 17,500. How does this compare to the actual
>spending
>> this year?
>>
>> If you agree, I'll go ahead and ask our projects to provide input for
>next
>> year's budget. This way, the incoming board will already have the
>> information they need to start planning.
>>
>> Regards,
>> Anita
>>
>>
>>
>>
>>
>> ___
>> Board mailing list
>> bo...@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/board
>>
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [Motion] Proposing Stefan Blumentrath as a new core developer

[Moritz Lennert]

+1

Moritz

On 30/01/18 23:02, Markus Neteler wrote:

I turn this into a motion:

On Tue, Jan 30, 2018 at 10:48 PM, Markus Neteler  wrote:

PSC,

I pick up a recent suggestion on grass-dev, to invite Stefan
Blumentrath as a core developer.

All of you will know him (virtually or in person):
- https://www.osgeo.org/member/blumentrath/
- https://github.com/ninsbl

He is continuously contributing to various parts of the source code
through others (see ChangeLog).

I asked him off-list and he's interested to join the core team with
write access.

According to RFC1 [1] we all need then to vote here once a motion is
made. Optionally I can make this a motion right away.


+1 Markus



Best,
Markus


[1] https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines

--
Markus Neteler, PhD
http://www.mundialis.de - free data with free software
http://grass.osgeo.org
http://courses.neteler.org/blog

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




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

Re: [GRASS-PSC] [GRASS-dev] planning releases - spring 2018

[Moritz Lennert]

Am 25. März 2018 12:32:24 MESZ schrieb Martin Landa :
>Dear all,
>
>2018-02-27 22:14 GMT+01:00 Martin Landa :
>> major release 7.4.0 is almost one month old, we should think about
>> time schedule for a next releases. Assuming that we are trying to
>> release new (point) version every three/four months, 7.4.1 could be
>> schedule to May [1].
>> [1] https://trac.osgeo.org/grass/milestone/7.4.1
>
>I would propose based on planned time schedule soft freeze starting by
>tomorrow (Mon 26/3).


+1

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

Re: [GRASS-PSC] Figures/numbers describing the increase of GRASS modules / Addons over time ?

[Moritz Lennert]

Le Sun, 18 Mar 2018 12:17:04 +0100,
"Peter Löwe"  a écrit :

> Dear PSC,
> 
> I'm currently working on a poster about GRASS as a project (Research
> Data Alliance conference): Do we already have numbers/figures/tables
> summarizing the total growth of GRASS modules / addons over the
> years ?

For the addons, I've tried to keep a list up to date in the release
news:

7.0 -> 7.2:
https://trac.osgeo.org/grass/wiki/Release/7.2.0-News#NewAddons
7.2 -> 7.4:
https://trac.osgeo.org/grass/wiki/Release/7.4.0-News#NewAddonssinceGRASS7.2.0

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

Re: [GRASS-PSC] [Motion] Print 500 GRASS GIS stickers for the upcoming conferences

[Moritz Lennert]

On 27/02/18 23:38, Markus Neteler wrote:

hi PSC,

since printing needs time, here my motion to approve 150 USD for
printing 500 stickers, die cut, 2x2" through stickermule.

The current budget plan foresees more than that sum for stickers, so
that would be in line with our planning:
https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2018



+1

Moritz

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

Re: [GRASS-PSC] Enabling FAIR Data project commitment statement: Feedback, please.

[Moritz Lennert]

Hi Peter,

On 21/09/18 09:12, "Peter Löwe" wrote:

Dear PSC members,
I would like to ask you for feedback regarding the proposal from September 
10th, to sign the online commitment statement of the Enabling FAIR Data project 
on behalf of the GRASS GIS project.

Is a motion for this needed/appropriate ?


I have no specific objections to signing the commitment statement, but I 
am wondering: does the GRASS PSC qualify as an organisation ? We do not 
have any legal status.


Moritz


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

Re: [GRASS-PSC] [Board] quick project status check and response to budget inquiry

[Moritz Lennert]

On 19/01/19 23:56, Helena Mitasova wrote:

Jody,

by no response do you mean no response to the budget request?

GRASS has been preparing the request (I am on PSC) and I asked the PSC to 
submit the request - if it has not come yet, I can submit it - the draft budget 
is here
https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2019#Planned_Expenses

we have a larger than usual item there - we need help to cover the cost of 
GRASS website update,
so we had some discussion about doing some fundraising to help out with that so 
that might have caused the delay. I can put the request on the board budget 
wiki if there are no objections from the rest of GRASS PSC,



+1 from me.

Sorry, have been extremely busy at work and outside in the last months 
and have not been able to be as active as I would have liked.


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

Re: [GRASS-PSC] GRASS GIS Budget 2019 - draft

[Moritz Lennert]

On 20/01/19 21:06, Markus Neteler wrote:

On Thu, Jan 17, 2019 at 2:50 PM Helena Mitasova  wrote:


Please, prepare the budget for as much as we really need ($9000) with solid 
explanation and a committment to do fundraising for the website.


Working on it with Vero.

Important: we request 9000 USD - note that our
https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2019 is in EUR! As
of today, that would be 10.235 USD.

Since we plan a fundraising campaign (any volunteer to lead that?) we
can hopefully fill the delta.


I would be willing to be part of a team for this, but rather not alone 
because of the load at work for the moment.


Should we include our fundraising target as part of the 2019 budget ?




This budget request is just to allocate money in the osgeo budget and see what 
the needs are - no money is distributed at this time so we will get some 
feedback on what can be funded. The board budget discussion is on Monday so it 
would be good to submit the request asap.


It is now updated in the OSGeo wiki:
https://wiki.osgeo.org/wiki/OSGeo_Budget_2019#OSGeo_Projects

The request to the board still has to be written, I suppose (can do
that later tonight).


Great thanks ! I am busy writing a research proposal tonight, so can't 
really help.



PS: Martin, Moritz: what were the bank fees? Pls add to our budget.


There should normally not be any bank fees.

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

Re: [GRASS-PSC] [MOTION] Write access to the GRASS-SVN repository Ondřej Pešek

[Moritz Lennert]

+1

Moritz

Am 20. Januar 2019 00:44:35 MEZ schrieb Markus Neteler :
>Dear PSC,
>
>please vote (in a timely manner) on granting GRASS-core write access
>to Ondřej Pešek:
>
>On Sat, Jan 12, 2019 at 8:53 PM Markus Neteler 
>wrote:
>> On Thu, Jan 10, 2019 at 11:37 AM Ondřej Pešek
> wrote:
>> >
>> > Dear GRASS,
>> >
>> > I already have the access to GRASS addons repository (mainly
>because of my master's thesis [1]), but with my Ph.D. supervisor Martin
>Landa we decided that it might be useful to have the access also to
>normal trunk. Now, I mostly work on the modeler (parameterization in
>the Python export [2], which should be followed by still-not-finished
>PyWPS export [3] - but before this one, we should wait for one
>GRASS-related fix in PyWPS) and I test some python3 functionalities
>with my ANN AddOns.
>> >
>> > I have read and accepted the legal aspects of code contributions
>(RFC2).
>> >
>> > My osgeo_id is "pesekon2".
>> >
>> > Many thanks for considering my request,
>> >
>> > Kind regards,
>> >
>> > Ondrej Pesek
>> >
>> > [1]
>https://trac.osgeo.org/grass/browser/grass-addons/grass7/imagery/i.ann.maskrcnn
>> > [2] https://trac.osgeo.org/grass/ticket/3669
>> > [3] https://github.com/ctu-yfsg/2017-d-grass-modeler-pywps
>>
>> Thanks for your request!
>>
>> According to RFC1 [1] and "HowToContribute" [2] we need to vote for a
>> new core developer [3].
>> I have added this topic to the PSC Agenda [4].
>>
>> Motion timeline:
>> - proposal published: 12 Jan 2019
>> - voting to be opened on 19 Jan 2019
>
>I start with a
>+1
>
>Markus
>
>> [1]
>https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines
>> [2]
>https://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheMainGRASS-SVNrepository
>> [3] https://trac.osgeo.org/grass/wiki/RFC/3_PSCVotingProcedures
>> [4] https://trac.osgeo.org/grass/wiki/PSC/Agenda
>___
>grass-psc mailing list
>grass-psc@lists.osgeo.org
>https://lists.osgeo.org/mailman/listinfo/grass-psc
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] Publicity about donations ?

[Moritz Lennert]

Dear all,

Yesterday we received a donation of 10,00€ from someone, with the message:

>Thanks for your work! just a little contribution for GrassGIS >development

What do you think: should we send a public thank you for every donation 
received to the grass-user mailing list ? Should we create a list of 
names of all donors in the current year ?


If we decide to do some publicity, we should add something like

"All donors are listed at http://XXX.CCC [or: All donors are announced 
on the grass-user list]. If you prefer to remain anonymous, please say 
so explicitely in the message accompanying your donation."


at

https://grass.osgeo.org/donations/

Any opinions ?

Moritz


 Forwarded Message 
Subject:You've received a contribution to your Money Pool
Date:   Mon, 14 Jan 2019 09:31:47 -0800
From:   serv...@paypal.be 
To:     Moritz Lennert 



You've received a contribution to your Money Pool
Moritz Lennert, you've received 10,00 EUR

    

Hello, Moritz Lennert.






PayPal  








Chiara Audisio sent you 10,00 EUR.

Note from Chiara Audisio:

quote 	Thanks for your work! just a less contribution for GrassGIS 
development 	quote


Transaction Details

Transaction ID: 8MK29770SK2545030   14 January 2019

   Amount received


10,00 EUR

Don't see the money in your account?
Don't worry. Sometimes it takes a few minutes for it to show up.

If you'd like to extend the duration of your Money Pool, or edit the 
Money Pool details, log in to your PayPal account and select your Money 
Pool.


Check your Money Pool details to see how much you've collected so far by 
visiting https://paypal.me/pools/campaign/109820698851547347


To spend the money, simply log in to your PayPal account and transfer 
the Money Pool balance to your PayPal primary balance.


Go to PayPal 
<https://www.paypal.com/?ppid=PPC000955=BE=en_BE(en_AT)=SBGLHS6BNU57S=40a73360-1822-11e9-9aa3-d4856454d6a8==ed2dbe05dc204=ed2dbe05dc204=ed2dbe05dc204_tpcid=sendmoney-receiver=main:email=main:email=op=em=ci=sys> 



Get the Details 
<https://www.paypal.com/myaccount/transaction/details/8MK29770SK2545030?ppid=PPC000955=BE=en_BE(en_AT)=SBGLHS6BNU57S=40a73360-1822-11e9-9aa3-d4856454d6a8==ed2dbe05dc204=ed2dbe05dc204=ed2dbe05dc204_tpcid=sendmoney-receiver=main:email=main:email=op=em=ci=sys> 






PayPal  

Help & Contact 
<https://www.paypal.com/selfhelp/home?ppid=PPC000955=BE=en_BE(en_AT)=SBGLHS6BNU57S=40a73360-1822-11e9-9aa3-d4856454d6a8==ed2dbe05dc204=ed2dbe05dc204=ed2dbe05dc204_tpcid=sendmoney-receiver=main:email=main:email=op=em=ci=sys> 
  | Security 
<https://www.paypal.com/be/webapps/mpp/paypal-safety-and-security?ppid=PPC000955=BE=en_BE(en_AT)=SBGLHS6BNU57S=40a73360-1822-11e9-9aa3-d4856454d6a8==ed2dbe05dc204=ed2dbe05dc204=ed2dbe05dc204_tpcid=sendmoney-receiver=main:email=main:email=op=em=ci=sys> 
  | Apps 
<https://www.paypal.com/be/webapps/mpp/mobile-apps?ppid=PPC000955=BE=en_BE(en_AT)=SBGLHS6BNU57S=40a73360-1822-11e9-9aa3-d4856454d6a8==ed2dbe05dc204=ed2dbe05dc204=ed2dbe05dc204_tpcid=sendmoney-receiver=main:email=main:email=op=em=ci=sys> 





twitter 
<https://twitter.com/PayPal?ppid=PPC000955=BE=en_BE(en_AT)=SBGLHS6BNU57S=40a73360-1822-11e9-9aa3-d4856454d6a8==ed2dbe05dc204=ed2dbe05dc204=ed2dbe05dc204_tpcid=sendmoney-receiver=main:email=main:email=op=em=ci=sys> 
	instagram 
<https://www.instagram.com/paypal/?ppid=PPC000955=BE=en_BE(en_AT)=SBGLHS6BNU57S=40a73360-1822-11e9-9aa3-d4856454d6a8==ed2dbe05dc204=ed2dbe05dc204=ed2dbe05dc204_tpcid=sendmoney-receiver=main:email=main:email=op=em=ci=sys> 
	facebook 
<https://www.facebook.com/PayPalUSA?ppid=PPC000955=BE=en_BE(en_AT)=SBGLHS6BNU57S=40a73360-1822-11e9-9aa3-d4856454d6a8==ed2dbe05dc204=ed2dbe05dc204=ed2dbe05dc204_tpcid=sendmoney-receiver=main:email=main:email=op=em=ci=sys> 
	linkedin 
<http://www.linkedin.com/company/1482?trk=tyah=PPC000955=BE=en_BE(en_AT)=SBGLHS6BNU57S=40a73360-1822-11e9-9aa3-d4856454d6a8==ed2dbe05dc204=ed2dbe05dc204=ed2dbe05dc204_tpcid=sendmoney-receiver=main:email=main:email=op=em=ci=sys> 





*How do I know this is not a Spoof email?*

PayPal is committed to preventing fraudulent emails. Emails from PayPal 
will always contain your full name. Spoof or "phishing" emails tend to 
have generic greetings such as "Dear PayPal member".


To learn more, go to the PayPal website and click *Security*.





Please don't reply to this email. To get in touch with us, click *Help & 
Contact 
<https://www.paypal.com/selfhelp/home?ppid=PPC000955=BE=en_BE(en_AT)=SBGLHS6BNU57S=40a73360-1822-11e9-9aa3-d4856454d6a8==ed2dbe05dc204=ed2dbe05dc204=ed2dbe05dc204_tpcid=sendmoney-receiver=main:email=main:email=op=em=ci=sys>*.






Copyright © 1999-2019 

Re: [GRASS-PSC] GRASS GIS Budget 2019 - draft

[Moritz Lennert]

On 5/01/19 15:26, Markus Neteler wrote:

Hi,

On Fri, Jan 4, 2019 at 6:06 PM Martin Landa  wrote:

pá 4. 1. 2019 v 17:51 odesílatel Moritz Lennert  
napsal:

I would suggest something very simple such as:

https://lite.framacalc.org/rtaam2nzg3

where we just note all income as positive and expenditures as negative
numbers to get automatic balance.


Nice :-) Martin


Looks nice but how to protect from random vandalism?



Yes, this is only for proof-of-concept. If we want a publicly available, 
but read-only spreadsheet we will have to go to a provider offering a 
password-protected solution.


The other option would be to see with OSGeo whether the provision of 
some only accounting software within the OSGeo infrastructure would be 
worth the effort, now that more projects are into the money-raising 
business and OSGeo distributes funds to projects systematically. Sounds 
like a perfect use-case of shared ressources within an umbrella 
organisation to me.


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

Re: [GRASS-PSC] GRASS GIS Budget 2019 - draft

[Moritz Lennert]

On 6/01/19 12:19, Markus Neteler wrote:

(I have taken liberty to re-copy your answer into the original thread
- @vero: through enabling "mime digest" in your list settings you
should get the emails in a better way)

On Sat, Jan 5, 2019 at 4:36 PM Veronica Andreo  wrote:

Hi

[...]


Well, I don't think the actual amount spent for travel grants was

2957.28€, as IIRC, Nikos never claimed his 225.00€, so total expenses
would be 2838.28€, and so we should have

3630.74€ - 2838.28€ = 792,46€

left. On the bank account we have 887,46€, so either some reimbursements
still need to happen (but I'm not aware of any), or there is some error
in the calculations somewhere.



I was not reimbursed either, but instead donated that for beers next time :)
(IIRC, was something like 90 euros or so from train tickets)


Thanks - we should keep track of that as well!


This actually reduces our accounting error to about 5€ (negative now, 
i.e. 5 € are not accounted for), which is probably an acceptable error rate.


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

Re: [GRASS-PSC] GRASS GIS Budget 2019 - draft

[Moritz Lennert]

On 19/12/18 15:07, Moritz Lennert wrote:

On 18/12/18 21:54, Markus Neteler wrote:

Hi PSC,

I have drafted a new Wiki page at
https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2019

... to be done in the Wiki page:
- what is the surplus of 2018? (Martin or Moritz?) - please add


The current amount in the bank account is 1159,61€, but I think Martin
has never been reimbursed for the 2018 Sprint as I never received the
bank account info.


After having reimbursed Martin, the current amount in the bank account 
is 887,46.





I don't know if the amount on the bank account is to be considered a
"surplus". For that we would need the detailed accounts of 2018, not
only the planned expenses as currently in [1].

Looking at what we had left at the end of 2017 (1592,85€ according to
[1]), this would mean that we actually have a negative balance of
1159,61€ - 1592,85€ = −433,24€, if what is on the bank account is all
that is left (i.e. no other sums lying somewhere else).


As the 1592.85€ were not put onto the current bank account, I suppose 
that they have been spent completely, but I don't know. Where was this 
money located "physically", only in Martin's bank account, or is there 
some money somewhere else, maybe in the US ?


The current bank account's only income were 2000€ Euro apparently 
received from OSGeo. In the Sprint 2018 account's [1] I see that a bit 
over 2700€ were supposed to be reimbursed (IIRC, Nikos did not claim 
reimbursement), so we did spend more than we received for this sprint.


I think we probably need some more structured general accounting, not 
only ad-hoc for different events, and not only on the wiki. At least 
some spreadsheet listing income and spending. Or does this already exist 
somewhere ?


Moritz


[1] 
https://docs.google.com/spreadsheets/d/1BgFMiYlLosFjsVUlUCWwssoxiQB_G7gpkVFgG29gZBM/edit#gid=607358029

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

Re: [GRASS-PSC] GRASS GIS Budget 2019 - draft

[Moritz Lennert]

On 4/01/19 17:22, Martin Landa wrote:

Hi,

pá 4. 1. 2019 v 16:25 odesílatel Moritz Lennert
 napsal:

As the 1592.85€ were not put onto the current bank account, I suppose
that they have been spent completely, but I don't know. Where was this
money located "physically", only in Martin's bank account, or is there
some money somewhere else, maybe in the US ?


money have been located at my Fio bank account and my PayPal account.
Fio bank account has been canceled and my PayPal account is currently
on zero.


The current bank account's only income were 2000€ Euro apparently
received from OSGeo. In the Sprint 2018 account's [1] I see that a bit
over 2700€ were supposed to be reimbursed (IIRC, Nikos did not claim
reimbursement), so we did spend more than we received for this sprint.


Based on [1] and [2,3]:

  3630.74 -  3063.28 = 567.46

Or I am wrong?


Well, I don't think the actual amount spent for travel grants was 
2957.28€, as IIRC, Nikos never claimed his 225.00€, so total expenses 
would be 2838.28€, and so we should have


3630.74€ - 2838.28€ = 792,46€

left. On the bank account we have 887,46€, so either some reimbursements 
still need to happen (but I'm not aware of any), or there is some error 
in the calculations somewhere.





I think we probably need some more structured general accounting, not
only ad-hoc for different events, and not only on the wiki. At least


I completely agree.


I would suggest something very simple such as:

https://lite.framacalc.org/rtaam2nzg3

where we just note all income as positive and expenditures as negative 
numbers to get automatic balance.


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

Re: [GRASS-PSC] GRASS GIS Budget 2019 - draft

[Moritz Lennert]

On 13/01/19 23:54, Martin Landa wrote:

Hi,

ne 13. 1. 2019 v 23:28 odesílatel Markus Neteler  napsal:

3630.74€ - 2838.28€ = 792,46€

I was not reimbursed either, but instead donated that for beers next time :)
(IIRC, was something like 90 euros or so from train tickets)


if I count well

Bonn: 2732.28 -99.70->2632.58 ([1] updated)


This actually reduces our accounting error to about 5€ (negative now,
i.e. 5 € are not accounted for), which is probably an acceptable error rate.


3630.74 -(2632.58+106) -> 892.16


left. On the bank account we have 887,46€, so either some reimbursements


I took liberty to updated also [2].

Moritz, please check, feel free to correct.


I've added to [1] the small amount that is unaccounted for in order to 
get as surplus from 2018 in [2] the exact amount on the bank account.


So to my best knowledge we now have correct accounts.

Moritz



Thanks, Martin

[1] https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2018#Expenses
[2] https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2019#Income




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

Re: [GRASS-PSC] GRASS GIS Budget 2019 - draft

[Moritz Lennert]

On 18/12/18 21:54, Markus Neteler wrote:

Hi PSC,

I have drafted a new Wiki page at
https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2019

... to be done in the Wiki page:
- what is the surplus of 2018? (Martin or Moritz?) - please add


The current amount in the bank account is 1159,61€, but I think Martin 
has never been reimbursed for the 2018 Sprint as I never received the 
bank account info.


I don't know if the amount on the bank account is to be considered a 
"surplus". For that we would need the detailed accounts of 2018, not 
only the planned expenses as currently in [1].


Looking at what we had left at the end of 2017 (1592,85€ according to 
[1]), this would mean that we actually have a negative balance of 
1159,61€ - 1592,85€ = −433,24€, if what is on the bank account is all 
that is left (i.e. no other sums lying somewhere else).



- since 2016, we have some offlist we-need-a-new-web-site discussion
(see below), some figure added
- decide about community sprint in Bucarest at FOSS4G (a no-brainer I think :-)
- decide about other sprints throughout the year


I think a second sprint somewhere in February/March would be nice. Is 
there a general OSGeo Sprint planned again ? If the information in the 
"Planned expenses" table in [1] is correct, we should probably aim at 
something like 2500-3000€ if this is possible.



- your ideas


Proposal: Web site update

For years we have a CMS with a style which does not really support
mobile devices. Furthermore, it looks a bit old fashioned etc.

Nicolas Boson (who has ample experience in creating OSGeo related Web
sites and recently the symbol set etc) offers to redesign the site.
In our offlist discussion we came up with the idea to switch to
markdown etc. This could all be discussed in a separate email thread.


Sounds good. Is he willing to do this for free or should we try to raise 
some money in the community to finance this ?




Overall, time to prepare the budget. We may ask OSGeo for financial
support here.


I think the main support would be for travelling costs to sprints.

Moritz


[1] https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2018.

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

Re: [GRASS-PSC] git migration

[Moritz Lennert]

On 7/04/19 22:02, Markus Neteler wrote:

Hi PSC,

a months has passed since the publication of the draft

RFC 6: Migration from SVN to GitHub
https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub

Since then comments have been received and integrated into the document.

Let me suggest to come to a vote in the next days in order to move on
with the SVN to git migration.


+1



I would also suggest to postpone
- label details in the issue tracker (can be done later)
- trac wiki migration (can be done later)
to a date after the git migration has been done, otherwise we remain stuck.


+1

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

Re: [GRASS-PSC] stickers for FOSS4G in Bucharest

[Moritz Lennert]

+1 

Moritz

Am 25. Juni 2019 20:12:19 MESZ schrieb Veronica Andreo :
>Dear PSC
>
>I was thinking that we should definitely print some stickers to bring
>to
>the OSGeo booth at FOSS4G in Bucharest, as we have done in the past. I
>think stickers give us some visibility, everyone likes them and no
>folding
>is needed as compared to flyers :p
>
>I ordered from Stickermule last time and the quality was much better
>than
>that of sticker-app. I thought of ordering 500 die cut stickers (same
>as
>last year) with GRASS logo (
>https://www.stickermule.com/products/die-cut-stickers). Choosing the
>smallest dimension (also as last year), it's something like ~150
>dollars.
>However, since our logo is not exactly 2x2 inches, price is a bit less
>IIRC.
>
>If PSC agrees, I can assist with the ordering process, but cannot
>really
>pay with my credit card this time. So, it would be great if we can pay
>directly from GRASS bank account.
>
>What do you say?
>
>Best,
>Vero
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] stickers for FOSS4G in Bucharest

[Moritz Lennert]

Hi all,

Thanks Vero for the detailed instructions. I'll try to do it tonight.

Where should the stickers be delivered to ?

Moritz

Le Mon, 8 Jul 2019 17:30:05 +0200,
Veronica Andreo  a écrit :

> Hi all,
> 
> great!
> 
> So, here are the instructions, it's really simple.
> 
> 1. go here: https://www.stickermule.com/products/die-cut-stickers
> 2. pick 2" x 2" size and 500 stickers
> 3. you'll have to upload the grass gis color logo (
> https://grass.osgeo.org/uploads/images/logo/grassgis_logo_colorlogo_text_alphabg.png
> )
> 4. payment details (GRASS account)
> 
> Since our logo is not exactly squared, they'll send an email after
> they process the request, so you confirm you agree with the final
> size. And that's it :)
> 
> @Moritz, please let me know if I can assist further and thanks much!!!
> 
> Cheers,
> Vero
> 
> 
> El vie., 5 jul. 2019 a las 21:48, Markus Neteler ()
> escribió:
> 
> > On Fri, Jul 5, 2019 at 9:46 PM Anna Petrášová
> >  wrote:  
> > > On Fri, Jul 5, 2019, 15:37 Markus Neteler 
> > > wrote:  
> > [...]  
> > > Sorry, I didn't know it it was a formal motion. For what is
> > > worth, +1  
> >
> > I guess we vote on everything (not sure).
> >
> > Maybe I should have put "Motion" into the subject...
> >
> > Markus
> >  



-- 
Département Géosciences, Environnement et Société Université Libre de
Bruxelles Bureau: S.DB.6.138
CP 130/03
Av. F.D. Roosevelt 50
1050 Bruxelles
Belgique

tél. + 32 2 650.68.12 / 68.11 (secr.)
fax  + 32 2 650.68.30 
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] stickers for FOSS4G in Bucharest

[Moritz Lennert]

Le Tue, 9 Jul 2019 10:16:09 -0300,
Veronica Andreo  a écrit :

> Hi Moritz,
> 
> El mar., 9 jul. 2019 06:51, Moritz Lennert
>  escribió:
> 
> > Hi all,
> >
> > Thanks Vero for the detailed instructions. I'll try to do it
> > tonight.
> >
> > Where should the stickers be delivered to ?
> >  
> 
> Well, to you, if you don't mind to take them to Bucharest. Unless
> someone else volunteers. I'm afraid the delivery to Argentina will
> increase price quite a bit ;)

OK. I just have to make sure that they won't get lost as I will be away
from home for 3 weeks...

Moritz

> 
> Cheers,
> Vero
> 
> 
> > Le Mon, 8 Jul 2019 17:30:05 +0200,
> > Veronica Andreo  a écrit :
> >  
> > > Hi all,
> > >
> > > great!
> > >
> > > So, here are the instructions, it's really simple.
> > >
> > > 1. go here: https://www.stickermule.com/products/die-cut-stickers
> > > 2. pick 2" x 2" size and 500 stickers
> > > 3. you'll have to upload the grass gis color logo (
> > >  
> > https://grass.osgeo.org/uploads/images/logo/grassgis_logo_colorlogo_text_alphabg.png
> >   
> > > )
> > > 4. payment details (GRASS account)
> > >
> > > Since our logo is not exactly squared, they'll send an email after
> > > they process the request, so you confirm you agree with the final
> > > size. And that's it :)
> > >
> > > @Moritz, please let me know if I can assist further and thanks
> > > much!!!
> > >
> > > Cheers,
> > > Vero
> > >
> > >
> > > El vie., 5 jul. 2019 a las 21:48, Markus Neteler
> > > () escribió:
> > >  
> > > > On Fri, Jul 5, 2019 at 9:46 PM Anna Petrášová
> > > >  wrote:  
> > > > > On Fri, Jul 5, 2019, 15:37 Markus Neteler 
> > > > > wrote:  
> > > > [...]  
> > > > > Sorry, I didn't know it it was a formal motion. For what is
> > > > > worth, +1  
> > > >
> > > > I guess we vote on everything (not sure).
> > > >
> > > > Maybe I should have put "Motion" into the subject...
> > > >
> > > > Markus
> > > >  
> >
> >
> >
> > --
> > Département Géosciences, Environnement et Société Université Libre
> > de Bruxelles Bureau: S.DB.6.138
> > CP 130/03
> > Av. F.D. Roosevelt 50
> > 1050 Bruxelles
> > Belgique
> >
> > tél. + 32 2 650.68.12 / 68.11 (secr.)
> > fax  + 32 2 650.68.30
> >  



-- 
Département Géosciences, Environnement et Société Université Libre de
Bruxelles Bureau: S.DB.6.138
CP 130/03
Av. F.D. Roosevelt 50
1050 Bruxelles
Belgique

tél. + 32 2 650.68.12 / 68.11 (secr.)
fax  + 32 2 650.68.30 
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS-dev] Motion: Migrate SVN and trac tickets to github under OSGeo organization

[Moritz Lennert]

Am 25. April 2019 16:45:01 MESZ schrieb Martin Landa :
>Dear PSC,
>
>po 22. 4. 2019 v 17:27 odesílatel Markus Neteler 
>napsal:
>> Next steps of migration to Github:
>
>I will prepared detailed plan in the next days. Ma


Kudos to you, Martin, for all the work you are doing on this !

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

[GRASS-PSC] Report about sponsoring

[Moritz Lennert]

Hi all,

Just to let you know: I just transferred 683,39€ from the PayPal Money 
Pool to our bank account.


This corresponds to all the sponsoring money received since January.

For details of the sponsoring, you can see

https://grasswiki.osgeo.org/wiki/Sponsors

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

Re: [GRASS-PSC] GRASS GIS Community Sprint Prague 2019 Expenses

[Moritz Lennert]

On 12/12/19 10:30, Moritz Lennert wrote:

On 12/12/19 10:19, Luca Delucchi wrote:

On Thu, 12 Dec 2019 at 10:14, Moritz Lennert
 wrote:


P.S. Maybe we can also decide on a general policy of using
nextcloud.osgeo.org, instead of gdrive ?



yes, I fully support this! We could ask to the manager to create a
GRASS group and folder


They already exist, and there is a special GRASS PSC folder in which
there is an ACCOUNTING folder...



I have just created a folder for the accounting year 2019-2020 (linked 
to the OSGeo-EU accounting because our bank account is hosted by them) 
and uploaded the invoices from the Prague sprint.


Moritz

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

Re: [GRASS-PSC] GRASS GIS Community Sprint Prague 2019 Expenses

[Moritz Lennert]

P.S. Maybe we can also decide on a general policy of using 
nextcloud.osgeo.org, instead of gdrive ?


Moritz

On 12/12/19 10:10, Moritz Lennert wrote:

Hi Martin !

On 12/12/19 09:33, Martin Landa wrote:

Dear PSC,

first of all I would like to thank to the all participants of recently
organized community sprint in Prague [1]. We spent 5 nice days
fulfilled by GRASS hacking:-) See related reports [2].

Based on that we collected all expenses [3]. The budget is relatively
minimalistic since no travel/accommodation grants have been requested.

In this regard I would like to ask GRASS PSC to cover all expenses [3;
Reimbursements tab] (280.24 EUR in overall). Scanned bills [4].

If no objection we could start voting (in *different thread*).


No objections on my side. Rather a big thank you for having organized this !

Two questions though, one concerning budget, the other concerning content:

- IIUC, most of the budget you are asking for is actually for
promotional material (stickers, magnets) that are only indirectly linked
to the code sprint, or ? I would therefore suggest to separate the two
requests to make that more apparent. Your actual "sprinting" costs are
<60€, or ?

- In the report, you write: "We spent several hours over the course of
the sprint discussing different alternatives and finding a best way to
implement the one we have chosen." I see that everything has been
documented in detail on the relevant wiki page:
https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/New_Startup#GRASSGISCommunitySprintPrague2019,
but would it be possible summarize the general philosophy on the mailing
list ? I think this is an important part of GRASS GIS and discussion
should be larger.

Moritz




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

Re: [GRASS-PSC] GRASS GIS Community Sprint Prague 2019 Expenses

[Moritz Lennert]

On 12/12/19 10:19, Luca Delucchi wrote:

On Thu, 12 Dec 2019 at 10:14, Moritz Lennert
 wrote:


P.S. Maybe we can also decide on a general policy of using
nextcloud.osgeo.org, instead of gdrive ?



yes, I fully support this! We could ask to the manager to create a
GRASS group and folder


They already exist, and there is a special GRASS PSC folder in which 
there is an ACCOUNTING folder...


;-)

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

Re: [GRASS-PSC] GRASS GIS Community Sprint Prague 2019 Expenses

[Moritz Lennert]

On 12/12/19 10:51, Martin Landa wrote:

Hi Moritz,

čt 12. 12. 2019 v 10:13 odesílatel Moritz Lennert
 napsal:

- IIUC, most of the budget you are asking for is actually for
promotional material (stickers, magnets) that are only indirectly linked
to the code sprint, or ? I would therefore suggest to separate the two


make sense to me. In reality you are suggesting two separated voting
procedures, right?


Well, don't know if we really need two voting procedures, or just one 
vote combining the two expenses...





requests to make that more apparent. Your actual "sprinting" costs are
<60€, or ?


Yes, only one dinner, two lunches + small food.


No beer ??? ;-)




- In the report, you write: "We spent several hours over the course of
the sprint discussing different alternatives and finding a best way to
implement the one we have chosen." I see that everything has been
documented in detail on the relevant wiki page:
https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/New_Startup#GRASSGISCommunitySprintPrague2019,
but would it be possible summarize the general philosophy on the mailing
list ? I think this is an important part of GRASS GIS and discussion
should be larger.


Sure, on the other hand we cannot discuss it forever :-) We have
prepared step-by-step roadmap, see [1]. No big revolution, just small
but important steps. Feel free to comment!



Yes, I saw that (that's why I already included the same link ;-) ), but 
it is very detailed and so I'm not sure I really understand the big 
picture of the general philosophy you have decided. On the wiki page we 
started out by discussing two general options: "Keep current paradigm, 
but make contact easier" or "Change paradigm" (e.g. "Open into a 
predefined lat-long location but give information message"). IIUC, your 
roadmap follows the first option, or ?


There's just too many trees for me to see the forest ;-)

Moritz


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

[GRASS-PSC] Fw: [Motion] First payment for new GRASS GIS Hugo based web site

[Moritz Lennert]

Sorry, sent this from the wrong address.

- Message Transféré -

Date : Mon, 17 Feb 2020 16:05:02 +0100
De : Moritz Lennert 
À : grass-psc@lists.osgeo.org
Sujet : Re: [GRASS-PSC] [Motion] First payment for new GRASS GIS Hugo
based web site


On 17/02/20 13:58, Markus Neteler wrote:
> Dear PSC,
> 
> After a long time of discussions and developments, the first prototype
> of the new GRASS GIS website is available at
> https://staging.grass.osgeo.org/ with the code available at
> https://github.com/OSGeo/grass-website .
> 
> The entire project follows what has been discussed earlier:
> https://grasswiki.osgeo.org/wiki/Website_migration_plan_2019
> We requested OSGeo in 2019 to cover the development with 6000 USD, see
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2019 - given the
> delays it was moved to
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020 . See therein
> for the related OSGeo budget wiki page.
> 
> This motion is to vote on the first payment of 4000 USD (out of 6000
> USD) to the developer, Nicolas Bozon (https://github.com/nbozon). Some
> issues are still open and he scheduled to continue further work on the
> Hugo code later this month.
> 
> The money transfer can then be directly done from OSGeo to the
> developer (already clarified with the OSGeo treasurer).
> 
> Motion:
> I start with a +1.  


+1

Moritz


-- 
Département Géosciences, Environnement et Société Université Libre de
Bruxelles Bureau: S.DB.6.138
CP 130/03
Av. F.D. Roosevelt 50
1050 Bruxelles
Belgique

tél. + 32 2 650.68.12 / 68.11 (secr.)
fax  + 32 2 650.68.30 
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] GRASS GIS Budget request for 2020

[Moritz Lennert]

On 10/01/20 20:53, Markus Neteler wrote:

On Thu, Jan 9, 2020 at 4:00 AM Vaclav Petras  wrote:

On Mon, Jan 6, 2020 at 6:58 AM Markus Neteler  wrote:

On Mon, Jan 6, 2020 at 12:57 PM Moritz Lennert

Am 6. Januar 2020 12:50:12 MEZ schrieb Markus Neteler :

Hi PSC,

Below the email which I had sent to the board.
However, we need to modify the request as code sprint support needs to
be requests separately from the general (current) request.

Hence, I have separated out the sprint requests (to be submitted later
this year):
https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020#Planned_Expenses



Thank you. I like that the new budget is more compatible with OSGeo. I was just 
thinking that the meetup item
should go to the the events [1] since it is likely to be more outreach event 
than a sprint. Do you have any thoughts on that?


I just made it " Events/Community Sprints" to not overcomplicate the table.


Perhaps more importantly, I don't understand where the "delta to be fundraiser" 
is coming from, although it generally makes sense to have it.


"Delta to be fundraised" is indicating how much money we still lack to
get an even budget.

(only USD here)
TOTAL  15,704

from that:
- Request to OSGeo (as main budget)  8,973 (i.e. excluding
Events/Community Sprints)
- Request to OSGeo (as Sprint support) 6,731

Hence we have the:
Delta to be fundraised 3,704



If our total budget is 15,704, and we request

8,973 + 6,731 = 15,704

then there is no delta to be fundraised, everything is covered via the 
requested money.


So, I also do not understand what this delta represents...

Moritz

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

Re: [GRASS-PSC] GRASS GIS budget 2020 - was: Re: [Board] OSGeo Budget 2020

[Moritz Lennert]

On 31/12/19 18:13, Markus Neteler wrote:

Hi all,

On Mon, Dec 30, 2019 at 10:41 PM Moritz Lennert  wrote:


Am 30.12.2019 18:50 schrieb Markus Neteler:

Hi Peter, Moritz, PSC,

On Fri, Dec 27, 2019 at 1:39 PM "Peter Löwe" 
wrote:


Hello Markus, hi PSC,

regarding our surplus from 2019, does the item "Travel grants for
community sprints: 1043.09 EUR" summarize all costs for both events in
Berlin and the Prague (including food, drinks, etc.) ?


I am not sure where this number came from.
The figure was added by Moritz:
https://grasswiki.osgeo.org/w/index.php?title=GRASS_GIS_Budget_2019=26007=26006

@Moritz Lennert could you pls add how it was calculated?


The total corresponds to all expenses of the Berlin Community Sprint,
travel grants, but also other expenses. Should these be separated ?


I guess so, or we rename the entry. Ok, given the time we have I have
just renamed it for now.

[...]

The Praque Sprint is not included, yet.


@Martin pls enlighten us. Is there a table? I darkly remember some
figures having been sent to this list.



The figures have been sent to the list. There was a discussion whether 
the cost of buying stickers, etc should be part of the sprint budget, or 
not. Thus there has not been an official vote by the PSC, yet, and the 
money has not been sent to Martin.


Therefore, the actual reimbursement will happen in 2020 so I guess it 
will be part of the 2020 budget, or ?



I guess at one point we have to decide on a bit more systematic
accounting and budget definition procedures. I just quickly cobbled
things together when they were needed by OSGeo-EU.


I agree.
For now I have reworked the Wiki pages and added an USD column since
that is the currency we have to report to the OSGeo board.


Great, thanks!




Now that I've learned
today that I was officially a treasurer, I'll have to find some time to
put things in order, but don't know when that will be...


We might actually discuss and vote about this role :-)



Good idea.

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

Re: [GRASS-PSC] GRASS GIS Budget request for 2020

[Moritz Lennert]

Am 6. Januar 2020 12:50:12 MEZ schrieb Markus Neteler :
>Hi PSC,
>
>Below the email which I had sent to the board.
>However, we need to modify the request as code sprint support needs to
>be requests separately from the general (current) request.
>
>Hence, I have separated out the sprint requests (to be submitted later
>this year):
>https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020#Planned_Expenses
>
>Now:
>- please verify that the figures are right

Sprint budget thus only includes catering and possibly some venue costs ?

If that is the case, 2000 seems a lot, no ?

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

Re: [GRASS-PSC] [MOTION] Prague 2019 Community Sprint Reimbursements

[Moritz Lennert]

On 7/01/20 14:21, Martin Landa wrote:

Dear PSC members,

based on thread [1] I am taking liberty to start motion related to
GRASS GIS Community Sprint Prague 2019 [2] (see reports [3]). Overall
expenses contains two major items:

* food & drinks (112.78EUR), and
* promotional materials printed (222.20EUR)

See [3], tab "Reimbursements".

This motion is about asking for 100% funding of participation expenses
listed above [3].


+1

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

Re: [GRASS-PSC] Fwd: [Board] GitHub sponsors

[Moritz Lennert]

On 25/05/20 15:02, Moritz Lennert wrote:

On 25/05/20 11:12, Markus Neteler wrote:

Hi PSC,

Potentially interesting for us as well! Any opinions?


Looks good after a rapid look.

I don't understand whether the limitation to some regions [1] concerns 
the organisations receiving the sponsoring, or the people who sponsor. 
We did receive some donations from outside that list.


The advantage would be to really make this into a GRASS sponsorship 
account, instead of going through a money pool linked to my personal 
PayPal account as currently.


Moritz

[1] https://github.com/sponsors#countries


Hmmh, just read some more here [2] where it says:

"Anyone with a GitHub account can sponsor anyone with a sponsored 
developer profile or sponsored organization profile through a recurring 
monthly payment."


So, that means that only people on github can sponsor ? And that 
sponsorship necessarily means a "recurring monthly payment" ? If any of 
those two are true, then I think this would be a possible complement to, 
not a replacement of our current PayPal money pool.


Moritz


[2] 
https://help.github.com/en/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors

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

Re: [GRASS-PSC] Fwd: [Board] GitHub sponsors

[Moritz Lennert]

On 25/05/20 11:12, Markus Neteler wrote:

Hi PSC,

Potentially interesting for us as well! Any opinions?


Looks good after a rapid look.

I don't understand whether the limitation to some regions [1] concerns 
the organisations receiving the sponsoring, or the people who sponsor. 
We did receive some donations from outside that list.


The advantage would be to really make this into a GRASS sponsorship 
account, instead of going through a money pool linked to my personal 
PayPal account as currently.


Moritz

[1] https://github.com/sponsors#countries



Cheers,
Markus

-- Forwarded message -
From: Jody Garnett 
Date: Mon, May 25, 2020 at 12:29 AM
Subject: [Board] GitHub sponsors
To: osgeo-board List 

We noticed that several of our projects qualify for https://github.com/sponsors

As GeoTools project lead, how would the board feel if we signed up for
this (as a zero-fees replacement for current PayPal donation button)?

Note our project does not run a separate bank account so some
coordination with the osgeo treasurer is required here.
--
Jody Garnett
___
Board mailing list
bo...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/board
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc



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

Re: [GRASS-PSC] Fwd: [Projects] Get ready for our OSGeo AGM 2020 virtual event on 10 September 2020 18 UTC

[Moritz Lennert]

Am 5. August 2020 18:44:32 MESZ schrieb Markus Neteler :
>FYI, we are invited to present at the annual general meeting in the
>usual
>60 seconds slot.
>
>For sure the new web site plays a role, what else do you suggest?

Some brainstorm ideas:

- the effort of revamping startup, i.e. first-time entry into GRASS GIS (with 
current GSoC effort by Linda)
- sponsoring by individuals
- releases since last year


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

Re: [GRASS-PSC] Proposing Tomas Zigo as a new core developer

[Moritz Lennert]

+1 

Moritz

Am 20. November 2020 23:17:39 MEZ schrieb Markus Neteler :
>Dear PSC,
>
>Let me propose Tomáš Zigo (https://github.com/tmszi) to be accepted as
>a core developer.
>
>Tomáš has impressively contributed to various parts of the source code:
>
>- in "core": as of today 132 accepted pull requests in the main repo [1],
>- in "addons": as of today 132 accepted pull requests in addons [2],
>- and he offered many more comments on other pull requests and as well
>as in the mailing list.
>
>I have asked him off-list and he would be happy to join the core team
>with write access to the main repository.
>
>According to RFC1 [1] all PSC members need to vote in a separate motion.
>
>Best,
>Markus
>
>
>[1] https://github.com/OSGeo/grass/pulls?q=is%3Apr+is%3Aclosed+author%3Atmszi
>[2] 
>https://github.com/OSGeo/grass-addons/pulls?q=is%3Apr+is%3Aclosed+author%3Atmszi
>[3] https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines
>___
>grass-psc mailing list
>grass-psc@lists.osgeo.org
>https://lists.osgeo.org/mailman/listinfo/grass-psc
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections in 2020

[Moritz Lennert]

On 7/12/20 21:28, Markus Neteler wrote:

Dear PSC,

Almost a year has passed...

On Wed, Dec 11, 2019 at 12:08 AM Markus Neteler  wrote:

Hi PSC,

I have drafted a page for the needed PSC elections:
https://trac.osgeo.org/grass/wiki/PSC/Election2020

All details yet to be defined.

I would like to re-suggest discussing the next PSC election.


+1

First step would probably be to find a CRO. Doesn't have to part of the 
current PSC, or ? So we should ask on the -dev and probably also the 
-user list for candidates. Any objections to me sending the following 
mail to both lists ?


Moritz




Dear all,

As part of the effort to guarantee a solid and sustainable governance of 
GRASS GIS development, and in accordance with OSGeo guidelines, we have 
a Project Steering Committee [1]. Although most decisions are taken by 
consensus via the developers mailing list or via discussions in github 
issues, some decisions go through this committee: annual budget, 
admission of new developers into the core development team, and some 
fundamental decisions (recent example: phasing out of a 32-bit version 
for MS Windows). For an overview of the (fairly low-noise) activity of 
the PSC, you can browse through the archives of its public mailing list 
[2]. You will see that it is not a job that requires a lot of work, but 
it is an essential job nevertheless. Also: no need to be a developer to 
be part of the PSC, users should also be represented.


The last election for this committee was in 2016 and at the time we 
decided that the PSC should be renewed approximately every 3 years. We 
are already beyond this time frame and so a new election should happen, 
soon. The general outline of the procedure has been drafted [3]. The 
first step in that procedure is the nomination of one (or several) Chief 
Return Officers who will oversee the election process.


Is anyone willing to play this role ? You can just respond directly here 
on the list to display your interest.


The current PSC

***

[1] https://trac.osgeo.org/grass/wiki/PSC 



[2] https://lists.osgeo.org/pipermail/grass-psc/ 



[3] https://trac.osgeo.org/grass/wiki/PSC/Election2020

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

Re: [GRASS-PSC] PSC elections

[Moritz Lennert]

On 14/12/20 09:44, Chief Return Officer (CRO) - GRASS GIS election 2020 
wrote:


On 2020-12-13 23:12, Veronica Andreo wrote:

Hi everyone,

El dom, 13 dic 2020 a las 21:19, Moritz Lennert 
(mailto:mlenn...@club.worldonline.be>>) 
escribió:



Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler
mailto:nete...@osgeo.org>>:
>On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
>mailto:variablestarli...@gmail.com>> wrote:
>>
>> Hi again,
>>
>> In the wiki, eligible voters are defined as those with svn
access. This is perhaps outdated?
>
>Yes, that's definitely outdated.
>
>> In 2020 it should perhaps be those who can merge a pull request
in GitHub? Or should we choose another definition?

Only merge rights (i.e. write access to the grass repository)
seems very restrictive in current github PR times.


Fully agreed! Last time, all of us in the contributors and 
contributors_extra files were given voting rights. We could also 
consider those in translators.csv. I don't remember if they were 
considered last time. I believe they were not.


>I believe that we should also recognize other contributions
>(documentation, translation etc).

How to define this, though. In my eyes we should be as inclusive
as reasonable.

Maybe we could say:

- All people with write access to any of the GRASS GIS
repositories (i.e for example also including add-ons and website).
- All people that have already posted a pull request to github
(possibly only those PR that have been merged)
- All people that have contributed to Transifex.


+1!


+1 to this too

A couple of related questions:

1. is there any easily accessible/searchable list over people who have 
the right to vote? How it is supposed the CRO will check this?


The three files that Vero mentioned are all in the root of the github 
repository:


https://github.com/OSGeo/grass/blob/master/contributors.csv
https://github.com/OSGeo/grass/blob/master/contributors_extra.csv
https://github.com/OSGeo/grass/blob/master/translators.csv

I don't know if there are many contributors of pull requests via github 
that are not in those files, same for translators that might be active 
on Transifex, but not in the relevant list.


@MarkusN what is the status of these lists ?

For github PR contributors, maybe the tool MarkusN mentioned could help 
getting a list from github.




2. Now that we are talking about lists of names, at least in EU we have 
to follow GDPR. We should add somewhere a note stating that names are 
going to be stored and shown, and also describing how. Perhaps this is 
already considered?


We do not add anything to the three lists above, and they are already 
public, so I don't think we have to worry about that too much.


Indepently of the election, in the context of GDPR we maybe have to send 
a mail to all mailing lists reminding people that these lists exist and 
that they can inform us if they want to be taken off. I'm really no GPDR 
expert, though.


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

Re: [GRASS-PSC] PSC elections

[Moritz Lennert]

On 14/12/20 12:43, Moritz Lennert wrote:
On 14/12/20 09:44, Chief Return Officer (CRO) - GRASS GIS election 2020 
wrote:


On 2020-12-13 23:12, Veronica Andreo wrote:

Hi everyone,

El dom, 13 dic 2020 a las 21:19, Moritz Lennert 
(<mailto:mlenn...@club.worldonline.be>>) escribió:



    Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler
    mailto:nete...@osgeo.org>>:
    >On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
    >mailto:variablestarli...@gmail.com>> wrote:
    >>
    >> Hi again,
    >>
    >> In the wiki, eligible voters are defined as those with svn
    access. This is perhaps outdated?
    >
    >Yes, that's definitely outdated.
    >
    >> In 2020 it should perhaps be those who can merge a pull request
    in GitHub? Or should we choose another definition?

    Only merge rights (i.e. write access to the grass repository)
    seems very restrictive in current github PR times.


Fully agreed! Last time, all of us in the contributors and 
contributors_extra files were given voting rights. We could also 
consider those in translators.csv. I don't remember if they were 
considered last time. I believe they were not.


    >I believe that we should also recognize other contributions
    >(documentation, translation etc).

    How to define this, though. In my eyes we should be as inclusive
    as reasonable.

    Maybe we could say:

    - All people with write access to any of the GRASS GIS
    repositories (i.e for example also including add-ons and website).
    - All people that have already posted a pull request to github
    (possibly only those PR that have been merged)
    - All people that have contributed to Transifex.


+1!


+1 to this too

A couple of related questions:

1. is there any easily accessible/searchable list over people who have 
the right to vote? How it is supposed the CRO will check this?


The three files that Vero mentioned are all in the root of the github 
repository:


https://github.com/OSGeo/grass/blob/master/contributors.csv
https://github.com/OSGeo/grass/blob/master/contributors_extra.csv
https://github.com/OSGeo/grass/blob/master/translators.csv

I don't know if there are many contributors of pull requests via github 
that are not in those files, same for translators that might be active 
on Transifex, but not in the relevant list.


@MarkusN what is the status of these lists ?

For github PR contributors, maybe the tool MarkusN mentioned could help 
getting a list from github.




Maybe we can start with an email to all mailing lists, informing 
everyone that we consider these three files as our "electoral registry" 
and that if anyone feels she or he should be in one of these files, that 
they send a mail to the respective list informing us ?


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

Re: [GRASS-PSC] 2020 Election wiki - request for comments on details

[Moritz Lennert]

On 17/12/20 10:43, Chief Return Officer (CRO) - GRASS GIS election 2020 
wrote:

To avoid confusion with ASCII emails, here the clean version:

- Number of PSC members to be elected: 9
- Election duration: 2020-12-21 - 2021-01-28
    - Nomination period: 2020-12-21 - 2021-01-11
    - Reflection week: 2021-01-11 - 2021-01-18
    - Voting period: 2021-01-18 - 2021-01-25
    - Latest possible announcement of new PSC: 2021-02-01


Are these dates reasonable?

To me it sounds reasonable.


Fine! Then I write them in the wiki and we aim to launch on monday 21/12.



Eligible voters:

- have already posted a pull request to github **(possibly only those 
PR that have been merged)**

I understood that in addition we want the translators.
- have contributed to Transifex

Yes, my question was about the part within parentheses

Note the second criterion, what about PR:s being merged or not?

Opinions on this?

"PR still open" would be fine for me because it shows interest, an
active contribution and maybe tackles complicated stuff which cannot
be merged quickly.

Then, we can say that submitting a PR gives a person the right to vote, 
independently of the PR having been accepted or not.




 From the current wiki drat: Election tool?

  During the Voting period, eligible voters, can vote their preferred
  candidate(s) via an on-line tool which will protect privacy.

Which tool? How does this work?

O see that https://vote.heliosvoting.org/ was used in 2016. Is this 
being used in 2020 too? How?

Nikos knows about heliosvoting.
But as Moritz suggests, perhaps we may use
https://limesurvey.osgeo.org - I can try to find out.


We will wait for the answer on this then. In a sense, we could just 
start on monday 21/12 and hope for a clear solution regarding the voting 
system later during the process. But perhaps this is too risky. I would 
prefer to have a definition on which system is to be used and how to use 
it before launching the election.


I think you can launch the nomination period on the 21. Heliosvoting 
should work. Just log in with your Google account and click "create an 
election".


For the OSGeo Limesurvey, on https://limesurvey.osgeo.org/ it says 
"Please contact OSGeo CRO ( c...@osgeo.org ) for further assistance.", so 
you could probably just do that.


Personally I like the idea of keeping things within the OSGeo ecosystem, 
and so would privilege that solution, but we shouldn't make this too 
much of an issue.


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

Re: [GRASS-PSC] Announcements to all lists

[Moritz Lennert]

@MarkusN is there a way to either whitelist the address for all lists so that 
mails automatically are admitted ? Or to automatically register it as member of 
all lists (but with mail delivery from the lists deactivated) ?

Moritz

Am 15. Dezember 2020 10:22:28 MEZ schrieb "Chief Return Officer (CRO) - GRASS 
GIS election 2020" :
>It seems that messages sent from this account are not automatically 
>approved for various lists of which I am not a member. Should I become a 
>member of all lists? Or is this adress (cro.grass ...)  already 
>"blessed" for pushing messages in all related lists?
>
>/H.
>
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Announcements to all lists

[Moritz Lennert]

Am 15. Dezember 2020 16:14:23 MEZ schrieb Markus Neteler :
>On Tue, Dec 15, 2020 at 4:12 PM Hernán De Angelis
> wrote:
>> On 2020-12-15 15:39, Markus Neteler wrote:
>> > On Tue, Dec 15, 2020 at 3:37 PM Chief Return Officer (CRO) - GRASS GIS
>> > election 2020  wrote:
>> > ...
>> >> I mailed this morning to all lists mentioned in
>> >>
>> >> https://grass.osgeo.org/about/community/
>> > Sorry - please do again - they have been silently "eaten" due to the
>> > huge spam load (no way for me to manually go through every day).
>> > Only grass-web arrived which I manually moderate.
>>
>> I re-mailed the announcement a few minutes ago to the dev, stats,
>> translations and announce lists. No signs that it passed yet.
>
>Mh, it should be immediate.
>
>Importantly, I whitelisted the CRO email. Perhaps you have sent from
>your gmail account?

If you still have the same config, i.e. sender = your personal address and 
reply-to = CRO address it will fail. You have to use the CRO address as sender.

IIUC, you use Google Mail ? Then here are relevant instructions on how to do 
that: https://support.google.com/mail/answer/22370?hl=en.

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

Re: [GRASS-PSC] PSC elections

[Moritz Lennert]

Hi Hernán,

Am 13. Dezember 2020 18:41:02 MEZ schrieb "Hernán De Angelis" 
:
>Dear Nikos,
>
>Thank you for your message and considerations. I believe I understand 
>the basis of this process.
>
>It seems that we will need to update the 2020 Election wiki 
> before we start. 
>How do we proceed with that?

If you don't have one already, you need an OSGeo User ID to log in:

https://www.osgeo.org/community/getting-started-osgeo/osgeo_userid/

While waiting for that, you should begin by defining the calendar (also based 
on your possible constraints).

In 2016 [1] we had a four week nomination period of which the last week was 
used to give candidates the opportunity to reevaluate if they really want to 
stand for elections. Then a one week period for the vote. So depending on when 
you can announce, this will mean mid-December to mid-January for nomination and 
then a week end of January for the vote.

Moritz


[1] https://trac.osgeo.org/grass/wiki/PSC/Election2016
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] PSC elections

[Moritz Lennert]

Dear Hernán,

Thanks for accepting the role as CRO ! We will obviously support you in 
whatever ways necessary.

The first step would now be to define a calendar and to update the wiki page.

@MarkusN, do we have a dedicated email address for the CRO ?

@Nikos, as you were the CRO at the last election, maybe you have some advice 
for Hernán ?

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

Re: [GRASS-PSC] Proposing Nicklas Larsson as a new core developer

[Moritz Lennert]

+1

Moritz

Am 16. Dezember 2020 15:19:04 MEZ schrieb Markus Neteler :
>Dear PSC,
>
>Let me propose Nicklas Larsson (https://github.com/nilason) to be
>accepted as a new core developer.
>
>Nicklas has impressively contributed to various parts of the source code:
>
>- in "core": as of today 40 accepted/approved pull requests in the
>main repo [1],
>- in "addons": as of today 1 accepted pull requests in addons [2],
>- and he offers support, especially for the packaging on Mac.
>
>I have asked him off-list and he would be happy to join the core team
>with write access to the main repository.
>
>According to RFC1 [1] all PSC members need to vote on this proposal.
>
>Best,
>Markus
>
>
>[1] https://github.com/OSGeo/grass/pulls?q=is%3Apr+is%3Aclosed+author%3Anilason
>[2] 
>https://github.com/OSGeo/grass-addons/pulls?q=is%3Apr+is%3Aclosed+author%3Anilason
>[3] https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines
>___
>grass-psc mailing list
>grass-psc@lists.osgeo.org
>https://lists.osgeo.org/mailman/listinfo/grass-psc
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] 2020 Election wiki - request for comments on details

[Moritz Lennert]

As I suggested several of the proposals, I'd appreciate if other PSC 
members could voice their opinion.

I don't know the heliosvoting system. I imagine Nikos found it last time. For 
the recent board elections OSGeo used a limesurvey instance installed on the 
OSGeo servers. Maybe we can use that ?

Moritz

Am 16. Dezember 2020 19:28:23 MEZ schrieb "Chief Return Officer (CRO) - GRASS 
GIS election 2020" :
>Comments appreciated, so we can move forward with this. See below.
>
>Thanks
>
>/H.
>
>
>
>On 2020-12-16 09:18, Chief Return Officer (CRO) - GRASS GIS election 
>2020 wrote:
>> Good morning,
>>
>> I am now set to edit the trac wiki and start defining the process. At 
>> this stage I would like us to reach a consensus regarding critical 
>> parts of the process. This is preliminary, please comment and suggest 
>> other options as you consider necessary.
>>
>>
>> Number of PSC members to be elected: 10 9
>>
>> Election duration: 2020-12-1721 - 2021-01-28
>>
>> Nomination period: 2020-12-1721 - 2021-01-0711
>>
>> Reflection week: 2021-01-0711 - 2021-01-1418
>>
>> Voting period: 2021-01-1418 - 2021-01-2125
>>
>> Latest possible announcement of new PSC: 2021-01-2802-01
>>
>>
>Are these dates reasonable?
>
>
>> Eligible voters:
>>
>> - have already posted a pull request to github **(possibly only those 
>> PR that have been merged)**
>>
>> Note the second criterion, what about PR:s being merged or not?
>
>Opinions on this?
>
>
>>
>> From the current wiki drat: Election tool?
>>
>> During the Voting period, eligible voters, can vote their preferred
>> candidate(s) via an on-line tool which will protect privacy.
>>
>> Which tool? How does this work?
>
>O see that https://vote.heliosvoting.org/ was used in 2016. Is this 
>being used in 2020 too? How?
>
>
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS GIS Elections 2020] Current members of the PSC willing to stand up for reelection?

[Moritz Lennert]

On 22/12/20 14:48, Markus Neteler wrote:

On Tue, Dec 22, 2020 at 12:34 PM Chief Return Officer (CRO) - GRASS
GIS election 2020  wrote:

On 2020-12-22 12:08, Markus Neteler wrote:

On Tue, Dec 22, 2020 at 10:28 AM Moritz Lennert

...

But I agree with Hernán that we should have discussed this earlier.

Still it is not too late, say, "nothing lost".


Marcus, what do you say on this?


What I tried to say is that we might quickly modify our procedure to
Helli's suggestion as no PSC member had answered yet (hence, no
conflict arises so far).


What do other PSC members say? Shall
the PSC make a consensus on these proposals? In that case it would be
nice to have the matter resolved rather sooner than later.


Definitely.

@PSC: do you agree to change our procedure to

"GRASS GIS PSC members are to be nominated for re-election in the same
way by the community as possible new candidates"



+1

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

Re: [GRASS-PSC] [GRASS GIS Elections 2020] Current members of the PSC willing to stand up for reelection?

[Moritz Lennert]

Am 22. Dezember 2020 09:24:17 MEZ schrieb "Chief Return Officer (CRO) - GRASS 
GIS election 2020" :
>
>On 2020-12-21 22:20, Helmut Kudrnovsky wrote:
>> wouldn't it be more transparent if current GRASS GIS PSC members are
>> nominated for re-election in the same way by the community as possible new
>> candidates?
>>
>>
>Thanks for your input, Helmut. The election wiki is not very clear about 
>this, it only states that "current PSC members will be asked if they 
>wish to stand as a candidate for the upcoming election" without any 
>further clarification. This is definitely a grey area worth developing. 
>I agree your proposal is a good idea, but it is possibly not my role to 
>decide on this. Also it is possibly late as we we have already launched 
>the nominations.
>
>I believe this is something the PSC can decide:
>
>1. should current PSC members have the right to stand up for reelection 
>without explicit nomination? (current line of action)
>
>or
>
>2. should current PSC members have to be nominated in the same way as 
>any other member of the community? (we could start right now as no PSC 
>members have yet stand up)

I agree with Helmut and would plead for 2).

But I agree with Hernán that we should have discussed this earlier.

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

Re: [GRASS-PSC] PSC elections

[Moritz Lennert]

Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler :
>On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
> wrote:
>>
>> Hi again,
>>
>> In the wiki, eligible voters are defined as those with svn access. This is 
>> perhaps outdated?
>
>Yes, that's definitely outdated.
>
>> In 2020 it should perhaps be those who can merge a pull request in GitHub? 
>> Or should we choose another definition?

Only merge rights (i.e. write access to the grass repository) seems very 
restrictive in current github PR times.

>
>I believe that we should also recognize other contributions
>(documentation, translation etc).

How to define this, though. In my eyes we should be as inclusive as reasonable.

Maybe we could say:

- All people with write access to any of the GRASS GIS repositories (i.e for 
example also including add-ons and website).
- All people that have already posted a pull request to github (possibly only 
those PR that have been merged)
- All people that have contributed to Transifex.

How does that sound?




>
>Does anyone know this tool for the identification of contributors (I
>never tried)
>https://allcontributors.org/

Sounds interesting, but probably only for github, or ? So not Transifex.

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