brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Nalley <>
Subject Re: license headers and config section
Date Sat, 20 Sep 2014 02:14:59 GMT
So in general, citing precedence because a TLP does something won't
help you. TLPs are generally pretty independent, their PMCs get to
make decisions and worst case they have to justify their actions to
the board. Podlings on the other hand, have their releases, especially
their first release, really vetted thoroughly to comply with policy as
its written. In place of a PMC, podlings have the IPMC - which is a
group of 450 people who sit in judgement of your codebase. I don't
mean that to sound harsh, but that's the situation. Demonstrating the
ability to do IP Clearance right is a big deal; and a huge effort. It
can be painful, and annoying; for the first ACS release, we had a
number of config files with no copyright information that we had to
track the original author down for to get an explicit grant; and it
took us weeks to get that sorted to everyone's satisfaction. I said
all of that to say, there are valid reasons to not have a source
header; that $BigTLP does it that way is invariably not one of them.
The Apache brand has a strong reputation for it's clean IP, and decent
record keeping, and some of the rigidity in place is designed to keep
that reputation intact.


On Fri, Sep 19, 2014 at 5:45 AM, Alex Heneveld
<> wrote:
> Mentors,
> I was curious how other projects addressed these problems.  It seems that
> what we are seeking to do has precedents by some of the best-known Apache
> projects.
> Hadoop, for example, excludes the Apache header in HTML *template* files
> [1].
> And Cassandra, for example, excludes the Apache header in YAML files
> intended for end-user consumption (config and examples) [2].
> Hopefully this means we can proceed with this?!
> As penance I have been extra diligent with our NOTICE file.  [4]
> Best
> Alex
> [1]
> [2]
> [3]
> [4]
> On 19/09/2014 09:03, Alex Heneveld wrote:
>> David-  Thanks.
>> Chip, mentors-  Appreciate your thoughts.
>> The issue is that many of the HTML files are templates.  Many are just
>> one-line.  They'll be included hundreds of times, or thousands if it's a big
>> (in-memory) table when pages are rendered.  So it has significant
>> performance and memory impact.
>> It is only those templates which have had the header removed.  All the
>> base HTML files include the header.
>> I don't know if it makes a difference but these template files are not in
>> the distributables directly (wrt the condition that "human readable files in
>> the distribution); they are only inside the WAR inside the distributable and
>> there is already a LICENSE inside the WAR.
>> Given the above would this be alright?  Or if not can you suggest how
>> other projects resolve this?
>> Cheers
>> Alex
>> On 19/09/2014 07:06, David Nalley wrote:
>>> Hi Alex,
>>> So expect this to be challenged when your first release hits the IPMC
>>> (or even when mentors are reviewing code)
>>> Specifically, saving space or bandwidth isn't a good justification for
>>> not having a license header; from a policy perspective. There have
>>> been discussions in the past about using a shorter license header -
>>> but I'd argue that it's probably not in the best interest of folks
>>> trying to get a podlings first release out to engage on that issue.
>>> Chip; or other mentors - anyone feel I am off base here?
>>> --David
>>> On Wed, Sep 17, 2014 at 5:17 AM, Alex Heneveld
>>> <> wrote:
>>>> Hi folks,
>>>> I've prepared a PR #169 which removes the license headers from the YAML
>>>> blueprints, as discussed.  The reason was that these are used as
>>>> examples,
>>>> often cutting and pasting, and having the license really gets in the way
>>>> at
>>>> runtime.  (You can't see the blueprint when you paste the YAML into the
>>>> GUI,
>>>> all you see are the headers!)
>>>> I've also remove it from most of the HTML source pages:  I don't think
>>>> we
>>>> realized the implication of putting them there -- since most of the HTML
>>>> pages are templates, the license header ends up included in the
>>>> resulting
>>>> HTML hundreds of times!  This bloats the pages and slows down
>>>> processing.
>>>> The header is still included in the root index.html which is used for
>>>> every
>>>> page -- so it appears in every page at runtime.  It is also in every CSS
>>>> and
>>>> JS, where the optimizer can remove it so there is no runtime impact.
>>>> I think this is the best compromise but of course if there is guidance
>>>> to
>>>> the contrary we can reconsider.
>>>> I have also moved the config section to the summary tab, to try that
>>>> out.
>>>> [#168]
>>>> Best
>>>> Alex
>>>> [#169]
>>>> [#168]

View raw message