Skip to content
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

Closed
130s opened this issue Apr 27, 2014 · 10 comments
Closed

Abandon the repository? #3

130s opened this issue Apr 27, 2014 · 10 comments

Comments

@130s
Copy link
Contributor

130s commented Apr 27, 2014

Since roswww is now merged into rwt_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.

@jihoonl
Copy link
Member

jihoonl commented Dec 7, 2014

I wonder if roswww is no longer maintained. If yes, could I take it back? I would like to revive the package with some api changes.

@130s
Copy link
Contributor Author

130s commented Dec 7, 2014

@jihoonl we've moved roswww under rwt_ros. We're happy to maintain it there (and of course accepting PRs) but we're open to suggestions as well.

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). rwt_ros is intended as an app layer framework laid on top of rwt, and is slowly developed (a project is going on now). Now, however, I reviewed the decision and I started feeling roswww doesn't necessarily lie under rwt umbrella so it might be better to separate it back (that allows us to DEB-release easily like it used to be).

@jihoonl
Copy link
Member

jihoonl commented Dec 7, 2014

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.

@jihoonl
Copy link
Member

jihoonl commented Dec 7, 2014

I was just curious because it was not release in indigo. 😉

@jihoonl
Copy link
Member

jihoonl commented Dec 7, 2014

BTW. Wouldn't it be better to release only roswww?

Javascript libs like roslibjs and ros2djs could easily be out of sync from upstream..

@jihoonl
Copy link
Member

jihoonl commented Dec 8, 2014

roswww update proposal tork-a/rwt_ros#13

@130s
Copy link
Contributor Author

130s commented Dec 8, 2014

rwt_ros branch as long as it is released as deb with clean dependency chain. :)

Releasing as DEB is actually not in the plan for rwt_ros yet (needs to happen. Related: tork-a/rwt_ros#3).

BTW. Wouldn't it be better to release only roswww?

Yeah. That's what I wanted to mean in #3 (comment)
I guess we rejuvenate roswww_pkg as standalone repository so that it can be released separately. I can do so only later this week but I or someone can review pull requests that'll make it happen faster.

Javascript libs like roslibjs and ros2djs could easily be out of sync from upstream..

I might be too behind web-development scene to figure out what you mean by this.

@130s
Copy link
Contributor Author

130s commented Dec 8, 2014

@jihoonl Actually I invited you for a write access if you feel like ;)

@jihoonl
Copy link
Member

jihoonl commented Dec 9, 2014

Great thanks!

@130s 130s changed the title Abondan the repository? Abandon the repository? Dec 12, 2014
@130s
Copy link
Contributor Author

130s commented Dec 12, 2014

We're not abandoning this repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants