[GRASS-PSC] Re: [Incubator] Motion: GRASS to Graduate Incubation

[Jody Garnett]

Frank Warmerdam wrote:

If you insist, I'll populate the Wiki page with notes.


No need!  I just wanted to get a sense of the review process for
my own comfort and that of other committee members.
I actually found your email quite informative; it is good to have some 
guidance on what a sensible level of automation is.

Quite the amazing history for this code base :-)

+1

Jody



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

Re: [GRASS-PSC] GRASS Development team as a legal entity

[Jody Garnett]

Jody here with a few links to share:

The GeoTools PMC asked these questions from OSGeo legal council a couple
years back, the long and short of it is that this these requirements are
grounded in an international treaty (so nothing US specific).

Here are some references out of that session:

   - Copyright Headers in Source Code
   

(GeoTools
   blog post writing up legal advise from OSGeo)
   - Update to Copyright Header Policy
   

(GeoTools
   Proposal based on the above)
  - Coding Style
  
(GeoTools
  Developers Guide)
  - GeoTools Header Policy Updated
  

(Blog
  post)

While there were a few surprises for me personally out of this exchange,
the good news is that headers are not strictly needed to claim copyright
(so any missteps we do here will cause long term harm). The other important
note is that copyright is the legal stick we use to enforce our open source
license ... so we end up caring about this a lot as a foundation ( (perhaps
more that proprietary software who use trade secret).

On Wed, Feb 13, 2019 at 1:09 PM Michael Barton 
wrote:

> Important questions. But I’m not sure if we have the expertise to answer.
> Is there a legal expert among us?  Also, since OSGeo is in the US, does
> that mean that all GRASS has to comply with Us copyright laws?  Many
> authors are not from the US. How does this work in an international Open
> Source project.  I have a vested interest in hearing from legal minds
> because of other initiatives in addition to GRASS.
>
> Michal
>
> Michael Barton
> School of Human Evolution &Social Change
> Center for Social Dynamics & Complexity
> Arizona State University
>
> ...Sent from my iPad
>
> > On Feb 13, 2019, at 8:56 PM, Markus Neteler  wrote:
> >
> > Hi PSC,
> >
> > in the incubator list the question came up if GRASS Development team
> > is legal entity to which the copyright can be assigned.
> >
> > At time the GRASS Development team is not an incorporated entity but
> > usually the first copyright holder name in the source code files is
> > the initial author followed by the GRASS Development team.
> > If that's legally sufficient I cannot say nor what the implications are.
> >
> > Hence this mail to start a discussion on this.
> >
> > Best,
> > 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-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=Ys10Rz0ZpFEXXLN_nhgDgUVGQWTr4C1UUQsuavJYjoA&s=GZgL4GgXWxa7XuPpNzXBvs12M5MTtLAc72pCJ2a14jk&e=
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] GRASS Development team as a legal entity

[Jody Garnett]

Thanks for taking this up Markus:

I know when GeoTools went through incubation we had to change our codebase
from "(c) GeoTools Project Management Committee" since it was not a legal
entity; indeed retroactively creating a legal entity was shot down as an
idea also. The good news is that we have some recent legal guidance from
osgeo
<http://geotoolsnews.blogspot.com/2016/07/copyright-headers-in-source-code-files.html>
on this topic.

The examples that were provided to to incubation simply listed Copyright
(c) GRASS Development Team. The approach you describe using "initial author
followed by grass development team" sounds much better, it is very similar
to what our friends at the eclipse foundation
<https://www.eclipse.org/legal/epl-2.0/faq.php#h.aq5xwcjmpy2a> do: *Copyright
(c) {date} {owner} [and others]*


--
Jody Garnett


On Wed, 13 Feb 2019 at 11:56, Markus Neteler  wrote:

> Hi PSC,
>
> in the incubator list the question came up if GRASS Development team
> is legal entity to which the copyright can be assigned.
>
> At time the GRASS Development team is not an incorporated entity but
> usually the first copyright holder name in the source code files is
> the initial author followed by the GRASS Development team.
> If that's legally sufficient I cannot say nor what the implications are.
>
> Hence this mail to start a discussion on this.
>
> Best,
> Markus
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Fwd: [OSGeo-Discuss] osgeo budget 2019

[Jody Garnett]

I did note in your budget a "GRASS GIS Community Sprint" item, is there a
reason this was requested in your committee budget (rather than through the
code sprint guidelines?) I ask because PostGIS made similar arrangements
and I wanted to ask if there is a pattern we could fix?

Personally I feel it offers a lot more to event organizers, but if it is
being misunderstood and not used we can drop it.
--
Jody Garnett


On Thu, 14 Feb 2019 at 10:55, Markus Neteler  wrote:

> FYI: See below for great news!
>
>
> -- Forwarded message -----
> From: Jody Garnett 
> Date: Thu, Feb 14, 2019 at 7:52 PM
> Subject: [OSGeo-Discuss] osgeo budget 2019
> To: OSGeo Discussions 
>
>
> Gotten a couple folks asking for an update, the budget has indeed passed:
>
> https://wiki.osgeo.org/wiki/OSGeo_Budget_2019
>
> The vast majority of budget request have been met as requested, with
> the board scaling back some of its own activities, and combing events
> and code sprints to make this happen.
>
> For the details on how to work with your budget we have some draft
> being assembled here (TLDR: OSGeo trusts you, work with your committee
> officer, officer contacts the treasurer as needed).
>
> If you have questions please reply to this email thread, or contact a
> board member for clarification.
> --
> Jody Garnett
> ___
> 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
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

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

[Jody Garnett]

Jody here, think I am still on this list from a while back ...

Code sprint funding has seen a wide range of use at OSGeo:
- Catering / venue as Mortiz notes
- Travel / Accommodation
- Financial assistance to help folks attend
- Reduction in attendance fee (as proposed for Bolsena sprint this year)

Hunt through the wiki and board mailing list for example.
--
Jody Garnett


On Mon, 6 Jan 2020 at 03:57, Moritz Lennert 
wrote:

>
>
> Am 6. Januar 2020 12:50:12 MEZ schrieb Markus Neteler :
> >Hi PSC,
> >
> >Below the email which I had sent to the board.
> >However, we need to modify the request as code sprint support needs to
> >be requests separately from the general (current) request.
> >
> >Hence, I have separated out the sprint requests (to be submitted later
> >this year):
> >https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020#Planned_Expenses
> >
> >Now:
> >- please verify that the figures are right
>
> Sprint budget thus only includes catering and possibly some venue costs ?
>
> If that is the case, 2000 seems a lot, no ?
>
> Moritz
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc