Draft governance model by benjeffery · Pull Request #3188 · tskit-dev/tskit

benjeffery · 2025-06-05T11:13:57Z

I've created this PR on the tskit repo for visibility - eventually this will live at https://github.com/tskit-dev/administrative.

Following the meeting and discussion yesterday, I've written up what I consider to be the lightest, yet focused and meaningful, governance policy for the core repositories.

Please provide your feedback on this, even if it's just a +1 if you're happy, as we'd like community consensus on this.

codecov · 2025-06-05T11:19:08Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.63%. Comparing base (1537830) to head (06ac675).
⚠️ Report is 74 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3188      +/-   ##
==========================================
+ Coverage   89.62%   89.63%   +0.01%     
==========================================
  Files          28       28              
  Lines       31969    32004      +35     
  Branches     5873     5879       +6     
==========================================
+ Hits        28653    28688      +35     
  Misses       1886     1886              
  Partials     1430     1430

Flag	Coverage Δ
c-tests	`86.66% <ø> (ø)`
lwt-tests	`80.38% <ø> (ø)`
python-c-tests	`88.18% <ø> (ø)`
python-tests	`98.86% <ø> (+<0.01%)`	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 3 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

jeromekelleher

I like it!

jeromekelleher · 2025-06-05T11:24:57Z

+
+- proposing, discussing, or reviewing a change to the code, documentation, or specification
+  via a GitHub pull request to the above repositories;
+- reporting a GitHub issue or starting a discussion on the above repositories;


What's the process for someone getting added to the github org? (I don't know, just asking the question for visibility)

We need to set this up and have a clean out of permissions across the repos. It's under settings on the org page.

I meant what's the process for deciding whether someone should be in the Org or not. That's something we should document

sounds good but in vague terms; too prescriptive might go out of date (as for instance perhaps possible github roles change)

perhaps some general principles - like "the steering committee will choose roles in the github org so that X Y and Z"

ah I see this has been added below

hyanwong · 2025-06-05T12:45:44Z

+- [kastore - key-value store](http://github.com/tskit-dev/kastore)
+- [administrative](http://github.com/tskit-dev/administrative)
+- [.github - common config](http://github.com/tskit-dev/.github)
+


Great to have this laid out. Do we want explicitly say the other repos on the tskit-dev workspace (e.g. tscompress, tsinfer) may become the responsibility of other maintainers if need be, or is that too prescriptive?

I thought about this, but decided, as they are out of scope for this document, that it shouldn't say anything about them.

hyanwong · 2025-06-05T12:48:10Z

I like this. Not too heavyweight, just does what's needed. +1 from me.

nspope · 2025-06-05T18:41:11Z

Looks great to me-- simple and transparent.

petrelharp · 2025-06-11T17:21:11Z

+  via a GitHub pull request to the above repositories;
+- reporting a GitHub issue or starting a discussion on the above repositories;
+
+Potential contributors are encouraged to read and abide by the [CODE OF CONDUCT](https://github.com/tskit-dev/.github/blob/main/CODE_OF_CONDUCT.md).


Suggested change

Potential contributors are encouraged to read and abide by the [CODE OF CONDUCT](https://github.com/tskit-dev/.github/blob/main/CODE_OF_CONDUCT.md).

Potential contributors are expected to abide by the [CODE OF CONDUCT](https://github.com/tskit-dev/.github/blob/main/CODE_OF_CONDUCT.md).

I think I put "encouraged" as the contributors are "potential" but I agree that stronger wording here is better. Maybe even remove the "potential" e.g. "contributors are required to abide by"

or even "contributors must abide by"

Changed in c05939a

Co-authored-by: Peter Ralph <petrel.harp@gmail.com>

petrelharp · 2025-06-12T15:21:19Z

+
+Decisions about the future of the project are made through discussion with all
+members of the community. All non-sensitive project management discussion takes
+place on the issue trackers of the appropriate repositories.


Suggested change

place on the issue trackers of the appropriate repositories.

place in the issue trackers of the appropriate repositories

or other public forums.

petrelharp · 2025-06-12T15:22:00Z

+Decisions about the future of the project are made through discussion with all
+members of the community. All non-sensitive project management discussion takes
+place on the issue trackers of the appropriate repositories.
+Where possible decisions and discussions of the steering council should be documented as issues on the [administrative](https://github.com/tskit-dev/administrative) repository. Sensitive discussion may occur via email to admin@tskit.dev.


What's the idea about emailing admin? to have record of things? I'd vote to remove the last sentence?

It was a way to encourage things not to go through personal email as the admin address will have a record for all the SC members. I get your point that this maybe promotes that too much. Removed in 06ac675

benjeffery · 2025-08-05T17:06:58Z

@tskit-dev/all Thanks for all the feedback. I will place this in the admin repo soon, linking from the other repos. Last chance for feedback!

This adds the draft governance model proposed in tskit-dev/tskit PR #3188 so that governance lives in the administrative repo.

benjeffery · 2025-10-09T11:57:52Z

Governance is now live at https://tskit.dev/governance/

Strawman governance

457ff2e

jeromekelleher reviewed Jun 5, 2025

View reviewed changes

Address comments

2850cee

hyanwong reviewed Jun 5, 2025

View reviewed changes

petrelharp reviewed Jun 11, 2025

View reviewed changes

Comment thread GOVERNANCE.md Outdated

petrelharp reviewed Jun 11, 2025

View reviewed changes

Comment thread GOVERNANCE.md Outdated

benjeffery and others added 2 commits June 11, 2025 23:36

Update GOVERNANCE.md

284e40c

Co-authored-by: Peter Ralph <petrel.harp@gmail.com>

Update GOVERNANCE.md

fe1e150

Co-authored-by: Peter Ralph <petrel.harp@gmail.com>

petrelharp reviewed Jun 12, 2025

View reviewed changes

benjeffery added 3 commits June 13, 2025 11:42

Stronger CoC wording

c05939a

Add public forums

cec9e68

Remove email

06ac675

This was referenced Sep 28, 2025

Add tskit governance policy tskit-dev/administrative#18

Closed

Add default organization governance policy tskit-dev/.github#6

Merged

Add Governance page and footer link tskit-dev/tskit-site#265

Merged

benjeffery closed this Oct 9, 2025

benjeffery deleted the governance branch October 9, 2025 11:57

	Potential contributors are encouraged to read and abide by the [CODE OF CONDUCT](https://github.com/tskit-dev/.github/blob/main/CODE_OF_CONDUCT.md).
	Potential contributors are expected to abide by the [CODE OF CONDUCT](https://github.com/tskit-dev/.github/blob/main/CODE_OF_CONDUCT.md).

	place on the issue trackers of the appropriate repositories.
	place in the issue trackers of the appropriate repositories
	or other public forums.

Conversation

benjeffery commented Jun 5, 2025

Uh oh!

codecov Bot commented Jun 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

jeromekelleher left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

hyanwong commented Jun 5, 2025

Uh oh!

nspope commented Jun 5, 2025

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

benjeffery commented Aug 5, 2025

Uh oh!

benjeffery commented Oct 9, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

codecov Bot commented Jun 5, 2025 •

edited

Loading