openerp-community team mailing list archive

[Ovnicraft <ovnicraft@xxxxxxxxx>]

On Thu, Nov 22, 2012 at 6:30 PM, Eric Caudal <eric.caudal@xxxxxxxxxxxxxx>wrote:

>  +1
> The community branch should be absolutely bugproof and well designed.
> Let's try to favor quality over quantity
>


I am totally agree with you, please rules must be that *rules* no more +100
modules and ~90 does not works, if community works very well we get
bugproof and well designed as you said.


Best regards,

>
>
>   [image: openerp]
>
> *Eric CAUDAL*, Elico Corp, Shanghai.eric.caudal@xxxxxxxxxxxxxx
> Cell: + 86 186 2136 1670. Skype: elico.corp*Premium Certified Training Partner - OpenERP Ready Partner.*
>
>
> [image: Premium CTP]
> http://www.elico-corp.com
> On 11/22/2012 11:31 PM, Niels Huylebroeck wrote:
>
> 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
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Cristian Salamea
@ovnicraft