Comments (7)
Comment by piyushk
Monday Apr 24, 2017 at 20:53 GMT
I understand the issues with extra maintenance effort. If you would prefer, you can also merge freenect_*
into a meta repo as well.
I also recommend calling the repository rgbd_meta
.
from openni_camera.
Comment by 130s
Monday Apr 24, 2017 at 21:11 GMT
@piyushk I'm only doing the release tasks for these packages so feedback from actual developers like you is appreciated.
Do you mean to include freenect_*
into the same single repo where openni_*
and rgbd_*
are, and that repo name can be rgbd_meta
?
from openni_camera.
Comment by piyushk
Monday Apr 24, 2017 at 21:21 GMT
@130s Thanks for spending time releasing!
Yes, that is exactly what I meant!
from openni_camera.
Comment by 130s
Tuesday Apr 25, 2017 at 01:21 GMT
I see.
@piyushk could you provide one more feedback? A caveat I can think of by the unified release from the aggregated repo is that all packages need to align the same package version. The current ersions taken from the main branch of each repo:
- 0.4.2 https://github.com/ros-drivers/freenect_stack (btw I was able to find only this package that prefixes with
freenect_
). - 1.9.5 https://github.com/ros-drivers/openni_camera
- 1.9.8 https://github.com/ros-drivers/openni_launch
- 2.1.3 https://github.com/ros-drivers/rgbd_launch
I propose either:
- 2.2.0 (adjusting to the highest available, rgbd_launch, and incremented minor ver)
- 3.0.0 (similar to adjusting to the highest available but incremented major ver for simplicity)
from openni_camera.
Comment by piyushk
Tuesday Apr 25, 2017 at 01:34 GMT
That's the only repository. There are multiple packages inside it.
I would recommend 2.1.4
across all of them, since this change maintains backward compatibility. However, given that other numbers are going to change, 2.2.0
sounds good to me.
from openni_camera.
Comment by mintar
Tuesday May 30, 2017 at 11:50 GMT
What about openni2_camera and openni2_launch? openni2_launch also depends on rgbd_launch, so by that logic it should also go into that merged repo.
Personally, I'm not convinced of the proposal to merge everything together. Especially openni2_camera, openni_camera and freenect_stack don't seem to have any inter-dependencies (please correct me if I'm wrong). It might be more convenient to release everything in one go, but I think this is outweighed by the loss of clarity when trying to pinpoint a bug in one mega-repository.
Also, there are third-party packages for cameras such as the Orbbec Astra that include rgbd_launch. It's a bit weird for them to require the freenect, openni and openni2 libraries just to include some launch file.
Just my 2 cents, it's up to you maintainers to decide. :)
from openni_camera.
Issue mover script ended in the middle so not all comments were moved. I don't know why. I completed the original ticket anyway, so closing.
from openni_camera.
Related Issues (20)
- [ROS Lunar] many gcc warning
- Consolidate rgbd repositories into a single repo HOT 1
- 'process has died' while executing openni.launch with Kinect1 HOT 14
- Failed to load nodelet [/camera/rgb_rectify_mono] of type [image_proc/rectify] even after refreshing the cache: Failed to load library /home/ap4isr/kinetic_workspc/devel/lib//libimage_proc. HOT 2
- moving launch files for processing nodelets to a driver independent package HOT 14
- No point cloud when using hardware depth registration HOT 5
- Error with Kinect using standalone OpenNI only after installing openni_launch for ROS too HOT 1
- No Data by using Depth_Registration HOT 2
- Problem with IR image HOT 2
- No data received HOT 1
- ROS Lunar release disabled (since 1.11.0) HOT 1
- Melodic Release? HOT 3
- How to get registered depth camera data in gazebo?
- ROS Melodic on RockPro64 - no devices connnected
- Command invalid when launching on ros kinetic
- Please Help! nodelet: /usr/include/boost/smart_ptr/shared_ptr.hpp:728: typename boost::detail::sp_dereference::type boost::shared_ptr::operator*() const [with T = xn::NodeInfo; typename boost::detail::sp_dereference::type = xn::NodeInfo&]: Assertion `px != 0' failed. HOT 1
- OpenNI compatibility with CSI-2 connection?
- Noetic release request HOT 9
- ROS Melodic + Ubuntu Mate 18.04 + Kinect V1 + Raspberry PI 4B
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from openni_camera.