openerp-community team mailing list archive

[Joël Grand-Guillaume <joel.grandguillaume@xxxxxxxxxxxxxx>]

Hi,


This is not a "light" topic.... I agree of the need, and suggest the
following rules:


 * Never put "odoo-" as repo name => this way, we have a github address
like : git@xxxxxxxxxx:OCA/connector.git and not
git@xxxxxxxxxx:OCA/odoo-connector.git
=> We all know that modules we make is about Odoo, no need to repeat that
in the name. Moreover, if they change the name again, no more extra-work
for us ;)
E.g. odoo-travel must be just "travel" or in this case, because it's
vertial : "vertical-travel".

 * The word "logistic" is renamed everywhere with "logistics"
e.g. E.g. "stock-logistic-tracking" must be "stock-logistics-tracking"

 * We do remove the mgmt or management everywhere. It makes it simplier to
read and use and what matter here is the subject. The exception is for
https://github.com/OCA/mgmtsystem that stay like this as it correspond to a
reality
e.g. "department-mgmt" become "department".

 * Remove "addons" prefix or suffix everywhere. We know it's about addons.
e.g. "banking-addons" -> "banking"

 * All PSC referenced as Vertical here :
http://odoo-community.org/page/website.List are prefixed with "vertical-"
so if we type vertical in the search on Github, we can have all available
verbalization at a glance. e.g. "isp" become "vertical-isp" and
"ngo-addons" become "vertical-ngo"

 * The same for localization (here again:
http://odoo-community.org/page/website.List). We prefix them all with
"local-" so typing local will show all available one. e.g. "france" become
"local-france"

 * All connector are already prefixed with "connector" so i'ts ok.

 * For all others, verify that the first name is the name of the main Odoo
official module like "product-kitting" or "sale-wkfl".


TODO on every rennamed repo (as Guewen pointed out) :

 - rename it on GitHub
 - change the link on odoo-community.org
 - change the mapping for the migration


Anybody want to make all the work. Honestly we're running low on resources
and already give our best to build all of this...

Anybody that can give time here can answer here and take contact with
Guewen.

Thanks


Regards,

Joël



On Fri, Jun 27, 2014 at 1:08 PM, Guewen Baconnier <
guewen.baconnier@xxxxxxxxxxxxxx> wrote:

> Hello Yannick,
>
> Only the owners of the OCA's project on GitHub (so the Board's
> members) have the rights to rename the repositories.
> Renaming a repository implies to:
>  - rename it on GitHub
>  - change the link on odoo-community.org
>  - change the mapping for the migration
>
> But you are right, we must do it right now when nobody is using them yet.
>
> On Fri, Jun 27, 2014 at 12:03 PM, Yannick Vaucher
> <yannick.vaucher@xxxxxxxxxxxxxx> wrote:
> > Hello dear community,
> >
> > I think we could take the opportunity to improve a bit our oca github
> > repositories by renaming some of them to make them to fix some
> > inconsistencies.
> >
> > For exemple, branch for reports are named report or reports
> > I would suggest that as for 'tools' we use plural for reports
> >
> > account-financial-report >> account-financial-reports
> > account-invoice-report >> account-invoice-reports
> > sale-reports
> > stock-logistic-report >> stock-logistic-reports
> > manufacture-reports
> >
>
> +1
> Also, logistics takes a final 's':
> stock-logistics-warehouse
> stock-logistics-tracking
> stock-logistics-reports
> stock-logistics-flows
> stock-logistics-barcode
>
> >
> >
> > An other one is for management. Sometimes it is mgmt and sometimes
> > management.
> > My suggestion, use always mgmt instead of management.
> > Other question is this term always necessary ?
>
> +1
> I would not be against the removal of -mgmt:
> contract
> commission
> department
> ...
>
> >
> > contract-management >> contract-mgmt
> > commission-mgmt
> > crm-mgmt
> > department-mgmt
> > edition-mgmt >> *
> > hotel-management-system >> *
> > hr-mgmt
> > manufacture-mgmt >> manufacture ?
> > mgmtsystem >> mgmt-system
> > partner-contact-management >> partner-contact-mgmt
> > program-mgmt
> > rma-mgmt
> > travel-mgmt >> *
> >
> > (*) see bellow vertical integration
> >
> >
> >
> > Is "addons" necessary? We knows those branches are for addons right?
> >
> > e-commerce-addons >> e-commerce
> > geospatial-addons >> geospatial
> > knowledge-addons >> knowledge
> > banking-addons >> banking
> > ngo-addons >> *
> > web-addons
>
> + 1 to remove -addons
>
> >
> > (*) see bellow vertical integration
> >
> >
> >
> > * Vertical Integrations
> > Shouldn't we keep a keyword for vertical integration branches?
> > to mean it aims a complete solution, we could add odoo before it
> >
> > hotel-management-system >> odoo-hotel
> > construction >> odoo-construction
> > medical >> odoo-medical
> > isp >> odoo-isp
> > edition-mgmt >> odoo-edition
> > ngo-addons >> odoo-ngo
> > travel-mgmt >> odoo-travel
>
> Maybe. No opinion here.
>
> See you
> Guewen
>
> _______________________________________________
> 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
>



-- 


*camptocamp*
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

*Joël Grand-Guillaume*
Division Manager
Business Solutions

+41 21 619 10 28
www.camptocamp.com