Skip to Content
  2. Mailing Lists
  3. Contributors
  4. Re: Company as maintainer

Archives

Contributors

Re: Company as maintainer

Re: Company as maintainer

Re: Company as maintainer

Hi,

I share the same observation more and more: there is a need to track/manage modules instead of repositories.

Going in this direction I started to work on this topic which started around OpenUpgrade only at first until I realized that this need was broader than OpenUpgrade only:

I have prepared a prototype to share the information per module and which can be tested here https://oca-cm-15.komit.link

The Issues and PRs are linked to the module based on the name of the Issues/PRs so at this stage it's not reliable.
But naming conventions could be enforced by github checks I guess, at least for the PRs.

Adding a notification mechanism should not be complicated.
I am currently working on a v2 of the prototype.
I am open to sharing the code, which I already did upon request.
I am also open to discussions.

Best regards,

Jean-Charles



On Sat, Oct 29, 2022 at 4:57 PM Pedro M. Baeza <notifications@odoo-community.org> wrote:
I'm afraid I don't have a solution for that. I'm subscribed to everything... and yes, lots of noise. But it also serves for having a whole picture, as "what are the modules I am interested in?" Maybe a new module arises over a feature I want.

I use my self-called "5 seconds rule" for dealing with the huge amount of notifications: 5 seconds to decide if to discard it, answer immediately if it takes less than a minute, which can be my distraction window, or let it in my inbox for a later and more calm answer. This allows me to be reactive enough as well as not requiring too much time.

Regards.

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

by Jean-Charles Drubay - 01:35 - 30 Oct 2022

Reference

  • Company as maintainer
    Hello, 

    since we have several devs working on modules developed by our company in OCA, we'd like to attribute the role of "maintainer" of such modules to a company github account in order to centralize: 

    - notifications about changes to modules we have originally developed
    - questions and communications about the aforementioned modules
    - merging of minor changes such as this one

    Would it be possible for us to do so?

    Thanks for your opinion!

    --

    Francesco Foresti
    Sicurpharma Srl
    by Francesco Foresti - 04:20 - 27 Oct 2022