Fun fact, if I'm slow on code reviews for a low-activity project you can just fork it and keep working on it at your own pace and if that goes well I'll just nominate your fork as the new upstream
-
Fun fact, if I'm slow on code reviews for a low-activity project you can just fork it and keep working on it at your own pace and if that goes well I'll just nominate your fork as the new upstream
Other maintainers may not be as cooperative as me insofar as nominating a new upstream is concerned but FYI you can fork any FOSS project with little to no fanfare
-
I do a lot of projects where the premise is "I want this to exist, and it doesn't" so I'll lay some groundwork and do some designing and architecture but I may not have time to finish the implementation or add polish. But I don't start from the premise of "I want this to exist and *I* want to be responsible for it", it's more that *someone* has to do it and so it may as well be me. But if someone else wants to adopt it and put more time into it, I'm thrilled!
-
This is what happened to aerc, by the way. I didn't have enough time to maintain it, so Robin forked it and started maintaining it and after a little bit I just nominated him as the new upstream and it has been going strong ever since