i've thrown together something speculative based on comments in http://mail-archives.apache.org/mod_mbox/incubator-general/200606.mbox/% [EMAIL PROTECTED]
i think that jakarta might be a good home for a central point for specification API implementations in Java and is definitely less work than creating a new API. if anyone has strong objections to jakarta hosting this, please post them here. otherwise, it's probably better to join the thread over in the incubator. - robert On Wed, 2006-06-07 at 20:15 +0000, Apache Wiki wrote: > Dear Wiki user, > > You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for > change notification. > > The following page has been changed by RobertBurrellDonkin: > http://wiki.apache.org/jakarta/SpecificationRepository > > The comment on the change is: > First draft for a proposal to host an API specification [EMAIL PROTECTED] > > New page: > = API Specification Repository = > > == Rationale == > > Apache has many codebases scattered throughout various projects that > containing clean room implementations of specification APIs. > > Though these are extremely useful, there is no central location where users, > developers or committers can find which specifications Apache has clean room > API implementations for. > > In addition, there is no space where existing committers from different > projects can collaborate on clean room API implementations of mutual benefit. > > There are various legal issues which arise from clean room API > implementations. A central point of contact should make it easier to manage > these issues. > > Jakarta seems an ideal candidate for hosting a central specification > repository. Jakarta is well known amongst Java users. Jakarta is also neutral > development ground. > > == Manifesto == > > * To maintain a central index of Specification API's with clean room Apache > implementations in Java whether hosted in a repository @ Jakarta or elsewhere > * To host a repository allowing: > * existing Apache committers to collaborate on clean room specification > API implementations in Java > * existing Apache clean room specification API implementations in Java to > be maintained > * new specification API implementations in Java to be homed at Apache > after vetting and approval by the incubator > * To documentation the legal difficulties around clean room implementations > * To accept that some projects may prefer to maintain their own APIs > * To accept that one day a TLP may be preferrable > * To offer advice (when asked) on the creation of clean room API > implementations > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
signature.asc
Description: This is a digitally signed message part
