=== Pre Barcelona / Email / Phone Calls ===
Tech "Vision"
- What does p2pu need/should provide versus using what is already out there?
- How can we create a platform that forms the glue of p2pu but gives people the flexibility to integrate existing open web tools?
- What are the differentiating aspects of p2pu as a platform?
- Focus on the RIGHT features, not ALL features. (minimum viable product)
- create a platform that gives people freedom and flexibility to innovate/include their own solutions, but still feels integrated and like a community.
Site Architecture / Tech Details
- Stable site, easy to scale
- Easy to setup development environment
- the dreaded discussion - drupal, django, rails stone tablets...
- this should happen after the features and capabilities discussion, and should follow from it.
- Proper staging environment and QA
Find potential Tech Lead candidates
- Identify a few people who might be suitable to become P2PU Tech Lead (full-time) and invite them to Barcelona for (gentle) community vetting(eventually a paid gig?)
Discuss Tech Sprint Goals
- (What do we want to accomplish leading up to and during the tech sprint)
- Involve community in identifying relevant things to "build" during the tech sprint
Actions:
- Have a discussion about this on p2pu-dev
- Outcomes pre-barcelona: list of features/capabilities/key architectural details (to be reviewed and agreed upon in person?)
- review batacuda code/status and decide whether it's something that's ready for us to build on it
- Everyone to think about tech sprint participants that might be interested / available to take on full-time position
=== In Barcelona / Face to face workshop ===
- Discuss main changes/decisions and come to closure (er, or beginning) on them-- ie move from planning to action (hacking).
- Possible development/hacking focuses:
- Batucada Experiment - Build something that is immediately useful to P2PU
- Alternatively, see how much of a specific set of features we can re-implement in (say) django by just going nuts on it for 3 days.
Barcelona Outcomes:
Make it easier for other developers to hack / get involved (is this related to the dreaded discussion?)
- github repo
- regular irc channel/chat
- documentation on how to get involved
- documentation on whatever platform/features we are moving forward with
- regular sprint planning (adopt an informal agile development process?)
- might be difficult with volunteers, but regular techsprint events (remote) would be good