Thanks for the explanations Uwe. I am talking about the final binary release package. Not the source.
My current focus is Solr onboarding experience from the eyes of a first-time user. Ideally, there is a super-duper-happy-path (SDHP) for them to follow from the moment of download to the first example to the first non-example. I just did a download of Elastic Search (which people report having happier first time experience with). So, I am sort of evaluating it side-by-side in terms of experience. The difference in philosophy is quite interesting. ElasticSearch out of the box is much smaller, does not include offline documentation or examples and downloads additional functionality (including Admin UI and Tika components) post deploy as plugins. Solr, on the other hand, is a kitchen sync with some extra bits thrown for free (hadoop :-) I don't have a particular problem with either philosophy. But, as a side-effect, it reduces the SDHP through increased confusion and - in this case - too many files in various directories. So, I imagine that having a zip of licences under documentation folder or some other non-prime location might decrease that confusion a little bit. And, of course, this is not a Solr 4.8 blocker of any kind. I just wanted to know what the requirements actually were at this point. And whether it is worth a Jira, if it is possible at all. Regards, Alex. Personal website: http://www.outerthoughts.com/ Current project: http://www.solr-start.com/ - Accelerating your Solr proficiency On Wed, Apr 16, 2014 at 7:19 PM, Uwe Schindler <[email protected]> wrote: > Hi, > > It is not an issue for ElasticSearch at all. The regulations for releases > within the Apache Software Foundation require special care about used > licenses. Important are proprietary JARs using Sun CDDL licenses. > Where is the issue for you? If you don't care about the licensed, delete the > folder. There is no difference in deleting the ZIP file. > > The folder with the licenses is checked and maintained by lots of build > scripts and checking tasks to make sure the release is according to legal > requirements and the JAR files shipped with the tgz are identical to Maven > Central ones. We could ZIP it up for the binary ZIP file, but not for the > source.tgz release. This is not a blocker issue for Lucene/Solr 4.8 and > requires careful handwork. > > Uwe > > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: [email protected] > > >> -----Original Message----- >> From: Alexandre Rafalovitch [mailto:[email protected]] >> Sent: Wednesday, April 16, 2014 2:08 PM >> To: [email protected] >> Subject: Re: Why does Solr bundle all the licences >> >> Even with ES uses the same ASF jars, it's not an issue for them? >> >> What about zipping them all up? Would that violate the rules? >> >> Regards, >> Alex. >> Personal website: http://www.outerthoughts.com/ Current project: >> http://www.solr-start.com/ - Accelerating your Solr proficiency >> >> >> On Wed, Apr 16, 2014 at 7:05 PM, Uwe Schindler <[email protected]> wrote: >> > Hi, >> > >> > This is required by the ASF. The same goes for the NOTICE.txt file, which >> > is >> a requirement for every release. ElasticSearch is not ASF software, so it >> does >> not apply there. >> > >> > Uwe >> > >> > ----- >> > Uwe Schindler >> > H.-H.-Meier-Allee 63, D-28213 Bremen >> > http://www.thetaphi.de >> > eMail: [email protected] >> > >> > >> >> -----Original Message----- >> >> From: Alexandre Rafalovitch [mailto:[email protected]] >> >> Sent: Wednesday, April 16, 2014 1:57 PM >> >> To: [email protected] >> >> Subject: Why does Solr bundle all the licences >> >> >> >> Hello, >> >> >> >> I am curious what the legal reason for bundling all the .sha and >> >> license files (plus the NOTICE.txt plus the LICENSE.txt)? I am >> >> looking at ElasticSearch by comparison and they have only one. >> >> >> >> Even when they download something like Tika as a plugin, they do not >> >> seem download the license files. >> >> >> >> Are they out of compliance or is Solr going beyond and above >> >> requirement for some reason. >> >> >> >> And, if we do have to have it, would it still be compliant to ship it >> >> as a licences.zip directory (say under docs), as vast majority of the >> >> people will never need to actually extract individual files and it >> >> saves the on-disk representation. >> >> >> >> Regards, >> >> Alex. >> >> P.s. I need a common tag for my latest bunch of emails. #onboarding? >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
