Difference between revisions of "User:Alsroot"
Jump to navigation
Jump to search
| Line 25: | Line 25: | ||
# GNU/Linux distribution part, build activities and their dependencies on OBS using 0sugar.info spec file | # GNU/Linux distribution part, build activities and their dependencies on OBS using 0sugar.info spec file | ||
# 0install part, compose 0isntall feeds using 0sugar.info spec file and use packages built on OBS as feeds implementations | # 0install part, compose 0isntall feeds using 0sugar.info spec file and use packages built on OBS as feeds implementations | ||
| − | # sugar part, collect all packaging related code in packaging core (could be dbus service) | + | # sugar part, collect all packaging related code in packaging core (could be dbus service) |
| + | ## sugar shell will just ask packaging core to get list of all activities in the system (installed from native packages, via 0install, just placed to ~/Activities) or to launch particular activity by its id (packaging core will check what dependencies should be installed/downloaded and what sources to use, native packages or 0install) | ||
| + | ## rainbow integration, having easy way to launch arbitrary blobs, security related issues are critical | ||
* ActivityLibrary activity to replace existed shell (in case of managing activities) to support 0sugar | * ActivityLibrary activity to replace existed shell (in case of managing activities) to support 0sugar | ||
Revision as of 07:56, 30 June 2010
Hi
My name is Aleksey Lim, I am a volunteer for SugarLabs.
Short time tasks queue
- Build 0sugar packages on OBS
- build GC in major distros on OBS
- ASLO redesign
- per arch/locale uploads
- no experimental activities by default
- microformat support
- Sugarize OOo4Kids
- journal integration
- OOo4Kids builds
- libjounral/Library-2 entirely based on Polyol
- First Polyol public release
Long time tasks queue
- Improve Polyol libraries.
- Encircle all packaging related stuff within sugar in one well designed packaging system, 0sugar:
- GNU/Linux distribution part, build activities and their dependencies on OBS using 0sugar.info spec file
- 0install part, compose 0isntall feeds using 0sugar.info spec file and use packages built on OBS as feeds implementations
- sugar part, collect all packaging related code in packaging core (could be dbus service)
- sugar shell will just ask packaging core to get list of all activities in the system (installed from native packages, via 0install, just placed to ~/Activities) or to launch particular activity by its id (packaging core will check what dependencies should be installed/downloaded and what sources to use, native packages or 0install)
- rainbow integration, having easy way to launch arbitrary blobs, security related issues are critical
- ActivityLibrary activity to replace existed shell (in case of managing activities) to support 0sugar
Every day background tasks
- Maintain ASLO code base
- Sucrose packaging for:
- Gentoo overlay
- ALT Linux
- Mandriva
- openSUSE
- Maintain code for:
- tuxpaint
- speak
- flipsticks
- cartoon-builder
- gst-plugins-espeak
- gcompris
- Maintain orphaned activities:
- tamtam
- joke-machine
- jigsaw-puzzle
- slider-puzzle
- story-builder
In perspective
- 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.
- 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)