1. Mailing Lists
  2. Contributors
  3. Re: The removal of the core maintainers team

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: The removal of the core maintainers team

Re: The removal of the core maintainers team

Avatar

Re: The removal of the core maintainers team

by
Open Architects Consulting, Houssine BAKKALI
- 06/01/2016 10:27:15
Agreed wiht Stefan, at the time everybody are saying that we are lacking of resources for reviewing and for merging PR. we can't just wait that only a member of the board will find the time to do it of the PSC members are too short of time or simply not enough to do the job correctly.

As said Stefan the mission of the board isn't that... Core maintenairs Team should strenghtened instead of being suppressed...

2016-01-06 10:08 GMT+01:00 Stefan Rijnhart <stefan@opener.am>:
Hi,

I was very much disappointed (and surprised, but that was my fault for
not closely reading the OCA newsletter) to see that the Core Maintainers
Team on Github was removed a couple of days ago.

This was a team of broadly oriented and highly qualified developers,
committed to the goals and standards of the OCA, that could perform
merges and manage labels (PR statuses) on all OCA projects. I enjoyed
being part of that team because it allowed me to do the whole review
trajectory from setting the target branch on someone's PR to performing
the merge after the required number of approvals was acquired.

We discussed this in the community recently here:
https://odoo-community.org/groups/contributors-15/contributors-27648?mode=date&date_begin=2015-10-01&date_end=2015-11-01.
The concensus was that PSC reviews were not mandatory, implying that the
core maintainers group was functioning well. And now the board goes and
overrules a community discussion. IMHO the OCA should strive to a
*larger core maintainers team* instead of trying to micromanage each
project with one or two contributors. During my time at the board I have
always resisted the tendency of the board to put up their bureaucracy
and hierarchical structures but there you go.

Just one example: there is this guy, he is the only person in
l10n-romania. He made some requests on Twitter so I came over and helped
out a little bit
(https://github.com/OCA/l10n-romania/pull/5#issuecomment-169255527), but
I don't really want to be in their team. Who is there to merge? There is
only the board who can do that then. So here the OCA are moving part of
the real need for this team from the broader community (even if it is
only 10 developers some of which are actually in the board) back to the
shoulders of the board. That is not why they were elected. And again, I
(and not only me) work in the whole broad field of Odoo be it banking,
POS, HR, framework, web client, website, warehousing or whatever. If you
put me on all those teams, you make me co-responsible for whatever is
going on in all those projects but that is just not realistic.

I would therefore plead for the return of the core maintainers team.

Thanks,
Stefan.

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


Reference