-
Notifications
You must be signed in to change notification settings - Fork 889
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
Is anyone maintain this repo? #2008
Comments
Unfortunately, I would have to say it's more on the dead side of things at this point. I'm the last person who's paying any attention to the repo, and it's been a while since I've had any time to devote to it. |
So 2y ago, there was this: #1834. Did this lead to anything ? There seemed to be a few people interested. Could something like what's proposed in #1998 help this project in the long run ? |
@bording I would also be interested in getting involved however I can. And it looks like the folks over at OctopuseDeploy are interested in sponsoring the project (RE: #1834 (comment) by @zentron ). Not to mention UbiSoft (RE: #1834 (comment)) - which is quite a substantial organization I may be mistaken but I believe Microsoft also uses this library in their toolchain in Azure DevOps (based on errors I've personally seen while working with it) and I know the Mono project did at least at one point. It appears to be a very widely used project. A little prodding in the right places could really help get some re-invigorated support. Notable projects / organizations using this library: |
Any progress on this? |
There is number of 44 opened pull requests. Most of them untouched by maintainers. Last release was in December of 2019. Is anyone here who own this repo and maintain it? Or we can consider this project as dead?
The text was updated successfully, but these errors were encountered: