User:Mstone/Rainflow: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 5: | Line 5: | ||
== Background == |
== Background == |
||
People have been concerned with this question (and with variants and related questions) for some time: |
People in the OLPC community have been concerned with this question (and with variants and related questions) for some time: |
||
: <trac>5657</trac>, on spoofing-resistant update algorithms for de-isolated activities |
: <trac>5657</trac>, on spoofing-resistant update algorithms for de-isolated activities |
||
| Line 15: | Line 15: | ||
: [[Bundles and updates|homunq's ideas on bundles and updates]] |
: [[Bundles and updates|homunq's ideas on bundles and updates]] |
||
Most likely, others have shared analogous concerns in their environments: |
|||
the devil is truly in the details. |
|||
: ''citations needed'' |
|||
This proposal offers some new details for adventurous devil-spotters to peruse. |
|||
Consequently, here's an attempt at details. |
|||
Revision as of 20:20, 29 May 2009
Carrying on the tradition of naming software via puns, I'll lay down some thoughts on how to answer the question:
- When should our software automatically do risky thing X?
Background
People in the OLPC community have been concerned with this question (and with variants and related questions) for some time:
- <trac>5657</trac>, on spoofing-resistant update algorithms for de-isolated activities
- questions on activity signing and update thread
- activity semantics conversation
- runtime build customization thread and <trac>6432</trac>
- user-created activities and updates thread
- horizontal distribution thread
- homunq's ideas on bundles and updates
Most likely, others have shared analogous concerns in their environments:
- citations needed
This proposal offers some new details for adventurous devil-spotters to peruse.