Wiki source code of 2. Relation avec les membres
Last modified by Cyril Boillat on 12/03/2021
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
2.1 | 1 | After having aquired the quality of member of the Association, the new member appoints, within his institute, 3 referents who wil ensure the contacts with the Association. These 3 roles can be carried by the same person. |
| |
1.1 | 2 | |
| 3 | |||
| |
2.1 | 4 | * **A representative** |
| |
1.1 | 5 | |
| |
2.1 | 6 | : |
| 7 | :: The representative must have decision-making power allowing his institute to be invoved in all decisions taken within the Association. The representative sits at the General Meeting. | ||
| |
1.1 | 8 | |
| |
2.1 | 9 | * **A project leader (Product Owner - PO)** |
| |
1.1 | 10 | |
| 11 | : | ||
| |
2.1 | 12 | :: The project leader is the reference person in the institute for all questions relating to the //Botalista.community// software, both at the technical and organizational level. He is the link between the business part within the institution and the Association. He participates in the life of the Association by being part of the process of defining and prioritizing new features to be developed ([[User Stories>>doc:Computaceae-IT.Administration.1\. Organisation.2\. Association.1\. Règlement et processus de Botalista.WebHome||anchor="HProductBacklog"]]) within the Association's Technical commission. The principles and functioning of this Technical commission are governed by the [[//Rules and status of the Botalista technical commission.//>>doc:Computaceae-IT.Administration.2\. Commission Technique.Règlement et status de la commission technique de Botalista.WebHome]] |
| |
1.1 | 13 | |
| |
2.1 | 14 | {{{ |
| 15 | }}} | ||
| |
1.1 | 16 | |
| |
2.1 | 17 | * **The User reperesentative (Release Manager - RM)** |
| 18 | |||
| |
1.1 | 19 | : |
| |
2.1 | 20 | :: The user representative is in charge of testing the new functionalities before their publication (made available to users).He checks the business consistency of the developments and gives his publication agreement for all new functional versions (eg 1.**4**.12 -> 1.**5**.0)(% style="background-color:inherit; color:inherit; font-family:Menlo,Monaco,Consolas,~"Courier New~",monospace; font-size:inherit; white-space:pre" %).(%%) |
| 21 | The //Botalista.community// version management is described in [[the continuous delivery documentation>>doc:Computaceae-IT.Administration.2\. Commission Technique.asdfsafsaf.WebHome||style="font-size: inherit; white-space: pre; background-color: rgb(255, 255, 255);"]](% style="background-color:inherit; color:inherit; font-size:inherit; white-space:pre" %). | ||
| |
1.1 | 22 | |
| 23 | (% style="text-align:center" %) | ||
| |
2.1 | 24 | Organization chart between Botalista and the institutes |
| |
1.1 | 25 | {{thumbnail image="Organigramme-Institut.png" height="801" keepAspectRatio="true"/}} |