Talk:9.1.0 requirements

From OLPC
Revision as of 10:31, 24 September 2008 by Gregorio (talk | contribs)
Jump to: navigation, search

Comments from Michael on Technical Strategy section

As explained in detail here, I have serious problems with this statement of purpose. Come talk to me and let's work out better wording. --Michael Stone 23:54, 23 September 2008 (UTC)

Thanks for the comments

Thanks for the input on priorities. Good points! BTW please leave you name or pseudonym for future contact.

The top priority is "Stability". I'm not sure who gets the final say but that's my position and I haven't heard any dissenters yet.

Its not the kind of priority that you can call completely done. What I want to do is set a target (including a list of bugs) and get agreement on a definition of success.

In the mean time I think we need to continue making progress on the other Goals (not using "priority" :-) too....

BTW nice use of ascii art, I like it.


Gregorio 11:54, 23 September 2008 (UTC)

Words of Wisdom (regarding priorities)

\\//_ Priorities (pluralized) is an oxymoron. _\\//

\\//_ Two priorities is no priorities. _\\//

At any point in time, the team should have exactly one top priority. Each team member should focus on that one top priority, unless somehow blocked. The top priority will normally only change when something is substantially finished.

What is the #1 top priority for 9.1.0 right now ?

(Who chooses the #1 top priority?)

Top Priority candidates for 9.1.0

  • new datastore
  • new filesystem to replace jffs2 (or make jffs2 work better?)
  • system security
  • performance
  • reliability
  • document existing stuff
  • document future stuff
  • new features
  • fix known bugs
  • software update tools
  • identify, attract, or acquire development resources
  • remove impediments to progress
  • reduce memory footprint
  • reduce work-in-progress
  • take out the garbage; clean up the house; improve the work environment

Choose a top priority that has few blockers, a high probability of success, that contributes to short-term and long-term survival, that will ultimately make many customers happy, and that makes the next successor priority easier to accomplish.