Re: player project

I suggest checking out http://playerstage.sourceforge.net/wiki/Roadmap and
http://playerstage.sourceforge.net/wiki/Contributing to get started.  There
are several bugs and feature requests open on the bug tracker, and there's a
multitude of things that could otherwise be improved.  Off of the top of my
head I can come up with:

* adding interfaces to libstageplugin 
* debugging client disconnect/reconnect problems with libstageplugin
* cleaning up example config/world files, and adding better error checking
for malformed config files
* adding an option to disable all player drivers from building to avoid a
mess like in [1]
* testing and fixing player drivers
* clarifying player driver documentation, adding info for undocumented
config file options
* porting serial and Ethernet based drivers to use
serialstream/tcpstream/flexiport through an opaque interface 
* adding a fault tolerance model for driver communication
* creating a graphical player launcher
* parsing drivers for config file options, required and optional "provides",
required and optional "requires", and adding them as options to a graphical
launcher
* standardizing config file option names
* break up libplayerdrivers into individual plugin libraries, maintain
ability to list available drivers when "player" is typed on command line
* graceful failure when a client program loses connection to the server (no
core dumps)
* fix documentation build process, add it to cmake build process

I'm not sure how active Player development is anymore.  It looks like most
people have moved on to other projects like ROS, and Player is in "accept
patches/maintenance" mode.  I wouldn't let that discourage you though, it's
still a powerful piece of software, and there's definitely lots of
opportunity for improvement.

Rich

[1]:
http://playerstage.sourceforge.net/wiki/Cross_Compile_Player_with_Openembedd
ed_and_bitBake

-----Original Message-----
From: Richard Vaughan [mailto:[email protected]] 
Sent: Sunday, May 23, 2010 2:47 PM
To: [email protected]
Subject: Re: [Playerstage-developers] player project

Hi Mohammed,

Thanks for your interest! The best thing to do is to pick something to
work on, preferably something you care about for your research/school
work, etc. and contribute some patches or new code. Use the patch
tracker at first, and keep in touch via the mailing lists. If your
stuff is useful and well done, it'll soon become easier for us to give
you commit rights than to manage all your nice patches.

Feel free to use this list to discuss things you might work on.

I hope you have fun hacking on Player code!

Richard/

On Sun, May 23, 2010 at 4:11 PM, Mohammed Rashad <[email protected]> wrote:
> Hi all,
> I would like to join Player Project and contribute to it. I had done a
> geo-visualization project using GRASS GIS & UMN MapServer
> http://keralainfo.web4all.in/resources/htdocs/index.php. Also made some
> contributions to GRASS GIS Project http://grass.itc.it
>
http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/data_catalog.
> i had a good knowledge in C, C++,Python & Java. Also done two custom
> projects using QT & mysql and
> have openGL basics. I had done a software for linux remote administration
> using C++ & FOX (Toolkit)
> will you allow me to join this project. my email id is [email protected]
> my sourceforge id is rashadkm
>
>
>
----------------------------------------------------------------------------
--
>
>
> _______________________________________________
> Playerstage-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/playerstage-developers
>
>



-- 
Richard Vaughan
Autonomy Lab / Computing Science / Simon Fraser University

----------------------------------------------------------------------------
--

_______________________________________________
Playerstage-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/playerstage-developers


------------------------------------------------------------------------------