#9 Different ticket repos for different regions?
Opened 7 years ago by ankursinha. Modified 5 years ago

Should we have one Pagure repo to service tickets for all regions, or should we have a few that manage tickets for different regions? This would make it more granular, and we could have small teams of people managing their regions. This will also enable us to link up better with the Ambassadors that are organised region wise, and their budgets, and so on.

  • NA
  • SA
  • APAC (more break down - India/SE Asia etc.?)
  • EMEA (more break down - N/S/E/W)
  • LATAM (?)
    ...

IMHO, I think we have to wait the conclusion of the ticket #7
to see how many contributors we have to decide if we break down the regions or not.

I think the current system we have on Trac works well enough - one repo with some sort of tag to identify the region. Users have, in the past, modified the region tag (whether intentionally or accidentally). If we did go down the route of separate repos, depending on how the tickets were added to those repos we could end up with tickets getting stuck with the wrong team, and therefore perhaps not getting fulfilled.

Depending on how #14 goes, it could be possible to do away with the region tag altogether for metrics purposes. As long as countries are recorded, these can be grouped into regions afterwards.

Any objections to Free-Media/Tickets/{Region} OR Free-Media/{NA,EMEA,APAC,LATAM,APAC-India}-Requests ??

Thoughts??

I think good to have centralized ticketing system for it, since if we split it into region we might need more people to track it.

Login to comment on this ticket.

Metadata