incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: [Proposal] Blaze
Date Thu, 20 Jul 2006 07:57:30 GMT
On 7/19/06, Carl Trieloff <cctrieloff@redhat.com> wrote:
> Paul Fremantle wrote:
> > Carl
> >
> > I think some of the team have a good point on the IP and licensing
> > issues. One issue that is very frustrating from an Apache perspective
> > is if there are some committers involved in the spec process, and
> > other committers not involved.
> >
> > This is frustrating for both halves: the committers who (by dint of
> > which employer they work for) have access to information and knowledge
> > about future unpublished spec changes have to be very careful: they
> > might donate IP to Apache that is under NDA and they don't have the
> > right to use in code.
> The work in AMQP is not under NDA, however IPR rights are only granted
> on each version of the spec as it is published. This is true for just
> about all of the
> standards process, so the group can deal with issues if they want. So I
> don't see that it
> is meaning-full to commit draft work into an OSS project, but it might
> make sense for
> the team at large to see updates that could help out in the project
> knowing how things may
> change.
>
> I see two options:
> a.) The project requests of the Working Group to review drafts
> b.) Apache looks at joining the Working Group.
>
> Both should resolve this issue.

I agree that it could make lots of sense for Apache to join the
Working Group and allow any Apache contributor to have access to the
discussions & working group material - in the same way that Apache is
a member of the JCP and a J2EE iicensee and that Apache committers who
sign the right NDA can get access to and contribute to J2EE
certification efforts etc.

Which brings me on to an important area - certification and TCKs.

If AMQP is really gonna work as an interoperable standard I think its
imperative that there is an open and easy to use TCK for it. Having
struggled with many lousy TCKs in the past that are created behind
closed doors or have wierd or strange licensing policies - it would be
in the AMQP proponents interest to have the AMQP TCK donated to the
Blaze project as well.

The Blaze project has to be able to certify itself against AMQP - not
just write unit tests against its own implementation code; adding this
to the continuous integration builds is a good thing too. So is there
a plan to move the AMQP TCK to Blaze? I'm assuming whenever a
standards body is chosen for AMQP that the AMQP Working Group will
still be able to decide the best home and licensing terms of the TCK
right?
-- 

James
-------
http://radio.weblogs.com/0112098/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message