On 4/26/06, Leo Simons <[EMAIL PROTECTED]> wrote: > > On Fri, Apr 21, 2006 at 09:40:34AM -0600, Bruce Snyder wrote: > > On 4/21/06, Rodent of Unusual Size <[EMAIL PROTECTED]> wrote: > > > Leo Simons wrote: > > > > *sigh*. I feel like a broken record these days. > > > > > > > > Nowhere does any policy ever say "you can do stuff which is not > permitted by > > > > law or for which you have no license". To state the reverse in a > policy would > > > > be rather, well, redundant. There is ample documentation out there > on our > > > > websites (and more in the works) to help with complying with the law > and various > > > > licenses. > > > > > > No, but the legal aspect isn't necessarily the concept > > > looming largest in a developer's mind. So a simple checkbox > > > on the page (I'll do it myself in a few minutes, if I figure > > > out how to frob the site) to the effect of: 'Have the > > > licences of any/all bundled code been identified and noted > > > in the release? Has a NOTICE file been included that > > > summarises them and their requirements where they differ > > > from the Apache licence's? Have their requirements been > > > met?' would, IMHO, be a goodness. > > > > Bingo! Ken hit the nail on the head!!! A checklist would do wonders > > for podlings and preparing releases. > > Okidoki. But checklists are scary, since they could provide a false sense > of > security and have a tendency not to be updated or kept (keeping the status > files > for podlings up-to-date seems very hard).
+1 Note it should not be for podlings, it should be for all of the ASF. Cliff > has been working on lots of this kind of stuff > i've not created an ASF wide checklist since i believe that it would be risky: release managers really need to understand the issues rather than just tick boxes. IMO checklists work best at project level and contain a description of what each project expects and how their release process works. podlings really need to develop their own release policy and document it. creating an ASF guide aimed at new release managers might be a good idea, though. i had a think about this and i have come up with something that i do think would work: a index-style (with links into the ASF documentation) summary for the incubator project plus guides to best practice (which would include language specific material excluded from the ASF documentation). if there are no objections or ideas for improvement, i might start looking at some of this in the next week or two. - robert
