Infrastructure would like to create a plan to move the Badges wiki and trac instance to Pagure. If you are not familiar, Pagure is our own git repository service for the web, created by Pierre-Ybes Chibon of the Fedora Engineering team. Any Fedora contributor create a repository at Pagure.io - more info in FedoraMag; https://fedoramagazine.org/pagure-diy-git-project-hosting/

Moving projects from fedorahosted to pagure would help us modernize our infrastrcture. See email from Nirik:

We need feedback from all types of user; artists, admins, and anyone in the community that has reported a badges bug or suggested an idea. Can you please answer a couple of questions for us?

 - Have you used Pagure? Are you comfortable with using git?

 - Are there any use cases where opening issues on Pagure would not be a functional replacement for Trac tickets?

NOTE - Pagure has the ability to create ticket Templates which we would use to

replace Trac's ticket functionality. Making it easy to suggest a new badge, work on a request, and flow through the artwork approvals stages.

 - Badges has a pretty big history. As you go back through time in git, how far

back is important? Do we need a year's history? More? Less?

 - Pagure also has the ability to host docs for a project, so we could move the design resources there. Are there any other documents that would belong in a docs repo?

 - Is anyone using the .stl files to print physical badges? Is anyone communicating with vendors regarding printing badges?

I will begin creating forms and putting together a project in Pagure over the next few days. I will initially set up members of the sysadmin-badges FAS group with commit access to the testing repo. If you are

interested in testing or have other suggestions, please let me know.

Happy Badging!

-Zach

#aikidouke

- fedora infra/badges