unikraft · gabrielmocanu · Dec 23, 2022 · Jan 26, 2023 · razvand · Dec 28, 2022
diff --git a/content/en/community/governance.md b/content/en/community/governance.md
@@ -0,0 +1,180 @@
+---
+title: Governance
+date: 2022-12-28T14:09:21+02:00
+draft: false
+weight: 600
+---
+
+## Governance
+
+Unikraft is an open source software (OSS) project.
+To ensure an effective way to drive the project, we use governance principles inspired from other OSS projects.
+The governance model is designed to provide structure around how decisions are made, how the various elements of our community interact, and how we work together to achieve our goals.
+
+## Governance Scope and Terms
+
+* SIGs (_Special Interest Groups_) are persistent open groups that focus on a part of the project.
-* SIGs (_Special Interest Groups_) are persistent open groups that focus on a part of the project.
+* SIGs (_Special Interest Groups_): Persistent open groups that focus on a part of the project.
-* SIGs (_Special Interest Groups_) are persistent open groups that focus on a part of the project.
+* SIGs (_Special Interest Groups_): 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.
- 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.
- 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.
+* Meetings: The project has regular meetings.
+  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).
+
-
-
+* 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.
+
-  
-  
+* Roadmap: The roadmap is a document that identifies the goals and direction of the project.
+  The roadmap is owned by the community leaders and is a living document that can be updated at any time.
+  The roadmap is used to help guide the decisions of the SIGs and the community leaders.
+
-
-
+* Releases: Stable versions of the project are released on a regular basis.
+
-
-
+* Values: a set of principles that define the culture, and how the community should work together.
+
+### Special Interest Groups (SIGs)
+
+The Unikraft OSS project is organised on the principle that "everything-is-a-library," whether they are a wrapper library for an external OSS project or library, an architecture, platform or application.
-The Unikraft OSS project is organised on the principle that "everything-is-a-library," whether they are a wrapper library for an external OSS project or library, an architecture, platform or application.
+The Unikraft OSS project is organized on the principle that "everything-is-a-library," whether they are a wrapper library for an external OSS project or library, an architecture, platform or application.
-The Unikraft OSS project is organised on the principle that "everything-is-a-library," whether they are a wrapper library for an external OSS project or library, an architecture, platform or application.
+The Unikraft OSS project is organized on the principle that "everything-is-a-library," whether they are a wrapper library for an external OSS project or library, an architecture, platform or application.
+There are also auxiliary repositories and projects which are part of the Unikraft OSS community:
+
+  * the command-line companion tool [`kraft`](https://github.com/unikraft/kraft)
+  * forks of upstream libraries
+  * application repositories
+  * other test / suppor repositories
+
+As a result, there are many repositories and directories within the [Unikraft core repository](https://github.com/unikraft/unikraft) which overlap and represent some interest or focus point.
+To address the growing ecosystem, the Unikraft OSS project is organised into self-governing Special Interest Groups (SIGs).
-To address the growing ecosystem, the Unikraft OSS project is organised into self-governing Special Interest Groups (SIGs).
+To address the growing ecosystem, the Unikraft OSS project is organized into self-governing Special Interest Groups (SIGs).
-To address the growing ecosystem, the Unikraft OSS project is organised into self-governing Special Interest Groups (SIGs).
+To address the growing ecosystem, the Unikraft OSS project is organized into self-governing Special Interest Groups (SIGs).
+Each SIG oversees some number of libraries, repositories or code and are in themselves responsible for maintaining and reviewing changes.
+This means there are dedicated maintainers and dedicated reviewers for each SIG.
+
+ > A list of all Special Interest Groups and their maintainers, reviewers and members can be found in [`teams/`](https://github.com/unikraft/governance/tree/main/teams).
+
+GitHub is the primary SCM used by Unikraft and it offers management tooling for organising persons via the [teams feature](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams).
-GitHub is the primary SCM used by Unikraft and it offers management tooling for organising persons via the [teams feature](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams).
+GitHub is the primary SCM used by Unikraft, and it offers management tooling for organizing persons via the [teams feature](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams).
-GitHub is the primary SCM used by Unikraft and it offers management tooling for organising persons via the [teams feature](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams).
+GitHub is the primary SCM used by Unikraft, and it offers management tooling for organizing persons via the [teams feature](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams).
+The provided tooling offers hierarchical team management, meaning there can exist a sub-team within an existing team.
+This feature is utilised in order to create the separation between "maintainers" and "reviewers" whilst still being part of the same SIG.
-This feature is utilised in order to create the separation between "maintainers" and "reviewers" whilst still being part of the same SIG.
+This feature is utilized in order to create the separation between "maintainers" and "reviewers" whilst still being part of the same SIG.
-This feature is utilised in order to create the separation between "maintainers" and "reviewers" whilst still being part of the same SIG.
+This feature is utilized in order to create the separation between "maintainers" and "reviewers" whilst still being part of the same SIG.
+Each SIG has its own team within the [Unikraft Github organisation](https://github.com/unikraft), identified with `sig-$NAME`.
+This represents an outer-most team and `maintainers-$NAME` and `reviewers-$NAME` representing two sub-teams within `sig-$NAME`.
+This means that when you look at at all the Unikraft teams on GitHub, it will create something like this:
-This means that when you look at at all the Unikraft teams on GitHub, it will create something like this:
+This means that when you look at all the Unikraft teams on GitHub, it will create something like this:
-This means that when you look at at all the Unikraft teams on GitHub, it will create something like this:
+This means that when you look at all the Unikraft teams on GitHub, it will create something like this:
+
+```
-```
+```text
-```
+```text
+unikraft
+├── sig-alloc
+│   ├── maintainers-alloc
+│   └── reviewers-alloc
+├── sig-test
+│   ├── maintainers-test
+│   └── reviewers-test
+├── ...
+└── sig-etc
+    ├── maintainers-etc
+    └── reviewers-etc
+```
+
+Members listed in the `maintainers-$NAME` and `reviewers-$NAME` sub-teams will also be members of the higher-order `sig-$NAME` team but with the corresponding GitHub roles of "maintainer" and "member", respectively.
+Members of a `sig-$NAME` team which are neither maintainers nor reviewers will simply be listed with the corresponding GitHub "member" role of the `sig-$NAME` team.
+
+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`;
-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`;
-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`;
-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`;
-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 [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.:
-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.:
+
+```diff
++   - name: Your Name
++     github: yourusername
+```
+
+Please include a short description as why you would like to join the team in your PR.
+
+### Community Leadership
+
+The Unikraft OSS project is led by a group of community leaders who are responsible for the overall direction of the project.
+We have different types of leaders, each with their own area of responsibility.
+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
+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
+The current list of community leaders is:
+
+- [Răzvan Deaconescu](https://github.com/razvand) - Community Management
+- [Andrei Mutu](https://github.com/mandrei12) - Blog
+- [Ștefan Jumarea](https://github.com/StefanJum) - Documentation
+- [Răzvan Virtan](https://github.com/razvanvirtan) - Releases
+- [Alexander Jung](https://github.com/nderjung) - Website
+- [Gabi Mocanu](https://github.com/gabrielmocanu) - Governance
+- [Alexander Jung](https://github.com/nderjung), [Cezar Craciunoiu](https://github.com/craciunoiuc) - CI / CD
+
+### Meetings
+
+Most SIGs have weekly or biweekly meeting where progress and problems encountered are discussed.
+Meetings take place online, on [the Unikraft Discord server](http://bit.ly/UnikraftDiscord).
+They are listed in the [Unikraft OSS Calendar](https://calendar.google.com/calendar/u/0/[email protected]);
+a meeting reminder is sent out on the appropriate Discord channel typically a day before the meeting.
+Everyone is welcome to join meetings of interest.
+Summaries of meetings are stored in the [`meeting-notes` repository](https://github.com/unikraft/meeting-notes/).
+
+### Roles and Responsibilities
+
+The table below outlines the various responsibilities of contributor roles in Unikraft.
+All the work is organized in SIGs, each SIG has members with different roles and responsibilities. 
+
+| Role | Responsibilities | Requirements | Defined by |
+| -----| ---------------- | ------------ | -------|
+| Member | Active member in the community | Multiple contributions to the projects | Member entry to any [SIG](https://github.com/unikraft/governance/tree/main/teams) |
+| Reviewer | Review contributions | Active member with multiple contributions and present at meetings | Reviewer entry to any [SIG](https://github.com/unikraft/governance/tree/main/teams) |
+| Maintainer | Approve contributions and suggests improvements | Highly experienced contributor | Maintainer entry to any [SIG](https://github.com/unikraft/governance/tree/main/teams) |
+
+#### Member
+
+Members are continuously active contributors to the community.
+They can have issues and PRs assigned to them, participate in SIGs through GitHub teams, and pre-submit tests are automatically run for their PRs.
+Members are expected to remain active contributors to the community.
+
+#### Reviewer
+
+Reviewers are members with a history of contributions in the community.
+Reviewers are responsible for reviewing code contributions and for the quality of the codebase.
+They are knowledgeable about the codebase and software engineering principles.
+Reviewers are expected to review code contributions in a timely manner.
+They are assigned to a SIG and are added as a reviewer in the `CODEOWNERS` file of that SIG.
+
+#### Maintainer
+
+Maintainers are responsible for the overall health and direction of the project.
+They are knowledgeable about the codebase and software engineering principles.
+Their primary responsibility is to ensure that the code is readable, maintainable, and meets the requirements of the project.
+Maintainers are expected to review code contributions in a timely manner.
+They are assigned to a SIG and are added as a maintainer in the `CODEOWNERS` file of that SIG.
+Maintainers are also responsible for helping new contributors to become familiar with the codebase and contributing process.
+
+### Tasks / Projects
+
+Tasks are organized in [projects](https://github.com/orgs/unikraft/projects).
+Usually, a project is created for a specific release and contains the tasks that need to be done for that release.
+
+### Contributions
+
+The [contributing](https://unikraft.org/docs/contributing/) section of the website is the main entry point for new contributors.
+It contains information about the project, how to get started, and how to contribute.
+
+### Roadmap
+
+Projects and tasks are brought together in a roadmap.
+The roadmap is a high-level view of the project and is used to communicate the direction of the project to the community.
+
+There is a dual view of the roadmap:
+* [A web page](https://hackmd.io/@unikraft/HyNdSyAki) created via [HackMD.io](https://hackmd.io)
+* [A list of issues](https://github.com/unikraft/unikraft/issues?q=is%3Aissue+is%3Aopen+label%3Akind%2Fproject) tagged `kind/project`
+
+We also keep a [Community Roadmap](https://github.com/orgs/unikraft/projects/24/views/35) as a GitHub project, with collects all current under-development items in the community.
+
+### Releases
+
+[Releases](https://github.com/unikraft/unikraft/releases) are used to provide a stable version of the project that can be used by the community.
+The release process is based on a schedule, with a new release expected to occur once about every 3 months.
+The release schedule is available as [milestones](https://github.com/unikraft/unikraft/milestones).
+
+### Values
+
+The Unikraft community is expected to follow the values defined in the [Code of Conduct](https://unikraft.org/docs/contributing/code-of-conduct/).
+As the community grows, we strive for kindness, giving feedback effectively, and ensuring a good development environment for all.