Andrus Adamchik wrote:
> Jean, as usual, thanks for providing the useful info.
>
> My take on it - this is yet another insanity coming from the world
> ruled by lawyers, and we have no choice, but comply. As far as the
> exported wiki-docs, I guess we'll have to augment the ant script with
> the header addition step. We can do the same thing for the generated
> test classes (generate with standard template, and then postprocess
> with Ant to add a header). Maven migration is going to be fun...
Are the wiki-docs included in the product distribution? If so, then
they definitely need the header.
If they're only displayed on the web site, then
http://www.apache.org/legal/src-headers.html says content displayed on a
web site doesn't need it. (But if that web site gets included in the
product distribution it does need the header.)
Here's what does NOT need the header:
http://www.apache.org/legal/src-headers.html#faq-exceptions
When in doubt, add the header.
-jean
> Andrus
>
>
> On Jul 18, 2006, at 2:13 PM, Jean T. Anderson wrote:
>
>> Gentry, Michael (Contractor) wrote:
>>
>>> I think I'm going to make the strategic decision, for now, that
>>> XML/DTD/etc is data and not code and doesn't need the ASF header.
>>> Jean/etc can chime in on this later if they want.
>>
>>
>> I haven't read this thread very carefully this morning :-) but
>> documentation source needs the header, and the policy does apply to
>> documentation files included in a release according to
>> http://www.apache.org/legal/src-headers.html . For example, for derby,
>> this means the dita xml source for documentation needs the header, as do
>> the html files generated from that xml source.
>>
>> Picture it this way: if somebody wants to reuse a particular file, we
>> want the license governing use/reuse of that file to be clear.
>>
>> helpful context:
>>
>> http://tinyurl.com/m7jrq
>> http://tinyurl.com/mkc3c
>>
>> -jean
>>
>>
>>> Also, I'm not going to add headers to the generated classes, such as
>>> _Artist.java and Artist.java, since these are produced from a template
>>> and we don't want the standard templates to have the ASF headers in
>>> them.
>>>
>>> It looks like many test classes don't have headers, either, but I'll
>>> add
>>> it to them.
>>>
>>> Thanks,
>>>
>>> /dev/mrg
>>>
>>>
>>> -----Original Message-----
>>> From: Andrus Adamchik [mailto:andru..bjectstyle.org]
>>> Sent: Tuesday, July 18, 2006 11:09 AM
>>> To: cayenne-de..ncubator.apache.org
>>> Subject: Re: NOTICE Text
>>>
>>>
>>>
>>> On Jul 18, 2006, at 11:04 AM, Gentry, Michael ((Contractor)) wrote:
>>>
>>>
>>>> Ooops, misread what you said originally. Thanks.
>>>>
>>>> I'm adding the ASF license to a few files which were missing the OS
>>>> one,
>>>> but everything else is looking good so far. Do you think
>>>> org/apache/cayenne/dba/types.xml (and kin) need it, too? My gut
>>>> feeling
>>>> is no.
>>>
>>>
>>>
>>> I don't know. I guess we can add the header as XML comment. Probably
>>> wouldn't hurt.
>>>
>>>
>>>> What about HTML files? I'm guessing no on that one, too. At
>>>> least for now ...
>>>
>>>
>>>
>>> At least not in cayenne-other/wiki-docs, as those are generated.
>>>
>>> Andrus
>>
>>
>>
>
This archive was generated by hypermail 2.0.0 : Tue Jul 18 2006 - 14:37:16 EDT