Design Summit/Folsom/Unconference
Folsom Design Conference Open Space
Unconference
The keyword is participatory. That's what makes it different from the regular conference sessions - we're looking for sessions that really engage all the participants, be it in hands on exercises or vigorous dialogue.
Principles and Rule
- Whoever comes is the right people
- Whenever it starts is the right time
- Whatever happens is the only thing that could have
- When it's over, it's over
The only rule is The Law of Two Feet.
It says simply that you, and only you, know where you can learn and contribute the most to the work that must take place today. It demands that you use your two feet to go where you need to go and do what you need to do. If at any time today, you find that you are not learning or contributing, you have the right and the responsibility to move... find another breakout session, visit the food table, take a walk in the sunshine, make a phone call -- but DO NOT waste time.
Session Proposals
The actual sessions will be decided in the morning and after lunch each day starting after lunch Monday, but here is your chance to warm your fellow participants to to your proposal on an etherpad: http://etherpad.openstack.org/folsom-unconference-proposals
Schedule
Room is Golden Gate.
If there is no contention for the space, post the schedule here from http://etherpad.openstack.org/folsom-unconference-proposals . Otherwise, negotiate with the other people wanting the space in person.
Past
| Date | Title | Proposer | Description |
| 11:00am-12:30pm | Brainstorming ideas for PaaS (Reddwarf) | Nirmal Ranganathan/Michael Basnight | There's been a lot of talk about PaaS in general and several proposals. It would be nice to brainstorm ideas and come up with a solution to get it kickstarted in the community. The Reddwarf code base is already at a point where some of the basic features are implemented. We would like to propose to move this project with others interested in the community for the Folsom release. |
| 14:00 - 15:00 | Vote/Pick a name (needed for a repo) | Plan * Create new repo * Leverage/Contribute to Common everywhere possible * Export DB tables * Interface/API back in to compute * Use recent Glance work as model for client etc * Focus on migration of existing features and functionality nothing more, nothing less * Survey of volunteers/interested in working on different pieces |
