TracOrganisation » History » Version 16
mehdi, 03/02/2010 07:41 PM
| 1 | 1 | mehdi | = Trac Organisation = |
|---|---|---|---|
| 2 | To perform a better use of this trac and make it Understandable for all, a charter of use has been defined. |
||
| 3 | 8 | mehdi | |
| 4 | 5 | mehdi | This trac had to be used because it is the central tools to define the priorities of development and to follow the Openspace3D project. |
| 5 | 1 | mehdi | |
| 6 | == milestones == |
||
| 7 | |||
| 8 | 4 | mehdi | A milestone corresponds to a version of Openspace3D and the corresponding voyager. |
| 9 | 1 | mehdi | |
| 10 | 5 | mehdi | The "Openspace3D beta" milestone permits to define the global objectives concerning the platform. |
| 11 | 1 | mehdi | |
| 12 | == Components == |
||
| 13 | |||
| 14 | They allow to identify which components is targeted for a corresponding tickets. |
||
| 15 | 8 | mehdi | |
| 16 | 5 | mehdi | A ticket could concern several components especially for Openspace3D beta'tickets |
| 17 | 1 | mehdi | |
| 18 | 13 | mehdi | === Example === |
| 19 | 2 | mehdi | VM_SO3Engine: 3D Engine Component(SO3Engine), could be : a development to modify SO3Engine.dll or to add a functionality into it |
| 20 | 8 | mehdi | |
| 21 | 2 | mehdi | ex : Add functions to use stereoscopic rendering |
| 22 | 1 | mehdi | |
| 23 | 2 | mehdi | OS3D_PlugIT : Component conerns the development of a new plugIT or a modification of an existing plugIT |
| 24 | 1 | mehdi | |
| 25 | 2 | mehdi | == Naming Tickets == |
| 26 | 1 | mehdi | |
| 27 | 2 | mehdi | The objetive is to define tickets as thematic tickets. |
| 28 | 8 | mehdi | |
| 29 | 2 | mehdi | It optimises the project management. |
| 30 | 8 | mehdi | |
| 31 | 14 | mehdi | === Example === |
| 32 | 8 | mehdi | |
| 33 | 6 | mehdi | [Particles] Integration of particles system in Openspace3D (it is a global ticket) |
| 34 | 1 | mehdi | |
| 35 | 2 | mehdi | == A concrete example == |
| 36 | 8 | mehdi | |
| 37 | 2 | mehdi | The following example shows and explain the naming for tickets corresponding to a functionality. |
| 38 | 8 | mehdi | |
| 39 | 16 | mehdi | - "We want to develop an Avatar plugIT into Openspace3D" |
| 40 | 1 | mehdi | |
| 41 | 5 | mehdi | - The global tickets in Openspace3D beta milestone is : |
| 42 | 8 | mehdi | |
| 43 | 5 | mehdi | ''milestone'' : Openspace3D beta ''summary'' : [Avatar] Add a plugIT to manage avatar. ''components'' : VM+OS3D_plugIT |
| 44 | 1 | mehdi | |
| 45 | 2 | mehdi | - Into the milestone corresponding to the implementation, we add to give all the "subTickets" corresponding to Avatar plugIT project : |
| 46 | 8 | mehdi | |
| 47 | 11 | mehdi | ''milestone'' : Openspace3D alpha 0.1.9 ''summary'': [Avatar] Management of bones into 3D Engine ''Component'' : VM_SO3Engine |
| 48 | 8 | mehdi | |
| 49 | 11 | mehdi | ''milestone'' : Openspace3D alpha 0.1.9 ''summary'': [Avatar] Possibility to Add Mesh to a bone into 3D Engine ''Component'' : VM_SO3Engine |
| 50 | 8 | mehdi | |
| 51 | 11 | mehdi | ''milestone'' : Openspace3D alpha 0.1.9 ''summary'': [Avatar] plugIT editor ''Component'' : OS3D_plugIT |
| 52 | 8 | mehdi | |
| 53 | 11 | mehdi | ''milestone'' : Openspace3D alpha 0.1.9 ''summary'': [Avatar] Animation system ''Component'' : OS3D_plugIT |
| 54 | 1 | mehdi | |
| 55 | 12 | mehdi | === Why used this topology? === |
| 56 | 8 | mehdi | |
| 57 | 9 | mehdi | The global functionality is defined by a project ex : [Avatar] |
| 58 | 8 | mehdi | |
| 59 | 7 | mehdi | The functionallity is cutted in several tickets for the development into a version |
| 60 | 8 | mehdi | |
| 61 | 7 | mehdi | Openspace3D beta allow to have a global vision of the final project and the different priorities |