openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #06269
Re: OCA repositories naming convention
Hi Guewen and all,
+1 to have better names
+1 to remove management/mgmt and addons
But Guewen say :
Also, logistics takes a final 's':
> stock-logistics-warehouse
> stock-logistics-tracking
> stock-logistics-reports
> stock-logistics-flows
> stock-logistics-barcode
1/ I don't think we must add 's' to logistic.
May be i'm wrong but isn't it 'report' of logistic kind (or stock-logistic
type), then report must be plural but not logistic.
If plural must be define could be
stock-logistic-warehouses
stock-logistic-flows
2/ in fact isn't it easier to avoid plural : all concept in the repository
are 'collection of' (warehouse, report, partner, etc)
In a database table name have no plural (except res_users ;'-( )
David BEAL
Akretion
Odoo Development - Integration
+33 (0)6 67 22 86 89
+33 (0)4 82 53 84 60
2014-06-27 13:08 GMT+02:00 Guewen Baconnier <guewen.baconnier@xxxxxxxxxxxxxx
>:
> 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
>
Follow ups
References