OW2 has traditionally provided an infrastructure based on Subversion and GForge. However, software development is evolving toward a more distributed, social, flexible, and lean process. This talk presents how OW2 is embracing this new trend and the new tools and possibilities offered for your OW2 project.
5. GForge
● Objectweb was a forerunner
○ All in one integrated solution
■ CVS and a Web view
■ Bug Tracker
■ File management
■ Syndication
■ Mailing list
■ Role management
○ LDAP management
6. Up to now
● GForge enhancement
○ Moved from CVS to SVN
○ JSPWiki
● Progressive integration:
○ JIRA, Bamboo, Fisheye
○ XWiki
○ Gitorious
○ Nexus
○ Jabber
7. So far, so good
● Centralized workflow
○ I work in my place and commit to the reference
○ Project team is clearly defined
● But
○ Tools are scattered all around the place
■ Management became difficult
○ Tools are not unified (but sometimes are)
■ Multiple user account to manage
○ Contribution Wall too high
10. Development is going "social"
● Introduction of DVCS
○ Git / Mercurial
○ Everyone has the source repository at home
○ Everyone can become the reference point
○ There can even be multiple "trusted" references
○ Workflow schema is open
11. Development is going "social"
● Clone / Fork
○ Fork is no more a swear word
○ More clone is better, means more contributors
○ Contribution re-integration (merge) is super easy
12. Development is going "social"
● Merge / Pull Requests
○ Working in isolation is great, but sharing is the final
objective
○ Mean of contributing back without losing control or
credit
13. Everyone wants to be friends
● Twitter / Facebook
○ Individually subscribe to sources of interest (other
devs, ...)
● Recent tools incorporates a social aspect
○ Follow someone in a Wiki and be notified when
he/she changes a page
○ Follow diverse activities
● There is no community, there are
communities