Archives
Contributors
Re: Company as maintainer
> The main point of this is keeping track with proposed changes
to modules we have developed, migration to other versions, and to be
contacted in case there's any request about them.
Yes, being notified when something affects addons you are interested in (whether or not you maintain it actively) is an important feature, and difficult to achieve at the moment.
But the more I think of it the more I think using the maintainers key for that is actually diverting it from its intended purpose.
If everyone starts putting their team names there just to get notifications... well it's going to be bizarre :)
I wonder if people around here have found good solutions for that.
Or if there are good ideas that would not be too hard to implement.
-sbi
by Stéphane Bidoul - 11:20 - 29 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 oneWould it be possible for us to do so?Thanks for your opinion!--Francesco ForestiSicurpharma Srl
by Francesco Foresti - 04:20 - 27 Oct 2022
