On Sun, Jan 13, 2013 at 5:34 PM, Craig L Russell <craig.russ...@oracle.com> wrote: > There have been many opinions expressed over the last few years about what > constitutes a "release". At least one opinion was that having the source in > SCM that is freely available constitutes "release" and therefore best > practice is to mark the source directory with the appropriate source LICENSE > and NOTICE. > > Obviously, the LICENSE and NOTICE might be different for binary releases > that include some dependencies that are distributed only with convenience > binary releases. > > But many of the incubator release issues I've seen could have been avoided > simply by including the LICENSE and NOTICE files in the source root, making > it very difficult to release source without these files.
I'm happy to state a best practice here. At the same time, I'd like to establish a firm basis of actual requirements that we can refer to, which I why I opened LEGAL-155. > > Craig > > > On Jan 13, 2013, at 2:14 PM, Benson Margulies wrote: > >> Is it actually required to have these files in SCM in any particular >> location, or just to have a build/packaging process that delivers them >> in the package? >> >> >> On Sun, Jan 13, 2013 at 3:30 PM, Craig L Russell >> <craig.russ...@oracle.com> wrote: >>> >>> We can also add a checklist item to the top level checklists, to be done >>> as >>> part of the source migration: >>> >>> Add LICENSE and NOTICE files to the top level repository directory. [I >>> don't >>> know if there is anything more specific than that, because where a >>> project >>> is using project/trunk, project/site, project/branches style it would go >>> into the project/trunk directory and thence propagated to branches etc.] >>> >>> Craig >>> >>> >>> On Jan 13, 2013, at 7:51 AM, Andy Seaborne wrote: >>> >>>> On 13/01/13 12:45, Benson Margulies wrote: >>>> ... >>>>> >>>>> >>>>> 3. Most of the reviewing in this area is done by sebb. We're lucky to >>>>> have him paying attention to this at all, because it sure seems >>>>> sometimes as if no one else does. >>>>> >>>>> Adding all of this up, I've got a very modest proposal. Let's create a >>>>> checklist, put it prominently at the top of the relevant doc, and then >>>>> see if we can't improve the visibility of this. Sebb, could I ask you >>>>> to dump your checklist into this email thread? >>>> >>>> >>>> >>>> +1 >>>> >>>> We need to clone sebb's reviewing process as good practice and it would >>>> pull together the knowledge about N&L. >>>> >>>> Andy >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>> >>> >>> Craig L Russell >>> Architect, Oracle >>> http://db.apache.org/jdo >>> 408 276-5638 mailto:craig.russ...@oracle.com >>> P.S. A good JDO? O, Gasp! >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > Craig L Russell > Architect, Oracle > http://db.apache.org/jdo > 408 276-5638 mailto:craig.russ...@oracle.com > P.S. A good JDO? O, Gasp! > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
