-
Notifications
You must be signed in to change notification settings - Fork 6
Update roles reference #182
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
Conversation
✅ Deploy Preview for open-terms-archive-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Congratulations, that's really good!!
docs/ota-tracking.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be here? 🤔
|
||
Each role represents a set of responsibilities and tasks that contribute to the collection's success. A role can be filled by one or multiple people, and one person can fulfill multiple roles. All roles can be either volunteer or paid positions, depending on the collection's resources and needs. | ||
|
||
This reference guide serves as a practical tool for collection organizers. It helps them understand the different roles needed for a collection, assign responsibilities effectively, ensure all necessary tasks are covered, and plan for long-term sustainability. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's avoid introducing the notion of “collection organizers”, which sounds like a role in itself 🙂
This reference guide serves as a practical tool for collection organizers. It helps them understand the different roles needed for a collection, assign responsibilities effectively, ensure all necessary tasks are covered, and plan for long-term sustainability. | |
This reference guide helps understand the different roles needed for a collection, assign responsibilities effectively, ensure all necessary tasks are covered, and plan for long-term sustainability. |
I'm not sure of the added value of this introductory section.
- Identify significant modifications | ||
- Write detailed analysis reports | ||
- Create regular digest reports | ||
- Flag critical changes to maintainers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why? What is “critical”?
- Create regular digest reports | ||
- Flag critical changes to maintainers | ||
- Provide analysis materials to diffusers | ||
- Report issues affecting analysis |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To whom? Maybe merge this with reporting to maintainers above 🙂
Co-authored-by: Matti Schneider <matti@opentermsarchive.org>
Co-authored-by: Matti Schneider <matti@opentermsarchive.org>
Thanks @MattiSG for the quality review and for relevant suggestions ! |
Co-authored-by: Matti Schneider <matti@opentermsarchive.org>
- Verify service declarations against scope criteria | ||
- Check service names match official branding | ||
- Validate completeness of extracted terms | ||
- Manage repository issues and pull requests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe:
- Manage repository issues and pull requests | |
- Facilitate discussions in issues and pull requests |
?
No description provided.