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

Maintenance Roadmap for ActiveTriples #88

Open
Tracked by #149
jrgriffiniii opened this issue Mar 10, 2022 · 2 comments
Open
Tracked by #149

Maintenance Roadmap for ActiveTriples #88

jrgriffiniii opened this issue Mar 10, 2022 · 2 comments
Assignees

Comments

@jrgriffiniii
Copy link
Contributor

Given that an update made to https://github.com/ActiveTriples/ActiveTriples is going to block an update supporting Ruby 3.0.z releases for active_fedora (please see samvera/active_fedora#1470) (I have created https://github.com/samvera-labs/ActiveTriples as a community fork for this), I would like to please propose one of two solutions:

@jrgriffiniii jrgriffiniii self-assigned this Mar 24, 2022
@jrgriffiniii
Copy link
Contributor Author

jrgriffiniii commented Mar 24, 2022

In order to fulfill the promotion to core component status, the following requirements must be met:

  • Code is stored in a repository in the Samvera github organization https://github.com/samvera and meets the requirements for being there.
  • Component has a designated product owner.
  • A participant of the [Component Maintenance Interest Group] must have a vested interest in the maintenance of that component, acting as a representative for their institution’s needs.

I can volunteer to serve as the product owner of this Gem. The requirements for promotion must also be met:

  • (https://samvera.github.io/samvera_labs.html#documentation-requirements)Documentation Requirements
    LICENSE file, Apache 2 (or compatible)
  • README.md
  • Statement of purpose
  • Basic install steps
  • Identify any volatile/experimental features
  • How to contribute -> CONTRIBUTING.md
  • How/Who to contact for help -> push out to all gems like CONTRIBUTING.md
  • Known issues documented in github Issues tickets (not just listed in text)
  • Tutorial / Walkthrough / Example usage
  • Resolve TODO items in documents and remove them
  • All Contributors should have signed Samvera Contibutor License Agreement (CLA)

@jrgriffiniii
Copy link
Contributor Author

Investigating the contributors listed in the Google Sheet linked within https://samvera.atlassian.net/wiki/spaces/samvera/pages/405211659/Samvera+Licensed+Contributors, I am not finding https://github.com/mjsuhonos or https://github.com/eocarragain listed (or their respective institutions of Ryerson University and University College Cork). Perhaps they contributed when they were located in previous roles in other organizations?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant