From c606a28d0321fa0ddbd26a57411b3cfb1aa368d4 Mon Sep 17 00:00:00 2001 From: Mirko Mollik Date: Fri, 23 Feb 2024 10:26:50 +0100 Subject: [PATCH] fix: add maintainer file (#25) Signed-off-by: Mirko Mollik Co-authored-by: Mirko Mollik --- MAINTAINERS.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 MAINTAINERS.md diff --git a/MAINTAINERS.md b/MAINTAINERS.md new file mode 100644 index 0000000..980d799 --- /dev/null +++ b/MAINTAINERS.md @@ -0,0 +1,30 @@ +# Maintainers + +| Maintainer | GitHub ID | Company Affiliation | +| ----------------- | --------------- | ------------------- | +| Maaike van Leuken | maaikevanleuken | TNO | +| Samuel Rinnetmäki | samuelmr | Findynet | +| Mirko Mollik | cre8 | Fraunhofer FIT | + +## 1. What Does Being a Maintainer Entail + +- Reviewing code contributions. +- Managing issues and bugs. +- Maintaining documentation. +- Communicating with the community. +- Managing version control. +- Participating in project decisions. +- Building and sustaining a contributor community. + +## 2. How to Become a Maintainer + +Before being considered as a maintainer, contributors should meet the following requirements: + +- A history of substantial and consistent contributions to the project. +- A deep understanding of the project's goals, codebase, and best practices. +- Active involvement in the community, including helping others and engaging in discussions. +- Ultimately, the maintainers decide who will become the new maintainer through a majority vote. + +## 3. How Maintainers are Removed or Moved to Emeritus Status + +- Inactivity or consensus decision can lead to removal.