No longer actively maintained repositories

[chaconnewu]

According to our discussion #626, I generated a list of not-pushed-in-previous-3-month repositories with date pulling from GitHub API:

• Cordova
• Dart
• Coldfusion
• Fortran
• Web Components
• Dojo Toolkit
• Inspiration
• Play1 Framework
• Speech and Natural Language Processing
• Spanish
• Spanish
• Linguistics
• Cryptography
• Dev Env
• Speaking
• Tech Videos
• Radio
• Open Companies
• Services Engineering
• Sketch (OS X app)
• FOSS Production Apps
• Answers
• Productivity
• JSON Datasets

[sindresorhus]

@chaconnewu I don't think 3 months is a good enough metric alone. How many open PRs is also a good factor. Some lists just aren't that active just because the community is small or inactive.

[davisonio]

I think we're mostly concerned about the lists where people's contributions (pull-requests) are not being reviewed, I've gone through your list and here's the ones where I think there's a bit of a problem with inactivity:

• Cordova - 1 unreviewed PR
• Play1 Framework - 2 unreviewed PRs
• Speech and Natural Language Processing - 10 unreviewed PRs
• Dev Env - 5 unreviewed PRs

[chaconnewu]

@davisonio @sindresorhus I think that the number of open PRs is definitely one important perspective. So maybe it is better to use different metrics for bigger and smaller community?

[davisonio]

So maybe it is better to use different metrics for bigger and smaller community?

Not necessarily, I think that mostly the awesome lists need to be monitored manually regularly to check that people's contributions are being taken into account.

The most useful thing to generate in my opinion would be to check for unreviewed pull requests.

---

@busterc @PerfectCarl @edobashira @jondot

Are you able to review the pull requests for the awesome lists highlighted above / add a collaborator to do so on your behalf?

[busterc]

@davisonio I agree that unreviewed PRs are the better metric to consider. Also, I've reviewed the 1 outstanding PR and updating the list.

If anybody out there is interested in being a collaborator on Awesome Cordova, just let me know (add an issue).

[inputsh]

Maybe instead of "nothing pushed in the last three months" we can have something like "no pull requests reviewed in the last three months"?

[chaconnewu]

In my opinion, 'no pull requests reviewed' partially reflects the maintainer's commitment. It signals the owner's willingness to interact with the community. However, what if authors don't hold the same standard and just try to comply with this metric? I'm more concerned about the maintenance of existing resources. Many curated lists index software projects, and many indexed projects are deprecated if they are no long maintained or replaced by better ones, which should be reflected in the lists.

[rachmadaniHaryono]

what about migrated project? https://github.com/rosarior/awesome-django is migrated to gitlab and didn't process any PR from december

[JesseTG]

Why not add a .travis.yml to this project that, among other things, checks to see which repos are active? It doesn't even have to cause a failure, it could just e-mail @sindresorhus or post an automatic issue here or something.

[sindresorhus]

@JesseTG How do you programmatically define inactivity though? Some lists are just inactive because they're about an obscure thing. Some are inactive because they're pretty much done.

[JesseTG]

@sindresorhus Maybe once every six months or so the maintainer should check in on an issue thread or with an e-mail or something, if they don't have a reason to update the list itself?

[web-padawan]

I know that this issue is outdated, would like to let you know that Web Components list is maintained again. I have put some effort into actualising that list, and will be working to keep it up-to-date. Also, will align it with the guidelines. The only thing I have to keep for now is the MIT license (haven't yet asked the author about it though, could be that he would allow moving to Creative Commons).

[jjangga0214]

@JesseTG @sindresorhus I got what @sindresorhus worried about. Yes, there is no simple metric to carefully decide which repo is inactive. However, I think @JesseTG's idea is also great, not for final decision making, but to suggest some repos that we might ought to reconsider, which would helps us enhance a kind of productivity and reduce mistake.

[davisonio]

@chaconnewu wonder if you could share the script you used to calculate these back in 2017? Would be great to run this again to see if there are any more unmaintained lists.

[elenigen]

There's graphql which has 79 PRs and almost two months of inactivity.
Is there something we can do? ... Fork and change the reference?

[davisonio]

Try emailing the creator first @chentsulin
I'm happy to fork and maintain if needs be but two months isn't very long for inactivity let's wait first

[elenigen]

I sent an email, so let's see if it will unblock, now it's been 3 months.

[elenigen]

@davisonio I sent an email to @chentsulin on Jan 20, 2020 and still no reply. We have now 112 PRs, last activity on Feb 12 and people agree with me that it should be faster to review and merge PRs, so we need more admins but for some reason they don't grant admin to others.
chentsulin/awesome-graphql#636

[sancarn]

@davisonio I sent an email to @chentsulin on Jan 20, 2020 and still no reply. We have now 112 PRs, last activity on Feb 12 and people agree with me that it should be faster to review and merge PRs, so we need more admins but for some reason they don't grant admin to others. chentsulin/awesome-graphql#636

Half feel like there should be an awesome organisation which owns repos like this, and the awesome repo itself and have the power to merge PRs in all repos. I can totally understand being in a situation where you are burnt out and no longer want to maintain something if you don't use the technology anymore, and don't get paid for either.

[ghost]

wait a second. you probably misunderstand something. can somebody talk to me? Bongdautay ***@***.***>於 2024年9月6日 週五，上午2:06寫道：

…

***@***.*** — Reply to this email directly, view it on GitHub <#628 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASM7JGLBVT662NKIACPX7YDZVCMSXAVCNFSM6AAAAABNHBHCAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZSGMZTANZYGA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>