Draft policy for decision making, voting (quorum), and membership terms. #17

Closed
jukervin opened this Issue May 6, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@jukervin
Member

jukervin commented May 6, 2015

How many board members will be needed to make a decision / schema change?
Since participation in the calls vary maybe the voting should be done offline.

@jukervin jukervin self-assigned this May 6, 2015

@jukervin jukervin added this to the 2015-06-03 Board Call milestone May 6, 2015

@jukervin jukervin added the action item label May 6, 2015

@cowboyMontana cowboyMontana changed the title from Policy for decision making and quorum to Draft policy for decision making, voting (quorum), and membership terms. Jun 23, 2015

@jukervin

This comment has been minimized.

Show comment
Hide comment
@jukervin

jukervin Jun 24, 2015

Member

Draft: ALTO Schema Revisions & Change Request Process

Proposals for changes to the ALTO schema should be made in writing to the ALTO XML schema GitHub repository as an issue and optionally to ALTO list. They may come from individuals, ALTO interest groups, or other entities.

Change request requirements: statement of change, reasons/use case for the request and description of solution. The issue should also include example ALTO xml section showing the change in use and it can also optionally include changes needed to ALTO schema file.

The Board aims to process the change requests in order of submission when possible but reserves right to prioritize requests if needed due to complexity, impact, urgency or other reason.

The change request will undergo following steps:

First discussion. Board begins processing the submitted change request in a board call. Minutes from the discussion are entered as a comment to the issue.

Commenting period. Board members and public can comment the Change Request in GitHub for minimum of two weeks.

Second discussion. The change request is discussed in a board call. Minutes from the discussion are entered as a comment to the issue.

Change Approval. Approval voting with two thirds majority needed to accept the change request. Voting is done by having Board members enter their votes to the issue as comments. Voting timeframe is two weeks.

Schema drafting. Schema editors prepare the needed schema file and documentation changes as a new branch in GitHub.

Schema Change Approval. Voting with two thirds majority needed to accept the schema changes. The changes are merged to draft version. Voting is done by commenting the branch.

Schema Release. The latest draft version is released as new version. Schema releases should be done twice a year unless an urgent fix is needed.

Member

jukervin commented Jun 24, 2015

Draft: ALTO Schema Revisions & Change Request Process

Proposals for changes to the ALTO schema should be made in writing to the ALTO XML schema GitHub repository as an issue and optionally to ALTO list. They may come from individuals, ALTO interest groups, or other entities.

Change request requirements: statement of change, reasons/use case for the request and description of solution. The issue should also include example ALTO xml section showing the change in use and it can also optionally include changes needed to ALTO schema file.

The Board aims to process the change requests in order of submission when possible but reserves right to prioritize requests if needed due to complexity, impact, urgency or other reason.

The change request will undergo following steps:

First discussion. Board begins processing the submitted change request in a board call. Minutes from the discussion are entered as a comment to the issue.

Commenting period. Board members and public can comment the Change Request in GitHub for minimum of two weeks.

Second discussion. The change request is discussed in a board call. Minutes from the discussion are entered as a comment to the issue.

Change Approval. Approval voting with two thirds majority needed to accept the change request. Voting is done by having Board members enter their votes to the issue as comments. Voting timeframe is two weeks.

Schema drafting. Schema editors prepare the needed schema file and documentation changes as a new branch in GitHub.

Schema Change Approval. Voting with two thirds majority needed to accept the schema changes. The changes are merged to draft version. Voting is done by commenting the branch.

Schema Release. The latest draft version is released as new version. Schema releases should be done twice a year unless an urgent fix is needed.

@jukervin

This comment has been minimized.

Show comment
Hide comment
@jukervin

jukervin Nov 6, 2015

Member

Discussion from meeting:

  • Voting is needed from 2/3rds of members.
  • Acceptance requires 2/3rds approval from voters. Board strives for unanimous decision.
  • Voting is opened at a board meeting and closed at the next meeting. Minimum voting time is two weeks.
Member

jukervin commented Nov 6, 2015

Discussion from meeting:

  • Voting is needed from 2/3rds of members.
  • Acceptance requires 2/3rds approval from voters. Board strives for unanimous decision.
  • Voting is opened at a board meeting and closed at the next meeting. Minimum voting time is two weeks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment