> what i mean with "non-commercial" (probably it's not the best term) is to > focus the development on what end-users and clients really need instead of > what is needed by the openerp release plan.
We on Netquatro from venezuela are TOTALLY agree with the main concept of your post, this kind of meeteng should cumply IMHO with very good prepared schedule..... We can participate, and we have A LOT of features thought in a generic way to improve, but,we are a little worry about some things. -- RML reports MUST NOT be supresed, we really think after learn about this functions that is more powerfull than Jasper, or even OpenOffice, we forgot openoffice, and we modify an invoice in 2 or 3 hours, BUT IT SHOULD BE IMPLEMENTED COMPLETE not PARTIAL, this is the problem, with a little invesment of time an resources from all we can develop a web editor that change the tags on RML by web (something like Workflow or view editor, we use this toolls a lot to show concepts and several behaviour) IOH try to implement several "official options" is a waste of time we need have ONE but EXTRAORDINARY report tool written on python ;-), we in Netquatro was born with CRYSTAL and other grafical report tools and really none is comparable with the power of REPORTLAB + PYTHON + OPENERP COMBINED but we need to make this relation very very strong, but by the way this is our opinion. -- From the accounting point of view, we dedicate several hours in our very little quantitiy of implementation and we automate almost everything, with OPENERP you need only reports to audit, and the result is in very little changes on accounting, but this work can not be done by only a programmer, you need people that understand both words ACCOUNTANT AND PROGRAMIG, with this kind of people you can make that only the company intend to use them funtional parts not the accounting (only for auditing), we have today a customer that have expend a lot of time in planify all the accounting process, right now the accounting team only AUDIT not POST lines, this is dificult and a little abstract but now we have a company with this behaviour, and they even don't have technical people inside them team. We think that we need to have a very powerfull tool to post account move from a functional programming way, i mean, if you want to make a very complex move several ways, you can build it one time (with a very little manual) and post this basic account process, this concept is a little confuse too, but we want to participate in this meeting and we will prepare this concepts... ;-) BTW we need to arm our teams with very good people because not only have a a "easy to use" ERP tool ensure the success, the tool needs grow up not exploid work on several funtional issues. (Is only an opinion.) -- I'm really worry about a bug and a post on lists around FISCAL POSITIONS, this need DOCUMENTATION not be removed or changed, we need to invest on make documentation almost the same effort that we are doing on program and post bugs..... Concepts HOW, WHAT AND WHY something was done and is important, because we have seen solutions in modules very complex than overwritte very good features of the core and the main reason is "Leak of documentation that support the reasons" -- I'm almost sure that openerp can host at least a pair of ears to this meeting, Fabien what do you think??. my 2 cents,,, planify the meeting we want to participate, we can begin with IRC and this forum post to become in a very great resume, to planify a great work and sprint. Chapeau enlightX ------------------------ Nhomar Hernandez CTO at http://openerp.netquatro.com -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=61193#61193 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
