RE: License for relaxng.sourceforge.net

[Fabio Arciniegas <faa@speakeasy.org>]

As far as I know (after reading the documentation), the answer is yes, all
components of the project share the same license.; there is no per-item
licensing under a sourceforge project.
The datatype interface and any other software component, including
documentation, will be under MIT if you submit it to the project.

On the other hand, articles are an interesting case, as they may be regarded
as additional material, which is hosted as a courtesy on the site. It may be
possible to host a relevant article with a short clear notice of
non-compliance with the overall license. However, since the topic is not
treated on the SF documentation, I have sent the question to their team. I
will forward the response.

All the best,
	Fabio


> -----Original Message-----
> From: Kohsuke KAWAGUCHI [mailto:kohsuke.kawaguchi@eng.sun.com]
> Sent: Thursday, June 28, 2001 8:08 PM
> To: relax-ng@lists.oasis-open.org
> Subject: License for relaxng.sourceforge.net
>
>
>
> I need the clarification of the license applied to test cases
> contributed to the relaxng project at SourceForge.
>
> Specifically, is it possible for individual contributor to specify its
> own license for their test case/suite? Or do they have to use the MIT
> license?
>
> If I want my "name class cook book" article to be hosted on the relaxng
> SourceForge project, do I have to use the MIT license for that article?
>
> I think we have to be clear about this...
>
>
>
> Also, my understanding is, the datatype interface set will be hosted at
> SourceForge. Are they also covered by the MIT license? (--- which is
> fine for me. Just asking for the clarification)
>
>
>
> regards,
> --
> Kohsuke KAWAGUCHI                          +1 650 786 0721
> Sun Microsystems                   kohsuke.kawaguchi@sun.com
>
>
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: relax-ng-request@lists.oasis-open.org
>