From dev-return-22820-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Sun Aug 5 15:43:44 2012 Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-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 9B226979A for ; Sun, 5 Aug 2012 15:43:44 +0000 (UTC) Received: (qmail 31197 invoked by uid 500); 5 Aug 2012 15:43:43 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 31161 invoked by uid 500); 5 Aug 2012 15:43:43 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 31151 invoked by uid 99); 5 Aug 2012 15:43:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Aug 2012 15:43:43 +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 (nike.apache.org: domain of robert.newson@gmail.com designates 209.85.160.180 as permitted sender) Received: from [209.85.160.180] (HELO mail-gh0-f180.google.com) (209.85.160.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Aug 2012 15:43:37 +0000 Received: by ghbg10 with SMTP id g10so148646ghb.11 for ; Sun, 05 Aug 2012 08:43:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :content-type; bh=gkvVRYtPjt43SS+IWs/P7iCz5RNZlmZlvF5s0ypy+30=; b=sF+HoEHmuKoXu3VGYAHRnMssWO2yb7rSCdIMsR1hVBNdXHGGiRHYv1VrSODsCYDp+f XWbRRTy7Tar3QnJz7IjGftWkVI47Nh+VgQvbvh1k1yypKzBrC7iE66z88OEfK0SlefBx Uzpal14URK9J6d9bRJikNjunTbtJK7SVJQjf8CgChYaPt9UNTVSi40Wi4G/GX1sdve9+ jGNddVsqvrXvgNU/CxBhWu2EZWHEEOYKgX6987fUJSKX3EnPy3p64/PFeKyvuTOeMLYW pH4umKn7Stpop5pS4ikMm74fluWv9AxgIlOILoKQWuA6pFVvb9XEijwMafQJW+vu1N7m 60FA== Received: by 10.50.219.194 with SMTP id pq2mr3245055igc.25.1344181396011; Sun, 05 Aug 2012 08:43:16 -0700 (PDT) References: From: Robert Newson In-Reply-To: Mime-Version: 1.0 (1.0) Date: Sun, 5 Aug 2012 16:43:13 +0100 Message-ID: <5581890478489220827@unknownmsgid> Subject: Re: Process for code submissions? To: "dev@couchdb.apache.org" Content-Type: text/plain; charset=ISO-8859-1 Sorry for the delay, the patch looks good to me. I'm happy to merge it if you do two things. 1) consistent use of utc_id_suffix instead of id_suffix in config 2) add your name to the THANKS file. B. Sent from my iPad On 5 Aug 2012, at 16:05, Nick North wrote: > I'm wondering if there is any process for dealing with code submissions > i.e. for getting a decision that they are accepted, rejected, or ignored. I > hope the following doesn't come across as a complaint, because I think > CouchDb and the community are great, but I feel in limbo on this particular > topic. > > The reason for asking is that I submitted JIRA issue > COUCHDB-1373a > while back, then let it drop for some while before submitting pull > request 28 with proposed code > for implementing the suggestion. After some initial discussion on the JIRA > issue, there was no response to the pull request, and I don't know if that > means I didn't follow the right process, it has been rejected, it's been > decided to ignore it, or it's gone into a queue to be considered eventually. > > There are many good reasons for not accepting submitted code: the > suggestion may be bad, the code may be bad, there may not be the resources > to deal with it, it may be undesirable creeping featurism, it may come from > someone who hasn't demonstrated good understanding of the project etc. Any > of those verdicts might apply in this case but, whatever the reason is, it > would be good to be told it so that I know whether it's worth expending > more effort to improve my chances of acceptance, or whether to spend that > time on finding ways to carry on without the proposed code. > > If someone can help or guide me, or give an outline of how things operate > in this area, I'd be really grateful. Many thanks, > > Nick North