UbuntuFoodProductSpecification
Note: This is just for laughs (hopefully)
Launchpad Entry: https://launchpad.net/distros/ubuntu/+spec/foo
Created: 2006-04-29 by JeromeGotangco
People: NeedsLead, NeedsSecond
Contributors:
Packages affected:
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):
Ubuntu Cakes - http://jonathancarter.co.za/?p=20
Ubuntu Pizza - http://thomas.holba.ch/?p=83
Ubuntu Soup - http://janewsblog.blogspot.com/2006/03/ubuntu-is-soup-er.html
Ubuntu eggs and hot bun - http://janewsblog.blogspot.com/2006/04/more-ubuntu-food.html
Ubuntu BBQ Chicken - http://people.simplifiedcomplexity.com/~mgalvin/spring-is-in-the-air/
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
UbuntuFoodProductSpecification (last edited 2008-08-06 16:40:06 by localhost)