Learning, describing, tooling "The Eclipse way".
From closed to open – not only regarding OS, but also direct interaction with the dev team.
Project gives community and vice versa. "Village Effect" create accountability without blaming others. Transparency – who does what. Continuity (?) => continuous health.
Mindmap of Eclipse practices ###get###
Organizational Patterns of Agile SW Dev / Coplien ###get###
Bugzilla Pivotgraph demo.
EPF examples. Bottom-down-and-up-collaboration;
Process/practice awareness: Instead of writing documentation help on the tool level.First products 2 b released in 2008. "Open commercial" software – seems that Jazz’ll be fully commercial (hm, maybe as commercial as EPF is considering the "RUP composer").
Jazz overview. Team first – codesharing.
Finally we can see something – after a long time of waiting (since http://portal.acm.org/citation.cfm?id=965670&coll=portal&dl=ACM&CFID=21208174&CFTOKEN=43773194 I’m eager to see more) there’s a clear concept. If I understood it correctly, the tool-suite shall only be released commercially 😐
I hope this can be understood in the sense of never giving Eclipse for free or the RUP composer… I assume, there’ll be connectors to Lotus or Rational stuff – hope this’ll be a separate commercial part.
The vision I understood was this: One can design a collaborative process within EPF and apply it to Jazz-enabled IDEs in the way that it ensures that the developers stick to the process. This would work – plain documentation not.