EuroPython day 3

• Talk on templating: another Python backend application, mildly interesting
• JSON-RPC: only 3 methods in the protocol and extremelly simple object model (dictionary, aka JSON)
• Process in PyPy:
  • Key message: keep the scaffolding evolving, put it in place early to orient people, jettison it as soon as unecessary.
  • Some confusion I think between process and structure
• Users’ participation in the design process of Open Source Software communities: mostly an analysis of group dynamics in online conversations in the python project. Question to Chandler: how is our design structure helping or impending the evolution of Chandler? According to Flore, design is own by the users/participants. If that doesn't happen, the evolution may stall. Is our Chandler design process too highjacked by OSAF core staff?
• From agile development to agile evolution of enterprise systems
• Managing the Launchpad team at Canonical (Ubuntu): very similar to our own processes for meetings, etc... Potential ideas for OSAF:
  • Use the Sprints not to write code but to write specs for the next 6 months.
  • Define a "Keep, Bag, Change" list for each meeting to review (allow the processes to evolve in an ad-hoc fashion)
• Managing a distributed company: interesting though we actually have a much more complete and working system at OSAF...
• Agile customer management
• Personal note : I really need to write down my ideas on "Processes" and base a talk on it at the next PyCon or EuroPython

-- PhilippeBossut - 19 Jul 2006