-
Notifications
You must be signed in to change notification settings - Fork 25
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
Abandon the repository? #3
Comments
I wonder if |
@jihoonl we've moved The reason we integrated roswww into another package suite was only because we then thought a bit verbose to have many web-related repositories, according to tork-a/rwt_ros#2 (comment) (in Japanese sorry). |
It is good to keep in the rwt_ros branch as long as it is released as deb with clean dependency chain. :) I would like to propose some changes to use roswww as catkin_based webserver which does not bring ros_comm dependency. I will create other issue to propose changes in rwt_ros. |
I was just curious because it was not release in indigo. 😉 |
BTW. Wouldn't it be better to release only roswww? Javascript libs like roslibjs and ros2djs could easily be out of sync from upstream.. |
roswww update proposal tork-a/rwt_ros#13 |
Releasing as DEB is actually not in the plan for
Yeah. That's what I wanted to mean in #3 (comment)
I might be too behind web-development scene to figure out what you mean by this. |
@jihoonl Actually I invited you for a write access if you feel like ;) |
Great thanks! |
We're not abandoning this repository. |
Since
roswww
is now merged intorwt_ros
(see tork-a/rwt_ros#2 (comment)), keeping a separate repository might be just confusing.roswww
used to be released into ROS Groovy too, but it was withdrawn.The text was updated successfully, but these errors were encountered: