<br>
<div class="note">
<p class="first admonition-title">Note</p>
<p class="last">This is a draft document!!</p>
</div>
<br>
<p>The regulations include the following sections:</p>
<ul>
<li><a href="#reuniones">Meetings of the Technical Steering Committee</a></li>
<li><a href="#CDT">Changes in the membership of the TSC</a></li>
<li><a href="#board">Changes in the membership of the Board of Directors</a></li>
</ul>
<br />
<hr>
<br />
<h3><a name="reuniones"><em><strong>Meetings of the Technical Steering Committee</strong></em></a></h3>
<br />
<p> In general, any meeting must always be reflected in the private area of the Technical Steering Committee (TSC), creating a folder for that purpose. The TSC has two main folders, one for the TSC in full and another for the Board.</p>
<br />
<h4><strong>Regular meetings</strong></h4>
<br />
<ul>
<li><strong>Frequency and schedule:</strong> Regular meetings will be held the first and third Monday of each month or the next working day if that day is a public holiday. Meetings will take place from 9.30 to 11.30 am (GTM+1 in winter, GTM+2 in summer).</li>
<li><strong>Preparing the Agenda: </strong>The agenda for each meeting will be prepared the previous week and the coordinator will have the responsibility of preparing a document and an initial proposal for the meeting. After creating the document, the coordinator shall notify all Board members that they can propose new issues for discussion at the meeting as well as changes to the order of the issues because all issues probably may not be discussed at one meeting. Those agenda items that may not be discussed at one meeting, won't be removed. They will be proposed for the next meeting.</li>
</ul>
<br />
<h4><strong>Structure of a meeting </strong></h4>
<br />
<p> A regular meeting of the Board will have some fixed issues and there will be time limit to discuss each of those issues to ensure that the meeting is productive and aimed at solving problems.</p>
<ul>
<li><strong>Review scheduled tasks (10 minutes):</strong> Those members who have some scheduled task will report on the state of that task. If they want to present some kind of documentation, it's better they put that documentation on the agenda of the meeting directly or as related content.</li>
<li><strong>Review of the status of the working groups of TSC (2-3 minutes per group): </strong>Each leader of a working group will give a brief summary of the tasks that his/her working group is carrying out.</li>
<li><strong>Core of the meeting (1h 30minutes):</strong> The issues that have been included in the agenda of the meeting will be discussed one by one with the aim of tackling most of them.</li>
<li><strong>Next meeting (5 minutes):</strong> Review items on the agenda for the next meeting.</li>
<li><strong>Pending matters (5 minutes):</strong> Allocation of tasks for the next meeting.</li>
</ul>
<br />
<h4><strong> Minutes</strong></h4>
<br />
<p> Each meeting will have a minute which will summarize the issues discussed and the decisions and activities which have been agreed.</p>
<p> </p>
<h3><a name="CDT"><strong><em>Changes in the membership of the TSC</em></strong></a></h3>
<br />
<h4><strong>Votes</strong></h4>
<br />
<p> In general, the changes in the membership of the TSC shall be approved by a qualified majority of 50% of the votes cast and the quorum of that meeting shall be at least two third (2/3) of the voting membership.</p>
<br />
<h4><strong>Acceptance of new members</strong></h4>
<br />
<p> Any member of the TSC(including the Board) can propose the incorporation of a new member from the gvSIG community and the TSC in full must vote. It is desirable that the acceptance of a new member is properly justified to provide elements for discussion if necessary. Specifically, the procedure will be:</p>
<ol>
<li>Any member of the TSC may contact the nominee to confirm that that person wants to belong to the TSC. This is an informal preliminary contact, but it's necessary to avoid making an unnecessary proposal.</li>
<li>Any member of the TSC (or the coordinator on behalf of that candidate) may make a nomination, that basically consists of the following steps:<br>
<ol>
<li>Create a new folder with a descriptive title, for example "Acceptance of (nominee's name) in the TSC”.</li>
<li>Create a text document with the same title in that folder.</li>
<li>Copy the template “template of acceptance of a new member in the TSC” in that document and complete it.</li>
<li>Include the members of the TSC as collaborators of the document.</li>
<li>Add a comment to inform the members of the TSC about this nomination for discussion.</li>
</ol>
</li>
<li>The coordinator is responsible for opening and closing the voting period.</li>
<li>If the nominee is accepted:<br>
<ol>
<li>A new ticket will be opened in the Trac of activities to notify there is a new member in the portal group.</li>
<li>That person will be included as collaborator in the forum and the other members will welcome him and say to him where the relevant documentation is.</li>
</ol>
</li>
<li>If the nominee is not accepted, the nominee will be also notified.</li>
</ol>
<br />
<p> The Board of the TSC can't accept new members in the TSC unilaterally, the nominations only can be approved by the TSC in full.</p>
<br />
<h4><strong>Exclusion of members</strong></h4>
<br />
<p> At any time, a member of TSC may request his voluntary exclusion of the TSC. That person only needs to communicate it formally to the coordinator, who will inform the other members of the TSC through the forum.</p>
<br />
<p>On the other hand, the following situations will cause the irrevocable exclusion of a member:</p>
<ul>
<li>Gross misconduct with other members of the TSC.</li>
<li>Criticize in public gvSIG or the gvSIG Association.</li>
<li>Lack of continued activity in the TSC (participation in voting, in working teams, etc.).</li>
<li>Incompatibility with his duties in the TSC owing to:<br>
<ul>
<li>A conflict of interests between the TSC and the entity with which that member has a professional relationship.</li>
<li>Lack of time to carry out his duties in the TSC.</li>
</ul>
</li>
</ul>
<br />
<p> The procedure to handle a non-voluntary exclusion from the TSC is as follows:</p>
<ol>
<li>Any member of the TSC communicates the coordinator about any of the above situations.</li>
<li>The coordinator includes that issue in the agenda of the next regular meeting of the Board to discuss it.</li>
<li>The Board discusses the issue in a meeting, although it can be discussed on more than one meeting or off-line through the portal. The Board may request additional information from the informant or from the member involved to determine if that member must be excluded from the TSC.</li>
<li>The Board votes and decides if that member is excluded.</li>
</ol>
<br />
<p>When the exclusion of a member from the TSC is approved, the coordinator must:</p>
<ol>
<li>Request the exclusion of that user from the Plone group of the TSC.</li>
<li>Inform the other members of the TSC about the exclusion of that member through the forum and ask them to remove the member of any document in which he was a collaborator.</li>
<li>Exclude that user from the general forum of the TSC.</li>
</ol>
<br />
<p> Moreover, if that member gives up the project completely, the coordinator will follow the general procedure to request the exclusion of that member from the rest of the services (SVN, trackers, etc.).</p>
<p> </p>
<h3><a name="board"><strong><em>Changes in the membership of the Board of Directors</em></strong></a></h3>
<br />
<h4><strong>Votes</strong></h4>
<br />
<p> In general, the changes in the membership of the Board shall be approved by a qualified majority of 50% of the votes cast and the quorum of that meeting shall be at least two third (2/3) of the voting membership.</p>
<br />
<h4><strong>Acceptance of new members</strong></h4>
<br />
<p> To become a member of the Board of the TSC, it's necessary to fulfil the following requirements:</p>
<ul>
<li>Have belonged to the TSC for at least <strong>a year</strong>.</li>
<li>Have collaborated actively in at least <strong>two working groups</strong>.</li>
</ul>
<br />
<p> These requirements aim to ensure that nominees already have some experience about how the TSC works internally and knowledge in-depth of the gvSIG project and its technical management institutions.<br>
<br>
Both the nominee and any member of the Board can propose the incorporation of a new member in the Board. In any case the nominee (or the person who has nominated him) must submit an application to the Board stating the reasons for wishing to belong to that group. Then, the Board may ask the candidate the questions that the Board deems appropriate.<br>
<br>
Specifically, the procedure will be:</p>
<ol>
<li>Any member of the Board may contact the nominee to confirm that that person wants to belong to the Board. This is an informal preliminary contact, but it's necessary to avoid making an unnecessary proposal.</li>
<li>Any member of the Board (or the coordinator on behalf of that candidate) may make a nomination, that basically consists of the following steps:<br>
<ol>
<li>Create a new folder with a descriptive title, for example "Acceptance of (nominee's name) in the Board” in the private area of the Board.</li>
<li>Create a text document with the same title in that folder.</li>
<li>Copy the template “template of acceptance of a new member in the TSC” in that document and complete it.</li>
<li>Include the members of the Board as collaborators of the document.</li>
<li>Add a comment to inform the members of the Board about this nomination so that they can include their comments in that text document.</li>
</ol>
</li>
<li>The coordinator is responsible for opening and closing the voting period.</li>
<li>If the nominee is accepted:
<ol>
<li>A new ticket will be opened in the Trac of activities to notify there is a new member in the portal group.</li>
<li>That person will be included as collaborator in the forum.</li>
</ol>
</li>
<li>If the nominee is not accepted, the nominee will be also notified. </li>
</ol>
<br />
<h4><strong>Exclusion of members</strong></h4>
<br />
<p><em> A member of the Board and any other member of the TSC are excluded by the same reasons and following the same procedure of exclusion. The only difference is the seriousness of the situation, since the Board is the highest technical authority of the project.</em></p>
<br />
<p> At any time, a member of the Board may request his voluntary exclusion of the Board. That person only needs to communicate it formally to the coordinator, who will inform the other members of the Board through the forum.</p>
<br />
<p> On the other hand, the following situations will cause the irrevocable exclusion of a member from the Board:</p>
<ul>
<li>Gross misconduct with other members of the TSC.</li>
<li>Criticize in public gvSIG or the gvSIG Association.</li>
<li>Lack of continued activity in the Board (participation in voting, in working teams, etc.).</li>
<li>Incompatibility with his duties in the Board or in the TSC owing to:<br>
<ul>
<li>A conflict of interests between the TSC and the entity with which that member has a professional relationship.</li>
<li>Lack of time to carry out his duties in the Board.</li>
</ul>
</li>
</ul>
<br />
<p> The procedure to handle a non-voluntary exclusion from the Board is as follows:</p>
<ol>
<li>Any member of the group communicates the coordinator about any of the above situations.</li>
<li>The coordinator includes that issue in the agenda of the next regular meeting of the Board to discuss it.</li>
<li>The Board discusses the issue in a meeting, although it can be discussed on more than one meeting or off-line through the portal. The Board may request additional information from the informant or from the member involved to determine if that member must be excluded from the Board.</li>
<li>The Board votes and decides if that member is excluded.</li>
</ol>
<br />
<p> When the exclusion of a member from the Board is approved, the coordinator must:</p>
<ol>
<li>Request the exclusion of that user from the Plone group of the TSC.</li>
<li>Inform the other members of the TSC about the exclusion of that member through the forum and ask them to remove the member of any document in which he was a collaborator.</li>
<li>Exclude that user from the general forum of the TSC.</li>
</ol>
<br />
<p>Moreover, if that member gives up the project completely, the coordinator will follow the general procedure to request the exclusion of that member from the rest of the services (SVN, trackers, etc.).</p>
