← Back to team overview

openerp-community team mailing list archive

Re: New booking chart and web core modules

 

Sorry, I'm trying to understand the situation and found the best solution :)

I'm not sure to understand this:/
/

   /Then the branch of the
   //https://code.launchpad.net/~openerp-community/web-addons/7.0-web-unleashed
   <https://code.launchpad.net/%7Eopenerp-community/web-addons/7.0-web-unleashed>/
   ///is on the right place, but it contains a branch replicated from
   github... That prevent any merge to be done in the "official"
   community branch here : //lp:web-addons
   <https://code.launchpad.net/%7Ewebaddons-core-editors/web-addons/7.0>/

From what I see, the repository on launchpad is a clone of the github one... and new revision on github will be sync automatically on launchpad from what I understand (with a delay, but it's not really an issue).

So maybe the problem is because web-unleashed is not a fork of web-addons ?
If yes, it's mean any new module has to be based on an "official" community branch (with all side modules, not directly related) ?

Regards,



On 11/06/2013 08:15 PM, Nhomar Hernández wrote:

2013/11/6 Joël Grand-Guillaume <joel.grandguillaume@xxxxxxxxxxxxxx <mailto:joel.grandguillaume@xxxxxxxxxxxxxx>>


    My personnal opinion is that people who want to push their
    contribs in the OpenERP community should do it be requesting a
    merge of their work in the "official" branches. That also means
    adpot Launchpad and Bazaar as the VCS...

    Any opinion here ? Idea how to manage that ?


IMHO I think somebody in community which like git should develop some kind of sync tool or something like that.

bzr has some of them:

http://askubuntu.com/questions/96176/how-can-i-migrate-an-application-from-github-to-launchpad

bzr-git plugin.

And viceversa (from bzr to git).

https://groups.google.com/forum/#!topic/cairoplot/ugdh-SLrl0k <https://groups.google.com/forum/#%21topic/cairoplot/ugdh-SLrl0k>

But BTW I really think until we don't have other option, this must be done manually by the developer:

A.- pull from git commit and push in "both" with bzr-git can be an option.

note: Obviously if somebody has some "Auto" plugin to do both at same time excellent.

*In terms of process:*

In terms of process always pull the branch from what you want to start to work - do your job - commit and push on lp and your own git.

It is only an option.

Only as a thought community:

For Contributors: Waste time making things on github is really harmfull for the "Organization" we are trying to do here, several actual tools are already done (and WiP) to help everybody (Users and Integrators) work with all the "Process" already implemented, If we lost what we got until now we will brake a lot of things, It is not a matter of "Ask a pull request" __only__ There are a lot of "process" to comply with and It is (again IMHO) a bad wasting of time.

For actual community members: Maybe we need more centralized documentation about this transitions between several CVS to LP and/or viceversa who can be in charge of that and we can put it on doc.openerp.com <http://doc.openerp.com>¿?

Then mixing clear rules (more clear even than what we have today) with clear documentation it will help a lot.

Note: We are almost sure from time to time we will be able to manage all the CVS in the market but until then, help us to help you.

Regards.

--
--------------------
Saludos Cordiales

Nhomar G. Hernandez M.
+58-414-4110269
Skype: nhomar00
Web-Blog: http://geronimo.com.ve <http://geronimo.com.ve/>
Servicios IT: http://vauxoo.com <http://vauxoo.com/>
Linux-Counter: 467724
Correos:
nhomar@xxxxxxxxxxxxxx <mailto:nhomar@xxxxxxxxxxxxxx>
nhomar@xxxxxxxxxx <mailto:nhomar@xxxxxxxxxx>
twitter @nhomar


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp


Follow ups

References