[Solr Wiki] Update of "HowToContribute" by ErickErickson

[Apache Wiki <wi...@apache.org>]

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 ErickErickson:
https://wiki.apache.org/solr/HowToContribute?action=diff&rev1=103&rev2=104

Comment:
A bit more on referencing Git rather than SVN

  
  Please be patient.  Committers are busy people too.  If no one responds to your patch after a few days, please make friendly reminders.  Please incorporate others suggestions into your patch if you think they're reasonable. Remember that even a patch that is not committed is useful to the community. Supply first patch as early as possible and updated patches as often as possible during your work. This helps the rest of the community and committers to start understanding, help shaping, commenting on etc. your work throughout the entire process. Supplying a patch does not necessarily mean that it is complete and ready to be committed, it might also just be a way of communicating your idea and progress.
  
+ == Commit process using Git ==
+ '''For committers''' Only committers can put the code in the Git repository. We're still (as of Feb, 2016) in the transition period from SVN to Git and are working out the preferred process.
+ 
+ See [[Git commit process]] for the current recommendations.
+ 
  == JIRA tips (our issue/bug tracker) ==
  The issue tracker we use is a JIRA instance at https://issues.apache.org/jira/browse/SOLR. If you don't yet have an account, just click the "login" link and you'll get the opportunity to create one that will allow you to add tickets, upload patches etc.
  
@@ -213, +218 @@

   * When attaching newer versions of a file/patch, use the same name... JIRA will "gray out" the older versions automatically.
   * Please do not delete older files that you have already added - the complete history of an issue is important.
   * If you aren't sure if something is a bug, please ask on the solr-user mailing list before opening an issue.
-  * The "Activity" section of an issue by default only lists "Comments".  If you click on the "All" subtab you can see all activity related to this issue, including any edits that might have been made to the summary or description, as well as an SVN commits that mention this issue in the commit log.
+  * The "Activity" section of an issue by default only lists "Comments".  If you click on the "All" subtab you can see all activity related to this issue, including any edits that might have been made to the summary or description, as well as an commits that mention this issue in the commit log.
  
  <<Anchor(TestingPatches)>>
  
@@ -225, +230 @@

  
  {{{
  $ cd <your Solr trunk checkout dir>
- $ svn up
+ $ git pull
  $ wget <URL of the patch>
- $ patch -p0 -i name of the patch --dry-run
+ $ patch -p1 -i name of the patch --dry-run
  }}}
  
+ (notes: 
- (note: --dry-run just pretends to apply a patch, so you can see if it would succeed or fail.  Remove --dry-run to *really* apply the patch)
+    --dry-run just pretends to apply a patch, so you can see if it would succeed or fail.  Remove --dry-run to *really* apply the patch
+    -p1 may need to be -p0 for svn-generated patches that should be rare going forward.)
  
  The address for the patch can be obtained from the issue page, under the "File Attachments" section of the issue.
  
@@ -238, +245 @@

  
  {{{
  $ cd <your Solr trunk checkout dir>
- $ svn up
+ $ git pull
- $ wget <URL to the patch> -O - | patch -p0 --dry-run
+ $ wget <URL to the patch> -O - | patch -p1 --dry-run
  }}}
  
  If you are on Solaris, you should replace 'patch' with 'gpatch' to use GNU Patch instead.
@@ -287, +294 @@

  See [[https://wiki.apache.org/lucene-java/HowtoConfigureNetbeans|the Lucene wiki page on configuring Netbeans]].
  
  = Maven =
- There is information about using Maven with Solr and Lucene in the source tree, at `dev-tools/maven/README.maven`.  The information differs slightly by code branch.  Here is a link to this file for the trunk version (unreleased; will be released as version 6.0 as of this writing): [[http://svn.apache.org/repos/asf/lucene/dev/trunk/dev-tools/maven/README.maven]]
+ There is information about using Maven with Solr and Lucene in the source tree, at `dev-tools/maven/README.maven`.  The information differs slightly by code branch.  Here is a link to this file for the trunk version (unreleased; will be released as version 6.0 as of this writing): [[README.maven|https://git1-us-west.apache.org/repos/asf?p=lucene-solr.git;a=blob;f=dev-tools/maven/README.maven;h=390177172cd2fee2639e83d2cf4900bea1e8d05f;hb=refs/heads/master]]
  
  = Getting your feet wet: where to begin? =
  New to Solr?  Want to find JIRA issues that you can work on without taking on the whole world?