I think most people would accept that open source projects and developers undergo
quiet periods. The recurring theme of this thread though has been that the community
(both users and contributors) need to have a clear idea about the direction of the
project to ensure it stays on
track. With something as simple as a public "to do" list work can be split up and
managed easily and the Castor commiters are much more likely to get the type of
external contributions they are looking for. It is really refreshing to see the list
Thomas has published. I'd like to
see this list appear on the web site so that people have a single place to get an
overview of what features are under development and to track their progress. The
feature of great interest to myself and my team is the ability to perform searches on
foreign keys that form part of
the identity of a class (aka "the FK as part of a PK problem"). This was identified as
a high priority feature over a year ago. Had there been better documentation and a
clear understanding that no work was taking place on this feature I would have had a
go at fixing this problem
myself months ago (with this fix we can actively recommend Castor for *much* wider
use). Clear goals, clear direction and well coordinated communication about work on
specific features should regalvanize the Castor community.
Max
Pete Carapetyan wrote:
> > I agree with most of the discussion about the status of Castor JDO
> > being stagnant for a while now.
>
> Lot's of open source technologies go in and out of this mode all the time. It is a
>feature of open source.
>
> When people feel hopeful and have extra time, they contribute a ton, which usually
>wrecks everything else in their life for a while. But it is a lot of fun. Then, they
>spend a few months or years recuperating.
>
> No big deal.
>
> The key thing is that people will contribute if they feel that they are contributing
>to a winner, else they will say forget it, that xxxx is just a loser anyway. Open
>source is a very fickle world, and so it should be. Look at how many things on source
>forge do the same thing.
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
