Matthieu Moy <[EMAIL PROTECTED]> writes: > Stefan Reichör <[EMAIL PROTECTED]> writes: > >> * The hardest, but perhaps best way would be to define that common >> interface and add support for the different revision control systems >> from that base. > > Would be nice, but I won't have time to do that. > > I'll have some free time from October to December, but I'm not sure > how much time I'll invest in free software in 2006. Probably not far > from zero. > > > Next option: > > * Create an initially empty dvc/ directory in the Xtla project, with > an initially empty dvc.el file. Then, consider the new Xtla as "An > interface to tla and Bazaar, built on top of a common DVC layer -- > except the code refactoring hasn't begun yet". Then, move code from > Xtla to dvc when we think it's generic enough. That's what we did > with xtla-core.el. This forces us to do a bit of code review as we > move the code. > > If enough person have time and motivation to do so, that's probably > the best option. Can give good results in the short term, and goes in > the right direction too.
Quoting me again: >> * The hackish (and more fun way) would be to add xtla-bzr, >> xtla-mercurial,... and try to refactor the existing Xtla and build a >> common base during that process. >> >> I would prefer that way, because it is more fun, because it takes less >> time to get something working. The drawback is here, that we will have >> code duplication and a system that is not designed from ground up. I think, your Next option and my hackish way are essentially the same. So lets go that road. My time budget is also limited. But it is fun to hack a few new functions now and then. Stefan.
