| 69 | | milo - |
| 70 | | * General: |
| 71 | | * We should add the corresponding milestones (at least on the wiki page), because developers will get confused, since Release 1 corresponds to M02_PRE2 (and so on). |
| 72 | | * I think that it is ok not to define lots of things, but it is important for our clients to see all the major features they expect. |
| 73 | | * Release 1: |
| 74 | | * "Can be run on the Macintosh with script changes" - should be changed to "Can be run on the Macintosh with configuaration tweaking" or something |
| 75 | | * On the community site we may add "mail lists, discussion forum, developers wiki". Documentation page is ambigious and should be written in another way. |
| 76 | | * Release 2: |
| 77 | | * While on the heading it says prototypical, some of the features are also marked as prototypical, while others are not. We should either remove the protypical word from these, or add it to the all. |
| 78 | | * Plugin support may be added. (we already have it) |
| 79 | | * Release 3: |
| 80 | | * The resource changes are not only part of the server. To the application, there will be added functionalities to list and manipulate resources. |
| 81 | | * The prototype of the book's desktop is a significant feature and we may add it. |
| 82 | | * Release 4: |
| 83 | | * "Developers skin" is not an apropriate name. If we dont want to use "hackers" we should use "Alternative skin". |
| | 69 | gogov: |
| | 70 | |
| | 71 | General: |
| | 72 | * lots of tasks are listed with a prototype phase but don't contain medium or finishing phases so further planning is needed to include finishing or even medium development phases for certain feature sets. |
| | 73 | * there could be some sort of listing the level of completeness of different categories of features in the Alpha phases. |
| | 74 | There is some outline provided now but it'd be better if more details are included to underline the priorities of completing different categories in time. |
| | 75 | * in general the list is too short in details which might lead to lots of extra questions and planning at a later phase. |
| | 76 | |
| | 77 | The following are a few more specific things I noticed and listed in order to get a discussion going on if such details are to be included in this list or not. |
| | 78 | I've got lots of other specific comments like these but if not needed there's no sense in listing them here. |
| | 79 | |
| | 80 | Release 2: |
| | 81 | * more menu support -- this section should be more specific |
| | 82 | |
| | 83 | Release 3: |
| | 84 | * Community Web Site -- it'd be better if this is included in Release 2, so more people can get involved earlier in the Sophie project in general |
| | 85 | |
| | 86 | Release 4: |
| | 87 | * page zooming & frame rotating -- these tasks should be included as subtasks in a more general scene management task, and this task should be broken in different phases. |
| | 88 | * application help -- should be updated more frequently so users of earlier versions have some documentation available |
| | 89 | |
| | 90 | Release 5: |
| | 91 | * adding to the comments listed in the Release 6 notes, timelines should definitely have more detailed breakdown, since the task of completing them is quite complex and reuires much effort. |
| | 92 | * page element grouping -- this seems related to Release 2 "Prototype for selecting multiple page objects", so it could be brought earlier in time so the two tasks are closer. |
