Re: [Playerstage-developers] developing new Player robot driver

[Dafydd W. <da...@wa...>]

Since I need to get my driver for the Open Automaton Project up and
running quickly, I've decided to keep things simple for the initial
version, and worry about some of the finer points, like the sonar timing
issues, later.

So, for now, I'm going to press on with writing the following
drivers/interfaces initially:

 oap_sonar/sonar
 oap_sonar/bumper
 oap_position/position
 oap_power/power
 oap_ptz/ptz
 oap_eltec/blobfinder

I'll try to stick to all the source code layout conventions used in the
existing code, and I'll ensure that my driver design is in keeping with
the existing drivers (I'm looking at the P2OS driver code in particular,
for guidance).

If I update all the necessary Makefile.am files, etc., and create a patch
file against the latest CVS version, what are the chances of this driver
being merged into the main CVS tree? In other words, what does it take for
a driver to be deemed "worthy"?  I'm not looking to just "throw the code
over the wall"; I'd like to be the maintainer for this driver. If this is
out of the question, I'll just maintain the OAP driver within the Open
Automaton Project, but I'd obviously prefer it to be merged into the
Player package.