felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francesco Furfari (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-147) Determine how to handle OSGi source and classes for release
Date Tue, 03 Oct 2006 09:07:20 GMT
    [ http://issues.apache.org/jira/browse/FELIX-147?page=comments#action_12439422 ] 
Francesco Furfari commented on FELIX-147:

Hi folks,
I would like to discuss about  the Notice file we shuold include in the release of our sub-projects.
As may you know the UPnP projects are based on a code derived by the Cyberlink library released
under BSD licence. This situation is similar for other projects.

The ASF policy says to add in the Notice file any reference to third-party notices. Moreover
the BSD license says:
# Redistributions of source code must retain the above copyright notice, this list of conditions
and the following disclaimer.
# Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the

So concerning the UPnP stuff I was thinking to a main Notice file like:

           Apache Felix UPnP Base Driver
          Copyright 2006 The Apache Software Foundation

          This product includes software developed at
          The Apache Software Foundation (http://www.apache.org/).

         This software contains code derived from the Cyberlink library
         and licensed under the same license as the original work

I think we should also add  a *Notice-Cyberlink* file repporting the original license.

We didn't discuss yet how all our project will be packaged and released so far, 
here an initial list of questions.

1. should we add the various Notice files in our CVS for each subproject ?
2. should we add the same files in the bundle (as redistribution unit) ?
3. should every subproject  have its own release ? or is better topackage all the related
stuff toghether?

> Determine how to handle OSGi source and classes for release
> -----------------------------------------------------------
>                 Key: FELIX-147
>                 URL: http://issues.apache.org/jira/browse/FELIX-147
>             Project: Felix
>          Issue Type: Task
>            Reporter: Richard S. Hall
>            Priority: Blocker
>             Fix For: 0.8.0
> We need to make sure we understand what we can and cannot do with the OSGi sources and/or
class files. For example, can we include the OSGi source in our release...I assume we can
include the OSGi binaries without any issue. This is a third-party issue, so we need to make
sure that we understand what is necessary with respect to our NOTICE file, etc. Most of this
is discussed in http://www.apache.org/legal/src-headers.html and also in http://people.apache.org/~cliffs/3party.html.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message