We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
To have full functionality of fedmsg in fedora messaging, we need to implement fedmsg_meta_fedora_infrastructure methods in the-new-hotness schema.
This will allow any application consuming the-new-hotness messages to have the same functionality as in fedmsg.
The text was updated successfully, but these errors were encountered:
This issue needs to go through every method in https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/blob/develop/fedmsg_meta_fedora_infrastructure/hotness.py and move them to corresponding message class in https://github.com/fedora-infra/the-new-hotness/blob/master/hotness_schema/hotness_schema/messages.py
Sorry, something went wrong.
Messaging schema were migrated to separate repository. This issue is now migrated as well. fedora-infra/the-new-hotness-messages#4
No branches or pull requests
To have full functionality of fedmsg in fedora messaging, we need to implement fedmsg_meta_fedora_infrastructure methods in the-new-hotness schema.
This will allow any application consuming the-new-hotness messages to have the same functionality as in fedmsg.
The text was updated successfully, but these errors were encountered: