Line 1: |
Line 1: |
− | {{TeamHeader|Platform Team}} | + | <noinclude>{{TeamHeader|Platform Team}}[[Category:Roadmap]]</noinclude> |
| | | |
| + | == Releasing schedules == |
| | | |
− | {| cellpadding="10" cellspacing="0" border="1" | + | * [[Platform_Team/Sweets/1.1|Sweets]] |
− | !Date
| + | |
− | !Task
| + | ==== Activity Library ==== |
− | !Notes
| + | |
− | |- | + | {| class="wikitable" border="1" |
− | |2010-12-31 | + | |-k |
− | |sweets-tracker-1 | + | ! scope="col" | '''Deadline''' |
− | |Full functional (except sharing), sweets-tracker. | + | ! scope="col" | '''Closed''' |
− | |-
| + | ! scope="col" | '''Notes''' |
− | |2011-01-31
| |
− | |Bazaar-1
| |
− | |Initial version of OBS Web UI, adapted to sweets' needs. 0install support in OBS backend.
| |
− | |-
| |
− | |2011-02-28
| |
− | |ASLO-5
| |
− | |Migrate to new AMO code base and implement initial support of OBS Web UI as an additional AMO DevHub.
| |
| |- | | |- |
− | |2011-04-06 | + | |''postponed'' |
− | |Sweets Distribution 2011 | + | | |
− | |[[Platform_Team/Doers_environment|sweets]] initial ready-to-use release. | + | |ASLO-5, Migrate ASLO to the new AMO code base. SDK initial support.<br> |
| + | Migration is postponed until upstream implement features ASLO needs, see the [https://spreadsheets.google.com/ccc?key=0AgX-nlaDaTaBdGhVd3ZlU1ZySWRiNmZ4YmgxTkV6ZlE&hl=en#gid=0 migration progress] (green lines are parts that work on new AMO). |
| |- | | |- |
| |} | | |} |
| + | |
| + | == Shot-term goals == |
| + | |
| + | * Activity Library related tasks: |
| + | ** polish the [[Activity_Library/Editors/Policy|Policy]] (work with [[Education Team]] on an initial Policy), |
| + | ** start discussion on MLs, |
| + | ** land it. |
| + | |
| + | == Medium-term goals == |
| + | |
| + | * Work with [[Infrastructure Team]] on the Central Login system to make it possible to be logged in only once while browsing Sugar Labs resources. |
| + | * Develop an infrastructure to share logs on activity fails. |
| + | * Develop an infrastructure to share anonymous usage statistics on Sugar Labs level, i.e., not only for particular deployment. |
| + | * See around for ways how Sugar objects (Journal objects, .xol, etc) might be shared. |
| + | |
| + | == Long-term goals == |
| + | |
| + | * The entirely Platform Team infrastructure should mature to be used in production mode on regular basis. |
| + | |
| + | == Status == |
| + | {{Iframe|collapsed=collapsed|'''2011 September report:''' |http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg12349.html |
| + | |740|1820|1}} |
| + | |
| + | == Constraints == |
| + | |
| + | The most [non-technical] critical constraints related to the Activity Library are a lack of editors and the fact that all active editors are software technology people. In other words, it would be useful to have a common strategy, created in cooperation with the Education Team, that covers such important resources as the [[Activity Library]]. And, eventually having educators as Activity Library editors. |
| + | |
| + | == Proposals == |
| + | |
| + | * [http://far.no/fram/index.php?title=Fram FRAM] based activities on the Sugar Labs wiki. |
| + | * [[Platform_Team/Polyol|polyol]] as a sugar-toolkit for non-Python activities. |