You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-commits@lucene.apache.org by Apache Wiki <wi...@apache.org> on 2011/09/13 07:37:34 UTC

[Solr Wiki] Update of "HowToContribute" by kirill.lykov

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "HowToContribute" page has been changed by kirill.lykov:
http://wiki.apache.org/solr/HowToContribute?action=diff&rev1=65&rev2=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 wiki is a great way to help the patch get committed:  It helps serve as a road map for what the "goal" of the issue is, what should be possible for users to do once the issue is resolved; it helps get people who may not understand the low level details get excited about the new functionality; and it can eventually evolve into the final documentation once the code is committed.  (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).
  
- = Contributing Code (Features, Big Fixes, Tests, etc...) =
+ = Contributing Code (Features, Bug Fixes, Tests, etc...) =
  This section identifies the ''optimal'' steps community member can take to submit a changes or additions to the Solr code base.  This can be new features, bug fixes optimizations of existing features, or tests of existing code to prove it works as advertised (and to make it more robust against possible future changes).
  
  Please note that these are the "optimal" steps, and community members that 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" ...