Planning for post-WG life: what do we do with CSVW Github esp issue tracker?

Ivan,

Are there any conventions for life-after-WG regarding Github presence, e.g.
issue trackers or test case repositories? I am wondering what we can do for
issue tracking in the new Community Group(*). Should it have its own Github
repo (maybe with a fork of the final state of the WG at closure) so that
its issues can be kept separate? That way any issues branches made
informally within the CG could eventually give rise to pull requests (in
2-3 years time or whatever) should a full WG ever be reactivated. Just
thinking out loud, and glad to hear of any useful precedents we can
follow...

Dan


* http://www.w3.org/community/csvw/