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

[Bug] Globally "Dispute Resolution Committee" should be "Membership Committee" #146

Open
1 task done
xolotl opened this issue Sep 27, 2022 · 3 comments
Open
1 task done
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents 🚧 status: blocked Blocked & therefore, not ready for work

Comments

@xolotl
Copy link
Contributor

xolotl commented Sep 27, 2022

Description

I think what may have been called the CCGN Dispute Resolution Committee later transformed into the Membership Committee and not all references in documentation were changed.

Reproduction

See for example: https://github.com/creativecommons/global-network-strategy/blob/main/docs/chapters-standards.md

Expectation

Either only one name should be used consistently, or if there really are two different bodies, they both need to be documented.

Resolution

  • I would be interested in resolving this bug.
@xolotl xolotl added 🟧 priority: high Stalls work on the project or its dependents 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 💻 aspect: code Concerns the software code in the repository labels Sep 27, 2022
@TateGunning
Copy link

TateGunning commented Jan 11, 2024

Apologies, good reflection hard to stomach sour to taste- thanks for bringing to attention. Adjustments made internally notated. Have a great weekend...

@T29Ar
Copy link

T29Ar commented Aug 1, 2024

Find this sh&$t its my new best moment of my life <3

@TateGunning
Copy link

Find this sh&$t its my new best moment of my life <3

Thank you ✔️

@possumbilities possumbilities added 🚧 status: blocked Blocked & therefore, not ready for work and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents 🚧 status: blocked Blocked & therefore, not ready for work
Projects
Status: Backlog
Development

No branches or pull requests

7 participants
@xolotl @TateGunning @possumbilities @T29Ar and others