Re: [Openerp-community] OCA LP Project migration to Github
Hello all, Joël Grand-Guillaume also made a remarkably similar mapping for teams. I updated the spreasheet to integrate his contribution. I invite you all to review it and flag anything that doesn't seem right.[1] Joël: I kept a few differences from your list, they are marked in blue colour to help you identify them and comment. Again, the list can be found here: https://docs.google.com/spreadsheets/d/15aVznH-4ploi7d6yPvchyh5ZplzewbA2qYmDLDfndqU/edit?usp=sharing Regards /DR Ligações: - [1] a href= /a ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] OCA LP Project migration to Github
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.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-community@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-community@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
Re: [Openerp-community] OCA LP Project migration to Github
I must say me too, but it sounded to me that most people prefered to keep LP as a v7.0 reference. LP can replicate a github repo, not the contrary (or not without scripting / croning some tasks). On Wed, May 21, 2014 at 10:13 AM, Leonardo Pistone leonardo.pist...@camptocamp.com wrote: 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! I misunderstood this, so do you suggest keep LP 7.0 series keep it alive ? I suggest working on 7.0 on github, with automatic, read-only mirrors on launchpad. ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@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-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] OCA LP Project migration to Github
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-community@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-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [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-community@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-community@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-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] OCA LP Project migration to Github
Logo is great ;) Thanks for doing the heavy lifting for us! Eric CAUDAL Eric Caudal /CEO/ -- *Elico Corporation, Shanghai branch /OpenERP Premium Certified Training Partner/ * Cell: + 86 186 2136 1670 Office: + 86 21 6211 8017/27/37 Skype: elico.corp eric.cau...@elico-corp.com mailto:eric.cau...@elico-corp.com http://www.elico-corp.com Elico Corp On 05/20/2014 06:18 PM, Joël Grand-Guillaume 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 https://launchpad.net/%7Eopenerp-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 mailto: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 mailto: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 tel:%2B33%203%2088%2056%2082%2018 Fax : +33 3 88 56 46 64 tel:%2B33%203%2088%2056%2046%2064 ___ Mailing list: https://launchpad.net/~openerp-community https://launchpad.net/%7Eopenerp-community Post to : openerp-community@lists.launchpad.net mailto:openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community https://launchpad.net/%7Eopenerp-community More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openerp-community https://launchpad.net/%7Eopenerp-community Post to : openerp-community@lists.launchpad.net mailto:openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community https://launchpad.net/%7Eopenerp-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 http://www.camptocamp.com/ ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@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-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [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-community@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-community@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-community@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-community@lists.launchpad.net Unsubscribe :
Re: [Openerp-community] OCA LP Project migration to Github
Here is a proposal to cut the 47 teams into only 28: https://docs.google.com/spreadsheets/d/15aVznH-4ploi7d6yPvchyh5ZplzewbA2qYmDLDfndqU/edit?usp=sharing Some teams have only empty repos and have been inactive. Not sure it it's worth to create them on GitHub, but I haven't removed them from the list. Regards /DR Quoting 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.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[1] Fax : +33 3 88 56 46 64[2] ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@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-community@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[3] Ligações: - [1] a href=tel:%2B33%203%2088%2056%2082%2018 tel:%2B33%203%2088%2056%2082%2018/a [2] a href=tel:%2B33%203%2088%2056%2046%2064 tel:%2B33%203%2088%2056%2046%2064/a [3] a href=http://www.camptocamp.com/; http://www.camptocamp.com//a ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] OCA LP Project migration to Github
Joël, Maybe the best name for the organization is OCA, instead of OpenCommunity, this way we get clean and a short URLs: oca/sales for example. Regards, -- PS: escribí este email desde mi teléfono, por favor disculpe la brevedad y cualquier error de escritura. Carlos Vásquez CTO · Director de Ingeniería carlos.vasq...@clearcorp.co.cr CR: +(506) 4000 CORP (4000 2677) US: +1 (786) 472-4267 Cel: +(506) 8351 4484 skype: crvasquez twitter: cvclearcorp 300 m. Este de la Escuela Calle de Platanares 11402 San Jerónimo, Moravia San José, Costa Rica http://www.clearcorp.co.cr ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] OCA LP Project migration to Github
On Tue, May 20, 2014 at 7:03 AM, Leonardo Pistone leonardo.pist...@camptocamp.com wrote: 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. Not, git submodules works really fine and its easy when you get a main repo and needs *link* another repos. 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! I misunderstood this, so do you suggest keep LP 7.0 series keep it alive ? 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:
Re: [Openerp-community] OCA LP Project migration to Github
Dear community, I know many are eager to change vcs but please give everyone time to insert this in their already too small timetables. Probably we at Numerigraphe will stick to Launchpad for as long as we can because use bzr all the way though to production servers. We can't afford to switch now. If you do migrate v7 to github, pleaseset up upstream branches on launchpad, this way LP will pull the new commits itself. Regarding v8, I don't understand how it's better to have a myriad of small unconnected repositories instead of one cleanly organized tree. If we instead merged all OCA projects into one branch like Odoo did, it would be easier for new contributers. I for one spent hours searching for which project had which module in Launchpad. OCA must eventually become a large code-base (linux-size large would not surprise me): does it help if we spread it all over the place? Some claim each OCA project has it's own very small community: but wasn't OCA about uniting? And it won't be extra-addons again - that was a savage dump, and OCA is cleanly organized. Git wizards say it's easy to rebase the subtrees' staged unpulled remote into the master out-of-index sub-ether-spacial workflow, but for the rest of us, I beg you to make it simple. Lionel Sausin. ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] OCA LP Project migration to Github
On 05/19/2014 07:38 PM, Nhomar Hernández wrote: I think the proposal y 1 Organization (organization == Team)/ Several repositories (repository == project-launchpad). Then we can follow the Repository under the Organization. Thanks Nhomar, the way you describe it, I do agree with completely. Lionel howerver was talking about merging all OCA projects into one branch like Odoo did. Cheers, Stefan. ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] OCA LP Project migration to Github
On Mon, May 19, 2014 at 3:38 PM, Daniel Reis dgr...@sapo.pt wrote: Raphael, you mean one Github Organization, right? yes -- Raphaël Valyi Founder and consultant http://twitter.com/rvalyi http://twitter.com/#!/rvalyi +55 21 3942-2434 www.akretion.com ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] OCA LP Project migration to Github
OCA must eventually become a large code-base (linux-size large would not surprise me): does it help if we spread it all over the place? I'm counting around 50 OCA repos. Personally, I'm interested in only about 5 of them. I would prefer avoiding the notifications on the modules of the other 45 repos. If you really want to, getting all OCA modules is at the reach of a bash or python script. Maybe git submodules make a nice trick for that, but in the end it's perfectly doable without any Git magic. A community maintained list like this one would make that simple: https://github.com/openerpapps/openerpapps.github.io/blob/master/sources/oca.list Git wizards say it's easy to rebase the subtrees' staged unpulled remote into the master out-of-index sub-ether-spacial workflow, but for the rest of us, I beg you to make it simple. Moving to git and GitHub won't be easy for 98% of us. Workflows will be very different. So yes, let's keep it as simple as possible. Having GitHub as the reference only for 8.0 onward is a good step in that direccion: It will allow everyone to adapt at their own pace. Remember that current proposals is that code = 7.0 keeps LP as the reference (possibly keeping GH in sync). So nothing would change there. Regards /DR PS: Just out of curiosity, this is thecurrent OCA repo name list though some repos are empty): account-analytic account-budgeting account-closing account-consolidation account-financial-report account-financial-tools account-invoice-report account-invoicing account-payment banking-addons bank-statement-reconcile carriers-deliveries contract-management department-mgmt e-commerce-addons geospatial-addons hotel-management-system hr-timesheet knowledge-addons margin-analysis multi-company openerp-accountedge openerp-construction openerp-crm openerp-fiscal-rules openerp-icm openerp-manufacturing openerp-mgmtsystem openerp-product-attributes openerp-product-variant partner-contact-management product-kitting project-reporting project-service purchase-report purchase-wkfl redmine-openerp report-print-send rt-openerp sale-financial sale-reports sale-wkfl server-env-tools stock-logistic-barcode stock-logistic-flows stock-logistic-tracking stock-logistic-warehouse sugarcrm-openerp web-addons webkit-utils ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] OCA LP Project migration to Github
Hi all, My 2 cents. Option D with future plans to move 7 and maybe 6.1 to new branches. Regards, Erdem 7Gates On Sun, May 18, 2014 at 12:43 AM, Daniel Reis dgr...@sapo.pt wrote: Jean-Charles, Building up on your mail: *A) - OCA would be a Github organizations (...) Wouldn't it be good to use one Github organization per github projects? This would have 2 benefits:* Agree on 1 OCA Organization. Github has Teams under an Organization. So we could just move LP Project Teams into GitHub teams. But here I propose a change: I believe that the concept of a (global) OCA Reviewer makes little sense. Collaboration on OCA projects should instead be centred on areas of expertise. So, I propose to create a Team per Expertise Area, rather than for each Project. These would be maintainer teams, rather than reviewer. Maintainer have the last word on pull requests, but anyone can - and should - review. Current team member should be invited for maintainer roles in the new teams according to interests and expertise. *B) - OCA projects/apps would be Github projects* I would rephrase that into OCA Projects would be Github Repositories. I suggest to keep it simple for the migration: 1 LP repo - 1 GH repo After the migration, the community would of course be free to discuss, case by case, on splitting or joining repos (just like Odoo did). *C) - OCA modules would git sub- modules* I would avoid sub-modules, at least for now. I see advantages in keeping closely related modules in the same repository: We need to acknowledge that technical module is not a functional module. A technical module is rather a feature. An app is a core module complemented by a collection closely related module implementing additional features. *D) - series 7, 8, 9.. would be branches* Agree, just like in the core repos. *E) OCB* (my addition) I believe this will be a fork of the official repo, maintained by a Team under OCA. As I read from Stephan , rebase will greatly simplify keeping it in sync. Of course, comments are welcome. Regards /DR Quoting Jean-Charles Drubay jcdru...@trobz.com: Hi, It will be challenging to solve 2 issues at the same time in this thread: . what should be the source code organization in github . what should be the process to migrate Also, here are my 2 cents for targeted source code organization from what I understand of Joel's mail: - OCA would be a Github organizations - OCA projects/apps would be Github projects - OCA modules would git sub- modules - series 7, 8, 9.. would be branches Wouldn't it be good to use one Github organization per github projects? This would have 2 benefits: - no need to use submodules - better team management Apps will support github repos soon, see https://github.com/odoo/odoo/wiki/GitHub-Transition Regards, Jean-Charles Drubay, sent from my phone ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@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-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] OCA LP Project migration to Github
Thanks Daniel. I support 100% your explanation :-) I was writting my answer and read yours and I think I need just add my extra comment to your points because are so closely. 2014-05-17 16:43 GMT-05:00 Daniel Reis dgr...@sapo.pt: Jean-Charles, Building up on your mail: *A) - OCA would be a Github organizations (...) Wouldn't it be good to use one Github organization per github projects? This would have 2 benefits:* Agree on 1 OCA Organization. Github has Teams under an Organization. So we could just move LP Project Teams into GitHub teams. But here I propose a change: I believe that the concept of a (global) OCA Reviewer makes little sense. Collaboration on OCA projects should instead be centred on areas of expertise. So, I propose to create a Team per Expertise Area, rather than for each Project. These would be maintainer teams, rather than reviewer. Maintainer have the last word on pull requests, but anyone can - and should - review. Current team member should be invited for maintainer roles in the new teams according to interests and expertise. *B) - OCA projects/apps would be Github projects* I would rephrase that into OCA Projects would be Github Repositories. I suggest to keep it simple for the migration: 1 LP repo - 1 GH repo After the migration, the community would of course be free to discuss, case by case, on splitting or joining repos (just like Odoo did). *C) - OCA modules would git sub- modules* I would avoid sub-modules, at least for now. I see advantages in keeping closely related modules in the same repository: We need to acknowledge that technical module is not a functional module. A technical module is rather a feature. An app is a core module complemented by a collection closely related module implementing additional features. I think every repository should have a module called App - XYZ that at least ensure these repository by itself works as an APP. I think is important because is how the V8 will be working, as decentralized apps bundle with bridge modules. *D) - series 7, 8, 9.. would be branches* Agree, just like in the core repos. *E) OCB* (my addition) I believe this will be a fork of the official repo, maintained by a Team under OCA. As I read from Stephan , rebase will greatly simplify keeping it in sync. Of course, comments are welcome. Regards /DR Quoting Jean-Charles Drubay jcdru...@trobz.com: Hi, It will be challenging to solve 2 issues at the same time in this thread: . what should be the source code organization in github . what should be the process to migrate Also, here are my 2 cents for targeted source code organization from what I understand of Joel's mail: - OCA would be a Github organizations - OCA projects/apps would be Github projects - OCA modules would git sub- modules - series 7, 8, 9.. would be branches Wouldn't it be good to use one Github organization per github projects? This would have 2 benefits: - no need to use submodules - better team management Apps will support github repos soon, see https://github.com/odoo/odoo/wiki/GitHub-Transition Regards, Jean-Charles Drubay, sent from my phone ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Saludos Cordiales Nhomar G. Hernandez M. +58-414-4110269 Skype: nhomar00 Web-Blog: http://geronimo.com.ve Servicios IT: http://vauxoo.com Linux-Counter: 467724 Correos: nho...@openerp.com.ve nho...@vauxoo.com twitter @nhomar ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [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-community@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 Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [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-community@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-community@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-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help :
Re: [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-community@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-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [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-community@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-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] OCA LP Project migration to Github
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: 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-community@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) 614478606http://therp.nlhttps://twitter.com/therp_stefan ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net
Re: [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-community@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] 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-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Therp - Maatwerk in open ontwikkeling
Re: [Openerp-community] OCA LP Project migration to Github
d) or c) at least as first move (it could be done in 2 phases) or unless apps.odoo.com does not support lp anymore. Eric CAUDAL Eric Caudal /CEO/ -- *Elico Corporation, Shanghai branch /OpenERP Premium Certified Training Partner/ * Cell: + 86 186 2136 1670 Office: + 86 21 6211 8017/27/37 Skype: elico.corp eric.cau...@elico-corp.com mailto:eric.cau...@elico-corp.com http://www.elico-corp.com Elico Corp On 05/17/2014 12:51 AM, Ovnicraft wrote: On Fri, May 16, 2014 at 10:51 AM, Stefan Rijnhart ste...@therp.nl mailto: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
