|
| 1 | +Long Running Issues - Help Needed |
| 2 | +================================= |
| 3 | + |
| 4 | +Long Running Issues - Scancode Toolkit |
| 5 | +-------------------------------------- |
| 6 | + |
| 7 | +- `Good First Issues List <https://github.com/nexB/scancode-toolkit/issues/1825>`_ |
| 8 | +- `First Timers Only Issues List <https://github.com/nexB/scancode-toolkit/issues/1826>`_ |
| 9 | +- `Add improved documentation for V3.0 <https://github.com/nexB/scancode-toolkit/issues/1146>`_ |
| 10 | +- `Documentation Roadmap <https://github.com/nexB/scancode-toolkit/issues/1824>`_ |
| 11 | +- `Documentation Inconsistencies Tracker <https://github.com/nexB/scancode-toolkit/issues/1813>`_ |
| 12 | + |
| 13 | +.. |
| 14 | + [Suggestions for LRIs][ToDo] |
| 15 | + - People Interested in GSoC (And PRs Opened by Them) |
| 16 | +
|
| 17 | +Roadmaps |
| 18 | +-------- |
| 19 | + |
| 20 | +This section provides a overview of ScanCode developement roadmap, in the sense what maintainers |
| 21 | +are considering, what the long-term goals are. |
| 22 | + |
| 23 | +- :ref:`roadmap` |
| 24 | +- `Milestones <https://github.com/nexB/scancode-toolkit/milestones>`_ |
| 25 | +- `v3.1 <https://github.com/nexB/scancode-toolkit/milestone/11>`_ |
| 26 | +- `v3.2 <https://github.com/nexB/scancode-toolkit/milestone/12>`_ |
| 27 | +- `Documentation Roadmap <https://github.com/nexB/scancode-toolkit/issues/1824>`_ |
| 28 | + |
| 29 | +.. _good_first_issue: |
| 30 | + |
| 31 | +Good First Issue |
| 32 | +---------------- |
| 33 | + |
| 34 | +A `good first issue <https://github.com/nexB/scancode-toolkit/labels/good%20first%20issue>`_ |
| 35 | +means it's recommended for people who haven't contributed to our codebase before. |
| 36 | + |
| 37 | +A ``Solving Good First Issue`` is basically an issue based guide for new contributors to |
| 38 | +solve a ``Good First Issue``. |
| 39 | + |
| 40 | +Manitainers of ScanCode Toolkit label small bugs as good first issues for new contributors. |
| 41 | + |
| 42 | +Important Links |
| 43 | +^^^^^^^^^^^^^^^ |
| 44 | + |
| 45 | +- Issues labeled `good first issue <https://github.com/nexB/scancode-toolkit/labels/good%20first%20issue>`_ |
| 46 | +- The status `list of good first issue <https://github.com/nexB/scancode-toolkit/issues/1825>`_ |
| 47 | +- opening a `Solving Good First Issue <https://github.com/nexB/scancode-toolkit/issues/new?assignees=&labels=first+issue+solving&template=--good-first-issue.md&title=>`_ |
| 48 | + |
| 49 | +What you should understand before Solving a Good First Issue |
| 50 | +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 51 | + |
| 52 | +- ScanCode Toolkit tracks different kinds of `issues using GitHub <https://github.com/nexB/scancode-toolkit/issues/>`_. |
| 53 | +- Some of these issues are labeled ``Good First Issue`` by the Maintainers, as in they |
| 54 | + recommend them. |
| 55 | +- A list of ``Good First Issue`` is also maintained `here <https://github.com/nexB/scancode-toolkit/issues/1825>`_. |
| 56 | +- The list of ``Good First Issue`` contains a list of Issues, people assigned to them |
| 57 | + (or waiting to be assigned) and their status (active/completed). |
| 58 | +- Issues here are marked Solved using a `Task List <https://help.github.com/en/github/managing-your-work-on-github/about-task-lists>`_. |
| 59 | +- Contributors come at this issue (and not at individual issues) and ask the maintainers to |
| 60 | + be assigned. |
| 61 | +- After being assigned, contributors open another Issue labeled ``Solving Good First Issue`` |
| 62 | + so maintainers can Track their Progress on that Issue. |
| 63 | +- The task list in the new issue opened (labeled ``Solving Good First Issue``) has to be updated by |
| 64 | + the Contributor. |
| 65 | + |
| 66 | +Step by Step Workflow : Contributor's Tasks |
| 67 | +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 68 | + |
| 69 | +#. Look at the Issues in `Good First Issues List <https://github.com/nexB/scancode-toolkit/issues/1825>`_ |
| 70 | + These are basically all the `issues labeled Good First Issue <https://github.com/nexB/scancode-toolkit/labels/good%20first%20issue>`_ |
| 71 | + with information on people assigned to the issues, and their status. |
| 72 | + |
| 73 | +#. Select a ``Good First Issue`` which isn't assigned and comment in the `Good First Issues List <https://github.com/nexB/scancode-toolkit/issues/1825>`_ |
| 74 | + asking the maintainers to assign you. |
| 75 | + |
| 76 | +#. After you are assigned to that Issue by a maintainer, make sure you are assigned to the one you |
| 77 | + requested. It'll look like ``[ ] #1724 @AyanSinhaMahapatra`` where ``#1724`` is the Issue number |
| 78 | + and ``AyanSinhaMahapatra`` is your GitHub user ID. |
| 79 | + |
| 80 | +#. Open an Issue labeled `Solving Good First Issue here <https://github.com/nexB/scancode-toolkit/issues/new?assignees=&labels=first+issue+solving&template=--good-first-issue.md&title=>`_ . |
| 81 | + |
| 82 | +#. In this issue you opened, reference the following: |
| 83 | + (include ``#[number]`` in comments, like ``#1724``) |
| 84 | + |
| 85 | + - The Original issue labeled ``Good First Issue`` that you are solving. |
| 86 | + - The Pull Request you open later. |
| 87 | + - The `Good First Issues List <https://github.com/nexB/scancode-toolkit/issues/1825>`_ |
| 88 | + |
| 89 | +#. Follow the Instruction on that Issue (It's a Template you'll just have to mark the Task List |
| 90 | + as you complete tasks) |
| 91 | + |
| 92 | + - **Claim this issue** |
| 93 | + - **Reproduce** |
| 94 | + - **Create a Unit test** |
| 95 | + - **Come up with a Solution** |
| 96 | + - **Code your Solution** |
| 97 | + - **Run the tests locally** |
| 98 | + - **Commit and Push** |
| 99 | + - **Start a Pull Request** |
| 100 | + - **Make Sure all the Tests Pass** |
| 101 | + - **Done** Ask in comments for a review :) |
| 102 | + |
| 103 | +#. Remind maintainers to close both Issues, after your Pull Request is Merged. |
| 104 | + |
| 105 | + - The Original issue labeled ``Good First Issue`` |
| 106 | + - The issue opened by you labeled ``Solving Good First Issue`` |
| 107 | + |
| 108 | +.. _first_timers_only: |
| 109 | + |
| 110 | +First Timers Only |
| 111 | +----------------- |
| 112 | + |
| 113 | +A `first timers only <https://github.com/nexB/scancode-toolkit/labels/%20first%20timers%20only>`_. |
| 114 | +issue means we've worked to make it more legible to folks who either **haven't contributed to our |
| 115 | +codebase before, or even folks who haven't contributed to open source before**. |
| 116 | + |
| 117 | +Small documenation inconsistencies are first timers only issues for new contributors. |
| 118 | + |
| 119 | +Important Links |
| 120 | +^^^^^^^^^^^^^^^ |
| 121 | + |
| 122 | +- Issues labeled `first timers only <https://github.com/nexB/scancode-toolkit/labels/%20first%20timers%20only>`_ |
| 123 | +- The status list of `all first timers only <https://github.com/nexB/scancode-toolkit/issues/1826>`_ Issues |
| 124 | +- All `Documentation Inconsistencies Issue <https://github.com/nexB/scancode-toolkit/issues/1813>`_. |
| 125 | +- opening a `First Timers Only Issue <https://github.com/nexB/scancode-toolkit/issues/new?assignees=&labels=first+timers+only&template=--first-timers-only.md&title=>`_ |
| 126 | + |
| 127 | +What you should understand before Solving a First Timers Only Issue |
| 128 | +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 129 | + |
| 130 | +- ScanCode Toolkit tracks different kinds of `issues using GitHub <https://github.com/nexB/scancode-toolkit/issues/>`_. |
| 131 | +- Some of these issues are documentation inconsistencies `listed here <https://github.com/nexB/scancode-toolkit/issues/1813>`_. |
| 132 | +- A list of ``First Timers Only`` Issues is also `maintained here <https://github.com/nexB/scancode-toolkit/issues/1826>`_. |
| 133 | +- The list of ``First Timers Only`` contains a list of Issues, people assigned to them |
| 134 | + (or waiting to be assigned) and their status (active/completed). |
| 135 | +- Issues here are marked Solved using a `Task List <https://help.github.com/en/github/managing-your-work-on-github/about-task-lists>`_. |
| 136 | +- Contributors come at this issue and ask the maintainers to be assigned. |
| 137 | +- After being assigned, contributors open another Issue labeled ``First Timers Only`` |
| 138 | + so maintainers can Track their Progress. |
| 139 | +- The task list has to be updated by the Contributor. |
| 140 | + |
| 141 | +Step by Step Workflow : Contributor's Tasks |
| 142 | +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 143 | + |
| 144 | +#. Look at the Issues in ``First Timers Only`` `List <https://github.com/nexB/scancode-toolkit/issues/1825>`_ |
| 145 | + These are basically all the `issues <https://github.com/nexB/scancode-toolkit/labels/%20first%20timers%20only>`_ |
| 146 | + labeled ``First Timers Only`` issues, with information on people assigned to the issues, |
| 147 | + and their status. |
| 148 | + |
| 149 | +#. Select a ``First Timers Only`` issue which isn't assigned to anyone yet, and comment on the |
| 150 | + `List <https://github.com/nexB/scancode-toolkit/issues/1825>`_ asking the maintainers to assign |
| 151 | + you. |
| 152 | + |
| 153 | +#. After you are assigned to that Issue by a maintainer, make sure you are assigned to the one you |
| 154 | + requested. It'll look like ``[ ] #1724 @AyanSinhaMahapatra`` where ``#1724`` is the Issue number |
| 155 | + and ``AyanSinhaMahapatra`` is your GitHub user ID. |
| 156 | + |
| 157 | +#. Open an Issue labeled `First Timers Only here <https://github.com/nexB/scancode-toolkit/issues/new?assignees=&labels=first+timers+only&template=--first-timers-only.md&title=>`_ . |
| 158 | + |
| 159 | +#. In this issue you opened, reference the following: |
| 160 | + (include ``#[number]`` in comments, like ``#1724``) |
| 161 | + |
| 162 | + - The Original issue labeled ``Good First Issue`` that you are solving. |
| 163 | + - The Pull Request you open later. |
| 164 | + - The `Good First Issues List <https://github.com/nexB/scancode-toolkit/issues/1825>`_ |
| 165 | + |
| 166 | +#. Follow the Instruction on that Issue (It's a Template you'll just have to mark the Task List |
| 167 | + as you complete tasks) |
| 168 | + |
| 169 | + - **Issue Claimed** |
| 170 | + - **Review Guidelines** |
| 171 | + - **Refer Documentation** |
| 172 | + - **Build Docs Locally** |
| 173 | + - **Update** |
| 174 | + - **Commit and Push** |
| 175 | + - **Start a Pull Request** |
| 176 | + - **Make Sure all the Tests Pass** |
| 177 | + - **Done** Ask in comments for a review :) |
0 commit comments