-
Notifications
You must be signed in to change notification settings - Fork 68
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 abandoned? #81
Comments
it's not very active right now as maintainers are mainly focused on doing other things. I'll review and merge certain PRs if they're things I know enough about/sensible-enough but that's generally it. If anyone wants to pick it up and do more with it they're more than welcome to pitch in though 😄 |
Hope to see more maintainers in the near future :)
I wish I could help but lack much knowledge with AI and stuff.
…On Wednesday, May 8th, 2024 at 11:53 PM, xd009642 ***@***.***> wrote:
it's not very active right now as maintainers are mainly focused on doing other things. I'll review and merge certain PRs if they're things I know enough about/sensible-enough but that's generally it. If anyone wants to pick it up and do more with it they're more than welcome to pitch in though 😄
—
Reply to this email directly, [view it on GitHub](#81 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AG7P2BTPILVCLUF4CB2222TZBIU4XAVCNFSM6AAAAABHNAC7J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBQGYZTCNZWGI).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Would the maintainers be open to merging this crate with the |
If the imageproc people wanted to do that I'd have no opposition to it personally. I don't think they will though, like one of the reasons this started was because imageproc a few years ago had a number of unfortunate limitations making it's use for computer vision limited to image processing. This crate is also more focused on 3D computer vision stuff so there's a lot of non-image based functionality for 3D geometry solving, point clouds, non-linear optimisation etc. Generally, all the stuff you need for vSLAM. If you wanted to look at merging it I'd start by identifying something present here and not in imageproc and then raising an issue on their repo to see if it's a desired feature. If it is you can grab the code from here and integrate it into their library (may require some refactoring to match their APIs etc). The licensing does allow for that and that's the kind of approach that makes it feasible for maintainers to actually review and consider features (as opposed to opening a ton of PRs without prior communication). |
Anything which could be moved out of here and into imageproc probably should be. We have some things being used for akaze for instance like shar filters which maybe belong there. I would consider this project to be, at most, kept up to date with new versions of dependencies. Active development has been light for a while now. This isn't to say that it can't begin again. Anyone who is interested in taking over some of these things can ask me or @xd009642 about taking over crate ownership or other possibilities. |
last commit was 10 months ago so wanted to know if it is still alive or not?
The text was updated successfully, but these errors were encountered: