On 01/18/2017 05:02 PM, Vincent Gerris wrote: > I guess you didn't like redmine, gitlab, mattermost, the Atlassian > stack, or some others out there :)? We wanted something open source, non-propriety, similar trac functionality, trac ticket migration tools, and does not require Pull Requests. There are some other minor factors that went into this decision (internal tools, etc). Everyone has their own preferences, so not everyone is going to like Pagure. However, it's very similar to how trac worked. Which means there is a very small learning curve. We also have a great relationship with the Pagure dev team(we are contributors as well), so it will be "easy" to add new features and fix bugs in the future. Regards, Mark > It looks neat. > So the question is why this and not anything else :)? > Maybe not the question you expected, but I am just curious. > > Greetings, > Vincent > > > On Wed, Jan 18, 2017 at 3:56 PM, Mark Reynolds <mareynol@xxxxxxxxxx> wrote: >> On February 28th the fedorahosted trac ticket system/repo is being >> decommissioned, and we will be moving to Pagure (https://pagure.io/) as our >> ticketing system and source code repository. The Pagure work flow is very >> similar to trac, and we will be adding a wiki doc on how to use it once we >> get closer to doing our migration to Pagure. We are currently planning on >> doing the migration in the middle of February. >> >> As for the trac ticket migration there is one issue. All cc'ed users will >> be lost. If you are the assignee or the reporter you will still get >> notifications, but you won't if you were only in the cc list of a ticket. >> Also, the pagure tickets (Issues) that are migrated will continue to use the >> same trac ticket IDs. So you can still easily track/follow tickets you were >> previously interested in. >> >> If you have previously filed tickets, or you might want to, please goto the >> pagure web site https://pagure.io/ and simply log in using for FAS >> credentials. This will automatically add you to the Pagure system. Please >> do this sooner than later so you don't experience any disruptions with >> notifications. >> >> We will keep you posted as we get closer to the migration. Feel free to >> email me with any questions. >> >> Regards, >> Mark >> >> _______________________________________________ >> 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx >> > _______________________________________________ > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
