Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 76807431FB6 for ; Sat, 2 Jun 2012 22:35:09 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NevWY6t9sZDF for ; Sat, 2 Jun 2012 22:35:08 -0700 (PDT) Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 2724E431FAF for ; Sat, 2 Jun 2012 22:35:07 -0700 (PDT) Received: by lbbgk8 with SMTP id gk8so2768235lbb.26 for ; Sat, 02 Jun 2012 22:35:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=vi5bgmYnojgV5DieDtCFBWexYwNrzCtCVPSrNlAdyvw=; b=NgCzpbVu2mH5vuGnl/JpyaphJ7hukkhaEBbeUm41gQceaXXtzTQZODWccBNyf/5ZoB JkF1vft6dQk5sb4yUwxfwX/wavaIv2zRJjapHWyJ0F2TPQ1u5CEWpurQJjqaw8vd6MOH nxowcRT8ghBiqJEgSHaIOc2sINaoEcnGoztBtacDIHn65MqZVgVj+vHBEfFUgTwDXyFV 4eV6qkC1l5q8A7bL9x+/2C6rc9kaG+8zwdIDKah0wXfal94r1gnzQdTDf/ASx+QV/07h 6quu8dzceem4ryYsWVa2aW99disdLW1iD8rmS/HwNznzTGgFqYSafCcWHLS+SOEaK+Lb /HhQ== MIME-Version: 1.0 Received: by 10.152.106.12 with SMTP id gq12mr403985lab.17.1338701705060; Sat, 02 Jun 2012 22:35:05 -0700 (PDT) Sender: awg@xvx.ca Received: by 10.112.88.99 with HTTP; Sat, 2 Jun 2012 22:35:04 -0700 (PDT) X-Originating-IP: [136.159.108.48] In-Reply-To: <87sjefufub.fsf@servo.finestructure.net> References: <20120531214259.GA18272@desktop> <87lik7171d.fsf@zancas.localnet> <87sjefufub.fsf@servo.finestructure.net> Date: Sat, 2 Jun 2012 23:35:04 -0600 X-Google-Sender-Auth: _wSjZAtPzR7WlpBp29YgOcI32G0 Message-ID: Subject: Re: Can't compile notmuch-delivery From: Adam Wolfe Gordon To: Jameson Graef Rollins Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQmaH8e1JLP202NG1S0HTwAyZsO+WJro7lG1p+YWKDIuZqqQwPrX3uHxXpAReOM5GGeEaPDR Cc: Tomi Ollila , notmuch@notmuchmail.org, Ali Polatel X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2012 05:35:09 -0000 On Fri, Jun 1, 2012 at 11:01 AM, Jameson Graef Rollins wrote: > On Fri, Jun 01 2012, David Bremner wrote: >> I guess we should clarify what it means to accept some code into >> contrib. Do we accept to maintain it even after the original contributor >> loses interest? > > I don't know, but this is one of the reasons I'm against having > "contrib" stuff in the notmuch repo. =A0If it's not part of the stuff > we're willing to release in source tarballs or binary packages then it > should probably be in a separate repo. +1. I think having the bindings in the tree and including them in build system is reasonable, since they're interfaces into the core of the notmuch library. We should be careful of what bindings we accept in to the tree (I don't want to fix Fortran bindings ;-) ), but the small set we have seems maintainable. It's harder to make a case for contrib. Keeping stuff that relies on notmuch up-to-date is a nice idea, but doing so creates more work for developers working on the library and core, since they have to fix a bunch of code they're not that familiar with. Things that are actively used (e.g. alot) will be updated quickly anyway since their developers will tend to keep up with what notmuch is doing. -- Adam