|
| 1 | +************************ |
| 2 | +Contribute to the Driver |
| 3 | +************************ |
| 4 | + |
| 5 | +.. default-domain:: mongodb |
| 6 | + |
| 7 | +Report Bugs and Request Ruby Driver-Specific Features |
| 8 | +===================================================== |
| 9 | + |
| 10 | +To report a bug in the driver or request a feature specific to the Ruby driver: |
| 11 | + |
| 12 | +1. Visit `our issue tracker <https://jira.mongodb.org/>`_ and login |
| 13 | + (or create an account if you do not have one already). |
| 14 | +2. Navigate to the `RUBY project <https://jira.mongodb.org/browse/RUBY>`_. |
| 15 | +3. Click :guilabel:`Create Issue` and fill out all of the applicable form |
| 16 | + fields. |
| 17 | + |
| 18 | +When creating an issue, please keep in mind that all information in JIRA |
| 19 | +for the RUBY project, as well as the core server (the SERVER project), |
| 20 | +is publicly visible. |
| 21 | + |
| 22 | +**PLEASE DO:** |
| 23 | + |
| 24 | +- Provide as much information as possible about the issue. |
| 25 | +- Provide detailed steps for reproducing the issue. |
| 26 | +- Provide any applicable code snippets, stack traces and log data. |
| 27 | + Do not include any sensitive data or server logs. |
| 28 | +- Specify version numbers of the driver and MongoDB server. |
| 29 | + |
| 30 | +**PLEASE DO NOT:** |
| 31 | + |
| 32 | +- Provide any sensitive data or server logs. |
| 33 | +- Report potential security issues publicly (see 'Security Issues' below). |
| 34 | + |
| 35 | +.. note:: |
| 36 | + |
| 37 | + Bug reports in JIRA for the Ruby driver and the core server (the **SERVER**) |
| 38 | + projects are public. |
| 39 | + |
| 40 | +If you identified a potential security vulnerability in the Ruby driver or |
| 41 | +any other MongoDB product, please report it according to the instructions found |
| 42 | +in the :manual:`Create a Vulnerability Report |
| 43 | +</tutorial/create-a-vulnerability-report>`. |
| 44 | + |
| 45 | + |
| 46 | +Request Product Features |
| 47 | +======================== |
| 48 | + |
| 49 | +To request a feature which is not specific to the Ruby driver, or which |
| 50 | +affects more than the driver alone (for example, a feature which requires |
| 51 | +MongoDB server support), please submit your idea through the |
| 52 | +`MongoDB Feedback Forum <https://feedback.mongodb.com/forums/924286-drivers>`_. |
| 53 | + |
| 54 | + |
| 55 | +Contribute Code |
| 56 | +=============== |
| 57 | + |
| 58 | +The MongoDB Ruby driver source is located |
| 59 | +`at GitHub <https://github.com/mongodb/mongo-ruby-driver>`_. |
| 60 | + |
| 61 | +The list of known issues in the driver is available |
| 62 | +`in JIRA <https://jira.mongodb.org/browse/RUBY>`_. |
| 63 | + |
| 64 | +We recommend creating a JIRA ticket before starting work on a bug fix or |
| 65 | +an improvement to the driver, to obtain feedback from the Ruby driver team |
| 66 | +as to the proposed changes. A JIRA ticket is not required to submit |
| 67 | +a pull request but it is appreciated, especially for non-trivial changes. |
| 68 | + |
| 69 | +Pull requests should be made against the ``master`` branch and |
| 70 | +include relevant tests, if applicable. The Ruby driver team will backport |
| 71 | +the changes to the stable branches, if needed. |
| 72 | + |
| 73 | +A MongoDB deployment is required to run the tests. Setup procedures and |
| 74 | +recommendations for various deployments, as well as how to configure the |
| 75 | +driver's test suite for the deployments, are covered in the `spec |
| 76 | +readme <https://github.com/mongodb/mongo-ruby-driver/blob/master/spec/README.md>`__. |
| 77 | + |
| 78 | +The driver is tested on `Evergreen <https://github.com/evergreen-ci/evergreen>`_, |
| 79 | +MongoDB's in-house continuous integration platform. After a pull request |
| 80 | +is created, one of the Ruby driver team engineers will schedule an Evergreen |
| 81 | +build. |
0 commit comments