This is a great idea. I think a distributed revision control system would have advantages over a single central repository. The last time I investigated the available options it seemed that Bazaar had some advantages over Git and Mercurial, but I don't remember the details (and the features of the various systems may have changed since I last compared them). Both Launchpad and SourceForge support Bazaar. I like the idea of "drive-by" contributions, multiple branches that can be scrutinized prior to merging with the main branch, and plentiful documentation that is offered by Launchpad. Tobias, what are you thoughts now that you have been using Launchpad for a while? -- Ken <div class="gmail_quote">2010/9/21 Kaarel Kaljurand <<a href="mailto:kaljurand@gmail.com">kaljurand@gmail.com</a>> <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Hi, 2010/9/21 Jean-Marc Vanel <<a href="mailto:jeanmarc.vanel@gmail.com">jeanmarc.vanel@gmail.com</a>>: <div class="im">> > After talking with Norbert at CNL 2010, it seems that it is time to setup a > new source repository for the ACE prolog core code. </div>I think it's a good idea. It could contain: * APE * Attempto Java Packages * Regression tests for APE (currently not public) * APE API usage examples (currently not public) * Documentation (currently available only on the Attempto website) <div class="im"> > While migrating to a new repository, it's important to preserve history of > changes (changes logs), because this is the memory of the project. This will > be an important criterium to choose a host for the new repository. We need > to import the whole repository changes database. I have to check where this > is possible. For this, I need to know which tool the current repository uses > (CVS, Subversion, git, Bazaar, Mercury, ...). </div>APE currently uses Subversion. The history goes back to July 2006, i.e. not all the way back to 1995 when the Attempto project started. ;) I'm not sure that keeping all the history is that useful, although it would be nice. The history might actually contain sensitive info that we would not like to make public. I've been so far happy with Subversion and Google Code, but I'm not familiar with other source control systems and hosts. With a larger set of developers we might profit from fancier branching/merging support offered by Git, Mercurial and other similar systems. Greetings from Xi'an, Kaarel _______________________________________________ attempto mailing list <a href="mailto:attempto@lists.ifi.uzh.ch">attempto@lists.ifi.uzh.ch</a> <a href="https://lists.ifi.uzh.ch/listinfo/attempto" target="_blank">https://lists.ifi.uzh.ch/listinfo/attempto</a> </blockquote></div>