Re: [dxwg] Should we split the DXWG GitHub Repo? (#1216)

I admit it might be handy to have separate repositories. However,  I share some of the concerns related to the splitting of the repository. I do not know if the advantages balance the efforts,  as  I do not understand how demanding and problematic the repository splitting might turn out.

Perhaps, the only way to mitigate the concerns is to give a try. We could think of making a test in the small. We can start cloning the repo and transforming it into a repository only for one of our documents.

Is there a member who can volunteer on this  "experiment in the small"? Which of the documents do we want to try on?

> I'm still a bit concerned about splitting / cloning the repo, for the cons outlined by @riccardoAlbertoni , although I recognise that having separate repos would help reduce the "noise".
> 
> A clarification: in case we clone the repo, what will happen with the references we have across issues? The link will point to the issue in the original repo or in the new one?


-- 
GitHub Notification of comment by riccardoAlbertoni
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1216#issuecomment-584282339 using your GitHub account

Received on Monday, 10 February 2020 18:32:08 UTC