Planning badges wiki/trac transition to Pagure

[Zach Villers]

Greetings Badgers!

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;
https://fedoramagazine.org/pagure-diy-git-project-hosting/

Moving projects from fedorahosted to pagure would help us modernize our
infrastrcture. See email from Nirik:
https://lists.fedoraproject.org/archives/list/[e-mail]...

I need input (suggestions, corrections, constructive shouting) from
people that use badges Trac or Wiki. Can you please answer a couple of
questions?

- 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?

- Is anyone using the .stl files to print physical badges? Is anyone
   communicating with vendors regarding printing badges? 
   [e-mail] 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?

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
    - Proposed
    - Triaged (Does it have artwork concept + Description)
    - Artwork
    - NEW tag for creating .stl file [Proposed]
    - Definition
    - Ready (for deployment)
 - Bug Issue ---> Tagged Issue
    - New
    - Triaged
    - Resolved
 - Proposed request for .stl file after creation
    - New
    - Resolved
 - Badges Wiki ---> Pagure Docs Repo
 - Groups in Pagure for badges
    - badges-designers
    - badges-design-review
    - badges-admin

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 ]

[Design-team] Planning badges wiki/trac transition to Pagure

[Marie Nordin]

Hiya,

Their is a Fedora Design FAD coming up this next weekend- we can discuss
and put any thoughts or concerns out there shortly. I don't personally use
Pagure, so I am wondering how this will change the workflow for badges.
Currently I only use the trac site to work on badges. Perhaps I will need
to transition :)

Thanks!

On Wednesday, July 20, 2016, Zach Villers  wrote:
> Greetings Badgers!
>
> 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;
> https://fedoramagazine.org/pagure-diy-git-project-hosting/
>
> Moving projects from fedorahosted to pagure would help us modernize our
> infrastrcture. See email from Nirik:
>
> https://lists.fedoraproject.org/archives/list/[e-mail]...
>
> I need input (suggestions, corrections, constructive shouting) from
> people that use badges Trac or Wiki. Can you please answer a couple of
> questions?
>
> 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?
>
> Is anyone using the .stl files to print physical badges? Is anyone
> communicating with vendors regarding printing badges?
> [e-mail] javascript:; 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?
>
> 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
> Proposed
> Triaged (Does it have artwork concept + Description)
> Artwork
> NEW tag for creating .stl file [Proposed]
> Definition
> Ready (for deployment)
> Bug Issue ---> Tagged Issue
> New
> Triaged
> Resolved
> Proposed request for .stl file after creation
> New
> Resolved
> Badges Wiki ---> Pagure Docs Repo
> Groups in Pagure for badges
> badges-designers
> badges-design-review
> badges-admin
>
> 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 ]
> _______________________________________________
> design-team mailing list
> [e-mail] javascript:;
>
> https://lists.fedoraproject.org/admin/lists/[e-mail]....