Hello, As I guessed the question was purely rhetoric :P
As Joel says, community will take the relay. Can you please provide us a procedure to extract history from github repo for report_webkit. Going forward and having a strategy is a good thing, but good grief, please respect at least some release cycle or provide a least a better roadmap. You should really adopt a better communication with community and partner because I'm sure at that time they don't feel in confidence with odoo/OpenERP. I'm really gratefull to OpenERP/odoo for this great product that make me eat. But that also why I want to have a trustworthy relation with it. My two cents Nicolas 2014-05-21 10:30 GMT+02:00 Fabien Pinckaers <f...@openerp.com>: > Hello, > > > > /Here is my plan: v8: we keep "server/report" and "report_webkit" > > unchanged, but every report in our addons are converted to qweb./ > > Yes, we can change our mind if we have better ideas. > > We try to avoid this, but if it helps building a better product by > focusing on the essentials, that's good. (for example, we'd like to > assign resources to keep pull requests under control) > > It's not only about community. This is the way we work internally too. > Antony can promise me something and change his mind later and I do the > same with him. > > Having such a level of flexibility is sometimes frustrating (nobody > likes to abort a project in the middle), but it's a good thing in the > long term. It allows us to keep staying focused and not waste time on > non valuable developments. > > We used to say that nothing is granted with the R&D. Being agile matters. > > > > It's the same with the github story, ofcourse the github is better, but > > we get a message on the webminar and the other day we are all github. It > > also takes some time to adapt our installation scripts, to get used to > > this new tool. > > We moved version 8 to github from one day to another, because it has no > impact for the community that do not use v8 yet. (and we provide scripts > for your feature branches) > > But version 7 is still on launchpad and we are ready to maintain > launchpad for a transition period in order to help you organize > yourself. That's something we should discuss and decide at the community > days. > > But, for now on, there are no emergencies to move to github for your v7 > projects as we continue to maintain launchpad for v7 and earlier. > > > > You know odoo has a long tail and we are member of it :-) > > Yes, and the long tail is the strenght of Odoo too. (actually both the > head and the long tail are our strenght :) > > That's why the OCA can maintain report_webkit without damage to this > good module. > > > > > Hope to see you all in june ... > > me too :) The community days will be a great event. We work hard to > ensure the quality of the talks will be good. > Hope you will like, > > Fabien > > > > > > Peter > > > > > > 2014-05-21 9:18 GMT+02:00 Joël Grand-Guillaume > > <joel.grandguilla...@camptocamp.com > > <mailto:joel.grandguilla...@camptocamp.com>>: > > > > +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.be...@camptocamp.com <mailto:nicolas.be...@camptocamp.com>> > > 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 <erdemu...@gmail.com > > <mailto:erdemu...@gmail.com>>: > > > > 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 > > <a...@openerp.com <mailto:a...@openerp.com>> 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@lists.launchpad.net> > > 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@lists.launchpad.net > > <mailto:openerp-community@lists.launchpad.net> > > 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@lists.launchpad.net > > <mailto:openerp-community@lists.launchpad.net> > > 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@lists.launchpad.net > > <mailto:openerp-community@lists.launchpad.net> > > Unsubscribe : https://launchpad.net/~openerp-community > > More help : https://help.launchpad.net/ListHelp > > > > > > > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~openerp-community > > Post to : openerp-community@lists.launchpad.net > > 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 > > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : openerp-community@lists.launchpad.net > 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 Direct: +41 21 619 10 26 Office: +41 21 619 10 10
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
