|
Hello to all, I am not sure if you are
planing to control every module that is developed and the
developer wants to upload it to the community branch.
IMHO this is going to be a hard work for the reviewers, and maybe
a bunch of modules are going to leave "pending" from the
developer, they are not going to change the code because another
one has told it, even if the change was right.
Maybe this could leave us with a lot of branches with the
"community modules" and an official "community module" branch
with a few ones, my two cents.
Greetings!
El 22/11/12 16:31, Niels Huylebroeck escribió:
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"
_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp
--
Daniel Campos
Técnico programador OpenERP, Avanzosc, S.L. Office phone / Tfono
oficina: (+34) 943 02 69 02
www.openerpsite.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
