Move to WG repo?

[rctoris]

Not sure where this should live -- @baalexander ?

[jkammerl]

It is also used by the RobotWebTools packages. Why do you think the WG repo would be a better fit?

[rctoris]

I'm not aware of anything in RWT that uses this a.t.m. We waiting to here if we should switch over (e.g., for something like https://github.com/RobotWebTools/mjpegcanvasjs/tree/devel) but were advised/decided to use http://ros.org/wiki/mjpeg_server until better RTC came along.

The massive discussion on moving packages comes from the attept to keep RWT a minimul set of standard tools/libraries (e.g., https://github.com/RobotWebTools/roslibjs or https://github.com/RobotWebTools/rosbridge_suite) and to move specific implementations (e.g., https://github.com/RobotWebTools/nav2djs) into respective repos. This also prevents the RWT github from becoming a "best friends" club. An index will also be started as well to list all projects/repos.

[baalexander]

After discussing on Friday, we're looking at keeping this in Robot Web Tools as it's needed for an upcoming feature in ros3djs.

We did discuss renaming ros_http_video_streamer. One idea I said was webm_video_streamer. However, after discussing with @jkammerl, it's possible to add h264 encoding in the future (instead of just webm, like it is currently), which would allow us to support a wider range of browsers and devices (like an ipad).

[rctoris]

video_codec_streamer?

[jkammerl]

I guess you would like the package name to be shorter, right? What about ros_web_video?

[rctoris]

sounds good to me

[baalexander]

Agreed, ros_web_video sounds good.

[jkammerl]

I renamed the package in my fork: https://github.com/jkammerl/ros_web_video

Since we are already creating debs from it, I am not sure what the best way is to deprecate the current package. Maybe we should just create a new package and deprecate the ros_http_video_streamer in hydro. What do you think?