Participants, please comment directly by editing this page.
JB: I suggest the following formats
T=Talk (Practical Code Knowledge): One person gives informative overview and points to relevant source code, followed/interrupted by time slots to look up and read the code.
Brainstorm: One person presents ideas (slides, black/white board, ???) about future features and development, and is chairing a discussion round afterwards. After discussion, results have to be fixed in keywords, within 5 minutes.
Pair Programming: groups of 2 read and write code, focus on one particular aspect
Snapshot: <5 minute for reporting results of hacking sessions to the group
Individual setup on arrival
T:Jumpstart session: repository and build setup, Debugging
?Vladimir? / Jost
T:Overview of the Implementation Structure, Eden parts