Modernize contributors file a bit by converting to markdown

Author: TylerBrock

CONTRIBUTING.rst renamed to CONTRIBUTING.md

@@ -1,48 +1,44 @@
-Contributing to the MongoDB Legacy C++ Client Driver Project
-===================================
+## Contributing to the MongoDB Legacy C++ Driver Project
 
 Pull requests are always welcome, and the MongoDB dev team appreciates any help the community can
 give to help make MongoDB better.
 
 For any particular improvement you want to make, you can begin a discussion on the
-`MongoDB Developers Forum`_.  This is the best place discuss your proposed improvement (and its
+[MongoDB Developers Forum][dev-forum]. This is the best place discuss your proposed improvement (and its
 implementation) with the core development team.
 
-.. _MongoDB Developers Forum: https://groups.google.com/forum/?fromgroups#!forum/mongodb-dev
+[dev-forum]: https://groups.google.com/forum/?fromgroups#!forum/mongodb-dev "MongoDB Developers Forum"
 
 
-Getting Started
----------------
+## Getting Started
 
-- Create a `MongoDB JIRA account`_.
-- Create a `Github account`_.
+- Create a [MongoDB JIRA account][jira-account].
+- Create a [Github account][github-account].
 - Fork the repository on Github at https://github.com/mongodb/mongo-cxx-driver.
 - Check out the 'legacy' branch 'git checkout legacy'
 
-.. _MongoDB JIRA account: https://jira.mongodb.org/secure/Signup!default.jspa
-.. _Github account: https://github.com/signup/free
+[jira-account]: https://jira.mongodb.org/secure/Signup!default.jspa "MongoDB JIRA Signup"
+[github-account]: https://github.com/signup/free "Githup Signup"
 
 
-JIRA Tickets
-------------
+## JIRA Tickets
 
-All commits to the C++ driver  repository must reference an issue in the `CXX project`_ of the
-MongoDB JIRA.  Before creating any new tickets, please search the existing backlog for any open
-tickets that represent your change request.  If there is not one, then you should create a new
-ticket. Tickets specific to the legacy driver should be filed the label `legacy-cxx`_.
+All commits to the C++ driver  repository must reference an issue in the [CXX project][cxx-project]
+of the MongoDB JIRA. Before creating any new tickets, please search the existing backlog for any open
+tickets that represent your change request. If there is not one, then you should create a new
+ticket. Tickets specific to the legacy driver should be filed the label [legacy-cxx][legacy-cxx].
 
 For bugs, please clearly describe the issue you are resolving, including the platforms on which
 the issue is present and clear steps to reproduce.
 
 For improvements or feature requests, be sure to explain the goal or use case and the approach
 your solution will take.
 
-.. _SERVER project: https://jira.mongodb.org/browse/CXX
-.. _legacy-cxx: https://jira.mongodb.org/browse/CXX-69?jql=labels%20%3D%20legacy-cxx
+[cxx-project]: https://jira.mongodb.org/browse/CXX
+[legacy-cxx]: https://jira.mongodb.org/browse/CXX-69?jql=labels%20%3D%20legacy-cxx
 
 
-The Life Cycle of a Pull Request
---------------------------------
+## The Life Cycle of a Pull Request
 
 Here's what happens when you submit a pull request:
 
@@ -51,30 +47,27 @@ Here's what happens when you submit a pull request:
 - You should receive a response from one of our engineers with additional questions about your
   contributions.
 - If your pull request matches a ticket and is aligned with the Server Roadmap, it will get
-  triaged and reviewed by the Kernel team.
+  triaged and reviewed by the C++ driver and Kernel teams.
 - Pull requests that have been reviewed and approved will be signed off and merged into a
   development branch and the associated JIRA CXX issue will be resolved with an expected
   fixVersion.
 
 
-Style Guide
------------
+## Style Guide
 
-All commits to the legacy branch must follow the `kernel development rules`_.
+All commits to the legacy branch must follow the [kernel development rules][kernel-dev-rules].
 
-In particular, all code must follow the MongoDB `kernel code style guidelines`_.  For anything
-not covered in this document you should default to the `Google CPP Style Guide`_.
+In particular, all code must follow the MongoDB [kernel code style guidelines][kernel-style-guide].
+For anything not covered in this document you should default to the [Google CPP Style Guide][google-style-guide].
 
-Your commit message should also be prefaced with the relevant JIRA ticket, e.g. "CXX-XXX Fixed
-a bug in aggregation".
+Your commit message should also be prefaced with the relevant JIRA ticket, e.g. "CXX-XXX Fixed a bug in aggregation".
 
-.. _kernel development rules: http://dochub.mongodb.org/core/kernelcodedevelopmentrules
-.. _Kernel Code Style guidelines: http://dochub.mongodb.org/core/kernelcodestyle
-.. _Google CPP Style Guide: http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml
+[kernel-dev-rules]: http://dochub.mongodb.org/core/kernelcodedevelopmentrules
+[kernel-style-guide]: http://dochub.mongodb.org/core/kernelcodestyle
+[google-style-guide]: http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml
 
 
-Testing
--------
+## Testing
 
 Every non-trivial change to the code base should be accompanied by a relevant addition to or
 modification of the test suite.  If you don't believe this is necessary, please add an explanation
@@ -84,10 +77,9 @@ All changes must also pass the full test suite (including your test additions/ch
 local machine before you open a pull request.
 
 
-Contributor Agreement
----------------------
+## Contributor Agreement
 
 A patch will only be considered for merging into the upstream codebase after you have signed the
-`contributor agreement`_.
+[contributor agreement][contributor-agreement].
 
-.. _contributor agreement: http://www.mongodb.com/contributor
+[contributor-agreement]: http://www.mongodb.com/contributor "MongoDB Contributor Agreement"