Clarify status of maintained repos #54
Replies: 2 comments
|
At some point I'm planning to go through them and help. But, if you want to start looking at how you can help out some of these projects, that could be useful. Our archived repos have been very deliberately abandoned (e.g. because we upstreamed the project, or we're confident there are no real users left and we don't want to maintain it). So, I'm cautious about actually archiving projects (we've revived several projects after as much as a 5 year gap). |
|
For some projects, I know that the maintainers don't necessarily have enough time but they didn't abandon them. Some maintainers are in contact with me, but sometimes they write me in private rather than publicly. I've met @ods a couple of times in person, for example ( For |
Uh oh!
There was an error while loading. Please reload this page.
The aio-libs organization currently have 65 non-archived repos, some of them without commits or answers in a long time.
I think it would be useful to investigate the status and suggest what to do with that repos. I was thinking that for some repos (abandoned clients and utils) we should archive, like: (https://github.com/aio-libs/aiocouchdb, https://github.com/aio-libs/aiohttp-benchmarks and https://github.com/aio-libs/aioppspp)
And for others we should clarify if it's currently maintained and try to find a maintaneer or collaborators needed. (like: https://github.com/aio-libs/aiomysql)
Should I do a fundamented suggestion per repo? And in that case should I do it on here or as an issue in each repo?
All reactions