Add DANDI governance document #204

kabilar · 2025-08-11T21:26:05Z

The governance document is based on the GPT-5 prompt below, and then I manually curated the document.
- Please create a governance document for the DANDI Archive project. This document should apply to all sites (https://dandiarchive.org/, https://about.dandiarchive.org/, https://hub.dandiarchive.org/), organizations (https://github.com/dandi/, https://github.com/dandisets, https://github.com/dandizarrs) and all their repositories. The source code for the DANDI Archive is available here: https://github.com/dandi/. Format this document in markdown. Here are some example governance documents from other projects: https://bids.neuroimaging.io/collaboration/governance.html?h=governance, https://github.com/nebari-dev/governance, https://github.com/cncf/project-template/blob/main/GOVERNANCE-subprojects.md. And discuss who will review and merge pull requests.
Once approved, update the following in the document:
- Effective Date
- Status

docs/terms-policies/governance.md

Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>

docs/terms-policies/governance.md

Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>

asmacdo · 2025-09-09T23:51:51Z

docs/terms-policies/governance.md

+
+## 7. Pull Request Workflow
+
+### 7.1 Pull Request Requirements


Given that it takes 30 days minimum to properly amend this doc, IMO we should move pull request requirements, draft-pr policy and possibly release process into the developers guide.

@asmacdo That's fair but I kept this here because we have had discussions on who should merge, when merges should happen, etc. so I think that all aspects of pull requests should be discussed here.

Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>

docs/terms-policies/governance.md

kabilar · 2025-09-17T19:13:14Z

Hi @satra @waxlamp @jjnesbitt @mvandenburgh @candleindark @bendichter @djarecka, could you please take a look at this doc when you get a chance. Thanks.

yarikoptic

a nearly complete pass

yarikoptic · 2025-10-15T19:42:57Z

docs/terms-policies/governance.md

+- A cloud-based platform to store, process, and disseminate data. You can use DANDI to collaborate and publish datasets.
+- Open access to data to enable secondary uses of data outside the intent of the study.
+- Optimize data storage and access through partnerships, compression and accessibility technologies.
+- Enables reproducible practices and publications through data standards such as NWB and BIDS.
+- The platform is not just an endpoint to dump data, it is intended as a living repository that enables collaboration within and across labs.


Opening is "DANDI provides:" so IMHO all items should be continuations to such an opening, thus:

Suggested change

- A cloud-based platform to store, process, and disseminate data. You can use DANDI to collaborate and publish datasets.

- Open access to data to enable secondary uses of data outside the intent of the study.

- Optimize data storage and access through partnerships, compression and accessibility technologies.

- Enables reproducible practices and publications through data standards such as NWB and BIDS.

- The platform is not just an endpoint to dump data, it is intended as a living repository that enables collaboration within and across labs.

- a cloud-based platform to store, process, and disseminate data. You can use DANDI to collaborate and publish datasets.

- open access to data to enable secondary uses of data outside the intent of the study;

- optimized data storage and access through partnerships, compression and accessibility technologies;

- facilities to encourage reproducible practices and publications through data standards such as NWB and BIDS;

- a platform that is not just an endpoint to dump data, but intended to be a living repository that enables collaboration within and across labs.

or redo opening somehow differently ("DANDI is" ...)

yarikoptic · 2025-10-15T19:44:35Z

docs/terms-policies/governance.md

+## 3. Core Principles
+
+1. Openness & Transparency: Designs, discussions, and decisions are public by default
+2. FAIR & Reproducibility: Data and code evolution remain traceable and citable


Suggested change

2. FAIR & Reproducibility: Data and code evolution remain traceable and citable

2. FAIR & Reproducibility: Data and code follow standards and their evolution remain open, traceable, and citable

since IMHO standards are the core of FAIR

yarikoptic · 2025-10-15T19:45:58Z

docs/terms-policies/governance.md

+### 5.1 Contributors
+Anyone submitting issues, pull requests, documentation, or feedback.  
+Responsibilities:
+- Follow Code of Conduct and contribution guidelines


hard to follow if no references! Will they be per project or generic?

yarikoptic · 2025-10-15T19:46:34Z

docs/terms-policies/governance.md

+Anyone submitting issues, pull requests, documentation, or feedback.  
+Responsibilities:
+- Follow Code of Conduct and contribution guidelines
+- Provide context and reproducible steps


Suggested change

- Provide context and reproducible steps

- Strive to provide sufficient context and steps to reproduce

yarikoptic · 2025-10-15T19:47:51Z

docs/terms-policies/governance.md

+
+### 5.2 Reviewers
+Contributors granted reviewer status for designated repositories.  
+Responsibilities:


Suggested change

Responsibilities:

Responsibilities:

yarikoptic · 2025-10-15T19:49:42Z

docs/terms-policies/governance.md

+Expectations:
+- Active presence
+- Adhere to conflict of interest and bias avoidance
+Path to role:


Suggested change

Path to role:

Path to role:

yarikoptic · 2025-10-15T19:53:01Z

docs/terms-policies/governance.md

+## 6. Decision-Making Model
+
+### 6.1 Roadmap
+- Project targets are discussed during the biweekly Engineering Core and Scientific Core meetings.


ideally, make trailing . uniform across listings. Above sections didn't have them, and here they come. Just add them all over

yarikoptic · 2025-10-15T19:57:01Z

docs/terms-policies/governance.md

+### 7.2 Merge Policy
+- All pull requests require:
+    - All comments must be resolved or addressed
+    - Approval by at least 1 listed Maintainer for that repository


"listed" where?

how do we resolve road-blocks? e.g. Project Leadership could have a decree to approve/disprove?

yarikoptic · 2025-10-15T19:57:32Z

docs/terms-policies/governance.md

+- All pull requests require:
+    - All comments must be resolved or addressed
+    - Approval by at least 1 listed Maintainer for that repository
+    - 24 hour waiting period (unless addressing a critical issue)


Suggested change

- 24 hour waiting period (unless addressing a critical issue)

- 24 hour waiting period (unless addressing a critical issue or obviously trivial)

? so that some typo in comment could be fixed without waiting/forgetting

yarikoptic · 2025-10-15T19:59:01Z

docs/terms-policies/governance.md

+- Convert to “Ready” only when tests and documentation are updated
+
+### 7.4 Reverts
+- Any Maintainer may revert a merged pull request causing regression, security issue, or service degradation, with immediate notice in original pull request thread.


"almost", release might not be needed if prior change was not even released yet. so state not "must be made" but "must be made if prior change was already released"?

kabilar added 2 commits August 11, 2025 16:22

Create governance document with sections 1,2,4

6c1ad6c

Add section 3

f49306c

kabilar self-assigned this Aug 11, 2025

kabilar added 12 commits August 11, 2025 16:51

Add section 5

0cb9fd8

Update navigation

c051cfe

Add Amendments to Project Governance section

28c50c3

Add Documentation section

5689ba4

Add Communication section

6f635f6

Add Sunset Policy section

726f856

Add Releases section

f7f4194

Add Community section

c450e97

Add Licenses section

3d1fd85

Add Security section

03280c1

Add Pull Request Workflow section

64914af

Add Decision-Making Model section

55f16bd

kabilar changed the title ~~[WIP] Add governance document~~ Add DANDI governance document Sep 9, 2025

kabilar marked this pull request as ready for review September 9, 2025 16:55

kabilar requested review from CodyCBakerPhD, asmacdo, bendichter, candleindark, jjnesbitt, mvandenburgh, satra, waxlamp and yarikoptic September 9, 2025 16:56

CodyCBakerPhD reviewed Sep 9, 2025

View reviewed changes

docs/terms-policies/governance.md Show resolved Hide resolved

kabilar added 3 commits September 9, 2025 12:06

Add table of maintainers

3faf19f

Update maintainers table

ecc2a71

Add maintainer responsibility

3a05ed0

kabilar and others added 4 commits September 9, 2025 17:27

Update docs/terms-policies/governance.md

dff3810

Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>

Update docs/terms-policies/governance.md

cfee9a7

Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>

Update docs/terms-policies/governance.md

48eb363

Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>

Update docs/terms-policies/governance.md

fd3646d

Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>

kabilar commented Sep 9, 2025

View reviewed changes

docs/terms-policies/governance.md Show resolved Hide resolved

kabilar and others added 2 commits September 9, 2025 17:31

Update docs/terms-policies/governance.md

d876f9d

Update docs/terms-policies/governance.md

2451780

Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>

asmacdo reviewed Sep 9, 2025

View reviewed changes

Update docs/terms-policies/governance.md

d869748

Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>

CodyCBakerPhD mentioned this pull request Sep 17, 2025

We should also probably start adding SECURITY.md files to our repos too: https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies #211

Open

kabilar commented Sep 17, 2025

View reviewed changes

docs/terms-policies/governance.md Outdated Show resolved Hide resolved

Update docs/terms-policies/governance.md

9da61f0

kabilar commented Sep 17, 2025

View reviewed changes

docs/terms-policies/governance.md Outdated Show resolved Hide resolved

Update docs/terms-policies/governance.md

dd24798

kabilar commented Sep 17, 2025

View reviewed changes

docs/terms-policies/governance.md Outdated Show resolved Hide resolved

Update docs/terms-policies/governance.md

63a0fc7

kabilar commented Sep 17, 2025

View reviewed changes

docs/terms-policies/governance.md Outdated Show resolved Hide resolved

Update docs/terms-policies/governance.md

2666b00

kabilar commented Sep 17, 2025

View reviewed changes

docs/terms-policies/governance.md Show resolved Hide resolved

Update docs/terms-policies/governance.md

d2f71ee

kabilar commented Sep 17, 2025

View reviewed changes

docs/terms-policies/governance.md Outdated Show resolved Hide resolved

Update docs/terms-policies/governance.md

dc77de8

kabilar commented Sep 17, 2025

View reviewed changes

docs/terms-policies/governance.md Outdated Show resolved Hide resolved

Update docs/terms-policies/governance.md

59e5097

kabilar requested review from CodyCBakerPhD, asmacdo, djarecka and yarikoptic September 17, 2025 19:10

yarikoptic requested changes Oct 15, 2025

View reviewed changes


		## 7. Pull Request Workflow

		### 7.1 Pull Request Requirements

	2. FAIR & Reproducibility: Data and code evolution remain traceable and citable
	2. FAIR & Reproducibility: Data and code follow standards and their evolution remain open, traceable, and citable

	- Provide context and reproducible steps
	- Strive to provide sufficient context and steps to reproduce

	- 24 hour waiting period (unless addressing a critical issue)
	- 24 hour waiting period (unless addressing a critical issue or obviously trivial)

Add DANDI governance document #204

Are you sure you want to change the base?

Add DANDI governance document #204

Conversation

kabilar commented Aug 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

kabilar commented Sep 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

yarikoptic 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!

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!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

kabilar commented Aug 11, 2025 •

edited

Loading

kabilar commented Sep 17, 2025 •

edited

Loading