PointCloudLibrary / PointCloudLibrary/pcl
[openni] Deprecate OpenNI in favor of OpenNI2
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 4.7k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 6
Description
Currently almost all components still use OpenNI, although OpenNI2 support has been implemented for years. Somehow I am not able to run a Kinect with OpenNI on Win10, but it works with OpenNI2 (no idea why). Since both versions of the library are very old (OpenNI 2.2.0.33 was released on 2013-11-12, and OpenNI 1.5.7.10 a day before that) there won't be anything new, so I'm not sure if anyone still uses it, but at least we can say that it's enough to support only one version (with our usual deprecation cycle, it may take another ~two years until the code is really removed).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the components that still use OpenNI and compare them with the existing OpenNI2 support. Review the project's usual deprecation cycle and identify the changes needed to leave OpenNI2 as the supported version; the work is done when the remaining components follow that deprecation plan and no longer require OpenNI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-vision
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100