[EMAIL PROTECTED] (daniel) wrote:
> Is there any chance that prc-tools development might be opened up [...]
Actually I think prc-tools development is already *open*. The maintainers
have always produced full source tarballs, and have always been very happy
to accept patches.
> Right now, the
> development is too closed to encourage any kind of participation. Making
> developers wait for prc-tools 2.1 [...] isn't the right way to go when you
> can have those developers [...] submitting patches.
But that openness doesn't mean that it's *convenient*. This isn't
1988 anymore: people today expect public CVS access rather than periodic
tarballs :-).
However, in the two years that I have been the prc-tools maintainer, there
has been noone else who has expressed interest in contributing patches
on an ongoing basis. Hence it hasn't been a big priority to make doing
so more convenient. (I believe Michael Sokolov originally intended to
contribute via patches to the same sources, but circumstances conspired
such that in the end he decided to fork a separate full distribution.
I hope that the rift can be repaired, and that the changes outlined below
can be a step in that direction.)
This is a chicken and egg problem. Perhaps if contributing were more
convenient, contributors would appear. To this end, I created a prc-tools
project at SourceForge last week: it's currently at
http://sourceforge.net/project/?group_id=4429
though once the site gets populated, http://prc-tools.sourceforge.net/ will
be a more memorable entry point.
It will take a little while to get historical and current sources into the
CVS repository there, but there are mailing lists and other SourceForge
facilities that are useful immediately.
In particular, there is a mailing list especially for discussion of
prc-tools improvements and patches. Those interested in the development
of prc-tools can send the usual "subscribe" email to
[EMAIL PROTECTED]
or use the form at
http://lists.sourceforge.net/mailman/listinfo/prc-tools-devel
This is a more appropriate place for these discussions than any of
palm-dev-forum, pilot.programmer.gcc, and pilot-unix, which are all really
about *using* the tools, and I hope that everyone working on prc-tools
in all its flavours will be able to be comfortable there.
To be frank, this is going to be a substantial amount of extra work for me
initially, but I think in the long term it will be worthwhile. I'm looking
forward to seeing your STL contributions, Daniel!
(Followups to [EMAIL PROTECTED] please!)
John
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
