Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Print customer address in all pages of a stock.picking report (delivery slip) #33
Re:py3o and commit rights on reporting-engine
Re: py3o and commit rights on reporting-engine
by
InitOS GmbH, Frederik Kramer
Hi Alexis, as also Eric pointed out that decision sounds more than reasonable, however, i am still very curious to know the argument of Aeroo's inital contributors not to include it to the OCA? Is that exactly what the block post will be about ? I am curious especially for scientific purposes here (i am researching Open Source and OS movements since 2007 basically), so more insight would be very much appreciated Kind regards Frederik Am Donnerstag, den 02.03.2017, 08:23 +0000 schrieb Alexis de Lattre: > Dear community friends, > > You are certainly aware that the module report_py3o has be merged in > the OCA/reporting-engine project (merged in the 10.0 branch ; should > be merged soon in the 9.0 branch too). Report_py3o is a Libreoffice- > based reporting engine developped by the French integrator XCG > Consulting and in particular by Florent Aide. > > It is an alternative to the Aeroo reporting engine that has been a > popular Libreoffice-based reporting engine since OpenERP 5.0. But the > main author of the Aeroo project refused to include Aeroo in the OCA > (we tried to convince him several times without success), and we > prefered to include report_py3o in the OCA than maintain an not- > friendly fork of Aeroo in the OCA. There is a lot more to say about > this story ; I am planning to write a blog post about > report_py3o/aeroo and also promote my sample py3o reports available > on https://github.com/akretion/odoo-py3o-sample-report for Odoo 10 > (should be a big help for beginners on report_py3o). Personnally, I > already have 4 deployments of Odoo 10 + report_py3o in production > since 01/01/2017 and they've all been working without a glitch. > > If report_py3o becomes as popular as Aeroo in the future, report_py3o > will become one of the main modules of OCA/reporting-engine. So I > think it's important that the active contributors of the report_py3o > module have commit rights on OCA/reporting-engine. That's why I > suggest to add commit rights on OCA/reporting-engine to: > > - Florent Aide from XCG (github login: faide) > - Laurent Mignon from Acsone (github login: lmignon) > > Regards, > > Alexis de Lattre > _______________________________________________ > Mailing-List: http://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: http://odoo-community.org/groups?unsubscribe -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
Reference
-
py3o and commit rights on reporting-engine
byAlexinux, Alexis de Lattre-
Re: py3o and commit rights on reporting-engine
byInitOS GmbH, Frederik Kramer -
Re: py3o and commit rights on reporting-engine
byInitOS GmbH, Frederik Kramer -
Re: py3o and commit rights on reporting-engine
byAlexinux, Alexis de Lattre -
Re: py3o and commit rights on reporting-engine
byOpener B.V., Stefan Rijnhart -
Re: py3o and commit rights on reporting-engine
byInitOS GmbH, Frederik Kramer
-