mindshare/tickets

Fork 0

Action items for Recognition Service team from Fedora Council Strategy Summit 2026 #116

New issue

Open

opened 2026-04-01 09:13:02 +00:00 by t0xic0der · 4 comments

t0xic0der commented

2026-04-01 09:13:02 +00:00

Owner

This action item includes a necessary activity prescribed from the discussions that took place during the Fedora Council Strategy Summit 2026, for the Recognition Service team of the Fedora Mindshare committee.

Make progress on the Fedora Badges Revamp Project by onboarding contributors in the ongoing efforts and sharing updates with the community and with the Fedora Council regularly along the way.
Liaise with the Data WG to funnel their deliverables into leveraging community health metrics and the tangible contributor recognition programme, while sharing progress updates on a regular basis.

The aforementioned requirements are expected to be completed and reported upon by the commencement of the annual flagship community conference, Flock To Fedora 2026 (that is, on or before 14th June 2026).

This action item includes a necessary activity prescribed from the discussions that took place during the **Fedora Council Strategy Summit 2026**, for the [**Recognition Service**](https://docs.fedoraproject.org/en-US/mindshare-committee/#responsibilities-recognition) team of the [**Fedora Mindshare**](https://docs.fedoraproject.org/en-US/mindshare-committee/) committee. - Make progress on the Fedora Badges Revamp Project by onboarding contributors in the ongoing efforts and sharing updates with the community and with the Fedora Council regularly along the way. - Liaise with the Data WG to funnel their deliverables into leveraging community health metrics and the tangible contributor recognition programme, while sharing progress updates on a regular basis. The aforementioned requirements are expected to be completed and reported upon by the commencement of the annual flagship community conference, **Flock To Fedora 2026** (that is, on or before **14th June 2026**).

t0xic0der self-assigned this

2026-04-02 10:20:27 +00:00

gwmngilfen was assigned by t0xic0der

2026-04-02 10:20:27 +00:00

t0xic0der commented

2026-05-11 03:31:17 +00:00

Author

Owner

I can provide updates on the Fedora Badges Revamp Project's progress. @sdglitched, @abompard and I are participating as mentors in this Outreachy cohort. We have also gotten ourselves an intern who would start working with us from 18th May 2026 onward. We are expecting to have a staging deployment with the advancements made available to the community by the Flock To Fedora 2026's commencement (i.e. by 14th June 2026), and/or have regular updates provided on community platforms.

@gwmngilfen, do you have any updates to provide on the community data health metrics? Is there anyway we can help you?

t0xic0der added a new dependency

2026-05-11 03:50:11 +00:00

#96 Proposal for Tangible Contributor Recognition Awards under Fedora Mindshare Recognition Service

gwmngilfen commented

2026-05-11 13:02:05 +00:00

Owner

@t0xic0der Sadly, I do not. I have not had the time to get on top of this, and I don't see that changing in the next few weeks.

I believe the Data WG is coving out from under CommOps, so I wonder if @mwinters or @rwright would be able to join the discussion directly to help inform us on what's available today, and what might be doable in the near future?

@t0xic0der Sadly, I do not. I have not had the time to get on top of this, and I don't see that changing in the next few weeks. I believe the Data WG is coving out from under CommOps, so I wonder if @mwinters or @rwright would be able to join the discussion directly to help inform us on what's available today, and what might be doable in the near future?

mwinters commented

2026-05-20 15:14:11 +00:00

FYI @rwright is taking some time away from open source until at least Flock, and possibly longer.

I'd be delighted to connect around this! Everyone seems to have had their hands full with the new cohort and interns, so we indefinitely deferred that conversation until further notice. I think a "high bandwidth" convo would be best for initial sync, though keep in mind I'm in UTC-5. Want to catch me on Matrix to set up a time?

There are absolutely opportunities for FDWG and Badges to complement each other, though this requires a shared understanding and alignment of our technical roadmaps. I'm slightly concerned that there is a possibility that the Badges revamp could get built in a way that doesn't capitalize on those opportunities, or where we end up duplicating effort to achieve the same result through different means, so I'm eager to discuss.

As for FDWG status, very briefly:

Technical status

In short, "what's available today, and what might be doable in the near future" is entirely malleable:

FDWG has an ambitious technical roadmap, and we are operating in an extremely constrained environment (a single bare-metal server of fairly meek capacity by modern standards). So we are iterating on both "what can be done" and "the best way to do it given the constraints." As a result, the "current status" shifts frequently.
A significant aspect of "what might be doable in the near future" depends on the status of several upstream projects. The nature of "working with difficult data within tight constraints" has us leaning heavily on cutting-edge features across several projects. This is a significant part of why the current status shifts frequently, as new software releases unlock new capabilities (which sometimes don't work!).
I have been re-prioritizing my efforts frequently based on current interest and availability of others. So the roadmap is very "squishy", and I'm happy to shift it based on a big-picture view. We've been iterating in our own bubble simply for lack of opportunities to connect.

Community status

@gwmngilfen is correct: we have been busy establishing ourselves as an independent SIG. You can check out our extremely bare-bones orientation at https://forge.fedoraproject.org/fdwg/fdwg . We have several other near-term goals including setting up public docs and similar foundational pieces.
We now have several consistent contributors (with widely-varying availability) across infra, analytics, etc. We have seen a slow trickle of newcomers (1 or 2 a month), which is entirely organic because:
I have generally held off on creating a public FDWG presence up until very recently in order to get some policy pieces in place first, e.g. council/tickets#566 and https://forge.fedoraproject.org/fdwg/fdwg-agreements . But since I'm not expecting a quick response (based on past Council velocity), I'm accepting "WIP" status as "good enough" to start announcing our work more publicly. I plan to take a slightly more official version of https://hatlas.mwinters.net/news to the Community Blog soon.

Let's chat!

_FYI @rwright is taking some time away from open source until at least Flock, and possibly longer._ --- I'd be delighted to connect around this! Everyone seems to have had their hands full with the new cohort and interns, so we indefinitely deferred that conversation until further notice. I think a "high bandwidth" convo would be best for initial sync, though keep in mind I'm in UTC-5. Want to catch me on Matrix to set up a time? There are absolutely opportunities for FDWG and Badges to complement each other, though this requires a shared understanding and alignment of our technical roadmaps. I'm slightly concerned that there is a possibility that the Badges revamp could get built in a way that doesn't capitalize on those opportunities, or where we end up duplicating effort to achieve the same result through different means, so I'm eager to discuss. As for FDWG status, very briefly: ### Technical status In short, "what's available today, and what might be doable in the near future" is entirely malleable: - FDWG has an ambitious technical roadmap, and we are operating in an extremely constrained environment (a single bare-metal server of fairly meek capacity by modern standards). So we are iterating on both "what can be done" and "the best way to do it given the constraints." As a result, the "current status" shifts frequently. - A significant aspect of "what might be doable in the near future" depends on the status of several upstream projects. The nature of "working with difficult data within tight constraints" has us leaning heavily on cutting-edge features across several projects. This is a significant part of why the current status shifts frequently, as new software releases unlock new capabilities (which sometimes don't work!). - I have been re-prioritizing my efforts frequently based on current interest and availability of others. So the roadmap is very "squishy", and I'm happy to shift it based on a big-picture view. We've been iterating in our own bubble simply for lack of opportunities to connect. ### Community status - @gwmngilfen is correct: we have been busy establishing ourselves as an independent SIG. You can check out our extremely bare-bones orientation at https://forge.fedoraproject.org/fdwg/fdwg . We have several other near-term goals including setting up public docs and similar foundational pieces. - We now have several consistent contributors (with widely-varying availability) across infra, analytics, etc. We have seen a slow trickle of newcomers (1 or 2 a month), which is entirely organic because: - I have generally held off on creating a public FDWG presence up until very recently in order to get some policy pieces in place first, e.g. https://forge.fedoraproject.org/council/tickets/issues/566 and https://forge.fedoraproject.org/fdwg/fdwg-agreements . But since I'm not expecting a quick response (based on past Council velocity), I'm accepting "WIP" status as "good enough" to start announcing our work more publicly. I plan to take a slightly more official version of https://hatlas.mwinters.net/news to the Community Blog soon. Let's chat!

t0xic0der commented

2026-05-21 03:54:33 +00:00

Author

Owner

To be clear, I am really not trying to have it done by Flock. As long as we have a pathway that we can progress on, I can see if we can get more folks enlisted to help us with this. I get the feeling of being occupied to the brim too so we need to plan wisely.

@mwinters let us touch base on this to share learnings. I think that we can most definitely have a sync call next week. Do you mind sharing a whenisgood link (or something similar tool) so that we can discuss on a workable time? I am in UTC+0530 by the way. To be clear, I am really not trying to have it done by Flock. As long as we have a pathway that we can progress on, I can see if we can get more folks enlisted to help us with this. I get the feeling of being occupied to the brim too so we need to plan wisely.

t0xic0der added the

Rows
Columns