Selenium Project Governance
- The Selenium Project wants as much as possible to operate using procedures that are fair, open, inviting, and ultimately
- good for the community. For that reason, we find it valuable to codify some of the ways that the Project goes about its
- day-to-day business. We want to make sure that no matter who you are, you have the opportunity to contribute to Selenium.
- We want to make sure that no corporation can exert undue influence on the community or hold the Project hostage. And
- likewise, we want to make sure that corporations which benefit from Selenium are also incentivized to give back. This
- document describes how various types of contributors work within the Selenium project.
+ The Selenium Project is committed to maintaining fair, transparent, and inclusive governance practices that serve the broader
+ community's interests. This document establishes the foundational procedures and principles that guide our day-to-day operations
+ and decision-making processes.
{{< /blocks/section >}}
+
+
+
Governance Objective
+ Our governance framework is designed to achieve three core objectives:
+
+
+ Inclusive Participation
+
We ensure that all individuals, regardless of background or affiliation, have meaningful
+ opportunities to contribute to Selenium's development and direction.
+
+
+
+ Corporate Balance
+
We maintain safeguards against undue corporate influence while preventing any single entity
+ from compromising the project's independence or community-driven nature.
+
+
+
+ Reciprocal Value
+
We create structures that encourage organizations benefiting from Selenium to contribute back to the
+ project's sustainability and growth.
+
+
+
This document outlines the roles, responsibilities, and processes that define how various
+ types of contributors work within the Selenium project.
+
+
Roles and Responsibilities
@@ -25,8 +50,6 @@
Roles and Responsibilities
Users
Contributors
Triagers
-
Documenters
-
Translators
Committers
Technical Leadership Committee Members
Project Leadership Committee Members
@@ -60,30 +83,30 @@
Users
Contributors
Contributors are community members who contribute in concrete ways to the project,
- most often in the form of code and/or documentation. Anyone can become a Contributor,
- and contributions can take many forms, e.g.:
+ most often in the form of code and/or documentation in the respective project repository.
+ Anyone can become a contributor, and contributions can take many forms, other than code contributions, e.g.:
There is no expectation of commitment to the project, no specific skill requirements,
and no selection process.
- Some Contributors might have some basic privileges to the GitHub repos, based on
+ Some Contributors might have some basic privileges to the GitHub repos to which they have contributed, based on
their type of contribution (e.g., close an issue after triaging it).
@@ -105,7 +128,7 @@
Contributors
Triagers
As contributors grow into the project they will be added as members of the triage team. Their
- role is to help triage issues and potentially submit Pull Requests with fixes or at least a
+ role is to help triage issues and potentially submit Pull Requests in the github repos with fixes or at least a
failing test to help committers recreate the issue.
Process for becoming a triager
@@ -122,58 +145,14 @@ Process for becoming a triager
-
-
Documenters
-
- Good documentation is crucial to all software projects. Documenters are community members
- who have shown that they are committed to improving the examples and descriptions of
- the various features and functionality of the project. Documenters are given push
- access to the project's Documentation GitHub repo.
-
-
Process for becoming a documenter
-
- -
- Add the GitHub user to
selenium-docs-and-site GitHub team
-
- -
- Invite to Slack team chat room (
selenium-docs)
-
- -
- Tweet congratulations to the new documenter from the SeleniumHQ Twitter account
-
-
-
-
-
-
Translators
-
- To better support our international community, we provide translations of our documentation. A translator is
- responsible for all content in a given language. This includes creating and updating content, helping ensure
- that content created in one language is flagged for distributions to other languages, and managing any
- Pull Requests relevant to those language files.
-
-
Process for becoming a translator
-
- -
- Add the GitHub user to
selenium-docs-and-site GitHub team
-
- -
- Invite to Slack team chat room (
selenium-docs)
-
- -
- Tweet congratulations to the new translator from the SeleniumHQ Twitter account
-
-
-
-
Project Committers
- Committers are community members who have shown that they are committed to the
- continued development of the project through ongoing engagement with the community.
+ Committers are contributors who have shown that they are committed to the
+ continued development of the project through ongoing engagement with the project.
Committers are given push access to the project's GitHub repos where they
- contribute to.
+ contribute to. Example getting access to the selenium-docker repository for those contribute to it.
@@ -212,12 +191,10 @@
Becoming a committer
Have submitted sufficient substantive contributions to one or more of the
- different projects (IDE, Docker-Selenium, Selenium, Site & Docs). For
- technical contributions, enough weight is present and requires little effort to
- accept because it is well documented and tested. Normally 10 substantive
- contributions are needed to qualify as a candidate to be a committer, but there
- could be cases where the contributions are substantial enough that a fewer
- amount is also acceptable.
+ different projects (Selenium IDE, Docker-Selenium, Selenium Client Bindings, WebSite & Docs).
+ Normally 10 substantive contributions are needed to qualify as a candidate to be a committer, but there
+ could be cases where the contributions are substantial enough or technically significant enough that a fewer
+ number is also acceptable.