similar to: GPL as the main reason why Xapian might not get the widespread success it deserves?

Displaying 20 results from an estimated 1000 matches similar to: "GPL as the main reason why Xapian might not get the widespread success it deserves?"

2018 Aug 29
2
Compatibility of GPL 2.0 licensed SSL library
Hi all, I'm wondering if the GPL-2.0 licensed mbedTLS (that's the version in OpenWrt) is 'compatible' with NUT binaries (not including the Python or Perl binaries which aren't used in OpenWrt) which is GPL 2.1+ AIUI. Because mbedTLS is the default library for OpenWrt and NSS is not yet in OpenWrt, and because OpenSSL is considered incompatible (I seem to recall reading that
2015 Apr 27
4
Real sh? Or other efficient shell for non-interactive scripts
Les Mikesell <lesmikesell at gmail.com> wrote: > On Mon, Apr 27, 2015 at 1:46 PM, Always Learning <centos at u64.u22.net> wrote: > > > >> Yes, in english, 'work as a whole' does mean complete. And the normal > >> interpretation is that it covers everything linked into the same > >> process at runtime unless there is an alternate
2016 Jan 07
2
LGPL relicense port of rsync
Hi, I am maintaining a port of rsync (https://github.com/perlundq/yajsync) which is GPL:ed of course. The main purpose of the project is to provide a Java API library for the rsync protocol. It would therefore be really nice to be able to use LGPL as the license. But in order to do so I would first have to get a list of all the individual contributors to rsync and then be able to contact them
2013 Sep 06
4
About de Bruijn sequences in bitmath.h
Found this code: ftp://ftp.samba.org/pub/unpacked/ntdb/lib/ccan/ilog/ilog.c Tests show that it's faster to use the following code in FLAC__bitmath_ilog2_wide(): static const unsigned char DEBRUIJN_IDX32[32]={ 0, 1,28, 2,29,14,24, 3,30,22,20,15,25,17, 4, 8, 31,27,13,23,21,19,16, 7,26,12,18, 6,11, 5,10, 9 }; FLAC__uint32 v; int m;
2017 Aug 10
5
Relicensing: Revised Developer Policy
On Aug 10, 2017, at 3:08 PM, Rafael Avila de Espindola via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Chris Lattner <clattner at llvm.org> writes: > >>> On Aug 10, 2017, at 2:59 PM, Rafael Avila de Espindola <rafael.espindola at gmail.com> wrote: >>> >>> I can find old threads about it, but nothing saying why it was decided >>> that
2015 Oct 21
3
RFC: Improving license & patent issues in the LLVM community
On Oct 19, 2015, at 10:53 AM, Joerg Sonnenberger <joerg at britannica.bec.de> wrote: >>>> 2) We could require new contributors to sign the Apache CLA. >>> >>> To me, this is the most acceptable option of the listed terms. >> >> Please explain: why? > > First part for me is that switching the code to a different license > doesn't
2017 Sep 13
2
[RFC] Polly Status and Integration
On Wed, Sep 13, 2017 at 7:43 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > On 09/13/2017 02:16 AM, C Bergström wrote: > > A completely non-technical point, but what's the current "polly" license? > Does integrating that code conflict in any way with the work being done to > relicense llvm? > > > Good question. I discussed this explicitly with
2017 Aug 10
3
Relicensing: Revised Developer Policy
> On Aug 10, 2017, at 2:59 PM, Rafael Avila de Espindola <rafael.espindola at gmail.com> wrote: > > I can find old threads about it, but nothing saying why it was decided > that contributor agreement wouldn't work. Care to send the URL? Here are some quick points that come to mind: 1. It raises the bar to contribution, because something must be “signed” before a
2015 Oct 19
3
RFC: Improving license & patent issues in the LLVM community
I really really do not like armchair lawyer discussions and this is just flamebait if I've ever seen it... --------------- #1 Is the submarine patent risk really that bad? (What's driving this) #2 Pragmatically have "you" even considered how to execute on this relicense plan? a. What if one of the copyright holders doesn't agree? b. What audit procedure do you plan to use c.
2016 Jan 09
3
LGPL relicense port of rsync
... > Getting the approval for a relicensing I think the contributions to > rsync have to be analyzed in detail to approach a reasonable number of > contributors. > > I experienced that finding a responsible person that is willing to > discuss such a case in an organization that contributed source code is > nearly impossible. > > Looking at the source code (my short
2012 Apr 09
2
[LLVMdev] RFC: R600, a new backend for AMD GPUs
On Mon, Apr 09, 2012 at 09:37:37AM -0400, Tom Stellard wrote: > On Mon, Mar 26, 2012 at 12:50:07PM -0400, Tom Stellard wrote: > > Hi, > > > > We've been working on an LLVM backend for the previous generation of AMD > > GPUs (HD 2XXX - HD 6XXX) and we would like submit it for inclusion in the > > main LLVM tree. The latest code can be found in this git
2015 Oct 19
18
RFC: Improving license & patent issues in the LLVM community
Hi Everyone, I’d like to start a discussion about how to improve some important issues we have in the LLVM community, regarding our license and patent policy. Before we get started, I’d like to emphasize that *this is an RFC*, intended for discussion. There is no time pressure to do something fast here -- we want to do the right long-term thing for the community (though we also don’t want
2006 Aug 23
11
i18n friendly, plugable Rails Core
In my work with a simple localization plugin, i''m running into a lot of places in the Rails core, where text and other localization specific information is hardcoded. I''ve included some examples in the bottom of this post. It''s hard for an outsider to know, if the hardcoded values are a result of inconsistency in code, or "by design". I hope that we can have
2013 Aug 28
6
Request to relicense hash gnulib module to LGPLv2+
libguestfs (an LGPLv2+ library) uses the 'hash' module, which turns out to be "GPL". Actually this happened because we started to use it in a separate GPL'd utility program, but later on included this functionality in the core library, copying the same code from the utility but not checking the license of 'hash'. We'd therefore like to request that
2015 Oct 19
2
RFC: Improving license & patent issues in the LLVM community
> On Oct 19, 2015, at 9:27 AM, Joerg Sonnenberger via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Mon, Oct 19, 2015 at 08:25:16AM -0700, Chris Lattner via llvm-dev wrote: >> 1) We could introduce a novel legal solution. > > Please, no. > >> 2) We could require new contributors to sign the Apache CLA. > > To me, this is the most acceptable
2015 Oct 21
2
RFC: Improving license & patent issues in the LLVM community
On Wed, Oct 21, 2015 at 5:16 AM, Joerg Sonnenberger via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Tue, Oct 20, 2015 at 09:54:30PM -0700, Chris Lattner wrote: >> On Oct 19, 2015, at 10:53 AM, Joerg Sonnenberger <joerg at britannica.bec.de> wrote: >> >>>> 2) We could require new contributors to sign the Apache CLA. >> >>> >>
2019 Jul 26
3
Revisiting the PHP binding license issues
Hello, I would like to see Xapian used more widely in the PHP community. The major obstacle is that binaries of the PHP extension cannot be distributed. I've been reading earlier discussions on this and wonder if there's now an option. My starting points were https://trac.xapian.org/wiki/FAQ/PHP%20Bindings%20Package and the discussion at https://trac.xapian.org/ticket/191. One comment
2007 Apr 02
1
Kernel timer frequency and HTB
Hello, i have a linux box which is acting as a lan router towards the internet doing traffic shaping. My link is 10Mbit/s full duplex. I have set some HTB classes with a rate of 20% (2Mbit/s) and a ceil of 95% (9.5Mbit/s). Is such an excursion of bandwidth in the HTB classes feasible for HTB to control? What Timer frequency (kernel menuconfig) is the most suitable among 250, 300 and 1000Hz
2014 Nov 19
14
[LLVMdev] Proposal: add Go frontend subproject based on llgo
Hi all, I'd like to propose the contribution of a Go frontend subproject to the LLVM project, based on the existing llgo project at https://github.com/go-llvm/llgo . As with the previous contribution of the Go bindings, I have obtained permission from all llgo contributors whose code is part of this contribution, to contribute their changes to the LLVM project and relicense their changes
2012 Mar 26
6
[LLVMdev] RFC: R600, a new backend for AMD GPUs
Hi, We've been working on an LLVM backend for the previous generation of AMD GPUs (HD 2XXX - HD 6XXX) and we would like submit it for inclusion in the main LLVM tree. The latest code can be found in this git repository: http://cgit.freedesktop.org/~tstellar/llvm/ in the r600-initial-review branch or if you prefer you can download the entire tree with this link: