Open Source Geospatial Foundation (OSGeo) How things work OpenWIS Association March 2016 Open Source Geospatial Foundation (OSGeo) How things work Bruce Bannerman a/Data Director – Australian Bureau of Meteorology Charter Member – OSGeo Member – OSGeo Incubation Committee

OSGeo Not For Profit organisation Vision: Empower everyone with open source geospatial Mission Foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development The foundation's projects are all freely available and useable under an Open Source Initiative certified open source license 2

OSGeo Projects 3

OSGeo Committees 4

How are things done? By the principle of Meritocracy: A society governed by people selected according to merit Oxford Dictionary the more you do, the more that you’re able to do Most communication via email lists Annual ‘gathering of the tribes’ FOSS4G conference 5

Categories of Membership Participant No voting rights Member Self-declared on OSGeo wiki May vote on OSGeo Committee issues Charter Member Must be nominated and voted in by other Charter Members By merit Can vote in elections for: Charter Members Board Members 6

OSGeo Incubation Purpose to ensure that projects that are officially part of OSGeo: have a successfully operating open and collaborative development community have clear IP oversight of the code base of the project adopt the OSGeo principles and operating principles are mentored through the incubation process 7

OSGeo Incubation Principles – ‘the OSGeo way’ Projects should manage themselves, striving for consensus and encouraging participation from all contributors - from beginning users to advanced developers Contributors are the scarce resource and successful projects court and encourage them Projects are encouraged to adopt open standards and collaborate with other OSGeo projects Projects are responsible for reviewing and controlling their code bases to insure the integrity of the open source baselines. 8

OSGeo Incubation Operating Principles Projects should: document how they manage themselves maintain developer and user documentation maintain a source code management system maintain an issue tracking system maintain project mailing lists actively promote their participation in OSGeo have automated build and smoke test systems Projects are encouraged to: adopt OSGeo look and feel, branding, logos on their project sites participate in OSGeo standardisation efforts to present a common interface for OSGeo visitors and members 9

OSGeo Incubation Graduation Checklist Open: The project has demonstrated that it has an open, active and healthy user and developer community Projects are expected to function in an open and public manner and including: Open source license(s) Open communication channels Open decision making process 10

OSGeo Incubation Graduation Checklist Active and healthy community: The project should have a community of developers and users who actively collaborate and support each other in a healthy way Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations: Resilient enough to sustain loss of key developers or sustaining organisation Decisions made openly, not behind closed doors All participants empowered to take ownership of project 11

OSGeo Incubation Graduation Checklist Copyright and License: All source code available under an open source license All documentation available under open document license, e.g. CC Provenance review to adequately examine source code Project maintains: list of all copyright and IP holders signed contributor agreements 12

OSGeo Incubation Graduation Checklist Processes: All source code and configuration managed under source code repository, e.g. git Uses Issue Tracker and issues are up to date Management processes are adequately documented Developers Guide, Code Style Guide etc Open Project governance processes Public communications processes for decision making 13

OSGeo Incubation Graduation Checklist Documentation: User Documentation Developer Documentation 14

OSGeo Incubation Graduation Checklist Release Process: Follows defined Release Process Including execution of Testing Process prior to Stable Release Follows documented Testing Process Automated and manual testing Documented conformance to set quality goals percentage code coverage of Unit Tests Release and Testing process have sufficient detail for senior developer to follow Software ideally packaged for deployment (RPM, .deb etc) 15

www.osgeo.org