Closed jar398 closed 3 years ago
Thanks @jar398 . No, you are not. Will put this on the agenda for our next meeting.
Thanks. If you decide to go this way, this page on moving issues between repositories might be helpful
Thanks @jar398 . I did not know you could do that.
On request of @nielsklazenga I have created https://github.com/tdwg/tcs2 for which @nielsklazenga is the admin.
I hope this helps and think this issue can be closed.
Thanks @timrobertson100 , yes, definitely helps.
I always get confused in any context about whether we're talking about TNC business, which I think admits relatively freewheeling technical and policy discussions, and TCS2, which is a very strictly delimited project. (I was guilty of this just this past week.) E.g. we have a 'use-cases' directory but some use cases are relevant to TCS generally but some (maybe, I'm not sure) are specific to TCS2. Similarly we have issues for TNC only some of which are TCS2 specific.
Not only would a separate repository make it clear whether any file or issue was about TCS2 or not, it would make it easier to start or work on parallel TNC efforts unrelated to TCS2.
I find myself wishing that TCS2 had its own repository. Am I the only one who feels this way?