Contributors mailing list archives
Re: Move setuptools-odoo to OCAby
Vauxoo, Nhomar Hernández
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.
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) .
5.- We need have a cookiecuter-template that help us prepare future repositories
 I can prepare specific ideas on oca repository once it is done.
 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.
 More precise comments on official repo.
On Wed, Apr 13, 2016 at 3:38 PM, <Bidoul@pad.odoo-community.org> wrote:
Nhomar requested  that the setuptools-odoo repo  and it's companion odoo-autodiscover  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  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?