Stefano Fornari - Come creare e far crescere un progetto ed una community open source

1,705 views
1,611 views

Published on

Creare un software open source è molto di più che rendere scaricabile del codice sorgente. E' creare e alimentare una comunità fatta di utenti prima che di sviluppatori, che assieme contribuiscono a far progredire il prodotto innescando un circolo virtuoso tra le esigenze della comunità e quelle di un'azienda commerciale.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,705
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Stefano Fornari - Come creare e far crescere un progetto ed una community open source

  1. 1. Funambol & Open Source: creare e far crescere un progetto e una community Better Software Firenze 6-7 Maggio 2009 Stefano Fornari, Funambol CTO
  2. 2. Summary Today (the project, the company, the team) Funambol I – genesis of an open source project Funambol II – the project, the tools, the community Funambol III – the ecosystem
  3. 3. The company #1 cross-platform mobile open source company Headquartered in the US (Silicon Valley) Engineering team in Italy Sales presence in the US, Germany, Dubai, Beijing http://www.funambol.com A product company i.e. No consulting
  4. 4. Commercial deployment
  5. 5. Industry recognition
  6. 6. The product/1 “MobileMe” for the masses Client and server components Carrier grade server Many components Synchronization server Push server Inbox listener PIM listener
  7. 7. The product/2
  8. 8. The product/3 Multi platform clients WindowsMobile (smartphone & pocket PC) Win32/fat clients Symbian J2ME J2SE BlackBerry iPhone Android Mobile/Desktop linux An online portal (my.funambol.com)
  9. 9. The product/4 Licensing Dual license AGPL 3.0/commercial
  10. 10. The engineering team Based in Pavia Development team Pavia, Portugal QA team Pavia, Palermo, Portugal Product team chief architect, scrum master, technical writer, release eng, office manager Pavia
  11. 11. Funambol I
  12. 12. The Genesis - Sync4j Late 2002-early 2003 Motivations Do not reinvent the wheel Speed-up development Speed-up visibility Speed-up adoption Leading the space Think big, start small! Finding if there was any existing project Sharing idea with the owner Contributing code (patches, new code) Gaining trust and recognition Gaining write access to the repository Taking over project ownership and management
  13. 13. <250 250 – 2,500 2,500 – 10,000 10,000 – 25,000 25,000 – 50,000 >50,000
  14. 14. Funambol 2.0
  15. 15. Leading the project, starting a community Early 2004 More solid project Attracting interest in SyncML space Many implementations based on Project moved to the ObjectWeb consortium More visibility Become a player in encouraging open source adoption in business organizations Changed the name from Sync4j to Funambol Dual-licence Funambol Open Source Project Social Contract Making stronger and better use of community tools CVS, mailing lists, issue trackers, communication
  16. 16. Funambol 3.0
  17. 17. The ecosystem 3rd party Users developers Visible Stealth Mobile users System admins Core developers Funambol developers External developers
  18. 18. The ecosystem Hired a community manager Stefano Maffulli
  19. 19. The ecosystem Hired a community manager Funambol Forge http://forge.funambol.org
  20. 20. Forge: the place where the ecosystem meets Lifecycle and Subversion ,Task/Issue Tracking, Project Reporting Software Development Structured Mailing lists, Discussion Forums, Announcements, Document Collaboration Architecture of Portal, Wikis, Content Management, User Roles, Projec Community Participation
  21. 21. The ecosystem Hired a community manager Funambol Forge http://forge.funambol.org Code sniper
  22. 22. The ecosystem Hired a community manager Funambol Forge http://forge.funambol.org Code sniper Phone sniper
  23. 23. The ecosystem Community manager Funambol Forge http://forge.funambol.org Conversations http://identi.ca/group/funambol Irc.freenode.net #funambol Code sniper Device sniper Lion sniper
  24. 24. The ecosystem Community manager Roadmap Funambol Forge Backlog sharing http://forge.funambol.org Development plans sharing Code sniper Public design discussions Device sniper Public software metrics Lion sniper Transparency
  25. 25. The challenge Commercial vs Open Source development Commercial vs Open Source features Openness Shared Roadmap Development process integration
  26. 26. Questions?
  27. 27. The following slides are for further discussions
  28. 28. Open source development Contributions Core project
  29. 29. Funambol development community Contributors External developers Funambol developers
  30. 30. Funambol development community community projects connectors plug ins OEMs Contributors External developers Funambol developers core projects
  31. 31. Developers community core Funambol developers full time Funambol employees core developers committed developers owners of a module alone players or other companies' employees contributors 3rd party developers
  32. 32. Contributors and contributions contributors do not have write access to the code repository freely offered from developers to the community tracked in the bug tracking system reviewed by core developers accepted and integrated in the main trunk by core developers
  33. 33. core/3rd party development Funambol provides the framework and API 3rd parties develop independently Funambol offers the possibility to host the project on the Funambol forge forge.funambol.org community support core developers take care of the module they are owner

×