Platform Team/Roadmap: Difference between revisions

No edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 3: Line 3:
== Releasing schedules ==
== Releasing schedules ==


==== Sweets ====
* [[Platform_Team/Sweets/1.1|Sweets]]
 
{| class="wikitable" border="1"
|-
! scope="col" | '''Deadline'''
! scope="col" | '''Closed'''
! scope="col" | '''Notes'''
|-
|<strike>2011-04-06</strike><br>2011-09-18
|
|The initial public release of Sweets infrastructure to let people try it assuming that basic conceptions were settled down and Sweets is ready for the first experiments (not ''production'' mode).
|-
|}


==== Activity Library ====
==== Activity Library ====
Line 53: Line 41:
{{Iframe|collapsed=collapsed|'''2011 September report:''' |http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg12349.html
{{Iframe|collapsed=collapsed|'''2011 September report:''' |http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg12349.html
|740|1820|1}}
|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 ==
== Proposals ==


* [http://far.no/fram/index.php?title=Fram FRAM] based activities on the Sugar Labs wiki.
* [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.
* [[Platform_Team/Polyol|polyol]] as a sugar-toolkit for non-Python activities.