5,705
edits
Changes
Jump to navigation
Jump to search
Line 178:
Line 178: − + + + + + + + + − * 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. +
→1.0
* Likes for resources. Difficulty 2.
* Likes for resources. Difficulty 2.
* Live updates in resources user is subscribed after being online. Difficulty 4.
* Live updates in resources user is subscribed after becoming online. Difficulty 4.
* Getting digest of changes happened in resources where logged user is an author. Difficulty 3.
* Getting digest of changes happened in resources where logged user is an author. Difficulty 3.
* Uploading non-software content. Difficulty 5.
* Uploading non-binary software. Difficulty 3.
* Uploading binary software. Difficulty 1. (low priority).
*
* [[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):
* 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)
** 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)