Skip to content

New Pull Request Discussion section in Governance chapter. #294

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

Merged
ax3l merged 4 commits into from
Aug 31, 2026
Merged

New Pull Request Discussion section in Governance chapter. #294

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7a071c2
New `Pull Request Discussion` section in Governance chapter.
DavidSagan Aug 23, 2026
76b471c
Update source/governance.md
DavidSagan Aug 24, 2026
2c26f31
clarification.
DavidSagan Aug 24, 2026
0ecec41
Reword.
DavidSagan Aug 27, 2026
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
21 changes: 20 additions & 1 deletion source/governance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ Contributions can be in many forms and not all need to be code contributions.
Examples include contributing to pull requests, issues, user discussions, documentation, tutorials, etc.
Contributors can participate in developer meetings and weigh in on discussions.
Contributors can "triage" (add labels) to pull requests, issues, and GitHub discussion pages.
Contributors can comment and review PRs (but not merge).
Contributors can review PRs (but not merge).

### Decision Process

Expand All @@ -109,10 +109,29 @@ Appointed after contributing to PALS (see above) by any member of the TC.

The role can be lost by resigning or by decision of an individual TC or SC member, e.g., due to inactivity, bad acting or other.

## Pull Request Discussion

Anyone with an interest is invited to join the discussion of any Pull Request (PR).

So that the standard can evolve at a reasonable pace, anyone who raises an issue in a PR
discussion is encouraged to respond promptly to comments on the issue.
If that is not possible, the person should post a note saying when they expect
they can respond, and the decision to merge the PR should wait for them accordingly.

If an issue has been raised, and if
1) all the comments supporting the issue have been responded to, and
2) over two weeks has passed since the last comment on this issue has been posted, and
3) no one has asked for further time to respond,
then for the purposes of deciding whether to merge the PR, the issue is to be treated as resolved.
That is, the merge decision is not to be postponed to allow more time for responses.
Notice that this two week limit does not apply to cases where a comment raises an issue and
that comment has not been replied to.

## Former Members

"Former members" are the giants on whose shoulders we stand.
But, for the purpose of PALS governance, they are *not* tracked as a governance role in PALS.
Instead, former (e.g., inactive) contributors are acknowledged separately in GitHub contributor tracking, the PALS documentation, references, citable Zenodo archives of releases, etc. as appropriate.

Former members of SC, TC and Contributors are not kept in the roster, since committee role rosters shall reflect currently active members and the responsible governance body.