openerp-community team mailing list archive

[Fabien Pinckaers <fp@xxxxxxxxxxx>]

Hello,

As an opposite to libc, Odoo is fully modular.

Deprecating a feature does not mean it's not accessible anymore, it just
means that the feature is moved to another repository, and the
responsibility of the maintenance is transfered to someone else.

Moving report_webkit to an OCA project would be the best approach for
us. People can continue to use it as long as the OCA team decides to
keep it alive. (v8, v9, v10...)

More over, as we do not use report_webkit in our own development nor for
our own client, we are not the right entity to maintain it.

I guess camptocamp (and others?) will contribute much more to
report_webkit than Odoo in the future, because they really use it.

So, it looks normal that this module become a community one. Keeping a
module we don't want to use in the official repository is the worst
thing to do for report_webkit. (no possible evolution, constraints of no
feature applied to stable branches)


For your record, moving this module to a community branch is also a huge
cost for us: we have to port all custom webkit reports to QWeb for our
SaaS and on premise customers! (we will have to port hundreds of Webkit
reports to the new system at no extra revenues)

So, we do not take such a decision easily. Even if it's a huge pain, we
think it's good for the long term and it's better to do it soon than
later. (if people continue to build reports on webkit, it will costs us
even more later)

Hope you better understand our motivation,

Thanks,

Fabien


On 05/21/2014 09:22 AM, Erdem Uney wrote:
> This could be at least understandable if you had a roadmap for version 8
> and you have announced it like a year ago not 10 days before the release
> of v8.
> 
> Thank you Camptocamp at first creating and now supporting it.
> 
> Regards,
> Erdem
> 
> 
> On Wed, May 21, 2014 at 10:18 AM, Joël Grand-Guillaume
> <joel.grandguillaume@xxxxxxxxxxxxxx
> <mailto:joel.grandguillaume@xxxxxxxxxxxxxx>> wrote:
> 
>     +1 For Nicolas's opinion here. I think it's fair in an open source
>     project to at least give the community / partner one version to
>     convert their work by deprecating something. Please, do not just
>     remove that module for v8.0. You already dropped audittrail, project
>     long term and some others.
> 
>     If I perfectly understand all the reasons that motivate you to drop
>     them (trust me;), it's the editor's duty to announce, deprecate and
>     then only drop something. If you're not doing so, how can we as
>     partners / community rely on you ?
> 
>     Thanks for your understanding.
> 
> 
>     See you in june !
> 
>     Joël
> 
> 
> 
>     On Wed, May 21, 2014 at 8:28 AM, Nicolas Bessi
>     <nicolas.bessi@xxxxxxxxxxxxxx <mailto:nicolas.bessi@xxxxxxxxxxxxxx>>
>     wrote:
> 
>         Hello Anthony, 
> 
>         I will just quote you:
> 
>         """
>         Here is my plan:
> 
>         v8:
> 
>         we keep "server/report" and "report_webkit" unchanged, but
>         every report in our addons are converted to qweb.
> 
>         v9:
> 
>         we remove "server/report" and "report_webkit" from our
>         repository, "report_webkit" will be moved to a community repo
>         (like we do for every deprecated module).
> 
>         """
> 
>         It is a normal release cycle to deprate then to remove, even in
>         OpenSource. 
>         Such abruts abandon of addons may not entrust people with your
>         partner contract/guarantee...  
> 
>         I also think some PR where made on branche 7 if I'm correct.
> 
>         As I said previously, I was was my self not against abandonning
>         totally report_webkit if we can convert all our work to qweb report.
>         But doing so will take the community some time to do it.
> 
>         Now, if you really do not want to maintain it and the question
>         is just rethoric, Camptocamp/community will maintain the module.
> 
> 
>         Regards
> 
>         Nicolas
> 
>          
> 
> 
>         2014-05-21 5:25 GMT+02:00 Erdem Uney <erdemuney@xxxxxxxxx
>         <mailto:erdemuney@xxxxxxxxx>>:
> 
>             Thank you for asking.
> 
>             Weren't you the one who said about a month ago that you will
>             support report_webkit through v8 and drop both rml and
>             report_webkit in v9? 
> 
>             Regards,
>             Erdem
> 
> 
> 
>             On Wed, May 21, 2014 at 2:36 AM, Antony Lesuisse
>             <al@xxxxxxxxxxx <mailto:al@xxxxxxxxxxx>> wrote:
> 
>                 I would like to remove report_webkit from our master
>                 branch before releasing v8.
> 
>                 I think we wont maintain it properly and i expect that
>                 this will create frustrations during the lifetime of v8.
> 
>                 None of our modules use it at all (none ever did
>                 actually). Now that the conversion from rml to
>                 qweb/wkhtml report is done, i consider that the default
>                 report system of v8 is superior to report_webkit.
> 
>                 It has all the advantages like the speed and html/css
>                 syntax, but it's much more modular and versatile. It
>                 supports as many layout as you want, images and view
>                 inheritance. The codebase is also smaller.
> 
>                 report_webkit was a source inspiration when we developed
>                 the v8 pdf report generation. And i would like to thanks
>                 its author Nicolas Bessi.
> 
>                 On github we already have 2 pull requests (PR) about it,
>                 i dont want my developers to spend time on code that is
>                 not used at all by any addons.
> 
>                 So report_webkit PR's will stay unprocessed and i dont
>                 think the module deserve that.
> 
>                 Would oca be motivated enough to take over the module to
>                 ensure proper maintenance.
> 
>                 Antony Lesuisse.
> 
>                 _________________________________________________
>                 Mailing list: https://launchpad.net/~__openerp-community
>                 <https://launchpad.net/~openerp-community>
>                 Post to     : openerp-community@lists.__launchpad.net
>                 <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>                 Unsubscribe : https://launchpad.net/~__openerp-community
>                 <https://launchpad.net/~openerp-community>
>                 More help   : https://help.launchpad.net/__ListHelp
>                 <https://help.launchpad.net/ListHelp>
> 
> 
> 
>             _______________________________________________
>             Mailing list: https://launchpad.net/~openerp-community
>             Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>             <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>             Unsubscribe : https://launchpad.net/~openerp-community
>             More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
>         -- 
>         Nicolas Bessi
>         Senior ERP consultant
>         Business Solution technical manager
> 
>         Camptocamp SA
>         PSE A
>         CH-1015 Lausanne
> 
>         http://openerp.camptocamp.com <http://openerp.camptocamp.com/>
> 
>         Direct:   +41 21 619 10 26
>         Office:   +41 21 619 10 10
> 
> 
>         _______________________________________________
>         Mailing list: https://launchpad.net/~openerp-community
>         Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>         <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>         Unsubscribe : https://launchpad.net/~openerp-community
>         More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
>     -- 
> 
> 
>     *camptocamp*
>     INNOVATIVE SOLUTIONS
>     BY OPEN SOURCE EXPERTS
> 
>     *Joël Grand-Guillaume*
>     Division Manager
>     Business Solutions
> 
>     +41 21 619 10 28
>     www.camptocamp.com <http://www.camptocamp.com/>
> 
> 
> 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
> 


-- 
Fabien Pinckaers
Odoo Founder

Phone: +32.81.81.37.00
Web: https://www.odoo.com
Twitter: @fpodoo