I reiterate (ceterum censeo) towards Odoo SA the most important point:

Make some script connected with webhooks (or as a last resort, periodically scanning the repo), which pareses issue and comment text, and looks for special well documented tags. (Think about "{tag}" ) The suggestion for implementation details follows, if you're not intrested jump over this parragraf:

- (optionally) provide similar logic for community milstones, so community can better organize it's actual coding efforts. A implementation suggestion would be the following milestones maintained by selected (benevolent dictatorial) oca-contributors:

"oca-main", "oca-next", "oca-bluesky"

I hope, reader, you found this useful, and will be willing to undertake directed action which helps getting this setup soon. Please, if that sounds and adequate request to you, abstain from all too general purpose feedback.

Martin Trigaux, you have shown, with you're status report on translation to everyone the tacit benefits of transparency. I hope I can, based on a common understanding about the power of transparency in the organization of multitudes, convince you to buy in on this idea and help to provide internal guidance to make this idea happen ;-)

+1
On 30.07.2015 11:17, Alan Bell wrote:
>
> what I am after is not Odoo fixing all the issues, I am after some
> kind of triage, or discussion, some comment saying "yeah, that seems
> valid, go ahead and fix it" or "you are wrong, it works fine" or "you
> are thinking about it all wrong, you should be doing this instead" or
> "fix it in your own instance if you want, it isn't inline with the
> project goals".
>
> Alan.
>
>
--
twanda AG
Ermin Trevisan
Artherstrasse 19
CH-6318 Walchwil
T +41 41 758 1515
M +41 79 208 7373
E trevi@twanda.com