Cliff,

Thank you very much for talking a look. I was under the impression that you had previously approved our wording. I'll fix LICENSE and NOTICE files and spin a new release ASAP.

- Dave


On Apr 27, 2006, at 6:14 PM, Cliff Schmidt wrote:

-1 until the following is corrected:

I see a couple problems with what I've just downloaded at
http://people.apache.org/~snoopdave/roller-2.2-rc/:

1. There's no NOTICE file.
2. Although there is clear mention of the LGPL components in the
README (which isn't required), I don't see anything in the LICENSE
file (which is required).  There should be either a copy of all
relevant licenses or a pointer to the other relevant licenses in the
LICENSE file.

Please read http://apache.org/dev/apply-license.html#new.

Cliff

On 4/25/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Dave Johnson wrote:
We've gone through 5 release candidates and are ready to release
Roller 2.2-incubating.

next time [we'll] use [the] official [disclaimer] wording.

As per
http://incubator.apache.org/incubation/ Incubation_Policy.html#Branding, you need to either request the PMC to approve your substitute language or just
use the boilerplate we approved for general use.

I do not personally have a problem with your substitute wording:

This release of Roller is not endorsed by the Apache Software Foundation. Roller is in the Apache Incubator and is not an official Apache project.

so for a one-off usage I'll give you my +1, Others may have an issue with
the wording, and vote against the release with that wording.

        --- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to