Hi Werner, et al.
I'd like to touch again on the subject of "Intalio controlling Castor". It's true that the project was started by Intalio engineers, but as I pointed out many current committers are not employees, or contractors of Intalio. I should also add that my views are not representative of Intalio. In other word's I don't speak on Intalio's behave. It is my opinion however, that Intalio would prefer to stay out of "controlling Castor" and leave that up to the general Castor community. Intalio doesn't make money on Castor, they just use it to solve some problems, and felt that the general public could use it also. Intalio's main product is Intalio|n3, which is a Business Process Management System. That's where Intalio's main focus is. I am sure they would rather have Arnaud and I spend much more of our time working solely on Intalio|n3. It is true that Arnaud and I are both Intalio engineers. However we both work on Castor, because we really like the project and want to see it continually improve, not because Intalio wants to control it. Intalio has no vested interest in controlling it. As one of the original authors of Castor, I can say I am quite attached to it and I enjoy working with the public on improving it. I often fight for spending more time on it. Anyway...I think the more time you spend with Castor the more you will actually realize the influence that you all have on the project. I feel that we have a great community of users on this project and even if I don't reply to every single message on the list...I read every one (well I quickly skim some of the JDO ones, but I do try to get interested in that part of the project!) Thanks, --Keith Keith Visco wrote: > > Werner Guttmann wrote: > > > > Keith, > > > > > [lots of content snipped] > > > > > Yes and no. Exolab/Intalio certainly started the project, and the Castor > > > JDO project leader is from Intalio, but the rest of the JDO > > > committers/contributors are not from Intalio. I really believe the > > > community can control for the most part the direction of Castor JDO. > > > > Can you please give one or two examples where you think the community can *not* > > control the direction of Castor ? > > That's a very difficult question to answer. To be direct, the current > committers are the only ones with actual CVS write access. So in the > end, patches and enhancements must be commited by those with write > access. So the committers must agree that the changes are actually > beneficial to the community in general before committing them. > > If the many users really want a feature and someone is willing to write > and test the feature, then I see no reason why it would not be accepted. > > On the other hand if one person writes a patch and the patch is highly > specific to the individuals case, it might not be accepted. The patch > can be made available to the public via the list or any other means the > user may have at his or her disposal however. > > However, in both of these cases the community is really controlling the > direction, because user-demand or user-non-demand can cause features to > be accepted or rejected. > > In the end however, the decision will ultimately come from the > committers. A reason will always be given for not accepting a patch and > the community can comment about whether they agree or disagree. > > > > > I think that most of the people here on the list willing to contribute will have > > a need to understand what the limitations are, and > > whether any (substantial) progress can be made without being 'overruled' by >Intalio. > > This is a common misconception. If you look at the committers list you > will notice many non-Intalio committers. Intalio doesn't control Castor. > Intalio can control what Thomas, Arnaud, and I work on during work > hours, but they don't control Castor. Many of my contributions come > after hours...as you can see it's 4:00am as I write this e-mail! > > Also if you look at the contributors list you will find far more > non-Intalio contributors than Intalio ones. > > I think any reasonable patch that is well tested will be checked into > the CVS. > > > I think it all comes down to what license Castor JDO currently has and will have in > > the future. > > The license won't change. It's very liberal. It's a BSD style license > that has very few restrictions and nothing that prevents Commercial or > private use. > > The license is available with the source code, binary distributions as > well as on the website: > > http://castor.exolab.org/license.html > > --Keith > > ----------------------------------------------------------- > 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
