Hello Peter, that's cool. At Akretion we are also mirroring the main official repos on Github. In fact we are even mirroring a few more branches like OCB ones and RS-OCB ones (partner_id sematic not permuted): https://github.com/akretion
This can be used for deploy or continuous integration testing (like on Travis-CI) while Launchpad/bzr is so slow that it's prohibitive in comparison. For instance, I used that for continuous integration for OOOR, the Ruby OpenERP connector (BTW stay tuned v2.x is around the corner): https://github.com/akretion/ooor https://github.com/akretion/ooor/blob/master/.travis.yml https://travis-ci.org/akretion/ooor/builds I even want to offer to the OCB community automatic continuous integration testing for all its repos. Notice that currently our repos aren't compatible apparently, that would be cool to work hand in hand instead and make a consistent thing. Eventually we team up on that to avoid double working. What do you think? You can skype me at raphael.valyi if you like. A cool thing we would need for these git mirrors is to be able to develop right on Github and be able to push back to Launchpad where the legacy stuff is being made by OpenERP SA. I don't know what you are using, but we are using https://github.com/termie/git-bzr-ng and apparently that is possible to do that, may be if we include the maps in the repo. Are you using that? What do you think? Some of the things to expect from developing on Github (even if we could push the legacy back to LP) are IMHO: 1. I really think Github patform is vastly more productive and attractive for contributors because it really captures the social dimension of open source 2. git is fast, while bzr is nearly not usable for some use case: like already had a bzr customer branch for addons and try to merge head into it like 3 months later? How agile is that? 2 hours? Not really hot-deploy friendly... 3. git subree does work, that means breaking down a monolithic branch of modules into interdependently versionned submodules actually work seamlessly, this can be essential for being modular and avoid the pitfalls such as we had with the extra-addons repo and even that we have nearly now with the official addons-repo where module enter and exist and change beyond expectation during "stable releases" because things aren't layered properly with appropriate and multi-scale development cycle paces. 4. its is integrated with more standard and productive tools 5. git makes it easy to maintain tracking branches such as OCB or RS-OCB 6. git/github makes it easy to navigate into the src tree and compare two versions/branches, efficiently filter the translation from the diff etc... 7. github makes it easier to highlight the contributors, hence encouraging contributions, something that is lacking in OpenERP in general compared to the ambition of the project. 8. git makes it easy to cherrypick the thing that will work for you instead of living in the current hypocrisy that their would be an official version but the only people that put things in production patch it really heavily, even as part as the OPW thing that isn't systematically merged back (I'm not criticizing that, just saying cherrypicking with git would make that way more effective). As a side note, I would like to mention that after we successfully started mirroring all our dependencies (including the official ones), we will now be developping the Brazilian localization right on Github and mirror to LP instead. We will use that as a test case to see if contributions to the project increase and will report back here. Best regards. -- Raphaël Valyi Founder and consultant http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi> +55 21 2516 2954 www.akretion.com On Thu, Jun 13, 2013 at 8:55 AM, Peter Niederlag <[email protected]> wrote: > Hello, > > This mail goes to anyone interested to work with the sources of openerp > via git instead of bzr. I maintain the following git repos on github: > > https://github.com/t3dev/openerp-server > https://github.com/t3dev/openerp-web > https://github.com/t3dev/openerp-addons > > These (git) repositories reflect the content and (full) history of the > corresponding official bzr repositories (including tags / no empty > directories by design). They are currently updated via cron every two hour. > > Sincere Greets, > Peter Niederlag > > P.S.: Big thx goes to https://github.com/felipec who recently has > greatly improved the support to use bzr as foreign branches inside git. > -- > Peter Niederlag * Ehlentruper Weg 70 * 33604 Bielefeld * > http://www.niekom.de * TYPO3 und EDV Dienstleistungen * > > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-community > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
