1 Cooperation in development of Open Source Software

2 Background • Software developed by NSIs under commercial licensing terms – PC-Axis, Blaise

3 Cooperation within some defined frames Well defined Statistical Business Process Model Service Oriented

4 Cooperation within some defined frames Well defined Statistical Business Process Model Service Oriented

5 Open Source Community • Decide upon software development strategy and • • •

6 Open Source Community - responsibility • Establish ownership/ • partnership, sufficiently anchored within

7 OSS Community Interested parties Funding Partner(s) Contributions Consortium committee Services Repository Development Team

8 The 10 roles in OSS development teams • Developers (Coders) • Packagers (Install,

9 Legal aspects • Decide upon type of F/OSS Licence – – GPL, EUPL,

10 Other aspects • End user administration • Marketing • Should be self-financed

11 Funding • First time development must always • • • get targeted funds

Slides: 11

Download presentation

1 Cooperation in development of Open Source Software MSIS meeting in Oslo 18 -20 May 2009 Rune Gløersen IT Director Statistics Norway

2 Background • Software developed by NSIs under commercial licensing terms – PC-Axis, Blaise etc • Vulnerable to strategic • changes in the NSIs Success becomes costly • What should be considered when moving to OSS ?

3 Cooperation within some defined frames Well defined Statistical Business Process Model Service Oriented IT Architecture Cooperative development, adoption of CBMs and reuse of software Harmonised Information Architecture

4 Cooperation within some defined frames Well defined Statistical Business Process Model Service Oriented IT Architecture Open Source Community Development and Maintenance Harmonised Information Architecture

5 Open Source Community • Decide upon software development strategy and • • • cooperation Establish organisation Decide upon type of F/OSS Licence Involvement of commercial companies End user administration Marketing Funding

6 Open Source Community - responsibility • Establish ownership/ • partnership, sufficiently anchored within the participating organisations Establish organisation – – Development team (roles) Maintenance team (roles) Ownership and commitment Repository (Eurostat OSOR…)

7 OSS Community Interested parties Funding Partner(s) Contributions Consortium committee Services Repository Development Team Maintenance Team OSS End users

8 The 10 roles in OSS development teams • Developers (Coders) • Packagers (Install, integrate) • Artists (Graphical interfaces) • Documentation writers • Testers (Beta, …) • Translators • Support technicians • Marketing advocates • Users…. • Infrastructure providers (repositories etc)

9 Legal aspects • Decide upon type of F/OSS Licence – – GPL, EUPL, … (Copyleft) BSD, MIT, (derive as you like) Dual License (OSS and commercial) Differentiated licensing (GPL, LGPL) • NSIs position fits well with the • objectives for OSS Prepare for added value from commercial business – Contributors – Integrators – Value-added services

10 Other aspects • End user administration • Marketing • Should be self-financed

11 Funding • First time development must always • • • get targeted funds You need a success to establish a commercial product A roaring success becomes increasingly costly If you succeed to gain momentum, OSS will start to pay off – Contributions