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 AA486979C for ; Sun, 5 Aug 2012 15:44:30 +0000 (UTC) Received: (qmail 32839 invoked by uid 500); 5 Aug 2012 15:44:30 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 32804 invoked by uid 500); 5 Aug 2012 15:44:30 -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 32796 invoked by uid 99); 5 Aug 2012 15:44:30 -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:44:30 +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.214.180 as permitted sender) Received: from [209.85.214.180] (HELO mail-ob0-f180.google.com) (209.85.214.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Aug 2012 15:44:23 +0000 Received: by obbuo19 with SMTP id uo19so4396822obb.11 for ; Sun, 05 Aug 2012 08:44:03 -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=+fRbAE0iKD2XmvgX2PMM65fs6wv4EmhS52/FGgfgIVE=; b=xQbsOv+KWZ5ccFuGSSTu5OqND+yHdRGGztRK5m9LFbWcEd1HPM+XZjs8THLuokWIQC VLrgD4t5g1tagRoZqg0nfFBNSSXTh49vDQzRHuTas0TSJk4+q8I0z+XXlrscn01qbrN1 KP2d2DqB7R+Jp9J/JubStSDWeoCgXyT8c4MH0gPnfFdoXBwKxV7reAPdcDXZo2i5xUvQ OVkH9xKfdkRNix9Mey7s8tGP/I1M7nDzsWZ4m6zbAkvwJaUSOAMJn8RsAVHj/GTDDB+C yMP/U2s1YzZuEuRhv72usRRwg9kXZHyPbq0GOpDiBdXq3atn1hFIMqXmsLNtr0/Zc66n QgaA== Received: by 10.50.10.166 with SMTP id j6mr3279444igb.38.1344181442744; Sun, 05 Aug 2012 08:44:02 -0700 (PDT) References: From: Robert Newson In-Reply-To: Mime-Version: 1.0 (1.0) Date: Sun, 5 Aug 2012 16:44:00 +0100 Message-ID: <5799695298685609019@unknownmsgid> Subject: Re: Process for code submissions? To: "dev@couchdb.apache.org" Content-Type: text/plain; charset=ISO-8859-1 Heh, and update the changes and news file so it mentions the new feature. :) 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