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?
This is just a reminder that on 2018-May-22 at 23:59:59 UTC we will close
the Nomination window of May-2018 Elections.
Please check the nomination pages  and apply, if you are
interested to work in FESCo, Council or Mindshare teams.
On Wed, May 16, 2018 at 2:05 AM, Jan Kurik <jkurik(a)redhat.com> wrote:
> Today we are starting the Nomination & Campaign period during which we
> accept nominations to the "steering bodies" of the following teams:
> * FESCo (Engineering) (4 seats) 
> * Fedora Council (1 seat) 
> * Mindshare (1 seat) 
> This period is open until 2018-May-22 at 23:59:59 UTC.
> The nominees can already start preparing their answers for questions
> in the Election Questionnaire. The questions can be found in the
> template files.
> Nominees submit their questionnaire answers via a private Pagure
> issue. The Election Wrangler or their backup will publish the
> interviews to the Community Blog  a day before the start of the
> Voting period (2018-May-30).
> Please note that the interview is mandatory for all nominees. Nominees
> not having their interview ready by end of the Interview period
> (2018-May-29) will be disqualified and removed from the election.
> Nominees may submit their interview answers immediately and may edit
> them until the end of the interview period.
> Nominees are encouraged to begin their interview answers as soon as
> they accept their nomination.
> As part of the Campaign people might also ask questions to specific
> candidates on @devel mailing list, if they want.
> The full schedule of the May 2018 Elections is available on the
> Elections wiki page .
>  https://fedoraproject.org/wiki/Development/
>  https://fedoraproject.org/wiki/Council/Nominations
>  https://fedoraproject.org/wiki/Mindshare/Nominations
>  https://pagure.io/fedora-project-schedule/blob/master/
>  https://pagure.io/fedora-project-schedule/issues
>  http://communityblog.fedoraproject.org/
>  https://fedoraproject.org/wiki/Elections
> Jan Kuřík
> JBoss EAP Program Manager
> Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
JBoss EAP Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic