Archives
Contributors
-
Re: "Adopt a Module" campaign?
On Wed, Nov 20, 2019 at 11:02 AM Guewen Baconnier <guewen.baconnier@camptocamp.com> wrote:> An alternative could be to have the bot commenting on new pull requests for addons that have no maintainers.I created https://github.com/OCA/oca-github-bot/issues/93 to track this and link to ongoing work on a related task.-sbi
by Stéphane Bidoul - 12:31 - 20 Nov 2019 -
Re: "Adopt a Module" campaign?
> An alternative could be to have the bot commenting on new pull requests for addons that have no maintainers.I like this!On Tue, Nov 19, 2019 at 4:02 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote: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,-sbiOn 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: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 politelyTecnnically,- 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 volunteerHow to perform that?> 2) add a lint to ensure when module is added, it has a declared maintainerAre 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
_______________________________________________
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
by Guewen Baconnier - 11:01 - 20 Nov 2019 -
Re: "Adopt a Module" campaign?
+1 with Stéphane commentSergio CoratoIl giorno mer 20 nov 2019 alle ore 08:01 Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> ha scritto:Hi,That's a great initiative! I'm completely in-line with this Idea.+1 for the bit to comment as Stephane suggested.RegardsJoëlLe mar. 19 nov. 2019 à 19:02, David Arnold <dar@xoe.solutions> a écrit :Make an orphan-modules-list? like awesome lists, but exposing gruesome reality?On Tue, Nov 19, 2019 at 10:02 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote: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,-sbiOn 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: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 politelyTecnnically,- 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 volunteerHow to perform that?> 2) add a lint to ensure when module is added, it has a declared maintainerAre 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
_______________________________________________
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
_______________________________________________
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
by Sergio Corato - 09:01 - 20 Nov 2019 -
Re: "Adopt a Module" campaign?
Hi,That's a great initiative! I'm completely in-line with this Idea.+1 for the bit to comment as Stephane suggested.RegardsJoëlLe mar. 19 nov. 2019 à 19:02, David Arnold <dar@xoe.solutions> a écrit :Make an orphan-modules-list? like awesome lists, but exposing gruesome reality?On Tue, Nov 19, 2019 at 10:02 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote: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,-sbiOn 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: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 politelyTecnnically,- 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 volunteerHow to perform that?> 2) add a lint to ensure when module is added, it has a declared maintainerAre 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
_______________________________________________
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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Joël Grand Guillaume - 08:00 - 20 Nov 2019 -
Re: Place to share knowledge/tools on deployment
@Georg speccing for kops backend taskers startedAn opportunity for cleaning the python middleware.Also to slice off the essentially broken odoo built in scheduler/server :D (maybe)On Tue, Nov 19, 2019 at 5:42 PM David Arnold <dar@xoe.solutions> wrote:Planned refactoring to this regard from our side:- Modularize- Swap subcommands easily ("make your own `odooup`")On Mon, Nov 18, 2019 at 3:42 PM Georg Notter <georg.notter@agenterp.com> wrote:Haha sorry wrong targetMit freundlichen Grüßen
We look forward to see you. Best Regards
Dipl. Ing. (Fh) Georg Notter
Agent ERP GmbH
www.agenterp.comAm 18.11.2019 um 21:07 schrieb Georg Notter <georg.notter@agenterp.com>:
Moin david ruf mal wieder durch!Mit freundlichen Grüßen
We look forward to see you. Best Regards
Dipl. Ing. (Fh) Georg Notter
Agent ERP GmbH
www.agenterp.comAm 16.11.2019 um 02:38 schrieb David Arnold <dar@xoe.solutions>:
And beaten again: https://github.com/OdooOps/awesome-odoo-ops#readmeOn Fri, Nov 15, 2019 at 8:28 PM David Arnold <dar@xoe.solutions> wrote:Sorry, I've beaten myself, the reference should always be:https://github.com/OdooOps/awesome#readme(with the same document reference to the readme at the end)On Fri, Nov 15, 2019 at 8:27 PM David Arnold <dar@xoe.solutions> wrote:For now, there is a skeleton carefully ripped from: https://github.com/sindresorhus/awesomeFirst couple of PRs should come soon from myself, but please feel free to submit your own PRs abiding by the contributing rules. (those are relatively simple for once ;-)On Fri, Nov 15, 2019 at 5:33 PM David Arnold <dar@xoe.solutions> wrote:Now, for the first time in a row... :DOn Fri, Nov 15, 2019 at 5:06 PM Jordi Riera <jordi.riera@numigi.com> wrote:Hello David,Did you have the time to move forward with the awesome repo/list ?Best,JordiLe jeu. 31 oct. 2019 à 10:37, David Arnold <dar@xoe.solutions> a écrit :True, Russell has put together some compelling user stories. I plan to process them somehow to that end.El jue., 31 oct. 2019, 7:47 a.m., Jordi Riera <jordi.riera@numigi.com> escribió:Great,And we can create traffic to the ODEPs through the awesome-list.We need to find the good catch phrases to inspire people to contribute on doc.Thank you David,JordiLe jeu. 31 oct. 2019 à 00:27, David Arnold <dar@xoe.solutions> a écrit :Ok. I like, lots of communities do those awesome-x listing ;-)A good mix catering to different levels of abstraction should gain enough traction over time, you're right, we need to create practical value, too.But I think, especially for the more involved people to let loose of their deer siloes, the foundation's need to be talked true with time and effort (hence ODEPs).Only through excellent community governance will we have a chance to eventually agree.This week, I intent to create that awesome-deployment-odoo-repo.BR,David A.El mié., 30 oct. 2019, 3:12 p.m., Jordi Riera <jordi.riera@numigi.com> escribió:Hello everyone,sorry for my silence in the previous days. Busy days as we all know.I think we should start small to grow slowly but surely.I like your enthusiasm, David, and feel free to lead the effort on the subject. While ODEPs seem great, I have the feeling that might scare a lot of contributors due to the mass of reading to do.In parallel to it, I would like to see something more practical, like an awesome-odoo-deploy, where we would see a list of all the tool to deploy odoo.I see that you have already a good list with:* doodba* odoo cloud platform...What do you think?OdooOps seems a good place to start. Could you create a new repo for the listing?Cheers,JordiLe mer. 30 oct. 2019 à 12:27, David Arnold <dar@xoe.solutions> a écrit :Yeah, OCA might probably endorse it later on when OCA wishes to. Absolutely!From a constituency point of view, OCA does not seem to be able to add shared legitimacy. This needs to be provided by the involved actors themselves.Namely, to my knowledge, those are:- Tecnativa (doodba)- Camptocamp (Odoo cloud platform, and other tooling, anthem, marabunta)- Acsone (odoo-bedrock, click-odoo, Bob templates, and other tooling)- Akretion (docky and other tooling)- XOE ( DockeryOdoo & OdooOperator and a couple of forks / mix&match from Acsone and Camptocamp)Can we pass the point where PRoC > PRoSP (Perceived Return on Collaboration > Persived Return on Siloed Project) for those actors?El mié., 30 oct. 2019, 1:27 a.m., Russell Briggs <russ@paraflyer.net> escribió:Great stuff David!Yeah it feels like this should eventually become an OCA project once it gets some traction, since it is potentially quite a fundamental community component?I will have a read and make some comments in a bit :)RussOn Wed, 30 Oct 2019, 9:57 AM David Arnold, <dar@xoe.solutions> wrote:By the way I commit by all means NOT to retain unique ownership on the OdooOps GitHub organization. Any meritable community, abiding by the self constituing decision making processes (e.g. ODEPs) is eligible to share the burdon. ;-)El mar., 29 oct. 2019, 3:50 p.m., David Arnold <dar@xoe.solutions> escribió:Hi all,I redacted a first ODEP 0002 in Order to propose the constituency of a docker base runtime repository.I stepped over some steps and wrote down everything I had in mind.For legitimacy building, please comment on the PR and indicate your level of approval:Approve: Section 1, Section 2, etc.Disaprove: Section 4Ideally we would get unanimous approval of the "Motivation" section, so this section could be merged quickly.According to the eminent approval levels I'll outfactor parts into separate PRs / Discussions.Please leave your opinion / approval level, even if you are only a user and no active committer of the Odoo docker community.BR,David A.El dom., 27 oct. 2019, 11:36 p.m., David Arnold <dar@xoe.solutions> escribió:I plan to eventually write up some "ODEPs" ( like python PEPs ) " Odoo Dev Enhancement Proposal " where I want to lay out the reasoning behind some design decisions I made in DockeryOdoo over the past few years.However, I have a problem: if there is no second owner of such proposals and if there is no legitimate approval process of any sort, it's going to be yet another tribal silo.So I hope by writing up some "ODEPs", the discussion might get a chance to become structured, hence contribution might get a chance to become structured, hence consolidation and mind share might become a chance to get structured. Hence a legitimate constituency for this topic (outside of OCA path dependent reasoning) will be possible.People might think "what an overkill", but ultimately, we all know, that pulling tribes together around a common goal is not only a challenging task since open source communities exist.Maybe the best approach is formulating understandable, complete and concise proposals in human readable form (the vision behind "ODEPs").My 2 cents.El dom., 27 oct. 2019, 10:07 a.m., Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:The interest will grow if the few involve here make it work...El dom., 27 de octubre de 2019 08:16, <admin@ygol.com> escribió:What is the next step for this to move on?- Should we put to vote Maxime's idea to create those 2 repositories? Where would they live?- Or is it better to keep the discussion outside of OCA? David Arnold prepared a place (odooOps)?It would be nice to know who is interested by this topic.tnx--Yves Goldberg------- Original message -----From: Maxime Chambreuil <mchambreuil@opensourceintegrators.com>To: Contributors <contributors@odoo-community.org>Subject: Re: Place to share knowledge/tools on deploymentDate: Tuesday, October 22, 2019 19:52Hi Jordi,I think we could start with:- one repository to store a base/minimal docker image + documented extensions.
- one repository per orchestrator (or 1 for all) where we can share configuration with documentation of how to orchestrate the previous Docker images
My 2 cents.On Tue, Oct 22, 2019 at 11:22 AM Jordi Riera <jordi.riera@numigi.com> wrote:Hello list,During the OCA code sprint in belgium, I had the opportunity to talk again about docker. While the first talk, in 2018, was focused on usage of Docker. This year, the discussion focused on orchestration solutions.The discussion was interesting and it was found that we could use a place to share good practices and solutions. Regarding orchestration, but also on dockers (odoo and other services like postgres, acsone/kwkhtmltopdf) and around deployments helpers (git-aggregator, gitoo, clik-odoo, etc.)How would you see it ?What do you think about to start with a single place where we could have docker-compose templates (or link to repo with templates) and best practices, FAQs, etc (I was thinking questions like: https://odoo-community.org/groups/contributors-15/contributors-148040?mode=thread&date_begin=&date_end=)The aim would be to ease the adoption of docker based infrastructure over OCA members. Docker-compose is a good tool to ease docker adoption.Let me know what you thinkJordi--
Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada
_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: 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
_______________________________________________
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
--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________
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
--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________
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
--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________
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
by dar - 03:11 - 20 Nov 2019 - one repository to store a base/minimal docker image + documented extensions.
-
Re: Place to share knowledge/tools on deployment
Planned refactoring to this regard from our side:- Modularize- Swap subcommands easily ("make your own `odooup`")On Mon, Nov 18, 2019 at 3:42 PM Georg Notter <georg.notter@agenterp.com> wrote:Haha sorry wrong target
Mit freundlichen Grüßen
We look forward to see you. Best Regards
Dipl. Ing. (Fh) Georg Notter
Agent ERP GmbH
www.agenterp.comAm 18.11.2019 um 21:07 schrieb Georg Notter <georg.notter@agenterp.com>:
Moin david ruf mal wieder durch!Mit freundlichen Grüßen
We look forward to see you. Best Regards
Dipl. Ing. (Fh) Georg Notter
Agent ERP GmbH
www.agenterp.comAm 16.11.2019 um 02:38 schrieb David Arnold <dar@xoe.solutions>:
And beaten again: https://github.com/OdooOps/awesome-odoo-ops#readmeOn Fri, Nov 15, 2019 at 8:28 PM David Arnold <dar@xoe.solutions> wrote:Sorry, I've beaten myself, the reference should always be:https://github.com/OdooOps/awesome#readme(with the same document reference to the readme at the end)On Fri, Nov 15, 2019 at 8:27 PM David Arnold <dar@xoe.solutions> wrote:For now, there is a skeleton carefully ripped from: https://github.com/sindresorhus/awesomeFirst couple of PRs should come soon from myself, but please feel free to submit your own PRs abiding by the contributing rules. (those are relatively simple for once ;-)On Fri, Nov 15, 2019 at 5:33 PM David Arnold <dar@xoe.solutions> wrote:Now, for the first time in a row... :DOn Fri, Nov 15, 2019 at 5:06 PM Jordi Riera <jordi.riera@numigi.com> wrote:Hello David,Did you have the time to move forward with the awesome repo/list ?Best,JordiLe jeu. 31 oct. 2019 à 10:37, David Arnold <dar@xoe.solutions> a écrit :True, Russell has put together some compelling user stories. I plan to process them somehow to that end.El jue., 31 oct. 2019, 7:47 a.m., Jordi Riera <jordi.riera@numigi.com> escribió:Great,And we can create traffic to the ODEPs through the awesome-list.We need to find the good catch phrases to inspire people to contribute on doc.Thank you David,JordiLe jeu. 31 oct. 2019 à 00:27, David Arnold <dar@xoe.solutions> a écrit :Ok. I like, lots of communities do those awesome-x listing ;-)A good mix catering to different levels of abstraction should gain enough traction over time, you're right, we need to create practical value, too.But I think, especially for the more involved people to let loose of their deer siloes, the foundation's need to be talked true with time and effort (hence ODEPs).Only through excellent community governance will we have a chance to eventually agree.This week, I intent to create that awesome-deployment-odoo-repo.BR,David A.El mié., 30 oct. 2019, 3:12 p.m., Jordi Riera <jordi.riera@numigi.com> escribió:Hello everyone,sorry for my silence in the previous days. Busy days as we all know.I think we should start small to grow slowly but surely.I like your enthusiasm, David, and feel free to lead the effort on the subject. While ODEPs seem great, I have the feeling that might scare a lot of contributors due to the mass of reading to do.In parallel to it, I would like to see something more practical, like an awesome-odoo-deploy, where we would see a list of all the tool to deploy odoo.I see that you have already a good list with:* doodba* odoo cloud platform...What do you think?OdooOps seems a good place to start. Could you create a new repo for the listing?Cheers,JordiLe mer. 30 oct. 2019 à 12:27, David Arnold <dar@xoe.solutions> a écrit :Yeah, OCA might probably endorse it later on when OCA wishes to. Absolutely!From a constituency point of view, OCA does not seem to be able to add shared legitimacy. This needs to be provided by the involved actors themselves.Namely, to my knowledge, those are:- Tecnativa (doodba)- Camptocamp (Odoo cloud platform, and other tooling, anthem, marabunta)- Acsone (odoo-bedrock, click-odoo, Bob templates, and other tooling)- Akretion (docky and other tooling)- XOE ( DockeryOdoo & OdooOperator and a couple of forks / mix&match from Acsone and Camptocamp)Can we pass the point where PRoC > PRoSP (Perceived Return on Collaboration > Persived Return on Siloed Project) for those actors?El mié., 30 oct. 2019, 1:27 a.m., Russell Briggs <russ@paraflyer.net> escribió:Great stuff David!Yeah it feels like this should eventually become an OCA project once it gets some traction, since it is potentially quite a fundamental community component?I will have a read and make some comments in a bit :)RussOn Wed, 30 Oct 2019, 9:57 AM David Arnold, <dar@xoe.solutions> wrote:By the way I commit by all means NOT to retain unique ownership on the OdooOps GitHub organization. Any meritable community, abiding by the self constituing decision making processes (e.g. ODEPs) is eligible to share the burdon. ;-)El mar., 29 oct. 2019, 3:50 p.m., David Arnold <dar@xoe.solutions> escribió:Hi all,I redacted a first ODEP 0002 in Order to propose the constituency of a docker base runtime repository.I stepped over some steps and wrote down everything I had in mind.For legitimacy building, please comment on the PR and indicate your level of approval:Approve: Section 1, Section 2, etc.Disaprove: Section 4Ideally we would get unanimous approval of the "Motivation" section, so this section could be merged quickly.According to the eminent approval levels I'll outfactor parts into separate PRs / Discussions.Please leave your opinion / approval level, even if you are only a user and no active committer of the Odoo docker community.BR,David A.El dom., 27 oct. 2019, 11:36 p.m., David Arnold <dar@xoe.solutions> escribió:I plan to eventually write up some "ODEPs" ( like python PEPs ) " Odoo Dev Enhancement Proposal " where I want to lay out the reasoning behind some design decisions I made in DockeryOdoo over the past few years.However, I have a problem: if there is no second owner of such proposals and if there is no legitimate approval process of any sort, it's going to be yet another tribal silo.So I hope by writing up some "ODEPs", the discussion might get a chance to become structured, hence contribution might get a chance to become structured, hence consolidation and mind share might become a chance to get structured. Hence a legitimate constituency for this topic (outside of OCA path dependent reasoning) will be possible.People might think "what an overkill", but ultimately, we all know, that pulling tribes together around a common goal is not only a challenging task since open source communities exist.Maybe the best approach is formulating understandable, complete and concise proposals in human readable form (the vision behind "ODEPs").My 2 cents.El dom., 27 oct. 2019, 10:07 a.m., Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:The interest will grow if the few involve here make it work...El dom., 27 de octubre de 2019 08:16, <admin@ygol.com> escribió:What is the next step for this to move on?- Should we put to vote Maxime's idea to create those 2 repositories? Where would they live?- Or is it better to keep the discussion outside of OCA? David Arnold prepared a place (odooOps)?It would be nice to know who is interested by this topic.tnx--Yves Goldberg------- Original message -----From: Maxime Chambreuil <mchambreuil@opensourceintegrators.com>To: Contributors <contributors@odoo-community.org>Subject: Re: Place to share knowledge/tools on deploymentDate: Tuesday, October 22, 2019 19:52Hi Jordi,I think we could start with:- one repository to store a base/minimal docker image + documented extensions.
- one repository per orchestrator (or 1 for all) where we can share configuration with documentation of how to orchestrate the previous Docker images
My 2 cents.On Tue, Oct 22, 2019 at 11:22 AM Jordi Riera <jordi.riera@numigi.com> wrote:Hello list,During the OCA code sprint in belgium, I had the opportunity to talk again about docker. While the first talk, in 2018, was focused on usage of Docker. This year, the discussion focused on orchestration solutions.The discussion was interesting and it was found that we could use a place to share good practices and solutions. Regarding orchestration, but also on dockers (odoo and other services like postgres, acsone/kwkhtmltopdf) and around deployments helpers (git-aggregator, gitoo, clik-odoo, etc.)How would you see it ?What do you think about to start with a single place where we could have docker-compose templates (or link to repo with templates) and best practices, FAQs, etc (I was thinking questions like: https://odoo-community.org/groups/contributors-15/contributors-148040?mode=thread&date_begin=&date_end=)The aim would be to ease the adoption of docker based infrastructure over OCA members. Docker-compose is a good tool to ease docker adoption.Let me know what you thinkJordi--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: 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
_______________________________________________
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
--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________
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
--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________
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
--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________
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
by dar - 11:45 - 19 Nov 2019 - one repository to store a base/minimal docker image + documented extensions.
-
Re: "Adopt a Module" campaign?
Make an orphan-modules-list? like awesome lists, but exposing gruesome reality?On Tue, Nov 19, 2019 at 10:02 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote: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,-sbiOn 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: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 politelyTecnnically,- 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 volunteerHow to perform that?> 2) add a lint to ensure when module is added, it has a declared maintainerAre 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
_______________________________________________
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
by dar - 07:01 - 19 Nov 2019 -
Re: "Adopt a Module" campaign?
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,-sbiOn 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: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 politelyTecnnically,- 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 volunteerHow to perform that?> 2) add a lint to ensure when module is added, it has a declared maintainerAre 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
_______________________________________________
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
by Stéphane Bidoul - 04:01 - 19 Nov 2019 -
Re: "Adopt a Module" campaign?
Great initiative!👍MAXIME CHAMBREUIL
PROJECT MANAGER/CONSULTANTO: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.comP.O. BOX 940, HIGLEY, AZ 85236 
On Tue, Nov 19, 2019 at 3: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: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 politelyTecnnically,- 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 volunteerHow to perform that?> 2) add a lint to ensure when module is added, it has a declared maintainerAre 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
_______________________________________________
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
by Maxime Chambreuil - 03:30 - 19 Nov 2019 -
Re: Propose Jaime Arroyo as PSC of HR
+1El mar., 19 nov. 2019 a las 11:57, Alex Comba (<alex.comba@agilebg.com>) escribió:+1On Tue, Nov 19, 2019 at 9:31 AM Enric Tobella <etobella@creublanca.es> wrote:Hi all,Jaime has participated with a lot of contributions at hr repository: https://github.com/OCA/hr/pulls/jarroyomoralesHe has done migrations from 10 to 11 and 11 to 12, new addons and fixing issues.RegardsEnric Tobella AlomarCentros Médicos Creu BlancaTel: 902 202 230Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Alex Comba
Tel (CH): +41 91 210 23 40_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Héctor Villarreal OrtegaProduct Analyst | Eficent(+34) 666468605 | hector.villarreal@eficent.com | https://www.eficent.comTwitter: https://twitter.com/hveficent_erp | Linkedin: https://www.linkedin.com/in/hectorvior
by Héctor Villarreal Ortega - 12:01 - 19 Nov 2019 -
Re: Propose Jaime Arroyo as PSC of HR
+1On Tue, Nov 19, 2019 at 9:31 AM Enric Tobella <etobella@creublanca.es> wrote:Hi all,Jaime has participated with a lot of contributions at hr repository: https://github.com/OCA/hr/pulls/jarroyomoralesHe has done migrations from 10 to 11 and 11 to 12, new addons and fixing issues.RegardsEnric Tobella AlomarCentros Médicos Creu BlancaTel: 902 202 230Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Alex Comba
Tel (CH): +41 91 210 23 40
by Alex Comba. - 11:56 - 19 Nov 2019 -
Re: "Adopt a Module" campaign?
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 politelyTecnnically,- 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 volunteerHow to perform that?> 2) add a lint to ensure when module is added, it has a declared maintainerAre 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
by Sylvain LE GAL - 10:26 - 19 Nov 2019 -
Re: "Adopt a Module" campaign?
Le mar. 19 nov. 2019 à 09:56, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Sylvain, not sure that list is the most suitable one, because, which serious integrator is really downloading modules through OCA website instead of using git, pip or other deployment methods? But yes, we can focus on a criteria like that.Indeed ! I think that most integrators are not using odoo / OCA apps store. (they pip install, gitagregate, or whatever).But, the list I mention enumerates the "popular" modules of the OCA, and I think it's a good indicator of which modules should be maintained. In fact, the first page is listing : web_responsive, web_export_view, mis_builder, etc... that are the "must have" modules of the OCA in my opnion.If OCA receives donations from companies, it is because such modules exist, among other reasons.But it's just a suggestion. If other members find a better metrics, no problem !
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 Sylvain LE GAL - 10:20 - 19 Nov 2019 -
Re: "Adopt a Module" campaign?
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 politelyAre 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 volunteerHow to perform that?> 2) add a lint to ensure when module is added, it has a declared maintainerAre 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
by Pedro M. Baeza - 10:16 - 19 Nov 2019 -
Re: "Adopt a Module" campaign?
> 1) “noone”’s modules should be adopted either by their original author(s) or by volunteerHow to perform that?> 2) add a lint to ensure when module is added, it has a declared maintainerAre you suggesting Travis to fail if no maintainer is declared?Regards.
by Pedro M. Baeza - 10:00 - 19 Nov 2019 -
Re: "Adopt a Module" campaign?
Sylvain, not sure that list is the most suitable one, because, which serious integrator is really downloading modules through OCA website instead of using git, pip or other deployment methods? But yes, we can focus on a criteria like that.Regards.
by Pedro M. Baeza - 09:55 - 19 Nov 2019 -
Re: "Adopt a Module" campaign?
Hi Alexey,I find the idea quite funny. (And interesting for the OCA to have more maintainers).If community agree with such an idea, I think that we should first target the most used modules, (if they don't havemaintainers already).Candidate list : https://www.odoo.com/apps/modules/browse?author=Odoo+Community+Association+%28OCA%29&order=DownloadsLe mar. 19 nov. 2019 à 09:47, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Please detail a bit more what are the steps of that campaign.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 Sylvain LE GAL - 09:51 - 19 Nov 2019