Remove some Pagure issue tags based on current workflow
I was looking through the tag settings on this repo and thought we could clean them up a little. There are many we aren't using or not regularly maintained.
Per policy, we can use the lazy approval process for this ticket. Next Monday, if there are no objections, I will remove the following tags from our Pagure repo.
I propose removing these tags:
difficulty - (easy,medium,hard)
meeting
type - awareness
type - outreach
type - Flock
difficulty - (easy,medium,hard) - This one should not be removed if we want new comers to pick and choose some easy tasks IMHO.
I agree with Amita, because that was the purpose why we have that tag. If we want to rename it differently sure, but otherwise we should have a tag that can help newcomers to know which issue they can help us with and it's beginner friendly.
+1 for the type - Flock and awareness. -1 for the meeting tag, because I think it is really helpful to sort the tickets when we have meetings.
@amsharma: difficulty - (easy,medium,hard) - This one should not be removed if we want new comers to pick and choose some easy tasks IMHO. @jonatoni: I agree with Amita, because that was the purpose why we have that tag. If we want to rename it differently sure, but otherwise we should have a tag that can help newcomers to know which issue they can help us with and it's beginner friendly.
@amsharma: difficulty - (easy,medium,hard) - This one should not be removed if we want new comers to pick and choose some easy tasks IMHO.
@jonatoni: I agree with Amita, because that was the purpose why we have that tag. If we want to rename it differently sure, but otherwise we should have a tag that can help newcomers to know which issue they can help us with and it's beginner friendly.
Good points. Instead of rating difficulties, what if we consistently use the good first issue tag that already exists? What both of you said tells me it is important to identify good tasks for newcomers, which would be the easy difficulty. I think rating a task as medium or hard is subjective and depends on the person. Also, we don't use medium and hard tags regularly. Therefore, I suggest we consistently use the good first issue tag, especially since issues tagged with that show up on fedoraproject.org/easyfix.
good first issue
medium
hard
What do you think about replacing the difficulty tags with good first issue?
difficulty
@jonatoni: -1 for the meeting tag, because I think it is really helpful to sort the tickets when we have meetings.
For the last few weeks, I've used the next meeting priority field to sort ticket for meetings. As of now, we do not use the meeting issue tag consistently. So I think it is confusing to have two places to show the same thing. What do you think about replacing the issue tag with the priority field linked here?
next meeting
https://pagure.io/fedora-diversity/issues?status=Open&priority=20
I removed the type - awareness and type - Flock tags in place of the alternatives mentioned above.
@amsharma @jonatoni Let me know if my last comment addresses your feedback about the other tags.
I agree with the counter arguments given @jflory7. Please go ahead with the suggested removals, you have my +1.
Thanks for this,
+1 from me as well
Thanks all. I cleaned up the remaining tags. Closing this ticket as complete. :clapper:
Metadata Update from @jflory7: - Issue close_status updated to: complete - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.