4 ms·
On the flip side of this thread, some projects have started to adopt specific tagging in their issue systems for folks looking to get started as contributors.
by saidajigumi 11y ago
On the flip side of this thread, some projects have started to adopt specific tagging in their issue systems for folks looking to get started as contributors. I really like this as it's clear communication to both new contributors and to existing contributors that the issue in question is an on-ramp for the project.
Here's Neovim's "entry-level" label, for example:
https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3Aentry-level https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aiss...
- mden 11y agoAs another example it seems that Rust does the same: https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Ais...
- kibwen 11y agoServo inherited that policy too: https://github.com/servo/servo/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy https://github.com/servo/servo/issues?q=is%3Aopen+is%3Aissue...
- fijal 11y agoActually pypy tries to do the same, bitbucket does not support tagging very well though (but looking for "easy" or something in the issue tracker helps). I am personally sorry if the poster had an experience like that, IRC is difficult to communicate over, it must have been a misunderstanding