Roadmap for Community Building Granada, 12th January 2012

Transcription

1 Miguel Jaque Barbero Managing

2 Contents 01. About CENATIC 02. How Public Admins come to Open Source 03. CENATIC's Role 04. How to Build OS Communities

3 About CENATIC CENATIC is the Spanish National Competency Centre for Open Source Applications Public Foundation, Created in 2006, By Ministry of Industry, Energy and Tourism and the Government of Extremadura. 3

4

5 How Public Administrations Come to Open Source 5

6 First Step: ReUse 6

7 Reusing Software 1. FINDING Free Licenses Quick Acquisition High Quality Software Competitive Providers Community Support Budget Problems Free Software 2. SEEKING Learn about Open Source Ask for Open Source in next Tenders Look for Reusable Software in: Other Public Admins Public Forges 7

8 Second Step: Share 8

9 Sharing Software Where does it come from? 1. P2P Sharing your software with other public admins. 2. LIBERATION Making your software freely available. 9

10 Third Step: Collaborate 10

11 Collaborating with Software It's not my software. It's our software Create a Community to: Share Maintenance Costs Share Development Efforts Evolve Quicker Enhance Interoperability Accelerate Diffusion. 11

12 CENATIC's Role 12

13

14 Community Building 14

15 Steps in Community Building 1. Analyse the Ecosystem To identify who may be interested in participating and why. Look for users, service providers, related projects... Do SWOT Analysis to know Strengths, Weakness, Opportunity and Threats. 2. Plan your Community Design a feasible plan. Mind finance, government, technical evolution, IP management, quality control, marketing Execute your Plan Success is 10% planning, 90% execution. Get a Community Manager! Avoid known Community Anti-patterns. 15

16 Community Plan for Public Admin OS Community A Community Plan must include: Strategic Roadmap Governance Model Distribution Policy and IP Management Marketing/Diffusion Plan Knowledge Transfer Plan Community Tools Financial Model Strategy Strategy Governance Governance IP IP Marketing Marketing Knowledge Knowledge Tools Tools Finance Finance 16

17 Strategic Roadmap Identify Community Objectives. What are the interests for: Developers Companies Collaborating Projects Participating Institutions Design a Technological Path for Evolution. Which features will the software include. 17

18 Governance Model Define Decision Processes, Roles and Committees. You need: Clear Organizational Model Participation and Transparency Voting Rules Technical and Release Rules Define other Institutions Roles Metrics to Track Progress and Health. 18

19 Distribution Policy and IP Management Define Who Owns the Code. How Contributions are Accepted. Manage Intellectual Property. 19

20 Marketing Plan How Will Users Know About the Software. Design your Web/Forge Choose Social Channels Plan Events 20

21 Knowledge Transfer How Will New Participants Collaborate with the Community. Design Web Materials Plan Trainings Design Certification Programs Publish a Demo 21

22 Community Tools Choose the Collaborating Tools for the Community. Web Forge Wiki Mailing Lists Forums Define How they Will be Used. 22

23 Financial Plan Where Will Resources Come From. We need money and we need people. Budget Public-Private Collaboration Universities 23

24 Summary 1. Analyse the Ecosystem 2. Plan your Community - Define Strategic Roadmap. What the Objectives? - Design Governance Model. Who Decides What? - Define Distribution Policy. Who Owns the Code? - Design a Marketing Plan. How will Users Know About? - Design Knowledge Transfer. How will Participants Join? - Choose the Tools. How will Participants Collaborate? - Design a Financial Plan. How are We Paying the Bill? 3. Execute your Plan 24

25 Thanks

26