#9576 Please deploy discourse2fedmsg in infrastructure
Opened 10 days ago by mattdm. Modified 8 days ago

Describe what you would like us to do:


discourse2fedmsg is a small (currently 80 lines of python) service (a flask app) which bridges the Discourse forum to our message bus. I'd like this running in production somewhere, taking messages from both discussion.fedoraproject.org and ask.fedoraproject.org

I assume that this needs to actually be converted from fedmsg to the new message bus.

There may also be some adjustments needed to get the messages into a useful format. This was running in test before but never in production

When do you need this to be done by? (YYYY/MM/DD)


I would love to have this up and running before the next Flock -- well, Nest with Fedora. So, sometime like 2021/06/01 would be ideal.

It is not urgent, but I would love to be able to add forum participation to our general community metrics. It would also allow us to add Fedora Badges for forum activity.


This sounds more like a initiative to me: https://docs.fedoraproject.org/en-US/cpe/initiatives/
But we have one similar initiative this quarter, so we will see if this could be part of it.

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: dev, high-gain, high-trouble, ops

9 days ago

Metadata Update from @zlopez:
- Issue priority set to: Waiting on External (was: Waiting on Assignee)

9 days ago

Oh, also: this is the current fedmsg service: https://pagure.io/discourse2fedmsg. Patrick had it deployed in a testing instance but it is no longer running.

Also: we would want to be able to distinguish between different discourse instances. I'm not sure if the current code does this.

Metadata Update from @pingou:
- Issue tagged with: request-for-resources

8 days ago

Login to comment on this ticket.

Metadata
Boards 2
dev Status: Backlog
ops Status: Backlog