Difference between revisions of "GvSIG Technical Steering Committee"
m (GvSIG Technical Project Committee moved to GvSIG Technical Steering Committee: better translation of the Spanish name: Comité de Dirección Técnica) |
(reworded the name of the committee for a better translation from the Spanish name) |
||
| Line 3: | Line 3: | ||
in order to assure the decisions are made in a democratic way, etc. | in order to assure the decisions are made in a democratic way, etc. | ||
| − | The gvSIG Technical | + | The gvSIG Technical Steering Committee (TSC) is a group of 20 people, all experts |
form different areas (3D, mobile devices, documentation, i18n, ...) most of them are | form different areas (3D, mobile devices, documentation, i18n, ...) most of them are | ||
already working on gvSIG project for several years. They are part of | already working on gvSIG project for several years. They are part of | ||
| Line 9: | Line 9: | ||
administration. | administration. | ||
| − | == Objectives of the | + | == Objectives of the TSC == |
| − | The | + | The TSC is in charge of the technical steering of the gvSIG project. The |
technical aspects we delimit for the gvSIG project are: | technical aspects we delimit for the gvSIG project are: | ||
| Line 19: | Line 19: | ||
* collaborative infrastructure | * collaborative infrastructure | ||
| − | == The Board of Directors of the | + | == The Board of Directors of the TSC == |
| − | A subgroup of 8 people from the | + | A subgroup of 8 people from the TSC is formed by the technical leaders of the |
project. This group represents the Board of Directors and has the responsibility of approving or rejecting the most | project. This group represents the Board of Directors and has the responsibility of approving or rejecting the most | ||
important decisions of the governance of the project, usually based on the | important decisions of the governance of the project, usually based on the | ||
| − | proposals prepared by the | + | proposals prepared by the TSC. |
This group has ordinary meetings (mostly face to face, but also via IM) every two | This group has ordinary meetings (mostly face to face, but also via IM) every two | ||
weeks with documented agenda and minutes. ''(Please add link if possible)'' | weeks with documented agenda and minutes. ''(Please add link if possible)'' | ||
| − | == Coordinator of the | + | == Coordinator of the TSC == |
| − | A member of the board acts as a coordinator of the whole | + | A member of the board acts as a coordinator of the whole TSC. His role is to |
| − | manage the discussions, assure the communications inside the | + | manage the discussions, assure the communications inside the TSC and the rest |
| − | of the project are fluent, and act as an interlocutor for the | + | of the project are fluent, and act as an interlocutor for the TSC outside. |
| − | At this time [[Jorge Sanz]] is the coordinator of the gvSIG | + | At this time [[Jorge Sanz]] is the coordinator of the gvSIG TSC. |
== Working groups == | == Working groups == | ||
| − | The real work of the | + | The real work of the TSC happens in working groups. When a new proposal arises, |
| − | or a medium/big task appears, the | + | or a medium/big task appears, the TSC creates a new working group with a board |
member as a chair of it. | member as a chair of it. | ||
| Line 48: | Line 48: | ||
Some of these working groups can have a long term goal and work preparing | Some of these working groups can have a long term goal and work preparing | ||
| − | proposals to the Board of the | + | proposals to the Board of the TSC and others have a very specific objective and |
when it's accomplished the group is dissolved. | when it's accomplished the group is dissolved. | ||
| Line 55: | Line 55: | ||
reports, answer questions, etc. | reports, answer questions, etc. | ||
| − | == Adding members to the | + | == Adding members to the TSC == |
| − | The first | + | The first TSC group was elected by the Board of Directors. This group was |
decided by the Board based on the technical skills and role of the member in | decided by the Board based on the technical skills and role of the member in | ||
different areas of gvSIG development. | different areas of gvSIG development. | ||
| − | Now, after a test period, the | + | Now, after a test period, the TSC has the right to elect new members. |
| − | Any member of the | + | Any member of the TSC can nominate a member of the gvSIG community and the TSC |
should vote it. | should vote it. | ||
== Stepping down == | == Stepping down == | ||
| − | Any member can step down from the | + | Any member can step down from the TSC at any moment, but besides that the TSC can |
| − | also promote the expulsion of a member of the | + | also promote the expulsion of a member of the TSC (witch will be voted by the Board |
of Directors) on any of these situations: | of Directors) on any of these situations: | ||
| − | * Serious lack of discipline with any member of the | + | * Serious lack of discipline with any member of the TSC |
* Serious lack of consideration on a public forum with the gvSIG project | * Serious lack of consideration on a public forum with the gvSIG project | ||
| − | * Continued lack of activity on the | + | * Continued lack of activity on the TSC (voting, participating on working groups) |
| − | * Incompatibility with the | + | * Incompatibility with the TSC activities due to: |
| − | ** Lack of time to work on the | + | ** Lack of time to work on the TSC |
| − | ** Conflict of interest between the | + | ** Conflict of interest between the TSC or gvSIG and the current employer of the member |
[[Category:gvSIG]] [[Category:Incubation]] | [[Category:gvSIG]] [[Category:Incubation]] | ||
Revision as of 01:47, 25 February 2010
This page contains a summary of how gvSIG is technically managed, which groups are on the project to manage the technical decisions and how they operate in order to assure the decisions are made in a democratic way, etc.
The gvSIG Technical Steering Committee (TSC) is a group of 20 people, all experts form different areas (3D, mobile devices, documentation, i18n, ...) most of them are already working on gvSIG project for several years. They are part of different entities such as universities, private companies and public administration.
Objectives of the TSC
The TSC is in charge of the technical steering of the gvSIG project. The technical aspects we delimit for the gvSIG project are:
- new functionalities to develop
- development engineering (architecture, methodologies, etc.)
- project documentation
- collaborative infrastructure
The Board of Directors of the TSC
A subgroup of 8 people from the TSC is formed by the technical leaders of the project. This group represents the Board of Directors and has the responsibility of approving or rejecting the most important decisions of the governance of the project, usually based on the proposals prepared by the TSC.
This group has ordinary meetings (mostly face to face, but also via IM) every two weeks with documented agenda and minutes. (Please add link if possible)
Coordinator of the TSC
A member of the board acts as a coordinator of the whole TSC. His role is to manage the discussions, assure the communications inside the TSC and the rest of the project are fluent, and act as an interlocutor for the TSC outside.
At this time Jorge Sanz is the coordinator of the gvSIG TSC.
Working groups
The real work of the TSC happens in working groups. When a new proposal arises, or a medium/big task appears, the TSC creates a new working group with a board member as a chair of it.
These working groups have their own collaboration space at the gvSIG portal with its own forum and document space where the members work and discuss about the central topic.
Some of these working groups can have a long term goal and work preparing proposals to the Board of the TSC and others have a very specific objective and when it's accomplished the group is dissolved.
The chair of the working group (a member of the Board) should report to the rest of the board on any ordinary meeting how it's group is going, present reports, answer questions, etc.
Adding members to the TSC
The first TSC group was elected by the Board of Directors. This group was decided by the Board based on the technical skills and role of the member in different areas of gvSIG development.
Now, after a test period, the TSC has the right to elect new members. Any member of the TSC can nominate a member of the gvSIG community and the TSC should vote it.
Stepping down
Any member can step down from the TSC at any moment, but besides that the TSC can also promote the expulsion of a member of the TSC (witch will be voted by the Board of Directors) on any of these situations:
- Serious lack of discipline with any member of the TSC
- Serious lack of consideration on a public forum with the gvSIG project
- Continued lack of activity on the TSC (voting, participating on working groups)
- Incompatibility with the TSC activities due to:
- Lack of time to work on the TSC
- Conflict of interest between the TSC or gvSIG and the current employer of the member
Members
Committee
| Name | Organization |
|---|---|
| Álvaro Zabala | Junta Andalucia |
| César Martínez | |
| Cesar Ordiñana | DISID |
| Carlos Sánchez | Prodevelop |
| Diego Guerrero | UCLM |
| Javier Carrasco | Prodevelop |
| José Luis Celda | Logex |
| Chema Vivó | DISID |
| Jorge Piera | Prodevelop |
| Mario Carrera | IVER |
| Fran Peñarrubia | Software Colaborativo |
| Mijail Antón | |
| Sergio Beltran Talens | ITI |
| Víctor Acevedo | IVER |
| Victoria Agazzi | Prodevelop |
| Vicente Caballero | IVER |
| Víctor Olaya | UNEX |
Board of Directors
| Name | Organization |
|---|---|
| Álvaro Anguix | IVER |
| Nacho Brodin | Prodevelop |
| Gabriel Carrión | CIT |
| Joaquín del Cerro | IVER |
| Manuel Madrid | IVER |
| Miguel Montesinos | Prodevelop |
| Jorge Sanz | Prodevelop |
| Luis W. Sevilla | SIGRID |
| José Vicente Higón | Software Colaborativo |