My apologies Keith,
Intalio and the other contributors have been extremely generous in the
resources they provided.
Keith Visco
<kvisco@intal To: [EMAIL PROTECTED]
io.com> cc:
Subject: [castor-dev] Castor JDO status
04/22/2002
03:59 PM
Please
respond to
castor-dev
First of all, let me thank all of the current and past Castor JDO
contributors, you have all done a great job at helping to progress and
maintain Castor.
This e-mail is intended to clear up some of the confusion on the list
about the status of Castor JDO.
Castor JDO is open source. This means the souce code is freely (no cost)
available and modifiable. Feel free to modify it for your own needs,
just follow the rules of the BSD style license. If you make
modifications that are tested, and you feel others can benefit these
changes, please submit them back to the project. We appreciate test
cases along with any patches.
Currently there are no full time developers dedicated to Castor JDO.
There are a number of contributors with CVS access, such as Thomas Yip,
Bruce Snyder, Oleg Nitz, and Ned Wolpert, but none who are full-time or
even sponsored by their companies or any other company.
Contributors don't have to be from Intalio/Exolab. Anyone can be a
contributor. We grant CVS commit access to people who have demonstrated
a solid understanding of the code base, such as Ned and Bruce. If you
have time, then become a contributor. If any company wants to sponsor
developers...feel free to do so. We encourage you all to become more
pro-active in the development of Castor JDO, especially those who
benefit from it.
Thomas Yip is currently the JDO project lead, however, as he has stated
in the past, his time is very limited. This doesn't prevent anyone else
from stepping up and contributing more to the project. Any one of you
can become a contributor and committer on the project, regardless of who
manages the project. All you have to do is start sending in patches to
anyone who has commit access.
I've heard a number of ramblings about why doesn't Exolab donate the
project to some other group for maintenance, or someone else should take
over, etc. Exolab simply hosts the Castor JDO project, it provides
hardware and some network services to the project. It doesn't provide
the management of the project. So it makes no sense for Exolab to get
into who or who shouldn't be managing the project. If you, or someone
you know would like to be more pro-active in helping to manage the
project, then they should be getting in touch with Thomas. They should
have a thorough understanding of Castor JDO and all the technical issues
surrounding it. If you do know someone like this, then why are they not
already contributing to the project? Probably because of time
constaints. Funny how that works.
I've grown to realize that the people who complain the most are the
people who are not providing any contributions back to the project. This
doesn't have to be the case however.
The project is really being maintained by you, the Castor JDO users. By
making the source code freely available, we have given you the ability
to fix any issues that you face. We don't prevent you from doing so at
all. I just re-read the license and there is no clause that states only
Intalio employees can update the source code. If you don't have the
technical ability to fix a bug, then you have to rely on those that do.
The fate of the project is really in the hands of the users. If everyone
wants to simply use it, but not contribute to it, then it won't go any
further than where it is today. The choice is yours.
Thanks,
--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
