You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several kinds of improvements to the code that are long-term goals that cross the entire codebase and should be done in small pieces. These are often relatively easy to merge and help increase the overall code quality.
These types of changes are things like:
adding types to the code/increasing the use of linting
adding unit tests/increasing unit test coverage
making code style consistent (print statements)
improving the docs
etc
These types of issues are labeled with the sweeping changes label.
None of these changes should be solved by a single pull request - they are very easy to do in very small parts that are relatively easy to merge. These kinds of initiatives also help us take the older code in this project and bring it up to the same level of understandability as the newer code in the project. This work isn't always the most fun, but it is always helpful/appreciated!
Want something harder/more fun?
You can check the roadmap/task board here: CollectOSS + 8Knot WG Feature Roadmap.
This is a combined CollectOSS and 8Knot roadmap and contains a column for "on deck/up for grabs". This includes more challenging issues that are ready to contribute to. These may be a combination of "good first issues" as well as tasks that may be better suited for repeat contribution and aren't yet claimed/actively being worked on.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
For anyone looking for tasks to work on, here are a couple resources.
Many of these may also be listed in CONTRIBUTING.md, but if they are not, contributions to add them/improve our docs are also always welcome.
Just starting out?
Try [this github search link](https://github.com/chaoss/CollectOSS/issues?q=is%3Aissue%20state%3Aopen%20(label%3A%22good%20first%20issue%22%20OR%20label%3A%22challenging%20first%20issue%22%20OR%20label%3A%22help%20wanted%22) for CollectOSS issues. It will show you everything tagged either good first issue, challenging first issue, or help wanted. Those would be good places to start based on your comfort level with the codebase, Python, Etc. We also have a first-timers-only tag that is not used very much, but may be in the future.
Evergreen improvements
There are several kinds of improvements to the code that are long-term goals that cross the entire codebase and should be done in small pieces. These are often relatively easy to merge and help increase the overall code quality.
These types of changes are things like:
These types of issues are labeled with the
sweeping changeslabel.None of these changes should be solved by a single pull request - they are very easy to do in very small parts that are relatively easy to merge. These kinds of initiatives also help us take the older code in this project and bring it up to the same level of understandability as the newer code in the project. This work isn't always the most fun, but it is always helpful/appreciated!
Want something harder/more fun?
You can check the roadmap/task board here: CollectOSS + 8Knot WG Feature Roadmap.
This is a combined CollectOSS and 8Knot roadmap and contains a column for "on deck/up for grabs". This includes more challenging issues that are ready to contribute to. These may be a combination of "good first issues" as well as tasks that may be better suited for repeat contribution and aren't yet claimed/actively being worked on.
Want to forge your own path?
TBD
All reactions