Skip to content
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.

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

Make disclosure of conflicts of interest mandatory for spec change proposals #2079

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Johennes
Copy link
Contributor

@Johennes Johennes commented Feb 21, 2025

Fixes: #1700

Pull Request Checklist

Preview: https://pr2079--matrix-spec-previews.netlify.app

@Johennes Johennes changed the title Make disclosure of conflicts of interest mandatory Make disclosure of conflicts of interest mandatory for spec change proposals Feb 21, 2025
@@ -193,7 +206,8 @@ is as follows:
filename that follows the format `1234-my-new-proposal.md` where
`1234` is the MSC ID.
- Your PR description must include a link to the rendered Markdown
document and a summary of the proposal.
document and a disclosure of potential conflicts of interest where
they might reasonably apply.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Empirically, proposal summaries in the PR description don't appear to happen at all in practice. Therefore, I've dropped this part when adding the CoI clause.

For the purposes of transparency and to underpin the "greater benefit"
principle, proposals MUST disclose possible conflicts of interest where
they might reasonably exist. Authors MAY do this by filling out the
following checklist and publishing it together with their proposal.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is debatable whether RFC2119 language makes sense here. I found it helpful for differentiating between hard and optional requirements. I might be partial to this language by having worked with it in the spec for too long, however.

@Johennes Johennes marked this pull request as ready for review February 21, 2025 20:06
@Johennes Johennes requested a review from a team as a code owner February 21, 2025 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should we require disclosure of potential Conflict of Interest on MSCs?
1 participant