On Thu, Jun 28, 2018 at 5:50 AM, JonathanGregory <[email protected]> wrote:
> I agree with @rhattersley <https://github.com/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. > +1 > I don't think we should oblige everyone to switch immediately to GitHub > and stop using Trac, though we can encourage it. > yes, we should -- having the same thing managed two ways is a pain in teh #^$*. I know change can be hard, but semi-change / lack of clarity, confusing mess is harder. And it's really not that different for the common use cases! > The meeting last week was certainly in favor of a quick move, but the > people at that meeting may not be an entirely representative sample of the > whole community of contributors to CF. I guess it was a more technically > minded set than the average. > maybe so -- but TRAC isn't exactly a model of usability :-) gitHub (at least for issue management) isn't any more technical that TRAC, and I think it's more usable, not less. So it's more a old dog / new tricks issue. -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [email protected] -- 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-401089534
