[Openerp-community] OCA: transition from Launchpad to Github

classic Classic list List threaded Threaded
84 messages Options
12345
Reply | Threaded
Open this post in threaded view
|

[Openerp-community] OCA: transition from Launchpad to Github

Guewen Baconnier @ Camptocamp
Hi community,

I want to start to coordinate the transition of the OCA branches to
Github. Joël already created all the projects on Github, not without
sighs, thanks to him! We still have to create the teams, migrate the
code and setup the tooling for the maintainers / reviewers.

Several discussions have already taken place on the mailing list or
during the Opendays, but all is not yet defined. I will try to gather
here all the stuff around that, so please share your thoughts.

The decisions discussed so far
==============================

 - The branches up to 7.0 will stay on Launchpad
   Though, they will be mirrored on Github (Github doesn't have readonly
branches but the committers won't commit on them)
 - Starting from 8.0, they will be on Github
 - For the OCA committers and reviewers, it means that we will need to
review both on Launchpad and Github, but it avoid the need to migrate
all the pending merge proposals and bug reports
 - There is no date planned for the creation of the 8.0 branches, sooner
means more duplication of proposals (and some pain to follow the master
branch changes, which is still unstable), on the other hand, some people
already work on modules for v8.0.

Some scripts (fast-import, ...) or ideas have already been published but
I want to have a reference in this thread, so please share them.

Now, an inventory of what we'll need
====================================

 - A place where to write all the docs for maintainers of the projects
(the things we will discuss here). I'll try to write the docs, just not
sure of the best place to put them.
 - Create a mapping of projects/branches Launchpad → Github that will be
used by the scripts
 - At some point, push the head 7.0 branch of each Launchpad project to
their corresponding Github project as the new 8.0. This can be automated
I guess (using the mapping)
 - Write a script that mirrors the 6.1 and 7.0 branches to Github and
setup a cron
 - On Github, each project of the OCA has its own list of committers,
there is no way to put the OCA committers automatically in each OCA
project. What we'll do is to maintain 1 committer team [0] and to write
a script (with a cron) that copies all the members in all the others
projects' teams.
 - We have to decide where the OCA should deploy its tools (like the
mirroring script and committers script, and maybe others to come)

This is the minimal scope, but we would be more comfortable with:

 - a "nag" script for Github (openerp-nag equivalent), but I don't know
Github enough to know if Github is sufficient by itself
 - CI installed on all the OCA projects

Volunteers
==========

The transition will probably need a lot of boring and tedious - more or
less manual - work. More work than can be done by a single person, so my
first concern is to compile a list of the heroes who will take part and
will accept to share the tasks.

Please announce you! and inform if you have superpowers or special
abilities that could help (git-fu, launchpad api, github api, CI, ...).


I probably forget a lot of things, so do not hesitate to complete.
Thanks to be concise in your replies.

Have a nice and shiny week-end!


[0] https://github.com/orgs/OCA/teams/community-maintainers

--
Guewen Baconnier
Business Solutions Software Developer

Camptocamp SA
PSE A, CH-1015 Lausanne
Phone: +41 21 619 10 39
Office: +41 21 619 10 10
http://www.camptocamp.com/

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Joël Grand-Guillaume @ camptocamp
Comments in-line:


On Fri, Jun 20, 2014 at 3:08 PM, Guewen Baconnier <[hidden email]> wrote:
Hi community,

I want to start to coordinate the transition of the OCA branches to
Github. Joël already created all the projects on Github, not without
sighs, thanks to him! We still have to create the teams, migrate the
code and setup the tooling for the maintainers / reviewers.

=> I needed some patience, I confess...
 

Now, an inventory of what we'll need
====================================

 - A place where to write all the docs for maintainers of the projects
(the things we will discuss here). I'll try to write the docs, just not
sure of the best place to put them.

=> For that, I want to strongly suggest to use the Github wiki/README.md as the technical docs. This way, every project within the OCA will have:

a) A functionnal/business description on the new OCA website
b) A technical description on github for each repository.

 
 - Create a mapping of projects/branches Launchpad → Github that will be
used by the scripts 
 - At some point, push the head 7.0 branch of each Launchpad project to
their corresponding Github project as the new 8.0. This can be automated
I guess (using the mapping)
 - Write a script that mirrors the 6.1 and 7.0 branches to Github and
setup a cron

=> +1 for all 3
 
 - On Github, each project of the OCA has its own list of committers,
there is no way to put the OCA committers automatically in each OCA
project. What we'll do is to maintain 1 committer team [0] and to write
a script (with a cron) that copies all the members in all the others
projects' teams.
 - We have to decide where the OCA should deploy its tools (like the
mirroring script and committers script, and maybe others to come)

=> Commit the tools here: https://github.com/OCA/maintainers-tools
=> For running the cron, tow options:
 a) OCA buy something on one of those services : http://www.cronjobservices.com/
 b) Somebody within the OCA offer a server and access to Community Maintainers team to setup them
 

--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Ovnicraft



On Fri, Jun 20, 2014 at 8:46 AM, Joël Grand-Guillaume <[hidden email]> wrote:
Comments in-line:


On Fri, Jun 20, 2014 at 3:08 PM, Guewen Baconnier <[hidden email]> wrote:
Hi community,

I want to start to coordinate the transition of the OCA branches to
Github. Joël already created all the projects on Github, not without
sighs, thanks to him! We still have to create the teams, migrate the
code and setup the tooling for the maintainers / reviewers.

=> I needed some patience, I confess...
 

Now, an inventory of what we'll need
====================================

 - A place where to write all the docs for maintainers of the projects
(the things we will discuss here). I'll try to write the docs, just not
sure of the best place to put them.

=> For that, I want to strongly suggest to use the Github wiki/README.md as the technical docs. This way, every project within the OCA will have:

Totally agree, working in Ecuador Localization in https://github.com/odoo-ecuador/odoo-ecuador, for example i wrote how to setup a dev environment (https://github.com/odoo-ecuador/odoo-ecuador/wiki/Ambiente-de-Desarrollo) spanish by now. 

a) A functionnal/business description on the new OCA website
b) A technical description on github for each repository.

 
 - Create a mapping of projects/branches Launchpad → Github that will be
used by the scripts 
 - At some point, push the head 7.0 branch of each Launchpad project to
their corresponding Github project as the new 8.0. This can be automated
I guess (using the mapping)
 - Write a script that mirrors the 6.1 and 7.0 branches to Github and
setup a cron
 
=> +1 for all 3

For this is not extra job for OCA ? at some point automated task can give us problems, personally i think move from 7.0 to github, yes its a hard job. BTW stay tuned around script. 
 
 - On Github, each project of the OCA has its own list of committers,
there is no way to put the OCA committers automatically in each OCA
project. What we'll do is to maintain 1 committer team [0] and to write
a script (with a cron) that copies all the members in all the others
projects' teams.
 - We have to decide where the OCA should deploy its tools (like the
mirroring script and committers script, and maybe others to come)

=> Commit the tools here: https://github.com/OCA/maintainers-tools
=> For running the cron, tow options:
 a) OCA buy something on one of those services : http://www.cronjobservices.com/
 b) Somebody within the OCA offer a server and access to Community Maintainers team to setup them

If you want i can setup a machine at rackspace now and give the access.


Regards, 
 

--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp




--

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Moises Lopez
Hello,

We make a simple mini-script to migrate to github from launchpad. (See attachment)
Sorry to send it by email.
But if you send me the project which should be available this script.
I will push it

We migrate from:



2014-06-20 9:46 GMT-05:00 Ovnicraft <[hidden email]>:



On Fri, Jun 20, 2014 at 8:46 AM, Joël Grand-Guillaume <[hidden email]> wrote:
Comments in-line:


On Fri, Jun 20, 2014 at 3:08 PM, Guewen Baconnier <[hidden email]> wrote:
Hi community,

I want to start to coordinate the transition of the OCA branches to
Github. Joël already created all the projects on Github, not without
sighs, thanks to him! We still have to create the teams, migrate the
code and setup the tooling for the maintainers / reviewers.

=> I needed some patience, I confess...
 

Now, an inventory of what we'll need
====================================

 - A place where to write all the docs for maintainers of the projects
(the things we will discuss here). I'll try to write the docs, just not
sure of the best place to put them.

=> For that, I want to strongly suggest to use the Github wiki/README.md as the technical docs. This way, every project within the OCA will have:

Totally agree, working in Ecuador Localization in https://github.com/odoo-ecuador/odoo-ecuador, for example i wrote how to setup a dev environment (https://github.com/odoo-ecuador/odoo-ecuador/wiki/Ambiente-de-Desarrollo) spanish by now. 

a) A functionnal/business description on the new OCA website
b) A technical description on github for each repository.

 
 - Create a mapping of projects/branches Launchpad → Github that will be
used by the scripts 
 - At some point, push the head 7.0 branch of each Launchpad project to
their corresponding Github project as the new 8.0. This can be automated
I guess (using the mapping)
 - Write a script that mirrors the 6.1 and 7.0 branches to Github and
setup a cron
 
=> +1 for all 3

For this is not extra job for OCA ? at some point automated task can give us problems, personally i think move from 7.0 to github, yes its a hard job. BTW stay tuned around script. 
 
 - On Github, each project of the OCA has its own list of committers,
there is no way to put the OCA committers automatically in each OCA
project. What we'll do is to maintain 1 committer team [0] and to write
a script (with a cron) that copies all the members in all the others
projects' teams.
 - We have to decide where the OCA should deploy its tools (like the
mirroring script and committers script, and maybe others to come)

=> Commit the tools here: https://github.com/OCA/maintainers-tools
=> For running the cron, tow options:
 a) OCA buy something on one of those services : http://www.cronjobservices.com/
 b) Somebody within the OCA offer a server and access to Community Maintainers team to setup them

If you want i can setup a machine at rackspace now and give the access.


Regards, 
 

--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp




--

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp




--
Moisés López Calderón
Vauxoo - OpenERP's Gold Partner
Mobile: (+521) 477-752-22-30
Office: (+52) 477-773-33-46
web: http://www.vauxoo.com
twitter: @vauxoo
           @moylop260           


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

bzr2git_script.py (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Moises Lopez


2014-06-20 13:10 GMT-05:00 Moises Lopez <[hidden email]>:
Hello,

We make a simple mini-script to migrate to github from launchpad. (See attachment)
Sorry to send it by email.
But if you send me the project which should be available this script.
I will push it

We migrate from:



2014-06-20 9:46 GMT-05:00 Ovnicraft <[hidden email]>:




On Fri, Jun 20, 2014 at 8:46 AM, Joël Grand-Guillaume <[hidden email]> wrote:
Comments in-line:


On Fri, Jun 20, 2014 at 3:08 PM, Guewen Baconnier <[hidden email]> wrote:
Hi community,

I want to start to coordinate the transition of the OCA branches to
Github. Joël already created all the projects on Github, not without
sighs, thanks to him! We still have to create the teams, migrate the
code and setup the tooling for the maintainers / reviewers.

=> I needed some patience, I confess...
 

Now, an inventory of what we'll need
====================================

 - A place where to write all the docs for maintainers of the projects
(the things we will discuss here). I'll try to write the docs, just not
sure of the best place to put them.

=> For that, I want to strongly suggest to use the Github wiki/README.md as the technical docs. This way, every project within the OCA will have:

Totally agree, working in Ecuador Localization in https://github.com/odoo-ecuador/odoo-ecuador, for example i wrote how to setup a dev environment (https://github.com/odoo-ecuador/odoo-ecuador/wiki/Ambiente-de-Desarrollo) spanish by now. 

a) A functionnal/business description on the new OCA website
b) A technical description on github for each repository.

 
 - Create a mapping of projects/branches Launchpad → Github that will be
used by the scripts 
 - At some point, push the head 7.0 branch of each Launchpad project to
their corresponding Github project as the new 8.0. This can be automated
I guess (using the mapping)
 - Write a script that mirrors the 6.1 and 7.0 branches to Github and
setup a cron
 
=> +1 for all 3

For this is not extra job for OCA ? at some point automated task can give us problems, personally i think move from 7.0 to github, yes its a hard job. BTW stay tuned around script. 
 
 - On Github, each project of the OCA has its own list of committers,
there is no way to put the OCA committers automatically in each OCA
project. What we'll do is to maintain 1 committer team [0] and to write
a script (with a cron) that copies all the members in all the others
projects' teams.
 - We have to decide where the OCA should deploy its tools (like the
mirroring script and committers script, and maybe others to come)

=> Commit the tools here: https://github.com/OCA/maintainers-tools
=> For running the cron, tow options:
 a) OCA buy something on one of those services : http://www.cronjobservices.com/
 b) Somebody within the OCA offer a server and access to Community Maintainers team to setup them

If you want i can setup a machine at rackspace now and give the access.


Regards, 
 

--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp




--

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp




--
Moisés López Calderón
Vauxoo - OpenERP's Gold Partner
Mobile: (+521) 477-752-22-30
Office: (+52) 477-773-33-46
web: http://www.vauxoo.com
twitter: @vauxoo
           @moylop260           




--
Moisés López Calderón
Vauxoo - OpenERP's Gold Partner
Mobile: (+521) 477-752-22-30
Office: (+52) 477-773-33-46
web: http://www.vauxoo.com
twitter: @vauxoo
           @moylop260           


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

David Arnold - El Alemán
In reply to this post by Ovnicraft

​Comments in line​


2014-06-20 9:46 GMT-05:00 Ovnicraft <[hidden email]>:



On Fri, Jun 20, 2014 at 8:46 AM, Joël Grand-Guillaume <[hidden email]> wrote:
Comments in-line:


On Fri, Jun 20, 2014 at 3:08 PM, Guewen Baconnier <[hidden email]> wrote:
Hi community,

I want to start to coordinate the transition of the OCA branches to
Github. Joël already created all the projects on Github, not without
sighs, thanks to him! We still have to create the teams, migrate the
code and setup the tooling for the maintainers / reviewers.

=> I needed some patience, I confess...
 

Now, an inventory of what we'll need
====================================

 - A place where to write all the docs for maintainers of the projects
(the things we will discuss here). I'll try to write the docs, just not
sure of the best place to put them.

=> For that, I want to strongly suggest to use the Github wiki/README.md as the technical docs. This way, every project within the OCA will have:

Totally agree, working in Ecuador Localization in https://github.com/odoo-ecuador/odoo-ecuador, for example i wrote how to setup a dev environment (https://github.com/odoo-ecuador/odoo-ecuador/wiki/Ambiente-de-Desarrollo) spanish by now. 

I don't think github-wiki is the best choice. I strongly recommend a readthedocs.org compatible rst-style.

References:


a) A functionnal/business description on the new OCA website
b) A technical description on github for each repository.

 
 - Create a mapping of projects/branches Launchpad → Github that will be
used by the scripts 
 - At some point, push the head 7.0 branch of each Launchpad project to
their corresponding Github project as the new 8.0. This can be automated
I guess (using the mapping)
 - Write a script that mirrors the 6.1 and 7.0 branches to Github and
setup a cron
 
=> +1 for all 3

For this is not extra job for OCA ? at some point automated task can give us problems, personally i think move from 7.0 to github, yes its a hard job. BTW stay tuned around script. 
 
 - On Github, each project of the OCA has its own list of committers,
there is no way to put the OCA committers automatically in each OCA
project. What we'll do is to maintain 1 committer team [0] and to write
a script (with a cron) that copies all the members in all the others
projects' teams.
 - We have to decide where the OCA should deploy its tools (like the
mirroring script and committers script, and maybe others to come)

=> Commit the tools here: https://github.com/OCA/maintainers-tools
=> For running the cron, tow options:
 a) OCA buy something on one of those services : http://www.cronjobservices.com/
 b) Somebody within the OCA offer a server and access to Community Maintainers team to setup them

If you want i can setup a machine at rackspace now and give the access.


Regards, 
 

--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp




--

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Bidoul, Stéphane
In reply to this post by Guewen Baconnier @ Camptocamp
Hi,

Some comments about migration strategy below.

On Fri, Jun 20, 2014 at 3:08 PM, Guewen Baconnier <[hidden email]> wrote:

The decisions discussed so far
==============================

 - The branches up to 7.0 will stay on Launchpad
   Though, they will be mirrored on Github (Github doesn't have readonly
branches but the committers won't commit on them)
 - Starting from 8.0, they will be on Github
 - For the OCA committers and reviewers, it means that we will need to
review both on Launchpad and Github, but it avoid the need to migrate
all the pending merge proposals and bug reports
 - There is no date planned for the creation of the 8.0 branches, sooner
means more duplication of proposals (and some pain to follow the master
branch changes, which is still unstable), on the other hand, some people
already work on modules for v8.0.

Some scripts (fast-import, ...) or ideas have already been published but
I want to have a reference in this thread, so please share them.

I'm one of those who voted to keep 6.1 and 7.0 branches on launchpad.

I still think we need to keep those branches up-to-date on launchpad to 
preserve existing deployments.

I now believe however that maintenance activities should take place on
github for all branches, while maintaining launchpad as a mirror for 7.0 
and 6.1. This should facilitate development while preserving deployments.

Many of us we will have to maintain 7.0 (and 6.1) installations for
a possibly long period of time, and having everything under the
same VCS (git) will greatly facilitate the management of back and forward
ports of features and corrections.

The short term drawback I see so far is that we'd need to reapply 
current MP's to github as PR's. IMHO this is a small price to pay to reap
larger benefits on the long run.

What do you think?

Regarding tooling, I'm experimenting with git-bzr-ng (apt-get installable).
While I have not done anything fancy nor large scale yet, I could
easily migrate lp:acsone-addons from lp to github and the mirroring
workflow looks quite simple at first glance.

It looks like this:

# first create new empty repository on github

# then clone lp:acsone-addons in a new local git repo
git bzr clone lp:acsone-addons/trunk acsone-addons
# import additional branches from bzr
cd acsone-addons
git bzr import lp:acsone-addons/7.0
git bzr import lp:acsone-addons/6.1
# create a remote named origin, pointing to the github repo
git remote add origin [hidden email]:acsone/acsone-addons.git
# push the 3 branches to github
git push -u origin master
git push -u origin 7.0
git push -u origin 6.1

That was it and the git history is looking good at first glance.

Then adding stuff on github and mirroring to launchpad looks like this:

git checkout master
# ... add and commit README.md and LICENSE
# push to github
git push
# push to bzr
git bzr push

So if we decide to keep launchpad as a mirror, 
a nightly script could work like this:
- git fetch 
- for each branch: 
-    git checkout $branch
-    git bzr push
 
git-bzr maintains the mapping between git and bzr branches in .git/config.

In the end if the decision is to keep lp as the master for 7.0 and 6.1, 
the same tool could work too (git bzr sync, then git push for such branches).

I'll dig deeper next week and see what an automated script would look like in practice.

Volunteers
==========

The transition will probably need a lot of boring and tedious - more or
less manual - work. More work than can be done by a single person, so my
first concern is to compile a list of the heroes who will take part and
will accept to share the tasks.

Please announce you! and inform if you have superpowers or special
abilities that could help (git-fu, launchpad api, github api, CI, ...)

I'm in. No particular superpowers, I'm afraid :) 
For instance, I can help putting the mirroring scripts in place
I can also setup a virtual machine (at OVH) to run them.

Cheers,

-sbi


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Pedro Manuel Baeza Romero
Hi, Guewen, count with me to help in the transition.

Regards.


2014-06-21 14:09 GMT+02:00 Bidoul, Stéphane <[hidden email]>:
Hi,

Some comments about migration strategy below.

On Fri, Jun 20, 2014 at 3:08 PM, Guewen Baconnier <[hidden email]> wrote:

The decisions discussed so far
==============================

 - The branches up to 7.0 will stay on Launchpad
   Though, they will be mirrored on Github (Github doesn't have readonly
branches but the committers won't commit on them)
 - Starting from 8.0, they will be on Github
 - For the OCA committers and reviewers, it means that we will need to
review both on Launchpad and Github, but it avoid the need to migrate
all the pending merge proposals and bug reports
 - There is no date planned for the creation of the 8.0 branches, sooner
means more duplication of proposals (and some pain to follow the master
branch changes, which is still unstable), on the other hand, some people
already work on modules for v8.0.

Some scripts (fast-import, ...) or ideas have already been published but
I want to have a reference in this thread, so please share them.

I'm one of those who voted to keep 6.1 and 7.0 branches on launchpad.

I still think we need to keep those branches up-to-date on launchpad to 
preserve existing deployments.

I now believe however that maintenance activities should take place on
github for all branches, while maintaining launchpad as a mirror for 7.0 
and 6.1. This should facilitate development while preserving deployments.

Many of us we will have to maintain 7.0 (and 6.1) installations for
a possibly long period of time, and having everything under the
same VCS (git) will greatly facilitate the management of back and forward
ports of features and corrections.

The short term drawback I see so far is that we'd need to reapply 
current MP's to github as PR's. IMHO this is a small price to pay to reap
larger benefits on the long run.

What do you think?

Regarding tooling, I'm experimenting with git-bzr-ng (apt-get installable).
While I have not done anything fancy nor large scale yet, I could
easily migrate lp:acsone-addons from lp to github and the mirroring
workflow looks quite simple at first glance.

It looks like this:

# first create new empty repository on github

# then clone lp:acsone-addons in a new local git repo
git bzr clone lp:acsone-addons/trunk acsone-addons
# import additional branches from bzr
cd acsone-addons
git bzr import lp:acsone-addons/7.0
git bzr import lp:acsone-addons/6.1
# create a remote named origin, pointing to the github repo
git remote add origin [hidden email]:acsone/acsone-addons.git
# push the 3 branches to github
git push -u origin master
git push -u origin 7.0
git push -u origin 6.1

That was it and the git history is looking good at first glance.

Then adding stuff on github and mirroring to launchpad looks like this:

git checkout master
# ... add and commit README.md and LICENSE
# push to github
git push
# push to bzr
git bzr push

So if we decide to keep launchpad as a mirror, 
a nightly script could work like this:
- git fetch 
- for each branch: 
-    git checkout $branch
-    git bzr push
 
git-bzr maintains the mapping between git and bzr branches in .git/config.

In the end if the decision is to keep lp as the master for 7.0 and 6.1, 
the same tool could work too (git bzr sync, then git push for such branches).

I'll dig deeper next week and see what an automated script would look like in practice.

Volunteers
==========

The transition will probably need a lot of boring and tedious - more or
less manual - work. More work than can be done by a single person, so my
first concern is to compile a list of the heroes who will take part and
will accept to share the tasks.

Please announce you! and inform if you have superpowers or special
abilities that could help (git-fu, launchpad api, github api, CI, ...)

I'm in. No particular superpowers, I'm afraid :) 
For instance, I can help putting the mirroring scripts in place
I can also setup a virtual machine (at OVH) to run them.

Cheers,

-sbi


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Joël Grand-Guillaume @ camptocamp
Hi,


First thank you for your feedback. About the LP -> Github migration. The main arguments in favor of keeping v 6.1 and 7.0 on LP and mirror on Github is that we do have lot's of reviews in progress. It'll be difficult to maintain reviews on LP if the master is Github.

Moreover, the translation process is not clear on github, so we know that on LP everything is working fine.

Now, it's a democratic decision, if the majority of your wanna make github the main repo for all versions, so be it. I'm only giving my though here.

The responsible for that within the OCA is currently: Guewen Baconnier, Alexandre Fayolle, Stefan Rijnhart, Sébastien Beau and I. Share your point of view here and they'll make the final decision.

Regards,

Joël











On Mon, Jun 23, 2014 at 9:46 AM, Pedro Manuel Baeza Romero <[hidden email]> wrote:
Hi, Guewen, count with me to help in the transition.

Regards.


2014-06-21 14:09 GMT+02:00 Bidoul, Stéphane <[hidden email]>:
Hi,

Some comments about migration strategy below.

On Fri, Jun 20, 2014 at 3:08 PM, Guewen Baconnier <[hidden email]> wrote:

The decisions discussed so far
==============================

 - The branches up to 7.0 will stay on Launchpad
   Though, they will be mirrored on Github (Github doesn't have readonly
branches but the committers won't commit on them)
 - Starting from 8.0, they will be on Github
 - For the OCA committers and reviewers, it means that we will need to
review both on Launchpad and Github, but it avoid the need to migrate
all the pending merge proposals and bug reports
 - There is no date planned for the creation of the 8.0 branches, sooner
means more duplication of proposals (and some pain to follow the master
branch changes, which is still unstable), on the other hand, some people
already work on modules for v8.0.

Some scripts (fast-import, ...) or ideas have already been published but
I want to have a reference in this thread, so please share them.

I'm one of those who voted to keep 6.1 and 7.0 branches on launchpad.

I still think we need to keep those branches up-to-date on launchpad to 
preserve existing deployments.

I now believe however that maintenance activities should take place on
github for all branches, while maintaining launchpad as a mirror for 7.0 
and 6.1. This should facilitate development while preserving deployments.

Many of us we will have to maintain 7.0 (and 6.1) installations for
a possibly long period of time, and having everything under the
same VCS (git) will greatly facilitate the management of back and forward
ports of features and corrections.

The short term drawback I see so far is that we'd need to reapply 
current MP's to github as PR's. IMHO this is a small price to pay to reap
larger benefits on the long run.

What do you think?

Regarding tooling, I'm experimenting with git-bzr-ng (apt-get installable).
While I have not done anything fancy nor large scale yet, I could
easily migrate lp:acsone-addons from lp to github and the mirroring
workflow looks quite simple at first glance.

It looks like this:

# first create new empty repository on github

# then clone lp:acsone-addons in a new local git repo
git bzr clone lp:acsone-addons/trunk acsone-addons
# import additional branches from bzr
cd acsone-addons
git bzr import lp:acsone-addons/7.0
git bzr import lp:acsone-addons/6.1
# create a remote named origin, pointing to the github repo
git remote add origin [hidden email]:acsone/acsone-addons.git
# push the 3 branches to github
git push -u origin master
git push -u origin 7.0
git push -u origin 6.1

That was it and the git history is looking good at first glance.

Then adding stuff on github and mirroring to launchpad looks like this:

git checkout master
# ... add and commit README.md and LICENSE
# push to github
git push
# push to bzr
git bzr push

So if we decide to keep launchpad as a mirror, 
a nightly script could work like this:
- git fetch 
- for each branch: 
-    git checkout $branch
-    git bzr push
 
git-bzr maintains the mapping between git and bzr branches in .git/config.

In the end if the decision is to keep lp as the master for 7.0 and 6.1, 
the same tool could work too (git bzr sync, then git push for such branches).

I'll dig deeper next week and see what an automated script would look like in practice.

Volunteers
==========

The transition will probably need a lot of boring and tedious - more or
less manual - work. More work than can be done by a single person, so my
first concern is to compile a list of the heroes who will take part and
will accept to share the tasks.

Please announce you! and inform if you have superpowers or special
abilities that could help (git-fu, launchpad api, github api, CI, ...)

I'm in. No particular superpowers, I'm afraid :) 
For instance, I can help putting the mirroring scripts in place
I can also setup a virtual machine (at OVH) to run them.

Cheers,

-sbi


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
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



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Leonardo Pistone - camptocamp
Hi!

I am still convinced it would be somewhat less painful to have 6.1 and
7.0 in github, too.

Existing MPs scare me less, since it's a one-time problem, and it's
easy to spread the work: each person can take care to duplicate their
own MPs to github, so there is no enormous task or management needed.

On the other hand, we will continue to work on 7.0 on a long time, and
having all versions of the module on the same system, especially if
that system is git that handles multiple branches much more easily
that bzr, would make IMO our life much easier.

As an example, I imagine myself a year from now working in a module on
v8, and then backporting the same thing to v7. With two systems, that
will be a pain, whereas with git, a simple checkout/rebase should do
the trick. On the other hand, the few open MPs each one has can be
handled in an afternoon and be dealt with forever.

Whatever decision is taken I'm happy to help.

Thanks to all for the hard work!

On Mon, Jun 23, 2014 at 11:16 AM, Joël Grand-Guillaume
<[hidden email]> wrote:

> Hi,
>
>
> First thank you for your feedback. About the LP -> Github migration. The
> main arguments in favor of keeping v 6.1 and 7.0 on LP and mirror on Github
> is that we do have lot's of reviews in progress. It'll be difficult to
> maintain reviews on LP if the master is Github.
>
> Moreover, the translation process is not clear on github, so we know that on
> LP everything is working fine.
>
> Now, it's a democratic decision, if the majority of your wanna make github
> the main repo for all versions, so be it. I'm only giving my though here.
>
> The responsible for that within the OCA is currently: Guewen Baconnier,
> Alexandre Fayolle, Stefan Rijnhart, Sébastien Beau and I. Share your point
> of view here and they'll make the final decision.
>
> Regards,
>
> Joël
>
>
>
>
>
>
>
>
>
>
>
> On Mon, Jun 23, 2014 at 9:46 AM, Pedro Manuel Baeza Romero
> <[hidden email]> wrote:
>>
>> Hi, Guewen, count with me to help in the transition.
>>
>> Regards.
>>
>>
>> 2014-06-21 14:09 GMT+02:00 Bidoul, Stéphane <[hidden email]>:
>>>
>>> Hi,
>>>
>>> Some comments about migration strategy below.
>>>
>>> On Fri, Jun 20, 2014 at 3:08 PM, Guewen Baconnier
>>> <[hidden email]> wrote:
>>>>
>>>>
>>>> The decisions discussed so far
>>>> ==============================
>>>>
>>>>  - The branches up to 7.0 will stay on Launchpad
>>>>    Though, they will be mirrored on Github (Github doesn't have readonly
>>>> branches but the committers won't commit on them)
>>>>  - Starting from 8.0, they will be on Github
>>>>  - For the OCA committers and reviewers, it means that we will need to
>>>> review both on Launchpad and Github, but it avoid the need to migrate
>>>> all the pending merge proposals and bug reports
>>>>  - There is no date planned for the creation of the 8.0 branches, sooner
>>>> means more duplication of proposals (and some pain to follow the master
>>>> branch changes, which is still unstable), on the other hand, some people
>>>> already work on modules for v8.0.
>>>>
>>>> Some scripts (fast-import, ...) or ideas have already been published but
>>>> I want to have a reference in this thread, so please share them.
>>>
>>>
>>> I'm one of those who voted to keep 6.1 and 7.0 branches on launchpad.
>>>
>>> I still think we need to keep those branches up-to-date on launchpad to
>>> preserve existing deployments.
>>>
>>> I now believe however that maintenance activities should take place on
>>> github for all branches, while maintaining launchpad as a mirror for 7.0
>>> and 6.1. This should facilitate development while preserving deployments.
>>>
>>> Many of us we will have to maintain 7.0 (and 6.1) installations for
>>> a possibly long period of time, and having everything under the
>>> same VCS (git) will greatly facilitate the management of back and forward
>>> ports of features and corrections.
>>>
>>> The short term drawback I see so far is that we'd need to reapply
>>> current MP's to github as PR's. IMHO this is a small price to pay to reap
>>> larger benefits on the long run.
>>>
>>> What do you think?
>>>
>>> Regarding tooling, I'm experimenting with git-bzr-ng (apt-get
>>> installable).
>>> While I have not done anything fancy nor large scale yet, I could
>>> easily migrate lp:acsone-addons from lp to github and the mirroring
>>> workflow looks quite simple at first glance.
>>>
>>> It looks like this:
>>>
>>> # first create new empty repository on github
>>>
>>> # then clone lp:acsone-addons in a new local git repo
>>> git bzr clone lp:acsone-addons/trunk acsone-addons
>>> # import additional branches from bzr
>>> cd acsone-addons
>>> git bzr import lp:acsone-addons/7.0
>>> git bzr import lp:acsone-addons/6.1
>>> # create a remote named origin, pointing to the github repo
>>> git remote add origin [hidden email]:acsone/acsone-addons.git
>>> # push the 3 branches to github
>>> git push -u origin master
>>> git push -u origin 7.0
>>> git push -u origin 6.1
>>>
>>> That was it and the git history is looking good at first glance.
>>>
>>> Then adding stuff on github and mirroring to launchpad looks like this:
>>>
>>> git checkout master
>>> # ... add and commit README.md and LICENSE
>>> # push to github
>>> git push
>>> # push to bzr
>>> git bzr push
>>>
>>> So if we decide to keep launchpad as a mirror,
>>> a nightly script could work like this:
>>> - git fetch
>>> - for each branch:
>>> -    git checkout $branch
>>> -    git bzr push
>>>
>>> git-bzr maintains the mapping between git and bzr branches in
>>> .git/config.
>>>
>>> In the end if the decision is to keep lp as the master for 7.0 and 6.1,
>>> the same tool could work too (git bzr sync, then git push for such
>>> branches).
>>>
>>> I'll dig deeper next week and see what an automated script would look
>>> like in practice.
>>>
>>>> Volunteers
>>>> ==========
>>>>
>>>> The transition will probably need a lot of boring and tedious - more or
>>>> less manual - work. More work than can be done by a single person, so my
>>>> first concern is to compile a list of the heroes who will take part and
>>>> will accept to share the tasks.
>>>>
>>>> Please announce you! and inform if you have superpowers or special
>>>> abilities that could help (git-fu, launchpad api, github api, CI, ...)
>>>
>>>
>>> I'm in. No particular superpowers, I'm afraid :)
>>> For instance, I can help putting the mirroring scripts in place
>>> I can also setup a virtual machine (at OVH) to run them.
>>>
>>> Cheers,
>>>
>>> -sbi
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openerp-community
>>> Post to     : [hidden email]
>>> Unsubscribe : https://launchpad.net/~openerp-community
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openerp-community
>> Post to     : [hidden email]
>> 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     : [hidden email]
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Raphael Valyi
Hello,

my suggestion is: 
1) do v8 dev on Github only and as soon as we have our new branches.
2) do business as usual for some time on 6.1 and 7.0 on LP while we still work marginally on v8 and while we still have most of MP on LP with 6.1 and 7.0 MP.
3) then, as people will transition to v8, the volume of MP on Github will naturally pass the volume of work been done on LP. So we could then transition 6.1 and 7.0 maintenance on Github directly (still mirrored on LP for convenience). May be in 6 months from now.

As I said, I can help for bzr to Github migration as I have done it extensively since 1 yea for server, web and addons projects.
The thing is I'll fly back to Brazil in 2 days, so this is not exactly the moment I can help sadly.

My scripts are able to do cron synchronization of a collection of LP projects with several branches. They are minimal and need some comments. The plumbing code between the git commands is currently all done in Ruby (because this is the language I'm the most efficient with). May be 30 lines of Ruby at the moment. I'm willing to work on that to help the migration but of course I would not want spend further effort on that if that's to hear at the end that we cannot run a Ruby script or if that is double work with somebody else.

Regards.


-- 
Raphaël Valyi
Founder and consultant
+55 21 3942-2434



On Mon, Jun 23, 2014 at 7:04 AM, Leonardo Pistone <[hidden email]> wrote:
Hi!

I am still convinced it would be somewhat less painful to have 6.1 and
7.0 in github, too.

Existing MPs scare me less, since it's a one-time problem, and it's
easy to spread the work: each person can take care to duplicate their
own MPs to github, so there is no enormous task or management needed.

On the other hand, we will continue to work on 7.0 on a long time, and
having all versions of the module on the same system, especially if
that system is git that handles multiple branches much more easily
that bzr, would make IMO our life much easier.

As an example, I imagine myself a year from now working in a module on
v8, and then backporting the same thing to v7. With two systems, that
will be a pain, whereas with git, a simple checkout/rebase should do
the trick. On the other hand, the few open MPs each one has can be
handled in an afternoon and be dealt with forever.

Whatever decision is taken I'm happy to help.

Thanks to all for the hard work!

On Mon, Jun 23, 2014 at 11:16 AM, Joël Grand-Guillaume
<[hidden email]> wrote:
> Hi,
>
>
> First thank you for your feedback. About the LP -> Github migration. The
> main arguments in favor of keeping v 6.1 and 7.0 on LP and mirror on Github
> is that we do have lot's of reviews in progress. It'll be difficult to
> maintain reviews on LP if the master is Github.
>
> Moreover, the translation process is not clear on github, so we know that on
> LP everything is working fine.
>
> Now, it's a democratic decision, if the majority of your wanna make github
> the main repo for all versions, so be it. I'm only giving my though here.
>
> The responsible for that within the OCA is currently: Guewen Baconnier,
> Alexandre Fayolle, Stefan Rijnhart, Sébastien Beau and I. Share your point
> of view here and they'll make the final decision.
>
> Regards,
>
> Joël
>
>
>
>
>
>
>
>
>
>
>
> On Mon, Jun 23, 2014 at 9:46 AM, Pedro Manuel Baeza Romero
> <[hidden email]> wrote:
>>
>> Hi, Guewen, count with me to help in the transition.
>>
>> Regards.
>>
>>
>> 2014-06-21 14:09 GMT+02:00 Bidoul, Stéphane <[hidden email]>:
>>>
>>> Hi,
>>>
>>> Some comments about migration strategy below.
>>>
>>> On Fri, Jun 20, 2014 at 3:08 PM, Guewen Baconnier
>>> <[hidden email]> wrote:
>>>>
>>>>
>>>> The decisions discussed so far
>>>> ==============================
>>>>
>>>>  - The branches up to 7.0 will stay on Launchpad
>>>>    Though, they will be mirrored on Github (Github doesn't have readonly
>>>> branches but the committers won't commit on them)
>>>>  - Starting from 8.0, they will be on Github
>>>>  - For the OCA committers and reviewers, it means that we will need to
>>>> review both on Launchpad and Github, but it avoid the need to migrate
>>>> all the pending merge proposals and bug reports
>>>>  - There is no date planned for the creation of the 8.0 branches, sooner
>>>> means more duplication of proposals (and some pain to follow the master
>>>> branch changes, which is still unstable), on the other hand, some people
>>>> already work on modules for v8.0.
>>>>
>>>> Some scripts (fast-import, ...) or ideas have already been published but
>>>> I want to have a reference in this thread, so please share them.
>>>
>>>
>>> I'm one of those who voted to keep 6.1 and 7.0 branches on launchpad.
>>>
>>> I still think we need to keep those branches up-to-date on launchpad to
>>> preserve existing deployments.
>>>
>>> I now believe however that maintenance activities should take place on
>>> github for all branches, while maintaining launchpad as a mirror for 7.0
>>> and 6.1. This should facilitate development while preserving deployments.
>>>
>>> Many of us we will have to maintain 7.0 (and 6.1) installations for
>>> a possibly long period of time, and having everything under the
>>> same VCS (git) will greatly facilitate the management of back and forward
>>> ports of features and corrections.
>>>
>>> The short term drawback I see so far is that we'd need to reapply
>>> current MP's to github as PR's. IMHO this is a small price to pay to reap
>>> larger benefits on the long run.
>>>
>>> What do you think?
>>>
>>> Regarding tooling, I'm experimenting with git-bzr-ng (apt-get
>>> installable).
>>> While I have not done anything fancy nor large scale yet, I could
>>> easily migrate lp:acsone-addons from lp to github and the mirroring
>>> workflow looks quite simple at first glance.
>>>
>>> It looks like this:
>>>
>>> # first create new empty repository on github
>>>
>>> # then clone lp:acsone-addons in a new local git repo
>>> git bzr clone lp:acsone-addons/trunk acsone-addons
>>> # import additional branches from bzr
>>> cd acsone-addons
>>> git bzr import lp:acsone-addons/7.0
>>> git bzr import lp:acsone-addons/6.1
>>> # create a remote named origin, pointing to the github repo
>>> git remote add origin [hidden email]:acsone/acsone-addons.git
>>> # push the 3 branches to github
>>> git push -u origin master
>>> git push -u origin 7.0
>>> git push -u origin 6.1
>>>
>>> That was it and the git history is looking good at first glance.
>>>
>>> Then adding stuff on github and mirroring to launchpad looks like this:
>>>
>>> git checkout master
>>> # ... add and commit README.md and LICENSE
>>> # push to github
>>> git push
>>> # push to bzr
>>> git bzr push
>>>
>>> So if we decide to keep launchpad as a mirror,
>>> a nightly script could work like this:
>>> - git fetch
>>> - for each branch:
>>> -    git checkout $branch
>>> -    git bzr push
>>>
>>> git-bzr maintains the mapping between git and bzr branches in
>>> .git/config.
>>>
>>> In the end if the decision is to keep lp as the master for 7.0 and 6.1,
>>> the same tool could work too (git bzr sync, then git push for such
>>> branches).
>>>
>>> I'll dig deeper next week and see what an automated script would look
>>> like in practice.
>>>
>>>> Volunteers
>>>> ==========
>>>>
>>>> The transition will probably need a lot of boring and tedious - more or
>>>> less manual - work. More work than can be done by a single person, so my
>>>> first concern is to compile a list of the heroes who will take part and
>>>> will accept to share the tasks.
>>>>
>>>> Please announce you! and inform if you have superpowers or special
>>>> abilities that could help (git-fu, launchpad api, github api, CI, ...)
>>>
>>>
>>> I'm in. No particular superpowers, I'm afraid :)
>>> For instance, I can help putting the mirroring scripts in place
>>> I can also setup a virtual machine (at OVH) to run them.
>>>
>>> Cheers,
>>>
>>> -sbi
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openerp-community
>>> Post to     : [hidden email]
>>> Unsubscribe : https://launchpad.net/~openerp-community
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openerp-community
>> Post to     : [hidden email]
>> 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
>
> <a href="tel:%2B41%2021%20619%2010%2028" value="+41216191028">+41 21 619 10 28
> www.camptocamp.com
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : [hidden email]
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

eLBatti
In reply to this post by Joël Grand-Guillaume @ camptocamp
On 06/23/2014 11:16 AM, Joël Grand-Guillaume wrote:
Hi,


First thank you for your feedback. About the LP -> Github migration. The main arguments in favor of keeping v 6.1 and 7.0 on LP and mirror on Github is that we do have lot's of reviews in progress. It'll be difficult to maintain reviews on LP if the master is Github.

We could follow the same approach as OpenERP SA:
https://github.com/odoo/odoo/wiki/GitHub-Transition

About merge proposals, the page says:
Whenever such a MP is merged it will be forwarded to GitHub using this script.
But that link doesn't take to the script.

Does anybody know such a script?

-- 
Lorenzo Battistini


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Guewen Baconnier @ Camptocamp
On Mon, Jun 23, 2014 at 12:58 PM, Lorenzo Battistini
<[hidden email]> wrote:

> On 06/23/2014 11:16 AM, Joël Grand-Guillaume wrote:
>
> Hi,
>
>
> First thank you for your feedback. About the LP -> Github migration. The
> main arguments in favor of keeping v 6.1 and 7.0 on LP and mirror on Github
> is that we do have lot's of reviews in progress. It'll be difficult to
> maintain reviews on LP if the master is Github.
>
>
> We could follow the same approach as OpenERP SA:
> https://github.com/odoo/odoo/wiki/GitHub-Transition
>
> About merge proposals, the page says:
> Whenever such a MP is merged it will be forwarded to GitHub using this
> script.
> But that link doesn't take to the script.
>
> Does anybody know such a script?

The script is here http://nightly.openerp.com/move-branch.zip
But it seems that it does a lot of plumbing for the merge of the
addons, server and web branches.

We have to write a similar, simpler script to move the branches to
Github so I tend to think that it can be used for proposed branches
too.

>
> --
> Lorenzo Battistini
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : [hidden email]
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Guewen Baconnier @ Camptocamp
In reply to this post by Leonardo Pistone - camptocamp
On Mon, Jun 23, 2014 at 12:04 PM, Leonardo Pistone
<[hidden email]> wrote:

> Hi!
>
> I am still convinced it would be somewhat less painful to have 6.1 and
> 7.0 in github, too.
>
> Existing MPs scare me less, since it's a one-time problem, and it's
> easy to spread the work: each person can take care to duplicate their
> own MPs to github, so there is no enormous task or management needed.
>
> On the other hand, we will continue to work on 7.0 on a long time, and
> having all versions of the module on the same system, especially if
> that system is git that handles multiple branches much more easily
> that bzr, would make IMO our life much easier.
>
> As an example, I imagine myself a year from now working in a module on
> v8, and then backporting the same thing to v7. With two systems, that
> will be a pain, whereas with git, a simple checkout/rebase should do
> the trick. On the other hand, the few open MPs each one has can be
> handled in an afternoon and be dealt with forever.
>
> Whatever decision is taken I'm happy to help.
>
> Thanks to all for the hard work!
>

I start to have the same feeling. I'm also thinking about the reviews.
Doing them on 2 platforms, with different tools would not help, I even
fear that reviewers / committers would slowly forsake the launchpad
merge proposals as the time passes due to the hard feeling they have
regarding launchpad vs github and their easiness of review.

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Info SHS-AV
In reply to this post by eLBatti

Il 23/06/2014 12:58, Lorenzo Battistini ha scritto:
On 06/23/2014 11:16 AM, Joël Grand-Guillaume wrote:
Hi,


First thank you for your feedback. About the LP -> Github migration. The main arguments in favor of keeping v 6.1 and 7.0 on LP and mirror on Github is that we do have lot's of reviews in progress. It'll be difficult to maintain reviews on LP if the master is Github.

+1
We could follow the same approach as OpenERP SA:
https://github.com/odoo/odoo/wiki/GitHub-Transition

About merge proposals, the page says:
Whenever such a MP is merged it will be forwarded to GitHub using this script.
But that link doesn't take to the script.

Does anybody know such a script?

-- 
Lorenzo Battistini



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

--

Antonio M. Vigliotti
(Presidente & Chief Technical Officer)


SHS-AV s.r.l. (impresa innovativa)
zero
incombenze®

Via Domodossola, 64 - 10145 TORINO - ITALY

Tel. (+39) 011.0566929(2)

www.shs-av.com

PEC [hidden email]


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Guewen Baconnier @ Camptocamp
In reply to this post by Guewen Baconnier @ Camptocamp
I started to work on the tools:

https://github.com/OCA/maintainers-tools

The first script is the one that copies the members of the maintainers
team to the other teams.
The branch also contains a function to login on GitHub using a token,
that should be shared by all the other scripts.
The other OCA scripts should share the same repo.

Wiki for the migration:
https://github.com/OCA/maintainers-tools/wiki

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Mignon, Laurent
In reply to this post by Info SHS-AV
HI,

I am also in favor of an earlier migration to github. We are a community, and as such I would like to avoid introducing processes and tools that would be specific OCA. The greater part of us probably have enough experience to continue with both systems and even if IMHO it will introduce a lot of unnecessary complexity. However, if we want to remain / become an attractive and open community that can only be done if we use the tools of the community based on non-specific process to OCA. 

How to explain to a new contributor that he must know launchpad to contribute to OCA modules in 7.0 and  Github for 8.0?
Are our employers willing to bear the cost of training launchpad and github? Not to mention the specific processes introduced by OCA to support this duality ...

If OCA remains on launchpad while Odoo is on github, I feel we may see a large number of OCA modules migrated to Github outside the control of OCA because people simply find it easier to have everything on Github and will want to avoid further invest in launchpad.

One last point, I am one of those who blames Odoo not always follow community practices whether in terms of formatting code (pep8) or in the packaging of addons (python eggs). At the transition from launchpad to github, I'd avoid that OCA introduce its own processes and tools to support both systems simultaneously.

I think if we do not choose now to migrate everything to Github, it will never be possible.

My 2 cents,

lmi



On Mon, Jun 23, 2014 at 1:43 PM, Info SHS-AV <[hidden email]> wrote:

Il 23/06/2014 12:58, Lorenzo Battistini ha scritto:
On 06/23/2014 11:16 AM, Joël Grand-Guillaume wrote:
Hi,


First thank you for your feedback. About the LP -> Github migration. The main arguments in favor of keeping v 6.1 and 7.0 on LP and mirror on Github is that we do have lot's of reviews in progress. It'll be difficult to maintain reviews on LP if the master is Github.

+1
We could follow the same approach as OpenERP SA:
https://github.com/odoo/odoo/wiki/GitHub-Transition

About merge proposals, the page says:
Whenever such a MP is merged it will be forwarded to GitHub using this script.
But that link doesn't take to the script.

Does anybody know such a script?

-- 
Lorenzo Battistini



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

--

Antonio M. Vigliotti
(Presidente & Chief Technical Officer)


SHS-AV s.r.l. (impresa innovativa)
zero
incombenze®

Via Domodossola, 64 - 10145 TORINO - ITALY

Tel. <a href="tel:%28%2B39%29%20011.0566929" value="+390110566929" target="_blank">(+39) 011.0566929(2)

www.shs-av.com

PEC [hidden email]


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp




--
Laurent Mignon
Senior Software Engineer

Tel : +352 20 21 10 20 32
Fax : +352 20 21 10 21
Gsm : +352 691 506 009
Email: [hidden email]

Acsone SA, Succursale de Luxembourg
22, Zone industrielle
L-8287 Kehlen, Luxembourg



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Moises Lopez

Hello,
+1 with full migration to github... with scripts.

In github you will have new runbot available with PR for test it.
In github you will have just one tool of version control.
And you can make some script to migrate base branches and merge proposal branches.

Note, in old runbot refactory by vauxoo we check the MP here:
http://bazaar.launchpad.net/~vauxoo/openerp-tools/runbot7_vauxoo_stable/view/head:/openerp-runbot/openerprunbot/core.py#L715

We can use same concept to migrate MP to github.

*Bugs and blueprint to issue.

Translation Olivier told us:
""""
" 7. Translations [Planned Q3 2014]
The v8 release is too soon to allow setting up a new translation process on top
of GitHub, especially as there is almost nothing built-in.

Translators will still continue to work on LP at least until v8 is released. We
will set up a replay system to update the translation templates
`addons/i18n/*.pot` on LP with the latest terms from master/v8.0 in GitHub. And
in the other direction, we will replay the PO updates on `addons/i18n/*.po`
from LP to GitHub.

After the release of v8 we will set up a new translation process, probably
built on top of Transifex."
"""

*TODO script.

We can help with dev of this script in python if you like it.

El jun 23, 2014 8:07 AM, "Mignon, Laurent" <[hidden email]> escribió:
HI,

I am also in favor of an earlier migration to github. We are a community, and as such I would like to avoid introducing processes and tools that would be specific OCA. The greater part of us probably have enough experience to continue with both systems and even if IMHO it will introduce a lot of unnecessary complexity. However, if we want to remain / become an attractive and open community that can only be done if we use the tools of the community based on non-specific process to OCA. 

How to explain to a new contributor that he must know launchpad to contribute to OCA modules in 7.0 and  Github for 8.0?
Are our employers willing to bear the cost of training launchpad and github? Not to mention the specific processes introduced by OCA to support this duality ...

If OCA remains on launchpad while Odoo is on github, I feel we may see a large number of OCA modules migrated to Github outside the control of OCA because people simply find it easier to have everything on Github and will want to avoid further invest in launchpad.

One last point, I am one of those who blames Odoo not always follow community practices whether in terms of formatting code (pep8) or in the packaging of addons (python eggs). At the transition from launchpad to github, I'd avoid that OCA introduce its own processes and tools to support both systems simultaneously.

I think if we do not choose now to migrate everything to Github, it will never be possible.

My 2 cents,

lmi



On Mon, Jun 23, 2014 at 1:43 PM, Info SHS-AV <[hidden email]> wrote:

Il 23/06/2014 12:58, Lorenzo Battistini ha scritto:
On 06/23/2014 11:16 AM, Joël Grand-Guillaume wrote:
Hi,


First thank you for your feedback. About the LP -> Github migration. The main arguments in favor of keeping v 6.1 and 7.0 on LP and mirror on Github is that we do have lot's of reviews in progress. It'll be difficult to maintain reviews on LP if the master is Github.

+1
We could follow the same approach as OpenERP SA:
https://github.com/odoo/odoo/wiki/GitHub-Transition

About merge proposals, the page says:
Whenever such a MP is merged it will be forwarded to GitHub using this script.
But that link doesn't take to the script.

Does anybody know such a script?

-- 
Lorenzo Battistini



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

--

Antonio M. Vigliotti
(Presidente & Chief Technical Officer)


SHS-AV s.r.l. (impresa innovativa)
zero
incombenze®

Via Domodossola, 64 - 10145 TORINO - ITALY

Tel. <a href="tel:%28%2B39%29%20011.0566929" value="+390110566929" target="_blank">(+39) 011.0566929(2)

www.shs-av.com

PEC [hidden email]


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp




--
Laurent Mignon
Senior Software Engineer

Tel : +352 20 21 10 20 32
Fax : +352 20 21 10 21
Gsm : +352 691 506 009
Email: [hidden email]

Acsone SA, Succursale de Luxembourg
22, Zone industrielle
L-8287 Kehlen, Luxembourg



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Guewen Baconnier @ Camptocamp
On Mon, Jun 23, 2014 at 3:32 PM, Moises Lopez <[hidden email]> wrote:

Hello,
+1 with full migration to github... with scripts.  

In github you will have new runbot available with PR for test it.
In github you will have just one tool of version control.
And you can make some script to migrate base branches and merge proposal branches.

As far as I agree that we should migrate the base branches, I don't think that we should migrate merge proposals.
The proposed branches should be owned by the ones who proposed a branch, not by the OCA organization.
But at least we should help the contributors with a nice how-to.

Note, in old runbot refactory by vauxoo we check the MP here:
http://bazaar.launchpad.net/~vauxoo/openerp-tools/runbot7_vauxoo_stable/view/head:/openerp-runbot/openerprunbot/core.py#L715

We can use same concept to migrate MP to github.

*Bugs and blueprint to issue.

Translation Olivier told us:
""""
" 7. Translations [Planned Q3 2014]
The v8 release is too soon to allow setting up a new translation process on top
of GitHub, especially as there is almost nothing built-in.

Translators will still continue to work on LP at least until v8 is released. We
will set up a replay system to update the translation templates
`addons/i18n/*.pot` on LP with the latest terms from master/v8.0 in GitHub. And
in the other direction, we will replay the PO updates on `addons/i18n/*.po`
from LP to GitHub.

After the release of v8 we will set up a new translation process, probably
built on top of Transifex."
"""

*TODO script.


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] OCA: transition from Launchpad to Github

Joël Grand-Guillaume @ camptocamp
Ok, I agree on the principle as well (moving to github with mirroring on LP). I let the responsiblity to gather the opinions and take the decision to you Guewen.


On Mon, Jun 23, 2014 at 4:00 PM, Guewen Baconnier <[hidden email]> wrote:
On Mon, Jun 23, 2014 at 3:32 PM, Moises Lopez <[hidden email]> wrote:

Hello,
+1 with full migration to github... with scripts.  

In github you will have new runbot available with PR for test it.
In github you will have just one tool of version control.
And you can make some script to migrate base branches and merge proposal branches.

As far as I agree that we should migrate the base branches, I don't think that we should migrate merge proposals.
The proposed branches should be owned by the ones who proposed a branch, not by the OCA organization.
But at least we should help the contributors with a nice how-to.

Note, in old runbot refactory by vauxoo we check the MP here:
http://bazaar.launchpad.net/~vauxoo/openerp-tools/runbot7_vauxoo_stable/view/head:/openerp-runbot/openerprunbot/core.py#L715

We can use same concept to migrate MP to github.

*Bugs and blueprint to issue.

Translation Olivier told us:
""""
" 7. Translations [Planned Q3 2014]
The v8 release is too soon to allow setting up a new translation process on top
of GitHub, especially as there is almost nothing built-in.

Translators will still continue to work on LP at least until v8 is released. We
will set up a replay system to update the translation templates
`addons/i18n/*.pot` on LP with the latest terms from master/v8.0 in GitHub. And
in the other direction, we will replay the PO updates on `addons/i18n/*.po`
from LP to GitHub.

After the release of v8 we will set up a new translation process, probably
built on top of Transifex."
"""

*TODO script.


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
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



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
12345