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. -- Matthieu
