Java 2018 Code Sprint Budget
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

Comment only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
This budget is for Java 2018 Code Sprint
2
The information here is requested by the requested by the OSGeo Code_Sprint_Guidelines.
3
4
Basic Information
5
Audience:
10-15 people are expected, less then this and the planned activity may not work
6
Region/Location:VictoriaCanada
Boundless supplied venue, local billetting available to reduce costs
7
EpsomUK
Astun Office in Epsom, UK several point are gathering there
Q: Address? A: 17 West St, Epsom KT18 7RL, UK
8
SevillaSpain
Trying to find a free place, not confirmed yet
9
Projects:GeoServerOSGeo Project
10
GeoToolsOSGeo Project
11
GeoNetworkOSGeo Project
12
GeoWebCacheOSGeo Community
13
JTS Topology Suite
LocationTech Project
14
When:October 22-26th
15
16
17
18
Financials
19
Financials:
This event looks is taking steps to run a low cost (given lack of sponsors stepping forward)
20
If any profits are generated they would be returned to OSGeo for future code sprints.
21
Request:
GeoTools PSC requests $1000
GeoTools Budget Request 2018
TLDR: $1500 support bonn code sprint attendence unused, $1500 code sprint guidence.
22
GeoServer PSC request $1000
OSGeo 2018 Budget
TLDR: $3000 code sprint guidence
23
24
Loss:
This event will not occur a loss if unable to raise funds, we will just have less people (putting the activity at risk)
25
26
Attendees booking prior to approval are taking a personal risk with full understanding
sprint organizers may not be in position to assist with travel costs.
27
28
Risk:
Based on the above statement, financial risk is be assumed by attendees :(

We are aware of the risk and are a responsible project team planning out sprint activities prior
to the event (evaluating technical risk, choosing an appropriate sized task, completing change proposals,
and recruiting appropriate attendees for the activity).
29
Due to the nature of this event there is a set goal to be successful.
And a stretch goal:
30
- GeoServer able to run in a Java 11 environment, documenting the environment required
Refactored into non-conflicting packages, with automatic module name supplied.
31
- GeoNetwork as above
32
- GeoWebCache as above
Refactored into non-conflicting packages, with automatic module name supplied.
33
- GeoTools refactor into non-conflicting packages, with automatic module name supplied
Quickstart runnable as a Java 11 module
34
- JTS support above projects during migration to Java 11
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
Main menu