On 9 January 2011 02:33, Karl Wright <daddy...@gmail.com> wrote: > (1) There already is a separate DISCLAIMER.txt. I have attached it > for your consideration.
OK. > (2) As discussed earlier, the LICENSE file already contains sections > for HSQLDB and Jetty; the stuff added to the end of the README came > from NOTICE files in those projects, and is not license material. > (3) I don't know what download tool you have, but if you look in SVN > you will note that there are indeed no blank lines at the start of any > of the files. Sorry, I was looking at the attachments in GoogleMail. Appears to be a bug in the View option, because they are OK when downloaded. > (4) Making yet another ant target will make a very complex build twice > as complex. I don't think that is wise at this point. I don't understand how one extra target can double the complexity. > In short, I don't think there is any point in further changes. I still think the binary archive is unnecessarily bloated, and will cause wasted load and resources for mirrors and consumers. > Thanks, > Karl > > On Sat, Jan 8, 2011 at 8:48 PM, sebb <seb...@gmail.com> wrote: >> On 8 January 2011 16:40, Karl Wright <daddy...@gmail.com> wrote: >>> I've attached a new proposed version of README.txt, NOTICE.TXT, and >>> LICENSE.txt. Any further comments? >> >> As previously mentioned, all the files appear to have leading blank lines. >> These should be removed. >> >> The README file says: >> >> "Apache ManifoldCF is a multi-repository crawler framework, with >> multiple connectors, >> under incubation." >> >> This is insufficient as an incubation disclaimer. >> However I suggest the reference to incubation is removed, and a >> separate DISCLAIMER file created. >> >> See for example: >> http://svn.apache.org/repos/asf/incubator/empire-db/trunk/DISCLAIMER.txt >> >> Also, I think the NOTICEs at the end ot the README belong in the LICENSE >> file. >> >> == >> >> As an entirely separate issue, the README says that the project has to >> be built before use, and explains that one needs to download Java and >> Ant. >> If that is the case, why not include a download section in the build >> file which fetches all the dependencies? >> >> Or at least have an Ant target that copies the jar files to the >> correct directories, and update the binary package to include a single >> copy of each only. >> >>> Karl >>> >>> >>> --------------------------------------------------------------------- >>> 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 >> >> > > > --------------------------------------------------------------------- > 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
