community: Add governance page #175

gabrielmocanu · 2022-12-23T03:20:54Z

Signed-off-by: Gabriel Mocanu [email protected]

razvand

Thanks, @gabrielmocanu . I think this document will be very useful in the community. See my comments, we still have content to add to make it useful.

Aim to move the content from the README.md file in the governance repository to this page.

content/en/community/governance.md

razvand · 2022-12-28T06:59:27Z

content/en/community/governance.md

+
+This document describes the rules and governance of the project.
+It is meant to be followed by all the developers that are contributing.
+


I would add a summary on the scope of governance and the resources we use.

Scope is organizing the community, establishing and following guidelines, ensuring an effective development environment.

As development takes place primarily using Git and GitHub, governance is focused on it. Discord is used for community interactions (text, meetings). HackMD and Google Drive are used for collaborative text items. Google calendar stores meeting information.

Governance is thus concerned with:

accounting for community members and their adherence to specialized teams (named special interest groups - SIGs)

providing responsibilities as roles (reviewers, maintainers. community leaders) for experienced members of the community

assigning task ownership

accounting for task progress (as GitHub issues, PRs, GitHub projects)

ensuring a consistent release schedule

defining responsibilities for community leadership roles

defining and following project roadmaps

I would then structure the rest of the content in connection to these items.

I would first have a section "## Governance Scope and Terms" and define:

community members (implemented as GitHub IDs and Discord IDs)

teams / SIGs (implemented as GitHub teams, Discord roles)

roles (implemented as GitHub teams, Discord roles)

reviewers & maintainers (implemented as GitHub PR reviewers and assignees)

community leadership (currently implemented as meetings with community leaders with given roles)

tasks / projects / features (implemented as GitHub issues and / or GitHub projects)

contributions (implemented as GitHub PRs, aggregated in GitHub projects)

task / project ownership (implemented as GitHub issue assignee)

roadmap, a collection of features requests (small issues not included) (implemented as GitHub issues, tagged, listed on HackMD)

releases (implemented as GitHub issues milestones, available on GitHub releases, release notes developed on HackMD)

Then you would detail sections with each of those.

content/en/community/governance.md

- Add governance scope and terms descriptions - Add SIG section - Add Community Leadership section - Add Meetings section - Add Roles section - Add Tasks / Projects section - Add Contributions section - Add Roadmap section - Add Releases section - Add values section Co-authored-by: Razvan Deaconescu <[email protected]> Signed-off-by: Mocanu Viorel Gabriel <[email protected]>

gabrielmocanu · 2023-01-14T15:21:53Z

@razvand I added the section you mentioned above.
I didn't mark the conversations as solved since I don't know if you want to add something else.
I think for some sections I can add more text, but right now I don't know what to add.(e.g. Roadmap, Releases, Tasks / Projects)

razvand

@gabrielmocanu, see my comments.

content/en/community/governance.md

Apply suggestions from code review Co-authored-by: Razvan Deaconescu <[email protected]> Signed-off-by: Mocanu Viorel Gabriel <[email protected]>

gabrielmocanu · 2023-01-26T23:04:32Z

@razvand
I applied your suggestions.

gabrielmocanu · 2023-04-11T22:03:49Z

@StefanJum @razvand Bump on this.

StefanJum

Thanks @gabrielmocanu, see the comments.

StefanJum · 2023-04-12T08:43:05Z

content/en/community/governance.md

+* SIGs (_Special Interest Groups_) are persistent open groups that focus on a part of the project.
+   The purpose of a SIG is to own and develop a set of Unikraft components.
+
+- Community Leadership - The community leaders are responsible for the overall project and for driving the project roadmap.


Suggested change

- Community Leadership - The community leaders are responsible for the overall project and for driving the project roadmap.

* Community Leadership: The community leaders are responsible for the overall project and for driving the project roadmap.

StefanJum · 2023-04-12T08:44:00Z

content/en/community/governance.md

+
+* SIGs (_Special Interest Groups_) are persistent open groups that focus on a part of the project.
+   The purpose of a SIG is to own and develop a set of Unikraft components.
+


Suggested change

Remove the empty lines between list items.

StefanJum · 2023-04-12T08:44:08Z

content/en/community/governance.md

+  Anyone is welcome to join these meetings.
+  The meetings are used to discuss topics and report progress.
+* Roles: Roles and responsibilities of the various members of the community are defined in the [governance repository](https://github.com/unikraft/governance).
+


Suggested change

StefanJum · 2023-04-12T08:44:14Z

content/en/community/governance.md

+* Roles: Roles and responsibilities of the various members of the community are defined in the [governance repository](https://github.com/unikraft/governance).
+
+* Tasks / Projects: The project uses GitHub issues and projects to track tasks and projects.
+


Suggested change

StefanJum · 2023-04-12T08:44:22Z

content/en/community/governance.md

+
+* Contributions: A contribution is any direct or indirect work that is produced by a contributor and accepted by the project.
+  Examples of contributions include code, pull requests, issues, documentation and community participation in events.
+


Suggested change

StefanJum · 2023-04-12T08:59:43Z

content/en/community/governance.md

+This means that when you look at at all the Unikraft teams on GitHub, it will create something like this:
+
+```
+unikraft


Use tree --charset=ascii when doing this.

StefanJum · 2023-04-12T09:02:39Z

content/en/community/governance.md

+The purpose of organising the teams in this way is to:
+
+1. Allow maintainers and reviewers to have their own internal groups for discussion, and to use the available teams feature of GitHub for their desired purposes for these particular role types;
+2. Allow for quick reference of the groups of people by their role in any `CODEOWNERS` file and in the CI/CD with the syntax `@sig-$NAME`, or `@maintainers-$NAME` or `@reviewers-$NAME`;


Suggested change

2. Allow for quick reference of the groups of people by their role in any `CODEOWNERS` file and in the CI/CD with the syntax `@sig-$NAME`, or `@maintainers-$NAME` or `@reviewers-$NAME`;

1. Allow for quick reference of the groups of people by their role in any `CODEOWNERS` file and in the CI/CD with the syntax `@sig-$NAME`, or `@maintainers-$NAME` or `@reviewers-$NAME`;

StefanJum · 2023-04-12T09:02:54Z

content/en/community/governance.md

+
+1. Allow maintainers and reviewers to have their own internal groups for discussion, and to use the available teams feature of GitHub for their desired purposes for these particular role types;
+2. Allow for quick reference of the groups of people by their role in any `CODEOWNERS` file and in the CI/CD with the syntax `@sig-$NAME`, or `@maintainers-$NAME` or `@reviewers-$NAME`;
+3. We can reference all members of the Special Interest Groups, whether maintainer, reviewer or simply as a member with the handle `@sig-$NAME`;


Suggested change

3. We can reference all members of the Special Interest Groups, whether maintainer, reviewer or simply as a member with the handle `@sig-$NAME`;

1. Reference all members of the Special Interest Groups, whether maintainer, reviewer or simply as a member with the handle `@sig-$NAME`;

StefanJum · 2023-04-12T09:03:13Z

content/en/community/governance.md

+2. Allow for quick reference of the groups of people by their role in any `CODEOWNERS` file and in the CI/CD with the syntax `@sig-$NAME`, or `@maintainers-$NAME` or `@reviewers-$NAME`;
+3. We can reference all members of the Special Interest Groups, whether maintainer, reviewer or simply as a member with the handle `@sig-$NAME`;
+
+To join a Special Interest Group, create a pull request on [Governance repository](https://github.com/unikraft/governance) and add new line to the `members:` directive within the relevant team's YAML file, e.g.:


Suggested change

To join a Special Interest Group, create a pull request on [Governance repository](https://github.com/unikraft/governance) and add new line to the `members:` directive within the relevant team's YAML file, e.g.:

To join a Special Interest Group, create a pull request on the [Governance repository](https://github.com/unikraft/governance) and add new line to the `members:` directive within the relevant team's YAML file, e.g.:

StefanJum · 2023-04-12T09:24:23Z

content/en/community/governance.md

+The current list of community leaders is:
+- [Răzvan Deaconescu](https://github.com/razvand) - Community Management


Suggested change

The current list of community leaders is:

- [Răzvan Deaconescu](https://github.com/razvand) - Community Management

The current list of community leaders is:

- [Răzvan Deaconescu](https://github.com/razvand) - Community Management

gabrielmocanu marked this pull request as draft December 23, 2022 03:21

razvand requested changes Dec 28, 2022

View reviewed changes

gabrielmocanu force-pushed the gmocanu/governance-page branch from 575de8d to bf76cbb Compare January 14, 2023 15:19

gabrielmocanu marked this pull request as ready for review January 14, 2023 15:19

gabrielmocanu requested a review from razvand January 14, 2023 15:19

razvand requested changes Jan 22, 2023

View reviewed changes

Apply suggestions from code review

a54f09c

Apply suggestions from code review Co-authored-by: Razvan Deaconescu <[email protected]> Signed-off-by: Mocanu Viorel Gabriel <[email protected]>

andraprs mentioned this pull request Jan 31, 2023

Add Governance page #128

Open

StefanJum linked an issue Jan 31, 2023 that may be closed by this pull request

Add Governance page #128

Open

gabrielmocanu assigned razvand Apr 11, 2023

StefanJum requested changes Apr 12, 2023

View reviewed changes

razvand added the enhancement New feature or request label Aug 19, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

community: Add governance page #175

community: Add governance page #175

gabrielmocanu commented Dec 23, 2022

razvand left a comment

razvand Dec 28, 2022

razvand Dec 28, 2022

gabrielmocanu commented Jan 14, 2023

razvand left a comment

gabrielmocanu commented Jan 26, 2023

gabrielmocanu commented Apr 11, 2023

StefanJum left a comment

StefanJum Apr 12, 2023

StefanJum Apr 12, 2023

StefanJum Apr 12, 2023

StefanJum Apr 12, 2023

StefanJum Apr 12, 2023

StefanJum Apr 12, 2023

StefanJum Apr 12, 2023

StefanJum Apr 12, 2023

StefanJum Apr 12, 2023

StefanJum Apr 12, 2023


		This document describes the rules and governance of the project.
		It is meant to be followed by all the developers that are contributing.

	- Community Leadership - The community leaders are responsible for the overall project and for driving the project roadmap.
	* Community Leadership: The community leaders are responsible for the overall project and for driving the project roadmap.


		* SIGs (_Special Interest Groups_) are persistent open groups that focus on a part of the project.
		The purpose of a SIG is to own and develop a set of Unikraft components.

		* Roles: Roles and responsibilities of the various members of the community are defined in the [governance repository](https://github.com/unikraft/governance).

		* Tasks / Projects: The project uses GitHub issues and projects to track tasks and projects.


		* Contributions: A contribution is any direct or indirect work that is produced by a contributor and accepted by the project.
		Examples of contributions include code, pull requests, issues, documentation and community participation in events.

	2. Allow for quick reference of the groups of people by their role in any `CODEOWNERS` file and in the CI/CD with the syntax `@sig-$NAME`, or `@maintainers-$NAME` or `@reviewers-$NAME`;
	1. Allow for quick reference of the groups of people by their role in any `CODEOWNERS` file and in the CI/CD with the syntax `@sig-$NAME`, or `@maintainers-$NAME` or `@reviewers-$NAME`;

	3. We can reference all members of the Special Interest Groups, whether maintainer, reviewer or simply as a member with the handle `@sig-$NAME`;
	1. Reference all members of the Special Interest Groups, whether maintainer, reviewer or simply as a member with the handle `@sig-$NAME`;

	To join a Special Interest Group, create a pull request on [Governance repository](https://github.com/unikraft/governance) and add new line to the `members:` directive within the relevant team's YAML file, e.g.:
	To join a Special Interest Group, create a pull request on the [Governance repository](https://github.com/unikraft/governance) and add new line to the `members:` directive within the relevant team's YAML file, e.g.:

		The current list of community leaders is:
		- [Răzvan Deaconescu](https://github.com/razvand) - Community Management

community: Add governance page #175

Are you sure you want to change the base?

community: Add governance page #175

Conversation

gabrielmocanu commented Dec 23, 2022

razvand left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

gabrielmocanu commented Jan 14, 2023

razvand left a comment

Choose a reason for hiding this comment

gabrielmocanu commented Jan 26, 2023

gabrielmocanu commented Apr 11, 2023

StefanJum left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment