For me splitting the repository depends on how to proceed the checkout of all new repositories and externals. At the moment I have 4 repositories for developing (2 trunk 2 rewrite) and two (1/1) for committing approved changes and two (1/1) on a different machine for running the bot in autonomous mode. I do not like virual environment for developing, i didn't get it working in past. I would prefer splitting the framework trunk and rewrite and perhaps in next future a new py3.0 framework based on the rewrite branch. Next I would split i18n from these framework forks as they must be the same; now trunk use it as external from rewrite. In a same way the family files could be separated when the framework is able to handle remaining different setting (e.g. namespaces, ssl etc.) Also I have the idea to split scripts from the framework and enable running the same script with different frameworks (look at noreferences.py: only the imports are different). This means most bots must become a library and all interfaces must be the same, independent from py release and api/screen scrapping modules. Happy new year xqt ----- Original Nachricht ---- Von: Merlijn van Deen <valhallasw(a)arctus.nl> An: Pywikipedia discussion list <pywikipedia-l(a)lists.wikimedia.org>rg>, yuriastrakhan(a)gmail.com Datum: 27.12.2012 20:09 Betreff: Re: [Pywikipedia-l] git migration: repository structure