Labs/Bespin/Roadmap/Reboot

Bespin Reboot 2009

We have a new project to reboot Bespin, building on the knowledge that we have gained from the experiment so far. The goal is to allow us to build a solid foundation for the community at large to build on.

We have a different schedule for the reboot, which is:

• Weekly meetings, building to in person week
  • September 4th; flushing out the high level goals
  • September 11th
  • September 18th
  • September 25th
• In person: Week of Sept 28th
  • Bringing in consultant to help build on SproutCore
  • Use the week to decide if SproutCore Is It

High level principles for Bespin

What are the guiding principles for Bespin?

• Platform for developer tools
• Embedded component is a first class citizen
• Provide a fantastic editor user experience

What are un-goals?

• Provide a UI toolkit
• Use canvas
• Be everything to everyone

What are tactical things we want to fix?

What have we learned from Bespin that we don't want to mimic:

• Use a framework
• Events are great, but not too many
• One system for keyboard handling
• Embedded component must be a first class citizen else it gets left behind
• Tests, tests, tests
• Prototypes, prototypes, prototypes
• Plugins, plugins, plugins
• Documentation, ...

What is our software developer process?

• How do we do design?
• How do we work together?
• How do we prototype?

How do we work with the community?

• How are we inclusive?
• How do we deal with contributions?
• How do we reward the community?
• How do we grow the community?