User:Alsroot: Difference between revisions
No edit summary |
|||
| Line 36: | Line 36: | ||
* Timezone UTC | * Timezone UTC | ||
== | == TODO == | ||
=== Foreground tasks === | |||
* [[Platform_Team/Doers_environment/Implementation#Sweets_tracker|sweets-tracker]] to handle development implementations. | * [[Platform_Team/Doers_environment/Implementation#Sweets_tracker|sweets-tracker]] to handle development implementations. | ||
* review dextrose@ patches | * review dextrose@ patches | ||
* fix [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=keywords&col=status&col=type&col=priority&col=milestone&col=component&keywords=~dextrose dextrose bugs] | |||
=== Background tasks === | |||
* Maintain [[Service|SL services]] | |||
* Maintain [http://git.sugarlabs.org/search?q=user:alsroot sugar projects] | |||
== | === Current glucose cycle === | ||
* [[Platform_Team/Roadmap|Sweets Distribution 2011]] | * [[Platform_Team/Roadmap|Sweets Distribution 2011]] | ||
== | === Next glucose cycle === | ||
* First Polyol public release | * First Polyol public release | ||
* [http://far.no/fram/index.php?title=Fram FRAM] based activities | * [http://far.no/fram/index.php?title=Fram FRAM] based activities | ||
* libjounral/Library-2 entirely based on Polyol | * libjounral/Library-2 entirely based on Polyol | ||
* ActivityLibrary activity to replace existed shell (in case of managing activities) to support 0sugar | |||
* rainbow integration, having easy way to launch arbitrary blobs, security related issues are critical | * rainbow integration, having easy way to launch arbitrary blobs, security related issues are critical | ||
= | === In perspective === | ||
== In perspective == | |||
* Sugarize OOo4Kids | |||
** journal integration | |||
** OOo4Kids builds | |||
* Life in sugar! - support full time being online in sugar | * 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.) | ** 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.) | ||
Revision as of 03:20, 10 December 2010
Hi
A short bio:
| Name | Aleksey Lim |
| Birth | 1977 |
| Residence | Russia |
| Education | University college, USSR, 1994-1999, software developer |
| Career | 1999-2008, C/C++ developer for various commercial companies |
| 2008-2010, the first experience of being a FOSS contributor, full time Sugar Labs contributor and volunteer | |
| 2010-now, supported by Activity Central to help new sugar developers and support sugar projects |
Contacts
- Email me
- IRC nick alsroot
- Timezone UTC
TODO
Foreground tasks
- sweets-tracker to handle development implementations.
- review dextrose@ patches
- fix dextrose bugs
Background tasks
- Maintain SL services
- Maintain sugar projects
Current glucose cycle
Next glucose cycle
- First Polyol public release
- FRAM based activities
- libjounral/Library-2 entirely based on Polyol
- ActivityLibrary activity to replace existed shell (in case of managing activities) to support 0sugar
- rainbow integration, having easy way to launch arbitrary blobs, security related issues are critical
In perspective
- Sugarize OOo4Kids
- journal integration
- OOo4Kids builds
- 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)