diff --git a/README.md b/README.md index 43c0c36..9bd8728 100644 --- a/README.md +++ b/README.md @@ -1,27 +1,25 @@ # SciCat Project Governance -_IMPORTANT: these governance document are still a work-in-progress_ - ## Introduction The purpose of this repository is to formalize the governance process that the SciCat project follows and has been using informally for the past few years. -These documents clarify who has which responsibility, how decisions are made and how the various elements of our community interact. -It is based from [Bluesky governance](https://), which has been adapted from -[GitHub's Minimum Viable Governance](https://github.blog/2021-07-22-minimum-viable-governance-lightweight-community-structure-foss-projects/). +These documents clarify the responsibilities, decision processes, and how the various elements of our community interact. +The governance model was inspired by the [Bluesky governance](https://) and the +[GitHub Minimum Viable Governance](https://github.blog/2021-07-22-minimum-viable-governance-lightweight-community-structure-foss-projects/). ## Why? -Data cataloging, curation and sharing are becoming a critical step in many facilities data lifecycle. +Data cataloging, curation and sharing are becoming a critical step in many organizations' data lifecycle. The SciCat project and its community aims to communicate clearly how the project is managed, how the priorities are set and effort is allocated. We would like to formalize and document the processes contributors and adopters can follow to become active members of the community and easily contribute to the project. This effort is also important to communicate the commitment of the community to the Project and render SciCat a viable and well thought option in the landscape of data catalogues. ## Purpose -The governance documents aim to formalize the SciCat project (following referred as the Project) as an international, multi-facility, community-driven project. +The governance documents aim to formalize the SciCat project as an international, multi-organization, community-driven project. ## Adoption -Project contributors, adopting facilities and commercial partners agree to adhere to the definition, procedure and responsabilities described in the content of these documents +Project contributors, contributing organizations and commercial partners agree to adhere to the definition, procedure and responsibilities described in the content of these documents ## Governance Entities Mission @@ -39,13 +37,12 @@ The Governance Entities of the Project are set in place to promote a positive de ### Governance Entities -- [Users Community](./governance-entities/USERS-COMMUNITY.md) - [Contributors Community](./governance-entities/CONTRIBUTORS-COMMUNITY.md) - [Technical Leaders](./governance-entities/TECHNICAL-LEADERS.md) - [Project Leaders](./governance-entities/PROJECT-LEADERS.md) - [Steering Committee](./governance-entities/STEERING-COMMITTEE.md) - [Advisory Boards](./governance-entities/ADVISORY-BOARDS.md) -- [Facilities](./governance-entities/FACILITIES.md) +- [Contributing Organizations](./governance-entities/CONTRIBUTING-ORGANIZATIONS.md) - [Voting Body](./governance-entities/VOTING-BODY.md) ### Project Components @@ -83,20 +80,8 @@ The Governance Entities of the Project are set in place to promote a positive de ## Status -These documents are in active development. They have been adapted from: - -- [Bluesky Governance](https://), which have been derived from the -- [GitHub's Minimum Viable Governance](https://github.com/github/MVG). - -We are in Step 2 of the following process: - -1. Develop a draft of the governance. -2. Collect feedback and contributions from Collaborators and the Community - Please use GitHub Issues and PRs on this repository to provide feedback anc contributions. -3. Content revision based on feedback. -4. Announce initial memberships for each group and committee and maintainers for each repo, if possible. - -Even if we are in step 2, we already working to find Project Leaders, and forming the Main Technical Committee. +Governance documents are tracked at . +The latest [release](https://github.com/SciCatProject/governance/releases) is considered to be in effect, while the `main` branch represents the latest draft under consideration. *** Licensed under the [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License. diff --git a/governance-entities/CONTRIBUTING-ORGANIZATIONS.md b/governance-entities/CONTRIBUTING-ORGANIZATIONS.md new file mode 100644 index 0000000..2a7e195 --- /dev/null +++ b/governance-entities/CONTRIBUTING-ORGANIZATIONS.md @@ -0,0 +1,16 @@ +# Contributing Organizations + +## Abbreviations + +CO = Contributing Organization + +## Definition + +A _contributing organization_ is any facility, institute, or organization that commits to significant ongoing contribution to the Project. A significant contribution is defined as at least 50% of an full time position (0.5 FTE) per year. + +## Responsibilities + +A contributing organization has the responsibility to allocate resources equivalent to at least half of an FT to sustain and contribute to the Project. Only contributing organizations participate in the [Steering Committee](STEERING-COMMITTEE.md). + +--- +Licensed under the [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License. diff --git a/governance-entities/FACILITIES.md b/governance-entities/FACILITIES.md deleted file mode 100644 index 9bcd2f7..0000000 --- a/governance-entities/FACILITIES.md +++ /dev/null @@ -1,20 +0,0 @@ -# Facilities - -## Abbreviations - -AF = Adopting Facility -CF = Contributing Facility - -## Definition - -A facility is any entity, institute, group of people that has an active interest in the Project. -An _adopting facility_ is a facility that has installed SciCat in production and SciCat is part their technical infrastrucutre and data management. -A _contributing facility_ is a facility that has allocated at least half of an FT to actively contributing to the Project in any form or shape - -## Responsibilities - -There are no official responsibilities for an adopting facility, although, at times, they are called to provide feedback to the project. -A contributing facility has the responsibility to allocate resources equivalent to a half of an FT to sustain and contribute to the Project. - -*** -Licensed under the [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License. diff --git a/governance-entities/PROJECT-LEADERS.md b/governance-entities/PROJECT-LEADERS.md index 24b9506..6416a71 100644 --- a/governance-entities/PROJECT-LEADERS.md +++ b/governance-entities/PROJECT-LEADERS.md @@ -25,7 +25,7 @@ The PL's duties and responsibilities are: - promote the project, - maintain relationships with: - contributors community, - - adopting facilities and their management + - contributing organizations and their management - user community - provide project guidance - moderate in case of disputes or conflicts @@ -46,7 +46,7 @@ PL do agree to put as much effort as required in performing the responsibilities Any member of the Contributors Community is eligible to be nominated to become a Project Leader, proven that: - they have a solid knowledge of the Project, -- they are associated with a supporting facility. +- they are associated with a contributing organization. They might be asked to sustain one or more interviews with any of the Project governing entities. The interviews will be decided by the current PL on per-nomination case, with the guidance of the SC. The nomination for a PL position should follow the process described in the [Nomination](../procedures/NOMINATION.md) section. @@ -60,6 +60,13 @@ For each open position as a Project Leader, any member of the Contributors Commu No matter the number of candidates for each position, a vote by the Contributors Voting Body is required. The voting procedure will follow the procedure described in the [Voting](../procedures/VOTING.md) section. +## Ratification + +Following election, the SC should ratify the newly elected PL candidates by majority +vote of the SC within two weeks. If the SC fail to ratify a candidate, a special +election will be held. The special election should be held after at least four weeks to +allow additional nominations, and within at most 2 months of the initial vote. + ## Duration Project Leaders maintain their role for a three plus three years mandate. At the end of the first three years mandate, the outgoing PL can decide to renew their candidacies for the following three years and participate in the next round of elections. diff --git a/governance-entities/STEERING-COMMITTEE.md b/governance-entities/STEERING-COMMITTEE.md index ccf41c5..36593a0 100644 --- a/governance-entities/STEERING-COMMITTEE.md +++ b/governance-entities/STEERING-COMMITTEE.md @@ -10,50 +10,68 @@ FT = Full Time ## Description -The Steering Committee includes representatives of supporting facilities. -Members of the Steering Committee should not be Project Contributors, but should be part of the management team of the facilities or consortiuum they are part of. +The Steering Committee includes representatives of contributing organizations. +Members of the Steering Committee are usually not Project Contributors, but should be part of the management team of their contributing organization. ## Responsibilities and Duties The SC is tasked with: -- providing guidance and non-binding feedback to the Project Leaders (PL), -- promoting the Project within their home facilties and science community +- providing guidance and feedback to the Project Leaders (PL), +- promoting the Project within their home organization and science community - promoting the Project at large - help sustaining the project - discover possible funding sources -- make sure that their facility allocates resources to sustain the project -- monitor, confirm and support fair election of candidates for Project Leaders and Technical Leaders positions. +- make sure that their organization allocates resources to sustain the project +- monitor, confirm and support fair election of candidates for Project Leaders and Technical Leaders positions. +- ratifying PL elections and major decisions -## Meeting +## Meetings -The SC should meet at least once a year, possibly in person and at the annual meeting SciCatCon. +The SC should meet at least once a year (for instance, at the annual SciCatCon meeting). The meeting will be scheduled and announced in due time through the Project official channels. -Aside of the single annual meeting, additional meetings might be organized based on the Project needs. Additional meetings can happen on-line. +Additional meetings might be organized based on the Project needs. +The annual SC meeting is chaired by the host of SciCatCon for that year. -## Eligibility +## Committee Seats -A person is eligible to become a member of the SC if and only if their home facility is able to allocate at least a half FT, or an equivalent effort, to sustain the Project. +The following rules govern which contributing organizations hold seats on the SC. -## Representation +### Eligibility + +Each [_contributing organization_](CONTRIBUTING-ORGANIZATIONS.md) may hold one seat on the Steering Committee. The organization should confirm that their representative has authority for strategic decisions, such as allocating personnel for SciCat development. + +### Adding a Contributing Organization + +An eligible contributing organization may apply for a seat by contacting the PLs. Admission requires approval by a majority of the existing SC members, following confirmation of the organization's eligibility. + +### Yearly Review + +During the annual meeting, each contributing organization should state the effort it will allocate for the following year. -Each supporting facility is granted a number of votes equivalent to the number of half FTs that is able to dedicate to the Project. -The number of votes are distributed among the members representing the facility. The maximum number of facility members is equal to the number of half FTs allocated by the facility. +### Losing Representation -## Posting Duration +If a contributing organization no longer meets the eligibility criteria, the SC may vote to remove its seat. Removal requires a majority vote of the remaining SC members. An organization that loses its seat relinquishes all associated voting rights. -Memberships in the SC are not time bounded. -The list of the supporting facility and their effort will be updated once year. We will strive to generate the updated list at the in-person meeting, although it will not be guaranteed it. The new efforts will guide the adjustment to members of the SC. -The participating facility has the responsibility to manage its membership to the SC and nominate a new member if a current one is stepping down. If no new member is nominated, the supporting facility will relinquish their representation and voting power. +## Representatives -## Resignation +The following rules govern the individuals appointed by each contributing organization to fill its SC seat. -A member of the Steering Committee can resign at any time. -A resigning member should inform the Project members (the SC, the PL and TL) with a written communication posted in the official project channels. +### Appointment -## Effort evaluation +Each contributing organization appoints one representative to fill its SC seat. The representative speaks and votes on behalf of the organization. + +### Resignation + +A representative may resign at any time by informing the SC, the PL, and the TL through the official project channels. + +### Replacement + +When a representative steps down, the contributing organization may nominate a replacement, subject to approval by the SC. If no replacement is nominated or approved within a reasonable time, the contributing organization relinquishes its seat. + +## Representation -During the yearly meeting, each contributing facility is required to state the effort allocated for the following year, so representation in the SC can be adjusted. +Each member of the Steering Committee holds one vote, regardless of their organization's level of contribution. *** Licensed under the [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License. diff --git a/governance-entities/TECHNICAL-LEADERS.md b/governance-entities/TECHNICAL-LEADERS.md index c4b7322..7bac85c 100644 --- a/governance-entities/TECHNICAL-LEADERS.md +++ b/governance-entities/TECHNICAL-LEADERS.md @@ -3,9 +3,9 @@ ## Abbreviation TL = Technical Leader +PL = [Project Leaders](./PROJECT-LEADERS.md) CC = [Contributors Community](./CONTRIBUTORS-COMMUNITY.md) SS = [Supported Project](../project-components/SUPPORTED-PROJECTS.md) -VB = [Voting Body](./VOTING-BODY.md) ## Description @@ -28,12 +28,11 @@ TL's responsibilities are: Any member of the Contributors Community (CC) can become a TL, given that he/she proves the required skills. -## Nomination Process +## Appointment -A TL prospect is nominated through a public announcement on the official channels. The nomination for a TL position should follow the process described in the [Nomination](../procedures/NOMINATION.md) section. A TL is official after winning an election by the VB (see [Voting](../procedures/VOTING.md)). +A TL is appointed by the Project Leaders (PL) following a public announcement of the open position on the official channels. The appointment becomes official once the PL confirm the candidate and the name is listed in the relevant file under `roles/` and on the Project website. -The name of the TL must be listed in the relevant file under `roles/` and the Project website and updated following election results. -For supported project, the project repository should contain a file named GOVERNANCE.md listing the name of the official TL and, possibly, the official maintainers +For supported projects, the project repository should contain a file named GOVERNANCE.md listing the name of the official TL and, where applicable, the official maintainers. ## Posting Duration diff --git a/governance-entities/USERS-COMMUNITY.md b/governance-entities/USERS-COMMUNITY.md deleted file mode 100644 index 56fc149..0000000 --- a/governance-entities/USERS-COMMUNITY.md +++ /dev/null @@ -1,44 +0,0 @@ -# Users Community - -## Description - -We consider a user any person who uses, interact, and/or works with SciCat. -The _user community_ is the entity encompassing all the users. - -## Membership - -There are no barriers to become member of the users group and actively participate to users group meetings. - -## Responsibilities - -The users group does not have any assigned responsibilities nor duties, although its members are encouraged, welcome and, at times, asked to provide feedback and opinions on specific topic. -They are instrumental in guiding the project vision and effort allocation. - -## Meetings - -Once or twice a year a townhall meeting dedicated to the user community will be organized by the Project. -The objectives are to facilitate the communication between the leadership and the users community, specifically important topics are: - -- improve SciCat as a whole, -- improve user experience, -- dissseminate relevant knowledge, -- collect and distil feedback on usability and future features. -Dates and location of the user meeting will advertise through the Project channels - -### Local meetings - -Users are encouraged to organize local meetings in their home institution, geographic area, or science domain. The general objectives of local meetings are to discuss any topic related to the Project in a smaller and more focused setting. - -## User Feedback - -User feedback should be provide through the official channels: - -- slack posts, -- github issues, -- emails to the interested parties, -- direct contact with contributors. - -Users can participate to the contributors meetings upon request. They are highly encouraged to inform the meeting organizers if they want any specific topic on the agenda. They should respect the meeting agenda. - -*** -Licensed under the [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License. diff --git a/procedures/AMENDMENTS.md b/procedures/AMENDMENTS.md index 007366e..80f2feb 100644 --- a/procedures/AMENDMENTS.md +++ b/procedures/AMENDMENTS.md @@ -17,10 +17,11 @@ This document defines how the SciCat governance documents are amended after init Amendments apply to the following documents: - `governance-entities/` -- `roles/` - `procedures/` -Documents under `other/`, `project-components` and `utils/` are not subject to this procedure. They may be updated with approval by the Project Leaders (PL). +Documents under `other/`, `project-components` and `utils/` are not subject to this procedure. +They may be updated with approval by the Project Leaders (PL). +Documents in `roles/` will be updated with the current membership following elections and appointments. ## Document Versions @@ -41,17 +42,10 @@ Any Active Contributor may propose an amendment by pull request to this reposito ### Approval -An amendment requires approval from both voting bodies: +An amendment requires approval by a two-thirds supermajority of the SC. -1. **SC** — at least two-thirds (2/3) of votes cast -2. **AC** — at least two-thirds (2/3) of votes cast - -### Quorum - -The same quorum requirements as [Ratification](./RATIFICATION.md#quorum) apply: - -- **SC:** at least 2/3 of SC members must participate -- **AC:** at least 15 Active Contributors must participate +At least two-thirds (2/3) of SC members must participate (in person or remotely). If +quorum is not met, the vote does not take effect and may be rescheduled. ### Venue and Timing diff --git a/procedures/MEMBER_EARLY_DISMISSAL.md b/procedures/MEMBER_EARLY_DISMISSAL.md index 9e9eb1f..7a1f862 100644 --- a/procedures/MEMBER_EARLY_DISMISSAL.md +++ b/procedures/MEMBER_EARLY_DISMISSAL.md @@ -2,9 +2,9 @@ ## Abbreviations and Links -AC = [Active Collaborators](../governance-entities/CONTRIBUTORS-COMMUNITY.md) -PL = [Project Leaders](../governance-entities/PROJECT-LEADERS.md) -SC = [Steering Committee](../governance-entities/STEERING-COMMITTEE.md) +AC = [Active Collaborators](../governance-entities/CONTRIBUTORS-COMMUNITY.md) +PL = [Project Leaders](../governance-entities/PROJECT-LEADERS.md) +SC = [Steering Committee](../governance-entities/STEERING-COMMITTEE.md) Project = [SciCat Project](../project-components/SCICAT-PROJECT.md) ## Description @@ -15,17 +15,17 @@ At any time, a group of at least three Project AC can present the request for a - the member has been disrespectful to other Project members or any stakeholder - the member has been in clear violation of the code of conduct. -The request should be submitted to the PL, which will trigger the early dismissal protocol. +The request should be submitted to the PL, which will trigger the early dismissal protocol. If the PL wrongly decide to not take any action, the request might brought the attention of the SC. -In the extreme case of harrasment, the victim can reach out directly any PL or the SC, which has the duty to start the early dismissal protocol and manage in sansible way the initial communication. +In the extreme case of harassment, the victim can reach out directly any PL or the SC, which has the duty to start the early dismissal protocol and manage in sensible way the initial communication. ## Protocol Once the protocol is active, the subject of the protocol, should put on hold all of his/her duties. The PL and, if needed, the SC will hear all the parties involved. -If a reasonable agreement can be reached between the parties involved, the PL will document such agreement and make sure that the agreement is enforce and followed through. -If no reasonable agreement can be reached, the situation is escalated and a vote on the matter will be called. The vote will decide the early dismissal of the member subject of the protocol. -The whole process should be documented for fairness and later review. In case of harrassment, the identity of the victim should be protected and revealed only with the victim's agreement +If a reasonable agreement can be reached between the parties involved, the PL will document such agreement and make sure that the agreement is enforce and followed through. +If no reasonable agreement can be reached, the situation is escalated and a vote on the matter will be called. The vote will decide the early dismissal of the member subject of the protocol. +The whole process should be documented for fairness and later review. In case of harassment, the identity of the victim should be protected and revealed only with the victim's agreement *** Licensed under the [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License. diff --git a/procedures/NOMINATION.md b/procedures/NOMINATION.md index ad1c9db..847766f 100644 --- a/procedures/NOMINATION.md +++ b/procedures/NOMINATION.md @@ -26,7 +26,7 @@ Candidates for open positions as Project Leader or Technical Leader of core or s - direct email to one or more Project Leaders or Steering Committee members - a posting on the Official Project Channels. - each candidate should have the support from at least two other project members. One of them should be from a different institution. -- the nomination can be initiate directly by the candidate or by one of the supporting members. +- the nomination can be initiate directly by the candidate or by one of the contributing organizations. - the nomination becomes official when listed in the relevant file under `roles/` ## Important diff --git a/procedures/PROJECT_ARCHIVAL.md b/procedures/PROJECT_ARCHIVAL.md index 2d57a02..4ea6e70 100644 --- a/procedures/PROJECT_ARCHIVAL.md +++ b/procedures/PROJECT_ARCHIVAL.md @@ -2,14 +2,14 @@ ## Abbreviations and Links -SP = [Supported Project](../project-components/SUPPORTED-PROJECTS.md) -CC = [Core Component](../project-components/SCICAT-CORE.md) -PL = [Project Leaders](../governance-entities/PROJECT-LEADERS.md) -PC = [Project Channels](../project-components/PROJECT-CHANNELS.md) +SP = [Supported Project](../project-components/SUPPORTED-PROJECTS.md) +CC = [Core Component](../project-components/SCICAT-CORE.md) +PL = [Project Leaders](../governance-entities/PROJECT-LEADERS.md) +PC = [Project Channels](../project-components/PROJECT-CHANNELS.md) ## Description -Any Project active member, including Project Leaders and Sttering Committee members, are allowed to propose any project for archival if a valid reason is present. +Any Project active member, including Project Leaders and Steering Committee members, are allowed to propose any project for archival if a valid reason is present. ## Archival Reasons diff --git a/procedures/PROJECT_DECISION.md b/procedures/PROJECT_DECISION.md index f1aef90..83926c5 100644 --- a/procedures/PROJECT_DECISION.md +++ b/procedures/PROJECT_DECISION.md @@ -2,15 +2,27 @@ ## Abbreviations and Links -Project = [SciCat Project](../project-components/SCICAT-PROJECT.md) -PL = [Project Leaders](../governance-entities/PROJECT-LEADERS.md) -SC = [Steering Committee](../governance-entities/STEERING-COMMITTEE.md) -VB = [Voting Body](../governance-entities/VOTING-BODY.md) +Project = [SciCat Project](../project-components/SCICAT-PROJECT.md) +PL = [Project Leaders](../governance-entities/PROJECT-LEADERS.md) +SC = [Steering Committee](../governance-entities/STEERING-COMMITTEE.md) ## Description -Any decision that impact the Project, as a whole on any of its components, should be supported with a proper voting of the eligible voters. -Eligible voters are clearly defined in the Voting Body section. Any changes needed to the Voting Body should be supported by the Project Leaders, with the support of the Steering Committee, and clearly and publicly stated in the voting announcement. +The Project Leaders (PL) are jointly responsible for decisions affecting the Project. + +## Major Decisions + +For decisions with significant impact on the Project or its community, the PL will determine suitable steps to achieve community consensus before deciding. This may include: + +- discussion at contributor meetings, +- a formal vote following the [Voting](./VOTING.md) procedure, or +- consultation with the Steering Committee (SC). + +The PL will publicly announce major decisions and the process used to reach them through the official project channels. + +## SC Oversight + +The SC may choose to override a PL decision or request additional actions. Any SC member may request a meeting of the SC to review a PL decision. *** Licensed under the [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License. diff --git a/procedures/RATIFICATION.md b/procedures/RATIFICATION.md index 8052f7e..39a2f24 100644 --- a/procedures/RATIFICATION.md +++ b/procedures/RATIFICATION.md @@ -31,25 +31,15 @@ The ratification vote will be applied to the `main` branch of this repository. A ### Voting Bodies -Ratification requires approval from two separate voting bodies: +Ratification requires approval by a two-thirds supermajority of the SC. -1. **Steering Committee (SC)** — unanimous approval -2. **Active Contributors (AC)** — approval by at least two-thirds (2/3) of votes cast - -Only Active Contributors may vote in the AC ratification. Past contributors who are not Active Contributors are not eligible. - -### Quorum - -- **SC:** at least two-thirds (2/3) of SC members must participate (in person or remotely). -- **AC:** at least fifteen (15) Active Contributors must participate (in person or remotely). - -If quorum is not met, the vote does not take effect and may be rescheduled. +At least two-thirds (2/3) of SC members must participate (in person or remotely). If +quorum is not met, the vote does not take effect and may be rescheduled. ### Venue and Timing -The ratification vote will be held at the 2026 SciCatCon meeting. - -Remote participation is permitted and counts toward quorum and vote totals. +A draft of the governance documents was presented to the SC at the 2026 SciCatCon +meeting for discussion. The final version will be ratified by remote vote of the SC. ### Administration @@ -61,7 +51,9 @@ Upon successful ratification, the approved branch will be tagged as `v1.0.0` and ## Initial Elections -Elections for Project Leader (PL) and Technical Leader (TL) positions will be held following approval of the governance documents. Nominations follow the [Nomination](./NOMINATION.md) procedure. Elections follow the [Voting](./VOTING.md) procedure, except where this document or the pre-ratification administration provisions apply. +Elections for Project Leader (PL) positions will be held at SciCatCon 2026. +Nominations follow the [Nomination](./NOMINATION.md) procedure. +Elections follow the [Voting](./VOTING.md) procedure, except where this document or the pre-ratification administration provisions apply. ## Relationship to Other Procedures @@ -73,7 +65,7 @@ Elections for Project Leader (PL) and Technical Leader (TL) positions will be he Ratification results must be recorded and made publicly accessible through the official PC, including: -- the commit under vote +- the git commit under vote - quorum attainment for each voting body - vote totals - the effective date or release tag diff --git a/procedures/SUPPORTED_PROJECT_REQUEST.md b/procedures/SUPPORTED_PROJECT_REQUEST.md index 3c562d0..a94e476 100644 --- a/procedures/SUPPORTED_PROJECT_REQUEST.md +++ b/procedures/SUPPORTED_PROJECT_REQUEST.md @@ -2,10 +2,10 @@ ## Abbreviations and Links -SP = [Supported Project](../project-components/SUPPORTED-PROJECTS.md) -PC = [Project Channels](../project-components/PROJECT-CHANNELS.md) -PL = [Project Leaders](../governance-entities/PROJECT-LEADERS.md) -Project = [Scicat Project](../project-components/SCICAT-PROJECT.md) +SP = [Supported Project](../project-components/SUPPORTED-PROJECTS.md) +PC = [Project Channels](../project-components/PROJECT-CHANNELS.md) +PL = [Project Leaders](../governance-entities/PROJECT-LEADERS.md) +Project = [SciCat Project](../project-components/SCICAT-PROJECT.md) ## Eligibility @@ -20,12 +20,12 @@ The Supported Project Request can be submitted via the official Project Channels - documentation highlighting how to install, configure and run the application, if project provides an application - a compelling reason for acquiring the status of the Supported Project - a project technical leader -- a group of supporting members, if possible +- a group of supporting contributing organizations - current license the code is released under ## Procedure -The Project Leaders will make sure to present the case to the relevant stakeholders (Collaborators, Steering Committee, Users community) to the best suitable way given time and opportunities constraints. The project Leaders should schedule a vote, leaving enough time for an open discussion. +The Project Leaders will make sure to present the case to the relevant stakeholders (Collaborators, Steering Committee, and the user community) to the best suitable way given time and opportunities constraints. The project Leaders should schedule a vote, leaving enough time for an open discussion. ## Results diff --git a/procedures/VOTING.md b/procedures/VOTING.md index 02326a0..7e2effe 100644 --- a/procedures/VOTING.md +++ b/procedures/VOTING.md @@ -22,16 +22,12 @@ An official announcement should be made through the official PC, and it should i A discussion period should precede the time of the voting. Any discussion may be conducted in person or electronically by text, voice, or video. The discussion will be open to the public and should be accessible through the official PC. -## Decision Making - -When a voting is requested and scheduled, although the Project strive to reach a consensus, the outcome will always be decided by majority of the voting body. -If a proper outcome cannot be reached at the time of the Voting, the PL have the authority to reschedule the voting or take upon themselves to selected the outcome based on their good faith consideration of a number of factors, including the dominant view of the all the stakeholders and nature of support and objections. -If a decision cannot be reached at all, the PL will seek out the guidance of the SC. - ## Vote In any voting, each member of the VB will have one vote, and all the votes are equal. +Unless otherwise specified, votes will be decided by simple majority. + ### Delegation In the case of absence during a vote, VB members may temporarily delegate their vote to another person by emailing the Project Leaders. diff --git a/project-components/PROJECT-CHANNELS.md b/project-components/PROJECT-CHANNELS.md index 6d20835..64846dd 100644 --- a/project-components/PROJECT-CHANNELS.md +++ b/project-components/PROJECT-CHANNELS.md @@ -7,7 +7,7 @@ Project = [SciCat Project](./SCICAT-PROJECT.md) ## Description -Project channels PC are all the methods that the Project use to communicate with its collaborators, users and facilities. +Project channels PC are all the methods that the Project use to communicate with its collaborators, users and contributing organizations. At the moment of this writing, official PC are: - [Official website](https://scicatproject.org) diff --git a/project-components/SUPPORTED-PROJECTS.md b/project-components/SUPPORTED-PROJECTS.md index 4beaa23..7037235 100644 --- a/project-components/SUPPORTED-PROJECTS.md +++ b/project-components/SUPPORTED-PROJECTS.md @@ -1,27 +1,27 @@ # Supported Projects -## Abbrevations +## Abbreviations -SP = Supported Project -PL = [Project Leader(s)](../governance-entities/PROJECT-LEADERS.md) -SC = [Steering Committee](../governance-entities/STEERING-COMMITTEE.md) -TL = [Technical Leader(s)](../governance-entities/TECHNICAL-LEADERS.md) +SP = Supported Project +PL = [Project Leader(s)](../governance-entities/PROJECT-LEADERS.md) +SC = [Steering Committee](../governance-entities/STEERING-COMMITTEE.md) +TL = [Technical Leader(s)](../governance-entities/TECHNICAL-LEADERS.md) Project = [SciCat Project](./PROJECT-CHANNELS.md) ## Description -__Support Projects__ are all the projects adopted by the SciCat community and having a repository on the github Project page, but outside the [SciCat Core](./SCICAT-CORE.md). +__Support Projects__ are all the projects adopted by the SciCat community and having a repository on the github Project page, but outside the [SciCat Core](./SCICAT-CORE.md). ## Governance -SP are officially covered under and have to adire to the Project governance described in these documents. -They also have to follow the [code of conduct](../other/CODE-OF-CONDUCT.md) included in the Project geovernance. +SP are officially covered under and have to adhere to the Project governance described in these documents. +They also have to follow the [code of conduct](../other/CODE-OF-CONDUCT.md) included in the Project governance. ## Resources and Support -Each SP is granted its own repository under the SciCat project umbrella and supported by the Project community. -SP are encouraged to manage their leadership on their own, although following the rules described under the TL section. They might request direct involvement of and seek advice from the PL and the SC. -SP may be orphaned, meaning they do have no project leadership and/or contributors. In such case, it is responsability of the PL and the SC to step in, temporarily lead the project and advocate for new leadership and/or contributors. They can also decide to end the SP and archive the repository. +Each SP is granted its own repository under the SciCat project umbrella and supported by the Project community. +SP are encouraged to manage their leadership on their own, although following the rules described under the TL section. They might request direct involvement of and seek advice from the PL and the SC. +SP may be orphaned, meaning they do have no project leadership and/or contributors. In such case, it is responsibility of the PL and the SC to step in, temporarily lead the project and advocate for new leadership and/or contributors. They can also decide to end the SP and archive the repository. ## Process diff --git a/roles/ADVISORY-BOARDS.md b/roles/ADVISORY-BOARDS.md index 3cb4255..a717189 100644 --- a/roles/ADVISORY-BOARDS.md +++ b/roles/ADVISORY-BOARDS.md @@ -4,15 +4,15 @@ This document lists the Organization's active Advisory Boards or AB and their me ## Advisory Boards -| **Id** | **Name** | **Start Date** | **Esitmated End Date** | **Description** | **Deliverables** | -| --- | --- | --- | --- | --- | --- | -| ... | ... | ... | ... | ... | ... | +| **Id** | **Name** | **Start Date** | **Estimated End Date** | **Description** | **Deliverables** | +| ------ | -------- | -------------- | ---------------------- | --------------- | ---------------- | +| ... | ... | ... | ... | ... | ... | ## Members | **Board Id** | **NAME** | **Email** | **GitHub Username** | **Affiliated Organization** | -| --- | --- | --- | --- | --- | -| ... | ... | ... | ... | ... | +| ------------ | -------- | --------- | ------------------- | --------------------------- | +| ... | ... | ... | ... | ... | *** Licensed under the [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License. diff --git a/roles/PROJECT-LEADERS.md b/roles/PROJECT-LEADERS.md index 4a5b599..7234c1c 100644 --- a/roles/PROJECT-LEADERS.md +++ b/roles/PROJECT-LEADERS.md @@ -1,12 +1,24 @@ # Project Leaders (PL) -This document lists nominated candidates for Project Leader (PL) positions. Entries reflect nominations under the [Nomination](../procedures/NOMINATION.md) procedure and are updated to record election results. By adding your name to this document, you are agreeing to abide by all Organization policies, including the organizational charter document, the code of conduct, and the antitrust policy. +## Current leaders -| **POSITION** | **NAME** | **GitHub Handle** | **Affiliated Organization** | **Mandate started** | -| --- | --- | --- | --- | --- | -| Project Leader | Massimiliano (Max) Novelli | nitrosx | ESS | 2026-01-01 | -| Project Leader | Laura Shemilt | LAShemilt | RFI | 2026-01-01 | -| Project Leader | Spencer Bliven | sbliven | PSI | 2026-06-30 | +The current Project Leader (PL) members are: + +| **POSITION** | **NAME** | **GitHub Handle** | **Organization** | **Date of Election** | +| -------------- | -------------------------- | ----------------- | ---------------- | -------------------- | +| Project Leader | Massimiliano (Max) Novelli | nitrosx | ESS | 2026-06-30 | +| Project Leader | Laura Shemilt | LAShemilt | RFI | 2026-06-30 | +| Project Leader | Spencer Bliven | sbliven | PSI | 2026-06-30 | + +PLs were ratified by the SC on 2026-06-30. + +## Nominations + +This section lists nominated candidates Project Leader (PL) positions. Entries reflect nominations under the [Nomination](../procedures/NOMINATION.md) procedure and are updated to record election results. By adding your name to this document, you are agreeing to abide by all Organization policies, including the organizational charter document, the code of conduct, and the antitrust policy. + +| **POSITION** | **NAME** | **GitHub Handle** | **Organization** | +| ------------ | -------- | ----------------- | ---------------- | +| | | | | *** Licensed under the [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License. diff --git a/roles/STEERING-COMMITTEE.md b/roles/STEERING-COMMITTEE.md index 382e9b2..f66ada5 100644 --- a/roles/STEERING-COMMITTEE.md +++ b/roles/STEERING-COMMITTEE.md @@ -2,30 +2,29 @@ This document lists the members of the Organization's Steering Committee or SC. -Members from supporting organizations and facilities may be added once approved by the Steering Committee as described in the Governance document. +Members from contributing organizations may be added once approved by the Steering Committee as described in the Governance document. -By adding your name to this list you are agreeing to abide by all Organization polices, including the organizational charter document, the code of conduct, and the antitrust policy. +By adding your name to this list you are agreeing to abide by all Organization polices, including the organizational charter document, the code of conduct, and the antitrust policy. If you are serving on the Steering Committee because of your affiliation with another organization (designated below), you represent that you have authority to bind that organization to these policies. -__IMPORTANT__: +**IMPORTANT**: - _Membership is still preliminary and will need to be confirmed_ - _please comment or reach out to the Project Leaders with any feedback or comment_ -| __NAME__ | __GitHub Handle__ | __Supporting Organization__ | __Status__ | -| --- | --- | --- | --- | -| Fredrik Bolmsten | --- | ESS | Preliminary | -| Alun Ashtun | --- | PSI | Preliminary | -| Paolo Mutti | --- | ILL | Preliminary | -| Mark Basham | --- | RFI | Preliminary | -| Bridget Murphy | --- | DAPHNE | Preliminary | -| Philipp Neumann | --- | DESY | Preliminary | -| Daphne van Dijken | --- | Dectris | Preliminary | -| Marjam Lindberg | --- | MaxIV | Preliminary | -| Majid Ounsy | --- | SOLEIL | Preliminary | -| --- | --- | --- | --- | +| **NAME** | **GitHub Handle** | **Organization** | **Status** | +| ----------------- | ----------------- | ---------------- | ----------- | +| Fredrik Bolmsten | --- | ESS | Preliminary | +| Alun Ashtun | --- | PSI | Preliminary | +| Paolo Mutti | --- | ILL | Preliminary | +| Mark Basham | --- | RFI | Preliminary | +| Bridget Murphy | --- | DAPHNE | Preliminary | +| Philipp Neumann | --- | DESY | Preliminary | +| Daphne van Dijken | --- | Dectris | Preliminary | +| Marjam Lindberg | --- | MaxIV | Preliminary | +| Majid Ounsy | --- | SOLEIL | Preliminary | *** Licensed under the [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License. diff --git a/roles/TECHNICAL-LEADERS.md b/roles/TECHNICAL-LEADERS.md index 17f050c..1d4768d 100644 --- a/roles/TECHNICAL-LEADERS.md +++ b/roles/TECHNICAL-LEADERS.md @@ -2,11 +2,10 @@ This document lists nominated candidates for Technical Leader (TL) positions for Core efforts or Supported projects. Entries reflect nominations under the [Nomination](../procedures/NOMINATION.md) procedure and are updated to record election results. By adding your name to this document, you are agreeing to abide by all Organization policies, including the organizational charter document, the code of conduct, and the antitrust policy. -| **EFFORT/PROJECT** | **NAME** | **GitHub Handle** | **Affiliated Organization** | **Mandate started** | -| --- | --- | --- | --- | --- | -| Core effort or Supported Project | Name | Git Handle | Organization | Started | -| BE | Junje Quan | Junjiequan | ESS | 2026-01-01 | -| --- | Carlo Minotti | minottic | PSI | 2026-06-30 | +| **EFFORT/PROJECT** | **NAME** | **GitHub Handle** | **Organization** | **Mandate started** | +| -------------------------------- | ------------- | ----------------- | ---------------- | ------------------- | +| BE | Junje Quan | Junjiequan | ESS | 2026-01-01 | +| | Carlo Minotti | minottic | PSI | 2026-06-30 | *** Licensed under the [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License. diff --git a/utils/create_single_document.bash b/utils/create_single_document.bash index beb2914..9e8151f 100755 --- a/utils/create_single_document.bash +++ b/utils/create_single_document.bash @@ -1,4 +1,5 @@ #!/bin/bash +set -e # Use provided suffix or generate timestamp SUFFIX="${1:-$(date +%Y%m%d%H%M%S)}" @@ -44,7 +45,7 @@ pandoc \ -V fontsize=6pt # fix links in combined markdown -sed -Ei 's|\((\./)?[^)]*/([A-Z-]+)\.md\)|(#\L\2)|g' "scicat_governance_full_${SUFFIX}.md" +sed -E -i'' 's|\((\./)?[^)]*/([A-Z-]+)\.md\)|(#\L\2)|g' "scicat_governance_full_${SUFFIX}.md" # remove temporary files rm -f cover.md combined.md diff --git a/utils/manifest.txt b/utils/manifest.txt index 626e9cf..9af924d 100644 --- a/utils/manifest.txt +++ b/utils/manifest.txt @@ -1,11 +1,10 @@ ../README.md -../governance-entities/USERS-COMMUNITY.md ../governance-entities/CONTRIBUTORS-COMMUNITY.md ../governance-entities/TECHNICAL-LEADERS.md ../governance-entities/PROJECT-LEADERS.md ../governance-entities/STEERING-COMMITTEE.md ../governance-entities/ADVISORY-GROUPS.md -../governance-entities/FACILITIES.md +../governance-entities/CONTRIBUTING-ORGANIZATIONS.md ../governance-entities/VOTING-BODY.md ../project-components/SCICAT-PROJECT.md ../project-components/SCICAT-CORE.md