UbuntuFoodProductSpecification

Differences between revisions 1 and 4 (spanning 3 versions)
⇤ ← Revision 1 as of 2006-04-29 03:41:29 →
Size: 1655
Editor: 210
Comment: don't take this seriously :)
← Revision 4 as of 2006-04-29 15:19:25 → ⇥
Size: 2151
Editor: 125
Comment:
Deletions are marked like this. Additions are marked like this.
Line 19: Line 19:
They are very useful for release parties. Some obvious cases include: They would be very useful for release parties and distro sprints. During the Dapper development cycle, we have seen (and a select few got to taste):
Line 23: Line 23:
 * Ubuntu Soup - http://www.flickr.com/photos/13916877@N00/116406863/in/set-72057594113669601/
Line 24: Line 25:
 * Ubuntu BBQ Chicken - http://www.simplifiedcomplexity.com/images/ubuntu-bbq-chicken.png
  * Ubuntu BBQ Chicken - http://people.simplifiedcomplexity.com/~mgalvin/spring-is-in-the-air/
Line 34: Line 34:

We really need the people who posted their Ubuntu food to release the code under a free license.		  
 * Ingredients should be human-friendly
 * We need the people who posted their Ubuntu food to release the code under a OSI-approved license
 * We still have to consider if the license included would be edible too.
Line 40: Line 42:

Possibly we could open a global chain of Ubuntu Restaurants. Of course these would need to be opened close to our homes. Ubunteros run the risk of withdrawal if keep away from Ubuntu for to long.

Summary

During the Dapper development cycle, a flurry of Ubuntu-related food products came out from the community - must be a bad case of being overworked and overexposed to Ubuntu. Is it good or bad? Should we consider releasing a cookbook and package with the Edgy?

Rationale

Use cases

They would be very useful for release parties and distro sprints. During the Dapper development cycle, we have seen (and a select few got to taste):

Scope

Design

Implementation

Code

  • Ingredients should be human-friendly
  • We need the people who posted their Ubuntu food to release the code under a OSI-approved license
  • We still have to consider if the license included would be edible too.

Data preservation and migration

There's a big issue on how long these products will last when we start distributing it to hungry end-users. Obviously, someone ordering a soup from shipit won't wait for a month to have his soup fix. Shall we make it powereded instant or canned? Tetra pak or vaccum sealed? We also have to consider that most people expect their pizza to arrive in 20 minutes or else they won't pay for a cold one.

Possibly we could open a global chain of Ubuntu Restaurants. Of course these would need to be opened close to our homes. Ubunteros run the risk of withdrawal if keep away from Ubuntu for to long.

Outstanding issues

BoF agenda and discussion

CategorySpec

UbuntuFoodProductSpecification (last edited 2008-08-06 16:40:06 by localhost)