Hi, I am writing here to get some feedback about migration Twisted Trac Ticket to GitHub Issues.
In short, try to spend more time doing Twisted development and less time developing custom tools and doing sysadmin work. The main reason for the migration is that we don't have enough people/time to manage the Trac instance or improve the dev tools around Trac. With GitHub issues it should be easier to reuse tools created by others for GitHub. Also, I think that having Pull Requests an GitHub with the GitHub own review queue/report and a separate set of report in Trac is extra "office" work We are already doing Trac authentication via Github. Anyone over here who is against migrating the Twisted Trac tickets to GitHub ? I see Trac has about 10300 tickets and GitHub PR is now at 1672 . We can migrate with keeping the same ID for the majority of the tickets. With the migration the original author of a ticket/comment is lost. This is a security feature in GitHub. Also, it's not trivial to get all the Trac accounts mapped to GitHub accounts. We can keep the existing Trac in read-only mode for some time. And it can (and will be) linked from Github Issues For the attachments, they can be hosted on a static HTTP site like `trac-attachments.twisted.org` (which can be hosted by Github pages) and linked from GitHub Issues. Components, Priority, and keywords can be converted to GitHub Issue labels. "Owned by" can be converted to GitHub issue assignee ... if we have a mapping :) The milestones can be converted to GitHub Issue milestones "Branch" trac ticket custom field can be used to detect a link to a GitHub PR ---------- Until recently the Twisted Trac instance was running on Ubuntu 16.04 ... and I don't know how often it is updated. Now, Trac is hosted on an Azure VM with Ubuntu 20.04... but we don't have time to look after it. --------- If the majority of Twisted devs agree to migrate to GitHub we can look into the execution details. My company has recently migrated from Trac to GitHub and I can ask my colleague to help with the Twisted migration. PS: later we can also look at migrating the Trac Wiki to GitHub Wiki PS: there is also planning to have a simpe (static) presentation site for Twisted https://github.com/twisted/twisted.github.io/pull/6 .. to replace the current site that is hosted via Trac Wiki with heavy customization Regards -- Adi Roiban _______________________________________________ Twisted mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/twisted.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/6LCALRSVC6DRSWWRWCAMENKDYOX2MS7N/ Code of Conduct: https://twisted.org/conduct
