Skip to content

Commit fed7875

Browse files
rpallavisharmarpallavisharma
committed
modified governance document
1 parent cfd39c7 commit fed7875

1 file changed

Lines changed: 45 additions & 71 deletions

File tree

‎website_and_docs/content/project/governance/_index.html‎

Lines changed: 45 additions & 71 deletions
Original file line numberDiff line numberDiff line change
@@ -8,25 +8,48 @@
88
<div class="mx-auto p-4">
99
<h1 class="d-1 text-center">Selenium Project Governance</h1>
1010
<p class="lead mt-3 mb-0">
11-
The Selenium Project wants as much as possible to operate using procedures that are fair, open, inviting, and ultimately
12-
good for the community. For that reason, we find it valuable to codify some of the ways that the Project goes about its
13-
day-to-day business. We want to make sure that no matter who you are, you have the opportunity to contribute to Selenium.
14-
We want to make sure that no corporation can exert undue influence on the community or hold the Project hostage. And
15-
likewise, we want to make sure that corporations which benefit from Selenium are also incentivized to give back. This
16-
document describes how various types of contributors work within the Selenium project.
11+
The Selenium Project is committed to maintaining fair, transparent, and inclusive governance practices that serve the broader
12+
community's interests. This document establishes the foundational procedures and principles that guide our day-to-day operations
13+
and decision-making processes.
1714
</p>
1815
</div>
1916
{{< /blocks/section >}}
2017

18+
<div class="row -bg-selenium-cyan-20 justify-content-center">
19+
<div class="col-12 px-5 pt-5 bg-transparent">
20+
<h2>Governance Objective</h2>
21+
Our governance framework is designed to achieve three core objectives:
22+
<p>
23+
<p>
24+
<b>Inclusive Participation</b>
25+
<br>We ensure that all individuals, regardless of background or affiliation, have meaningful
26+
opportunities to contribute to Selenium's development and direction.
27+
</p>
28+
29+
<p>
30+
<b>Corporate Balance</b>
31+
<br>We maintain safeguards against undue corporate influence while preventing any single entity
32+
from compromising the project's independence or community-driven nature.
33+
</p>
34+
35+
<p>
36+
<b>Reciprocal Value</b>
37+
<br> We create structures that encourage organizations benefiting from Selenium to contribute back to the
38+
project's sustainability and growth.
39+
</p>
40+
41+
<br>This document outlines the roles, responsibilities, and processes that define how various
42+
types of contributors work within the Selenium project.
43+
</div>
44+
</div>
45+
2146
<div class="row -bg-selenium-cyan-20 justify-content-center">
2247
<div class="col-12 px-5 pt-5 bg-transparent">
2348
<h2>Roles and Responsibilities</h2>
2449
<ul>
2550
<li><a href="#users">Users</a></li>
2651
<li><a href="#contributors">Contributors</a></li>
2752
<li><a href="#triagers">Triagers</a></li>
28-
<li><a href="#documenters">Documenters</a></li>
29-
<li><a href="#translators">Translators</a></li>
3053
<li><a href="#project-committers">Committers</a></li>
3154
<li><a href="#technical-leadership-committee-tlc">Technical Leadership Committee Members</a></li>
3255
<li><a href="#project-leadership-committee-plc">Project Leadership Committee Members</a></li>
@@ -60,30 +83,27 @@ <h3 id="users">Users</h3>
6083
<h3 id="contributors">Contributors</h3>
6184

6285
Contributors are community members who contribute in concrete ways to the project,
63-
most often in the form of code and/or documentation. Anyone can become a Contributor,
64-
and contributions can take many forms, e.g.:
86+
most often in the form of code and/or documentation in the respective project repository.
87+
Anyone can become a contributor, and contributions can take many forms, other than code contributions, e.g.:
6588
<ul>
6689
<li>
6790
<p class="m-0">
68-
Help other users through any of the <a href="#communication-channels">communication channels</a>
91+
Actively help other users through any of the <a href="#communication-channels">communication channels</a>
6992
made for that purpose.
7093
</p>
7194
</li>
7295
<li>
7396
Triage GitHub issues.
7497
</li>
75-
<li>
76-
Organize Selenium meetups.
77-
</li>
78-
<li>
79-
Organize and collaborate in Selenium Conferences.
98+
<li>
99+
Organize and collaborate in Selenium meetups, events and conferences.
80100
</li>
81101
</ul>
82102

83103
<p>
84104
There is no expectation of commitment to the project, no specific skill requirements,
85105
and no selection process.
86-
Some Contributors might have some basic privileges to the GitHub repos, based on
106+
Some Contributors might have some basic privileges to the GitHub repos to which they have contributed, based on
87107
their type of contribution (e.g., close an issue after triaging it).
88108
</p>
89109

@@ -105,7 +125,7 @@ <h3 id="contributors">Contributors</h3>
105125
<div class="pb-5">
106126
<h3 id="triagers">Triagers</h3>
107127
As contributors grow into the project they will be added as members of the triage team. Their
108-
role is to help triage issues and potentially submit Pull Requests with fixes or at least a
128+
role is to help triage issues and potentially submit Pull Requests in the github repos with fixes or at least a
109129
failing test to help committers recreate the issue.
110130

111131
<h4 class="pt-4">Process for becoming a triager</h4>
@@ -122,58 +142,14 @@ <h4 class="pt-4">Process for becoming a triager</h4>
122142
</ol>
123143
</div>
124144

125-
<div class="pb-5">
126-
<h3 id="documenters">Documenters</h3>
127-
128-
Good documentation is crucial to all software projects. Documenters are community members
129-
who have shown that they are committed to improving the examples and descriptions of
130-
the various features and functionality of the project. Documenters are given push
131-
access to the project's Documentation GitHub repo.
132-
133-
<h4 class="pt-4">Process for becoming a documenter</h4>
134-
<ol>
135-
<li>
136-
Add the GitHub user to <code>selenium-docs-and-site</code> GitHub team
137-
</li>
138-
<li>
139-
Invite to Slack team chat room (<code>selenium-docs</code>)
140-
</li>
141-
<li>
142-
Tweet congratulations to the new documenter from the SeleniumHQ Twitter account
143-
</li>
144-
</ol>
145-
</div>
146-
147-
<div class="pb-5">
148-
<h3 id="translators">Translators</h3>
149-
150-
To better support our international community, we provide translations of our documentation. A translator is
151-
responsible for all content in a given language. This includes creating and updating content, helping ensure
152-
that content created in one language is flagged for distributions to other languages, and managing any
153-
Pull Requests relevant to those language files.
154-
155-
<h4 class="pt-4">Process for becoming a translator</h4>
156-
<ol>
157-
<li>
158-
Add the GitHub user to <code>selenium-docs-and-site</code> GitHub team
159-
</li>
160-
<li>
161-
Invite to Slack team chat room (<code>selenium-docs</code>)
162-
</li>
163-
<li>
164-
Tweet congratulations to the new translator from the SeleniumHQ Twitter account
165-
</li>
166-
</ol>
167-
</div>
168-
169145
<div class="pb-5">
170146
<h3 id="project-committers">Project Committers</h3>
171147

172148
<p class="pb-4">
173-
Committers are community members who have shown that they are committed to the
174-
continued development of the project through ongoing engagement with the community.
149+
Committers are contributors who have shown that they are committed to the
150+
continued development of the project through ongoing engagement with the project.
175151
Committers are given push access to the project's GitHub repos where they
176-
contribute to.
152+
contribute to. Example getting access to the selenium-docker repository for those contribute to it.
177153
</p>
178154

179155
<p class="fw-bold">
@@ -212,12 +188,10 @@ <h4 class="pt-3">Becoming a committer</h4>
212188
</li>
213189
<li>
214190
Have submitted sufficient substantive contributions to one or more of the
215-
different projects (IDE, Docker-Selenium, Selenium, Site & Docs). For
216-
technical contributions, enough weight is present and requires little effort to
217-
accept because it is well documented and tested. Normally 10 substantive
218-
contributions are needed to qualify as a candidate to be a committer, but there
219-
could be cases where the contributions are substantial enough that a fewer
220-
amount is also acceptable.
191+
different projects (Selenium IDE, Docker-Selenium, Selenium Client Bindings, WebSite & Docs).
192+
Normally 10 substantive contributions are needed to qualify as a candidate to be a committer, but there
193+
could be cases where the contributions are substantial enough or technically significant enough that a fewer
194+
number is also acceptable.
221195
</li>
222196
</ul>
223197

0 commit comments

Comments
 (0)