Hi, Since Marvel requires a license for production usage, does this mean in order to use the Marvel bundled Sense against a production instance requires you to buy a license?
I just got out of a meeting where I told a bunch of people to go download sense off the chrome store. Whoops :) Thanks! Paul On Tuesday, April 1, 2014 12:14:44 PM UTC-4, kimchy wrote: > > Sense started as a weekend project, and Boaz did not place a license on > it. As you mentioned, this license effectively applies: > http://choosealicense.com/no-license/. We consulted our lawyers, who > specialize in open source, and changing the license to open source one is > complex, expensive, and requires a lot of resources. The reason is that its > not only getting the committers agreement, but also reaching all possible > users and have them agree to it (or at least showing big investment in > trying to do so, + a rather large time window to allow for people to > object). > > When Boaz created Sense, he was not employed by Elasticsearch. Obviously > any project started by our employees has a clear license (as you can notice > with the many projects we created). > > Regarding Marvel: > > - You are only required to pay for it when used in production. > - You don’t have to be a support customer of Elasticsearch the company, > you can buy a license for Marvel easily on the web. We made it super cheap > since we think its something that a lot of people will find benefit from. > > On Apr 1, 2014, at 17:00, Ivan Brusic <[email protected] <javascript:>> > wrote: > > I personally do not require an open source license for Marvel/Sense, but I > would like to see an explicit clarification about the use of Marvel in this > scenario. Marvel does require a license to use and that would apply to any > of its subsystems. Then again, Sense does not have a license, which means > its use is also somewhat restricted. > > Sense is an excellent tool and users dependency on the tool is quite > apparent from this thread. :) > > I haven't packaged a Chrome plugin in about 3 years. Not only has my > memory faded, but I would assume the mechanism has changed in our fast > changing world of development. It would be a fun exercise to attempt to do > it again. > > Cheers, > Ivan > > > On Tue, Apr 1, 2014 at 5:48 AM, Tim S <[email protected] <javascript:>>wrote: > >> @kimchy the whole reason for me asking these questions is that sometimes >> a customer is using elasticsearch but they don't (yet) have a support >> contract, but don't consider themselves "in development" either, and thus >> wouldn't allow me to use Marvel. Yes, there are other tools for poking >> around, but sense is invaluable for constructing complicated queries etc >> quickly. In this situation they wouldn't let me install a chrome plugin >> either, but sense works nicely as an elasticsearch plugin too. >> >> So, if sense (the abandoned version on github) had some kind of >> permissive licence, I could turn up on customer site and use sense to poke >> around. >> Ideally, it would have a licence like AL2 which would allow me to modify >> it if necessary. >> >> I realise that you don't want updates pushed back to the version of sense >> on github because those changes are helping you to make money from Marvel, >> I understand that. But if the abandoned version of sense did have an >> appropriate licence, it would allow us to use the current version - it's >> still useful even if it's not kept up to date. I might even be tempted to >> try and keep it up to date in my spare time. But clearly I can't do this >> unless it has a licence that allows me to do it. >> >> Glad to see I'm not the only person thinking along these lines. >> >> >> >> On Tuesday, April 1, 2014 11:15:07 AM UTC+1, Jörg Prante wrote: >>> >>> +1 for Sense standalone packaging >>> +1 for Sense in Chrome Web Store >>> >>> Sense is used here all the time, it's essential. >>> >>> I have also forked the code in case Sense goes away, hoping for a FOSS >>> license. >>> >>> Not that I'm fluid in writing browser plugins, but if I find time, I am >>> not afraid of the learning curve. >>> >>> Jörg >>> >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "elasticsearch" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/837794c8-1a0a-411f-a29c-852133d6fbc2%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/837794c8-1a0a-411f-a29c-852133d6fbc2%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDQQ%2BJRADr%2Bu%3DiqHjs9suKS6Yu8pSc1aKv0JsmavFypoQ%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDQQ%2BJRADr%2Bu%3DiqHjs9suKS6Yu8pSc1aKv0JsmavFypoQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d22cd5e3-9f6f-4142-8021-71b033ac38de%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
