1. Mailing Lists
  2. Contributors
  3. Re: "Adopt a Module" campaign?

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: "Adopt a Module" campaign?

Re: "Adopt a Module" campaign?

Avatar

Re: "Adopt a Module" campaign?

by
Acsone SA/NV, Stéphane Bidoul
- 19/11/2019 15:58:17
Excellent! Enabling such a campaign was part of the goals when we added the maintainer role back then.

Doing it in the travis lint phase is perhaps too big a step? An alternative could be to have the bot commenting on new pull requests for addons that have no maintainers.

Best regards,

-sbi


On Tue, Nov 19, 2019 at 10:42 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
I agree to volunteer, as long as we agree on approach and steps. In my mind, every repository should have a “Adopt Me” issue with “help” wanted, where bot will maintain a list of modules that are not adopted. And periodic "call for maintainers” on events?
As for lint: have no idea how to approach this, “if commit has a new file __manifest__.py then do something"

On 19 Nov 2019, at 11:27, Sylvain LE GAL <sylvain.legal@grap.coop> wrote:


Sylvain LE GAL - Twitter
GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
Site Web | FramaSphere | Facebook
3 Grande rue des Feuillants, 69001 Lyon
Bureau : (+33) 09.72.32.33.17 - Astreinte : (+33) 06.81.85.61.43
Member of the OCA (Odoo Community Association)


Le mar. 19 nov. 2019 à 10:17, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
Well, OK for both, but resources are needed to perform that, so if you volunteer for performing them, +1 for me.

Regards.

El mar., 19 nov. 2019 a las 10:12, Alexey Pelykh (<alexey.pelykh@gmail.com>) escribió:
How to perform that?

Ask them, very-very politely
Tecnnically,
- In a first step, it's quite easy to add maintainers keys in the odoo modules that fetch github code. (https://github.com/OCA/interface-github)
- In a second step a nice bot can create PR adding maintainers for some (all modules). (a little more complex, but not so hard) Can be an objective of a code sprint.

regard.

Are you suggesting Travis to fail if no maintainer is declared?

For new modules, yes. For current ones - give warning. It makes no sense of adding module and not becoming a maintainer for it (unfortunately, I did the same for some time because lack of knowledge)


On 19 Nov 2019, at 11:02, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:

> 1) “noone”’s modules should be adopted either by their original author(s) or by volunteer

How to perform that?

> 2) add a lint to ensure when module is added, it has a declared maintainer

Are you suggesting Travis to fail if no maintainer is declared?

Regards.

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

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


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

Reference