Loomio
Wed 10 Oct 2018 12:35AM

Java 2018 Code Sprint Support

JG Jody Garnett Public Seen by 184

Request is for $2000 Sprint Support following code sprint guidelines for Java 2018 Code Sprint

The sprint is organized by OSGeo Java projects looking to coordinate activities around migration to Java 11. Due to the nature of the change (repackaging the projects into modules) this work is best done as a coordinated activity:

  • OSGeo projects: GeoServer, GeoNetwork, GeoTools
  • Community projects: GeoWebCache
  • Partner projects: JTS Topology Suite - completed migration and is offering technical assistance

The request is well within our 20k code sprint budget and is less then the guidance provided by the GeoServer team during budget planning.

Reference:
* Java 2018 Code Sprint
* Java 2018 Code Sprint Budget
* Code Sprint Guidelines

MAD

María Arias de Reyna Wed 10 Oct 2018 6:20AM

This is money coming from the budget planned per project, right?

JG

Jody Garnett Wed 10 Oct 2018 6:18PM

The code sprints have a separate budget:

We have asked project teams for guidance to help set our code sprint budget:
* please note our Code Sprint Guidelines ask for event details, budget and fundraising on your part.
* Code sprint funding is setup to help carry funds from one event to the next allowing us to hold more code-sprints with a smaller annual budget.
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required
* We had requests to fund sprints that were part of larger events, these escaped our 2017 planning but were still funded to the best of our abilities

OSGeo annual code sprint: 2000 - prior funding available
GeoServer: 3000
GeoTools: 4000 - request withdrawn, planned to send people to Bonn but that did not work out
GRASS: 3500
PostGIS: 2000
Small Code sprints: 10000

This left us with a total code sprint budget of 20500. I do not have an accurate accounting of what has been sprint thus far.

JG

Jody Garnett Wed 10 Oct 2018 6:19PM

The requested amount, 2000, is well within our budget for 2018 code sprints. And smaller than the initial guidance provided by the GeoServer and GeoTools teams.

MS

Poll Created Thu 11 Oct 2018 12:31AM

Fund Java Code Sprint for $2000 (usd) Closed Tue 16 Oct 2018 5:16AM

Outcome
by Jody Garnett Tue 16 Oct 2018 5:16AM

Motion approved

The sprint is organized by OSGeo Java projects looking to coordinate activities around migration to Java 11. Due to the nature of the change (repackaging the projects into modules) this work is best done as a coordinated activity.
Wiki: https://wiki.osgeo.org/wiki/Java_2018_Code_Sprint

Results

Results Option % of points Voters
Agree 88.9% 8 MS VC HM AT MAB MAD AE JM
Abstain 11.1% 1 JG
Disagree 0.0% 0  
Block 0.0% 0  
Undecided 0% 0  

9 of 9 people have participated (100%)

JG

Jody Garnett
Abstain
Thu 11 Oct 2018 1:06AM

I am part of the group requesting support

JM

Jeff McKenna
Agree
Sat 13 Oct 2018 10:21PM

I'm very glad to see the removal of the 'cost sharing' confusion, and that we as Board are just approving the funding to an important community sprint.

JG

Jody Garnett Fri 12 Oct 2018 7:25PM

Update: We have had 2-3 sponsors step forward which considerably reduce the financial risk associated with supporting this code sprint.

Indeed if the 3rd sponsorship comes through costs may be completely covered and this even will start to return a profit to the foundation.

JG

Jody Garnett Fri 12 Oct 2018 7:28PM

@michaelsmith7 the phrasing "fund" do not match the intent of the code sprint guidelines.

The code sprint process is designed to have OSGeo as host, rather than directly funding, these activities. In part so our projects can use OSGeo as bank account and legal entity, and so that any profit or loss is borne by the organization rather than individual volunteers.

If we can figure out a way to make this more clear it would be beneficial. Confusion these questions was one of the key takeaways from the community sprint at foss4g.

JG

Jody Garnett Mon 15 Oct 2018 3:21AM

Jeff can we agree that "host" is better than cost sharing? Approving funding does not quite match what we are trying to accomplish for code sprints.