@janneman (and all) For accounting, as we discussed when we met, the big part of the job is to review and merge all the localization modules that have been made by OpenERP communities, like in Spain, Venezuela, the Netherlands, etc., and extract what should be part of the core. Carlos Liebana has just confirmed it, most of these modules have been made specific and it is not a small task to refactor them into just data and a bit of customizations on top of a generic (extended) core module. This is one big task remaining for v6, which is otherwise becoming almost ready for a feature freeze. As for the organization of communities, we are going to try to provide answers to those needs soon. One of the first steps will be the introduction of a new OpenERP website, with more focus on the communities, visibility, resources, etc. This is conducted in parallel to the v6 release. A second step is that we will dedicate more resources to the communities, and try to focus the energies around the community processes, which will also become more clear to everyone thanks to the website. In the mean time, I suggest you all discuss your needs on the accounting mailing-list, as Raphael hinted (https://launchpad.net/~openerp-expert-accounting). It will be easier to find the info there for reference when we need it.
@sraps: We fix a lot of bugs all the time, and even if accounting issues can be quite tricky and longer to troubleshoot, they end up being fixed eventually. There is very often more than meets the eye to an accounting bug, and I'd rather have an identified bug stay open for more time, than merge a fix without properly analyzing all sides of the issue, especially for such a core module, and risk ending up with more complicated/bloated code hiding the original bug even further. Just an example: bug 436449 you reported yourself, stayed open quite long, the community was shouting that patches were provided and that we were doing nothing (100+ comments!). After careful investigation from our side it turned out that the proper fix was a 2-lines patch and none of the proposed patches, and there was also another wishlist issue mixed in the bug report, for which we provided a hook in the module. Don't you think it was worth it? Thanks to the efforts of all involved we have more test scenarios, more comments in the code, better code (not *more* code, *better* code!), and an additional extension hook in the module. Of course it would be ideal if we could do this in real time for all issues, unfortunately we don't have the resources yet, but at least we're doing our best :-) And don't worry, your work is never wasted, even when it looks like it takes time to be accepted/reviewed/integrated! @rvalyi: Thanks for pointing out to the dedicated mailing-lists and illustrating the fact that we are indeed working constantly on improving OpenERP for everyone, and not just smartly ignoring the community while we play with the code randomly ;-) There's *a lot* of work to do and unfortunately it is not possible or easier in every case to ask the community to do the work but we are making OpenERP great together. And even if we don't have the leisure to reply to every question/post in the community channels, some of us are reading and listening, be sure of it ;-) Thank you for being out there and being relentless, guys :-) Now, back to work on v6... -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=59532#59532 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
