make sure the ticket hasn't already been picked up by someone else
Once someone volunteers on the issue, we generally assign it to them. This is also mentioned in the automatic reply we post on every new issue:
To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem
/oss and we will follow up within 3 business days.
Alas not everyone always follows this process, but overall this seems to be working out quite nicely lately.
There is one minor thing when you mention @forem
/oss generally it appears in normal font weight not in bold like when you mention user. I was confused couple of times because of this (double checking if I typed it correctly). It would be nice if the text @forem
/oss could also be made bold in Github comment.
Unfortunately it seems team mentions were primarily intended for internal use, there doesn't seem a way to make them work as expected when external contributors use them âšī¸
That's true - I think as a beginner to a repo you might not take that extra step of filtering though, and just default to looking through "good first issue".
Also I've found that sometimes there are some good tickets to work on that have already been picked up by someone else, but it will have been over a month or quite some time since it has been assigned to them and they never had the chance to work on it.
All good points and we're definitely aware of these issues. Maybe we could aid this process by automatically adding another label when assigning someone, but we're open to all suggestions đ
For further actions, you may consider blocking this person and/or reporting abuse
Once someone volunteers on the issue, we generally assign it to them. This is also mentioned in the automatic reply we post on every new issue:
Alas not everyone always follows this process, but overall this seems to be working out quite nicely lately.
There is one minor thing when you mention @forem /oss generally it appears in normal font weight not in bold like when you mention user. I was confused couple of times because of this (double checking if I typed it correctly). It would be nice if the text @forem /oss could also be made bold in Github comment.
Unfortunately it seems team mentions were primarily intended for internal use, there doesn't seem a way to make them work as expected when external contributors use them âšī¸
That's true - I think as a beginner to a repo you might not take that extra step of filtering though, and just default to looking through "good first issue".
Also I've found that sometimes there are some good tickets to work on that have already been picked up by someone else, but it will have been over a month or quite some time since it has been assigned to them and they never had the chance to work on it.
All good points and we're definitely aware of these issues. Maybe we could aid this process by automatically adding another label when assigning someone, but we're open to all suggestions đ