Difference between revisions of "User:Alsroot"
Jump to navigation
Jump to search
(→Todo) |
|||
| Line 20: | Line 20: | ||
* Remove login necessity to download experimental activities from ASLO, recheck all ASLO workflows to treat experimental activities as regular ones (update-aslo.php etc) | * Remove login necessity to download experimental activities from ASLO, recheck all ASLO workflows to treat experimental activities as regular ones (update-aslo.php etc) | ||
* Renovate Library activity to meet its original purposes e.g. [http://thread.gmane.org/gmane.comp.education.sugar.discuss/7374/focus=7442] and support peer-to-peer sharing. | * Renovate Library activity to meet its original purposes e.g. [http://thread.gmane.org/gmane.comp.education.sugar.discuss/7374/focus=7442] and support peer-to-peer sharing. | ||
| − | |||
=== Long running === | === Long running === | ||
Revision as of 13:23, 29 June 2010
Hi
My name is Aleksey Lim, I am a volunteer for SugarLabs.
Roadmap
- Push Zero Sugar Activities idea
- Support 0sugar
- Package sugar for:
- ALT Linux
- Gentoo
- jhconvert distributions
- Maintain activities
- Maintain ASLO code base
Todo
- Build 0sugar packages on OBS
- Sugarize OO4Kids
- Remove login necessity to download experimental activities from ASLO, recheck all ASLO workflows to treat experimental activities as regular ones (update-aslo.php etc)
- Renovate Library activity to meet its original purposes e.g. [1] and support peer-to-peer sharing.
Long running
- Improve Polyol libraries.
- Encircle all packaging related stuff around sugar in one well designed packaging system - 0sugar:
- move packaging related code from glucose to 0sugar e.g. if there are two activity installations, one to /usr and one to ~/Activities, sugar decides what version is preferable, or what should happen if user removes activity. This is regular packaging work which should be moved to packaging system.
- extensive usage of centralized (native packaging systems like rpm or deb) and decentralized (0install) models
- patch 0install to support not read only usage of installed packages (some activities could be under development)
- Life in sugar! - support full time being online in sugar
- Sugar Daemons, all time beeing online servers that provide useful shared instances for broad collaboration e.g. Chat instances per purposes ("Ask your nub question", "How to hack sugar" etc.)
- Library instance via Sugar Daemon to provide server sharing model
- Сheck notification system in shell if it works well in "all time being in sugar" workflow
- Сreate Collab activity
- Collab instance via Sugar Daemon to have global collaboration portal for all sugar contributors/requesters.
Postponed
- put Saccharin distribution to usable state
Going further
- standalone mode for activities thus more close merge sugar with other education software e.g. ASLO could be not just portal of sugar activities but portal of education software(non-sugar users could run particular activity w/o need to install sugar)