Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7353F97A8 for ; Mon, 23 Apr 2012 21:47:38 +0000 (UTC) Received: (qmail 83399 invoked by uid 500); 23 Apr 2012 21:47:37 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 83320 invoked by uid 500); 23 Apr 2012 21:47:37 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 83312 invoked by uid 99); 23 Apr 2012 21:47:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Apr 2012 21:47:37 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bimargulies@gmail.com designates 209.85.212.182 as permitted sender) Received: from [209.85.212.182] (HELO mail-wi0-f182.google.com) (209.85.212.182) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Apr 2012 21:47:31 +0000 Received: by wibhr14 with SMTP id hr14so12954wib.5 for ; Mon, 23 Apr 2012 14:47:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=mIrqGRS3kg00KDObMP0NcAjGtn0R5MckIDvKKr5kEx0=; b=nVd0qEhws43LUw1mGshB2pPSGA057LWFFP4HnAZnfG/MuN8DSgDwBZm+VvbRpBC2At LG0Wb/muEgqkO+L9VBm00fHPlsqmz7ducH8wlN6itOK0TsaFLMKCi+8RvTO1lPm8Lm99 cCDRLU/ZtdyP9nbC49FTKx/SdX57YeAgXFfaiZaBSwJinzitX2XNC4dHxmsK/bm7dASp /v/XRHa6Gxo9LcLrdiQyrD5NJlM9DwzbQ+JsxZlJ3HOMWAgd6B6iCwVmth3yVQ1SaUuP jgBBKX7v8es/LMbNm9vcb53tayFcSqDQIR7rCVNVDvgmUWvpY6rRS9jtRjvW54GpcNHb P80Q== MIME-Version: 1.0 Received: by 10.180.102.129 with SMTP id fo1mr16836494wib.6.1335217629743; Mon, 23 Apr 2012 14:47:09 -0700 (PDT) Received: by 10.180.96.33 with HTTP; Mon, 23 Apr 2012 14:47:09 -0700 (PDT) In-Reply-To: References: <008801cd2195$5daf5db0$190e1910$@thetaphi.de> <6C78E97C707B5B4C8CC61D44F87545861DD6BF@SUEX10-mbx-03.ad.syr.edu> <008c01cd2198$23677220$6a365660$@thetaphi.de> Date: Mon, 23 Apr 2012 17:47:09 -0400 Message-ID: Subject: Re: [DISCUSS] Build/deploy Maven artifacts outside of Lucene/Solr From: Benson Margulies To: dev@lucene.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Rob, I personally think that the Apache policy issues here are not entirely worked out, but let me try to summarize the situation. Starting condition: a marooned bugfix or feature in some other Apache TLP. 1. Communicate with the other TLP, possibly siccing Uwe on their chair. 2. If they are unresponsive or unhelpful, I think that further discussion with the board would be apropos. However, 3. Make a choice between three alternatives: a) Fork their source under your svn, rename packages, and go for it. Include that source in your source release. b) Create a patching process that grabs their release package, fixes it, and builds it, renaming packages. Include the patching process in your source release. c) A volunteer goes off to github and does the necessary, with this being that volunteer's individual effort, not an 'action of the PMC'. In this case, you can hypothetically leave the package names alone, but, in this case you are walking on a somewhat fine line. In this case, you use it as a binary dependency. Does this help? I think that more discussion with the board would be helpful on all of this, and I'd encourage your chair to do so. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org