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?
Hello CommOps team,
I'm writing this mail for ask about the advances or agreements
generated in the FLOCK about the FWD, Actually this is our most urgent
ticket (i think) and i want to know how to help :)
Alberto Rodriguez Sanchez <bt0dotninja(a)fedoraproject.org>
My name is John Harris, and I'm a systems engineer for Splentity Software. I
have been a member of CommOps in the past, though I've had about two years of
inactivity. I now have more stable employment, and I can attend commops
meetings more regularly. I also plan to become more active in other areas of
Fedora, as a packager. Additionally, I am a current member of both the Games
SIG and 3D Printing SIG.
It's good to be back.
John M. Harris, Jr. <johnmh(a)splentity.com>
I hope everyone had an amazing Flock this year! I was hoping to discuss
this there in-person but I couldn't make it this year :(
I've recently resurrected the NeuroFedora SIG (it's my area of research
so I'm quite happy to maintain it), but while I was looking around I saw
that we already have a few science related SIGs in Fedora---I was aware
of maybe one or two, but not all of them, in spite of one or two being
featured on labs.fp.o!
Now, mostly, these are groups of people who come together and package up
software that is relevant to the particular field, and the SIGs work
independently of each other. However when one looks at them, one
realises that lots of work that each SIG does overlaps with other SIGs.
I think it's quite within our community goals to further Open Science.
So, I was wondering if we could organise the SIGs better under a common
umbrella: "Fedora <3 science" or something of the sort. It'll give all
SIGs a common theme, it'll also enable us to market science in Fedora
better (or so I think), and it'll enable other community members
interested in other sciences to start their own SIGs in the future.
What do folks think? Would this come under CommOps? I'm happy to help
with this, of course---I'd really like to make Fedora a "go-to"
distribution for whatever sciences the community can support, not just
Ankur Sinha "FranciscoD"
Is the commblog set up to notify authors when people comment on their
articles? I didn't get one recently for a comment.
Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org
I've started publishing weekly FPgM updates. Right now, I publish on
my blog and put it in my 'fedoraplanet' tag so it shows up on Fedora
Planet. But I thought it might be suitable as a regular part of the
community blog...or it might not. So I put it to you. I'll publish it
wherever you think is best.
Fedora Program Manager
The "Metrics for Community Blog and Fedora Magazine" task  has been a
work in progress for a long time. There were discussions around it
during the FAD and the meetings that followed over the last 7 months. I
did some research on how we can implement this using the current tools
we have at our disposal and mentioned it on the ticket. 
I request everyone to take a look at the issue and share their thoughts
on the proposed approach. These metrics will go a long way in
understanding various aspects of the Community Blog and the Magazine and
also encouraging more contributions.
Dhanesh B. Sabane [dhanesh95]
User Wiki: https://fedoraproject.org/wiki/User:Dhanesh95
PGP ID: 0xB69A98C9C1642329
Fingerprint: 9655 11F2 0D18 E76A 2396 D64D B69A 98C9 C164 2329
You are kindly invited to the meeting:
CommOps weekly meeting on 2018-08-27 from 14:30:00 to 15:30:00 UTC
The meeting will be about:
This meeting is for members of the Community Operations (CommOps) team. We meet once a week on the Freenode IRC channel. Our meeting format is ticket-driven, so we look at tickets tagged as "[meeting](https://pagure.io/fedora-commops/issues?status=Open&tags=meeting)" in our [Pagure repository](https://pagure.io/fedora-commops).
More information about CommOps is found [here](https://docs.fedoraproject.org/fedora-project/subprojects/mindshare....