never met a part of the stack I didn't like. sr. engineer at clique studios in chicago, perpetual creative hobbyist, bird friend, local gay agenda promoter. she/her. tips: https://ko-fi.com/carlymho
I think part of labeling something as a good first issue should include saying what types of developer it's a good first issue for (e.g. if it's for CSS devs, Ruby devs, people who really want to do documentation, etc.). I think in general, though, issues for new contributors should be really small in scope (like, on the level of one- or two-line fixes) and well-documented, since that makes them an easier launching pad for people to start working on a project.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think part of labeling something as a good first issue should include saying what types of developer it's a good first issue for (e.g. if it's for CSS devs, Ruby devs, people who really want to do documentation, etc.). I think in general, though, issues for new contributors should be really small in scope (like, on the level of one- or two-line fixes) and well-documented, since that makes them an easier launching pad for people to start working on a project.