<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Background: <br>
The existing p2os repository is <a class="moz-txt-link-freetext" href="https://github.com/allenh1/p2os">https://github.com/allenh1/p2os</a><br>
The issue in question about transferring ownership is
<a class="moz-txt-link-freetext" href="https://github.com/allenh1/p2os/issues/14">https://github.com/allenh1/p2os/issues/14</a><br>
<br>
<br>
In general, if a ROS package is missing functionality or has bugs,
you should file a bug report, to let the maintainer know that there
is a problem. If you have fixes for a particular bug or additional
features, you should submit them as a pull request.<br>
<br>
<br>
Looking at the issue history for the p2os driver, I see that the
level of support is actually quite good: there are no open bug
reports, no open pull requests, and there has been a new release
fairly quickly after major issues were addressed.<br>
<br>
<br>
Aris: I suggest you fork the github repository, and submit your
fixes as pull requests. If you'd like the maintainer to make a
release of the p2os driver into Hydro or Indigo, open an issue
requesting a release, and see what the response is.<br>
<br>
Regards,<br>
-Austin<br>
<br>
<div class="moz-cite-prefix">On 05/29/2014 07:37 AM, Gert Kanter
wrote:<br>
</div>
<blockquote
cite="mid:CAE0DJibqL8kEpGGjmN_Jh1-bttE54P5OnXVh2K6F2gnFb1qgng@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Hi!<br>
<br>
I, for one, am in favor of taking over maintainership. If
Hunter Allen is not motivated (or too busy etc) maintaining
the package (already two ROS releases!), then in the
interest of the community, a willing and active new
maintainer should be able to pick up the slack. This way the
original contributors of the p2os can still be (more
prominently) credited for their previous contributions,
especially if you have originally forked the improved p2os
from the old p2os. I also agree that yet another package
that is a successor of a unmaintained package just adds
confusion for the community (and obscures the actively
maintained package from new ROS users).<br>
<br>
</div>
<div>It would be best if Hunter would approve of this action,
of course.<br>
</div>
<div><br>
</div>
Disclaimer: I am working on a robot with the Pioneer mobile
platform with p2os and I am very interested in the mentioned
new developments in your private repository.<br>
<br>
<br>
</div>
<div>Just my two cents,<br>
</div>
Gert Kanter<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2014-05-29 16:19 GMT+03:00 Aris
Synodinos <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:asynodin@mech.upatras.gr" target="_blank">asynodin@mech.upatras.gr</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi,<br>
<br>
I have just recently sent the following(cited) email about
the maintenance status of p2os, but since I was not a
member of the list, the email has not been made public. I
am therefore forwarding the email again, hoping that you
will not receive it twice. Just yesterday the maintainer
of p2os pushed a new commit to the p2os package, which is
however mostly unmaintained and old (no rqt - no
ros_control - no simulation etc). I have contacted the
ros-sig-pioneer mailing list as you can see in the
previous email and we want to not mix things up for the
community. <br>
<br>
Currently there are two drivers for pioneer robots,
rosaria and p2os. Rosaria is actively maintained by the
members of ros-sig-pioneer and uses libaria to communicate
with the robots. P2os however, which dates back to the
stage driver, has been left without proper ros support for
a long time, with no major upgrade ever since electric.
Hunter Allen used a part of Dereck Wonnacott's work ( <a
moz-do-not-send="true"
href="https://github.com/dawonn/ros-p2os-driver"
target="_blank">https://github.com/dawonn/ros-p2os-driver</a>
) and ported p2os to groovy, using bloom for releasing
the code with debs.<br>
<br>
The problem is that H. Allen is not updating the driver
(very little support) and due to the fact that he has
released the driver with the p2os package name, no one
else can take ownership/maintainership without causing
unnecessary confusion to the community. The result is very
poor support for p2os, (until yesterday there were no
install targets for p2os, so the deb packages were empty)
and outdated support (groovy). I have tried contacting H.
Allen about stepping up to the job, but he closed the
issue without responding.<br>
<br>
What is the proper way to proceed? Is it preferable to
release a new package under a different name? I will
upload my code publicly on github as soon as this is
resolved, under the same (p2os) or a different name if
that is requested. Currently, my code is in a private
bitbucket repository.<br>
<br>
Regards,<br>
Aris<br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Sun, May 25, 2014 at 10:30
AM, Aris Synodinos <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:asynodin@mech.upatras.gr"
target="_blank">asynodin@mech.upatras.gr</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px
0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">After contacting the ros-sig-pioneer
mailing list, and since the previous maintainer is
unfortunately not responding and has stopped
maintaining the p2os package, I am willing to step
up and claim maintainership of the package. <br>
<br>
I have fixed the issues that exist for groovy (no
install directives in cmake making the debian
package unusable), added features in hydro (moveit
integration, rqt_dashboard etc) and am willing to
continue maintaining it for future versions
(indigo etc).<br>
<br>
Please inform me how to proceed for this to
happen. Currently I have published all my work in
a private repo in bitbucket so as not to cause
confusion to the community, but of course I will
publish this in github when this is desirable.<br>
<br>
Here is the issue I created for the maintainership
status in github:<br>
<a moz-do-not-send="true"
href="https://github.com/allenh1/p2os/issues/14"
target="_blank">https://github.com/allenh1/p2os/issues/14</a><br>
<br>
Here is the mail in the ros-sig-pioneer mailing
list:<br>
<a moz-do-not-send="true"
href="https://groups.google.com/forum/?fromgroups#%21topic/ros-sig-pioneer/GVe3IQUn7cU"
target="_blank">https://groups.google.com/forum/?fromgroups#!topic/ros-sig-pioneer/GVe3IQUn7cU</a><span
class="HOEnZb"><font color="#888888"><span><font
color="#888888"><br>
<div><br>
</div>
<div>-- <br>
<div dir="ltr">Aris Synodinos<br>
PhD Student<br>
Robotics Group<a
moz-do-not-send="true"
href="https://github.com/dawonn/ros-p2os-driver"
target="_blank">https://github.com/dawonn/ros-p2os-driver</a><br>
Mechanical and Aeronautics Engineering
Department<br>
Tel. <a moz-do-not-send="true"
href="tel:%2B30-2610-996248"
value="+302610996248"
target="_blank">+30-2610-996248</a><br>
e-mail: <a moz-do-not-send="true"
href="mailto:asynodin@mech.upatras.gr"
target="_blank">asynodin@mech.upatras.gr</a><br>
Web: <a moz-do-not-send="true"
href="http://robotics.mech.upatras.gr/"
target="_blank">http://robotics.mech.upatras.gr/</a></div>
</div>
</font></span></font></span></div>
<span class="HOEnZb"><font color="#888888">
</font></span></blockquote>
</div>
<span class="HOEnZb"><font color="#888888"><br>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">Aris Synodinos<br>
PhD Student<br>
Robotics Group<br>
Mechanical and Aeronautics Engineering Department<br>
Tel. <a moz-do-not-send="true"
href="tel:%2B30-2610-996248"
value="+302610996248" target="_blank">+30-2610-996248</a><br>
e-mail: <a moz-do-not-send="true"
href="mailto:asynodin@mech.upatras.gr"
target="_blank">asynodin@mech.upatras.gr</a><br>
Web: <a moz-do-not-send="true"
href="http://robotics.mech.upatras.gr/"
target="_blank">http://robotics.mech.upatras.gr/</a></div>
</font></span></div>
</div>
<br>
_______________________________________________<br>
ros-release mailing list<br>
<a moz-do-not-send="true"
href="mailto:ros-release@code.ros.org">ros-release@code.ros.org</a><br>
<a moz-do-not-send="true"
href="http://lists.ros.org/mailman/listinfo/ros-release"
target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
ros-release mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ros-release@code.ros.org">ros-release@code.ros.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ros.org/mailman/listinfo/ros-release">http://lists.ros.org/mailman/listinfo/ros-release</a>
</pre>
</blockquote>
<br>
</body>
</html>