openerp-community-committers team mailing list archive

["Christophe CHAUVET (SYLEAM)" <christophe.chauvet@xxxxxxxxx>]

2010/11/17 Albert Cervera i Areny <albert@xxxxxxxxxxx>

>  Given that most of you have been pretty fast at subscribing to the
> mailing list, I resend the welcome message so we can start the discussion.
> Please add any comments you may have about what you expect out of this
> group. (Comments about how good tryton is are forbidden :P)
>
> ----
>
> Hi everyone,
>
> just a few things to start:
>
> I've chaged the group name. It's now called 'Committers' as I misspelled
>
> it in the first place (thanks to Davide for pointing out).
>
> We now have a mailing list as suggested by Jan Verlaan. Please,
>
> subscribe. I don't remember how it is changed in launchpad but by now
>
> the mailing list is only available to team members. I'd suggest to make
>
> the mailing list opened to everyone so that decisions as clear as
>
> possible (that includes the policies we decide below).
>

+1


>  By now, everyone I've approved have been set as administrators. Except
>
> for Pexego an NaN teams because I think only individuals should be
>
> administrators (Borja, I think you should be there, so you could
>
> subscribe individually and I'd add you as administrator). From now on I
>
> propose the policy that to become an administrator, 3 existing admins
>
> must approve the new one.
>

+1


>  I think everyone's idea (please, tell us if your idea is different)
>
> wants a community branch to make it more stable than the official one so
>
> the idea is that we need to ensure that only those with a good knowledge
>
> have access to the branches. That's why I only approved those that I
>
> know or have seen for a long time around OpenERP. That doesn't mean more
>
> people shouldn't become members but I think we should stablish a simple
>
> policy. For example, I'd suggest that to become a member at least 3
>
> existing members (not administrators) of the team should agree with it.
>

I thinks Commiters group must be 10 - 15 persons max, 1 person per company
(if possible)

But a second group "Community Members" must be created, and all people want
to join this group are accept automaticaly

The Commiters groups have a full access on the community branch (server,
addons, etc..)


>  So please, take a look at the list of people waiting for approval and if
>
> you know them and want to approve them tell us in the mailing list. (Of
>
> course, as long as you agree with the previous points).
>

See above


>  I'd like everyone to comment on my suggestions. These are only
>
> suggestions, so everything should be built from the community, not an
>
> individual, but at the same time I didn't want that to be a mess from
>
> the very beginning so that we should end up creating another group just
>
> because too many people is in.
>

+1

Regards,
-- 
Christophe Chauvet
Directeur Technique/CTO
27 Avenue Jean Mantelet
61000 Alençon, France
http://www.syleam.fr/


********************************************************************************
Ce message et toutes les pièces jointes (ci-après le "message") sont établis à
l'intention exclusive de ses destinataires et sont confidentiels. Si vous
recevez ce message par erreur, merci de le détruire et d'en avertir
immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa
destination, toute diffusion ou toute publication, totale ou partielle, est
interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer
l'intégrité de ce message, SYLEAM décline toute responsabilité au titre de ce
message, dans l'hypothèse où il aurait été modifié.

This message and any attachments (the "message") is intended solely for the
addressees and is confidential. If you receive this message in error, please
delete it and immediately notify the sender. Any use not in accord with its
purpose, any dissemination or disclosure, either whole or partial, is prohibited
except formal approval. The internet can not guarantee the integrity of this
message. SYLEAM shall not therefore be liable for the message if modified.
********************************************************************************