Link to Open days slides
http://www.slideshare.net/openobject/presentations
Tuesday, June 10, 2014
Sunday, June 08, 2014
Back from OpenDays 2014
Back from OpenDays 2014
Link to you
tube videos index is already posted. I suppose slides will follow.
Version 8 should be in RC in July
- New API (ORM)
- CMS and e-commerce
- New front-end views (Odoo dev will be more and more HTML crafting…)
- New warehouse management (quants, routes, evaluation and retrieval method)
- Gamification, tutorial
- New tooling (gitHub based)
- Many more small improvements on POS, surveys, marketing, mass-mailing
Strategy analysis
1) More marketing
-
Odoo
has appointed a Chief Marketing Office, so the new brand, the logo etc. OpenERP
claimed they were not doing marketing but in fact was doing some, Odoo now assumes
this DNA change.
-
Note
their plan is IMHO smart marketing as it includes developer marketing (api
docs, how-to , moving to gitHub etc). Good move.
2) CMS , e-commerce, website, more users
There are
much more web sites than erp instances. As open-source business is commonly
based on the fremium model (only a tiny percentage of users pay for the
software). The priority is ‘more users’. Having back-end and front-end integrated
makes many things simpler (if you trust the security inside the system).
3) Direct sales
Well the Sass
approach is direct sales, quick start methodology is direct sales so is renewal
team, direct sales team etc…
The
enterprise contract is support / maintenance / migration, their service
offering is fixed price service for implementation, they also provide data
import, web custom design.
Although
they claim to be interested in only very small projects their demonstrated
business case (20 employees in French speaking Belgium) is a nice company… They
target small, big and finally medium market... well I think everything is the
word.
Currently
they don’t officially propose customization. But the fact they allow in 8 to
deploy custom data modules and several times they mentioned loading custom
modules on the Saas as something being evaluated, make me thinking that they
don’t because of technical limitations that will be lifted off sooner or later…
Going
direct requires that good accounting localization is built-in… They announced
that 9 will include around 8 complete standard localizations. I guess they will
start by Belgium (obvious), France probably Switzerland….
In summary,
better the software is, less they need partners, more they will go direct.
Partners must therefore think their strategy based on Odoo approach:
- have your clients (don’t expect leads);
- build differentiator with software outside the Odoo scope;
- verticalize out of the main street erp activities;
- fork (small word, big work).
As stated
by a colleague ‘your competitor is your best friend that’s the magic of
open-source’. So is it between the editor and the partners…
OCA – Community
We had a
great time at the first general assembly of the Odoo Community Association.
Grouping contributing voices is a way to get a bit attention from Odoo, developing
alternative migration tool and complimentary modules is a good insurance to
keep the software open-source and a great place to work for independent
integrator.
Last words
Libellés :
community,
oca,
odoo,
open-source,
open-upgrade,
opendays,
openerp
Saturday, June 07, 2014
OpenDAYS 2014 - link to the video
Back fro the Odoo (formerly OpenERP) Open days:
here is a link to all the you tube videos :
https://lists.launchpad.net/openerp-community/msg05952.html
Sunday, July 07, 2013
Back from OpenERP Community days 2013
So here is my completely non exhaustive summary of these 3 days.
1) OpenERP Community Association
I think this is a great initiative from a few partners attempting to clean up the community branches and provide a structure for shared development. Let’s hope many contributors will join and cooperate. While I understand the target, I think the association must have two levels for projects registration: full community based and simple references of other open-source initiatives. The main reason being that transferring intellectual may not be acceptable for some contributors or simply impossible for some projects.2) New connector for Magento
Looks like a nice rework and a first successful shared funding attempt.3) Belgian localization.
I cross my fingers, the two first points may be inspiring for solving some issues around contributed modules including financial localization for Belgium …4) OpenERP as a CMS and e-shop.
I understand the strategy, this may be achievable. But I think it twill take a couple of years before OpenERP can equal the web leaders. Those who attended Antony session will understand my point : I know Drupal, Joomla are sometimes difficult to use… but they do also a lot of things, require competencies and have a learning curves .. so does it with OpenERP…5) Presentation of the new warehouse management for OpenERP version 8.
Great initiative from c2c again ! I will try to come back on the new concepts, rules and quants. It is promising and should solve many issues we have with stock management including cost computation, traceability and performance. To be tested end of the year (in trunk).5) Accounting workshop
We had a great workshop about accounting with Quentin. At least he now has points to add on the roadmap… Personally I really enjoyed these workshop sessions, especially with friendly faces…I will try to get back the pad and publish it as it is…
6) Pentaho reporting
I attended a last minute schedule session about Pentaho reporting. Finally, one report engine that is accessible to functional people… If they solve a few issues (like support of translatable field): we might be saved.7) New API expected in version 8
Shame on me, I missed the new API presentation expected for version 8 but I favored accounting workshop and Pentaho reports … I suppose the presentation slides will be posted soon. I heard a lot of positive feedback on these changes.8) News from the testing crypt
C2c presentation over testing. The presentation was more general than what I expected but remember at least that OEScenario is now full Python. No need to learn Ruby…9) When can we expect version 8 ?
No official word, but we are a few to believe mid 2014 is a reasonable target.Monday, October 01, 2012
Company_id default value
Looking at base objects in OpenERP is always source of inspiration.
I found the following
'company_id': lambda s,cr,uid,c: s.pool.get('res.company')._company_default_get(cr, uid, 'res.partner', context=c),
So there is a method for finding the company_id to use for an object - here a partner. Company_id is important since this field is used for partitioning your db between different companies.
Even better looking at res.partner, I found ab oject called 'multi_company.default' !
Basically there is a small and 'hidden' rules engine to set company_id ! Nice.
Sunday, August 26, 2012
Our KB project - going to Drupal
Very often we exchange tips with colleagues and partners. Things like do you have an example in OpenERP of a search / function field etc
Simply, we exchanges these by e-mail. Best of them go in mail folders.
When working on windows I am using OneNote (great MS office app with IMHO no open-source close equivalent).
I think these e-mails represent valuable material. Good for us during projects, but may be good for other people. So I decided to setup a knowledge-base web site where we can easily store and publish tips and code snippet.
My intention is to use Drupal instead of my usual Joomla. There are 2 keys reasons:
Creating content-type is also easy to manage. In Drupal 7 the so called CCK is now a core module. One click and you are done.
However my first snippet post was disappointing... All the alignments are lost. Well for python samples with indent being semantically import the result was not that bad.
2 google search later? I found a Geshi filter module. Well a drupal module using a PHP library called GeSHI.
http://qbnz.com/highlighter/index.php
Much better than simply keeping indentation. It hilight source code syntax with colors for an incredible number of languages.
This is were hughe communities of coder are incredibly good - thanks to all Drupaler and PHP guys and of course the GeSHI autors - you are great and you did my day !
Simply, we exchanges these by e-mail. Best of them go in mail folders.
When working on windows I am using OneNote (great MS office app with IMHO no open-source close equivalent).
I think these e-mails represent valuable material. Good for us during projects, but may be good for other people. So I decided to setup a knowledge-base web site where we can easily store and publish tips and code snippet.
My intention is to use Drupal instead of my usual Joomla. There are 2 keys reasons:
- Taxonomy : in Joomla the section/category is limited and makes impossible to classify articles. World is not a 2 levels tree - n level (Joomla 2.5) is not better. What I am waiting for since at 7 years: be able to put 1 article in multiple categories... E.G python / openerp / query / partner etc
- Front-editing : I just want to be able to login and change , cut and paste articles directly. The separation between the site and the admin may give security feeling for a classical site but is clear not appropriate for a community sharing site.
Creating content-type is also easy to manage. In Drupal 7 the so called CCK is now a core module. One click and you are done.
However my first snippet post was disappointing... All the alignments are lost. Well for python samples with indent being semantically import the result was not that bad.
2 google search later? I found a Geshi filter module. Well a drupal module using a PHP library called GeSHI.
http://qbnz.com/highlighter/index.php
Much better than simply keeping indentation. It hilight source code syntax with colors for an incredible number of languages.
This is were hughe communities of coder are incredibly good - thanks to all Drupaler and PHP guys and of course the GeSHI autors - you are great and you did my day !
Friday, August 17, 2012
openerp fields.py - paradise of extensibility
Here is an extract of fields.py one of the openerp kernel file:
class _column(object):
.....
def __init__(self, string='unknown', required=False, readonly=False, domain=None, context=None, states=None, priority=0, change_default=False, size=None, ondelete=None, translate=False, select=False, manual=False, **args):
...
for a in args:
if args[a]:
setattr(self, a, args[a])
...
This last for loop is programmer paradise. It simply means you can create any field and add directly data to the field definition like a qualifier or anything you need in the constructor.
Simply cool, elegant and efficient !
class _column(object):
.....
def __init__(self, string='unknown', required=False, readonly=False, domain=None, context=None, states=None, priority=0, change_default=False, size=None, ondelete=None, translate=False, select=False, manual=False, **args):
...
for a in args:
if args[a]:
setattr(self, a, args[a])
...
This last for loop is programmer paradise. It simply means you can create any field and add directly data to the field definition like a qualifier or anything you need in the constructor.
Simply cool, elegant and efficient !
Subscribe to:
Posts (Atom)