You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Justin Edelson <ju...@justinedelson.com> on 2010/06/09 20:05:07 UTC
Fwd: NOTICE/DEPENDENCIES files for Felix subproject releases
Should we follow Felix's lead here?
---------- Forwarded message ----------
From: Richard S. Hall <he...@ungoverned.org>
Date: Wed, Jun 9, 2010 at 1:55 PM
Subject: NOTICE/DEPENDENCIES files for Felix subproject releases
To: dev <de...@felix.apache.org>
With the latest release of the framework and Gogo modules, we've tried to
update the release process for how we handle the NOTICE file. Our past usage
is apparently not aligned with the intended usage, where the NOTICE file
should only contained notices for included third-party software whose
license requires notice. Our new approach (for now) is this:
1. Include a NOTICE file which contains only required notices.
2. Include a DEPENDENCIES file which contains our acknowledgments
about the software the subproject uses.
For the most part, this isn't a major hassle and largely boils down to this:
1. Rename the current NOTICE file to DEPENDENCIES.
2. Create a new NOTICE file that contains notices only for the "used"
software requiring notices in the DEPENDENCIES file.
Although the new DEPENDENCIES file is very similar to the old NOTICE file,
the template is slightly different as indicated here:
https://cwiki.apache.org/confluence/display/FELIX/DEPENDENCIES+file+template+%28PROPOSED%29
Of course, in the long term we can try to move to automating the generation
of the NOTICE and/or DEPENDENCIES files, which would make our lives simpler.
If any subprojects currently are able to automate this information, as long
as the generated files contain information consistent with what is proposed
here, then the exact formatting is not that important. But for hand
generated files, follow this template.
If you want to see examples, look in the framework or gogo subprojects.
-> richard
p.s. This is obviously all open for discussion to the specifics, but until
then we should use this approach for releases in an effort to better align
with Apache process (with perhaps the exception of Karaf since if/when it
goes TLP then its PMC will decide how to do releases).
Re: Fwd: NOTICE/DEPENDENCIES files for Felix subproject releases
Posted by Karl Pauls <ka...@gmail.com>.
On Thu, Jun 10, 2010 at 4:52 AM, Justin Edelson
<ju...@justinedelson.com> wrote:
> On Wed, Jun 9, 2010 at 2:55 PM, Felix Meschberger <fm...@gmail.com>wrote:
>
>> Hi,
>>
>> On 09.06.2010 20:05, Justin Edelson wrote:
>> > Should we follow Felix's lead here?
>>
>> I don't think so.
>>
>> In Sling we are using the remote resources plugin which manages this all
>> an an ASF compliant way for us. Exceptions (where LICENSE data is not
>> available from the Maven repository) can still be entered manually.
>>
>> As a consequence we already have the correct NOTICE, LICENSE, and
>> DEPENDENCIES files.
>>
> Richard seems to suggest that this automated method isn't good enough. But
> if you think it is, then I'm fine with it.
Iirc, we have some cases in Felix where it is not picking things up
due to the complicated way the artifacts are assembled. AFAIK, we
don't have such cases in sling so we should be fine.
regards,
Karl
> Justin
>
>
>>
>> Regards
>> Felix
>>
>> >
>> > ---------- Forwarded message ----------
>> > From: Richard S. Hall <he...@ungoverned.org>
>> > Date: Wed, Jun 9, 2010 at 1:55 PM
>> > Subject: NOTICE/DEPENDENCIES files for Felix subproject releases
>> > To: dev <de...@felix.apache.org>
>> >
>> >
>> > With the latest release of the framework and Gogo modules, we've tried to
>> > update the release process for how we handle the NOTICE file. Our past
>> usage
>> > is apparently not aligned with the intended usage, where the NOTICE file
>> > should only contained notices for included third-party software whose
>> > license requires notice. Our new approach (for now) is this:
>> >
>> > 1. Include a NOTICE file which contains only required notices.
>> > 2. Include a DEPENDENCIES file which contains our acknowledgments
>> > about the software the subproject uses.
>> >
>> > For the most part, this isn't a major hassle and largely boils down to
>> this:
>> >
>> > 1. Rename the current NOTICE file to DEPENDENCIES.
>> > 2. Create a new NOTICE file that contains notices only for the "used"
>> > software requiring notices in the DEPENDENCIES file.
>> >
>> > Although the new DEPENDENCIES file is very similar to the old NOTICE
>> file,
>> > the template is slightly different as indicated here:
>> >
>> >
>> >
>> https://cwiki.apache.org/confluence/display/FELIX/DEPENDENCIES+file+template+%28PROPOSED%29
>> >
>> > Of course, in the long term we can try to move to automating the
>> generation
>> > of the NOTICE and/or DEPENDENCIES files, which would make our lives
>> simpler.
>> > If any subprojects currently are able to automate this information, as
>> long
>> > as the generated files contain information consistent with what is
>> proposed
>> > here, then the exact formatting is not that important. But for hand
>> > generated files, follow this template.
>> >
>> > If you want to see examples, look in the framework or gogo subprojects.
>> >
>> > -> richard
>> >
>> > p.s. This is obviously all open for discussion to the specifics, but
>> until
>> > then we should use this approach for releases in an effort to better
>> align
>> > with Apache process (with perhaps the exception of Karaf since if/when it
>> > goes TLP then its PMC will decide how to do releases).
>> >
>>
>
--
Karl Pauls
karlpauls@gmail.com
Re: Fwd: NOTICE/DEPENDENCIES files for Felix subproject releases
Posted by Justin Edelson <ju...@justinedelson.com>.
On Wed, Jun 9, 2010 at 2:55 PM, Felix Meschberger <fm...@gmail.com>wrote:
> Hi,
>
> On 09.06.2010 20:05, Justin Edelson wrote:
> > Should we follow Felix's lead here?
>
> I don't think so.
>
> In Sling we are using the remote resources plugin which manages this all
> an an ASF compliant way for us. Exceptions (where LICENSE data is not
> available from the Maven repository) can still be entered manually.
>
> As a consequence we already have the correct NOTICE, LICENSE, and
> DEPENDENCIES files.
>
Richard seems to suggest that this automated method isn't good enough. But
if you think it is, then I'm fine with it.
Justin
>
> Regards
> Felix
>
> >
> > ---------- Forwarded message ----------
> > From: Richard S. Hall <he...@ungoverned.org>
> > Date: Wed, Jun 9, 2010 at 1:55 PM
> > Subject: NOTICE/DEPENDENCIES files for Felix subproject releases
> > To: dev <de...@felix.apache.org>
> >
> >
> > With the latest release of the framework and Gogo modules, we've tried to
> > update the release process for how we handle the NOTICE file. Our past
> usage
> > is apparently not aligned with the intended usage, where the NOTICE file
> > should only contained notices for included third-party software whose
> > license requires notice. Our new approach (for now) is this:
> >
> > 1. Include a NOTICE file which contains only required notices.
> > 2. Include a DEPENDENCIES file which contains our acknowledgments
> > about the software the subproject uses.
> >
> > For the most part, this isn't a major hassle and largely boils down to
> this:
> >
> > 1. Rename the current NOTICE file to DEPENDENCIES.
> > 2. Create a new NOTICE file that contains notices only for the "used"
> > software requiring notices in the DEPENDENCIES file.
> >
> > Although the new DEPENDENCIES file is very similar to the old NOTICE
> file,
> > the template is slightly different as indicated here:
> >
> >
> >
> https://cwiki.apache.org/confluence/display/FELIX/DEPENDENCIES+file+template+%28PROPOSED%29
> >
> > Of course, in the long term we can try to move to automating the
> generation
> > of the NOTICE and/or DEPENDENCIES files, which would make our lives
> simpler.
> > If any subprojects currently are able to automate this information, as
> long
> > as the generated files contain information consistent with what is
> proposed
> > here, then the exact formatting is not that important. But for hand
> > generated files, follow this template.
> >
> > If you want to see examples, look in the framework or gogo subprojects.
> >
> > -> richard
> >
> > p.s. This is obviously all open for discussion to the specifics, but
> until
> > then we should use this approach for releases in an effort to better
> align
> > with Apache process (with perhaps the exception of Karaf since if/when it
> > goes TLP then its PMC will decide how to do releases).
> >
>
Re: Fwd: NOTICE/DEPENDENCIES files for Felix subproject releases
Posted by Felix Meschberger <fm...@gmail.com>.
Hi,
On 09.06.2010 20:05, Justin Edelson wrote:
> Should we follow Felix's lead here?
I don't think so.
In Sling we are using the remote resources plugin which manages this all
an an ASF compliant way for us. Exceptions (where LICENSE data is not
available from the Maven repository) can still be entered manually.
As a consequence we already have the correct NOTICE, LICENSE, and
DEPENDENCIES files.
Regards
Felix
>
> ---------- Forwarded message ----------
> From: Richard S. Hall <he...@ungoverned.org>
> Date: Wed, Jun 9, 2010 at 1:55 PM
> Subject: NOTICE/DEPENDENCIES files for Felix subproject releases
> To: dev <de...@felix.apache.org>
>
>
> With the latest release of the framework and Gogo modules, we've tried to
> update the release process for how we handle the NOTICE file. Our past usage
> is apparently not aligned with the intended usage, where the NOTICE file
> should only contained notices for included third-party software whose
> license requires notice. Our new approach (for now) is this:
>
> 1. Include a NOTICE file which contains only required notices.
> 2. Include a DEPENDENCIES file which contains our acknowledgments
> about the software the subproject uses.
>
> For the most part, this isn't a major hassle and largely boils down to this:
>
> 1. Rename the current NOTICE file to DEPENDENCIES.
> 2. Create a new NOTICE file that contains notices only for the "used"
> software requiring notices in the DEPENDENCIES file.
>
> Although the new DEPENDENCIES file is very similar to the old NOTICE file,
> the template is slightly different as indicated here:
>
>
> https://cwiki.apache.org/confluence/display/FELIX/DEPENDENCIES+file+template+%28PROPOSED%29
>
> Of course, in the long term we can try to move to automating the generation
> of the NOTICE and/or DEPENDENCIES files, which would make our lives simpler.
> If any subprojects currently are able to automate this information, as long
> as the generated files contain information consistent with what is proposed
> here, then the exact formatting is not that important. But for hand
> generated files, follow this template.
>
> If you want to see examples, look in the framework or gogo subprojects.
>
> -> richard
>
> p.s. This is obviously all open for discussion to the specifics, but until
> then we should use this approach for releases in an effort to better align
> with Apache process (with perhaps the exception of Karaf since if/when it
> goes TLP then its PMC will decide how to do releases).
>