1. Mailing Lists
  2. Contributors
  3. Re: Move setuptools-odoo to OCA

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Move setuptools-odoo to OCA

Re: Move setuptools-odoo to OCA

Avatar

Re: Move setuptools-odoo to OCA

by
Acsone SA, Succursale de Luxembourg, Adrien Peiffer
- 14/04/2016 16:40:42
+1

Adrien PEIFFER,

Software Engineer

Tel : +352 20 21 10 20
Mobile: +352 691 506 100

Acsone sa/nv
22, Zone Industrielle | L-8287 KEHLEN  | Luxembourg
www.acsone.eu

2016-04-14 16:08 GMT+02:00 Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com>:
+1 thanks a lot for all this work

On Thu, Apr 14, 2016 at 1:08 AM, Eric Caudal <eric.caudal@elico-corp.com> wrote:

+1 for a generic tool
Thanks Stéphane for this huge contribution

--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 04/14/2016 06:22 AM, Nhomar Hernandez wrote:
<blockquote cite="mid:CAKtu5Y7k=1kCaT3zWzTZ5AXF-VgGu3dEvJPkqx-TnRbc+0Kbvw@mail.gmail.com" type="cite">
Hello.

Absollutly agree it is a +4 for me also.

Just 1 condition on my side....

This must evolve as a very well documented example of how do things, following some specific examples on how manage the package.[2]

I mean some proposals:

1.- It's own gh-pages (or readthedocs). [I prefer gh-pages]
2.- Its own sphinx project.
3.- Document the rationale behind it (the why's will not be OCA why's will be so generic why's).
4.- A very well documented package manager (something already done like the ones I shared in the previos topic) [1].
5.- We need have a cookiecuter-template that help us prepare future repositories[3]


[1] I can prepare specific ideas on oca repository once it is done.
[2] I propose myself as PSC also for this project I am doing this job for internal propose BTW, then merge my internal objective with the OCA's ones is REALLY a better approach for us.
[3] More precise comments on official repo.


On Wed, Apr 13, 2016 at 3:38 PM, <Bidoul@pad.odoo-community.org> wrote:
Nhomar requested [0] that the setuptools-odoo repo [1] and it's companion odoo-autodiscover [2] move from Acsone to OCA umbrella.

I personally think it's a good idea.

I would request only one additional condition to usual OCA rules: that is that these tool do not become OCA-specific, ie continue to be able to package any Odoo addon.
OCA specific tools such as [3] can of course be built on top of setuptools-odoo.

To manage these tools, I suggest the creation of a new Packaging PSC of which I would be honored to be the OCA representative.

Thoughts? Votes?




--
Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Skype: nhomar00 (Envia mail previo no lo superviso siempre).
Móvil Venezuela:
+58 4144110269
Móvil México:
+52 1 4773933942

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


Reference