Replying to [ticket:2 mailga]:

The example decause threw on the table is a tool like Taiga in use by the Infra.
For reference purposes:
[1] https://fedoraproject.org/wiki/Infrastructure/TaigaProject
[2] https://taiga.io/

Revisiting this, is [http://taiga.fedorainfracloud.org/ this] what we can use to do this? I was thinking about this and I'm trying to envision how we could go about making this happen.

Assigning to decause this might be more of a him kind of thing.

This ticket is beginning to stall. Adding it to today's agenda to see if we can put a request in motion or opt to close the ticket and track tickets in other Tracs manually (not preferential).

This is a good idea, but I would like to suggest a slightly different approach:

• zodbot has the #halp/help command, which publishes to fedmsg.
• we publicize to teams (via a short commblog post?) that if they want to 'light up the bat signal' and have commops help with their tickets, then they should write a short description, and link to a ticket in their track to get it onto our radar. This is listed as one of the tools in our box, IIRC (if it isn't then we should add it to the 'wiki gardening' section of the next meeting ;) )
• this doesn't require us to do duplicate ticket filing, keeps commops members hacking "upstream" (within the subproject's ticketing system), and publishes the call for help widely for anyone else who wants to help too.

Thoughts?

Replying to [comment:5 decause]:

they should write a short description, and link to a ticket in their track to get it onto our radar.

Could you clarify where they would put the description + ticket link? On our mailing list?

Replying to [comment:6 jflory7]:

Replying to [comment:5 decause]:

they should write a short description, and link to a ticket in their track to get it onto our radar.

Could you clarify where they would put the description + ticket link? On our mailing list?

They should use the #halp command like so:

help help us socialize this new tool that helps Fedoran's get contributors for commops to help them! https://fedorahosted.org/fedora-commops/ticket/2

'''Discussed in [https://meetbot.fedoraproject.org/fedora-meeting-2/2016-02-23/commops.2016-02-23-16.55.html 2016-02-23 meeting].'''

= Creating a tool =
We agreed that to help keep #help MeetBot messages on CommOps radar, the best course of action is to begin developing or request a tool that will take those notifications at the end of a meeting and email a list of #help messages and møte URL to CommOps mailing list and IRC.

= How to make the tool =
The question I still have is do we want to develop this "in house" a la CommOps or do we want to request for a tool by Infrastructure / other SIG to help us produce this? Or who knows, maybe this is something Remy or Ralph or someone else could whip out in 30 minutes.

'''Discussed in [https://meetbot.fedoraproject.org/fedora-meeting-2/2016-03-01/commops.2016-03-01-16.55.html 2016-03-08 meeting].'''

We opted to hold off on this ticket until Ralph (threebean) has more time to look into something like this. For now, we're holding off and will resume progress on this ticket once we discuss with Ralph.

= Milestone period reached =

The end of the Fedora 23 release cycle hit today. We're discussing this ticket in our hack session happening now, and we've come to the conclusion that developing a custom, Trac-based solution for this would be backwards-facing since there is a large push to "drop" Trac in favor of moving to Pagure. The Infrastructure team has put an EoL on Trac, although I'm unsure of the date.

For now, if we want to develop a custom solution, we should probably look closer at doing something with metadata in Pagure.

Closing ticket as ''wontfix''.