-
Notifications
You must be signed in to change notification settings - Fork 116
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
state project maintenance status #77
Comments
I should also mention that #46 is practically rendering stderred useless on MacOS. |
I'd be happy to invite more maintainers as I no longer understand most of this codebase anyway ;) I'm not C programmer by trade, and there are definitely better people to continue develop and maintain this project. @cehoffman is the one who probably knows this codebase best at the moment, but I guess he's been busy with other things (life in general :)) recently, so I'm open for any option/suggestion that could help stderred project. |
While my days as C/C++ are long gone (and happy about it), I can probably know enough to be able to test and review incoming PRs. |
@sickill Please sent me an invite, I will try to give a hand on that. Maybe others will join the effort so we can keep it alive. The reality is that at least on |
@ssbarnea are you still interested in giving a hand on stderred? I missed your prev comment, sorry about that. |
@ssbarnea Can you expand on the |
@ssbarnea Bump |
@ku1ik I'm interested! |
I love
stderred
and I used it for years but the fact that project seems to be unmaintained at this moment worries me.@sickill Maybe it would be a good idea to invite others to take care of the project maintenance so they can take care of doing reviews, sorting bugs and maybe even making new releases.
Does anyone knows an alternative that works on MacOS that is not affected by the the #60 bug?
The text was updated successfully, but these errors were encountered: