@ Maxime
We have public contribution
(https://code.launchpad.net/~openerp-community/openobject-addons/elico-6.0)
but not yet a formal manufacturing branch, which will come soon with
new additions.
@Nhomar,
thanks a lot for the summarized list. There is not one perfect
solution indeed but there are some good practices which could become
a solid common base.
My point, and you demonstrate it very well is that, from outside
(meaning "customer"), there are 3 or 4 (or more depending on the
topics) different modules/set of modules for a similar feature and
you have no clue which one is good practice/well coded unless you
spend long days testing/reading code and so on.
As partner/integrator, this is part of my job and my R/D but this is
a technical attitude, not customer oriented attitude. The image
given to potential customer is not the correct one.
Potential customers will see no common, strategic and controled
development on such important aspect as manufacturing. And this is a
drawback when you sell integration.
This is why I think on top of diversity of the opensource (which is
good anytime), there is also a need as for a common base for
advanced manufacturing/accounting/CRM/whatever functionalities
"certified"/controled by a group of community members expert in the
domain.
On 06/21/2012 12:30 PM, Nhomar Hernández wrote:
Hello Eric.
Exactly as @Maxime said:
You can see our work.
https://blueprints.launchpad.net/openobject-addons/+spec/mrp-advanced-cost-management
The work of others:
https://code.launchpad.net/avanzosc
More of our work:
http://bazaar.launchpad.net/~vauxoo/addons-vauxoo/6.0-trunk/files
[Here specifically stock_card and cost_structure can help on this]
We have deploy openerp in 2 Manufacturing companies VE, and
developed 2 more implementation on Mexico, and Coached 4 More
Colombia and Mexico, let me tell you, the power is in python
itself not in the ERP "WHAT EVER THE NAME YOU SAY".
In all cases problems has been solved with the same theory but
needs are not common, some of them work with what openERP bring
and go growing up in the midle working with standars and
understanding how thinking in future (testing trunk at same time),
is so complex to explain in few word, but i think you can
understand me.
Major of issue is desitions, BSC, key numbers and so on (Not well
automated on OpenERP) but with experience and not more than 250
lines of code you deploy a great MRP2 or MRP solution.
Obviously, if you think in Java's way where you have just one
contributor becouse he is the only mortal that understand what he
did (as adempiere did) when he isn't in this place who take the
lead???
In VE goverment tryied to implant adempiere in 200 manufacturing
companies 5 years ago, "NO BODY HAS OPEN ONE SINGLE LINE OF CODE"
and all start to move to OpenERP because is almost imposible in
adempiere architecture do it... with openerp it isn't in this way.
The proof:
https://Launchpad.net/sisb
In a nut shell:
Start with A single new feature as documented as you can following
all steps mentioned by @maxime, make public costructive critics to
makers of modules already done and free, contribute with them,
share your code in them branches, BUY services to suport some
improve or at least to help them to mantain this branches....
Step by Step OpenERP SA wll merge the best....
MEssage:
We are in the way you think we need to go, we need just people
documenting and studying and following implementing.
Regards.
2012/6/20 Eric Caudal <[email protected]>
@Maxime
We already did all of this and indeed I do not need any kind
of endorsement or authorization (Which I am not looking for
actually)...
I am just trying to have a broader vision for collaboration,
unifying what is or could be existing and getting a kind of
certified limited set of modules recognized by a group of
experts (manufacturing but not only).
@Pieter
We already do have several customers paying for our
expertise and modules developments. We will probably come
with another set of modules that will be another brick to
build the OpenERP house. I will have a look at Adempiere
functions: this is indeed what I would aim to. I have the
feeling that having those functionalities would help sell
easier OpenERP project without reducing our input as partner
or expert.
In nutshell, I just want to promote the idea of a reduced
but coordinated and stable advanced set of manufacturing
modules that could be part of what is already existing, part
of what we could contribute.
I hope we can get soon a good momentum: Wouldnot it be
possible somehow to create a code repository under the
expert group, gathering some of the community modules and
try to get a blueprint of what could be the most wanted
functionalities (LIFO/FIFO/MO and picking split with auto
procurement, advanced MRP etc...)
On 06/21/2012 11:46 AM, Maxime Chambreuil
wrote:
Hello,
You don't need
any funding or endorsement from anyone to :
* create a
project on Launchpad as part of the OpenERP
group project
* create a team
to lead the project
* contribute
couple modules, even if they are a proof of
concept or prototype
* announce your
project on the related topic of the forum
Google will do
the rest and it will be easier for contributions
to come. So please take the lead and go for it.
I'll be happy to contribute modules to
openerp-manufacturing project when the
opportunity arrives (might be anytime soon).
My 2 cents,
--
Maxime Chambreuil
Hi Geoff,
Thanks for the contribution. Financing is
important but does not actually need to be money
but as well dedication and HR that you can
allocate. Today unfortunately we do develop some
modules but I cannot afford to be contributing
alone in such a dense project (hence my call for
contribution).
Having OpenERP s.a endorsement is obviously a
must but will come IMO only when a consequent
group of partners feels the need to work
together as an Expert group and contribute
actively on advanced functionalities with a
certified code.
So far though, there seems to be no real will
from the partners or community to fill in the
gap (very few feedback) which makes me wonder:
- Maybe this is not really necessary?
- Maybe the fear that contribution will help
competitors is too strong?
- Maybe partners prefer to keep their knowledge
in order to justify their business model?
- Maybe we are not so many people to actually
use advanced manufacturing concepts?
- all of them or any other reason
I would probably vote for the 3rd one ;)
On 06/11/2012 12:13 AM, Geoff Gardiner wrote:
_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp
--
--------------------
Saludos Cordiales
Nhomar G. Hernandez M.
+58-414-4110269
Skype: nhomar00
Web-Blog: http://geronimo.com.ve
Servicios IT: http://vauxoo.com
Linux-Counter: 467724
Correos:
[email protected]
[email protected]
twitter @nhomar
|
