Odoo Community Association: First General Assembly on June 5th in Louvain

Odoo Community Association▸ Read this press release in: FR | ES | PT | NL

Following the recent announcements made by OpenERP SA, now renamed Odoo, the OpenERP Community Association has decided to rename itself into the “Odoo Community Association” (odoo-community-association.org) and to move its activities from Launchpad to GitHub.

OCA Mission

The OCA mission is to support the collaborative development of the Odoo features, and to promote the widespread use of Odoo by :

  • Helping and promoting the collaborative software development of Odoo;
  • Encouraging the development of Odoo and its features while coordinating and organizing the collaborative work on the software;
  • Assisting the community while defending its interests and the sustainability of its developments;
  • Promoting the use of the Odoo solution;
  • Facilitating synergies, collaborations and fund raising efforts;
  • Actively collaborating on the definition of the roadmaps of new versions of the tool and their implementation.

First OCA General Assembly

During the OpenDays 2014, the first general assembly of charter members will be held on June the 5th at 5:50pm in Hocaille room.

  • The first step to joining the general assembly is by filling the form at http://sflx.ca/ocaga
  • By joining the OCA as a member before the OpenDays, you will make yourself eligible to become a charter member, apply to the first board and elect it.

For more details regarding OCA membership, please visit our web site.

Make your voice heard

The OCA is willing to get your feedbacks and ideas to represent your interests in our next meeting with Odoo. Please fill in the survey available at http://ow.ly/x8n1E

About the OCA

The Odoo Community Association, or OCA, is a nonprofit organization whose mission is to support the collaborative development of the Odoo features, and to promote the widespread use of Odoo. The association provides financial, organizational and legal support to the broader Odoo Open Source community. It also serves as an independent legal entity to which community members can contribute the code, the funding and other resources, with the knowledge that their contributions will be maintained for public benefit.

▸ More info on odoo-community-association.org
▸ For any questions, please contact oca-board AT lists.launchpad DOT net

OpenERP becomes Odoo

odooBig news from Grand-Rosière, Belgium, this morning:
 

OpenERP is moving into new territories, beyond ERP. Over the past weeks, we released an open source CMS, a disruptive eCommerce and a Business Intelligence engine. Integrating your sales floor with inventory, accounting and manufacturing plant is one thing. But we think modern companies deserve more than this.

Great companies should integrate all their sales channels: point of sale, eCommerce, inbound sales. Great companies need to have strong inbound marketing activities linked to a 360° reporting engine and to their CRM. Great companies need their project management application linked to their timesheets, financial and accounting applications.

With 3.000+ apps, OpenERP is unique. No other product allows such a level of integration out-of-the-box. For these reasons we think it’s time to differentiate OpenERP from traditional ERP players. There is no comparison anymore.

So, we renamed the product and company into “Odoo”.

Read more on odoo.com

Launching The OpenERP Community Association

oerpcommunity-logoFive major OpenERP community and business partners have launched this week the OpenERP Community Association, or OCA, a not-for-profit organization based in Switzerland whose mission is to support the collaborative development of OpenERP features, and promote its widespread use. As one of the major North-American partners and contributors of OpenERP, Savoir-faire Linux is naturally one of them.

ISO Management Systems with OpenERP

Savoir-faire Linux have been developing OpenERP modules to help you manage your management systems. Whether for Quality (ISO9001), Environment (ISO14001) or Security (ISO27001), you will be able to :

  • Schedule your audit calendar
  • Assign the auditors
  • Print your verification list
  • Print your audit report
  • Manage your nonconformities, with origins, causes and procedures
  • Manage your immediate, corrective and preventive actions
  • Manage your improvement opportunities
  • Have a quick overview of your management system with a dashboard

The 4 modules :

  • mgmtsystem
  • mgmtsystem_action
  • mgmtsystem_nonconformity
  • mgmtsystem_audit

includes demo data and are available in : https://code.launchpad.net/~openerp-community/openobject-addons/mgmtsystem

OpenERP – Merged l10n_modules. Thank you, OpenERP Community.

You might have noticed that we merged some of what our community contributed regarding the l10n_ modules. You can see the complete list of the merged modules here:

http://bazaar.launchpad.net/~openerp/openobject-addons/trunk/files

We would like to thank all our contributors for the various localisation modules. Everybody from openerp-expert-accouting and openerp-expert-localization, and all the people we forgot to mention in the following list:

  • l10n_ar Luis Falcon (Thymbra)
  • l10n_br Raphael Valyi (Akretion)
  • l10n_ca Maxime Chambreuil (Savoir-faire Linux)
  • l10n_ch Joel Grandguillaume (Camptocamp sa)
  • l10n_cr Carlos Vasquez (ClearCorp S.A.)
  • l10n_de Thorsten Vocks (Openbig)
  • l10n_ec Cristian Salamea
  • l10n_es Albert Cervera, Borja López, Jordi Esteve (Spanish Localization Team)
  • l10n_fr Syleam, Sistheo Zeekom CrysaLEAD
  • l10n_gt José Rodrigo Fernández Menegazzo (solucionesprisma)
  • l10n_in OpenERP and Axelor
  • l10n_it Davide Corio, Lorenzo Battistini, Servabit srl
  • l10n_ma Herve Proust, kazacube
  • l10n_mx RelTek Mexico
  • l10n_nl Veritos – Jan Verlaan
  • l10n_pl Grzegorz Grzelak (Cirrus)
  • l10n_ro filsys
  • l10n_th David Janssens Almacom
  • l10n_uk Seath Solutions Ltd
  • l10n_ve Nhomar Hernandez (Netquatro)

This incredible work could have never happened without your contributions, your effort and time.

Our merge criteria can be summarized as KISS:

  • No python code unless really needed.
  • No new fields unless really, really needed.
  • Correct and clean xml files with a chart of account template and default taxes.
  • All legal requirements.

We would like to get some constructive feedback about those merges, and are willing to accept improvements and fixes:

  • if they fit the above criteria
  • if they are proposed by making an up-to-date launchpad merge proposal to
    openobject-addons/trunk from a feature branch named l10n_<CC>_<NAME> where
    <CC> is the country code and <NAME> is any name for your improvement
  • one feature branch per feature/fix so that we can cherry pick

More complete instructions about the creation of branches and merge proposals can be found here:

http://doc.openerp.com/contribute/15_guidelines/contribution_guidelines.html#merge-proposals-patches

Original post.

The federal government wants to be informed on Free Software

drapeau_canadaOn January 19th, Public Works and Government Services Canada (PWGS) sent a request for information regarding Free Software ». this request aimed at « helping the Government of Canada to establish guidelines for the planification, the acquisition, the use and the transfer to Free Software. Whereas the Governement shows no real interest to Free Software, there are still some questions that need precisions (see below). From an operational point of view, it is necessary to elaborate fair, open, transparent common guidelines that can be applied in all the ministries in a coherent way. »

Here are some of the questions that were asked:

  • Q2. What are reasonable criteria that the Crown should consider in a decision process for acquiring No Charge Licensed Software? Are there circumstances in which the acquisition of No Charge Licensed Software would not be advisable?
  • Q3. What factors other than price should be considered as part of an evaluation guideline for No Charge Licensed Software? Are there other factors beyond those outlined in Appendix A & B that the Crown should consider?
  • Q4. How should existing Government Furnished Equipment, Services, Service Level Agreements and internal resources be considered when evaluating the usage of No Charge Licensed Software?

One of Savoir-faire Linux’ answer is the necessity to use Free Software in the Governemnt: « We consider Free Software as a technologic necessity. It is the only alternative able to fit the new needs of the organisations information system. »

« Indeed they have become highly integrated, complex, heterogeneous and in constant mutation. It is the last point that invalidates all past economic indicators such as the TCO or the ROI since they were based on a stiff vision, vertical and static of the organization, as seen in the 20th century enterprises. This is not the reality anymore. Nowadays, in many cases, the organization and its information system are one and the cost of change becomes the main question. How should the organizations deal with these numerous interactions and these constant mutations while mastering the costs at the same time? This is where Free Software becomes the only feasible alternative and where Proprietary Software reaches its limit. »