|
From: Köditz, M. <Mar...@it...> - 2016-12-19 10:08:36
|
Though I'm a programmer, I find it very hard to use CVS. I had some problems using CVS when Helen committed some changes. I feel more comfortable using git. >> SourceForge itself considers CVS deprecated, and having the repository >> on GitHub might increase visibility and will likely lower the barrier >> for contribution. As mentioned earlier, CVS is considered as deprecated and I had problems finding an adequate client. Well this is not really a hurdle, but it's much easier to get modern git clients. We are trying to win new contributors, so we should make the entry as easy as possible. > No objections here, but does anybody have any experience with this kind > of migration? (Preferably including history.) I've already migrated a CVS project to git (not in such a dimension). But I think it is possible and if wished I can do some research on this. And Mark has some experiences too. Also I don't think we have to use git sub modules (it is really a nightmare). We could use an own git repo for the manual. I would also offer myself to edit the docbuilders guide in that case (review by Helen). What do you think? Regards Martin |