Return-Path: X-Original-To: apmail-lucene-solr-commits-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6CBFE85D8 for ; Tue, 13 Sep 2011 05:38:13 +0000 (UTC) Received: (qmail 75785 invoked by uid 500); 13 Sep 2011 05:38:12 -0000 Delivered-To: apmail-lucene-solr-commits-archive@lucene.apache.org Received: (qmail 75646 invoked by uid 500); 13 Sep 2011 05:38:00 -0000 Mailing-List: contact solr-commits-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-dev@lucene.apache.org Delivered-To: mailing list solr-commits@lucene.apache.org Received: (qmail 75629 invoked by uid 99); 13 Sep 2011 05:37:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Sep 2011 05:37:56 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.131] (HELO eos.apache.org) (140.211.11.131) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Sep 2011 05:37:55 +0000 Received: from eos.apache.org (localhost [127.0.0.1]) by eos.apache.org (Postfix) with ESMTP id F33AC86B; Tue, 13 Sep 2011 05:37:34 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: Apache Wiki To: Apache Wiki Date: Tue, 13 Sep 2011 05:37:34 -0000 Message-ID: <20110913053734.13642.22908@eos.apache.org> Subject: =?utf-8?q?=5BSolr_Wiki=5D_Update_of_=22HowToContribute=22_by_kirill=2Elyk?= =?utf-8?q?ov?= Auto-Submitted: auto-generated Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for chan= ge notification. The "HowToContribute" page has been changed by kirill.lykov: http://wiki.apache.org/solr/HowToContribute?action=3Ddiff&rev1=3D65&rev2=3D= 66 Comment: Corrected mistake: Big Fixes -> Bug Fixes = If there is a patch in Jira that you think is really great, writing some = "user guide" style docs about how it works (or is suppose to work) in the w= iki is a great way to help the patch get committed: It helps serve as a ro= ad map for what the "goal" of the issue is, what should be possible for use= rs to do once the issue is resolved; it helps get people who may not unders= tand the low level details get excited about the new functionality; and it = can eventually evolve into the final documentation once the code is committ= ed. (just make sure to link to the issue so people who find your wiki page= first know it's not included in Solr's main code line yet). = - =3D Contributing Code (Features, Big Fixes, Tests, etc...) =3D + =3D Contributing Code (Features, Bug Fixes, Tests, etc...) =3D This section identifies the ''optimal'' steps community member can take t= o submit a changes or additions to the Solr code base. This can be new fea= tures, bug fixes optimizations of existing features, or tests of existing c= ode to prove it works as advertised (and to make it more robust against pos= sible future changes). = Please note that these are the "optimal" steps, and community members tha= t don't have the time or resources to do everything outlined on this below = should not be discouraged from submitting their ideas "as is" per "Yonik's = Law of Patches" ...