The github2fedmsg app has been ported to Fedora Messaging, but it's still a Python 2 app running on Pyramid, in a VM. I think it would be a useful move towards standardization if this app was rewritten to be based on Flask and authlib (instead of Velruse). And Python 3 of course. And it should run in OpenShift.
There are teams in Fedora who rely on the github2fedmsg in their development. Originally this was opened as mini-initiative on fedora-infra tracker. But this is starting to become a more urgent issue and we don't have spare capacity to work on this in I&R team.
Github2fedmsg will be ported over to python3 and fully support Fedora Messaging.
There are a really good ideas in the original ticket about creating a webhook2fedmsg app instead, which could be used to consume various webhooks and could be used as centralised app for all our webhooks consumers. (Can toddlers do that?)
This impacts developers working in Fedora. @dustymabe was the one who wanted to make this more urgent.
Do this initiative have any dependencies? Not that I'm aware of Skills needed? Developer Person who must or should be involved? @dustymabe Other work that should be completed prior to this initiative? None
This is getting more urgent as the app is still running in python2, but there isn't a specific deadline.
big +1 for keeping github2fedmsg functionality maintained - thanks!
i'll note here too at some point the wiki will need to be converted over from using fedmsg to fedora messaging. (at the moment we use a custom PHP mediawiki plugin). Having a webhook to fedoramessaging service would we a possible win here to save us writing PHP code. (there appears to be a stable webhooks plugin for mediawiki already)
The ARC investigation is available here
The ARC investigation document is now finished
Metadata Update from @amoloney: - Issue tagged with: Accepted
This issue is being dropped as the request for Webhooks to Fedora Messaging enables us to deliver on this work instead https://pagure.io/cpe/initiatives-proposal/issue/18
Metadata Update from @amoloney: - Issue untagged with: Accepted - Issue status updated to: Closed (was: Open) - Issue tagged with: Dropped
Login to comment on this ticket.