+1 pedro. He explained much better than me with less words. El 29/11/2013 16:28, "Pedro Manuel Baeza Romero" <[email protected]> escribió:
> Hi, Maxime, > > Say in thay way, "plan to make incompatible modules" sounds very rude. > There are now incompatibilities in 6.1, but the plan is that in > refactorization to remove as many as we can (always take in mind that there > can be serious problems to decouple from the core some things, but I'm > submitting some bugs to avoid this "forks"). > > I think more on this repository as a *full manufacturing suite* included > in the same location. The final goal to us is to include the v7 repository > under the umbrella of OCA, or even merged with the repository you have > mentioned. > > So please, don't stay with the thought that we are making incompatible > modules. Everyone that has seen my work on community repositories (MPs and > reviews) can affirm that this is not my way of doing things, but I cannot > absolutely say that we are not going to face with something incompatible > (Avanzosc had this trouble in the past with 6.0). > > Regards. > > > 2013/11/29 Maxime Chambreuil <[email protected]> > >> Are you saying that you created a different project because you plan to >> make incompatible modules ? >> >> Thanks for the clarification. >> >> -- >> Maxime Chambreuil >> +1 (514) 276-5468 #126 >> >> ------------------------------ >> Hi Maxime: >> >> OpenMRP is modifying MRP standar master data and database structure so >> most modules built for standard will not be valid on extended modules and >> viceversa. It's because of that I think modules should be published on >> different branches. Most of extensions on both aproaches would be not >> compatible. >> >> Standar modules cover IMHO only small assembly companies but they don't >> cover complexity of real manufacturing company. >> >> One of the aproaches of OpenMRP is controlling manufacturing by >> workorders(operations) made on machines (work centers). >> The standar modules have no way to consume or produce materials by >> workorders, or controlling semielaborated products without putting them on >> stock. >> Other functional lack on standar modules would be, manufacturing cost >> control. Normally, there is workers on machines who made the workorders. A >> manufacturing order cost is not only materials included on it but materials >> + machine cost + worker cost on each operation. >> >> Same way if you need having a real manufacturing procurement planning, if >> your operations are long time, you don't need stocking all materials at >> begining of order as in standar way but you only need having materials >> ready when you are going to start the operation that is going to consume >> them (The real manufacturing procurement planning is not covered on OpenMRP >> yet). >> >> The aproach is totally different on both solutions and both could be >> valid depending on casuistic of company's needs. Using OpenMRP will complex >> a lot configuration and proccess on any company but it will cover aspects >> unexistant on standar ones. For example, if your lead is a factory making >> asembly where they don't need calculating cost for machine(they don't have) >> or worker, probably I will propose standar modules. If you have got a >> complex production factory with production likes, machines and wanting to >> know each piece unitary real cost, I would propose OpenMRP. >> >> Wishing it will help you, >> >> Thank you: >> >> Ana >> >> >> >> >> 2013/11/29 Maxime Chambreuil <[email protected]> >> >>> Hello Pedro, >>> >>> Just a few questions : What will be the difference between OpenMRP and >>> OpenERP Manufacturing projects ? Where should someone put its mrp related >>> modules ? >>> >>> Thanks. >>> -- >>> Maxime Chambreuil >>> +1 (514) 276-5468 #126 >>> >>> ------------------------------ >>> Hi, Raphael, >>> >>> Very interesting the backports and the method you have used. We will >>> look every new feature (I only make for now an oversight) of WMS trunk to >>> possible backports, but as you have said, there are some areas that simply >>> cannot be backported. If we get enough funds - I don't want to repeat >>> myself too much, but we are doing this without any other customer support - >>> we will point definitely to use all the v8 potential (without forgetting >>> v7, as I said previously). >>> >>> Regards. >>> >>> 2013/11/29 Raphael Valyi <[email protected]> >>> >>>> On Fri, Nov 29, 2013 at 9:12 AM, Fabien Pinckaers <[email protected]>wrote: >>>> >>>>> >>>>> >>>>> On 11/29/2013 11:51 AM, Nhomar Hernández wrote: >>>>> > >>>>> > @Fabien: I think it should be great if you share with us the specific >>>>> > branch in this thread where the new stock is landing please, to be >>>>> sure >>>>> > everybody start with it from the same place. >>>>> >>>>> >>>>> http://bazaar.launchpad.net/~openerp-dev/openobject-addons/trunk-wms/revision/9418 >>>> >>>> >>>> Hello, >>>> >>>> just a word: eventually we don't need to wait Q2 2014 (or later?) to >>>> start building upon the new things. A few things (only) are possible to >>>> backport on v7, that will make a smoother transition to v8 when it will be >>>> stable. >>>> >>>> For instance a project I'm working with should be in production by >>>> December 31th and it needs the concept of picking waves (that many already >>>> made similar modules but nothing OCA quality like). >>>> So instead of going unstable v8 or doing crap again on regular v7, I >>>> backported the picking wave module here: >>>> https://github.com/akretion/oe-addons-subtree-stock_picking_wave >>>> >>>> By using git and git-subtree (I will eventually post about the whole >>>> trick), we are able to properly keep in synch with the upstream branch >>>> without the need to have a folder with all the v8 modules to accommodate to >>>> the addons-path. >>>> So the extracted mirror of the trunk-wms is here: >>>> https://github.com/akretion/oe-addons-subtree-stock_picking_wave/tree/trunk-wms >>>> and the backported module is a branch of it >>>> https://github.com/akretion/oe-addons-subtree-stock_picking_wave/tree/backport-7.0 >>>> >>>> I think OCA could assume working this way for specific module backports >>>> (if we need a new branch of all modules for every kind of backport, soon >>>> these branches are simply incompatible and we face an combinatorial >>>> explosion of unmanageable backports). I'm willing to help setting this up >>>> in case people are interested. >>>> >>>> Now, make no mistake, backporting the new stock quant system to v7 is >>>> out of question. I also extracted/backported purchase_requisition to v7 >>>> that I use in another project. And something we could backport to v7 is the >>>> saas2 branch analytic_account module. Or eventually, as v8 isn't for now, >>>> we could start having a merge of saasX branches into OCB/RS-OCB. I started >>>> and I can tell the the merge is rather easy, so again I let OCA people >>>> bring the topic on the table again if they think it makes sense. >>>> >>>> That being said, I wish good luck to the funding, I also wish it base >>>> on V8 stock things as it fixes scalability issues that used to be one of >>>> the major OpenERP flaw, the kind of thing that was litteraly fueling >>>> sorryopenerp.com. This is very cool to see v8 finally bringing a lot >>>> of good work in the WMS area. >>>> >>>> >>>> Best Regards. >>>> >>>> >>>> >>>> -- >>>> Raphaël Valyi >>>> Founder and consultant >>>> http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi> >>>> +55 21 2516 2954 >>>> www.akretion.com >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~openerp-community >>> Post to : [email protected] >>> Unsubscribe : https://launchpad.net/~openerp-community >>> More help : https://help.launchpad.net/ListHelp >>> >>> >> >> >> -- >> CEO Avanzosc, S.L <http://www.avanzosc.es> : Office phone / Tfono >> oficina: (+34) 943 02 69 02 >> Ana Juaristi Olalde <http://www.anajuaristi.com/>: Personal phone: 677 >> 93 42 59. User/usuario skype: Avanzosc >> www.openerpsite.com >> >> >> *El contenido de esta comunicación y de toda su documentación anexa es >> confidencial y se dirige exclusivamente a su destinatario. El uso no >> autorizado de esta información está prohibido por la legislación vigente. >> Si usted no es el destinatario le rogamos nos lo indique, no comunique su >> contenido a terceros y proceda a su destrucción. Disculpe las molestias que >> le haya ocasionado la recepción indebida de este e-mail. Sus datos figuran >> en un fichero cuyo titular es Avanzosc, S.L., a quien usted puede dirigirse >> para ejercer sus derechos de acceso, rectificación, cancelación y oposición >> en Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), Tef. 943 02 69 02 - >> [email protected] <[email protected]> * >> >> *Komunikazio honen edukia eta dokumentazio erantsia konfidentziala da eta >> hartzaileak bakarrik jaso beharko luke. Indarrean dagoen legeriak debekatu >> egiten du bertan eskainitako informazioa baimenik gabe erabiltzea. >> Komunikazioa zuri iritsi bazaizu, baina zu ez bazara hartzailea, mesedez, >> guri jakinarazi, eta jasotako informazioa ez inori jakinarazi eta suntsitu. >> Barkatu okerreko email hau jasotzeak eragindako eragozpenak. Zure datuak >> Avanzosc, S.L. enpresaren fitxategietan sartuta daude. Zure datuak atzitzea >> eska dezakezu, bai eta, datuak zuzentzea, ezereztea eta tratamenduari aurka >> egitea ere. Horretarako, enpresara jo dezakezu, helbide honetan: Julio >> Urkijo, 32, 20720, Azkoitia (Gipuzkoa), telefonoa: 943 02 69 02 - >> **[email protected] >> <[email protected]> * >> *This message and all documents attached to it are confidential and >> intended only for the person or entity to which it is addressed. Any use of >> this information by unauthorised persons is prohibited under current >> legislation. If you received this message by error, please advise us, >> destroy it and refrain from communicating its contents to third parties. We >> apologise for any inconvenience receiving this email improperly may cause >> to you. Your personal data are included in a file owned by Avanzosc, S.L. >> If you want to exercise your rights of access, correction, erasure and >> objection you can contact the Controller at Julio Urkijo, 32, 20720, >> Azkoitia (Gipuzkoa), T: 943 02 69 02 – [email protected] >> <[email protected]>* >> >> >
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
