Dear all I agree with @rhattersley that it would make sense to copy the trac tickets to a separate cf-conventions GitHub repository, with their original numbers, in order to keep them for posterity. I don't think we should oblige everyone to switch immediately to GitHub and stop using Trac, though we can encourage it. The meeting last week was certainly in favour of a quick move, but the people at that meeting may not be an entirely representive sample of the whole community of contributors to CF. I guess it was a more technically minded set than the average.
We currently have three main repositories: the website, the conventions and the conformance document. I suggest that, for simplicity and unless it becomes inadequate, we could deal with governance issues in the website repository, because the gobernance rules are part of the website. This ticket ought to be in that repository, not this one, if you agree with this idea. I agree with @erget that it would make sense to merge the conformance and conventions repositories, since they have to be updated together. The data model will also belong with them. I don't know how the mechanism works for sending these postings on issue to the CF email list. If this system can filter by label, we could follow what @erget and @rhattersley suggest to mark some of them as not to be distributed. Best wishes Jonathan -- 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-401023162
