Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: Renaming OCA/project-service to OCA/vertical-service
Re: Renaming OCA/project-service to OCA/vertical-service
Re: Renaming OCA/project-service to OCA/vertical-service
byMaxime Chambreuil
+1 (514) 276-5468 #126
----- Le 30 Aoû 15, à 12:23, Daniel Reis <dgreis@sapo.pt> a écrit :
Hello all,
I initialized the 8.0 branch for the OCA/contract repository.
All is ready to receive new modules.
An admin is still needed to:
- make 8.0 the default branch and delete master
- create the milestones (8.0 at least)
- rename the OCA/vertical-service to OCA/project
Thanks!
Citando Eric Caudal (Elico Corp) <eric.caudal@elico-corp.com>:
+1One procedure onlySent from my Samsung device
-------- Original message --------
From: Maxime Chambreuil <maxime.chambreuil@savoirfairelinux.com>
Date: 2015/08/30 03:22 (GMT+08:00)
To: OCA Contributors <contributors@odoo-community.org>
Subject: Re: Renaming OCA/project-service to OCA/vertical-service
+1--
Maxime Chambreuil
+1 (514) 276-5468 #126
----- Le 29 Aoû 15, à 12:38, <Pedro@pad.odoo-community.org> a écrit :
For me it's clear: they should all pass through a review process in a per module basis to assure OCA guidelines are applied from the beginning.Regards.
2015-08-29 17:52 GMT+02:00 Daniel Reis <dgreis@sapo.pt>:One last question regarding the how:Should we accept a bulk unreviewed merge and do thorough reviews when porting to v9 (like what happened to hr), or go through a module by module review as usual?
--DROK, let's go for this approach.Regards.
2015-08-29 16:53 GMT+02:00 Eric Caudal <eric.caudal@elico-corp.com>:Sounds reasonable to me too
--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APACOn 08/29/2015 10:08 PM, Maxime Chambreuil wrote:<blockquote cite="mid:1039147872.755160.1440856526183.JavaMail.zimbra@savoirfairelinux.com" type="cite">> Daniel, we have done this move because there's a proposal for > including a bunch of contract-related modules. In concrete, these > ones: https://github.com/Domatix/maintenance-contract, so please redo > again your proposal so we can achieve an agreement. > Thank you for sharing the proposal Pedro. These modules look like a nice addition. They extend Odoo Contracts without using Project features, going as far as to create Work Orders without reusing Project Tasks. It's a possible approach with it's own merits, and is not incompatible with the Project task approach. In my opinion the existing "OCA/contract" is the best fit and should be reactivated to host them. The Project related modules should stay in the "OCA/project" repository. Both repos should be coordinated by the same PSC. --Daniel_______________________________________________
Mailing-List: http://odoo-community.org/groups/oca-contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: http://odoo-community.org/groups/oca-contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: http://odoo-community.org/groups/oca-contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: http://odoo-community.org/groups/oca-contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: http://odoo-community.org/groups/oca-contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: http://odoo-community.org/groups/oca-contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: http://odoo-community.org/groups/oca-contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: http://odoo-community.org/groups/oca-contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: http://odoo-community.org/groups/oca-contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe
Reference
-
Re: Renaming OCA/project-service to OCA/vertical-service
byElico Corp, Eric Caudal-
Re: Renaming OCA/project-service to OCA/vertical-service
byClosingAp Open Source Integrators Europe, LDA, Daniel Reis -
Re: Renaming OCA/project-service to OCA/vertical-service
byTecnativa. S. L., Pedro M. Baeza -
Re: Renaming OCA/project-service to OCA/vertical-service
byOpen Source Integrators, Maxime Chambreuil -
Re: Renaming OCA/project-service to OCA/vertical-service
byTecnativa. S. L., Pedro M. Baeza -
Re: Renaming OCA/project-service to OCA/vertical-service
byOpen Source Integrators, Maxime Chambreuil -
Re: Renaming OCA/project-service to OCA/vertical-service
byClosingAp Open Source Integrators Europe, LDA, Daniel Reis
-