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