Re: [Openerp-community-reviewer] [Openerp-community] OCA LP Project migration to Github
Dear community, Here is a Trello board to help us organize tasks of each of us for this migration : https://trello.com/b/JFEZglXl/moving-oca-to-github I already started. He's public to read, only members can write/create. I currently added/invited some of you to it, please just ask if you consider investing time in that task. I suggest we use this to organize our-self. It'll be much more eaiser than a mailing list thread ;) Though, If some point required your approbation, I'll post something here. Best regards, Joël On Wed, May 21, 2014 at 10:07 AM, Ana Juaristi ajuaris...@gmail.com wrote: Hi Raphael. Having on github a readonly mirror of what there is on LP for 7.0 and 6.1 it would be great I think. Just because people could go on mantaining old versions in LP as they did before but there is a history progression directly on Github Great idea. my vote: +1 :) 2014-05-20 12:41 GMT+02:00 Raphael Valyi rva...@gmail.com: Hello Joël, thank you so much for the work. I agree on all the points you made. If you want you can pass me the list of users to add to the teams, I can script something to do it or do it manually else. I can also push the converted LP to git branches (using git bzr helper) if you like as I'm used to do that (but it's not too complex either, just proposing my help). We push the head of each v7 branch, right? Is there any need to branch a v8 branch on Launchpad before doing that to stay as a reference (so we can analyse on LP how it was when it was separated? Also, sorry if I missed this point but: OK we will push the 8 series to Github. But will we also push a 7.0 serie to Github, even just as readonly (by discipline). I think that would be very useful to mirror 7.0 and even 6.1 to Github so that we can later merge part of these branches to the v8 branch. So such mirroring is not a 1 time job, it should be a cron. I can do it on our server like we did for the previous git synch if you want (it's quite easy). What do you think? The logo looks cool. Long life to it! -- Raphaël Valyi Founder and consultant http://twitter.com/rvalyi http://twitter.com/#!/rvalyi +55 21 3942-2434 www.akretion.com On Tue, May 20, 2014 at 7:18 AM, Joël Grand-Guillaume joel.grandguilla...@camptocamp.com wrote: Dear all, Thanks a lot for all your feedback here. So, to summarize opinions here: * Version = 7.0 keep Launchpad as a reference. We eventually setup a replication in github (lp - gituhub) in a couple of weeks * We do use one organization on github for the whole community work * We create one team on github per area of expertize (so that means like it is now on LP). I tried to see if we can lower the number of team, but wasn't able to decide how to merge them. Any though here, the list is here :https://launchpad.net/~openerp-community-reviewer/+participation ? * Every LP project become a repository on github. The branches hosted under the community reviewer team (bazaar extractor, etc..) will have a new repo called something like community toolkit. * Branches represent the serie (like OpenERP did with odoo) The only disadvantage I see here is that we cannot include a team in a team on github. So that means, we'll no longer have a community reviewer team that is part of all other team. We'll need to add in every team the right people, but apart from a bit of administrative work, it'll be ok. As Nhomar pointed out, I already took the time to create this organization on github : https://github.com/OdooCommunity It was a first test from me, but if you agree, I'll spend some time to create the team and repos. I suggest also that I make an OCA-board team with the administration right on the organization. So current OCA board member will be able to administrate the organization as well. As some of you already notice, I also took the liberty to make a new logo, keeping the ant ;) Hope it please you all ! Regards, Joël On Tue, May 20, 2014 at 9:16 AM, Alejandro Catalina alecat...@gmail.com wrote: Hi there, I also agree with the last proposal, one github organization and several repositories, one for each launchpad project. So let's move on. I think the best way to move all those projects and branches is to divide the work between all of us. We could make a list of all launchpad URL involved and begin the job. What do you think about? 2014-05-20 8:33 GMT+02:00 Quentin THEURET q...@tempo-consulting.fr: On 16/05/14 18:43, Maxime Chambreuil wrote: We agree with Stefan here. I'm also agree with Stefan point of view. Regards, -- Quentin THEURET TeMPO Consulting 20, Avenue de la paix 67000 Strasbourg France http://www.tempo-consulting.fr Tel : +33 3 88 56 82 18 Fax : +33 3 88 56 46 64 ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe :
Re: [Openerp-community-reviewer] [Openerp-community] OCA LP Project migration to Github
Dear all, Thanks a lot for all your feedback here. So, to summarize opinions here: * Version = 7.0 keep Launchpad as a reference. We eventually setup a replication in github (lp - gituhub) in a couple of weeks * We do use one organization on github for the whole community work * We create one team on github per area of expertize (so that means like it is now on LP). I tried to see if we can lower the number of team, but wasn't able to decide how to merge them. Any though here, the list is here : https://launchpad.net/~openerp-community-reviewer/+participation ? * Every LP project become a repository on github. The branches hosted under the community reviewer team (bazaar extractor, etc..) will have a new repo called something like community toolkit. * Branches represent the serie (like OpenERP did with odoo) The only disadvantage I see here is that we cannot include a team in a team on github. So that means, we'll no longer have a community reviewer team that is part of all other team. We'll need to add in every team the right people, but apart from a bit of administrative work, it'll be ok. As Nhomar pointed out, I already took the time to create this organization on github : https://github.com/OdooCommunity It was a first test from me, but if you agree, I'll spend some time to create the team and repos. I suggest also that I make an OCA-board team with the administration right on the organization. So current OCA board member will be able to administrate the organization as well. As some of you already notice, I also took the liberty to make a new logo, keeping the ant ;) Hope it please you all ! Regards, Joël On Tue, May 20, 2014 at 9:16 AM, Alejandro Catalina alecat...@gmail.comwrote: Hi there, I also agree with the last proposal, one github organization and several repositories, one for each launchpad project. So let's move on. I think the best way to move all those projects and branches is to divide the work between all of us. We could make a list of all launchpad URL involved and begin the job. What do you think about? 2014-05-20 8:33 GMT+02:00 Quentin THEURET q...@tempo-consulting.fr: On 16/05/14 18:43, Maxime Chambreuil wrote: We agree with Stefan here. I'm also agree with Stefan point of view. Regards, -- Quentin THEURET TeMPO Consulting 20, Avenue de la paix 67000 Strasbourg France http://www.tempo-consulting.fr Tel : +33 3 88 56 82 18 Fax : +33 3 88 56 46 64 ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Joël Grand-Guillaume* Division Manager Business Solutions +41 21 619 10 28 www.camptocamp.com -- Mailing list: https://launchpad.net/~openerp-community-reviewer Post to : openerp-community-reviewer@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community-reviewer More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community-reviewer] [Openerp-community] OCA LP Project migration to Github
Hello Joël, thank you so much for the work. I agree on all the points you made. If you want you can pass me the list of users to add to the teams, I can script something to do it or do it manually else. I can also push the converted LP to git branches (using git bzr helper) if you like as I'm used to do that (but it's not too complex either, just proposing my help). We push the head of each v7 branch, right? Is there any need to branch a v8 branch on Launchpad before doing that to stay as a reference (so we can analyse on LP how it was when it was separated? Also, sorry if I missed this point but: OK we will push the 8 series to Github. But will we also push a 7.0 serie to Github, even just as readonly (by discipline). I think that would be very useful to mirror 7.0 and even 6.1 to Github so that we can later merge part of these branches to the v8 branch. So such mirroring is not a 1 time job, it should be a cron. I can do it on our server like we did for the previous git synch if you want (it's quite easy). What do you think? The logo looks cool. Long life to it! -- Raphaël Valyi Founder and consultant http://twitter.com/rvalyi http://twitter.com/#!/rvalyi +55 21 3942-2434 www.akretion.com On Tue, May 20, 2014 at 7:18 AM, Joël Grand-Guillaume joel.grandguilla...@camptocamp.com wrote: Dear all, Thanks a lot for all your feedback here. So, to summarize opinions here: * Version = 7.0 keep Launchpad as a reference. We eventually setup a replication in github (lp - gituhub) in a couple of weeks * We do use one organization on github for the whole community work * We create one team on github per area of expertize (so that means like it is now on LP). I tried to see if we can lower the number of team, but wasn't able to decide how to merge them. Any though here, the list is here : https://launchpad.net/~openerp-community-reviewer/+participation ? * Every LP project become a repository on github. The branches hosted under the community reviewer team (bazaar extractor, etc..) will have a new repo called something like community toolkit. * Branches represent the serie (like OpenERP did with odoo) The only disadvantage I see here is that we cannot include a team in a team on github. So that means, we'll no longer have a community reviewer team that is part of all other team. We'll need to add in every team the right people, but apart from a bit of administrative work, it'll be ok. As Nhomar pointed out, I already took the time to create this organization on github : https://github.com/OdooCommunity It was a first test from me, but if you agree, I'll spend some time to create the team and repos. I suggest also that I make an OCA-board team with the administration right on the organization. So current OCA board member will be able to administrate the organization as well. As some of you already notice, I also took the liberty to make a new logo, keeping the ant ;) Hope it please you all ! Regards, Joël On Tue, May 20, 2014 at 9:16 AM, Alejandro Catalina alecat...@gmail.comwrote: Hi there, I also agree with the last proposal, one github organization and several repositories, one for each launchpad project. So let's move on. I think the best way to move all those projects and branches is to divide the work between all of us. We could make a list of all launchpad URL involved and begin the job. What do you think about? 2014-05-20 8:33 GMT+02:00 Quentin THEURET q...@tempo-consulting.fr: On 16/05/14 18:43, Maxime Chambreuil wrote: We agree with Stefan here. I'm also agree with Stefan point of view. Regards, -- Quentin THEURET TeMPO Consulting 20, Avenue de la paix 67000 Strasbourg France http://www.tempo-consulting.fr Tel : +33 3 88 56 82 18 Fax : +33 3 88 56 46 64 ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Joël Grand-Guillaume* Division Manager Business Solutions +41 21 619 10 28 www.camptocamp.com ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~openerp-community-reviewer Post to : openerp-community-reviewer@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community-reviewer More help
Re: [Openerp-community-reviewer] [Openerp-community] OCA LP Project migration to Github
Hello, Thanks for the work. I'm OK for most of the point except for the branch/lp replication. We should not mix the tools, it will be chaos. It will not be wise to have a 7.0 series on launchpad and on github, people will work on both at the same time. If we have a 7.0 branch on github it means 7.0 series should be closed on LP. Also having code on LP and Github will complexify forward/backward fix merging. I'm in favor to have all repo on github (or LP) only. Regards Nicolas 2014-05-20 12:18 GMT+02:00 Joël Grand-Guillaume joel.grandguilla...@camptocamp.com: Dear all, Thanks a lot for all your feedback here. So, to summarize opinions here: * Version = 7.0 keep Launchpad as a reference. We eventually setup a replication in github (lp - gituhub) in a couple of weeks * We do use one organization on github for the whole community work * We create one team on github per area of expertize (so that means like it is now on LP). I tried to see if we can lower the number of team, but wasn't able to decide how to merge them. Any though here, the list is here : https://launchpad.net/~openerp-community-reviewer/+participation ? * Every LP project become a repository on github. The branches hosted under the community reviewer team (bazaar extractor, etc..) will have a new repo called something like community toolkit. * Branches represent the serie (like OpenERP did with odoo) The only disadvantage I see here is that we cannot include a team in a team on github. So that means, we'll no longer have a community reviewer team that is part of all other team. We'll need to add in every team the right people, but apart from a bit of administrative work, it'll be ok. As Nhomar pointed out, I already took the time to create this organization on github : https://github.com/OdooCommunity It was a first test from me, but if you agree, I'll spend some time to create the team and repos. I suggest also that I make an OCA-board team with the administration right on the organization. So current OCA board member will be able to administrate the organization as well. As some of you already notice, I also took the liberty to make a new logo, keeping the ant ;) Hope it please you all ! Regards, Joël On Tue, May 20, 2014 at 9:16 AM, Alejandro Catalina alecat...@gmail.comwrote: Hi there, I also agree with the last proposal, one github organization and several repositories, one for each launchpad project. So let's move on. I think the best way to move all those projects and branches is to divide the work between all of us. We could make a list of all launchpad URL involved and begin the job. What do you think about? 2014-05-20 8:33 GMT+02:00 Quentin THEURET q...@tempo-consulting.fr: On 16/05/14 18:43, Maxime Chambreuil wrote: We agree with Stefan here. I'm also agree with Stefan point of view. Regards, -- Quentin THEURET TeMPO Consulting 20, Avenue de la paix 67000 Strasbourg France http://www.tempo-consulting.fr Tel : +33 3 88 56 82 18 Fax : +33 3 88 56 46 64 ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Joël Grand-Guillaume* Division Manager Business Solutions +41 21 619 10 28 www.camptocamp.com ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Nicolas Bessi Senior ERP consultant Business Solution technical manager Camptocamp SA PSE A CH-1015 Lausanne http://openerp.camptocamp.com Direct: +41 21 619 10 26 Office: +41 21 619 10 10 -- Mailing list: https://launchpad.net/~openerp-community-reviewer Post to : openerp-community-reviewer@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community-reviewer More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community-reviewer] [Openerp-community] OCA LP Project migration to Github
Nicolas, I agree with you we should never commit on two repos. But it looks like to me the consensus is towards keeping v7 on launchpad, then I do not see any problem with a mirror of old branches. Git and Github have very strong features for handling with multiple branches: you can easily compare them, switch etc on github, and on the command line too. Best On Tue, May 20, 2014 at 1:26 PM, Nicolas Bessi nicolas.be...@camptocamp.com wrote: Hello, Thanks for the work. I'm OK for most of the point except for the branch/lp replication. We should not mix the tools, it will be chaos. It will not be wise to have a 7.0 series on launchpad and on github, people will work on both at the same time. If we have a 7.0 branch on github it means 7.0 series should be closed on LP. Also having code on LP and Github will complexify forward/backward fix merging. I'm in favor to have all repo on github (or LP) only. Regards Nicolas 2014-05-20 12:18 GMT+02:00 Joël Grand-Guillaume joel.grandguilla...@camptocamp.com: Dear all, Thanks a lot for all your feedback here. So, to summarize opinions here: * Version = 7.0 keep Launchpad as a reference. We eventually setup a replication in github (lp - gituhub) in a couple of weeks * We do use one organization on github for the whole community work * We create one team on github per area of expertize (so that means like it is now on LP). I tried to see if we can lower the number of team, but wasn't able to decide how to merge them. Any though here, the list is here : https://launchpad.net/~openerp-community-reviewer/+participation ? * Every LP project become a repository on github. The branches hosted under the community reviewer team (bazaar extractor, etc..) will have a new repo called something like community toolkit. * Branches represent the serie (like OpenERP did with odoo) The only disadvantage I see here is that we cannot include a team in a team on github. So that means, we'll no longer have a community reviewer team that is part of all other team. We'll need to add in every team the right people, but apart from a bit of administrative work, it'll be ok. As Nhomar pointed out, I already took the time to create this organization on github : https://github.com/OdooCommunity It was a first test from me, but if you agree, I'll spend some time to create the team and repos. I suggest also that I make an OCA-board team with the administration right on the organization. So current OCA board member will be able to administrate the organization as well. As some of you already notice, I also took the liberty to make a new logo, keeping the ant ;) Hope it please you all ! Regards, Joël On Tue, May 20, 2014 at 9:16 AM, Alejandro Catalina alecat...@gmail.comwrote: Hi there, I also agree with the last proposal, one github organization and several repositories, one for each launchpad project. So let's move on. I think the best way to move all those projects and branches is to divide the work between all of us. We could make a list of all launchpad URL involved and begin the job. What do you think about? 2014-05-20 8:33 GMT+02:00 Quentin THEURET q...@tempo-consulting.fr: On 16/05/14 18:43, Maxime Chambreuil wrote: We agree with Stefan here. I'm also agree with Stefan point of view. Regards, -- Quentin THEURET TeMPO Consulting 20, Avenue de la paix 67000 Strasbourg France http://www.tempo-consulting.fr Tel : +33 3 88 56 82 18 Fax : +33 3 88 56 46 64 ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Joël Grand-Guillaume* Division Manager Business Solutions +41 21 619 10 28 www.camptocamp.com ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Nicolas Bessi Senior ERP consultant Business Solution technical manager Camptocamp SA PSE A CH-1015 Lausanne http://openerp.camptocamp.com Direct: +41 21 619 10 26 Office: +41 21 619 10 10 -- Mailing list: https://launchpad.net/~openerp-community-reviewer Post to : openerp-community-reviewer@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community-reviewer More help : https://help.launchpad.net/ListHelp -- Mailing list:
Re: [Openerp-community-reviewer] [Openerp-community] OCA LP Project migration to Github
About v8, I support the initial idea of splitting the modules into many small repos. Let me argue a bit about this: - especially with git, it is super-easy to make branches even for small modifications. Having many modules in the same branches means that if you have two feature branches that add or change two different modules in the purchase-wkfl project, you cannot use them at the same time, not cleanly. - once (soon, I'm sure!) we will have travis test runs for unit tests and flake8 on all oca branches, we will be able to see in github that a branch is green and that a PR makes it red. Small repos make it super-easy to find the culprit and take action. The test runs become smaller, faster and more atomic. This will make our life as code reviewers incredibly easier IMHO, in addition to the merge button. Git submodules or subtrees are tools that group together many repos in a big repo as subdirectories. This basically means that we get the best of both worlds (we have the original big repos that have the modules as subtrees/submodules). I do not believe these to be black wizardry: it is just that git is used in big projects with many modules, and being very much used, good and generic solutions for those problems we have problems are already there. The disadvantages seem very small to me: - Finding the projects is harder: I do not believe so. There will be the subtree repo looking like the old ones, plus we can look them up in a wiki page / apps site or something. - Needs some initial work by some git experts: True. Someone with more experience than me could give more details please? I believe Joël for example make some research in that. For v7, I still think that the original a) proposal by Joël or making an as-is mirror of the v7 branches immediately on github, with a read-only mirror back to launchpad is my favorite option. Reason: when we will start to work on v8 on github, it will be complex to handle the two at the same time. Thanks to all for your time! best On Tue, May 20, 2014 at 12:18 PM, Joël Grand-Guillaume joel.grandguilla...@camptocamp.com wrote: Dear all, Thanks a lot for all your feedback here. So, to summarize opinions here: * Version = 7.0 keep Launchpad as a reference. We eventually setup a replication in github (lp - gituhub) in a couple of weeks * We do use one organization on github for the whole community work * We create one team on github per area of expertize (so that means like it is now on LP). I tried to see if we can lower the number of team, but wasn't able to decide how to merge them. Any though here, the list is here : https://launchpad.net/~openerp-community-reviewer/+participation ? * Every LP project become a repository on github. The branches hosted under the community reviewer team (bazaar extractor, etc..) will have a new repo called something like community toolkit. * Branches represent the serie (like OpenERP did with odoo) The only disadvantage I see here is that we cannot include a team in a team on github. So that means, we'll no longer have a community reviewer team that is part of all other team. We'll need to add in every team the right people, but apart from a bit of administrative work, it'll be ok. As Nhomar pointed out, I already took the time to create this organization on github : https://github.com/OdooCommunity It was a first test from me, but if you agree, I'll spend some time to create the team and repos. I suggest also that I make an OCA-board team with the administration right on the organization. So current OCA board member will be able to administrate the organization as well. As some of you already notice, I also took the liberty to make a new logo, keeping the ant ;) Hope it please you all ! Regards, Joël On Tue, May 20, 2014 at 9:16 AM, Alejandro Catalina alecat...@gmail.comwrote: Hi there, I also agree with the last proposal, one github organization and several repositories, one for each launchpad project. So let's move on. I think the best way to move all those projects and branches is to divide the work between all of us. We could make a list of all launchpad URL involved and begin the job. What do you think about? 2014-05-20 8:33 GMT+02:00 Quentin THEURET q...@tempo-consulting.fr: On 16/05/14 18:43, Maxime Chambreuil wrote: We agree with Stefan here. I'm also agree with Stefan point of view. Regards, -- Quentin THEURET TeMPO Consulting 20, Avenue de la paix 67000 Strasbourg France http://www.tempo-consulting.fr Tel : +33 3 88 56 82 18 Fax : +33 3 88 56 46 64 ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openerp-community Post to :
Re: [Openerp-community-reviewer] [Openerp-community] OCA LP Project migration to Github
Hi Joel ! On Fri, May 16, 2014 at 10:16 AM, Joël Grand-Guillaume joel.grandguilla...@camptocamp.com wrote: Dear community, After the announcement of the brand new odoo instead of OpenERP, the main changes for contributors currently is the switch to Github. As I know, most of you waited for such a move ! Now it's done :) Though it remain a quite huge question : How the hell do we, as the community, will manage this switch ? I know there is lots of side questions (like making one repository per module, using subtree and many more). I see those options: a) Move all projects from LP to Github, but only the 7.0 series to create only the master branch. Every devs should create the pull request needed if they want their LP MP to be shown as pull request on github. Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Easy, quick,simple to understand, only still active MP will be ported by each devs - = Every devs will have to rebuild the pull request, loss of review infos in the pull request (though people can copy/paste the link to LP) b) Move all projects from LP to Github and try to take all branches related to a project using [1], create the master branch from the 7.0 series. Then all devs will have to take back his branch, branch by branch, in his own name (that process [1] was use to move openstack to github). Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Keep all branches of all projects - = Doesn't help to take back the MP as pull request, will let lots of obsolete branches c) Try to immediately split repository to have one repo by module, all owned by the OCA project (only one project, many, many repos). Just making one repo by module. Then we can have those many repos grouped by topic using submodule (here an example: https://github.com/camptocamp/puppet-modules). By topic I mean Apps (like sale, purchase, ..). + = We have one repo by module and start clean on github - = Not that easy to split, not clear exactly how to do that, we have the risk that by the time we figure that out we remain on LP for quite a while, change the architecture and tools all at once. My suggestion to allow a fast move forward is option a) as the following: 1) Take all OCA projects on LP and create one under the OCA umbrella on github 2) Then I suggest to create the master branch on Github from the 7.0 series on LP. Older one remain on LP only. 3) All current MPs must be made as pull request by his owner on GitHub to be merged. 4) All the 7.0 series starts on Github as soon as we have build them all (should not take more than 1 or 2 days to achieve. The older one (5, 6, 6.1) remain on LP. 5) For 8.0, we starts creating all needed sub-module repo Mains args: * Easy and fast * Make a smooth transition as projects are kept, just moved on github * Avoid having old MP or obsolete branches in the OCA umbrella * For 7.0 serie we have everything on github, so we avoid working with both git and bzr * For older serie we keep all on bzr, while future v8.0 will have a clean one repo by module solution Who's in favor of which option here (a,b,c) ? Any others I missed ? I think c) is the best but will not fast move, extract per module and create a repo will take time. I am agree with choose a) option, so one Q here, when you named 5) arg point what will be the process ? Thanks for your vote ! Please try to be as short as possible on your answer, so we can see who's voting for which option :) Best regards, Joël [1] https://github.com/termie/lp2gh/blob/master/docs/moving_branches.rst -- *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Joël Grand-Guillaume* Division Manager Business Solutions +41 21 619 10 28 www.camptocamp.com ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Cristian Salamea @ovnicraft -- Mailing list: https://launchpad.net/~openerp-community-reviewer Post to : openerp-community-reviewer@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community-reviewer More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community-reviewer] [Openerp-community] OCA LP Project migration to Github
Hi Joël, Maybe I don't understand, but having one addon per repo does that mean that when an API change requires a change in all the banking addons (for instance), that I have to make a pull request for all those repos? I'd be in favour of keeping OCA projects in bzr for 7.0 and in GitHub for 8.0. Should be less work for everybody. Just because OpenERP SA causes this overnight disruptive change does not mean that the OCA has to follow. Or does the app store not support Launchpad anymore either? Cheers, Stefan. On 16-05-14 17:16, Joël Grand-Guillaume wrote: Dear community, After the announcement of the brand new odoo instead of OpenERP, the main changes for contributors currently is the switch to Github. As I know, most of you waited for such a move ! Now it's done :) Though it remain a quite huge question : How the hell do we, as the community, will manage this switch ? I know there is lots of side questions (like making one repository per module, using subtree and many more). I see those options: a) Move all projects from LP to Github, but only the 7.0 series to create only the master branch. Every devs should create the pull request needed if they want their LP MP to be shown as pull request on github. Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Easy, quick,simple to understand, only still active MP will be ported by each devs - = Every devs will have to rebuild the pull request, loss of review infos in the pull request (though people can copy/paste the link to LP) b) Move all projects from LP to Github and try to take all branches related to a project using [1], create the master branch from the 7.0 series. Then all devs will have to take back his branch, branch by branch, in his own name (that process [1] was use to move openstack to github). Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Keep all branches of all projects - = Doesn't help to take back the MP as pull request, will let lots of obsolete branches c) Try to immediately split repository to have one repo by module, all owned by the OCA project (only one project, many, many repos). Just making one repo by module. Then we can have those many repos grouped by topic using submodule (here an example: https://github.com/camptocamp/puppet-modules). By topic I mean Apps (like sale, purchase, ..). + = We have one repo by module and start clean on github - = Not that easy to split, not clear exactly how to do that, we have the risk that by the time we figure that out we remain on LP for quite a while, change the architecture and tools all at once. My suggestion to allow a fast move forward is option a) as the following: 1) Take all OCA projects on LP and create one under the OCA umbrella on github 2) Then I suggest to create the master branch on Github from the 7.0 series on LP. Older one remain on LP only. 3) All current MPs must be made as pull request by his owner on GitHub to be merged. 4) All the 7.0 series starts on Github as soon as we have build them all (should not take more than 1 or 2 days to achieve. The older one (5, 6, 6.1) remain on LP. 5) For 8.0, we starts creating all needed sub-module repo Mains args: * Easy and fast * Make a smooth transition as projects are kept, just moved on github * Avoid having old MP or obsolete branches in the OCA umbrella * For 7.0 serie we have everything on github, so we avoid working with both git and bzr * For older serie we keep all on bzr, while future v8.0 will have a clean one repo by module solution Who's in favor of which option here (a,b,c) ? Any others I missed ? Thanks for your vote ! Please try to be as short as possible on your answer, so we can see who's voting for which option :) Best regards, Joël [1] https://github.com/termie/lp2gh/blob/master/docs/moving_branches.rst -- *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Joël Grand-Guillaume* Division Manager Business Solutions +41 21 619 10 28 www.camptocamp.com http://www.camptocamp.com/ ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Therp - Maatwerk in open ontwikkeling Stefan Rijnhart - Ontwerp en implementatie mail: ste...@therp.nl tel: +31 (0) 614478606 http://therp.nl https://twitter.com/therp_stefan -- Mailing list: https://launchpad.net/~openerp-community-reviewer Post to : openerp-community-reviewer@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community-reviewer More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community-reviewer] [Openerp-community] OCA LP Project migration to Github
I vote for a) as the quickest and easiest option to arrive to the full split for v8. (unless someone can manage to do the split of v7 in a few days, but I suppose that's not possible). On Fri, May 16, 2014 at 5:31 PM, Ovnicraft ovnicr...@gmail.com wrote: Hi Joel ! On Fri, May 16, 2014 at 10:16 AM, Joël Grand-Guillaume joel.grandguilla...@camptocamp.com wrote: Dear community, After the announcement of the brand new odoo instead of OpenERP, the main changes for contributors currently is the switch to Github. As I know, most of you waited for such a move ! Now it's done :) Though it remain a quite huge question : How the hell do we, as the community, will manage this switch ? I know there is lots of side questions (like making one repository per module, using subtree and many more). I see those options: a) Move all projects from LP to Github, but only the 7.0 series to create only the master branch. Every devs should create the pull request needed if they want their LP MP to be shown as pull request on github. Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Easy, quick,simple to understand, only still active MP will be ported by each devs - = Every devs will have to rebuild the pull request, loss of review infos in the pull request (though people can copy/paste the link to LP) b) Move all projects from LP to Github and try to take all branches related to a project using [1], create the master branch from the 7.0 series. Then all devs will have to take back his branch, branch by branch, in his own name (that process [1] was use to move openstack to github). Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Keep all branches of all projects - = Doesn't help to take back the MP as pull request, will let lots of obsolete branches c) Try to immediately split repository to have one repo by module, all owned by the OCA project (only one project, many, many repos). Just making one repo by module. Then we can have those many repos grouped by topic using submodule (here an example: https://github.com/camptocamp/puppet-modules). By topic I mean Apps (like sale, purchase, ..). + = We have one repo by module and start clean on github - = Not that easy to split, not clear exactly how to do that, we have the risk that by the time we figure that out we remain on LP for quite a while, change the architecture and tools all at once. My suggestion to allow a fast move forward is option a) as the following: 1) Take all OCA projects on LP and create one under the OCA umbrella on github 2) Then I suggest to create the master branch on Github from the 7.0 series on LP. Older one remain on LP only. 3) All current MPs must be made as pull request by his owner on GitHub to be merged. 4) All the 7.0 series starts on Github as soon as we have build them all (should not take more than 1 or 2 days to achieve. The older one (5, 6, 6.1) remain on LP. 5) For 8.0, we starts creating all needed sub-module repo Mains args: * Easy and fast * Make a smooth transition as projects are kept, just moved on github * Avoid having old MP or obsolete branches in the OCA umbrella * For 7.0 serie we have everything on github, so we avoid working with both git and bzr * For older serie we keep all on bzr, while future v8.0 will have a clean one repo by module solution Who's in favor of which option here (a,b,c) ? Any others I missed ? I think c) is the best but will not fast move, extract per module and create a repo will take time. I am agree with choose a) option, so one Q here, when you named 5) arg point what will be the process ? Thanks for your vote ! Please try to be as short as possible on your answer, so we can see who's voting for which option :) Best regards, Joël [1] https://github.com/termie/lp2gh/blob/master/docs/moving_branches.rst -- *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Joël Grand-Guillaume* Division Manager Business Solutions +41 21 619 10 28 www.camptocamp.com ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Cristian Salamea @ovnicraft ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~openerp-community-reviewer Post to : openerp-community-reviewer@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community-reviewer More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community-reviewer] [Openerp-community] OCA LP Project migration to Github
I think Stefan raises an interesting approach: let v7 as is on Launchpad, and move quietly to GitHub for v8 modules (one module migration, a module that is tested on v8 and works, etc) in the form 1 module/1 repo. About the other problem, I don't know exactly GitHub, but I think you can propose a merge at project or subproject level. Raphäel is an expert on GitHub, so he can guide us. Regards. 2014-05-16 17:51 GMT+02:00 Leonardo Pistone leonardo.pist...@camptocamp.com : I vote for a) as the quickest and easiest option to arrive to the full split for v8. (unless someone can manage to do the split of v7 in a few days, but I suppose that's not possible). On Fri, May 16, 2014 at 5:31 PM, Ovnicraft ovnicr...@gmail.com wrote: Hi Joel ! On Fri, May 16, 2014 at 10:16 AM, Joël Grand-Guillaume joel.grandguilla...@camptocamp.com wrote: Dear community, After the announcement of the brand new odoo instead of OpenERP, the main changes for contributors currently is the switch to Github. As I know, most of you waited for such a move ! Now it's done :) Though it remain a quite huge question : How the hell do we, as the community, will manage this switch ? I know there is lots of side questions (like making one repository per module, using subtree and many more). I see those options: a) Move all projects from LP to Github, but only the 7.0 series to create only the master branch. Every devs should create the pull request needed if they want their LP MP to be shown as pull request on github. Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Easy, quick,simple to understand, only still active MP will be ported by each devs - = Every devs will have to rebuild the pull request, loss of review infos in the pull request (though people can copy/paste the link to LP) b) Move all projects from LP to Github and try to take all branches related to a project using [1], create the master branch from the 7.0 series. Then all devs will have to take back his branch, branch by branch, in his own name (that process [1] was use to move openstack to github). Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Keep all branches of all projects - = Doesn't help to take back the MP as pull request, will let lots of obsolete branches c) Try to immediately split repository to have one repo by module, all owned by the OCA project (only one project, many, many repos). Just making one repo by module. Then we can have those many repos grouped by topic using submodule (here an example: https://github.com/camptocamp/puppet-modules). By topic I mean Apps (like sale, purchase, ..). + = We have one repo by module and start clean on github - = Not that easy to split, not clear exactly how to do that, we have the risk that by the time we figure that out we remain on LP for quite a while, change the architecture and tools all at once. My suggestion to allow a fast move forward is option a) as the following: 1) Take all OCA projects on LP and create one under the OCA umbrella on github 2) Then I suggest to create the master branch on Github from the 7.0 series on LP. Older one remain on LP only. 3) All current MPs must be made as pull request by his owner on GitHub to be merged. 4) All the 7.0 series starts on Github as soon as we have build them all (should not take more than 1 or 2 days to achieve. The older one (5, 6, 6.1) remain on LP. 5) For 8.0, we starts creating all needed sub-module repo Mains args: * Easy and fast * Make a smooth transition as projects are kept, just moved on github * Avoid having old MP or obsolete branches in the OCA umbrella * For 7.0 serie we have everything on github, so we avoid working with both git and bzr * For older serie we keep all on bzr, while future v8.0 will have a clean one repo by module solution Who's in favor of which option here (a,b,c) ? Any others I missed ? I think c) is the best but will not fast move, extract per module and create a repo will take time. I am agree with choose a) option, so one Q here, when you named 5) arg point what will be the process ? Thanks for your vote ! Please try to be as short as possible on your answer, so we can see who's voting for which option :) Best regards, Joël [1] https://github.com/termie/lp2gh/blob/master/docs/moving_branches.rst -- *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Joël Grand-Guillaume* Division Manager Business Solutions +41 21 619 10 28 www.camptocamp.com ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Cristian Salamea @ovnicraft
Re: [Openerp-community-reviewer] [Openerp-community] OCA LP Project migration to Github
vote : A Big thanks to Joel for this mail ;) 2014-05-16 17:16 GMT+02:00 Joël Grand-Guillaume joel.grandguilla...@camptocamp.com: Dear community, After the announcement of the brand new odoo instead of OpenERP, the main changes for contributors currently is the switch to Github. As I know, most of you waited for such a move ! Now it's done :) Though it remain a quite huge question : How the hell do we, as the community, will manage this switch ? I know there is lots of side questions (like making one repository per module, using subtree and many more). I see those options: a) Move all projects from LP to Github, but only the 7.0 series to create only the master branch. Every devs should create the pull request needed if they want their LP MP to be shown as pull request on github. Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Easy, quick,simple to understand, only still active MP will be ported by each devs - = Every devs will have to rebuild the pull request, loss of review infos in the pull request (though people can copy/paste the link to LP) b) Move all projects from LP to Github and try to take all branches related to a project using [1], create the master branch from the 7.0 series. Then all devs will have to take back his branch, branch by branch, in his own name (that process [1] was use to move openstack to github). Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Keep all branches of all projects - = Doesn't help to take back the MP as pull request, will let lots of obsolete branches c) Try to immediately split repository to have one repo by module, all owned by the OCA project (only one project, many, many repos). Just making one repo by module. Then we can have those many repos grouped by topic using submodule (here an example: https://github.com/camptocamp/puppet-modules). By topic I mean Apps (like sale, purchase, ..). + = We have one repo by module and start clean on github - = Not that easy to split, not clear exactly how to do that, we have the risk that by the time we figure that out we remain on LP for quite a while, change the architecture and tools all at once. My suggestion to allow a fast move forward is option a) as the following: 1) Take all OCA projects on LP and create one under the OCA umbrella on github 2) Then I suggest to create the master branch on Github from the 7.0 series on LP. Older one remain on LP only. 3) All current MPs must be made as pull request by his owner on GitHub to be merged. 4) All the 7.0 series starts on Github as soon as we have build them all (should not take more than 1 or 2 days to achieve. The older one (5, 6, 6.1) remain on LP. 5) For 8.0, we starts creating all needed sub-module repo Mains args: * Easy and fast * Make a smooth transition as projects are kept, just moved on github * Avoid having old MP or obsolete branches in the OCA umbrella * For 7.0 serie we have everything on github, so we avoid working with both git and bzr * For older serie we keep all on bzr, while future v8.0 will have a clean one repo by module solution Who's in favor of which option here (a,b,c) ? Any others I missed ? Thanks for your vote ! Please try to be as short as possible on your answer, so we can see who's voting for which option :) Best regards, Joël [1] https://github.com/termie/lp2gh/blob/master/docs/moving_branches.rst -- *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Joël Grand-Guillaume* Division Manager Business Solutions +41 21 619 10 28 www.camptocamp.com ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~openerp-community-reviewer Post to : openerp-community-reviewer@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community-reviewer More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community-reviewer] [Openerp-community] OCA LP Project migration to Github
We agree with Stefan here. -- Maxime Chambreuil +1 (514) 276-5468 #126 - Mail original - Stefan's approach has my vote. Keep = 7.0 on lauchpad and use github for = 8.0. Cheers, -sbi On Fri, May 16, 2014 at 5:51 PM, Stefan Rijnhart ste...@therp.nl wrote: Hi Joël, Maybe I don't understand, but having one addon per repo does that mean that when an API change requires a change in all the banking addons (for instance), that I have to make a pull request for all those repos? I'd be in favour of keeping OCA projects in bzr for 7.0 and in GitHub for 8.0. Should be less work for everybody. Just because OpenERP SA causes this overnight disruptive change does not mean that the OCA has to follow. Or does the app store not support Launchpad anymore either? Cheers, Stefan. On 16-05-14 17:16, Joël Grand-Guillaume wrote: blockquote Dear community, After the announcement of the brand new odoo instead of OpenERP, the main changes for contributors currently is the switch to Github. As I know, most of you waited for such a move ! Now it's done :) Though it remain a quite huge question : How the hell do we, as the community, will manage this switch ? I know there is lots of side questions (like making one repository per module, using subtree and many more). I see those options: a) Move all projects from LP to Github, but only the 7.0 series to create only the master branch. Every devs should create the pull request needed if they want their LP MP to be shown as pull request on github. Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Easy, quick,simple to understand, only still active MP will be ported by each devs - = Every devs will have to rebuild the pull request, loss of review infos in the pull request (though people can copy/paste the link to LP) b) Move all projects from LP to Github and try to take all branches related to a project using [1], create the master branch from the 7.0 series. Then all devs will have to take back his branch, branch by branch, in his own name (that process [1] was use to move openstack to github). Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Keep all branches of all projects - = Doesn't help to take back the MP as pull request, will let lots of obsolete branches c) Try to immediately split repository to have one repo by module, all owned by the OCA project (only one project, many, many repos). Just making one repo by module. Then we can have those many repos grouped by topic using submodule (here an example: https://github.com/camptocamp/puppet-modules ). By topic I mean Apps (like sale, purchase, ..). + = We have one repo by module and start clean on github - = Not that easy to split, not clear exactly how to do that, we have the risk that by the time we figure that out we remain on LP for quite a while, change the architecture and tools all at once. My suggestion to allow a fast move forward is option a) as the following: 1) Take all OCA projects on LP and create one under the OCA umbrella on github 2) Then I suggest to create the master branch on Github from the 7.0 series on LP. Older one remain on LP only. 3) All current MPs must be made as pull request by his owner on GitHub to be merged. 4) All the 7.0 series starts on Github as soon as we have build them all (should not take more than 1 or 2 days to achieve. The older one (5, 6, 6.1) remain on LP. 5) For 8.0, we starts creating all needed sub-module repo Mains args: * Easy and fast * Make a smooth transition as projects are kept, just moved on github * Avoid having old MP or obsolete branches in the OCA umbrella * For 7.0 serie we have everything on github, so we avoid working with both git and bzr * For older serie we keep all on bzr, while future v8.0 will have a clean one repo by module solution Who's in favor of which option here (a,b,c) ? Any others I missed ? Thanks for your vote ! Please try to be as short as possible on your answer, so we can see who's voting for which option :) Best regards, Joël [1] https://github.com/termie/lp2gh/blob/master/docs/moving_branches.rst -- camp to camp INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS Joël Grand-Guillaume Division Manager Business Solutions +41 21 61 9 10 28 www.camptocamp.com ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Therp - Maatwerk in open ontwikkeling Stefan Rijnhart - Ontwerp en implementatie mail: ste...@therp.nl tel: +31 (0) 614478606 http://therp.nl https://twitter.com/therp_stefan
Re: [Openerp-community-reviewer] [Openerp-community] OCA LP Project migration to Github
On Fri, May 16, 2014 at 10:51 AM, Stefan Rijnhart ste...@therp.nl wrote: Hi Joël, Maybe I don't understand, but having one addon per repo does that mean that when an API change requires a change in all the banking addons (for instance), that I have to make a pull request for all those repos? I'd be in favour of keeping OCA projects in bzr for 7.0 and in GitHub for 8.0. Should be less work for everybody. Just because OpenERP SA causes this overnight disruptive change does not mean that the OCA has to follow. Or does the app store not support Launchpad anymore either? So akretion has a mirror for OCB at github[1] and all of us can works, in fact ocb-7.0 is master :-) and it follows option a) suggested by Joel. By now its now possible so i dont understand organization in github from odoo, now master has server and addons in single repo, BTW move ASAP to github approaching what exists is better. Comments ! [1] https://github.com/akretion/openerp-server Cheers, Stefan. On 16-05-14 17:16, Joël Grand-Guillaume wrote: Dear community, After the announcement of the brand new odoo instead of OpenERP, the main changes for contributors currently is the switch to Github. As I know, most of you waited for such a move ! Now it's done :) Though it remain a quite huge question : How the hell do we, as the community, will manage this switch ? I know there is lots of side questions (like making one repository per module, using subtree and many more). I see those options: a) Move all projects from LP to Github, but only the 7.0 series to create only the master branch. Every devs should create the pull request needed if they want their LP MP to be shown as pull request on github. Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Easy, quick,simple to understand, only still active MP will be ported by each devs - = Every devs will have to rebuild the pull request, loss of review infos in the pull request (though people can copy/paste the link to LP) b) Move all projects from LP to Github and try to take all branches related to a project using [1], create the master branch from the 7.0 series. Then all devs will have to take back his branch, branch by branch, in his own name (that process [1] was use to move openstack to github). Then for serie 8.0, we start with one repo by module (as in option c): + = one LP project = one github project, Keep all branches of all projects - = Doesn't help to take back the MP as pull request, will let lots of obsolete branches c) Try to immediately split repository to have one repo by module, all owned by the OCA project (only one project, many, many repos). Just making one repo by module. Then we can have those many repos grouped by topic using submodule (here an example: https://github.com/camptocamp/puppet-modules). By topic I mean Apps (like sale, purchase, ..). + = We have one repo by module and start clean on github - = Not that easy to split, not clear exactly how to do that, we have the risk that by the time we figure that out we remain on LP for quite a while, change the architecture and tools all at once. My suggestion to allow a fast move forward is option a) as the following: 1) Take all OCA projects on LP and create one under the OCA umbrella on github 2) Then I suggest to create the master branch on Github from the 7.0 series on LP. Older one remain on LP only. 3) All current MPs must be made as pull request by his owner on GitHub to be merged. 4) All the 7.0 series starts on Github as soon as we have build them all (should not take more than 1 or 2 days to achieve. The older one (5, 6, 6.1) remain on LP. 5) For 8.0, we starts creating all needed sub-module repo Mains args: * Easy and fast * Make a smooth transition as projects are kept, just moved on github * Avoid having old MP or obsolete branches in the OCA umbrella * For 7.0 serie we have everything on github, so we avoid working with both git and bzr * For older serie we keep all on bzr, while future v8.0 will have a clean one repo by module solution Who's in favor of which option here (a,b,c) ? Any others I missed ? Thanks for your vote ! Please try to be as short as possible on your answer, so we can see who's voting for which option :) Best regards, Joël [1] https://github.com/termie/lp2gh/blob/master/docs/moving_branches.rst -- *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Joël Grand-Guillaume* Division Manager Business Solutions +41 21 619 10 28 www.camptocamp.com ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-commun...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Therp - Maatwerk in open ontwikkeling
