On 07/20/2016 05:14 PM, Zach Villers wrote:
Infrastructure would like to create a plan to move the Badges wiki and
trac instance to Pagure. Pagure is our own git repository service for
the web. Any Fedora contributor can create a repository at Pagure.io -
more info in FedoraMag;
Moving projects from fedorahosted to pagure would help us modernize our
infrastrcture. See email from Nirik:
Hey Zach - thanks for starting this conversation! I'll leave some of my
own personal thoughts all below.
I need input (suggestions, corrections, constructive shouting) from
people that use badges Trac or Wiki. Can you please answer a couple of
- Any concerns with using Pagure?
- Are there any use cases where opening issues on Pagure would not be
a functional replacement for Trac tickets?
- 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?
For all tickets in the Badges Trac, history and the attachments on those
tickets are a massive part of the workflow. All the tickets are linked
in specific badges on the front-end at badges.fp.o. Having the history
of importing *all* tickets with their attachments would be vitally
Attachments specifically too, as this is the best place to look for
exported images and SVGs of badges, either completed, in progress, or
temporarily paused. Not all the assets in the Badges Trac make it to
badges.git, and I can think of a few times where having that history
present was useful.
On the note of importing history, we would need to have a fairly large
effort on updating the "ticket criteria" field in Tahrir. There is no
front-end for this unfortunately, if I recall, so this would involve an
Infrastructure team member making manual edits to the database for Tahrir.
- Is anyone using the .stl files to print physical badges? Is
communicating with vendors regarding printing badges?
sayan(a)fedoraproject.org suggested that instead of creating an
.stl file for every badge, creation of the .stl file could be
requested with a tagged issue. (This would help us manage space and
time requirements.) Is anyone opposed?
We discussed this one in channel, but I'll put my thoughts here on the
list too. As far as STLs go, there is no current "central" or directed
effort into using those, or at least as not as I am aware.
As an Ambassador, I've used them before to get badges printed at an
event where a 3D printer was available. But that was what I feel like
was a one-off case, and it could probably be communicated about how to
use the script in bin/ on a case-by-case basis for making the STL too.
However, I do see the use in having some STLs available, if someone
requests them. Tahrir also supports notating badges when they have an
STL available, so it might be useful to figure out how to do that for
the badges that do have STLs available.
As an example, see this one with the options: "View badge as: STL, JSON,
I am +1 for only generating them on request.
In terms of how the workflows would transition, I am thinking;
- Trac Tickets ---> Pagure Ticket/Issue Templates
- Suggest a Badge Issue
- Report A bug Issue
- New Badge Workflow on Trac ---> Adding Tags to Pagure Issue
- Triaged (Does it have artwork concept + Description)
- NEW tag for creating .stl file [Proposed]
- Ready (for deployment)
- Bug Issue ---> Tagged Issue
- Proposed request for .stl file after creation
- Badges Wiki ---> Pagure Docs Repo
- Groups in Pagure for 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
[ fedora infra/badges ]
Hope this info helps!
Justin W. Flory