← Back to team overview

openerp-community team mailing list archive

Re: [Openerp-community-leaders] [Openerp-expert-framework] New Community Organization for OpenERP

 

Dear all,


Niels and Eric are now in the team. Thank you all for your trust and enthusiast about this new organization !

Let's have this dialog continue on the new mailing list as Stefan suggested  (openerp-community-reviewer@xxxxxxxxxxxxxxxxxxx).

@Daniel & Pieter: Everyone is still free to develop their own module in their branches as always. It's a start to build stronger, more reliable and more "shared" module between the community, with the support of more than just one person, partner or company. For that we need to review each other's work. Nobody is forced to those rules in their own branches or project. You're free to record them on app.openerp.com and distribute them if you want. No hurt to be done here I think (and hope :)

Best regards,


Joël



Le 22 nov. 2012 à 16:31, Niels Huylebroeck <nh@xxxxxxxxxx> a écrit :

> Thanks all for the confidence for mentioning me, I've been in a very busy week and was unable to jump into the conversation until now.
> 
> I understand there was some concern about quality control and who gets to decide "when" or "if" something is acceptable.
> While this may sound harsh and "exclusive" I'd like to remind everyone that we are not here to make life difficulty for other people, we do this quality check so both we and new people can learn from their mistakes and at the same time produce something we can all agree on. While the rules for this are not set in stone, this sort of eco system has worked out for many other opensource projects (Linux, Firefox, ...) where the most contributing members typically have a better understanding or more pronounced opinion on code changes.
> 
> I personally think we should not accept new modules without a thorough checkup of it's necessity, usability, generic use and code quality. Using a veto-no system here (with some help/explanation of why ofcourse) would be most efficient I think. So anyone in the group can veto flag a merge request which will attract more attention and more eyes on the code which should result in a faster alteration of the code and finally acceptance.
> 
> The way bazaar is structured people can still easily make their own branch with their custom code and just do merges from our set of "stable community" branches without losing much time.
> We should strive for modules that would never fail if you just install them. Ideally I would like to be able to install any module from these branches while sitting with a customer and not get any stacktraces which I would have to examine to see what is going wrong.
> 
> I'd also like to give my vote of confidence to following people: Jay Vora (and Serpent CS), Eric Caudal, the camp2camp team and Stefan Rijnhart
> 
> 
> Regards,
> Niels "Red15"
> 
> 
> 2012/11/22 Serpent Consulting Services <serpentcs.lp@xxxxxxxxx>
> +1 Niels (agaplan)
> 
> On Thursday 22 November 2012 08:39 PM, Maxime Chambreuil wrote:
>> +1 for Eric
>> 
>> -- 
>> Maxime Chambreuil
>> 1-514-276-5468 #126
>> 
>> Dear all,
>> 
>> 
>> A little summarizing of all candidates and their status ;)
>> 
>>  - Vauxoo Reviewer team is now 5 people. We all agreed to trust Nhomar here so I added them to the reviewer team.
>>  - Jay Vora claimed in favor of adding his team "serpent CS" instead of his name. I also know Hussein and I can also vote for him. So as others seems to agree, I add his team as well.
>> 
>> I want to remember that we accept teams as long as their maintainer promise not to add other people inside without asking the community's vote. Anyone who do not follow this rule may see his whole team removed from the OpenERP Community Reviewer. Not to be rude here, just a matter of trust between us all.
>> 
>> Then we have other candidates to vote for. Please give your voice if you know their work/skills. I gave it to those I can  :
>> 
>>  * Stephane Bidoul (Acsone)  https://launchpad.net/~sbi
>> 
>>  * Niels Huylebroeck (Agaplan)  https://launchpad.net/~red15 
>>    (1 endorsed him, I gave my vote)
>> 
>>  * Eric Caudal (Elico Corp. China)  https://launchpad.net/~elicoidal
>>    (I voted for him)
>> 
>> Well, we don't actually have rules on who to accept, which will soon be a problem. If anybody want to have a try on writing them, please do it. 
>> 
>> Don't forget you can also apply for on or more specific domain as well.
>> 
>> 
>> Best regards,
>> 
>> 
>> Joël
>> 
>> 
>> 
>> Le 22 nov. 2012 à 13:12, Stefan Rijnhart <stefan@xxxxxxxx> a écrit :
>> 
>> 
>> -- 
>> 
>> Joël Grand-Guillaume 
>> Division Manager
>> Business Solutions
>> 
>> Camptocamp SA
>> PSE A, CH-1015 Lausanne
>> http://openerp.camptocamp.com/
>> 
>> Phone: +41 21 619 10 28
>> Office: +41 21 619 10 10
>> Fax: +41 21 619 10 00
>> Email: joel.grandguillaume@xxxxxxxxxxxxxx
>> 
>> 
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openerp-community-leaders
>> Post to     : openerp-community-leaders@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openerp-community-leaders
>> More help   : https://help.launchpad.net/ListHelp
>> 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-framework
> Post to     : openerp-expert-framework@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-expert-framework
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
> -- 
> Niels Huylebroeck
> Lead Architect   --   Agaplan
> Tel. : +32 (0) 93 95 98 90
> Web : http://www.agaplan.eu
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community-leaders
> Post to     : openerp-community-leaders@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community-leaders
> More help   : https://help.launchpad.net/ListHelp

-- 

Joël Grand-Guillaume 
Division Manager
Business Solutions

Camptocamp SA
PSE A, CH-1015 Lausanne
http://openerp.camptocamp.com/

Phone: +41 21 619 10 28
Office: +41 21 619 10 10
Fax: +41 21 619 10 00
Email: joel.grandguillaume@xxxxxxxxxxxxxx


References