-
Notifications
You must be signed in to change notification settings - Fork 166
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 this project still maintained? #193
Comments
I got granted the permissions to add new maintainers, so if anyone wants to be an active maintainer I can make that happen. I neither work with netbox anymore nor do I have time to maintain this. |
I wonder if @nutgood might be interested since they're already maintaining an updated, #178 (review). |
@awlx @jfreeland, I can maintain this. While I don't use netbox anymore (and don't work @sherweb either, instead @edgedb), it was fairly straightforward to fix the issues and I have some bandwidth to maintain this. |
Cool, once I am back at my desk tomorrow (EU timezone). I'll get your permissions elevated to have the necessary things to merge and approve PRs. |
@nutgood you should have an invite now. |
@awlx Thanks I'll work on getting this updated. @couloum, @AlekseyKnyrko: Yes this project is still maintained (as of now) |
The last version is from May 2024 and is broken.
There are 3 pull requests waiting for merge that would fix problems encountered by many people.
We wanted to add support of netbox v4 from one of our tool working with netbox v3 currently, but faced issues due to openapi specification being broken compared to actual behavior of netbox v4. We are willing to fix things and submit a PR, but would like to know if this PR would have a change to be integrated into main branch.
Is there still someone to review PR and maintain code?
The text was updated successfully, but these errors were encountered: