Identify projects that might be candidates for removal

[griggsca91]

Problem

As time goes on projects may no longer be maintained and worked on, and eventually become stale. This list will have those projects that once were active, but not anymore.

This causes an issue of making it harder to use this list for people looking for current and maintained libraries to use.

These projects are still awesome in their own right and have a good source of information for many who may look for it, but it will do this project good to remove them from this list until they start maintaining the project again.

Proposal

Have a schedule Github action that would run at a determined interval (once a day, once a week, once a month) and polls the current list of projects for information using the Github api

Identify the projects that are candidates for removal based on criteria below:

• Over 1 year without a commit
• The project is not "Feature Complete"
• Issues have no activity for over a year
• No current PR in the awesome-go project that has it listed for removal already
• <Insert Criteria here>

Create an issue in the identified project that says it's going to be removed from awesome-go

Create a PR that removes the said project, with the issue created above, and the criteria that this project matched in order to make it a candidate for removal

Maintainers of this project will review the pr and criteria and make a decision on whether to accept it or not

Please provide any feedback or suggestions for this proposal if there are any differing opinions or ideas for it. Always open to opposing ideas, challenges, and areas of improvement :)

[phanirithvij]

Create an issue in the identified project that says it's going to be removed from awesome-go

PR should suffice. No point in creating an issue.

[phanirithvij]

The projects need not be spammed with our automated PRs. We can mention the owner and submitter of a project in the PR if necessary.

[griggsca91]

In the contribution docs, there is a mention of creating an issue in the project letting them know. https://github.com/avelino/awesome-go/blob/main/CONTRIBUTING.md#how-to-remove-an-item-from-the-list

Is this action something we want to discuss?

[griggsca91]

but do agree, spamming other projects iwth an automation might not be for the best

[phanirithvij]

Yes It does exist in the current removal guide but the removed projects usually are inactive for many years and expecting a response after notifying the project really wasn't necessary as of yet.
Removal due to other reasons (very rarely) can have discussions in the removal PR itself.
I don't think we need to notify in the project repo.

[griggsca91]

started a draft of a POC and exploring githubs api, would need to discuss thoughts on what we would want to look for in an "unhealthy" package

also we would need to accept that some packages that aren't hosted on github would need to be ignored for now