Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Avatar

Re: Company as maintainer

by
Acsone SA/NV, Stéphane Bidoul
- 28/10/2022 10:04:32
That said, even if that works, we need to be careful with this, as we would not want the maintainers key to become a marketing device for companies.

-sbi

On Thu, Oct 27, 2022 at 5:04 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hi Francesco,

What you put in the maintainers key must be valid GitHub handles.
It may work if you put both a team of your company (to receive notifications) and a user of your company (to get permissions to ocabot merge).
Can you try and ping me on the PR so I can follow the process?

-sbi

On Thu, Oct 27, 2022 at 4:47 PM Francesco Foresti <notifications@odoo-community.org> wrote:
Thanks Pedro, 

what I meant was either:

- assigning a "companyname" github account as maintainer of the module, or 
- both "companyname" and "devname" as maintainers. 

I don't think there's any issue in having multiple maintainers of a module?

Cheers

Francesco

Il giorno gio 27 ott 2022 alle ore 16:32 Pedro M. Baeza <notifications@odoo-community.org> ha scritto:
The problem is that all checks go through the GitHub user, so there's no notion of other grouping form (like GitHub organizations) that allows that. It would be interesting, but it should be implemented. The per user approach is also for not having noise in mid-size organizations.

Regards.

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



--

Francesco Foresti
Sicurpharma Srl
+39 333 8123 790

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

Reference