As a general observation on the transition from Trac to Github, I would encourage embracing existing GitHub idioms to take advantage of the resulting simplicity. For example:
re: porting Trac issues to GitHub, I would recommend that you copy them to a separate repo dedicated to being an archive. That way the issue numbers can easily be preserved. If there's a need for new native GitHub issues to refer back to the Trac content, cross-repo links are still very easy, e.g. cf-convention/test-trac-convert#1. re: conversations on "practical" vs "science" topis, I would recommend keeping all your issues and pull requests in the repo that they affect. Workflows across multiple repos are more complicated and error prone, and much less likely to receive any attention from GitHub. @erget's suggestion to take advantage of issue labels is a more natural fit. The use of issue labels is very common on GitHub. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/130#issuecomment-400936458
