Just a word, started reviews again yesterday and I promise to do more in the future (I really had a few rush things in the last months that kept me away from that). I also want to mention that at Akretion we also made the internal commitment to to get more reviews from the other Akretion people too. So this is a process ramping up, but this is certainly what we aim at and we don't really see any alternative than building up such a meritocracy.
Also, I want say welcome to Pedro. I was on the line, but if that's of any help, my vote would have gone for him too, I could see all the work he has been doing in the Spanish localization and above and we are happy because in Brazil we have a few synergies with the Spanish localization and what Pedro did/does. Best regards. On Wed, Sep 11, 2013 at 5:51 AM, Ana Juaristi <[email protected]> wrote: > Hi Joël, at the end I don't know if you decided or not including Pedro > Baeza as reviewer but if it's yes, then one task 3) is missing on your > sumary > > Thank you: > Ana > > > 2013/9/11 Joël Grand-Guillaume <[email protected]> > >> Dear all, >> >> >> Thanks you for your input on that topic. So if I summarize: >> >> 1) Removal of people from the reviewer team (nothing to do again with >> contribution, just to have people in there that take time to review and >> merge others work): >> >> We agreed to remove: >> >> Borja López Soilán : https://launchpad.net/~borjals >> Jordi Esteve : [email protected] >> Olivier Dony: [email protected] >> >> We agreed to keep: >> >> Raphaël Valyi : https://launchpad.net/~rvalyi >> >> Unless someone write his discomfort here, I will remove the named people >> at the end of the week. Still, they can apply again in case their interest >> come back, we'll be more than happy on that :) ! Raphaël, great to have you >> on board, I'm looking forward to have your review beside ours, thanks ! >> >> 2) Usage of named person instead of team. It seems that everybody vote >> for that, so I would remove those following team: >> >> * Camptocamp Community Reviewer >> * Vauxoo Community Reviewer >> * Serpent Consulting Services >> >> And include their actual members, which are: >> >> For Vauxoo: >> * Tulio Ruiz (Vauxoo) : https://launchpad.net/~truiz >> * Nhomar - Vauxoo : https://launchpad.net/~nhomar >> * Moisés López - http://www.vauxoo.com : >> https://launchpad.net/~moylop260 >> * Isaac López Zúñiga - http://www.vauxoo.com : >> https://launchpad.net/~isaako34 >> * hbto [Vauxoo] http://www.vauxoo.com : >> https://launchpad.net/~humbertoarocha >> >> For Camptocamp: >> * Alexandre Fayolle : https://launchpad.net/~alexandre-fayolle-c2c >> * Nicolas Bessi : https://launchpad.net/~nbessi-c2c >> * Guewen Baconnier : https://launchpad.net/~gbaconnier-c2c >> * Joël Grand-Guillaume : https://launchpad.net/~jgrandguillaume-c2c >> >> For Serpent Consulting Service: >> * Here I don't find any person in here as it is a login for a single >> account and not a team. So please provide me the personal account to >> include instead or I will have to remove you here :( >> >> >> Note that as Daniel said, everybody here is free to make his review, even >> if not part of the reviewer team, so please, join the effort ! >> >> I'll do this by the end of the week or beginning of the next one. I >> really hope this will helps moving forward to straighten the community >> effort. >> >> Best regards to you all, >> >> >> Joël >> >> >> >> >> >> On Wed, Sep 11, 2013 at 9:29 AM, Joël Grand-Guillaume < >> [email protected]> wrote: >> >>> Dear Raphaël, >>> >>> >>> I never mean here (and never will) that you do not contribute to OpenERP >>> !! >>> >>> The thread here is about having an OpenERP Community Reviewer team with >>> active people in it. That's not the same. You do contribute a lot, >>> everybody agree on that. But without any harm, you are not making review. >>> That's 2 different things. >>> >>> We all had one year (a bit less) to prove our investment here, and trust >>> me, I do not have lot of time in there either, but I try at least to give >>> some time every month for it. >>> >>> So, if you say you still want to review and take time for this, fine for >>> me, I'm more than happy trust me ! That's a good news :) >>> >>> Cheers, >>> >>> >>> Joël >>> >>> >>> >>> >>> >>> On Tue, Sep 10, 2013 at 6:36 PM, Raphael Valyi <[email protected]> wrote: >>> >>>> On Tue, Sep 10, 2013 at 1:03 PM, Nhomar Hernández <[email protected]>wrote: >>>> >>>>> >>>>> >>>>> >>>>> 2013/9/10 Leonardo Pistone <[email protected]> >>>>> >>>>>> Raphael, >>>>>> I know very well you are a contributor, and I think most people do. >>>>>> If you say you're willing to review somewhat soon, that's fine by me. >>>>>> >>>>> >>>>> Same for me. >>>>> >>>>> No problem mantain Raphael. >>>>> >>>>> BTW, if you put openly in what you are working this kind of >>>>> misunderstood will be avoided. >>>>> >>>>> Our unique way to measure is the activities in the "Reviewer Team" >>>>> what is the work in what we are working now. >>>>> >>>>> But if you think to finish you big job you will need the reviewer >>>>> access, for me is fine keep you in the team. >>>>> >>>> >>>> Also, as a complement, I would like to let you know that at the >>>> Brazilian part of Akretion, we recently did a major push forward of Noviat >>>> work around cashflow (in a 150 users/500 employees mechanical industry >>>> company), interacting with Noviat (Luc de Meyer) and even Ana Juaristi. >>>> Polishing that cashflow work should bring us on par with major ERP players >>>> around. Specifically we worked on creating mixin to create cashflow lines >>>> from other ERP managed facts with ease. >>>> We should still test a bit more in production and polish the feedback >>>> around this, but this is coming. In the meanwhile, this made me release >>>> Noviat relies on their bank_statement_extension module for that (and we did >>>> too, v6.1 project). We will need to refactor bank statement extension >>>> modules to extract a minimal common denominator. I will happily participate >>>> to this clean up work, but that won't be that easy as it has deep >>>> implications with eBanking and SEPA eventually. I hope we won't end up as >>>> fragmented the account_payment extensions modules. If we start soon enough >>>> we have more chance to get that clean early. So at some point, the >>>> impression you get if smb participate or not depends a bit where exactly >>>> you look or not. And we didn't consider this to be polished enough to >>>> bother the community with prototyping with us at these early stages. >>>> Anyway, not trying to excuse me for little reviews these months, but >>>> just informing you on what we have been doing and may not be immediately >>>> visible to you, but certainly is useful in the community prospective. >>>> >>>> Generally speaking, I think it will be important OCA chart members vote >>>> for what modules OCA should focus or not. By trying to be too ambitious, we >>>> loose focus from the core and decrease the quality of the core. And we >>>> shouldn't reproduce the errors from the past with god branches gathering >>>> too many modules with too little quality/reusability and incompatibilities >>>> between branches as soon as you need to patch something as you often need >>>> to the framework being what it is (with good things coming in v8 >>>> fortunately). This is specially because I have this concern in mind that >>>> I'm ambitious regarding the git synch because IMHO this is the only tool >>>> (or say long with hg) that is fast enough (hey unlike with bzr git-subtree >>>> works) to seamlessly approach the one module = one branch that we will need >>>> soon to avoid spaghetti branches again. With these bridges, we could even >>>> think about a continuous, modules extraction into sub-branches and >>>> continuous publication as pip modules. When we will have this, things will >>>> be much easier when one will need to patch just one module to make it >>>> compatible with one localization or something like that. Today, I would say >>>> the complexity doesn't scale yet, it's just too easy people need to patch >>>> branches in incompatibles ways at the same time and at the end it's still a >>>> headache to maintain (though easier than in the past) and we end up too >>>> often with branches per customers. And if it's too hard, community is too >>>> small, integrators aren't profitable enough to grow and to maintain >>>> themselves and that's a shot in the feet for everybody. So in a word, today >>>> we still need these grouping branches. But in the future, that will again >>>> hit a scalability limits we will neeed to overcome with a better tool >>>> chain, and I've been working a bit on that, as well as others I'm sure. >>>> >>>> Finally, ending with an optimistic note: things like fixing the >>>> on_change API in v8 (as it seems to be done in Raphaël Collet's 'rco' >>>> branch) will dramatically improve this situation of incompatible modules. >>>> >>>> >>>> Regards. >>>> >>>> -- >>>> Raphaël Valyi >>>> Founder and consultant >>>> http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi> >>>> +55 21 2516 2954 >>>> www.akretion.com >>>> >>>> >>>> >>>> _______________________________________________ >>>> Mailing list: https://launchpad.net/~openerp-community >>>> Post to : [email protected] >>>> 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 >>> >>> >>> >> >> >> -- >> >> >> *camptocamp* >> INNOVATIVE SOLUTIONS >> BY OPEN SOURCE EXPERTS >> >> *Joël Grand-Guillaume* >> Division Manager >> Business Solutions >> >> +41 21 619 10 28 >> www.camptocamp.com >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openerp-community >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~openerp-community >> More help : https://help.launchpad.net/ListHelp >> >> > > > -- > CEO Avanzosc, S.L <http://www.avanzosc.es> : Office phone / Tfono > oficina: (+34) 943 02 69 02 > Ana Juaristi Olalde <http://www.anajuaristi.com/>: Personal phone: 677 93 > 42 59. User/usuario skype: Avanzosc > www.openerpsite.com > > > *El contenido de esta comunicación y de toda su documentación anexa es > confidencial y se dirige exclusivamente a su destinatario. El uso no > autorizado de esta información está prohibido por la legislación vigente. > Si usted no es el destinatario le rogamos nos lo indique, no comunique su > contenido a terceros y proceda a su destrucción. Disculpe las molestias que > le haya ocasionado la recepción indebida de este e-mail. Sus datos figuran > en un fichero cuyo titular es Avanzosc, S.L., a quien usted puede dirigirse > para ejercer sus derechos de acceso, rectificación, cancelación y oposición > en Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), Tef. 943 02 69 02 - > [email protected] <[email protected]> * > * * > > *Komunikazio honen edukia eta dokumentazio erantsia konfidentziala da eta > hartzaileak bakarrik jaso beharko luke. Indarrean dagoen legeriak debekatu > egiten du bertan eskainitako informazioa baimenik gabe erabiltzea. > Komunikazioa zuri iritsi bazaizu, baina zu ez bazara hartzailea, mesedez, > guri jakinarazi, eta jasotako informazioa ez inori jakinarazi eta suntsitu. > Barkatu okerreko email hau jasotzeak eragindako eragozpenak. Zure datuak > Avanzosc, S.L. enpresaren fitxategietan sartuta daude. Zure datuak atzitzea > eska dezakezu, bai eta, datuak zuzentzea, ezereztea eta tratamenduari > aurka egitea ere. Horretarako, enpresara jo dezakezu, helbide honetan: Julio > Urkijo, 32, 20720, Azkoitia (Gipuzkoa), telefonoa: 943 02 69 02 - ** > [email protected] <[email protected]> * > *This message and all documents attached to it are confidential and > intended only for the person or entity to which it is addressed. Any use of > this information by unauthorised persons is prohibited under current > legislation. If you received this message by error, please advise us, > destroy it and refrain from communicating its contents to third parties. We > apologise for any inconvenience receiving this email improperly may cause > to you. Your personal data are included in a file owned by Avanzosc, S.L. > If you want to exercise your rights of access, correction, erasure and > objection you can contact the Controller at Julio Urkijo, 32, 20720, > Azkoitia (Gipuzkoa), T: 943 02 69 02 – > [email protected]<[email protected]> > * >
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
