5,705
edits
Changes
Jump to navigation
Jump to search
Line 127:
Line 127: − + − ** let all people, not only editors, expose the fact that particular activity [doesn't]works in theirs environment (maybe just by exposing how many fail Reports exist for the Implementation, Report might have the level of failure: doesn't do basic work, doesn't do optional work but basic features work fine). Line 138:
Line 137: + +
→Intermediate releases
* Synchronization between SN nodes.
* Synchronization between SN nodes.
* Basic i18n support in SN content (excluding managing already entered strings).
* Basic i18n support in SN content (excluding managing already entered strings).
* Basic routines for SN editors (including initial populating SN content):
* <strike>Basic routines for SN editors (including initial populating SN content):</strike> 0.3 will contain only trivial and ready use activities, the editors workflow implementation work will start from 0.4.
* <strike>Since there are useful binary based activities (GC, TuxPaint), support upload such activities to SN. From developers point of view, the only they need to proceed is uploading sources bundle to SN, the rest (building sources for all supported platforms) should happen automatically.</strike> Moved to 0.4.
* <strike>Since there are useful binary based activities (GC, TuxPaint), support upload such activities to SN. From developers point of view, the only they need to proceed is uploading sources bundle to SN, the rest (building sources for all supported platforms) should happen automatically.</strike> Moved to 0.4.
* Revise most popular ASLO activities to add all needed meta information (like required dependencies) and mark the as stable and ready to run from Sugar Network.
* Revise most popular ASLO activities to add all needed meta information (like required dependencies) and mark the as stable and ready to run from Sugar Network.
* Since there are useful binary based activities (GC, TuxPaint), support upload such activities to SN. From developers point of view, the only they need to proceed is uploading sources bundle to SN, the rest (building sources for all supported platforms) should happen automatically.
* Since there are useful binary based activities (GC, TuxPaint), support upload such activities to SN. From developers point of view, the only they need to proceed is uploading sources bundle to SN, the rest (building sources for all supported platforms) should happen automatically.
* [[Wiki:Create,_read,_update_and_delete|CRUD]] workflow for SN content.
* [[Wiki:Create,_read,_update_and_delete|CRUD]] workflow for SN content.
* Basic routines for SN editors (including initial populating SN content):
** let all people, not only editors, expose the fact that particular activity [doesn't]works in theirs environment (maybe just by exposing how many fail Reports exist for the Implementation, Report might have the level of failure: doesn't do basic work, doesn't do optional work but basic features work fine).
== Statistics to gather ==
== Statistics to gather ==