I started writing this a while ago and never got it fully formed. Rather than let it keep rotting in my drafts folder I wanted to share it and see if it made sense to anyone else.
Warning - rough edges ahead!
Conversations with several people have resulted in distilling the following idea:
== Changing metadata
Modify the table that drives fedoraproject.org/easyfix that is located at https://fedoraproject.org/wiki/Easyfix
The table would now include two additional columns (optional)
Col 1 = existing reference to the issue tracker. We should consider adding gitlab.com support
Col 2 = existing point of contact
Col 3 = category of task (documentation, infrastructure, programming-Haskell, programming-Ruby, etc.)
Col 4 = SIG/WG/etc. this project is related too (Design, Council, KDE, etc.)
== Changing fedoraproject.org/easyfix
Today we show only two categories: Issues from Pagure/Github and Bugzillas
I believe those categories are not the right categories for consumers of the page. Using the new category (col 3) above, we would break things out by the kind of contribution. This would serve to let people browse related tasks more easily and to reduce the overwhelming nature of the current lists.
For BZs we are either going to have to guess based on BZ metadata or leave them lumped together.
WCDIFF should be extended to show the categories and groups appropriate for the various endpoints. This way the person who navigates WCDIFF has the option of reading a specific task they could work on right now, if they so desire.
The categories give us the opportunity to promote our easyfixes as a great way to join or contribute in a targeted manner. This could come in the form of articles, tweets, or live conference appearances.
What do people think?
I wanted to notify in advance that I will not be active in Fedora from
May to August 2018; I hope to continue maintaining the Community Blog
over the summer months, but I will not be active regularly or
participate during meetings.
I'd like to work with everyone on selecting a new Mindshare
representative from CommOps for Fedora 29 release cycle. We can cover
this more in next week's meeting.
Thanks all. We'll work more on transitioning towards the summer over
this next month.
Justin W. Flory
I reviewed the Etherpad for the proposed email to send to the
Ambassadors list; I added some edits but want your feedback too.
I think the draft was unfinished when I went through it. Without making
the email too long for most people to read, I think we should add more
of the "why" for the proposed changes so others understand our motivations.
Generally, I think it is important to be transparent and clear about
what the motivations and objectives are. While it doesn't perfectly
apply to the type of change we suggesting, consider some of the points
I added some of my edits and left footnotes with most of my revisions.
Feel free to write back here with your thoughts or edit directly on the
Justin W. Flory
This is a FBR for a patch to add a FAS group to Fedora Badge mapping for
the 'mindshare' FAS group.
It is a straightforward patch. The patch file is attached.
Let me know if anything else is needed. Thanks!
Justin W. Flory