package-url / package-url/community

Governance

Open
#7 31 comments 9 reactions 5 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
0
Forks
2
Avg merge
2m
Merged PRs (30d)
2

Description

As purl adoption increases, and others consider purl adoption, there is a desire for governance of the project to be more clearly defined. At the current size of the project this governance could be pretty lightweight, but even that would give adopters confidence.

@royaljust from GitHub published an article on Minimal Viable Governance (MVG) that we could use as a baseline:
https://github.blog/2021-07-22-minimum-viable-governance-lightweight-community-structure-foss-projects/

Example documents are here:
https://github.com/github/MVG

To implement this, we need to:

  • Create a technical steering committee (we could start with the 5 org owners if they agree).
  • Create a charter which the steering committee would vote to adopt.
    • Mission (we can derive this from the content we already have)
    • Decision making process (MVG has a proposed lightweight starting one).
    • Trademark policy.
    • Anti-trust policy.
    • Code of conduct (already in place).
  • Add the necessary files to the org's repositories.

If there's no objection to MVG as a starting point, I'm happy to pull together the files and create pull requests that the current org owners can review.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.