-
Notifications
You must be signed in to change notification settings - Fork 638
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
[HEALTH]: FabEdge #1459
Comments
I can see "some" activity for |
looking more in the org, it looks like those are something related to dependabot and other branches, theres only 1 activity reported and on a regular schedule. Either way, the project looks to be abandoned at this point. |
this can now move to a vote to archive the project. |
Vote created@mrbobbytables has called for a vote on The members of the following teams have binding votes:
Non-binding votes are also appreciated as a sign of support! How to voteYou can cast your vote by reacting to
Please note that voting for multiple options is not allowed and those votes won't be counted. The vote will be open for |
Additional activity note:
|
@mrbobbytables we're voting for the project to be archived is it? It might be worth making it explicit on the vote comment - it reads as we're voting on the project health. |
Vote statusSo far Summary
Binding votes (4)
|
Correct - its a vote to archive. Once this passes, the archive issue will be opened with the checklist. I'll edit the earlier comment to reflect that its a vote to archive. |
/check-vote |
Vote statusSo far Summary
Binding votes (4)
|
Vote closedThe vote passed! 🎉
Summary
Binding votes (9)
|
With the vote passing, will close this and create an archive issue |
Project name
FabEdge
Concern
There has been 0 activity since April of this year.
No releases cut since last year.
https://github.com/FabEdge
Activity:
No activity in the past 3 months
More information available here:
https://insights.lfx.linuxfoundation.org/foundation/cncf/overview/github?project=fabedge&repository=&routedFrom=Github
Prior engagement
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: