1. Building a better, global product
with the community
OLIVIER DONY
@odony

2. Agenda
 Community Facts
 New Community Tools
 Main Contribution Processes
 Translations
 Bug reports
 Bug fixes and improvements
 New features – new modules
 Localizations
@odony

3. Community Facts
// SOME INSIGHTFUL FIGURES…

4. Top Visiting Countries
#1 France / India (300k)
#2 Spain / USA (200k)
#3 Germany (150k)
#4 Belgium (140k)
#5 Morocco (130k)
www.openerp.com visits
4 million visits per year
2 million unique visitors, 50% new

5. Community Facts (Q1 2012)
2,781 3,760
3,942,979 2,002
17,132 42
@odony

6. Community Facts (Q1 2012)
2,781 3,760
@OpenERP followers
Registered Contributors
3,942,979 2,002
Yearly Web Visitors OpenERP Apps
17,132 42
Forum Users Translation Teams
@odony

7. Daily Community Feedback
@odony

8. How did we do in 2011?
@odony

9. How did we do in 2011?
 4,200 bug/suggestion reports
 ~20 bug reports/business day
 2,200 code reviews (merge proposals)
 20 new translation teams assigned
 ~340,000 total translation terms maintained
 One full OpenERP translation = 18,700 terms (340k=18x)
 30 standard localization modules maintained
Imagine the massive amount of work!
@odony

10. How do those numbers compare?
OpenERP Rails Launchpad Chromium
(Launchpad) (GitHub) (Launchpad) (GoogleCode)
Branches /
Forks 7,860 3,019 9,609
Issues (-1y) 4,200 5,500 3,000 9,372
Contributors
/ 2,780 13,980 4,124
Followers
@odony

11. This powerful force gives an
incredible boost to product
maturity
(if properly harnessed)
@odony

12. Why does it work?
@odony

13. Why does it work?
 Unique business model
 Balanced roles
 Community
 Partners
 Customers
 Editor
 Each works on what is
critical for them
 Each role works on what
others cannot work on
@odony

14. Community Tools
// NEW AND NOTEWORTHY…

15. OpenERP Apps
Apps library
o Tracks changes
o Global visibility
o Top Contributors
o Extra-addons
Future
o Rating system
o Better UI
o Better integration

16. Publish your work!
1. Upload your work in your own LP branch
2. Be sure to include description and screenshots
3. On apps.openerp.com, click on “Register branch”
4. Check format requirements, choose a version
5. Done!
Your modules are automatically tracked and published
as they evolve, and visible to the whole community
@odony

17. Runbot
 Monitors branches
 Automated test suite
 Coverage reports
 Live testing
runbot.openerp.com
@odony

18. Runbot
 Partners can register
their own branches!
 Access via Partner Portal
runbot.openerp.com
openerp.my.openerp.com
runbot.openerp.com
@odony

19. Nightly Builds
 Day+1 access to bugfixes
 Same packages as releases
 Same value as minor versions
(e.g. 6.0.3)
 Will actually replace minor
versions in the future
nightly.openerp.com
@odony

20. Main Contribution Processes
// HOW IT WORKS…

21. Translations
 Translate online
 Shared suggestions
 Automatic sync
 40+ languages
 Language inheritance
 3 projects
 ~18000 terms in total
@odony

22. Translations
 Teamwork!
 Guidelines
 Glossary
 Community suggestions
 Regular reviews
@odony

23. Bug Reports
 R&D team fixes trunk
 OpenERP Enterprise team fixes stable
 Requirements and results are different
 Resources are different
 Funding is different
@odony

24. Bug Reports
 R&D team fixes trunk
 Report on Launchpad
 Wait for bug triage (1-2 days, best effort)
 Test fix live on Runbot
 Grab nightly build
 OpenERP Enterprise team fixes stable
 Report via OpenERP Enterprise maintenance
 Wait for feedback (guaranteed, depending on plan)
 Test fix live on Runbot
 Grab nightly build
@odony

25. Bug Reports
http://runbot.openerp.com
@odony

26. Patches // Improvements
 Typical merge proposals:
 Improvements for the official addons
 Bug corrections
 Modules that are required in certain countries
 Other new features:
 Should live in a separate module to respect modular design
 Publish them on OpenERP Apps!
@odony

27. Patches // Improvements
@odony

28. New Features // New Modules
 Invaluable advantage of OpenERP: the number of
community modules!
 Combine efforts with other community members
 Possibly create your own LP projects to benefit from
bug tracking, translations, etc.
 Did I mention? Please publish your work!
@odony

29. Localizations // Chart of Accounts
 l10n_xx module contents:  No business logic code
 Chart(s) of Accounts (*) (almost)
 Account types  Considered “required”
 Accounts
 Bootstrap with an
 Chart(s) of Taxes (*) existing one (e.g.
 Taxcodes
l10n_be)
 Taxes
 Fiscal positions
 Specific legal reports
 Banking import/export
interfaces
@odony

30. Thanks for your contributions!
 2012: we continue improving contribution processes
 Merge proposals should be reviewed in real time
 You can help by reviewing others’ work!
 Join us on the community channels (mailing-lists,
LP answers, forum, IRC)
@odony

31. Will happily explain in more details and
discuss this with you, join me in the
Meet OpenERP Track – AZ1.101
@odony