On 12 June 2015 at 19:28, Andy Seaborne <[email protected]> wrote: > It's important NOTICE be minimal. LICENSE can contain more material. > Nowadays, "include the license" (in LICENSE) can be done with links.
Agreed on this approach - it reduces the viral effect of NOTICE. I might have time to change this until next week. > Like some of the N&L generators, they do simpel cases but for anythign else, > it'll need proper files. Probably if you put a DISCLAIMER into git, it'll > use that. >> DEPENDENCIES is also auto-generated by apache-jar-resource-bundle. You are right - that overrides it. >>> Release candidates are signed with a GPG key available at: >>> >>> https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS > I really wish I had time to make a technical contribution to Taverna but > that's unlikely. Please remove my key. The KEYS was generated from https://people.apache.org/keys/group/taverna.asc which seems to include you. http://taverna.staging.apache.org/community/releasing#gpg-keys I was hoping for not yet another thing to maintain manually.. Also https://www.apache.org/dev/release.html#what-must-every-release-contain says: > Folks who vote +1 for release may offer their own cryptographic signature to > be concatenated with the detached signature file (at the Release Manager's > discretion) prior to release. so a mentor who signs +1 could add his signature. I haven't seen this used in practice, though. -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718
