Skip to content

modified governance document #2442

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rpallavisharma wants to merge 3 commits into from
Closed

modified governance document #2442

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fed7875
modified governance document
rpallavisharma Aug 23, 2025
ce25fc8
added contributor can help in translations
rpallavisharma Aug 23, 2025
0d0d981
Merge branch 'trunk' into governanceDoc
rpallavisharma Aug 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
117 changes: 47 additions & 70 deletions website_and_docs/content/project/governance/_index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,25 +8,48 @@
<div class="mx-auto p-4">
<h1 class="d-1 text-center">Selenium Project Governance</h1>
<p class="lead mt-3 mb-0">
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.
</p>
</div>
{{< /blocks/section >}}

<div class="row -bg-selenium-cyan-20 justify-content-center">
<div class="col-12 px-5 pt-5 bg-transparent">
<h2>Governance Objective</h2>
Our governance framework is designed to achieve three core objectives:
<p>
<p>
<b>Inclusive Participation</b>
<br>We ensure that all individuals, regardless of background or affiliation, have meaningful
opportunities to contribute to Selenium's development and direction.
</p>

<p>
<b>Corporate Balance</b>
<br>We maintain safeguards against undue corporate influence while preventing any single entity
from compromising the project's independence or community-driven nature.
</p>

<p>
<b>Reciprocal Value</b>
<br> We create structures that encourage organizations benefiting from Selenium to contribute back to the
project's sustainability and growth.
</p>

<br>This document outlines the roles, responsibilities, and processes that define how various
types of contributors work within the Selenium project.
</div>
</div>

Copy link
Copy Markdown
Member

@diemol diemol Sep 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this section was useful, but if you want to keep it closed it is also fine.

Copy link
Copy Markdown
Member Author

@rpallavisharma rpallavisharma Sep 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I would try and create another PR this time keeping all roles intact. And would add this section again there.
Once done will share for review.

<div class="row -bg-selenium-cyan-20 justify-content-center">
<div class="col-12 px-5 pt-5 bg-transparent">
<h2>Roles and Responsibilities</h2>
<ul>
<li><a href="#users">Users</a></li>
<li><a href="#contributors">Contributors</a></li>
<li><a href="#triagers">Triagers</a></li>
<li><a href="#documenters">Documenters</a></li>
<li><a href="#translators">Translators</a></li>
Comment on lines -28 to -29
Copy link
Copy Markdown
Member

@diemol diemol Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the reason for removing these two roles? Can you please elaborate?

Copy link
Copy Markdown
Member Author

@rpallavisharma rpallavisharma Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please relook at the description of Contributors in the existing document. In the definition of that role we already mention about contributing to code/documentation.
I find these two roles redundant, and i have viewed few other open source projects roles, i gave a link as reference used, we can avoid having documenters and translators as separate and have contributors . current contributors definition already have that information.

incase the role of documenters and translators are to required explicitly, then what path do they take ? will any number of contributions from documenter or translator give them path to committer? or these roles will just stay as is it? are these sub categories of contributor?

i remember the earlier version of the governance doc when these roles were not defined, it used to make more sense to me. that version existed i believe before these two roles were created.

Copy link
Copy Markdown
Member

@diemol diemol Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Those roles were intended to clarify how community members could contribute to the project. Most of the time, the committer role suggests that you need to write code, and these two roles emphasize that "you do not only need to write code to contribute to this project".

Documenters and Translators are also repository committers.

Copy link
Copy Markdown
Member Author

@rpallavisharma rpallavisharma Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Diego, i have understood why these roles were created. it has been explained to me, more than once, here and in the plc channel. I found contributor role already having that information, and it could be written better to allow community to understand what all are various ways to contribute to the project.
I felt this would help simplify governance doc, that was all. I am sorry i won't be able to repeat this again and again.

Copy link
Copy Markdown
Member

@diemol diemol Sep 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the clarification, Pallavi. I wasn’t aware that this had already been explained to you in Slack. I can’t always follow all the threads, so I appreciate you flagging that. Given that the reasoning behind these roles has already been clarified, I’m just trying to understand what’s prompting the change now.

Copy link
Copy Markdown
Member Author

@rpallavisharma rpallavisharma Sep 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thats alright Diego, im sorry as well. I didn't realize that.
i will try to explain ... although i have said it before... or maybe i haven't been clear.. i will try one last time.

a. if we define who is a contributor better, which i have tried to do in the PR, and cover aspects of contribution other than code, which we do in that role already we don't need these two separate roles.
b. simplifies governance document, and maybe aligns it with common roles found in open source projects.
thats is all.
i am sorry i don't understand what else i can say more in here to explain this request. if this doesn't make sense kindly close it. i found the roles unnecessary and extra.
i understand the reasoning , even then i have my views. so i expressed. hope this helps.

<li><a href="#project-committers">Committers</a></li>
<li><a href="#technical-leadership-committee-tlc">Technical Leadership Committee Members</a></li>
<li><a href="#project-leadership-committee-plc">Project Leadership Committee Members</a></li>
Expand Down Expand Up @@ -60,30 +83,30 @@ <h3 id="users">Users</h3>
<h3 id="contributors">Contributors</h3>

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.
Copy link
Copy Markdown
Member

@diemol diemol Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if this level of detail is necessary.

Copy link
Copy Markdown
Member Author

@rpallavisharma rpallavisharma Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

Anyone can become a contributor, and contributions can take many forms, other than code contributions, e.g.:
<ul>
<li>
<p class="m-0">
Help other users through any of the <a href="#communication-channels">communication channels</a>
Actively help other users through any of the <a href="#communication-channels">communication channels</a>
made for that purpose.
</p>
</li>
<li>
Triage GitHub issues.
</li>
<li>
Organize Selenium meetups.
<li>
Translate Selenium Documentation in languages project support.
</li>
<li>
Organize and collaborate in Selenium Conferences.
<li>
Organize and collaborate in Selenium meetups, events and conferences.
</li>
</ul>

<p>
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
Copy link
Copy Markdown
Member

@diemol diemol Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If they are contributors, it is because they have contributed. This phrase is redundant.

Copy link
Copy Markdown
Member Author

@rpallavisharma rpallavisharma Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

their type of contribution (e.g., close an issue after triaging it).
</p>

Expand All @@ -105,7 +128,7 @@ <h3 id="contributors">Contributors</h3>
<div class="pb-5">
<h3 id="triagers">Triagers</h3>
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
Copy link
Copy Markdown
Member

@diemol diemol Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this level of detail necessary?

Copy link
Copy Markdown
Member Author

@rpallavisharma rpallavisharma Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think it made it more readable and clear to me. if not necessary please ignore.

Copy link
Copy Markdown
Member

@diemol diemol Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull requests are submitted to repositories. It is implicit.

failing test to help committers recreate the issue.

<h4 class="pt-4">Process for becoming a triager</h4>
Expand All @@ -122,58 +145,14 @@ <h4 class="pt-4">Process for becoming a triager</h4>
</ol>
</div>

<div class="pb-5">
<h3 id="documenters">Documenters</h3>

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.

<h4 class="pt-4">Process for becoming a documenter</h4>
<ol>
<li>
Add the GitHub user to <code>selenium-docs-and-site</code> GitHub team
</li>
<li>
Invite to Slack team chat room (<code>selenium-docs</code>)
</li>
<li>
Tweet congratulations to the new documenter from the SeleniumHQ Twitter account
</li>
</ol>
</div>

<div class="pb-5">
<h3 id="translators">Translators</h3>

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.

<h4 class="pt-4">Process for becoming a translator</h4>
<ol>
<li>
Add the GitHub user to <code>selenium-docs-and-site</code> GitHub team
</li>
<li>
Invite to Slack team chat room (<code>selenium-docs</code>)
</li>
<li>
Tweet congratulations to the new translator from the SeleniumHQ Twitter account
</li>
</ol>
</div>

<div class="pb-5">
<h3 id="project-committers">Project Committers</h3>

<p class="pb-4">
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.
</p>

<p class="fw-bold">
Expand Down Expand Up @@ -212,12 +191,10 @@ <h4 class="pt-3">Becoming a committer</h4>
</li>
<li>
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.
</li>
</ul>

Expand Down
Loading