Re: [GRASS-PSC] Motion: Grant SVN write access for Ivan Shmakov

[Helena Mitasova]

+1 from me for granting Ivan SVN write access,

Helena


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

Re: [GRASS-PSC] Motion: Grant SVN write access for Ivan Shmakov

[Helena Mitasova]

On Feb 4, 2008, at 6:28 PM, Dylan Beaudette wrote:


On Sunday 03 February 2008, Hamish wrote:

Markus Neteler wrote:

I would like to propose to grant SVN write access to Ivan Shmakov
who got very active to suggest improvements for the core  
libraries of

GRASS. You will have seen his contributions in the grass-dev mailing
list.


Hi,

Ivan seems like a decent fellow and I welcome his expertise. So "+1"
from me.


I would like to informally propose that in future we wait for a
contributer to be active on the -dev mailing list for some time
(perhaps 6 months?) before raising the question of granting SVN write
access. This gives the user a chance to develop a track record,
demonstrate an understanding of the codebase*, and get a feel for how
our little development team works. In addition it gives PSC voters a
chance to be confident in our votes rather than rubber stamping our
approval on a mostly unknown entity.


You bring up some good points. Markus did provide a nice run down  
of Ivan's
activity- and betwee that and watching the dev list I thought  
enough time had
past. I am not as familiar with the code base as the main  
developers, and
therefore my vote does not carry the same weight as the more  
seasoned devs.
How can we formalize / generalize the approach that you are  
suggesting? Would

a mandatory time limit (you suggested 6 months) be sufficient?


time is probably not a good measure - one person can show in one week
what another one shows (or has time to show) in a month or more.
It should be based on the contributions (this can be kept simple
or as complicated as imaginable - e.g. type, size, time interval of  
contributions etc.) -

I would vote for simple.



[*] I think we are in pretty good shape, but merely due to the age of
the codebase we seem to have a large number of undocumented "this is
done for historical reasons" spots to watch out for. Whereas the
initial reaction of a newcomer is to immediately try and fix  
something
that looks awkward, then get shot down by a long time devel. This  
bears
the potential for bad feelings and lost volunteers. The question  
is how

to mentor + promote an eager and competent helper to full developer
status while protecting the codebase from well meaning yet
unintentional damage?



Although it might require a little coordination- maybe it would be  
possible

for the senior devs to 'adopt' a junior.


that is what practically happens because somebody has to submit the  
new code
and that developer (I guess it is most often Markus) usually  
communicates
with the new developer and tests the submitted code - that is the  
time consuming part,
so that is where you want to provide the svn access as soon as  
reasonably possible.
Having to test and submit both your own code and a code of one or  
more other
people for 6 months can be quite a challenge, especially when the  
developer

is particularly active and capable (and we like to see those).

I would suggest something more like an incubation time - in our case
the PSC developer  would motion that a new developer is up for SVN  
access

vote so the PSC can look at what
he has contributed, test the changes that he has submitted and after
additional set of submissions that PSC has a chance to carefully  
monitor,
the PSC developer would ask for a vote. PSC may decide that more time  
is needed -

but that probably won't happen too often,

Helena




Not exactly sure how this would pan
out, but it having a mentor for the first 6 months (or however long  
we decide
on) might make the learning process simpler. This approach would  
really only
be appropriate for those volunteers truly interested in SVN write  
access- so

perhaps those individuals should mention this upfront.

just some ideas...

Dylan'



Hamish






_ 
__

_ Never miss a thing.  Make Yahoo your home page.
http://www.yahoo.com/r/hs

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




--
Dylan Beaudette
Soil Resource Laboratory
http://casoilresource.lawr.ucdavis.edu/
University of California at Davis
530.754.7341
___
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] grass manual translations

[Helena Mitasova]

I got an interesting question - see below.
I asked for more details, but when looking at the man pages
there is only Copyright by GRASS Development Team and
no license and no email who to contact in case somebody
wants to use/distribute/reprint etc. the material. In fact the Intro
pages don't have anything.
Should we include Creative commons license for the manual
at each page with a link to explanation of what CC means?
Or should we protect the manual by a stricter license or copyright
and provide contact to person who will handle the request?
( first option looks much better to me)

Helena


A few months ago i started making a translation of the Grass manual  
and after a lot of changes I prepared a greek manual according to my  
student needs.


In the Greek manual I have allready referenced the grass manual but I  
didnt print it because i still dont have the right to translate the  
english manual.
Is there any way for me to print my book which is about Grass and  
Qgis???
I mean could I somehow take a letter from the Grass team in which  
they will say that I have the right to print my book using as  
basework their work in the english manual??



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

[GRASS-PSC] grass man translation

[Helena Mitasova]

It turns out the author would like to get a letter from us - see  
below - who writes such a letter?
Is it really needed? Should this be raised with OSGeo too so that we  
have some common procedure?

I think that we need a quick answer for Nicholas and then
find a broader solution and include a link with relevant info to all  
man documents,


Helena


Begin forwarded message:


From: Nicolas Karanikolas <[EMAIL PROTECTED]>
Date: February 24, 2008 3:22:22 AM EST
To: Helena Mitasova <[EMAIL PROTECTED]>
Subject: Re: Dear Helena, Nicolas from Greece

Υes it is about this material you are talking about.


http://grass.osgeo.org/grass63/manuals/html63_user/index.html




In some cases I canged a lot of things, text pictures etc., but in  
others I follow your text

and I also use your pictures.
Offcourse there is a line in the beginning which is the basic  
reference of the book.

it says something like
"This whole book for open source gis, grass and qgis is based on  
the manual pages the reader can find in the following  
addresses ..." and offcourse there is a reference at the end.


I just would like to write something like that "the print of the  
book comes by courtesy of the authors and the core team of grass  
and qgis"


And if you could give it to me writen this would be the best for  
me. I would place your page at the beginning of the book.


The qgis seems not to have a problem with this, allthough I hope  
that they will give me their final answer  in the next days.


Finally I would like to say that there is no profit from this book  
for me, but there will be an isbn from the editing.


Thanks for your answer, and I hope to hear from you soon,

Nicolas

On 24 Φεβ 2008, at 2:45 ΠΜ, Helena Mitasova wrote:


Nicolas,

which material are you talking about? Is it the collection of  
manual pages

with basic intro listed here:


or some other tutorials?
many tutorials are published under creative commons license and
you can modify and distribute it (including printing) as long as you
credit the source.

If most of the writing and examples are yours then you are
the author and you can do what you want. Just reference the manual
where appropriate.

If the text is the same or almost the same as the english original
you should still be able to print it and distribute to your students,
but I can see that we do not have explicitly stated license for the
manual, so let me raise the issue with the steering committee to
make sure that it is stated on the web.

How do you handle the QGIS part? Do you have some explicit
permission from the steering committee?

thanks for asking - it is a good question that needs to be resolved,

Helena

On Feb 23, 2008, at 12:16 PM, Nicolas Karanikolas wrote:


Dear Helena,

My name in Nicolas Karanikolas

I teach cartography and GIS in a Greek university.

A few months ago i started making a translation of the Grass  
manual and after a lot of changes I prepared a greek manual  
according to my student needs.


In the Greek manual I have allready referenced the grass manual  
but I didnt print it because i still dont have the right to  
translate the english manual.
Is there any way for me to print my book which is about Grass and  
Qgis???
I mean could I somehow take a letter from the Grass team in which  
they will say that I have the right to print my book using as  
basework their work in the english manual??


I am not sure if you are the person I should contact but  
unfortunately I dont have any other mail adresses.

Could you please help me???

Thanks in advance,

Dr. Nicolas Karanikolas
Greece




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

Re: [GRASS-PSC] grass manual translations

[Helena Mitasova]

Hamish, see my second email about this for answers to some of your  
questions.


If I don't hear more comments I will email Nicolas that he does not  
need a letter

from us, he can go ahead and print his material and read the GPL2 for
more details on how to handle it. And if he has any more questions,
he should email to GRASS_dev list ? (although I assume he does not  
not subscribe)


thanks,

Helena


On Feb 23, 2008, at 11:01 PM, Hamish wrote:


Helena Mitasova wrote:

I got an interesting question - see below.
I asked for more details, but when looking at the man pages
there is only Copyright by GRASS Development Team and
no license and no email who to contact in case somebody
wants to use/distribute/reprint etc. the material.


The contact is the "GRASS Development Team". The email contact (if
there should be one) should be the -psc or -dev lists, but that is  
easy

to discover.

The GRASS module document license is the same as the rest of the
software distribution, ie the GPL >=v2.


In fact the Intro pages don't have anything.


fixed in svn.


Should we include Creative commons license for the manual
at each page with a link to explanation of what CC means?
Or should we protect the manual by a stricter license or copyright
and provide contact to person who will handle the request?
( first option looks much better to me)


IMHO we should provide the entire grass .tar.gz release under a single
license. To do other wise would be a mess, especially since the header
sections of the module help pages are directly derived from the GPL'd
module source code. (GPL2 sec. 2b)

Other parts of the project can use different licenses as appropriate,
although for flexibility it would be nice to promote common licenses
and ask that copyright be given to the project so that content can be
used and relicensed around the project's deliverable outputs as  
needed.


The MediaWiki content has been licensed under the GNU Free
Documentation License 1.2.

The website screenshots have been licensed under the CC-Attribution
ShareAlike 2.5 license.

The website generally asserts copyright without specifying a license.

If copyright is asserted, but not license terms, it just means you  
have

to ask the project before you copy/modify/redistribute the content or
assume terms. That's not a bug.


[the fwd'd message]

A few months ago i started making a translation of the Grass manual
and after a lot of changes I prepared a greek manual according to my
student needs.


It is unclear to me which "Grass manual" is being refered to.
The module help pages? intro pages? N&M's GRASS book? Programmer's
manual?

Regardless, this clearly sounds like a derived work.


In the Greek manual I have allready referenced the grass manual but I
didnt print it because i still dont have the right to translate the
english manual.
Is there any way for me to print my book which is about Grass and
Qgis???
I mean could I somehow take a letter from the Grass team in which
they will say that I have the right to print my book using as
basework their work in the english manual??


If it is the module help pages, then derived works are covered under
the terms of the GPL >=v2.


Hamish



   
__ 
__

Be a better friend, newshound, and
know-it-all with Yahoo! Mobile.  Try it now.  http:// 
mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ





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

[GRASS-PSC] GRASS part of NCSU OSI initiative

[Helena Mitasova]

I would like to ask for a permission to list GRASS GIS as a project  
that is part
of the NCSU Open Source Initiative launched at NCSU in collaboration  
with RedHat.
At this point it just means that the project is listed on the OSI web  
site

and I will be working with OIT to get GRASS installed in campus labs and
make it available to several universities and colleges through  
Virtual Computing System (VCL)
(which leads  me to a question whether I should wait for final  
GRASS63 release or

we can start testing at least VCL with GRASS63RC5)

here is the link to the relevant web sites
https://opensource.ncsu.edu/FrontPage
https://opensource.ncsu.edu/OpenSourceProjects

(well, I already listed GRASS and then I realized that it should  
probably go through PSC,

so here is the request).
I assume that we don't need a vote on this and as long as nobody  
objects I am fine,


thank you

Helena

Helena Mitasova
Associate Professor
Department of Marine, Earth
and Atmospheric Sciences
1125 Jordan Hall, Campus Box 8208
North Carolina State University
Raleigh NC 27695-8208
http://skagit.meas.ncsu.edu/~helena/




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

Re: [GRASS-PSC] Re: Copyright and License Statement: affiliation change

[Helena Mitasova]

I agree with suggestions from Markus.
Other PSC members - please respond so that Markus can finalize this  
for the release,


Helena

On Mar 25, 2008, at 6:27 AM, Markus Neteler wrote:

On Fri, Mar 21, 2008 at 10:08 AM, Markus Neteler  
<[EMAIL PROTECTED]> wrote:

Hi PSC,

 in our COPYING file and other places we still list FBK as primary
 headquarter. Martin suggested to change that (although he's still  
there).

 http://trac.osgeo.org/grass/browser/grass/trunk/COPYING

 Proposal (although I would prefer an European address ;-) ):



According to the responses, we can split this into two
parts:

A)

 ...
 The Geographic Resources Analysis and Support System (GRASS)
 Geographic Information System (GIS) is Copyright by the
 GRASS Development Team headquartered at the
 Open Source Geospatial Foundation, USA.
 ...


I suggest to accept the suggestion from Frank:

"is Copyright by members of the GRASS Development Team..."


B)

 Questions regarding GRASS GIS should be directed to the
 GRASS Development Team at the following address:

  GRASS Development Team
  c/o M. Neteler (GRASS PSC Chair)
  Fondazione Mach  -  Centre for Alpine Ecology
  38100 Viote del Monte Bondone (Trento)
  Italy
  neteler osgeo.org
  http://grass.osgeo.org/community/team.php
 ...


I have taken liberty to change my affiliation. It doesn't make
sense to keep an outdated address here. Note that this affected
3 files or so.

Summary: We can concentrate on part A) above. No need to change
thousands of files but just COPYING and likewise.

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


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

Re: [GRASS-PSC] SVN Write Access Request

[Helena Mitasova]

+1

Helena

On May 13, 2008, at 11:11 AM, Michael Barton wrote:


He's done a fantastic job stepping in as a windows binary maintainer.

+1

Michael


On 5/13/08 5:03 AM, "Massimiliano Cannata"  
<[EMAIL PROTECTED]>

wrote:


+1
I know Marco and his good work with the wingrass package.
I vote for give him write access to SVN.

Maxi

[EMAIL PROTECTED] wrote:

Dear Sirs,

with the present mail I'm asking you the SVN write access in  
order to

mantain the tasks related to the experimental WinGRASS project.

Best regards,

Marco Pasetti
 



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





__
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton


___
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] Registering GRASS at OSOR - Fwd: [OSGeo-Discuss] osor.eu - GIS Software Community

[Helena Mitasova]

+1 from me to have GRASS registered at OSOR.eu

Helena

On Aug 26, 2008, at 2:16 PM, Markus Neteler wrote:


GRASS-PSC,

I want to suggest that we get GRASS registered at
OSOR.eu (Open Source Observatory and Repository Europe).

This seems to become a window from/to the European Commission
(see also http://ec.europa.eu/idabc/en/chapter/452 ), so I think that
we should be present.

Eg, the SEXANTE (gvSIG extension) project has registered a stub.
Of course no need to use their infrastructure as we are happy with
OSGeo. They contacted me to participate in their workshop recently,
but I didn't manage to go.
I would register and fill out the relevant metadata if you agree.

Best
Markus


-- Forwarded message --
From: Theodoros G. Karounos <[EMAIL PROTECTED]>
Date: Tue, Aug 26, 2008 at 4:34 PM
Subject: [OSGeo-Discuss] osor.eu - GIS Software Community
To: OSGeo Discussions <[EMAIL PROTECTED]>


The GIS (Geographic Information System) Software Community aims at
supporting the development and referencing the open source geospatial
software on the OSOR. The OSOR GIS Community's goal is to promote
exchange of software and experience, and to encourage the use and
collaborative development of community-led projects. The OSOR GIS
community evolves: this web page is updated regularly.

The OSOR GIS Community workshop (pdfAgenda) - held in Brussels on 27
June 2008 - initiated the building of the community, and discussed how
the OSOR could help the Public Administrations in the re-use and
efficient development of GIS software. The exchange of experience
during the workshop proved very helpful to the attendees, and it was
decided to dedicate a section on the OSOR for further exchanges.

Following the workshop, the Open Data Spatial Publishing project was
initiated on the OSOR, aiming at discussing the need for a license for
the publication of spatial data that guarantees the legal
compatibility of data shared and integrated in an SDI. A mailing list
will soon be set up.

Further collaboration is foreseen and currently under discussion with
other existing GIS networks.
...
http://osor.eu/communities

--
___
Discuss mailing list
[EMAIL PROTECTED]
http://lists.osgeo.org/mailman/listinfo/discuss



--
Open Source Geospatial Foundation
http://www.osgeo.org/
http://www.grassbook.org/
___
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] SVN write access for Yann

[Helena Mitasova]

I would like to propose that Yann Chemin be granted write access
to the main GRASS SVN repository. He has been contributing to GRASS
for many years and has developed or updated many valuable modules which
now reside in add-ons. Several of these modules would be valuable  
addition

to the main GRASS7 code base and with the write access Yann should
be able to add the code and maintain it himself.
When the write access is granted we can discuss with Yann which  
modules to

include into main GRASS (as the discussion on the dev list somewhat died
on this topic).

I am voting +1 to grant Yann write access,

Helena



Yann


can you please send a mail back to this PSC list letting us know  
that you

have read and understood RFC2: Legal Aspects of Code Contributions
http://download.osgeo.org/grass/grass6_progman/rfc/rfc2_psc.html  
and that
the code you submit will be in compliance with this; also that you  
have read
the Submitting Guidelines (file SUBMITTING in the root directory  
of the
source code) and that you will try to follow it when committing  
code that

will be used in GRASS.


Helena Mitasova
Associate Professor
Department of Marine, Earth
and Atmospheric Sciences
1125 Jordan Hall, Campus Box 8208
North Carolina State University
Raleigh NC 27695-8208
http://skagit.meas.ncsu.edu/~helena/



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

[GRASS-PSC] Fwd: Please vote on PSC motion: SVN access for Yann

[Helena Mitasova]

Below is an additional vote from Maciek.
I think that we can now consider this motion passed.
Markus, is it you who actually add the new SVN committers?

I agree with Hamish and Paul that we need to revisit RFC3.
maybe there should be a separate voting procedure for SVN access
with at least 50% members voting yes and then something more flexible
for implementation proposals - although given that most decisions
about development are done on dev list, whatever gets to the committee
is probably pretty serious and the procedure should ensure that at least
50% of the PSC members at least look at the proposal and vote
(even if it is just 0)

Thank you for voting

Helena

Begin forwarded message:


From: Maciej Sieczka <[EMAIL PROTECTED]>
Date: September 11, 2008 4:10:41 AM EDT
To: Helena Mitasova <[EMAIL PROTECTED]>
Cc: Paul Kelly <[EMAIL PROTECTED]>, Dylan Beaudette  
<[EMAIL PROTECTED]>, Massimiliano Cannata  
<[EMAIL PROTECTED]>, Brad Douglas  
<[EMAIL PROTECTED]>, Markus Neteler <[EMAIL PROTECTED]>

Subject: Re: Please vote on PSC motion: SVN access for Yann

Helena Mitasova pisze:

I am aware that some of you are away, but if you have access to
email, please vote on the motion to grant SVN commit access to Yann -
 please email your vote to
grass-psc@lists.osgeo.org
thank you very much, it would be great if we don't let this die  
out because of one missing vote,


Hi Helena,

I've been having temporary problems with sending email from my email
address under which I'm registered to various MLs, including GRASS  
PSC one.


If you don't mind forwarding my email (I'm sending it from another
account), please let Folks know that I'm all supportive for granting
Yann SVN wite access. +1!

Best,
Maciek

--
Maciej Sieczka
www.sieczka.org


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

Re: [GRASS-PSC] SVN write access request

[Helena Mitasova]

+1 from me and welcome!

Colin, please discuss any changes that you plan to do on the dev list,
including whether they should go into GRASS7 or also in GRASS64 (if  
you plan

to do some fixes or enhancements that are broadly needed).

Helena


On Dec 5, 2008, at 7:38 PM, Colin Nielsen wrote:


Hello grass developers,
I am writing to request write access to the SVN so I can make some
updates to the r.cost, r.walk and r.drain modules.
I have read, and accept, the terms of the "Legal aspects of code
contributions (RFC2)", and have created an osgeo_id (cnielsen).

Thanks and let me know if there is any more information you require.

-Colin
___
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] SVN write access request

[Helena Mitasova]

Talking about SVN access - how about granting full SVN access to  
Markus Metz to work on r.watershed in GRASS7
- he has not officially requested it but he expressed interest in it  
and Markus N. encouraged him to post an official request.


Getting his latest improvements into GRASS7 would make it easier to  
test and we may be able to retire r.terraflow

if his version works well for large DEMs.


Helena 
___

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

Re: [GRASS-PSC] request for main SVN write access

[Helena Mitasova]

+1

Helena

On Jan 12, 2009, at 4:07 AM, Markus Neteler wrote:


On Mon, Jan 12, 2009 at 10:01 AM, Markus Metz
 wrote:

To the GRASS Project Steering Committee

following up the suggestion of Markus Neteler [1], I want to  
request main
SVN write access in order to improve r.watershed in grass7 with  
multiple
flow direction and related enhancements. I have read and abide by  
the legal

aspects of code contributions as detailed in RFC2.
 My
osgeo account id is "mmetz".

Please let me know if you require more information.


Excellent, I am +1.

best,

Markus (N)
___
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] Donations for the GRASS project

[Helena Mitasova]

On Mar 3, 2009, at 9:30 AM, Markus Neteler wrote:


PSC,
(cc President of GFOSS.it)

during the last Italian GFOSS/GRASS meeting (last week) we  
discussed again

to add a "donate to GRASS" button (via Paypal) to
http://www.gfoss.it

(also site of the Italian OSGeo chapter).

Given the fact that OSGeo is not interested in small donations (in my
opinion OSGeo errs here ignoring the potential community donations,
see for an old proposal: http://wiki.osgeo.org/wiki/Microdonations
and remember how Wikipedia and OSM get money),


I think it is a huge mistake too - it is not just Wikipedia but many  
other

organizations from moveon.org to Obama, hugely benefited from repeated
small donations.


I suggest to activate
the button.

The money is obviously hold in trust by GFOSS.it for the GRASS  
project.

We could, once some money is accumulated, co-finance bug-squashing
meetings, hack-sessings, promotional material or even invent our
own "GRASS winter/spring/... of code" with a competition for the best
proposals.
GFOSS.it already does the same for the QGIS project.

When operative, we can clone the button on the GRASS main
Web site, too.

Any objections to proceed?


I am all for adding the button for small donations.

We just need to make sure that
there is a trusted person designated to manage the money and that the  
spending
is completely transparent - best posted on-line. Especially these  
days, people want

to know where their money is going, even if it is a small amount,

Helena


Markus

On Thu, Apr 10, 2008 at 12:46 PM, Markus Neteler  
 wrote:
On Tue, Apr 8, 2008 at 4:01 PM, Frank Warmerdam  
 wrote:

Markus Neteler wrote:


While we are at it: do we have guidelines how to set up a new
sponsorship program? I want to launch one for GRASS now given
that we no longer use the IRST server as primary infrastructure.

I see
 http://wiki.osgeo.org/wiki/Project_Sponsorship
but that doesn't address our needs. We want to collect small
money donations first which aren't under level regulations.
Think "donate button".



 Markus,

 We have no program for this, and the sponsorship program was  
explicitly
 established to handle larger amounts because of a concern that  
small

 amounts would prove to be a hassle to manage properly.

 Perhaps the finance committee could consider mechanisms for  
handling

 project directed small donations efficiently.


At this point we could set up our own mechanism (for now).
E.g. the German GRASS Association (a legal entity) could
handle the money on a trust basis in a managed account - they
do it already for the FOSSGIS.de series of conferences.

Of course we need consulations in the PSC and 8if so) with
the German GRASS Association first.

I just wanted to explore the current situation.

thanks,
Markus


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


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

Re: [GRASS-PSC] Re: SVN write access request

[Helena Mitasova]

+1 from me too.

Thank you million times for WinGRASS - it allows us to
incorporate GRASS into our GIST program so we are extremely grateful,

Helena


Helena Mitasova
Associate Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
1125 Jordan Hall
NCSU Box 8208
Raleigh, NC 27695-8208
http://skagit.meas.ncsu.edu/~helena/

email: hmit...@unity.ncsu.edu
ph: 919-513-1327 (no voicemail)
fax 919 515-7802




On Sep 1, 2009, at 3:08 PM, Markus Neteler wrote:

On Tue, Sep 1, 2009 at 8:57 PM, Colin  
Nielsen wrote:

Hello grass developers,
I am writing to request write access to the Main SVN so I can  
continue

to maintain the standalone native WinGrass installer, the scripts
related to WinGrass packaging, and the WinGrass release notes on the
website (rather than sending my patches to Markus).

If I work on any bugs requiring C or Python code I plan to continue  
to

submit this work as patches to the trac system since my coding still
needs reviewing before commit.

I have read, and accept, the terms of the "Legal aspects of code
contributions (RFC2)", and have an osgeo_id (cnielsen).

Thanks and let me know if there is any more information you require.


I am all for it :-) +1

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


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

Re: [GRASS-PSC] Re: v.krige moved to trunk and devbr6 - SVN access request

[Helena Mitasova]

+1 from me too.
Ann, welcome to GRASS development team and
I hope you will be around often and for many years to come.

As Martin said it may take until early January until everybody  
(especially Markus)

get back on-line and the access can be activated

best regards

Helena

On Dec 25, 2009, at 8:53 PM, Hamish wrote:


Anne:
I'd like to ask for extension of write access to main SVN  
repository,

as v.krige is now part of trunk and develbranch_6. The module,
developed during Summer of Code 2009,

[...]

I've agreed with Martin that until the decision of PSC I'll continue
development by sending him patches.


Martin:

I am not member of PSC anyway I support Anne in her request.


It's fine with me, Anne is a most welcome contributer, brings much  
needed

QGIS plugin expertise, & is a source of positive energy.  Fair warning
that due to the holidays & all it may take a week or two to hear back
from everyone & before we can act on this.


ho ho ho & bbqs on the beach,
Hamish




___
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] Request for SVN-write-access

[Helena Mitasova]

+1 for SVN-write-access for Helmut,
thanks for the great work on WinGRASS, many students here greatly appreciate it,

Helena

On Jan 17, 2010, at 3:08 PM, Helmut Kudrnovsky wrote:

> hi,
> 
> recently I've helped in Windows-related things (testing, building 
> WinGrass-installer for testing, etc.) and SVN-write-access would make this 
> easier.
> 
> So I've read and accepted the Legal aspects of code contributions (RFC2) and 
> request for SVN-write-access.
> 
> My OSGEO-ID is hellik
> 
> best regards
> Helmut
> 
> 
> ___
> Preisknaller: WEB.DE DSL Flatrate für nur 16,99 Euro/mtl.! 
> http://produkte.web.de/go/02/
> 
> ___
> 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] Proposal: "donate some money to squash your most annoying bug"

[Helena Mitasova]

at first I was quite excited about it but when I thought about potential 
unintended consequences 
it appeared to me that people may stop submitting bug fixes for free and just 
wait until
enough people are willing to pay for it. I would wait to see how it works out 
for QGIS community.
It may have an effect of reduced bug fixing unless there is a good pool of 
money 
to get the fixes done.
Organizing set of needed bug fixes into an interesting GSoC project or student 
class project
may be safer,

Helena 

On Mar 22, 2010, at 6:42 PM, Dylan Beaudette wrote:

> On Saturday 20 March 2010, Markus Neteler wrote:
>> Hi PSC,
>> 
>> following the QGIS idea of
>> "Donate some money to squash your most annoying bug"
>> http://www.qgis.org/wiki/Bugs
>> 
>> I would suggest to do likewise for the GRASS bugs. The overhead
>> is almost zero, money directly payed from the donor(s) to the
>> bugfixer and all denoted in the Wiki.
>> 
>> How does it work:
>> * a user suggests a bug to be fixed in the Wiki with some seed
>>  funding including a precise description of his/her expectations;
>> * more users add money as needed until someone picks it up and
>>  fixes it for the available amount;
>> * the developer is payed directly by the donor(s).
>> 
>> The "normal" bug squashing business continuous of course as usual.
>> 
>> What do you think?
>> 
>> Markus
> 
> 
> Hi Markus,
> 
> It sounds like a good idea, as long as funds can be transparently accounted 
> for. What mechanism is used for payment? Also, it would be a useful to have 
> several people notified before a transaction is completed, as an additional 
> level of oversight. 
> 
> Cheers,
> Dylan
> 
> 
> -- 
> Dylan Beaudette
> Soil Resource Laboratory
> http://casoilresource.lawr.ucdavis.edu/
> University of California at Davis
> 530.754.7341
> ___
> 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] Fwd: GRASS-Addons-SVN acces request

[Helena Mitasova]

+1 for granting Alfonso SVN add ons access,

Helena 

On Aug 12, 2010, at 3:18 PM, Markus Neteler wrote:

> Forward to PSC
> 
> -- Forwarded message --
> From: Alfonso Vitti 
> Date: Thu, 05 Aug 2010 16:16:00 +0200
> Subject: GRASS-Addons-SVN acces request
> To: Markus Neteler 
> 
> Dear Markus,
> 
> as you know, I've developed a GRASS module for image segmentation and
> discontinuity detection, see www.ing.unitn.it/~vittia/sw for details.
> Thus, I kindly ask you to support my request to get write access to the
> GRASS-Addons-SVN repository to have the module hosted there.
> 
> I've read the document "Legal aspects of code contributions" (RFC2) and
> I accept it.
> 
> 
> Many thanks in advance and best regards,
> Alfonso
> ___
> 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] Re: GRASS Annual report 2010

[Helena Mitasova]

Markus,

I will add something later today,
I looked at some other reports and found the bulleted list such as this one 
easier to read than the continuous text, so I will stick with it.

Helena 


On Sep 24, 2011, at 6:41 PM, Markus Neteler wrote:

> On Thu, Sep 22, 2011 at 11:35 PM, Markus Neteler  wrote:
>> Hi,
>> 
>> please help me to complete the
>> http://wiki.osgeo.org/wiki/GRASS_GIS_Report_2010
>> 
>> Ideally it would not only be an annoying list but also some
>> text for the OSGeo Journal (maybe to be put under the list).
>> 
>> Thanks for your help (direct editing would be ideal),
> 
> Please consider to waste 2 min on this, thanks...
> 
> Markus
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc

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

Re: [GRASS-PSC] Generous donation received

[Helena Mitasova]

I agree with Martin - the donor must agree to have his name published.
With the agreement it is certainly a good idea to publish the names - it may 
inspire more people to donate.

Helena 


On Sep 29, 2011, at 5:54 PM, Martin Landa wrote:

> 2011/9/29 Markus Neteler :
>> one question: do we want to list donors on the web site as the QGIS
>> project does?
> 
> I am not the psc-member, so just my personal opinion. I think it's a
> good idea to publish donors if they want. The form could contain
> question: "Do you want to publish on the GRASS website that you
> donated this amount?"
> 
> Martin
> 
> -- 
> Martin Landa  * http://geo.fsv.cvut.cz/~landa
> ___
> 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] GRASS-SVN access

[Helena Mitasova]

I support granting Vaclav access to the main GRASS-SVN repository,

Helena

On Wed, May 30, 2012 at 2:36 PM, Markus Neteler  wrote:
> Dear PSC members,
>
> On Wed, May 30, 2012 at 2:28 PM, Vaclav Petras  wrote:
>> Hello,
>>
>> my name is Vaclav Petras and I'm asking you for the write access to
>> the main GRASS-SVN repository. I worked on wxIClass and now I start
>> working at wxGUI part of d.mon. I'm in touch with Martin Landa and
>> Markus Neteler. I read RFC 2: Legal aspects of code contributions.
>
> I know Vaclav Petras from two code sprints, he's doing excellent work
> for GRASS already. So far his changes have been committed by
> Anna Kratochvílová who has write access.
>
> We state in our procedure that:
> "After a period of evaluation, SVN write access may be granted and
> is set up in the OSGeo authentication system."
>
> I motion to grant write access already now since Vaclav has
> a notable record of contributions in the core GRASS system.
>
> If there are no objections in the next days, I'll set up his account to
> the main GRASS SVN repository.
>
> Best
> Markus
> _______
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc



-- 
Helena Mitasova
Associate Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
1125 Jordan Hall
NCSU Box 8208
Raleigh, NC 27695-8208
http://skagit.meas.ncsu.edu/~helena/

email: hmit...@ncsu.edu
ph: 919-513-1327 (no voicemail)
fax 919 515-7802
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC management

[Helena Mitasova]

I agree with Markus that PSC should have members involved in all kinds
of contributions
and who have enough time to keep up with the new developments and discussions
about important issues.

I am still on the road (currently in Bratislava) and I should be back
to work in mid June.

I would like to confirm my interest to continue as member of PSC.

Helena

On Wed, May 30, 2012 at 11:58 AM, Markus Neteler  wrote:
> On Mon, May 28, 2012 at 7:23 PM, Massimiliano Cannata
>  wrote:
>> I'm interested in continue.
>> Even though I'm not a core developer I feel I have demonstrated a
>> substantial involvement in GRASS GIS (I) giving courses for engineers,
>> architects and professionals (II) conducting research in natural hazards
>> using grass (see foss4g presentations from Bangkok to Denver).
>> In any case if you think someone else is more appropriate I'm ready to make
>> a step back.
>
> Please don't since all kinds of contributions are important, not only coding.
>
> Thanks also to Scott, Michael and Dylan for their replies.
> (Helena is on the road but was in Prague discussing this topic).
> Yann replied offlist to me that he is stepping back but also that he
> hopes to come back.
>
> Some members didn't answer yet:
> http://grass.osgeo.org/wiki/PSC
>
> Best
> Markus
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc



-- 
Helena Mitasova
Associate Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
1125 Jordan Hall
NCSU Box 8208
Raleigh, NC 27695-8208
http://skagit.meas.ncsu.edu/~helena/

email: hmit...@ncsu.edu
ph: 919-513-1327 (no voicemail)
fax 919 515-7802
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Access to upload python addon/skript

[Helena Mitasova]

I am not sure whether my vote is needed on this but in case yes: +1 from me - 
it sounds like an interesting and useful module,

Helena
 
Helena Mitasova
Associate Professor
Department of Marine, Earth, and Atmospheric Sciences
2800 Faucette Drive, Rm. 1125 Jordan Hall
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu

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

On Aug 8, 2012, at 7:30 AM, Johannes Radinger wrote:

> Dear GRASS Project Steering Committee!
> 
> First, thank you Markus for your previous answers!
> 
> Following the in "How to contribute..." 
> (http://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASS-Addons-SVNrepository),
>   I'd like to sent an official request for writing access to the GRASS AddOn 
> SVN repository. I read and agree with the "Legal aspects of code 
> contribution" (RFC 2). 
> Furthermore my osgeoid is: jradinger
> 
> Thank you very much!
> 
> Best regards,
> 
> Johannes Radinger
> 
> 2012/8/8 Markus Neteler 
> Hallo Johannes,
> 
> klingt gut! Die Prozedur ist hier:
> 
> http://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASS-Addons-SVNrepository
> --> Write access to the GRASS-Addons-SVN repository
> 
> Schoene Gruesse
> Markus
> 
> 2012/8/8 Johannes Radinger :
> > Hallo Markus,
> >
> > Ich möchte gerne meine Skripte und AddOns mit der GRASS-Community teilen
> > und dazu gerne auf die GRASS AddOn/Skript Plattform laden. In wenigen
> > Monaten
> > soll das vor allem das "Fish Dispersal Model" sein das ich in Prag
> > vorgestellt habe.
> > Im Moment ist es ein Python Skript für einen Rasterfilter basierend auf
> > realen Distanzen
> > (umgesetzt mit r.cost). Wie ist es möglich das ich meine Beiträge (im Moment
> > nur AddOns
> > und kein GRASS corecode) via SVN hochladen kann?
> >
> > viele Grüße aus Berlin
> > Johannes
> 
> ___
> 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] request access to the core svn

[Helena Mitasova]

+1 from me as well

Helena Mitasova
Associate Professor
Department of Marine, Earth, and Atmospheric Sciences
2800 Faucette Drive, Rm. 1125 Jordan Hall
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu

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

On Oct 1, 2012, at 6:38 AM, Markus Neteler wrote:

> On Mon, Oct 1, 2012 at 12:36 PM, Pietro  wrote:
>> On 10/1/12, Pietro  wrote:
>>> I read RFC 2: Legal aspects of code contributions
>> 
>> I will abide by the document: Legal aspects of code contributions (RFC2)
> 
> +1 to enable Pietro Zambelli to gain write access to GRASS core
> in order to implement and maintain the pyGRASS API.
> 
> Markus
> 
> PS: All PSC members have to vote.
> ___
> 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] [GRASS-dev] Renewal of GRASS-PSC

[Helena Mitasova]

I am not sure I responded (I may be the last one?)  but I vote for all nominees 
to be included in the PSC

Helena

Helena Mitasova
Associate Professor
Department of Marine, Earth, and Atmospheric Sciences
2800 Faucette Drive, Rm. 1125 Jordan Hall
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu

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

On Nov 12, 2012, at 2:46 PM, Markus Neteler wrote:

> PSC,
> 
> as a reminder for slots and such, the original email below.
> 
> The nominees are listed here (temporarily on grassold.osgeo.org during
> tricky site migration):
> http://grassold.osgeo.org/wiki/PSC_election_2012
> 
> Markus
> 
> -- Forwarded message --
> From: Markus Neteler 
> Date: Mon, Oct 8, 2012 at 11:20 AM
> Subject: Renewal of GRASS-PSC
> To: GRASS user list , GRASS developers
> list 
> 
> Dear all,
> 
> the GRASS-PSC (GRASS Project Steering Commitee, see also
> http://grass.osgeo.org/wiki/PSC ) formally oversees the activities
> of the GRASS GIS project. It operates at a low level of complication.
> 
> Since several members stepped down in this year due to time constraints
> or other reasons, we need to start the process to renew parts of the PSC.
> 
> List of current PSC members:
> - Hamish Bowman
> - Helena Mitasova
> - Markus Neteler (chair)
> - Massimiliano Cannata
> - Michael Barton
> - Scott Mitchell
> 
> Former PSC members:
> - Brad Douglas
> - Dylan Beaudette
> - Paul Kelly
> - Maciej Sieczka
> 
> In essence we have 4 slots available.
> 
> This is the "call for nomination" to obtain a list of people with
> recognized contribution to the GRASS project.
> The proposer should nominate community member(s) along
> with a small paragraph describing why the candidate is
> proposed as PSC member.
> We'll collect the nominations on a Wiki page and figure out
> how to identify the four new members if we get more than four
> candidates :)
> 
> Best
> Markus
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc

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

Re: [GRASS-PSC] Vice PSC chair selection

[Helena Mitasova]

Massimiliano,

I was just about to propose Martin Landa, if he agrees - I think we need 
somebody who can work on the release packaging
like Markus did. I will certainly help.

Other PSC members, please let us know your suggestions,

Helena 

On Dec 12, 2012, at 12:52 PM, Massimiliano Cannata wrote:

> Hi there
> hope in Padova things will Howard smoothly and fast.
> 
> If she agree, I would propose Helena as vice for her knowledge of the grass 
> community and leadership.
> Maxi
> 
> Il giorno 12/dic/2012 18:28, "Markus Neteler"  ha scritto:
> Dear PSC,
> 
> let me propose to select a vice chair in case that I am unable to
> respond for some time [1]. I would suggest to select a person
> among us to keep it simple, i.e. the PSC members may agree
> upon someone from us to act as Vice Chair.
> Perhaps the decision should then be communicated to the
> OSGeo board.
> 
> Best
> Markus
> 
> [1] Currently in Padova awaiting a heart surgery next week, ops.
> ___
> 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] Vice PSC chair selection

[Helena Mitasova]

Dear Markus and PSC members,

I will gladly step in as Vice Chair to give Markus peace of mind that GRASS is 
being taken care of
in case anything needs attention at the PSC chair level. 
Our community-based development hopefully won't see
any change and we will have Markus back soon.

Thank you for your support

Helena 

On Dec 12, 2012, at 12:28 PM, Markus Neteler wrote:

> Dear PSC,
> 
> let me propose to select a vice chair in case that I am unable to
> respond for some time [1]. I would suggest to select a person
> among us to keep it simple, i.e. the PSC members may agree
> upon someone from us to act as Vice Chair.
> Perhaps the decision should then be communicated to the
> OSGeo board.
> 
> Best
> Markus
> 
> [1] Currently in Padova awaiting a heart surgery next week, ops.
> ___
> 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] Invitation to donate for the GRASS GIS Community Sprint in February 2013

[Helena Mitasova]

+1 for Luca

Helena 
On Dec 28, 2012, at 12:20 PM, Markus Metz wrote:

> On Fri, Dec 28, 2012 at 5:01 PM, Margherita Di Leo  wrote:
>> 
>> 
>> On Fri, Dec 28, 2012 at 4:57 PM, Martin Landa 
>> wrote:
>>> 
>>> 2012/12/28 Massimiliano Cannata :
 +1 for Luca Delucchi
>>> 
>>> +1 for Luca.
>> 
>> 
>> +1 Luca
>> 
> +1 for Luca
> 
> Markus M
> ___
> 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] GRASS Community Sprint 2013 - email for possible sponsors

[Helena Mitasova]

Looks good to me too. Depending on where you send or post it you may also want 
to create a shorter version,
some people who get lot of emails or just scan a webpage may not get past the 
first paragraph.
I will check how difficult it is to pay from the US to this account - if it too 
complicated, it may deter potential donors.
Is there a reason why Paypal or some other credit card service cannot be used 
(high fees perhaps?, I am just curious,
I don't really know much about this),

Helena

Helena Mitasova
Associate Professor
Department of Marine, Earth, and Atmospheric Sciences
2800 Faucette Drive, Rm. 1125 Jordan Hall
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu

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

On Jan 10, 2013, at 11:20 AM, Michael Barton wrote:

> Looks good. Thanks.
> 
> Michael
> __
> C. Michael Barton 
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Arizona State University
> Tempe, AZ  85287-2402
> USA
> 
> voice: 
> 480-965-6262 (SHESC), 480-727-9746 (CSDC)
> fax:  480-965-7671(SHESC), 480-727-0709 (CSDC)
> www: 
> http://csdc.asu.edu, http://shesc.asu.edu
> http://www.public.asu.edu/~cmbarton
> 
> On Jan 10, 2013, at 2:34 AM, Margherita Di Leo 
>  wrote:
> 
>> Dear Members of the PSC,
>> 
>> since the GRASS Community Sprint is approaching, I've been asked by Luca 
>> Delucchi, who is in charge to collect the donations for the event, to 
>> prepare an e-mail to be sent to the main companies that make extensive use 
>> of GRASS for their work (he is currently listing their email addresses) in 
>> order to ask whether they would be willing to sponsor the event. We thought 
>> that such email should be sent on behalf of PSC by one member (I could do 
>> that if it's OK for you). Please find below the content of the email we are 
>> proposing to send and please feel free to propose any modification.
>> 
>> ---%<---
>> 
>> The GRASS GIS team will organize a GRASS Developer and Power User Meeting, 
>> aka 'GRASS Community Sprint' from 2-7 Feb, 2013 [1]. The Community Sprint is 
>> a get-together for GRASS project members and supporters and related OSGeo 
>> projects to make decisions and tackle larger problems. For this meeting, we 
>> welcome people committed to improving the GRASS GIS project and the 
>> interfaces to QGIS, GDAL, PostGIS, R statistics, Sextante, gvSIG, OGC 
>> Services (esp. WPS) and more. This includes developers, documenters, bug 
>> reporters, translators and others.
>> 
>> The outcomes of past editions include wxGUI bugfixing, GRASS 7 time series 
>> and 4D data management, translations, implementation of new modules and lots 
>> of bughunting, testing, and bugfixing. For interoperability, the new 
>> QGIS-Sextante-GRASS interface was completely overhault and updated. 
>> Developers also had discussions on broad topics like GRASS GIS usage mobile 
>> devices, creation of a visual guide to GRASS GIS usage and much more. See 
>> [2,3] for details.
>> 
>> The third GRASS Community Sprint is a great occasion for you to support the 
>> development of GRASS. With your contribution you'll enable more developers 
>> to meet. The Community Sprint is an important opportunity for the GRASS 
>> developers to discuss and collaboratively resolve bugs, plan the direction 
>> for the project and work on new features. Developers and contributors are 
>> donating their valuable time, so it would be great if in-kind funding can be 
>> made available from within the community to cover out-of-pocket expenses. 
>> All of the work that takes place at the community sprint will be directly 
>> contributed back into the GRASS project to the benefit of everyone who uses 
>> it. 
>> 
>> This year the Italian OSGeo Local Chapter (GFOSS.it [4]) is in charge of 
>> gathering all the donations. Donations should be addressed to:
>> 
>> "Associazione Italiana per l'Informazione Geografica Libera"
>> 
>> Details of bank account:
>> 
>> IBAN: IT32J033590160010015079
>> BIC: BCITITMX 
>> BANCA PROSSIMA S.P.A. Via Verdi Ang. Via Manzoni - 20121 Milano
>> 
>> Any further question about donations should be addressed to Luca Delucchi 
>> 
>> 
>> On behalf of the GRASS Community I would like to thank you in advance and to 
>> wish you happy new year.
>> 

[GRASS-PSC] GRASS GIS 2012 report

[Helena Mitasova]

I have prepared a draft report about GRASS GIS for the OSGEO report 2012. It is 
based on the report submitted by Markus in 2011,
I just updated it with the 2012 accomplishments and events. Please add your 
activities and whatever I have missed, modify, and fix,
the report is here
http://wiki.osgeo.org/wiki/GRASS_GIS_Report_2012

Thank you,

Helena

Helena Mitasova
Associate Professor
Department of Marine, Earth, and Atmospheric Sciences
2800 Faucette Drive, Rm. 1125 Jordan Hall
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu

"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
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Branding rules to be defined

[Helena Mitasova]

same here,

Helena Mitasova
Associate Professor
Department of Marine, Earth, and Atmospheric Sciences
2800 Faucette Drive, Rm. 1125 Jordan Hall
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu

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

On Jan 17, 2013, at 1:12 AM, Michael Barton wrote:

> This is exactly how I've used it.
> 
> So +1 for me.
> 
> Michael
> 
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity 
> Professor of Anthropology, School of Human Evolution & Social Change
> Arizona State University
> 
> voice:480-965-6262 (SHESC), 480-727-9746 (CSDC)
> fax:  480-965-7671 (SHESC),  480-727-0709 (CSDC)
> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Jan 16, 2013, at 10:46 PM, Markus Neteler 
> wrote:
> 
>> Hi PSC,
>> 
>> we need to define rules how to name GRASS GIS. There is a discussion in
>> [GRASS-user] Upon improving the GRASS-wiki
>> 
>> Here my few cents:
>> 
>> While the original name of the 80s has been 'GRASS', for
>> obvious reasons that isn't too clear. I write 'GRASS GIS' (no dash!)
>> for many years where appropriate.
>> 
>> So, in the new CMS Website, on page top 'GRASS GIS', then down perhaps
>> only 'GRASS' for readability.
>> 
>> In titles always 'GRASS GIS'. So readers always know that we are
>> speaking about a GIS.
>> 
>> Makes sense?
>> 
>> Markus
>> ___
>> grass-psc mailing list
>> grass-psc@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-psc
> 
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc

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

Re: [GRASS-PSC] request access to the core svn

[Helena Mitasova]

+1
Helena

On Feb 6, 2013, at 3:25 PM, Moritz Lennert wrote:

> On 06/02/13 12:50, Martin Landa wrote:
>> Dear PSC,
>> 
>> I would like to nominate Stepan Turek to have write access also to the
>> core SVN (he has already write access to add-ons). Stepan has been
>> working under my supervision on various projects related to the GRASS
>> development. He is author of the new generation of `r.in.wms` in GRASS
>> 7 [1], within Google Summer of Code he developed wxGUI vector network
>> analysis tool [2]. Recently he added WMS support to wxGUI [3],
>> currently working on wxGUI scatterplot tool. He is planning to
>> continue in his work for GRASS, to maintain the tools he developed. I
>> think it's reasonable to provided write access to the main SVN for
>> him.
>> 
>> Thanks for you feedback.
> 
> +1
> 
> Moritz
> ___
> 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] Call for donors - GRASS Community Sprint 2013 in Prague

[Helena Mitasova]

 Margherita or Martin,

could you please encourage people on dev and users list who plan to come to 
sign up on the wiki ?
The sponsors will be more likely to donate if they see that there are more 
people signed up.

Helena

On May 28, 2013, at 8:32 AM, Margherita Di Leo wrote:

> Dear PSC Members,
> 
> since the next GRASS Community Sprint [1] is approaching, I'd circulate an 
> email to the potential sponsors, which are listed here [2]. This list was the 
> one prepared for the previous event in Genoa. If you know any other potential 
> donor, could you please add their email to the list.
> 
> Thanks and best regards,
> Madi
> 
> [1] http://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Prague_2013
> [2] http://titanpad.com/i1rzvNEV39
> 
> -- 
> Best regards,
> 
> Margherita DI LEO
> Postdoctoral Researcher
> 
> European Commission - DG JRC 
> Institute for Environment and Sustainability (IES)
> Via Fermi, 2749
> I-21027 Ispra (VA) - Italy - TP 261
>
> Tel. +39 0332 78 3600   
> margherita.di-...@jrc.ec.europa.eu
> 
> Disclaimer: The views expressed are purely those of the writer and may not in 
> any circumstance be regarded as stating an official position of the European 
> Commission.
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc

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

Re: [GRASS-PSC] applying for svn writing access

[Helena Mitasova]

Margherita,

> Margherita wrote:
> 
>> in Vienna I've been working on manual pages cleanup on addons for their
>> moving to trunk. Since the manual pages in trunk
>> still need a good deal of clean up work, I would like
>> to apply for SVN writing access. My OSGeo ID is madi.
> 
> I thought you'd already had it. :)  guess not.

same here (I think it was for add-ons only)
> 
> You have my full support conditional on the statement-for-the-archives 
> agreeing to RFC2 as it pertains to the main repository.

you have my full support too and Hamish is right that the official statement is 
needed for the record,
https://trac.osgeo.org/grass/wiki/HowToContribute

Helena
> 
> 
> regards,Hamish
> ___
> 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] [GRASS-dev] too many branches => retirement GRASS6.5.svn (=develbranch6)

[Helena Mitasova]

I believe that we have a communication problem here rather than a disagreement 
about the GRASS6.5:

Hamish says:
"GRASS 6.x is already far along into bugfix maintenance mode.
*Please, just leave it to naturally and quietly make its way into history.*
 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. "

which is pretty much in agreement with Martin's:
"I think we should really stop thinking about GRASS 6 "development",
So please bug fix only should go there (relbr64). No new functionality."

So I think that we have a broad agreement on maintenance only mode for grass6 
line,
and if there is a concern that new features will be added to grass6.5, perhaps 
we can keep it
in read-only mode as suggested in one of the initial emails in this discussion 
and have
only Hamish keep write access for testing ("staging area").

I think that if Hamish can maintain GRASS6 line this will free the time for all 
other developers to focus on GRASS7.
Regarding GRASS7 - it is in a pretty good shape, we have been using it in 
classes since the fall semester
and I was quite surprised how little changes are needed to update the full 
semester course material for GRASS7.

Helena



Helena Mitasova
Associate Professor
Department of Marine, Earth, and Atmospheric Sciences
2800 Faucette Drive, Rm. 1125 Jordan Hall
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu

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

On Apr 6, 2014, at 4:45 PM, Markus Metz wrote:

> On Sun, Apr 6, 2014 at 3:16 PM, Moritz Lennert
>  wrote:
>> On 06/04/14 13:46, Hamish wrote:
>> 
>> 
>>> 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.
> 
> I don't see the need for a devbr6 because maintaining the GRASS 6 line
> means backporting bug fixes from trunk. New functionality should be
> implemented in trunk, as in any other project. Bug fixes are then
> backported to the release branch, unfortunately we have now two
> release branches. Apart from addons, there will most probably not be
> any more GRASS 6 development, only GRASS 6 bug fixing, for which a
> GRASS 6 release branch is IMHO sufficient.
> 
> I don't think it makes sense to maintain two GRASS major versions if
> development aka adding new functionality should take place in both.
> Some contributors like to implement new functionality in devbr6, but
> most contributors follow the (IMHO logical) way of trunk -> relbr. The
> now proposed development way of trunk -> relbr_7 -> devbr6 -> relbr6
> or or also devbr6 -> relbr6, skipping trunk, is unrealistic, will slow
> down GRASS development, and might lead to diverging branches.
> 
> If GRASS 6, and release branch maintenance in general, is restricted
> to bug fixing, it should be easy to maintain trunk and two release
> branches. Granted that trunk is not abused as addon repository by
> adding untested code.
> 
> My 2c,
> 
> Markus M
> 
> 
>>> 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
> ___
> grass-dev mailing list
> grass-...@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev

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

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

[Helena Mitasova]

I agree with the voting rules with the following changes/comments:

- change 4 business days to seven days to avoid confusion given that business 
days may be different in different countries due to holidays (as already 
suggested)
- I am confused about #6 - does this mean that it is enough for 2 PSC members 
(out of 10?) to agree to accept a proposal?
Should we have at least a simple majority? Does this voting procedure apply to 
svn access as well?

Helena

Helena Mitasova
Associate Professor
Department of Marine, Earth, and Atmospheric Sciences
2800 Faucette Drive, Rm. 1125 Jordan Hall
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu

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

On Apr 6, 2014, at 6:48 AM, 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
> 
> 
> Issues:
> - people are travelling and periodically offline
> - not all members may need to vote (majority, quorum, etc)
> - keep it simple
> - ...
> 
> Best,
> Markus
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc

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

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

[Helena Mitasova]

+1

although I am wondering whether there should be some clarification that in

5. it is 51% of the members voting on this particular proposal (meaning that a 
vote from all PSC members
is not needed to pass a proposal)

"5. A proposal will be accepted if it receives majority (51% including the 
proposer) of votes (+1) and no vetoes (-1)."

while in 
8. we are talking about all members of PSC which is clearly stated there.

"8.If a proposal is vetoed, and it cannot be revised to satisfy all parties, 
then it can be resubmitted for an override vote in which a majority of all 
eligible voters indicating +1 is sufficient to pass it. Note that this is a 
majority of all committee members, not just those who actively vote."

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

Helena

Helena Mitasova
Associate Professor
Department of Marine, Earth, and Atmospheric Sciences
2800 Faucette Drive, Rm. 1125 Jordan Hall
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu

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

On Jul 31, 2014, at 8:44 AM, Markus Neteler wrote:

> On Thu, Jul 31, 2014 at 12:05 PM, Margherita Di Leo  
> wrote:
>> Hi,
>> 
>> shouldn't we be voting upon this new rules proposal at a certain stage?
> 
> right!
> 
> PSC [1]: are you all happy with this version?
> http://trac.osgeo.org/grass/wiki/RFC/3_PSCVotingProcedures
> 
> Markus
> 
> [1] Members: http://trac.osgeo.org/grass/wiki/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] RFC3: New voting rules

[Helena Mitasova]

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

> On Sat, Aug 23, 2014 at 3:49 PM, Martin Landa  wrote:
>> Dear PSC,
>> 
>> 2014-08-17 21:37 GMT+02:00 Markus Neteler :
>> 
>> [...]
>> 
 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=diff&version=10&old_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
> 
> So far not all
> http://trac.osgeo.org/grass/wiki/PSC#Members
> 
> expressed their view. This may be fine but since it is the "vote about
> voting procedures", we need to be
> sure that we got the RFC3 proposal right.
> 
> I am fine to call for a vote in the next days.
> 
> Best
> Markus
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc

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

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

[Helena Mitasova]

+1 from me as we are going around the world. 

Helena

Helena Mitasova
Professor at the Department of Marine, 
Earth, and Atmospheric Sciences
and Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu
http://geospatial.ncsu.edu/osgeorel/
"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.” 

On Aug 25, 2014, at 8:19 AM, Scott Mitchell wrote:

> +1
> 
> Scott
> 
> On Aug 25, 2014, at 05: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.
>> 
>> Markus
>> 
>> -- 
>> GRASS GIS PSC Chair
>> http://grass.osgeo.org/
>> http://courses.neteler.org
>> http://gis.cri.fmach.it/neteler/
>> ___
>> 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] RFC3: New voting rules

[Helena Mitasova]

Hamish,

you make many good points, but to follow proper procedures, the text cannot
be changed after other members of PSC already voted for it. Just to recall
the timeline of this RFC3:

July 31 call for comments
Aug 25 motion called and seconded
Sep 20 all votes received except one

So if we want to modify the text we need to close this vote (which Markus
should do today), then open a new discussion about the voting rules
modification and call a new vote so that all PSC members can vote about the
new text.

Your points are really important and after a discussion they have a
potential to improve the voting process so I suggest that we follow the
procedure outlined above - finish the vote on the current RFC3 and then you
should start a discussion on modifications - the below comments are a good
start.

I hope this is acceptable to everyone,

Helena

On Sun, Oct 5, 2014 at 10:29 PM, Hamish  wrote:

> Hi all,
>
> sorry for my long absence, I've hardly been on email at all for many
> weeks now. (and enjoying the break from distractions! :) I certainly
> haven't caught up with all the messages in my inbox, there's a good
> chance I've missed things.
>
> But since people want to get moving, here are my comments on the text of
> RFC3 as it appears on the trac wiki today. (I guess that makes it
> version 10 according to trac)
>
>
> In general it just codifies what we're already doing, so no big
> surprises. Devil is in the details, and we are detail oriented
> people, so let's get this right. :)
>
>
> Proposals (2): make it clear that the Chair is the to to decide that "no
> more progress is being made", and close the vote in that case. The last
> sentence of (2) seems to indicate that, but the wording is a bit muddy.
>
> Voting (3): Strike the invalid veto text. I will not support passing
> RFC3 with that in place. Who is to judge that the reasons given are
> clear? What if we know something is definitely not the right solution
> but don't know the correct answer? In yacht racing we used to have a
> saying: "even if you do not know what the right thing to do is,
> especially then, never knowingly do the wrong thing."
> If nothing else it is IMHO quite disrespectful to our fellow PSCers.
>
> Voting (4): "... but has no effect" -- "other than to formally indicate
> the voter's position." (which should hold community weight even if it
> doesn't count in the calculus of the vote, so should be given a nod
> in the text)
>
> [new] Voting (9): The Chair is responsible for validating the final
> result. (or some text like that, we don't seem to explicitly say it
> elsewhere)
>
>
>
> some other points to consider:
>
> - lesser threshold for granting commit rights? (100% PSC members
> answering not req'd, just a quorum of 51% and no vetos. moreover
> maybe a shorter timeout of 3-4 days for these. Voting (8) mentions
> "active voters" but AFAICT elsewhere we don't formally discuss
> absentees vs. abstainers)
>
>
> - passing rfc by simple majority, or require a higher threshold?
> - overriding a veto by simple majority, or require a higher threshold?
>
> in both the above cases it seems to me the healthiness of the overall
> project would benefit by forcing us to work very very hard to come to a
> real consensus rather than expedite a quick decision. FOSS runs on good
> interpersonal relationships; any chance of unresolved bad feelings being
> left in the wake of a decision can be quite toxic to the long term heath
> of the project and avoided at all costs.
>
>
> As I catch up on my email I'll reply to the RFC3 threads on the PSC
> list inline, probably there are many fine points made by others
> already that I missed. :)
>
>
> regards,
> Hamish
>
>
> ps- I still strongly believe that a wiki is not the place to house
> approved RFCs, it should be in a more formal and secure VCS, such as
> Subversion. It is not necessary to keep it in the source code tarball,
> but that does have the benefit of widely disseminating copies. For
> historical changelog + diff interest, developing the RFC text in the
> final VCS would be preferable. (culturally, commit log messages tend to
> be much better in SVN than in a wiki, and the "why" of a change is quite
> important in this context. also the wiki is open to anyone on the
> internet who cares to create an account. will our RFCs get spammed or
> vandalized? even if approved motions are converted to locked pages, that
> doesn't work for working documents. these aren't some simple help page.)
> ___
> grass-psc mailing list
> grass-psc@

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

[Helena Mitasova]

I agree with Maris that no feedback should be interpreted as agreement. 
A statement : "if there are no further comments or feedback for the 7 days, RC1 
will be released on XXX date"
may help in case somebody has some issues and was just delaying posting them.

Also for the PSC, it appears that the release procedure is ready to be voted on?
http://trac.osgeo.org/grass/wiki/RFC/4_ReleaseProcedure

Helena



On Dec 29, 2014, at 3:11 AM, Maris Nartiss wrote:

> IMHO "lack of answer" in a transparent procedure with reasonable
> response windows just means "carry on, everyone agrees". Having a
> fixed last date for comments might force someone to say something (or
> used as an argument for STFU later).
> 
> 
> Just my 0.02,
> Māris.
> 
> 
> 2014-12-29 9:50 GMT+02:00 Markus Neteler :
>> On Mon, Nov 24, 2014 at 2:50 PM, Moritz Lennert
>>  wrote:
>>> 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.
>> 
>> While this is all nice, I am strongly lacking support in the day to
>> day release management.
>> Again the RC1 feedback is actually 0 (zero).
>> 
>> The "General Procedure" in the document is lacking answers to what to
>> do if no or no reasonable feedback occurs.
>> Any ideas? We are in soft freeze for months.
>> 
>> Markus
>> ___
>> grass-dev mailing list
>> grass-...@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-dev
> ___
> grass-dev mailing list
> grass-...@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev

___
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

[Helena Mitasova]

On Jan 7, 2015, at 4:20 PM, Markus Neteler wrote:

> On Wed, Jan 7, 2015 at 9:26 AM, Massimiliano Cannata
>  wrote:
>> Dear all, I went trough the document and it make perfectly sense to me.
> 
> I agree. I updated its date now and expanded "RC" in the beginning.
> 
> http://trac.osgeo.org/grass/wiki/RFC/4_ReleaseProcedure
> 
> Last doubts:
> 
> * Step1:  "The Project manager (or if exists the Release manager)
> then collects reactions to decide whether there is sufficient support
> for this proposal. "
> 
> --> this "sufficient" is still a bit elastic. If one developer is
> against it, others in favour, it is fine to start? Leave it to
> democratical debates? Just to be sure.

I changed "to decide" to "and decides" so it is more clear that it is at the 
discretion of the Project/Release manager to decide whether there is sufficient 
support.
If Project manager cannot decide by himself (e.g. he/she is not sure), he/she 
can always call for a vote by PSC.
> 
>> Just a minor comment is that we shall probably clearly specify who is
>> responsible for the mentioned actions: call for soft, hard freeze etc.
> 
> That's the release manager. But I added that now (looks more dramatic
> than it is, trac doesn't highlight well this time).:
> 
> http://trac.osgeo.org/grass/wiki/RFC/4_ReleaseProcedure?action=diff&version=16&old_version=13
> 
> ... makes sense?

I made small language edits which did not change the meaning of the document 
and I agree with the document.

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

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

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

[Helena Mitasova]

I agree with the suggested modification by Moritz,

Helena

Helena Mitasova
Professor at the Department of Marine, 
Earth, and Atmospheric Sciences
and Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu
http://geospatial.ncsu.edu/osgeorel/
"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.” 

On Mar 3, 2015, at 3:31 AM, Moritz Lennert wrote:

> On 01/03/15 19:02, Markus Neteler wrote:
>> Hi,
>> 
>> On Tue, Feb 17, 2015 at 1:54 PM, Markus Neteler  wrote:
>>> On Fri, Jun 20, 2014 at 3:39 AM, Scott Mitchell  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

___
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

[Helena Mitasova]

+1 from me as well. Helena

> On Apr 8, 2015, at 6:03 AM, Massimiliano Cannata 
>  wrote:
> 
> +1
> Completely in favour of having the the string "GRASS GIS" in the logo.
> 
> Maxi
> 
> 2015-04-08 11:30 GMT+02:00 Markus Neteler :
> On Wed, Apr 8, 2015 at 11:05 AM, Moritz Lennert
>  wrote:
> > 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 ?
> 
> yes, and with all written in capital letters: GRASS GIS
> 
> >> Any objections?
> >
> > None.
> >
> >>
> >> Which font to use?
> >
> > I'll leave this to graphically more competent people.
> 
> Yes - however, it doesn't need to be overly fancy.
> 
> Markus
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc
> 
> 
> 
> -- 
> Massimiliano Cannata
> Professore SUPSI in ingegneria Geomatica
> Responsabile settore Geomatica
> 
> Istituto scienze della Terra
> Dipartimento ambiente costruzione e design
> Scuola universitaria professionale della Svizzera italiana
> Campus Trevano, CH - 6952 Canobbio
> 
> Tel. +41 (0)58 666 62 14
> Fax +41 (0)58 666 62 09
> massimiliano.cann...@supsi.ch
> www.supsi.ch/ist
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc

Helena Mitasova
Professor at the Department of Marine, 
Earth, and Atmospheric Sciences
and Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu
http://geospatial.ncsu.edu/osgeorel/
"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
http://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] OSGeo signing certificates

[Helena Mitasova]

This is just FYI, that board has just voted for OSGeo to obtain signing 
certificates for OSGeo projects -
see more details in the follwing threads below:

motion:
https://lists.osgeo.org/pipermail/board/2015-October/013364.html

discussion:
https://lists.osgeo.org/pipermail/board/2015-October/013321.html

It was requested by QGIS but it should help GRASS as well, 

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

Re: [GRASS-PSC] local community sprint funding

[Helena Mitasova]

I think that this is an excellent idea and we should definitely support it
if we have the funds,
+1 from me,

Helena


On Tue, Jan 19, 2016 at 1:10 PM, 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. Best regards, Martin
>
> [1]
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_contributors_meetings_in_Solany
> [2]
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_contributors_meetings_in_Solany/December_2015
> [3]
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_contributors_meetings_in_Solany/January_2016
> [4] https://lists.osgeo.org/pipermail/grass-dev/2016-January/078519.html
> [5]
> https://grasswiki.osgeo.org/wiki/Talk:GRASS_GIS_contributors_meetings_in_Solany/January_2016
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc




-- 
Helena Mitasova
Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
1125 Jordan Hall
NCSU Box 8208
Raleigh, NC 27695-8208
http://www4.ncsu.edu/~hmitaso/
http://geospatial.ncsu.edu/

email: hmit...@ncsu.edu
ph: 919-513-1327 (no voicemail)
fax 919 515-7802
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] local community sprint funding

[Helena Mitasova]

+1 Helena



On Tue, Feb 16, 2016 at 11:53 AM, Markus Neteler  wrote:

> On Mon, Feb 15, 2016 at 3:14 PM, Martin Landa 
> wrote:
> ...
> > 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
>
> Markus
>
> PS: Other PSC members, please vote.
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc




-- 
Helena Mitasova
Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
1125 Jordan Hall
NCSU Box 8208
Raleigh, NC 27695-8208
http://www4.ncsu.edu/~hmitaso/
http://geospatial.ncsu.edu/

email: hmit...@ncsu.edu
ph: 919-513-1327 (no voicemail)
fax 919 515-7802
___
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)

[Helena Mitasova]

I thought I already voted about this, but here is my +1 if not,
Helena

On Sat, Apr 2, 2016 at 1:47 PM, Martin Landa  wrote:

> Dear PSC,
>
> 2016-03-25 10:48 GMT+01:00 Massimiliano Cannata <
> massimiliano.cann...@supsi.ch>:
>
> thanks to all who votes! Unfortunately, till now only 4 people
> (including me). Please, could you express your opinion? -1 is better
> than silence. Thanks! Martin
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc




-- 
Helena Mitasova
Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
1125 Jordan Hall
NCSU Box 8208
Raleigh, NC 27695-8208
http://www4.ncsu.edu/~hmitaso/
http://geospatial.ncsu.edu/

email: hmit...@ncsu.edu
ph: 919-513-1327 (no voicemail)
fax 919 515-7802
___
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

[Helena Mitasova]

> On May 14, 2016, at 11:34 AM, Markus Neteler  wrote:
> 
> Dear PSC,
> 
> time has passed since the last elections in 2012. As the chair of the
> PSC I suggest that we renew part of the current PSC (see:
> https://trac.osgeo.org/grass/wiki/PSC#Members).
> I suggest the following tentative schedule:
> 
> - May 2016: preannounce elections (see this email) and
>  - identify members who do not stand for election
>  - identify inactive members (here the Geoserver PSC has some useful rules [1]

I find the Geoserver rules rather drastic - they are really important for 
governance model where 
PSC makes a lot of decisions about development which is not the case for GRASS
I assume that our inactive members won’t be interested in standing for election 
and
that way their membership will end.
As suggested, we should have 3 year term membership so everybody will have to be
re-elected at least once in 3 years.
I like the way how the board of directors is elected - it ensures both the 
continuity and rotation of members.

>  - assign free'd up slots to election
> 
> - May 2016: officially announce PSC elections
> 
> - 16 June 2016, 12:00 UTC: nominations possible by community
> 
> - June 2016: elections (here it would be great use the technology of
> the OSGeo charter member elections)

there will be new technology used this year - Vasile knows more about it.

>  Here we have the problem to not have a charter membership.

we can have a system where anybody can nominate a candidate and the 
contributors with 
svn access (both core and add-ons) vote - can you find out how many we have ?
This is just my suggestion to keep things simple - we can put this out for 
dicussion on the 
GRASS dev and users list.
> 
> - July 2016: PSC communicates the new members.
> 
> 
> IMPORTANT:
> We need to solve the following issues:
> - how to remove members from the PSC? (see [1] for inspiration)

see my comment above - I don’t think the Geoserver model is good for us
(I don’t like kicking people out of anything), I think members should go 
through re-election every 3 years
if we start with this elections, third of the current member slots should open 
up
and the current members affected should stand or not stand for re-election.
We can randomly  pick up the slots to be freed to start the cycle.

> - how to elect new members?

if we have enough developers with svn access (core and add-on) they could 
represent “charter members”
because they are considered trusted members of the community.
But it would be good to find a way how to include power users who do not have 
svn access.
In the document [2], I think the nomination should go also to GRASS dev list 
(in addition to PSC and users list).

These are just my thoughts, others may have better ideas,

Helena


> 
> Best,
> Markus
> 
> [1] 
> http://docs.geoserver.org/latest/en/developer/policies/psc.html#stepping-down
> [2] https://trac.osgeo.org/grass/wiki/PSC/Election2016 (draft)
> 
> --
> GRASS GIS PSC chair
> https://grass.osgeo.org
> _______
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc

Helena Mitasova
Professor at the Department of Marine, 
Earth, and Atmospheric Sciences
and 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
http://lists.osgeo.org/mailman/listinfo/grass-psc

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

[Helena Mitasova]

> On Jun 3, 2016, at 8:02 AM, Moritz Lennert  
> wrote:
> 
> On 03/06/16 12:36, Markus Neteler wrote:
>> On Fri, Jun 3, 2016 at 11:24 AM, Moritz Lennert
>>  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 ;-)

that is what I had in mind. OSGeo board elections work that way as well. 
> 
> 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

This looks good to me on the first reading - I suggest that we think this 
through for a day or two (think about what may not work
under this scenario to avoid unexpected consequences) and if it still looks 
good we should put it on a wiki to keep track
of the process and then it can be announced.
I suggest that anyone regardless of voting right can nominate and the current 
members can nominate themselves
just by saying that they are standing for re-election.

Helena
> 
> Moritz
> 

Helena Mitasova
Professor at the Department of Marine, 
Earth, and Atmospheric Sciences
and 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
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS-announce] PSC election 2016 Result

[Helena Mitasova]

I strongly support nomination of Markus as PSC chair.
Markus, I hope you will be willing to continue in this position,

Helena

> On Sep 5, 2016, at 12:23 PM, Michael Barton  wrote:
> 
> I nominate Markus
> 
> Michael Barton
> School of Human Evolution &Social Change
> Center for Social Dynamics & Complexity
> Arizona State University
> 
> ...Sent from my iPad
> 
>> On Sep 5, 2016, at 2:12 AM, Markus Neteler  wrote:
>> 
>> All,
>> 
>> On Thu, Sep 1, 2016 at 11:46 PM, Nikos Alexandris
>>  wrote:
>>> Dear all, this post concerns the election result for the new steering
>>> committee (no cross-posting to avoid useless mail trafic).
>>> 
>>> 
>>> The new Project Steering Committee is composed by the following nine members
>>> 
>>> 1  Markus Neteler62
>>> 2  Helena Mitasova   53
>>> 3  Martin Landa  52
>>> 4  Anna Petrasova45
>>> 5  Moritz Lennert41
>>> 6  Margherita Di Leo 39
>>> 7  Michael Barton35
>>> 8  Peter Löwe33
>>> 9  Vaclav Petras 31
>> ...
>> 
>> See also: 
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.osgeo.org_grass_wiki_PSC&d=CwIGaQ&c=AGbYxfJbXK67KfXyGqyv2Ejiz41FqQuZFk4A-1IxfAU&r=vxOW6PLS28MPea_dWUwPfRf71TAIziRDuFqWJimQN1I&m=1cqLg6dR_e7uTZefac7RIqbPI7Y6Qj6Df9jPCPMsXSo&s=3bE_iBe67bzNl8wk2C35-dVrl6KeIale3c48niPOw38&e=
>>  
>> 
>> The new PSC got announced recently, we should now go ahead and elect
>> the new PSC Chair.
>> Any opinions?
>> 
>> Then let's revisit our
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.osgeo.org_grass_wiki_PSC_Agenda&d=CwIGaQ&c=AGbYxfJbXK67KfXyGqyv2Ejiz41FqQuZFk4A-1IxfAU&r=vxOW6PLS28MPea_dWUwPfRf71TAIziRDuFqWJimQN1I&m=1cqLg6dR_e7uTZefac7RIqbPI7Y6Qj6Df9jPCPMsXSo&s=2o1CurDfzluwF-WHZkLonNV8qV3DmOkzMyPeQEXnxOY&e=
>>  
>> 
>> Best
>> Markus
>> ___
>> grass-psc mailing list
>> grass-psc@lists.osgeo.org
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.osgeo.org_mailman_listinfo_grass-2Dpsc&d=CwIGaQ&c=AGbYxfJbXK67KfXyGqyv2Ejiz41FqQuZFk4A-1IxfAU&r=vxOW6PLS28MPea_dWUwPfRf71TAIziRDuFqWJimQN1I&m=1cqLg6dR_e7uTZefac7RIqbPI7Y6Qj6Df9jPCPMsXSo&s=SQI_IZqMMmcirlpqRfSBG21oQUXTG4j6e6BZn_1TLFw&e=
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc

Helena Mitasova
Professor at the Department of Marine, 
Earth, and Atmospheric Sciences
and 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
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] MOTION: approve Markus as GRASS GIS PSC chair

[Helena Mitasova]

Dear members of PSC, I would like to make a motion to approve Markus Neteler as 
PSC chair.

Helena

P.S. Just to clarify the procedure - we need somebody to second this motion and 
then please all PSC members except Markus email your votes here.

> On Sep 18, 2016, at 2:00 PM, Vaclav Petras  wrote:
> 
> 
> On Sun, Sep 18, 2016 at 12:45 PM, Markus Neteler  wrote:
> >> 6 out of 9 PSC members nominated their candidate in 3 days. Since all
> >> nominated the same candidate, Markus (who accepts the nomination), I
> >> suggest to proceed with elections.
> >
> > +1
> 
> Since I can hardly organize it myself, I kindly invite someone to organize it.
> 
> 
> I don't know what was done in the past and I don't see anything at the wiki. 
> Based on the current situation described above, it seems to me that a public 
> vote is fine this time with absolute majority (>=5 members) needed to pass 
> the vote. I would leave anything more complicated for the next elections.
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc

Helena Mitasova
Professor at the Department of Marine, 
Earth, and Atmospheric Sciences
and 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
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] MOTION: approve Markus as GRASS GIS PSC chair

[Helena Mitasova]

+1 from me for Markus as PSC chair. Helena

We now have 7 votes +1, one vote missing and Markus does not vote,
so the Motion to approve Markus as GRASS GIS PSC chair was passed and Markus
is now officially the chair of PSC.

Thank you Markus for willing to continue keeping GRASS GIS thrive,

Helena

> On Sep 19, 2016, at 4:42 AM, Moritz Lennert  
> wrote:
> 
> On 18/09/16 22:04, Helena Mitasova wrote:
>> Dear members of PSC, I would like to make a motion to approve Markus Neteler 
>> as PSC chair.
>> 
>> Helena
> 
> As I sent my first response from the wrong address, here again:
> 
> +1
> 
> Moritz
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc

Helena Mitasova
Professor at the Department of Marine, 
Earth, and Atmospheric Sciences
and 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
http://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] budget request

[Helena Mitasova]

Dear PSC,

OSGeo board is working on a 2017 budget and we ask every committee and every 
project
to provide a budget request - in the past this was mostly for code sprints. 
There is no guarantie 
that the request will be fully funded (as OSGeo plans for a major, professional 
redesign of its website),
but it would be good to know what the project needs are and I am sure that at 
least some 
funding will be possible.

A simple request will be fine - e.g. 
$XXX for code sprint after FOSS4G Europe and $XXX for code sprint after FOSS4G 
Global in Boston.
$XXX to print GRASS GIS flyers for upcoming conferences 

We need this info this week - perhaps we can decide tomorrow (Thursday)?

This reminds me that we still do not have the working groups / PSC member 
responsibilities set up,
so please sign up here
https://trac.osgeo.org/grass/wiki/PSC/Roles 


We are in particular need for treasurer to handle this request.

Thank you, Helena

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

Re: [GRASS-PSC] [voting] Genova Community Sprint funding

[Helena Mitasova]

+1 from me as well,

Helena

> On Apr 9, 2017, at 7:19 AM, Markus Neteler  wrote:
> 
> PSC,
> 
> On Apr 9, 2017 12:35 PM, "Martin Landa"  wrote:
> > I took liberty to start voting thread related to Genova Community
> > Sprint funding, see [1,2] and original discussion [3].
> >
> > I will start with +0 since I am also asking for funding as one of 
> > participants.
> >
> > Thanks for your feedback, Ma
> 
> +1 to financially support the sprint as requested.
> 
> Markus
> 
> 
> > [1] 
> > https://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Sprint_Genova_2017#How_much_money_is_needed.3F
> > [2] 
> > https://docs.google.com/spreadsheets/d/18Jx74WEqsuydSErTvCOfa_nhze54RUzc2BH5I49Z4Vg/edit
> > [3] https://lists.osgeo.org/pipermail/grass-psc/2017-March/001650.html
> 
> _______
> 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
and 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] [voting] T-shirts funding

[Helena Mitasova]

>
>  Therefore we would like to
>> request $41.50 from GRASS budget [1], through PayPal on my account
>> (kratocha...@gmail.com). I can send the receipt if needed.
>>
>> I suppose we need to vote about this,
>
>
+1

Helena


>
>
> Helena Mitasova
Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
1125 Jordan Hall
NCSU Box 8208
Raleigh, NC 27695-8208
http://www4.ncsu.edu/~hmitaso/
http://geospatial.ncsu.edu/

email: hmit...@ncsu.edu
ph: 919-513-1327 (no voicemail)
fax 919 515-7802
___
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

[Helena Mitasova]

On Fri, Jun 16, 2017 at 1:27 PM, Anna Petrášová 
wrote:

>
>
> On Jun 16, 2017 7:20 AM, "Margherita Di Leo"  wrote:
>
>
> On Fri, 16 Jun 2017 at 11:28, Moritz Lennert 
> wrote:
>
>>
>>
>> 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
>
>
> +1
>
> madi
>
>
>
>
> +1
>
> Anna
>

+1

Helena

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



-- 
Helena Mitasova
Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
1125 Jordan Hall
NCSU Box 8208
Raleigh, NC 27695-8208
http://www4.ncsu.edu/~hmitaso/
http://geospatial.ncsu.edu/

email: hmit...@ncsu.edu
ph: 919-513-1327 (no voicemail)
fax 919 515-7802
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] printing flyers for foss4g-eu and other events

[Helena Mitasova]

Given that there is a new rebranding effort going on for OSGeo which
includes new logo but also new templates for flyers that can be used by
projects, initiatives, etc. I suggest to print a limited number of the
current flyers for now. I can find the links to the new layouts but those
of us who have seen it like it and its all green so it should fit GRASS GIS
well.  I assume that GRASS flyers should have osgeo logo on it and it would
be good to use the new one.

The new branding will be launched at FOSS4G Boston so unless you need
hundreds of flyers for events before that, 200 may be enough for now.

Helena

On Tue, Jun 27, 2017 at 8:50 PM, Veronica Andreo 
wrote:

> Hello PSC,
>
> Given that we have a very nice flyer created by Vincent and translated
> already to French, Italian and Spanish, I think it would be nice to have it
> printed so we can take to upcoming FOSS4Gs.
>
> In the beginning, I thought only of printing 200 of them (130 en, 30 fr,
> 20 es, 20 it or other combination) to take to European foss4g in Paris (in
> a printing shop here in NL they charge 64 euros), but talking to Luca, he
> suggested to print some more in an online shop (http://pixartprinting.it,
> eg: 1000 en + 225 in other languages = 225 euros). In proportion, this
> latter option is much cheaper and then we would have flyers to take to
> different events.
>
> What do you think?
>
> best,
> Vero
>
> ps: translations in more languages would be welcome, as well... say,
> German, for example :P
>
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
>



-- 
Helena Mitasova
Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
1125 Jordan Hall
NCSU Box 8208
Raleigh, NC 27695-8208
http://www4.ncsu.edu/~hmitaso/
http://geospatial.ncsu.edu/

email: hmit...@ncsu.edu
ph: 919-513-1327 (no voicemail)
fax 919 515-7802
___
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

[Helena Mitasova]

+1, Helena

On Sat, Jul 22, 2017 at 11:37 AM, Michael Barton 
wrote:

> +1
> 
> 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 <(480)%20965-6262> (SHESC), 480-965-8130
> <(480)%20965-8130>/727-9746 (CSDC)
> fax: 480-965-7671 <(480)%20965-7671> (SHESC),  480-727-0709
> <(480)%20727-0709> (CSDC)
> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Jul 22, 2017, at 9:44 AM, Vaclav Petras  wrote:
>
> +1 from Vaclav for stickers and flyers
>
> On Sat, Jul 22, 2017 at 11:14 AM, Markus Neteler 
> wrote:
>
>> 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.
>>
>> Markus
>>
>> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
> osgeo.org_mailman_listinfo_grass-2Dpsc&d=DwIGaQ&c=l45AxH-
> kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6n
> fT1XEEEtR0&m=r2mIZCf-sP69gLJNyjiZ8w8Jcnv0GLJMnTGQdr5SFC4&s=
> JDFFu9LnjlMGlSuzoa6ix74jLvbKOHXXWaIwZrmA59Y&e=
>
>
>
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
>



-- 
Helena Mitasova
Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
1125 Jordan Hall
NCSU Box 8208
Raleigh, NC 27695-8208
http://www4.ncsu.edu/~hmitaso/
http://geospatial.ncsu.edu/

email: hmit...@ncsu.edu
ph: 919-513-1327 (no voicemail)
fax 919 515-7802
___
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

[Helena Mitasova]

+1 

(I just got my new GRASS GIS T-shirt - Thank you Anna and Vasek for putting 
effort into this)

Helena

 
> On Aug 4, 2017, at 6:54 AM, Markus Neteler  wrote:
> 
> Re: this motion:
> 
> yet missing Helena and Michael - please vote.
> 
> thanks,
> Markus

Helena Mitasova
Professor at the Department of Marine, 
Earth, and Atmospheric Sciences
and Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu
http://geospatial.ncsu.edu/osgeorel/publications.html 
<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] [Motion] Proposing Stefan Blumentrath as a new core developer

[Helena Mitasova]

+1

Helena

Helena Mitasova
Professor, Department of Marine, Earth and Atmospheric Sciences
Faculty Fellow, Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
http://www4.ncsu.edu/~hmitaso/
http://geospatial.ncsu.edu/osgeorel/publications.html

email: hmit...@ncsu.edu
ph: 919-513-1327 (no voicemail)
fax 919 515-7802

On Tue, Jan 30, 2018 at 5:02 PM, 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] [Motion] Print 500 GRASS GIS stickers for the upcoming conferences

[Helena Mitasova]

+1

Helena

> On Feb 27, 2018, at 5:38 PM, 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
> 
> I start with a +1.
> 
> Markus
> ___
> 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 
<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] [motion] Bonn Community Sprint funding

[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 
<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] Enabling FAIR Data project commitment statement: Feedback, please.

[Helena Mitasova]

Peter,

I think that GRASS support for this initiative is covered by the OSGeo 
foundation as organization which has agreed to sign it. I am not sure we need a 
separate signature from each project, but that is just my opinion, let us see 
what Enabling FAIR Project says about it,

Helena


> On Sep 24, 2018, at 8:29 AM, Peter Löwe  wrote:
> 
> Hi Moritz, PSC,
> 
> that's a good point. I will ask the ENabling FAIR Project and will report 
> back.
> 
> best,
> Peter
> 
> 
> 
> 
>> Gesendet: Montag, 24. September 2018 um 14:08 Uhr
>> Von: "Moritz Lennert" 
>> An: grass-psc@lists.osgeo.org
>> Betreff: Re: [GRASS-PSC] Enabling FAIR Data project commitment statement: 
>> Feedback, please.
>> 
>> 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
> ___
> 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] GRASS GIS Budget 2019 - draft

[Helena Mitasova]

The request for project budget from the board will be sent out to the projects 
within a day or two, 
so let us wait and then we can submit our request. The wiki is ready

https://wiki.osgeo.org/wiki/OSGeo_Budget_2019

there are just few things discussed regarding the wording of the request from 
the board.
In terms of the request for the website update - that will indeed go quite 
above what the projects usually ask for
so it will have a better chance to be approved if we include some fundraising 
effort looking for sponsors
on our side.

Helena



> On Jan 6, 2019, at 6:19 AM, 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!
> 
>> [...]
> ...
>> When can we submit/apply for the 2019 budget then?? I really wish to see a 
>> new GRASS website this year! :)
> 
> I think we can apply any time by proposing a structured budget.
> 
> Markus
> ___
> 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

"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] GRASS GIS Budget 2019 - draft

[Helena Mitasova]

Please, prepare the budget for as much as we really need ($9000) with solid 
explanation and a committment to do fundraising for the website. 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.

Helena


> On Jan 17, 2019, at 5:44 AM, Veronica Andreo  wrote:
> 
> Hi :)
> 
> El jue., 17 ene. 2019 7:25, Martin Landa  escribió:
> Hi,
> 
> čt 17. 1. 2019 v 10:51 odesílatel Moritz Lennert
>  napsal:
> 
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2019#Planned_Expenses
> 
> two notes:
> 
> 1) GRASS GIS Community Sprint FOSS4G Bucarest 2019 (extension of the
> OSGeo Code Sprint)
> 
> This year OSGeo Code Sprint is located in U.S. I would remove text in 
> brackets.
> 
> 2) Would be nice to plan our own Code Sprint in Spring/Autumn. Berlin
> has been discussed several times as good place.
> 
> > That would mean we should ask for about 7000€ from OSGeo. If they give
> > us less, then we will have to raise more... ;-)
> 
> 7e3 seems to be reasonable (since we want to redo website). I would
> even ask for more, we don't have so strong donation program as QGIS
> has.
> 
> I would also ask more, i.e., at least 8000 euro. 
> 
> IIUC, QGIS is asking a total of 11000 euro, including their developers and 
> users conf... So, why not? Whatever extra we might get from donations can be 
> used for financing code sprints, travels or support bug fixing or development 
> of new features
> 
> Cheers,
> Vero
> ___
> 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

"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] [Board] quick project status check and response to budget inquiry

[Helena Mitasova]

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,

Helena



> On Jan 19, 2019, at 5:31 PM, Jody Garnett  wrote:
> 
> Going to share this here as one of our responsibility is to check-in with 
> projects.
> 
> Here are notes from todo activity contacting projects 
> 
>   • deegree: active codebase, no response
>   • FDO: active codebase, PSC inactive (consider as community project?)
>   • GDAL/OGR: responded
>   • geomajas: last activity august 2018
>   • GeoMOOSE: very active, no response
>   • GeoNetwork: very active, no response
>   • GeoNode: active, no response
>   • GEOS: active, no response
>   • GeoServer: responded
>   • GeoTools: responded
>   • GRASS: activer, no response
>   • gvSIG: actually responded with a budget!
>   • Mapbender: active codebase, no response
>   • MapFish: website and latest release from 2011, consider as community 
> project?)
>   • MapGuide Open Source: PSC inactive, consider as community project?
>   • MapServer: active codebase, no response
>   • Marble: active codebase, no response
>   • OpenLayers: active codebase, no response
>   • OSSIM: active codebase, no budget response
>   • PostGIS: activer codebase, no response
>   • pycsw: active codebase, no response
>   • QGIS: responded
>   • OSGeoLive: last commit in September, discussion on mailing list but 
> no response yet 
> 
> Unless anyone has any objects I would like to discuss treating FDO, MapFish, 
> MapGuide Open Source as community projects for the 2019 budget. This allows 
> the us to fund projects like MapGuide Open Source while acknowledging that 
> they no meet as a committee. Should any of these projects step up in activity 
> it should be easy for them to go through incubation as their procedures are 
> already in place.
> 
> We may also wish to speak with the QGIS PSC about QGIS Server being listed as 
> a community project. This would allow us a way to thread the needle between 
> QGIS being graduated and the QGIS team adding and additional project which is 
> not yet part of OSGeo.
> --
> Jody Garnett
> _______
> Board mailing list
> bo...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/board

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

"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] [MOTION] Write access to the GRASS-SVN repository Ondřej Pešek

[Helena Mitasova]

+1 Helena
> On Jan 19, 2019, at 6:44 PM, Markus Neteler  wrote:
> 
> 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

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

"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

[GRASS-PSC] Fwd: contribution to GRASS project

[Helena Mitasova]

Please see below - would it be possible to add Robert Szczepanek as 
contributor? I am not sure whether he has svn access, but at least as Other 
would be appropriate.

Thank you, Helena


> Begin forwarded message:
> 
> From: robert 
> Subject: contribution to GRASS project
> Date: March 31, 2019 at 7:23:41 PM EDT
> To: hmit...@unity.ncsu.edu
> 
> Dear Helena,
> 
> Almost all icons presented on this page 
> (https://grass.osgeo.org/screenshots/user-interface/) have been created by me 
> for GRASS and QGIS projects.
> 
> Can it be treated as contribution to GRASS project?
> https://grass.osgeo.org/home/credits/
> 
> best regards,
> Robert Szczepanek

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

"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] stickers for FOSS4G in Bucharest

[Helena Mitasova]

+1 assuming we have it in the budget, 

Helena


> On Jun 25, 2019, at 2:16 PM, Moritz Lennert  
> wrote:
> 
> +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 
> <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

Helena Mitasova
Professor, Department of Marine, Earth and Atmospheric Sciences
Faculty Fellow,
Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu



___
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

[Helena Mitasova]

+1

Helena

> On Jan 7, 2020, at 9:14 AM, Moritz Lennert  
> wrote:
> 
> 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

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

"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] [Motion] First payment for new GRASS GIS Hugo based web site

[Helena Mitasova]

+1 

Helena

> On Feb 17, 2020, at 7:58 AM, 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.
> 
> Best,
> Markus
> 
> PS: once the web site is sufficiently (!) completed we'll switch the
> DNS entries:
>  https://grass.osgeo.org/ --> https://old.grass.osgeo.org/ , and
>  https://staging.grass.osgeo.org/ --> https://grass.osgeo.org/
> ___
> 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

"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

[GRASS-PSC] GRASS code spring slide for OSGeo AGM

[Helena Mitasova]

Hi, we are going through the slides for 2020 OSGeo AGM (scheduled for tomorrow 
https://wiki.osgeo.org/wiki/Annual_General_Meeting_2020 
<https://wiki.osgeo.org/wiki/Annual_General_Meeting_2020>

and there is no text for the code spring - Vashek (or somebody else) can you 
please add some info if there was a code spring
(we had some meetings but I am not sure about the code sprint)?
https://docs.google.com/presentation/d/1C6llSnWZ28c2aWQgttPiOnoo6dttdqKg07ugU_yr6Uc/edit#slide=id.g33e7b00af0_3_73
 
<https://docs.google.com/presentation/d/1C6llSnWZ28c2aWQgttPiOnoo6dttdqKg07ugU_yr6Uc/edit#slide=id.g33e7b00af0_3_73>
Also we need somebody to present the slide (1 minute or so).

Thank you, Helena



> On Sep 3, 2020, at 5:23 PM, Veronica Andreo  wrote:
> 
> Hi, 
> 
> I just added some content to it as items. Other ideas?
> 
> best, 
> Vero
> 
> El jue., 3 sept. 2020 a las 20:56, Markus Neteler () 
> escribió:
>  Hi,
> (sorry for cross-posting)
> 
> The OSGeo Annual General Meeting (AGM) will take place on 10th Sep
> 2020 from 6 pm to 8pm UTC
> (https://www.timeanddate.com/worldclock/fixedtime.html?msg=OSGeo+AGM&iso=20200910T18&p1=1440&ah=2)
> as a virtual meeting.
> 
> AGM 2020 announcement:
> - https://lists.osgeo.org/pipermail/discuss/2020-August/039019.html
> 
> AGM 2020 Wiki page:
> - https://wiki.osgeo.org/wiki/Annual_General_Meeting_2020
> 
> 
> We are, like all OSGeo projects, requested to provide one slide with
> the development and community news of the last year.
> Our draft slide is at p. 40:
> 
> https://docs.google.com/presentation/d/1C6llSnWZ28c2aWQgttPiOnoo6dttdqKg07ugU_yr6Uc/edit#slide=id.g233aae6a05_0_0
> 
> Please contribute to the content!
> 
> Markus
> 
> PS: content suggestions from the board list:
> 
> - key accomplishments
> - releases
> - infrastructure or process changes
> - community health and happiness
> - areas for improvements
> - these are challenges faced by the project
> - opportunities to help
> - anything for members to help with?
> - requests and communication
> - any formal request from the board, marketing or other committees?
> - did you make a budget request for 2020? How did it go ...
> - external correspondence? letter of recommendation for a GSOC
> student? code donation? etc…
> - outlook for 2020
> - any roadmap items to share with our members?
> - let the board know if there is anything to plan for in 2020
> ___
> grass-dev mailing list
> grass-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
> ___
> grass-dev mailing list
> grass-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev

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

"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] GRASS code spring slide for OSGeo AGM

[Helena Mitasova]

I can present it, if nobody else would like to. 

Helena

> On Sep 9, 2020, at 5:03 PM, Markus Neteler  wrote:
> 
> Hi PSC, devs,
> 
> On Wed, Sep 9, 2020 at 6:42 PM Helena Mitasova  wrote:
>> 
>> Hi, we are going through the slides for 2020 OSGeo AGM (scheduled for 
>> tomorrow
>> https://wiki.osgeo.org/wiki/Annual_General_Meeting_2020
> 
> btw: who is willing to present our project slide?
> 
> It is tomorrow at 13:00UTC:
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=OSGeo+AGM&iso=20200910T13&p1=1440&ah=2
> 
> best
> Markus
> 
> ...
>> We are, like all OSGeo projects, requested to provide one slide
> ...
>> https://docs.google.com/presentation/d/1C6llSnWZ28c2aWQgttPiOnoo6dttdqKg07ugU_yr6Uc/edit#slide=id.g233aae6a05_0_0

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

"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] [Motion] Second payment for new GRASS GIS Hugo based web site

[Helena Mitasova]

+1 Helena

> On Sep 27, 2020, at 3:03 PM, Markus Neteler  wrote:
> 
> Dear PSC,
> 
> The new, shiny GRASS GIS website is up and running for some time at
> https://grass.osgeo.org/ with its code base available at
> https://github.com/OSGeo/grass-website .
> 
> In the last weeks, the main developer, Nicolas Bozon
> (https://github.com/nbozon) has done further developments, esp. fixes.
> 
> This motion is to vote on the second (and last) payment of 2000 USD
> (out of the budgeted 6000 USD [1]) to Nicolas Bozon.
> The money transfer can then be directly done from OSGeo to the
> developer (already clarified with the OSGeo treasurer).
> 
> Motion:
> I hereby start with a +1.
> 
> Best,
> Markus
> 
> [1] https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc

Helena Mitasova
Professor, Department of Marine, Earth and Atmospheric Sciences
Faculty Fellow,
Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu



___
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

[Helena Mitasova]

+1 from me too. 

Thank you Tomas for all your work, Helena

> On Nov 21, 2020, at 9:16 PM, Anna Petrášová  wrote:
> 
> Definitely +1 
> 
> I would suggest with any new core devs we should have a policy that all their 
> PRs go through at least 1 review for some time. This policy would be nice for 
> all PRs (even from current devs), because it significantly improves the code, 
> but of course it's not always possible or practical given the workload.
> 
> Anna
> 
> On Fri, Nov 20, 2020 at 5:17 PM Markus Neteler  <mailto:nete...@osgeo.org>> wrote:
> Dear PSC,
> 
> Let me propose Tomáš Zigo (https://github.com/tmszi 
> <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 
> <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
>  
> <https://github.com/OSGeo/grass-addons/pulls?q=is%3Apr+is%3Aclosed+author%3Atmszi>
> [3] 
> https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines 
> <https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines>
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org <mailto:grass-psc@lists.osgeo.org>
> https://lists.osgeo.org/mailman/listinfo/grass-psc 
> <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

Helena Mitasova
Professor, Department of Marine, Earth and Atmospheric Sciences
Faculty Fellow,
Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu



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

Re: [GRASS-PSC] PSC elections in 2020

[Helena Mitasova]

Moritz, 

the proposed email looks good. Preferably CRO should not be a PSC member (but 
could be a former member)
I wish the process was much simpler, but I don’t have any good ideas about how 
to simplify it,

Helena
  
> On Dec 8, 2020, at 9:03 AM, Moritz Lennert  
> wrote:
> 
> 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 
> <https://trac.osgeo.org/grass/wiki/PSC>
> 
> [2] https://lists.osgeo.org/pipermail/grass-psc/ 
> <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

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

"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] Proposing Nicklas Larsson as a new core developer

[Helena Mitasova]

+1

Helena

> On Dec 16, 2020, at 9:37 AM, Anna Petrášová  wrote:
> 
> +1 
> Nicklas has been incredibly helpful in making GRASS more robustly working on 
> Mac solving various issues including GUI bugs, GUI design issues and 
> compilation problems.
> 
> Best,
> Anna
> 
> On Wed, Dec 16, 2020 at 9:19 AM Markus Neteler  wrote:
> 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

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

"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] [GRASS GIS Elections 2020] Current members of the PSC willing to stand up for reelection?

[Helena Mitasova]

I agree with #2 - the current PSC members should be nominated for re-election 
by member(s) of the community- this is consistent with the OSGeo election 
procedure. 

We should also make sure that the nominee agrees to be nominated, 

Helena

> On Dec 22, 2020, at 8:48 AM, 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"
> 
> ?
> 
> Markus
> ___
> 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

"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

[GRASS-PSC] Statement Helena Mitasova

[Helena Mitasova]

 Dear GRASS community,

I am  honored to be nominated - thank you.  

As most of you probably know I am faculty at the Center for Geospatial 
Analytics at North Carolina State University. 
I have participated in GRASS GIS development since 1991, working at USA CERL in 
90s and I have been on GRASS PSC
since it was established. I have collaborated with Markus on the GRASSbook and 
co-authored many papers and two
additional books with GRASS-related topics. I have promoted GRASS in academic 
communities and at conferences through
presentations of our research developing innovative tools and applications. 
  

I am currently on the board of directors for OSGeo and as GRASS PSC member I 
try to make sure that the views and needs
from GRASS project are well represented. I am rather quiet on the lists as I 
try to minimize sending emails, writing only when I feel
that it is absolutely necessary. But I closely follow GRASS development and 
follow up with any  issues that arise with Anna and Vasek.
I developed and teach courses where we use GRASS and my current and former 
graduate students use GRASS in their research.
I was fortunate to have Anna and Vasek as my grad students  bringing GRASS 
development into our lab at NCSU.

As a PSC member I see my role as guarding the continuity while supporting new 
ideas -I am excited about the new developments 
which may change how people use GRASS and make it more accessible. I am 
committed to working with GRASS community to further develop open access 
educational material  for courses and workshops.
I would also strive to keep the admin and procedures as simple as possible to 
focus the resources (time and effort)
on development, documentation and education, while dividing the work as 
suggested by Markus - perhaps bringing 
in some experience from currently well functioning OSGeo board.

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

Re: [GRASS-PSC] Fwd: Re: [OSGeo-Discuss] OSGeo Budget 2021

[Helena Mitasova]

I think Angelos misinterpreted what was in the GRASS wiki budget - it was a 
little bit confusing, but we did not go into details 
for each project so I did not get a chance to explain. I can fix it. 

Helena

> On Jan 23, 2021, at 7:13 AM, Moritz Lennert  
> wrote:
> 
> Hi !
> 
> IIUC, this indicates that we request 5,419$. Any idea why ? Our official 
> request was 2500$.
> 
> Moritz
> 
> 
>  Ursprüngliche Nachricht 
> Von: Angelos Tzotsos 
> Gesendet: 23. Januar 2021 11:41:26 MEZ
> An: OSGeo Board 
> CC: "proje...@lists.osgeo.org" , OSGeo Discussions 
> 
> Betreff: Re: [OSGeo-Discuss] OSGeo Budget 2021
> 
> Hi all,
> 
> Here is the first draft of the 2021 Budget based on the last meeting 
> discussion.
> 
> https://wiki.osgeo.org/wiki/OSGeo_Budget_2021
> 
> We need to cover some more areas in our next meeting this Monday:
> * Local Chapters
> * Code Sprints
> * Travel Grants
> 
> Regards,
> Angelos
> 
> On 12/29/20 11:35 AM, Angelos Tzotsos wrote:
>> Dear OSGeo project members and committees,
>> 
>> Over the previous years, OSGeo has been proud to support a growing 
>> number of project events, such as community/code sprints, developer 
>> meetings, and user conferences. As a result of the COVID-19 pandemic, 
>> most OSGeo events in 2020 were held as virtual events.
>> 
>> OSGeo is reaching out to all committees, including Project Steering 
>> Committees, to help plan our budget for 2021.
>> 
>> In 2020, the Board assigned an initial amount of 2000 USD to all 
>> graduated projects who have reported to the Board the last 12 months 
>> (e.g. during the AGM or directly to a Board meeting). This year the 
>> Board is planning to continue to offer a budget to all graduated 
>> projects with the exact amount to be determined.
>> 
>> Due to cancellation of events in 2020, we are not in a position to 
>> allocate and spend as much as we did in previous years.
>> 
>> To help navigate the uncertainties ahead in 2021, the Board is 
>> planning to have a budget meeting on 18 January 2021 to review 2020 
>> expenditures, sponsorship, and make financial decisions for the 2021 
>> budget.
>> 
>> Please send your detailed requests for approval (see detailed budget 
>> requests from 2020 e.g. 
>> https://wiki.osgeo.org/wiki/GeoServer_Budget_2020 
>> <https://wiki.osgeo.org/wiki/GeoServer_Budget_2020>)
>> 
>> We would like to ask you to help us with budget proposals to assist 
>> your project. This will help us set aside a realistic amount of funding.
>> 
>> Please add your project info to the budget draft at:
>> 
>> https://wiki.osgeo.org/wiki/OSGeo_Budget_2021 
>> <https://wiki.osgeo.org/wiki/OSGeo_Budget_2021>
>> 
>> ideally by 17 January 2021 in advance of our next Board meeting.
>> 
>> When making a budget request please keep in mind the vision and goals 
>> of our Foundation, along with any obligations you wish to meet.
>> 
>> Thank you.
>> 
>> On behalf of the OSGeo Board,
>> 
>> Angelos
>> 
>> 
> 
> 
> -- 
> Angelos Tzotsos, PhD
> President
> Open Source Geospatial Foundation
> http://users.ntua.gr/tzotsos
> 
> ___
> Discuss mailing list
> disc...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/discuss
> ___
> 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

"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: Re: [OSGeo-Discuss] OSGeo Budget 2021

[Helena Mitasova]

As I emailed my response and went into the document to change it I realized 
that carry-over from last year is not allowed 
in OSGeo budget, so unless we have the surplus $2,311 in the bank from some 
other source we cannot go to OSGeo
and ask for carry-over $2,311 and new $2500. I think Angelos got the Total 
number from the detailed budget document.

But this discussion is not really relevant because OSGeo allocated $2000 to all 
projects which provided request,
so pretty close to what we had. There is no money from 2020 global conference 
so the fund are quite limited although
a lot was saved on travel.

I hope this explains it, Helena


> On Jan 23, 2021, at 7:13 AM, Moritz Lennert  
> wrote:
> 
> Hi !
> 
> IIUC, this indicates that we request 5,419$. Any idea why ? Our official 
> request was 2500$.
> 
> Moritz
> 
> 
>  Ursprüngliche Nachricht 
> Von: Angelos Tzotsos 
> Gesendet: 23. Januar 2021 11:41:26 MEZ
> An: OSGeo Board 
> CC: "proje...@lists.osgeo.org" , OSGeo Discussions 
> 
> Betreff: Re: [OSGeo-Discuss] OSGeo Budget 2021
> 
> Hi all,
> 
> Here is the first draft of the 2021 Budget based on the last meeting 
> discussion.
> 
> https://wiki.osgeo.org/wiki/OSGeo_Budget_2021
> 
> We need to cover some more areas in our next meeting this Monday:
> * Local Chapters
> * Code Sprints
> * Travel Grants
> 
> Regards,
> Angelos
> 
> On 12/29/20 11:35 AM, Angelos Tzotsos wrote:
>> Dear OSGeo project members and committees,
>> 
>> Over the previous years, OSGeo has been proud to support a growing 
>> number of project events, such as community/code sprints, developer 
>> meetings, and user conferences. As a result of the COVID-19 pandemic, 
>> most OSGeo events in 2020 were held as virtual events.
>> 
>> OSGeo is reaching out to all committees, including Project Steering 
>> Committees, to help plan our budget for 2021.
>> 
>> In 2020, the Board assigned an initial amount of 2000 USD to all 
>> graduated projects who have reported to the Board the last 12 months 
>> (e.g. during the AGM or directly to a Board meeting). This year the 
>> Board is planning to continue to offer a budget to all graduated 
>> projects with the exact amount to be determined.
>> 
>> Due to cancellation of events in 2020, we are not in a position to 
>> allocate and spend as much as we did in previous years.
>> 
>> To help navigate the uncertainties ahead in 2021, the Board is 
>> planning to have a budget meeting on 18 January 2021 to review 2020 
>> expenditures, sponsorship, and make financial decisions for the 2021 
>> budget.
>> 
>> Please send your detailed requests for approval (see detailed budget 
>> requests from 2020 e.g. 
>> https://wiki.osgeo.org/wiki/GeoServer_Budget_2020 
>> <https://wiki.osgeo.org/wiki/GeoServer_Budget_2020>)
>> 
>> We would like to ask you to help us with budget proposals to assist 
>> your project. This will help us set aside a realistic amount of funding.
>> 
>> Please add your project info to the budget draft at:
>> 
>> https://wiki.osgeo.org/wiki/OSGeo_Budget_2021 
>> <https://wiki.osgeo.org/wiki/OSGeo_Budget_2021>
>> 
>> ideally by 17 January 2021 in advance of our next Board meeting.
>> 
>> When making a budget request please keep in mind the vision and goals 
>> of our Foundation, along with any obligations you wish to meet.
>> 
>> Thank you.
>> 
>> On behalf of the OSGeo Board,
>> 
>> Angelos
>> 
>> 
> 
> 
> -- 
> Angelos Tzotsos, PhD
> President
> Open Source Geospatial Foundation
> http://users.ntua.gr/tzotsos
> 
> ___
> Discuss mailing list
> disc...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/discuss
> ___
> 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

"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] First meeting of the new PSC

[Helena Mitasova]

I can cut my previous meeting short and be there at 9am (3pm EST), so no need 
for another doodle, Helena

> On Jan 29, 2021, at 9:59 AM, Veronica Andreo  wrote:
> 
> Hello everybody, 
> 
> Thanks for voting, I just realized I had not yet done so ;-D Done now!
> 
> Seems the best time slot is on Wednesday 3rd at 9 pm CET 
> (https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&month=2&day=3&hour=20&min=0&sec=0&p1=207&p2=51&p3=48&p4=25&p5=197),
>  but Helena wouldn't be there. 
> 
> Since this would be the constitting meeting of the new PSC and we should vote 
> for the chairperson, I think we should all be present. Hence, shall we search 
> for a different date, i.e., a new doodle for the other week? Or is there any 
> chance you could rethink and edit the entries for next week so we don't delay 
> it much?  
> 
> Let me know what you think or what would work best for you
> 
> Cheers, 
> Vero
> 
> El jue, 28 ene 2021 a las 12:20, Chief Return Officer (CRO) - GRASS GIS 
> election 2020 () escribió:
> 
> On 2021-01-27 21:21, Moritz Lennert wrote:
> > Hi Vero,
> >
> > Thanks for taking the initiative !
> >
> > Here are already some points we might want to discuss:
> >
> > - Debrief of the elections: during the process, several questions arose
> > and we should probably profit of the opportunity to clarify the procedure
> > and rules, ideally putting it into an RFC. @Hernan it would be very 
> > helpful
> > if you could briefly summarize your experience and give your opinion 
> > on what could be done now to make things even better.
> 
> I am sending an email to the PSC list later today with this.
> 
> /H.
> 
> 
> ___
> 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

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

"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] [GRASS-user] Support GRASS GIS financially !

[Helena Mitasova]

Hi Venka,

it is really nice to hear from you. I just checked the OSGeo github sponsor 
options and it includes also a credit card:

https://github.com/sponsors/OSGeo

Perhaps we can do the Sponsor option for GRASS the same way - I can ask Astrid 
how she set it up is it is not clear.
OSGeo board subgroup just had a meeting about expanding sponsroship 
opportunities and sponsorship recognition,
so there may be more options coming.

Helena


> On Feb 6, 2021, at 6:09 AM, Moritz Lennert  
> wrote:
> 
> Thanks for the info, Venka. We're looking into other options. Markus found 
> this, which looks promising: 
> 
> https://opencollective.com/
> 
> Moritz
> 
> Am 6. Februar 2021 04:16:27 MEZ schrieb VENKATESH RAGHAVAN 
> :
>> Hi Moritz,
>> 
>> I do not know why the PayPal lists only
>> countries of residence in the EU and Americas.
>> 
>> Perhaps since the PayPal account is linked
>> to the Belgian Bank.
>> 
>> Bank transfer rates are high, so bank is
>> not a good option, I think.
>> 
>> You could consider accepting Gift Vouchers (Amazon etc.)
>> maybe.
>> 
>> Best
>> 
>> Venka
>> 
>> On 2/5/2021 10:48 PM, Moritz Lennert wrote:
>>> Hi Venka,
>>> 
>>> [Putting the PSC in CC as this is an important question.]
>>> 
>>> We have a bank account (in €) in a Belgian bank. So bank transfer is 
>>> another option, but I'm not sure how feasible this is from Asia.
>>> 
>>> This might be something to raise with OSGeo: creating a worldwide system 
>>> for collecting sponsorship money that sponsors can dedicate to specific 
>>> projects. Not sure that the relatively small amounts we collect for GRASS 
>>> GIS warrant the establishment of such a system only for us.
>>> 
>>> Best wishes,
>>> Moritz
>>> 
>>> Am 5. Februar 2021 14:11:04 MEZ schrieb Venkatesh Raghavan 
>>> :
>>>> Hi Moritz Lennert,
>>>> 
>>>> Thanks for all the great work by the GRASS Team!!
>>>> 
>>>> Is there any other way to sponsor apart from using
>>>> PayPal?
>>>> 
>>>> Choosing "Pay as Guest" and "Pay by debit card"
>>>> does not list any country in Asia (or any country
>>>> in the southern hemisphere) under "Country or region of residence".
>>>> 
>>>> Best
>>>> 
>>>> Venka
>>>> 
>>>> 
>>>> On 2/5/2021 9:38 PM, Moritz Lennert wrote:
>>>>> Dear all,
>>>>> 
>>>>> We just received our very first sponsorship contribution of 2021 (thank
>>>>> you !) and we want to take this occasion to thank all those who sponsored 
>>>>> us last year and remind you that the GRASS
>>>>> GIS project needs financial support in order to:
>>>>> 
>>>>> - organize very valuable face-to-face meetings and sprints gathering
>>>>> developers and the wider community for a few days to concentrate on
>>>>> improving GRASS GIS
>>>>> 
>>>>> - fund specific fixes or enhancements (this year the use of
>>>>> micro-budgets for such fixes is planned)
>>>>> 
>>>>> - maintain our website
>>>>> 
>>>>> - produce marketing material to spread the word
>>>>> 
>>>>> You can see the list of past individual and corporate sponsors here:
>>>>> 
>>>>> https://grasswiki.osgeo.org/wiki/Sponsors
>>>>> 
>>>>> As you can see, no amount is too small: if all GRASS GIS users give just
>>>>> a small amount regularly, we will already have a sizeable budget to work
>>>>> with ! And I challenge you to find software that does all that GRASS GIS
>>>>> does for 5€/$ or 10 €/$ a year ;-)
>>>>> 
>>>>> So, just go to https://grass.osgeo.org/contribute/sponsoring/ and help
>>>>> us make GRASS GIS better.
>>>>> 
>>>>> If you want to see more details about how we use the money, note that
>>>>> the project budgets are public. For 2021 see
>>>>> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2021.
>>>>> 
>>>>> The GRASS GIS Project Steering Committee
>>>>> ___
>>>>> grass-user mailing list
>>>>> grass-u...@lists.osgeo.org
>>>>> https://lists.osgeo.org/mailman/listinfo/grass-user
>>>>> 
>>>> 
>> 
> ___
> 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

"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] Accounting and organization of sponsorship

[Helena Mitasova]

ps, including a series of different options and advantages 
>> (ex: receipts) for sponsors. How we organize this exactly (via fiscal 
>> host) is still to be determined (maybe OSGeo can become a fiscal host 
>> for all OSGeo projects ?).
>> 
>> - https://github.com/sponsors/OSGeo for recurring sponsorship.
>> 
>> - Our bank account for direct money transfer, mostly within Europe.
>> 
>> 
>> Does this sound reasonable for everyone ? If yes, I will look into the 
>> details of Open Collective and create our system.
>> 
>> Moritz
>> 
>> 
>> ___
>> 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://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!JYQHuCCW-r_wk5ZkIBeP49QU77SHS7hiB50Ncbo81102GGGA-Ce_UmCsrjjKdZlGnTm0oAE$
>>  
> 
> ___
> 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

"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] Accounting and organization of sponsorship

[Helena Mitasova]

Moritz - no need to mail the board, but please do send an email if you would 
like to offer a concise explanation 
of why GRASS PSC would like to have this set up with OSGeo as fiscal host - I 
can explain it, but a written note may be helpful.
You are also welcome to join the meeting - here is the time and jitsi link:

https://wiki.osgeo.org/wiki/Board_Meeting_2021-03-29

Thank you, Helena



> On Mar 17, 2021, at 6:33 PM, Moritz Lennert  wrote:
> 
> Thanks Helena !
> 
> So no need for a mail to the board on my side, then ?
> 
> Moritz
> 
> Am 17. März 2021 14:40:16 MEZ schrieb Helena Mitasova :
>> I put it up on the upcoming OSGeo board agenda - there has a been a new 
>> initiative setting up sponsorship infrastructure so it is a good timing,
>> 
>> Helena
>> 
>>> On Mar 17, 2021, at 8:24 AM, Veronica Andreo  wrote:
>>> 
>>> Thanks for looking at all this, Moritz, and for the explanation, of course 
>>> :)
>>> Asking OSGeo to be fiscal host then seems the way to go
>>> 
>>> Vero
>>> 
>>> El mié, 17 mar 2021 a las 8:40, Moritz Lennert 
>>> () escribió:
>>> Most foss4g projects are not legal entities, just a bunch of nice people 
>>> organizing to create beautiful software. As they are not legal entities 
>>> they cannot open a bank account, provide invoices, etc. This is what 
>>> fiscal 
>>> hosts are for. They are legal entities that allow groups to act like a 
>>> legal entity by allowing them to open accounts, etc. For more info: 
>>> https://opencollective.com/become-a-host. 
>>> <https://opencollective.com/become-a-host.> 
>>> 
>>> OSGeo is already playing the role of fiscal host for GitHub sponsoring: 
>>> https://github.com/sponsors/OSGeo. <https://github.com/sponsors/OSGeo.>
>>> 
>>> For our current banking account our fiscal host is OSGeo.eu.
>>> 
>>> OSGeo could become a fiscal host at opencollective and so allow all OSGeo 
>>> projects to organize sponsoring through there. I'll ask the board.
>>> 
>>> Otherwise we could use another fiscal host. Fiscal hosts can ask for a fee 
>>> for their services, usually around 5%, but they don't have to.
>>> 
>>> Opencollective uses stripe for credit card payments and also allows payment 
>>> via PayPal. Those payments generally also come with a small fee, so a few 
>>> percent of the money people give is lost on the way.
>>> 
>>> Moritz
>>> 
>>> Am 16. März 2021 21:35:57 MEZ schrieb Michael Barton 
>>> :
>>> I believe that a 'fiscal host' is a place where you can deposit money and 
>>> keep it until needed or moved to a different local. It could be a bank 
>>> account or other account. 
>>> 
>>> Michael
>>> _
>>> C. Michael Barton 
>>> Director, Center for Social Dynamics & Complexity
>>> Director, Network for Computational Modeling in Social & Ecological Sciences
>>> Associate Director, School of Complex Adaptive Systems
>>> Professor, School of Human Evolution & Social Change
>>> Arizona State University
>>> Tempe, AZ  85287-2402
>>> USA
>>> 
>>> voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
>>> fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
>>> www: http://shesc.asu.edu, https://complexity.asu.edu, 
>>> http://www.public.asu.edu/~cmbarton
>>> 
>>>> On Mar 16, 2021, at 12:12 PM, Veronica Andreo  wrote:
>>>> 
>>>> Hi Moritz, 
>>>> 
>>>> Thanks a lot for this initiative! Open collective seems like a pretty cool 
>>>> complement to other existing ways of collecting money.
>>>> 
>>>> I was inspecting a bit which other organizations are there, and I found 
>>>> many well known companies and NGOs (See for example: 
>>>> https://opencollective.com/babel). Furthermore, it seems it also allows 
>>>> for recurring contributions with different categories.
>>>> 
>>>> I do not understand the fiscal host part, but as you say maybe OSGeo can 
>>>> become a fiscal host. Would you ask them too? 
>>>> 
>>>> Cheers,
>>>> Vero
>>>> 
>>>> El sáb, 13 mar 2021 a las 16:34, Moritz Lennert 
>>>> () escribió:
>>>> Dear all,
>>>> 
>>>> FYI, for our accounting I have created a continuous ledger in 
>>>> https://nextcloud.osgeo.org/ -> GRASS-

Re: [GRASS-PSC] [motion] Language standard support for C and C++ in GRASS GIS

[Helena Mitasova]

> On Mar 22, 2021, at 4:24 PM, Martin Landa  wrote:
> 
> Dear PSC,
> 
> po 22. 3. 2021 v 20:57 odesílatel Veronica Andreo  
> napsal:
>> This motion is to vote for RFC 7 
>> (https://trac.osgeo.org/grass/wiki/RFC/7_LanguageStandardsSupport) that sets 
>> the language standard support for C and C++ in GRASS GIS.
>> 
>> Motion:
>> I hereby start with a +1
> 
> +1
> 
> Martin

+1   Helena

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

"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

[GRASS-PSC] Fwd: [GSoC 2021 - Urgent] Feedback Required Regarding Disbursal of GSoC Org Payments/Mentor Stipend to the Mentors

[Helena Mitasova]

I am not sure whether other members of PSC or other GSoC mentors received this 
but here is a message from Rajat regarding the potential GSoC mentor 
compensation. Feel free to read the entire message below but here is the 
important part (note that I was at the board meeting 
where this was discussed and the feedback from the board was that osgeo will 
give the funds to the participating projects to use as they see fit.)
So if you have ideas about what is the best procedure to receive and distribute 
the funds for the GRASS project
please share them here on the PSC list and I will compile them and provide to 
Rajat (note that this would be $1200 if we get 3 slots)

As a backup mentor I would vote for all funds going to the main mentor or to 
cover some collaborative development activity (in the past
it would have been e.g. travel to code sprint).

Helena

> Our decision as administrators is to reach out to the projects’ PSC for your 
> comments about the following idea.
> GSoC team will deposit $400 per accepted proposal
> The project can claim the money and distribute it to the “main” mentors and 
> “backup” mentors as they see fit.
> The claim can be done after the GSoC team deposits the stipend to the OSGeo 
> organization.
> 
> This idea has not yet been approved by the board, we need your input to 
> refine the idea and procedure. Based on your inputs, we will list the 
> possible options and forward them to the OSGeo board for their comments.


> Begin forwarded message:
> 
> From: Rajat Shinde 
> Subject: [GSoC 2021 - Urgent] Feedback Required Regarding Disbursal of GSoC 
> Org Payments/Mentor Stipend to the Mentors
> Date: April 29, 2021 at 3:11:29 PM EDT
> To: Helena Mitasova 
> Cc: "gsoc-adminosgeo.org" , Rahul Chauhan 
> 
> 
> Dear Prof. Mitasova,
> 
> Greetings!
> I am sending this email with regards to the Google Summer of Code (GSoC) 2021 
> stipend for mentors. This is OSGeo’s 15th year participating in the GSoC 2021 
> and GRASS GIS is one of the participating projects under the OSGeo umbrella 
> organization. Also, this is our second year working as OSGeo-GSoC 
> administrators team, and since last year it came to our attention that 
> mentors were not getting remuneration for their work. We feel that this is 
> very unfortunate and lacks incentive for the mentors to continue mentoring. 
> Moreover, mentoring for GSoC is a full-time commitment and requires a lot of 
> effort (which might vary depending on the coding and administration 
> mentoring). 
> 
> In this regard, I had a meeting with the board on April 26 [1] and it was 
> clear to me that the GSoC program does make a deposit to OSGeo. Citing below 
> from the website for reference:
> 
> [1] 
> https://wiki.osgeo.org/wiki/Board_Meeting_2021-04-26#Google_Summer_of_Code_organization_payment_discussion
>  
> <https://wiki.osgeo.org/wiki/Board_Meeting_2021-04-26#Google_Summer_of_Code_organization_payment_discussion>
> 
> “$400 per student developer for your organization (often called the mentor 
> stipend) though the money does not generally go to the actual mentor. One 
> payment is sent to the org, and if the org wishes to disburse the funds to 
> their mentors they are welcome to do that on their own.” [2]
> 
> [2] 
> https://developers.google.com/open-source/gsoc/help/org-payments#i_included_in_your_payment
>  
> <https://developers.google.com/open-source/gsoc/help/org-payments#i_included_in_your_payment>
> During the meeting I mentioned the following facts:
> Accepted proposals are required to have at least 2 mentors and one of them is 
> the “main” mentor
> It is strongly recommended to have 3 mentors
> The additional mentors are “backup” mentors
> A mentor can not mentor more than 2 proposals
> A mentor can not be the “main” mentor of 2 or more proposals
> Having mentioned that the number of projects participating in the OSGeo-GSoC 
> program has been decreasing, as a comparison:
> 20 proposals in 12 projects in 2016 
> (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2016_Accepted 
> <https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2016_Accepted>)
> 13 proposals in 8 projects in 2017 
> (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2017_Accepted 
> <https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2017_Accepted>)
> 10 proposals in 8 projects in 2018 
> (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2018_Accepted 
> <https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2018_Accepted>)
> 7 proposals in 4 projects in 2019 
> (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2019_Accepted 
> <https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2019_Accepted>)
> 10 proposals in 6 projects in 2020 
> (https://wiki.osgeo.org/wiki/Google_Summer_of_

Re: [GRASS-PSC] [GSoC 2021 - Urgent] Feedback Required Regarding Disbursal of GSoC Org Payments/Mentor Stipend to the Mentors

[Helena Mitasova]

s soon as possible, so that we can forward it 
> to the OSGeo board for approval. It would be amazing if we could get the 
> responses before the GSoC slot submission deadline i.e. May 3rd, 2021.
> 
> Kind regards
> Rajat Shinde and Rahul Chauhan
> OSGeo-GSoC Administration Team
> URL: https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2021_Administrative

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

"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

[GRASS-PSC] Fwd: [OSGeo AGM 2021] [Action required] GRASS GIS upload link please upload your video till August 30

[Helena Mitasova]

I am not sure whether this was discussed already or anybody from PSC knows 
about this but we need to prepare 
a short 1 minute video about GRASS updates for FOSS4G AGM - see more details 
below and here
https://wiki.osgeo.org/wiki/Annual_General_Meeting_2021 
<https://wiki.osgeo.org/wiki/Annual_General_Meeting_2021>

I checked the slides and GRASS project is updated (thanks Vasek?) so that is 
done, now we need the video.
I think that adding 2 narrated slides with some nice images/photos/animations 
would be great and we will
need a volunteer to record. 

I shared google slides with you - it has the AGM slide and 2 additional as 
template - feel free to add material keeping
in mind that it should be 1 minute.

Thanks a lot, Helena

> Begin forwarded message:
> 
> From: "Astrid Emde (OSGeo Secretary)" 
> Subject: [OSGeo AGM 2021] [Action required] GRASS GIS upload link please 
> upload your video till August 30
> Date: August 16, 2021 at 11:56:17 AM EDT
> To: Markus Neteler , hmit...@ncsu.edu
> Reply-To: secret...@osgeo.org
> 
> Hello Markus, hello Helena,
> 
> we invite you and your team to present the GRASS GIS project at the OSGeo AGM 
> 2021.
> 
> This year we will publish the OSGeo AGM video in advance of FOSS4G [1].
> 
> You find all important information about the AGM at [5].
> 
> 
> Video upload link
> ---
> Please use the following upload link to upload your video (Deadline 
> 2021-08-30)
> 
> https://vortraege.fossgis.de/u/d/b87f9e4fef7b434a839a/
> 
> Timeline
> ---
> - 2021-08-30: upload your video and update the AGM slides [2]
> - 2021-09-10: AGM 2021 complete video will be published
> - 2021-10-01: 11h Argentinian Time Zone (14:00 UTC) Join the OSGeo AGM 2021 
> meeting at FOSS4G [3] [4]
> 
> If you have questions or problems with the upload of your video please let us 
> know secretary (at) osgeo (dot) org.
> 
> Stay safe,
> 
> Astrid Emde
> OSGeo Secretary
> 
> [1] https://www.youtube.com/channel/UCDvJEf8hXbyeVqaYaS8sLvw
> [2] 
> https://docs.google.com/presentation/d/1brbBb7-sKRI6U4dZ7LKnBT_-NnWzyS2TaZqVXzy8RDo/edit#slide=id.p4
> [3] https://callforpapers.2021.foss4g.org/foss4g2021/talk/WDEW3P/
> [4] 
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&month=10&day=1&hour=14&min=0&sec=0&p1=51&p2=26&p3=49&p4=155&p5=217&p6=312&p7=250&p8=71&p9=248&p10=240
> [5] https://wiki.osgeo.org/wiki/Annual_General_Meeting_2021
> 
> -- 
> 
> -
> Astrid Emde
> OSGeo Board Member and OSGeo Secretary
> Open Source Geospatial Foundation
> https://www.osgeo.org/member/astrid-emde/
> astrid_e...@osgeo.org
> 

Helena Mitasova
Professor, Department of Marine, Earth and Atmospheric Sciences
Faculty Fellow,
Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu



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

[GRASS-PSC] Fwd: Card or Flowers for Markus?

[Helena Mitasova]

Vero,

I received a question below from our colleague who knows Markus quite well.
I assume that sending individual cards won’t work well but perhaps we can set 
up a virtual card that people 
from the community can sign? I am not sure what is available but maybe there is 
a good way how to do this?

Thank you, Helena

> Begin forwarded message:
> 
> From: Doug Newcomb 
> Subject: Card or Flowers for Markus?
> Date: August 30, 2021 at 8:51:18 AM EDT
> To: Helena Mitasova 
> 
> Helena,
> Is there any way we can send Markus a card or flowers?
> 
> Doug

Helena Mitasova
Professor, Department of Marine, Earth and Atmospheric Sciences
Faculty Fellow,
Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu



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

Re: [GRASS-PSC] First draft of call for student grants

[Helena Mitasova]

Dear all - I don’t have time right now to write more but as I was reading the 
document and thinking about all the pitfalls of paying for work 
I was wondering whether we should follow an example from geoforall and do it as 
award / prize for the work done -
e.g. Annual award for the best student contribution to GRASS (no invoices 
needed, but PSC will need to evaluate the contributions
and let students know about the opportunity).

Feel free to ignore this suggestion - it just came to mind as Geoforall is 
launching "Pitch your research competition, where students will have 5 minutes 
to talk about their project showcasing open source, open data or open 
standards.” with cash prizes from the OSGeo budget.

Helena
 
> On Nov 16, 2021, at 5:40 AM, Moritz Lennert  
> wrote:
> 
> Thanks, Vero, for your feedback (and Vaclav for the direct change) !
> 
> Here are some comments/replies.
> 
> Am 15.11.2021 21:35 schrieb Veronica Andreo:
>> This is great Moritz! Thanks for taking the lead on this and drafting
>> the call!
>> Here are my comments/questions:
>> - _"be eligible to work in the country in which they reside" -->
>> _maybe this is related to them having a tax number or bank account, no
>> idea.
> 
> I think it is more linked to the fact that GSoC pays for a student job, no ? 
> Or is it also considered a grant ?
> Maybe we can leave this out and only add it in the future if the issue 
> arises. But IANAL.
> 
>> Questions might be if the money goes directly from OSGeo to the
>> student, won't OSGeo need an invoice? If we pay directly from our bank
>> account, do we need it?
> 
> If necessary we can provide a standard form for requesting the payment of the 
> grant which function as invoice.
> 
>> - The agreement of a GRASS GIS core developer to mentor the student's
>> work --> Maybe no need to be core, perhaps no need to be dev at all if
>> the student proposes to create educational material. In any case, some
>> sort of mentor would be desired in my opinion.
> 
> Agreed.
> I changed to "an active member of the GRASS GIS community". Not sure how to 
> formulate it differently to ensure inclusion of all categories.
> 
>> - In the nature of the grant section, should we set a maximum
>> duration, eg. 2 months or so?
> 
> Done
> 
>> - In the how to apply section: email with proof of eligibility should
>> be sent to some of us privately I think for data privacy reasons (?).
> 
> Yes, that's why I put XYZ as the address. Maybe we can create an @osgeo.org 
> address for this ?
> 
>> Would be nice to ask them to introduce themselves to the community
>> too, no? Probably once accepted.
> 
> Yes, but not sure this needs to be in the grant procedure description.
> 
>> - Approval: 2 weeks sound better to me
> 
> ok, done
> 
>> - Final report: the report in the wiki seems fine to me, could also be
>> the trac wiki where all the GSoC reports live too.
> 
> I agree, but this raises the more fundamental question whether in the long 
> run we want to continue with two wikis, especially with the trac wiki, 
> knowing that we do not use trac for anything else anymore.
> 
>> The final report
>> could be sent to grass-dev and psc mailing lists.
> 
> Added.
> 
> Moritz
> 
> 
>> El lun, 15 nov 2021 a las 13:07, Moritz Lennert
>> () escribió:
>>> Dear all,
>>> Following the discussions at today's PSC I've written a first draft
>>> of a
>>> call for student grants:
>>> https://grasswiki.osgeo.org/wiki/Student_Grants [1].
>>> Several points still need clarification (see comments in
>>> [brackets]).
>>> Feel free to edit as you see necessary.
>>> If we really want to go forward with this still before Christmas,
>>> then
>>> we need to have the final version ready by end of next week the
>>> latest.
>>> Enjoy your weekend !
>>> Moritz
>>> ___
>>> grass-psc mailing list
>>> grass-psc@lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/grass-psc [2]
>> Links:
>> --
>> [1] https://grasswiki.osgeo.org/wiki/Student_Grants
>> [2] 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

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

"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] [Motion] Approve Linda's proposal for GRASS mini grant

[Helena Mitasova]

+1 

Helena
> On Dec 14, 2021, at 3:00 AM, Veronica Andreo  wrote:
> 
> Dear all, 
> 
> As previously discussed, I hereby propose that we approve and accept Linda 
> Kladivova's application for the first GRASS mini grant for students and that 
> we issue the first payment as described here: 
> https://grasswiki.osgeo.org/wiki/Student_Grants.
> 
> Linda's proposal is to continue working on the Single window and redesign the 
> map display status bar combo box into a new settings dialog to reach a fully 
> working single window GUI mode. 
> 
> I will start with my +1!
> 
> Thanks in advance,
> Vero
> ___
> 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

"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] [Motion] Approve Caitlin's proposal for GRASS mini grant

[Helena Mitasova via grass-psc]

+1 
Helena
P.S. Just a note that I have what could be considered a conflict of interest as 
I am her PhD co-advisor


> On Dec 29, 2021, at 7:11 PM, Michael Barton  wrote:
> 
> +1
> 
> __
> Michael Barton
> 
> Sent from  my iPhone
> Please excusr any typoz
> 
>> On Dec 29, 2021, at 4:13 PM, Veronica Andreo  wrote:
>> 
>> 
>> Dear all, 
>> 
>> I hereby propose to approve and accept Caitlin Haedrich's application for a 
>> GRASS mini grant and to issue the first payment as described here: 
>> https://grasswiki.osgeo.org/wiki/Student_Grants 
>> .
>> 
>> Caitlin was a GSoC 2021 student and her proposal for this 2 months mini 
>> grant is to continue working on the GRASS-Jupyter integration, more 
>> specifically on Space-Time Dataset Visualization and Improved Interactive 
>> Maps for grass.jupyter. The proposal was sent privately as described in the 
>> wiki above (for future mini grants calls we should consider moving to a 
>> public place, i.e., grass wiki, trac wiki, github, etc.). 
>> 
>> I will start with my +1!
>> 
>> Thanks in advance,
>> Vero
>> 
>> ___
>> grass-psc mailing list
>> grass-psc@lists.osgeo.org
>> https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!K3syhAtgMW3WalvoIPrBaXoAbkue6SVpnUi-5g_q9gKM6HQvu6LaKLfJ57kC1p2Ni-s$
>>  
> ___
> 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] GRASS DOI

[Helena Mitasova via grass-psc]

Peter Loewe is including the OSGeo projects' DOI in the Springer Handbook
chapter about open source geospatial
and we noticed that the authors names are messy (some are just ID) - I
assume that this is autogenerated and I am wondering
what would be the best way to fix it. Vashek, did you set this up? Do you
have any suggestions?
Here is the GRASS DOI link
https://doi.org/10.5281/zenodo.5810537

Thank you, Helena

Helena Mitasova
Professor, Department of Marine, Earth and Atmospheric Sciences
Faculty Fellow, Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208


-- Forwarded message -
From: Peter Löwe 
Date: Mon, Jan 3, 2022 at 11:09 AM
Subject: Aw: Re: Open Source Chapter of the Springer Handbook of
Geoinformation: Status update / New Deadline / Opportunity
To: Helena Mitasova 


Helena,

I just checked the DOI landing page for GRASS GIS (
https://doi.org/10.5281/zenodo.5810537).
It's amazing to see how the content has grown.

One minor detail: Your name shows in the list of authors in uppercase
letters, unlike the other authors. Is this intended ?

1. Martin Landa, Markus Neteler, Markus Metz, Anna Petrasova, glynnc,
HamishB, Vaclav Petras, huhabla, Huidae Cho, Luca Delucchi, Pietro, Michael
Barton, Yann Chemin, Tomas Zigo, Māris Nartišs, ostepok, Helmut Kudrnovsky,
mlennert, nilason, Stefan Blumentrath, William Kyngesburye, Linda
Kladivova, aghisla, Veronica Andreo, 積丹尼 Dan Jacobson, Denis Ovsienko,
madi, HELENA MITASOVA, Carmen Tawalika, Caitlin H.: OSGeo/grass: GRASS GIS
8.0.0RC1, (2021)

Cheers,
Peter




> Gesendet: Sonntag, 26. Dezember 2021 um 04:57 Uhr
> Von: "Helena Mitasova" 
> An: "Peter Löwe" 
> Cc: "Markus Neteler" 
> Betreff: Re: Open Source Chapter of the Springer Handbook of
Geoinformation: Status update / New Deadline / Opportunity
>
> Peter,
>
> Thank you for sharing the proof - the GRASS history and section looks
good to me, just a minor request if possible -
> For the Fig. 30.2 would it be possible to add GRASS GIS to the caption?
Something like this
> Examples of geospatial modeling and analysis in GRASS GIS with 2D/3D
raster data, vector data and tangible interaction.
>
> Thank you and let's hope for a Happy New Year,
>
> Helena
>
> > On Dec 23, 2021, at 4:42 AM, Peter Löwe  wrote:
> >
> > Dear co-authors of the Open Source Chapter of the Springer Handbook of
Geoinformation,
> >
> > I hope you are all in good health, ready for the upcoming holiday
season and the new year.
> >
> > Work on the Springer Handbook of Geoinformation has progressed.
Corrections and updates for all chapters are being implemented and checked.
The Handbook is now scheduled to be published in 2022.
> >
> > A new proof of our chapter is available here:
https://www.le-tex.de/dbdownload/6oAP4r6MyilKUIufQzXwRgnp29tm5OSIiLiCtcdp/M_3_030_proof_2.pdf
> >
> > A few minor quirks have been noted in the proof, which will be fixed.
> >
> > The Editors are asking us to review the proof and indicate any
additional corrections before January 6, if necessary.
> >
> > Please note that any changes in the chapter text are at this stage
limited to typographical errors and serious errors of fact.
> > Please review the parts of the document you have written and send me
your corrections before January 6, if necessary.
> >
> > In addition, I would like to point out an opportunity which has emerged
due to recent advances in scientific citation for software projects with
Digital Object Identifiers (DOI).
> > In the last months, improved options for the citation of open source
software projects have become available.
> > In a nutshell, any open source software project which is hosted on
GitHub (e.g. all OSGeo projects) can now be linked to the scientific Open
Access repository Zenodo (www.zenodo.org)
> > based on a persistant identifier (DOI), which can be used for
scientific citation, as in our chapter.
> >
> > Unlike a URL, a DOI can never "break" and it is guaranteed to point to
the lastest version of the software, which would be added value for the
readers of our chapter.
> >
> > In addition (this is new), the DOI reference can provide due scientific
credit to the whole project team (first authors, developers, maintainers,
etc.).
> > This is an emerging approach, which was first rolled out for
GitHub/Zenodo, there are also ongoing efforts to establish this for
GitLab-based software repositories.
> >
> > This creates a win-win-win situation, as our chapter will receive its
own DOI (as an individual book chapter, linked to the DOI of the overall
Handbook), which will be linked (for scientific credit from citation) to
the ORCIDs of all Coauthors, but _also_ to the software project DOIs and
their respective teams (and the

Re: [GRASS-PSC] Budget 2022

[Helena Mitasova via grass-psc]

Few comments, suggestions:

1. regarding unspent money from 2021 - if I remeber correctly, past OSGeo board 
policy was that if a project does not request the funds the given year the 
funds stay with OSGeo (the funds
do not roll-over to next year - this happened all the time),
but it may be worth reaching out to Michael Smith to see whether he would 
transfer the funds allocated for GRASS in 2021 to our account, given that we 
want to cover the 2021 student microgrants
and that many projects probably did not spend much money last year as well. 

2. There is a separate OSGeo budget item for code sprints - there has always 
been some confusion about that, so let us keep it in our budget and see what 
the board says.

3. Given the limited travel opportunities we could budget maybe $500-1000 to 
cover registration fees for on-line / hybrid conferences beyond FOSS4G to give 
presentations
or workshops to promote GRASS GIS development and applications to broader 
scientific community if there is an interest to do it.

4. I think that the students microgrants are a great idea and we should clearly 
split it as $2000 for 2021 and maybe $4000 for 2022.

Helena

Helena Mitasova
Professor, Department of Marine, Earth and Atmospheric Sciences
Associate Director and Faculty Fellow, Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu


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




> On Jan 8, 2022, at 12:31 PM, Michael Barton  wrote:
> 
> I've looked at it and it seems reasonable. I can't offer much in the way of 
> useful suggestions since this is being spent in Europe and you folks are more 
> up to date on costs there. Basing it on previous years seems reasonable. 
> 
> Michael
> _
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (https://scas.asu.edu 
> <https://scas.asu.edu/>)
> Professor, School of Human Evolution & Social Change (https://shesc.asu.edu 
> <https://shesc.asu.edu/>)
> Director, Center for Social Dynamics & Complexity (https://complexity.asu.edu 
> <https://complexity.asu.edu/>)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
> 
> Executive Director, Open Modeling Foundation 
> (https://openmodelingfoundation.github.io 
> <https://openmodelingfoundation.github.io/>)
> Director, Network for Computational Modeling in Social & Ecological Sciences 
> (https://comses.net <https://comses.net/>)
> 
> personal website: http://www.public.asu.edu/~cmbarton 
> <http://www.public.asu.edu/~cmbarton> 
> 
> 
>> On Jan 8, 2022, at 8:42 AM, Moritz Lennert > <mailto:mlenn...@club.worldonline.be>> wrote:
>> 
>> Hi Vero, Hi all,
>> 
>> Am 07.01.2022 02:02 schrieb Veronica Andreo:
>>> Dear all,
>>> 
>>> It is that time of the year :) We need to submit our budget by Jan 20,
>>> 2022.
>>> 
>>> I have already created the relevant page (1)
>> 
>> Please note that we decided to work on the budget in a spreadsheet in 
>> the OSGeo Nextcloud (file grass_project_budgets.ods, with a tab for each 
>> year, mentioned in the wiki as the download link 'Master file': 
>> https://urldefense.com/v3/__https://nextcloud.osgeo.org/s/dKXfqq4QkMmSkB5__;!!IKRxdwAv5BmarQ!LIT5_n7Gk9QvyNHoIPo4r-6WQBzuNjA9OM6n0knO_MO9uc5CRuYEYB641hjtgWu4tbQ$
>>  
>> <https://urldefense.com/v3/__https://nextcloud.osgeo.org/s/dKXfqq4QkMmSkB5__;!!IKRxdwAv5BmarQ!LIT5_n7Gk9QvyNHoIPo4r-6WQBzuNjA9OM6n0knO_MO9uc5CRuYEYB641hjtgWu4tbQ$>
>>  ) in order to make 
>> modifications easier while elaborating it. At the end it can be easily 
>> copied over to the wiki. I created the 2022 tab and synchronized between 
>> the wiki and the spreadsheet.
>> 
>>> and put in some suggested
>>> values thinking of in-person events for this year and offering 3x1000
>>> euro mini grants. What do you think? Do we consider travel grants as
>>> well? How many? Please, go ahead and edit directly.
>>> 
>>> @Moritz Lennert Would you please help out there with bank fees,
>>> surplus from 2021
>> 
>> I've updated the ledger in Nextcloud which represents our detailed 
>> accounts transaction by transaction. As a summary, here is our current 
>> financial situation as of Dec. 31, 2021:
>> 
>> - PayPal Money Pool: 3178.26€ (2698€ in donations in 2021)
>> - Bank Account: 869.67€ (-543,60€ spent of which -43.60€ for bank fees 
>> and taxes)
>> - OpenCollective: 206.67$ (all donations of 2021)

Re: [GRASS-PSC] [Motion] Approve Linda's student grant final report and issue the second payment

[Helena Mitasova via grass-psc]

+1 

Helena 


> On Mar 4, 2022, at 10:58 AM, Huidae Cho  wrote:
> 
> +1
> 
> Huidae
> 
> -- 
> Huidae Cho, Ph.D., GISP
> GRASS GIS Developer
> https://idea.isnew.info/ 
> Sent from my phone
> 
> On Fri, Mar 4, 2022, 9:21 AM Vaclav Petras  > wrote:
> +1 for Linda!
> 
> On Fri, Mar 4, 2022, 7:09 AM Markus Neteler  > wrote:
> +1 Markus
> Thanks Linda and mentors!
> 
> On Thu, Mar 3, 2022 at 11:30 PM Veronica Andreo  > wrote:
> >
> > Dear PSC,
> >
> > Linda has just completed her project for the student grant and submitted 
> > the final report (I FWD it here in case you missed it).
> >
> > I hereby propose to approve her final report and issue the second half of 
> > the payment. Big thanks to Linda and her mentors for your work and 
> > commitment!
> >
> > I start with my +1 !!
> >
> > Vero
> >
> > -- Forwarded message -
> > De: Linda Kladivová mailto:l.kladiv...@seznam.cz>>
> > Date: mié, 2 mar 2022 a las 19:19
> > Subject: [GRASS-dev] Final report for Mini project 2022: Redesigning a map 
> > display status bar combo box into a new settings dialog
> > To: mailto:grass-...@lists.osgeo.org>>, 
> > mailto:grass-u...@lists.osgeo.org>>
> >
> > Hello everyone,
> >
> >
> > I am sending my final Mini Project report. The more detailed version with 
> > permanent links on GitHub PRs and with several screenshots can be found at 
> > the project wiki [1].
> >
> > Abstract:
> >
> > Especially for Single-Window GUI, the Map Display status bar needs to be 
> > lightened up a bit since in the case of opening more Map Display notebook 
> > pages the check box on the right side of the status bar gets shrunk. The 
> > solution is to remove the combo box in the status bar occupying too much 
> > space and implement a new Map Display settings dialog accessible from the 
> > top map display toolbar.
> >
> > The state of the art BEFORE the start of Mini Project:
> >
> > At this moment, the status bar at the bottom of the Map Display window 
> > consists of the text/widget section, the combo box, the mask and the check 
> > box. For the Single-Window GUI, the number of widgets must be reduced so 
> > that the check box on the right side of the status bar is not shrunk.
> >
> > The state of the art AFTER Mini Project:
> >
> > The new Map Display settings dialog is introduced. The main task of this 
> > dialog is to manage General Map Display settings and Statusbar settings. It 
> > implies that the status bar combobox is not needed anymore because we can 
> > find all Map Display settings including status bar customization in the new 
> > dialog.
> >
> >
> > Next Steps:
> > Other possible improvements related to status bar stuff could be:
> >
> > Moving Projection page from GUI settings to the Map Display status bar 
> > settings
> > Adding context menu for status bar customization
> > Adding EPSG code label of current location to the main status bar
> > Merging „Go to coordinates X, Y“ and „Coordinates“ item into one widget
> >
> > Permanent links and screenshots can be found at [2] and [3].
> >
> > [1] https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/RedesigningStatusbar 
> > 
> >
> > [2] 
> > https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/RedesigningStatusbar#FinalReport
> >  
> > 
> >
> > [3] 
> > https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/RedesigningStatusbar#BrandnewScreenshotsofMapDisplaySettingsdialog
> >  
> > 
> >
> > Have a nice week,
> >
> > Linda
> > ___
> > grass-dev mailing list
> > grass-...@lists.osgeo.org 
> > https://lists.osgeo.org/mailman/listinfo/grass-dev 
> > 
> > ___
> > grass-psc mailing list
> > grass-psc@lists.osgeo.org 
> > https://lists.osgeo.org/mailman/listinfo/grass-psc 
> > 
> 
> 
> 
> -- 
> Markus Neteler, PhD
> https://www.mundialis.de  - free data with free 
> software
> https://grass.osgeo.org 
> https://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/l

Re: [GRASS-PSC] [Motion] Approve Caitlin's student grant final report and issue the second payment

[Helena Mitasova via grass-psc]

+1 Helena
Helena Mitasova
Professor, Department of Marine, Earth and Atmospheric Sciences
Faculty Fellow, Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208


On Tue, Apr 19, 2022 at 5:25 PM Vaclav Petras  wrote:

> +1, Vaclav
>
> On Tue, 19 Apr 2022 at 17:17, Veronica Andreo 
> wrote:
>
>> Dear PSC,
>>
>> Caitlin has just completed her project for the student grant and
>> submitted the final report (I FWD it here in case you missed it).
>>
>> I hereby propose to approve her final report and issue the second half of
>> the payment. Big thanks to Caitlin and her mentors for your work and
>> commitment! Thanks as well to those testing and providing feedback along
>> the process! Great work Caitlin!! Congratulations!
>>
>> I start with my +1 !!
>>
>> Vero
>>
>> -- Forwarded message -
>> De: Caitlin Haedrich 
>> Date: lun., 18 abr. 2022 19:25
>> Subject: [GRASS-dev] grass.jupyter Mini Project Final Report
>> To: , 
>>
>>
>> Hi all,
>>
>> Last week, we wrapped a final push on grass.jupyter and are excited for
>> its official release with GRASS 8.2. Here's my final report along with a
>> summary of grass.jupyter changes introduced as part of the project. Thank
>> you all for your support, feedback and testing over the past few months!
>>
>> *The state of the art BEFORE the start of the Mini Project:*
>> During GSoC 2021, we created “grass.jupyter”, a package that improves the
>> integration of GRASS GIS and Jupyter with a set of functions for displaying
>> GRASS data in Jupyter Notebooks. In its previous state, “grass.jupyter”
>> allows users to create static visuals and simple interactive maps. However,
>> several additional features are needed to allow Jupyter users to fully and
>> easily access the power GRASS, including space-time dataset visualization
>> and more options for interactive mapping.
>>
>> *Project Goals*:
>> In preparation for the stable release of grass.jupyter with GRASS 8.2,
>> this project had three main goals: (1) create space time dataset
>> visualizations for use in Jupyter Notebooks, (2) improve the integration of
>> GRASS with folium (leaflet library for Python) and (3) write a function for
>> displaying vector attributes in nicely-formatted tables (using Pandas or
>> Geopandas). Along the way, we also wanted to finalize the naming of
>> grass.jupyter classes and create documentation (thank you Vaclav Petras).
>>
>> *The state of the art AFTER the Mini Project:*
>> 1. New TimeSeriesMap class that creates ipywidget time sliders of space
>> time datasets (see attached timeseriesmap.png) and a notebook documenting
>> it's usage [1]
>> 2. Improved GRASS-folium integration allowing rasters and vectors to be
>> added to existing folium maps (see attached grass-folium.png) and updated
>> notebook demonstrating its usage [2]
>> 3. Updated class names:
>>
>>- GrassRenderer -> Map
>>- Grass3dRenderer -> Map3D
>>- InteractiveMap
>>- TimeSeries -> TimeSeriesMap
>>
>> 4. Thanks to Vaclav Petras, we also have a manual page for grass.jupyter
>> [3]
>> 5. I didn't end up working to integrate GRASS and Pandas. It seems that
>> it is quite straightforward to display vector attributes in
>> nicely-formatted Pandas tables. For example:
>>
>> >>> import pandas as pd
>>
>> >>> import sqlite3
>> >>> sql_path = gs.read_command("db.databases",
>> driver="sqlite").replace('\n', '')
>> >>> con = sqlite3.connect(sql_path)
>> >>> sql_stat="SELECT * FROM field"
>> >>> df = pd.read_sql_query(sql_stat, con)
>>
>> >>> con.close()
>> >>> df
>>
>> There are other outputs that would be nice to display in nice Pandas
>> tables, like text output from r.univar, r.stats, or t.vect.list. However,
>> this is difficult since there is no standard output that is easily
>> parse-able to pandas. I think the best way would be to create a standard
>> json or csv output for all modules that return text. Then, it would be
>> simple to take any module output and convert to a nice-looking Pandas table.
>>
>> *Next Steps:*
>> 1. Bug: InteractiveMap does not honor use_region=True for vectors.
>> 2. Bug: InteractiveMap for Jupyter does not handle not existing data
>> properly (https://github.com/OSGeo/grass/issues/2302)
>> 3. InteractiveMap: add legend options for rasters, suppor