|Ross Gardler||Feb 6, 2012 1:58 am|
|Christian Grobmeier||Feb 6, 2012 2:07 am|
|Ross Gardler||Feb 6, 2012 2:44 am|
|Franklin, Matthew B.||Feb 6, 2012 5:36 am|
|ant elder||Feb 6, 2012 5:44 am|
|ant elder||Feb 6, 2012 6:30 am|
|Jukka Zitting||Feb 6, 2012 6:39 am|
|Ate Douma||Feb 6, 2012 6:56 am|
|sebb||Feb 6, 2012 7:20 am|
|sebb||Feb 6, 2012 8:06 am|
|Ross Gardler||Feb 6, 2012 8:20 am|
|ant elder||Feb 6, 2012 8:29 am|
|sebb||Feb 6, 2012 8:40 am|
|Greg Stein||Feb 6, 2012 9:25 am|
|Ross Gardler||Feb 6, 2012 10:18 am|
|Craig L Russell||Feb 6, 2012 10:30 am|
|Ross Gardler||Feb 6, 2012 11:12 am|
|Ross Gardler||Feb 6, 2012 12:23 pm|
|sebb||Feb 6, 2012 12:33 pm|
|Subject:||RE: Licence headers in template files|
|From:||Franklin, Matthew B. (mfra...@mitre.org)|
|Date:||Feb 6, 2012 5:36:57 am|
I am sure you know this (especially since you first pointed me at this page),
but the release FAQ  makes it sound like you need the header, if you assume
your templates are source:
Which Files Must Contain An ASF License Text? Every source file must contain the appropriate ASF License text.
I am no lawyer, so I will defer to someone who has more experience than me to
help you determine whether your snippets count as source.
Just a thought that might solve your problem in a different way: if you define
some convention in Wookie to denote text to be stripped during processing, you
might find it useful for reasons other than just the license. This could be
especially true if you expect users of the system to be defining their own
templates. You could strip comments, examples, licenses, etc all at once.
A license header question...
There is no significant IP in these templates. they are mostly boilerplates that are intended to be replaced by the end user, but in some cases they will remain. You can see some of them at  (see the content_* files)
To save you looking here is an example of one of them...
Would it be acceptable for these files to *not* have licence headers in them?
-- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com