Dear All, I would be supportive of a clean break from Trac -- and it's clear that there is a constituency in the community that would prefer that path. I think it is also clear that we are suggesting that outcome in the near future anyways, but potentially not an immediate retirement of Trac. While it may introduce a bit of confusion, my opinion is that confusion may be worth while to keep all community members engaged and be as inclusive as possible. At the end of the day, those of us that prefer using github need to demonstrate how to evolve the standard in github so those without experience in this environment can learn and join the :shipit: tribe. (I use the [squirrel](http://excid3.com/blog/finishing-is-all-that-matters) as an example of how foreign some github traditions and mechanisms really are.)
Is there any strong disagreement to this line of argument? My thinking is that we would continue to allow use of Trac until usage has dropped to near nill or maintenance of Trac is not worth the effort. Putting a timeline on this may not be worth the energy as it should happen naturally if this switch to github really is the thing to do. I also think it would be a great idea to migrate the Trac history to a block of github issues. While the numbering would reset, we could embed the original Trac URLs in the issues for continuity. I think this would naturally occur at the time that we retire our use of Trac. Best, Dave p.s. I would like to remind everyone that while we have moved some of our discourse to github, I think we should attempt to maintain the traditions of CF in our correspondence. Each of these comments fires off an email to the group and, as such, should be thoughtful and worthy of people's attention if at all possible. -- 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-400711387
