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

Evaluate as candidate for maintenance #482

Open
9 tasks
MelSumner opened this issue Feb 17, 2024 · 1 comment
Open
9 tasks

Evaluate as candidate for maintenance #482

MelSumner opened this issue Feb 17, 2024 · 1 comment

Comments

@MelSumner
Copy link

MelSumner commented Feb 17, 2024

Summary

Per the plan to make this org's add-ons more consistent so it is simpler for org volunteers to maintain, evaluate repo to determine if it should continue to be maintained or archived.

Outcome

As a first step in the maintenance and upgrade project, the ember-cognito repository is marked for continued maintenance or archival.

Evaluation Criteria

Potential criteria for determining the value of continuing to maintain a repo are:

  • An existing champion / maintainer or well-maintained fork
  • Ember Inspector Reports
  • GitHub statistics: forks / stars / etc.
  • History of issues / ember discord messages requesting updates + bumps
  • External usage statistics (e.g. npm downloads, relative to comparable packages)

Acceptance Criteria

This issue is considered complete when:

  • Evaluation is commented in this issue
  • If recommended to archive, a PR is filed to recommend archive. Ensure README is included in PR with the updated information at the top of the file (don't delete the other content, in case folks are still using it and need to refer to the doc).
  • cc @adopted-ember-addons/admin and current primary maintaners for review.
  • If marked for continued maintenance, go into the ember-cognito maintenance and upgrade project and convert TODO drafts to issues.

Questions? Ask in the #adopted-ember-addons channel in Discord.

@RobbieTheWagner
Copy link
Member

👋 @MelSumner I use this addon personally, so I definitely think we should keep it around.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants