Learn more about these different git repos.
Other Git URLs
There's a lot of discussion going on about how we can help newcomers find tasks to work on.
https://fedoraproject.org/easyfix/ is one of our go-to locations. However, a common issue seems to be that people don't remember to mark their issues correctly, and so they don't end up on the easyfix list.
We could send out an e-mail to the -devel list to remind folks, but perhaps having an "EasyFix day" as part of the release schedule will be better---that way a reminder will go out each release, every few months?
Thoughts? Any other ideas on how we can keep easyfix in people's minds so they do continuously mark issues?
I wonder if there was a specific team or SIG in Fedora that might be willing to help trial an idea like this. If we could find an approach that worked well for a team or a smaller group, it would be easier to scale it out more widely to the rest of the Fedora community.
I like the idea of cross-sectional teams for this, so two teams that come to find as possibly good candidates would be the Websites & Apps Team and the Python SIG. I have not asked those teams about this yet.
I wonder if there was a specific team or SIG in Fedora that might be willing to help trial an idea like this. If we could find an approach that worked well for a team or a smaller group, it would be easier to scale it out more widely to the rest of the Fedora community. I like the idea of cross-sectional teams for this, so two teams that come to find as possibly good candidates would be the Websites & Apps Team and the Python SIG. I have not asked those teams about this yet.
EasyFix includes QuickDocs issue ticket. Docs team can use 'Good First Issue' label in Pagure. We need more technical reviewers, who are subject matter specialists to a product(s). I expressed my interest in Easyfix to @ankursinha in Discussion. I'm in.
It'll be great to have docs in it.
@jflory7 : could you clarify a little more what the idea to limit this to specific teams is? is it that we only add it to their tasks for the release cycle to begin with?
I was thinking of posting a "Please spend 2 minutes marking your EasyFix issues" thread to -devel per release, similar to the "Please spend 2 minutes testing upgrades to Fedora N+1" thread that we now have per release. So, having this item in the release schedule will provide them more visibility (and remind us to do it).
Login to comment on this ticket.