From Fedora Project Wiki
(all that I captured, I wasn't taking much notes compared to listening) |
(adding and sub-sectioning resources) |
||
| Line 21: | Line 21: | ||
== Resources == | == Resources == | ||
=== Slides from talk === | |||
http://lmacken.fedorapeople.org/moksha.odp | |||
=== Notes from talk === | |||
http://lmacken.fedorapeople.org/moksha | |||
=== Design and demo examples === | |||
http://johnp.fedorapeople.org/fedora-community/ | |||
=== Upstream === | |||
http://fedorahosted.org/moksha | |||
[[Category:FUDConF11]] | [[Category:FUDConF11]] | ||
[[Category:FUDCon BarCamp notes]] | [[Category:FUDCon BarCamp notes]] | ||
Revision as of 18:41, 10 January 2009
What is the problem?
Lots of good Fedora services that all act differently.
The MyFedora team ran in to complexity problems, writing code specific to Fedora.
What is Moksha?
Tool for making collaborative dashboards of widgets from existing social services and applications.
What does Moksha solve?
Many, many cool things. (Raw notes from quaid 16:56, 10 January 2009 (UTC))
- Data persistence
- Scalability. Extensive caching; each app deployed has its own sqlite dbase on disk, setup by Moksha automatically.
- Everything can be replicated and made redundant (clustered, etc.)
- WSGI middleware stack
Resources
Slides from talk
http://lmacken.fedorapeople.org/moksha.odp
Notes from talk
http://lmacken.fedorapeople.org/moksha
Design and demo examples
http://johnp.fedorapeople.org/fedora-community/