|
| 1 | +============ |
| 2 | +Contributing |
| 3 | +============ |
| 4 | + |
| 5 | +Contributions are welcome and appreciated! |
| 6 | +Every little bit helps, and a credit will always be given. |
| 7 | + |
| 8 | +.. _issues : https://github.com/nexB/scancode-workbench/issues |
| 9 | +__ issues_ |
| 10 | + |
| 11 | +If you are new to ScanCode Workbench and want to find easy tickets to work on, |
| 12 | +check `easy issues <https://github.com/nexB/scancode-workbench/labels/easy>`_ |
| 13 | + |
| 14 | +When contributing to ScanCode Workbench (such as code, bugs, documentation, etc.) you |
| 15 | +agree to the Developer `Certificate of Origin <http://developercertificate.org/>`_ |
| 16 | +and the ScanCode license (see the `NOTICE <https://github.com/nexB/scancode-workbench/blob/develop/NOTICE>`_ file). |
| 17 | +The same approach is used by Linux Kernel developers and several other projects. |
| 18 | + |
| 19 | +For commits, it is best to simply add a line like this to your commit message, |
| 20 | +with your name and email:: |
| 21 | + |
| 22 | + Signed-off-by: Jane Doe <[email protected]> |
| 23 | + |
| 24 | +Please try to write a good commit message, see `good commit message wiki |
| 25 | +<https://aboutcode.readthedocs.io/en/latest/contributing/writing_good_commit_messages.html>`_ for |
| 26 | +details. In particular use the imperative for your commit subject: think that |
| 27 | +you are giving an order to the codebase to update itself. |
| 28 | + |
| 29 | + |
| 30 | +Feature requests and feedback |
| 31 | +============================= |
| 32 | + |
| 33 | +To send feedback or ask a question, `file an issue <issues_>`_ |
| 34 | + |
| 35 | +If you are proposing a feature: |
| 36 | + |
| 37 | +* Explain how it would work. |
| 38 | +* Keep the scope as simple as possible to make it easier to implement. |
| 39 | +* Remember that your contributions are welcomed to implement this feature! |
| 40 | + |
| 41 | + |
| 42 | +Chat with other developers |
| 43 | +========================== |
| 44 | + |
| 45 | +For other questions, discussions, and chats, we have official Matrix rooms: |
| 46 | + |
| 47 | +- `discuss room <https://matrix.to/#/#aboutcode-org_discuss:gitter.im>`_ (for all projects) |
| 48 | +- `scancode-workbench room <https://matrix.to/#/#aboutcode-org_scancode-workbench:gitter.im>`_ |
| 49 | + |
| 50 | + |
| 51 | +Bug reports |
| 52 | +=========== |
| 53 | + |
| 54 | +When `reporting a bug`__ please include: |
| 55 | + |
| 56 | +* Your operating system name, version, and architecture. |
| 57 | +* Your ScanCode Workbench version. |
| 58 | +* Any additional details about your local setup that might be helpful to |
| 59 | + diagnose this bug. |
| 60 | +* Detailed steps to reproduce the bug, such as the scan file you imported, filters you applied, etc. |
| 61 | +* The error messages or failure trace if any. |
| 62 | +* If helpful, you can add a screenshot as an issue attachment when relevant or |
| 63 | + some extra file as a link to a `Gist <https://gist.github.com>`_. |
| 64 | + |
| 65 | + |
| 66 | +Documentation improvements |
| 67 | +========================== |
| 68 | + |
| 69 | +Documentation can come in the form of new documentation pages/sections, tutorials/how-to documents, |
| 70 | +any other general upgrades, etc. Even a minor typo fix is welcomed. |
| 71 | + |
| 72 | +If something is missing in the documentation or if you found some part confusing, |
| 73 | +please file an issue with your suggestions for improvement. Your help and contribution make ScanCode Workbench docs better, we love hearing from you! |
| 74 | + |
| 75 | +The ScanCode Workbench documentation is hosted at `scancode-workbench.readthedocs.io <https://scancode-workbench.readthedocs.io/en/latest/>`_. |
| 76 | + |
| 77 | +If you want to contribute to Scancode Workbench Documentation, you'll find `this guide here <https://scancode-workbench.readthedocs.io/en/latest/contribute/building.html#building-documentation>`_ helpful. |
| 78 | + |
| 79 | + |
| 80 | +Pull Request Guidelines |
| 81 | +----------------------- |
| 82 | + |
| 83 | +If you need a code review or feedback while you are developing the code just |
| 84 | +create a pull request. You can add new commits to your branch as needed. |
| 85 | + |
| 86 | +For merging, your request would need to: |
| 87 | + |
| 88 | +1. Include unit tests that are passing (run ``npm test``). |
| 89 | +2. Update documentation as needed for new UI screen, functionality, etc. |
| 90 | +3. Add a note to ``CHANGELOG.rst`` about the changes. |
| 91 | +4. Add your name to ``AUTHORS.rst``. |
0 commit comments