Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
-
Call for reviewers: account_bank_statement_import_online
Dear all,There’s a base module that would allow building online importers of statements from bank accounts. Base does not contain any implementation, as there’s no good enough candidate, but I plan to finish integration of TransferWise support, Holvi, LHV Bank (Estonia) and probably will consider PayPal. Yet base remains important milestone to be merged.Kind regards,Alexey
by Alexey Pelykh <alexey.pelykh@gmail.com> - 09:55 - 1 Sep 2019 -
Re: Issue with allowed_user_ids ?
With the help from community, it was found. It’s from project_hr module, it alters declaration on user_id field. And Pedro Baeza needs to take a look at that part of project_hr module as it’s his. I think that part should be changed a bit to introduce constraint on user_id field and alter domain in XML, not in code.On Aug 31, 2019, at 14:57, Lorenzo Battistini <elbaddy@gmail.com> wrote:Do you know where allowed_user_ids is defined and used?On Fri, 30 Aug 2019 at 16:11, Alexey Pelykh <alexey.pelykh@gmail.com> wrote:Dear community,Sorry for bothering via email, but I’ve encountered a very odd issue that goes beyond my area of knowledge. Please see https://github.com/OCA/project/pull/570It fails on OCA Travis, but works on our Travis, and fails with oddest issue ever:Field 'allowed_user_ids' used in attributes must be present in view but is missing: - 'allowed_user_ids' in domain="[('id', 'in', allowed_user_ids)]"I’ve tried:<field name="allowed_user_ids" invisible="1"/>adding this fixed OCA Travis, but breaks Runbot and our Travis. Not having that line (which seems really correct to me) is perfectly fine for Runbot and our Travis, but breaks OCA Travis. Any ideas?Alexey_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Lorenzo Battistini
https://github.com/eLBati_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Alexey Pelykh <alexey.pelykh@gmail.com> - 03:16 - 31 Aug 2019 -
Re: Issue with allowed_user_ids ?
Do you know where allowed_user_ids is defined and used?On Fri, 30 Aug 2019 at 16:11, Alexey Pelykh <alexey.pelykh@gmail.com> wrote:Dear community,Sorry for bothering via email, but I’ve encountered a very odd issue that goes beyond my area of knowledge. Please see https://github.com/OCA/project/pull/570It fails on OCA Travis, but works on our Travis, and fails with oddest issue ever:Field 'allowed_user_ids' used in attributes must be present in view but is missing: - 'allowed_user_ids' in domain="[('id', 'in', allowed_user_ids)]"I’ve tried:<field name="allowed_user_ids" invisible="1"/>adding this fixed OCA Travis, but breaks Runbot and our Travis. Not having that line (which seems really correct to me) is perfectly fine for Runbot and our Travis, but breaks OCA Travis. Any ideas?Alexey_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Lorenzo Battistini
https://github.com/eLBati
by Lorenzo Battistini. - 02:56 - 31 Aug 2019 -
Issue with allowed_user_ids ?
Dear community,Sorry for bothering via email, but I’ve encountered a very odd issue that goes beyond my area of knowledge. Please see https://github.com/OCA/project/pull/570It fails on OCA Travis, but works on our Travis, and fails with oddest issue ever:Field 'allowed_user_ids' used in attributes must be present in view but is missing: - 'allowed_user_ids' in domain="[('id', 'in', allowed_user_ids)]"I’ve tried:<field name="allowed_user_ids" invisible="1"/>adding this fixed OCA Travis, but breaks Runbot and our Travis. Not having that line (which seems really correct to me) is perfectly fine for Runbot and our Travis, but breaks OCA Travis. Any ideas?Alexey
by Alexey Pelykh <alexey.pelykh@gmail.com> - 04:10 - 30 Aug 2019 -
Re: Stale PR closing
I'm in favor to move forward with this.Alexey was kind enough to do a PR, which includes adding a "stale 🗃" label so they are easy to find.Note PR merged by /ocabot merge (virtually all of them these days) are labeled as "merged 🎉" so they too are easy to find even in case a rebase has been done.12 months is a reasonably long time. And if anyone is still interested it's easy to (ask to) reopen to get a new one year lease.@Graeme Gellatly does this address your concerns?-sbiOn Thu, Aug 29, 2019 at 6:27 PM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:We can implement just-labeling initially, at least to see the amount of impact. Personally, I don’t see any harm in closing PR that had 0 comments for 12 months, assuming it’s valuable and reviewers are doing their part of the deal.
On Aug 29, 2019, at 18:17, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:For your case @Graeme Gellatly may be we can just add a label "Close by bot" so it's still pretty easy to find them right ?Because today, the fact so many PRs remain open for months if not years is a real issue I think.Any how, we all agree there is something to do here. The OCA days is probably the best place to discuss it right ;)On Thu, Aug 29, 2019 at 2:36 PM Daniel Reis <dgreis@sapo.pt> wrote:If we do this, we need to make sure that closed PR really means that the PR was not merged.I see on the Odoo repo may closed PRs that had their code manually merged - not sure if we have this in the OCA.What if the bot just regularly (monthly?) pinged the followers.People would manually close a stale PR if that makes sense.DanielOr once it hit 12 months of inactivity, ocabot can auto assign to any active contributors (i..e, 2 person) to review it?After that like 3 months, if still no activity, close it.On Thu, Aug 29, 2019 at 4:17 PM Eduardo Magdalena <emagdalena@c2i.es> wrote:+1 12 months - 18 months. First add a comment or label as a warning, telling that the PR will be closed an the closed if there are no activity 6 months afterUn saludo,
Eduardo Magdalena
Fundador & CEO
✆ +34 678 713 373

C2i Change 2 improve
Optimización de procesos
Averigua a quién conocemos en común

Este correo y sus archivos asociados son privados y confidenciales y van dirigidos exclusivamente a su destinatario. Si recibe este correo sin ser el destinatario del mismo le rogamos proceda a su eliminación y lo ponga en conocimiento de su emisor. La difusión por cualquier medio de su contenido podría ser sancionada conforme a lo previsto en la legislación vigente, Ley Orgánica 15/1999, de Protección de Datos de Carácter Personal. Le rogamos que no imprima este correo ni sus documentos adjuntos, salvo que lo estime necesario. El jue., 29 ago. 2019 a las 3:32, Graeme Gellatly (<gdgellatly@gmail.com>) escribió:Hi,I don't like the idea personally, especially on OCA wide level. I often pick up abandoned PR's fix them up and resubmit them. At the very least I like to go through them when porting modules to see if anything in there is value that needs porting. If they are closed it is a hassle working out why it was closed (superseded, abandoned etc).Maybe for new to OCA modules, but for existing modules, a human should really determine whether it is worth reviving IMO. I think a much better application for a Bot is to find interested reviewers. Do some smart stuff likeWhen a PR is submitted, crawl history and cc any past reviewer or committer for that module (maybe even have a reviewer group so people can choose to opt in) (maybe in past 18 months)On Thu, Aug 29, 2019 at 10:41 AM Rafael Blasco <rafael.blasco@tecnativa.com> wrote:+1 18 months
De: Mignon, Laurent [mailto:laurent.mignon@acsone.eu]
Enviado el: martes, 27 de agosto de 2019 10:57
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Stale PR closing+1
On Tue, Aug 27, 2019 at 10:27 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hello Alexey,
+1
This is being tracked in: https://github.com/OCA/oca-github-bot/issues/10, awaiting PR :)
If someone wants to work on this at #OCADays, I'll be happy to help.
-sbi
On Tue, Aug 27, 2019 at 10:16 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear community,
In OCA repositories there are PRs that have not been updated for years, and are either abandoned by authors or by reviewers. Should we agree on policy (and implement it via OCA Bot) to close PR/issue if there was no activity for more than 6-12-18 months?
Kind regards,
Alexey
_______________________________________________
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
--camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDepartment HeadBusiness Solutions_______________________________________________
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 - 07:16 - 29 Aug 2019 -
Re: Stale PR closing
We can implement just-labeling initially, at least to see the amount of impact. Personally, I don’t see any harm in closing PR that had 0 comments for 12 months, assuming it’s valuable and reviewers are doing their part of the deal.
On Aug 29, 2019, at 18:17, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:For your case @Graeme Gellatly may be we can just add a label "Close by bot" so it's still pretty easy to find them right ?Because today, the fact so many PRs remain open for months if not years is a real issue I think.Any how, we all agree there is something to do here. The OCA days is probably the best place to discuss it right ;)On Thu, Aug 29, 2019 at 2:36 PM Daniel Reis <dgreis@sapo.pt> wrote:If we do this, we need to make sure that closed PR really means that the PR was not merged.I see on the Odoo repo may closed PRs that had their code manually merged - not sure if we have this in the OCA.What if the bot just regularly (monthly?) pinged the followers.People would manually close a stale PR if that makes sense.DanielOr once it hit 12 months of inactivity, ocabot can auto assign to any active contributors (i..e, 2 person) to review it?After that like 3 months, if still no activity, close it.On Thu, Aug 29, 2019 at 4:17 PM Eduardo Magdalena <emagdalena@c2i.es> wrote:+1 12 months - 18 months. First add a comment or label as a warning, telling that the PR will be closed an the closed if there are no activity 6 months afterUn saludo,
Eduardo Magdalena
Fundador & CEO
✆ +34 678 713 373

C2i Change 2 improve
Optimización de procesos
Averigua a quién conocemos en común

Este correo y sus archivos asociados son privados y confidenciales y van dirigidos exclusivamente a su destinatario. Si recibe este correo sin ser el destinatario del mismo le rogamos proceda a su eliminación y lo ponga en conocimiento de su emisor. La difusión por cualquier medio de su contenido podría ser sancionada conforme a lo previsto en la legislación vigente, Ley Orgánica 15/1999, de Protección de Datos de Carácter Personal. Le rogamos que no imprima este correo ni sus documentos adjuntos, salvo que lo estime necesario. El jue., 29 ago. 2019 a las 3:32, Graeme Gellatly (<gdgellatly@gmail.com>) escribió:Hi,I don't like the idea personally, especially on OCA wide level. I often pick up abandoned PR's fix them up and resubmit them. At the very least I like to go through them when porting modules to see if anything in there is value that needs porting. If they are closed it is a hassle working out why it was closed (superseded, abandoned etc).Maybe for new to OCA modules, but for existing modules, a human should really determine whether it is worth reviving IMO. I think a much better application for a Bot is to find interested reviewers. Do some smart stuff likeWhen a PR is submitted, crawl history and cc any past reviewer or committer for that module (maybe even have a reviewer group so people can choose to opt in) (maybe in past 18 months)On Thu, Aug 29, 2019 at 10:41 AM Rafael Blasco <rafael.blasco@tecnativa.com> wrote:+1 18 months
De: Mignon, Laurent [mailto:laurent.mignon@acsone.eu]
Enviado el: martes, 27 de agosto de 2019 10:57
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Stale PR closing+1
On Tue, Aug 27, 2019 at 10:27 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hello Alexey,
+1
This is being tracked in: https://github.com/OCA/oca-github-bot/issues/10, awaiting PR :)
If someone wants to work on this at #OCADays, I'll be happy to help.
-sbi
On Tue, Aug 27, 2019 at 10:16 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear community,
In OCA repositories there are PRs that have not been updated for years, and are either abandoned by authors or by reviewers. Should we agree on policy (and implement it via OCA Bot) to close PR/issue if there was no activity for more than 6-12-18 months?
Kind regards,
Alexey
_______________________________________________
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
--camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDepartment HeadBusiness Solutions_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Alexey Pelykh <alexey.pelykh@gmail.com> - 06:26 - 29 Aug 2019 -
Re: Stale PR closing
For your case @Graeme Gellatly may be we can just add a label "Close by bot" so it's still pretty easy to find them right ?Because today, the fact so many PRs remain open for months if not years is a real issue I think.Any how, we all agree there is something to do here. The OCA days is probably the best place to discuss it right ;)On Thu, Aug 29, 2019 at 2:36 PM Daniel Reis <dgreis@sapo.pt> wrote:If we do this, we need to make sure that closed PR really means that the PR was not merged.I see on the Odoo repo may closed PRs that had their code manually merged - not sure if we have this in the OCA.What if the bot just regularly (monthly?) pinged the followers.People would manually close a stale PR if that makes sense.DanielOr once it hit 12 months of inactivity, ocabot can auto assign to any active contributors (i..e, 2 person) to review it?After that like 3 months, if still no activity, close it.On Thu, Aug 29, 2019 at 4:17 PM Eduardo Magdalena <emagdalena@c2i.es> wrote:+1 12 months - 18 months. First add a comment or label as a warning, telling that the PR will be closed an the closed if there are no activity 6 months afterUn saludo,
Eduardo Magdalena
Fundador & CEO
✆ +34 678 713 373

C2i Change 2 improve
Optimización de procesos
Averigua a quién conocemos en común

Este correo y sus archivos asociados son privados y confidenciales y van dirigidos exclusivamente a su destinatario. Si recibe este correo sin ser el destinatario del mismo le rogamos proceda a su eliminación y lo ponga en conocimiento de su emisor. La difusión por cualquier medio de su contenido podría ser sancionada conforme a lo previsto en la legislación vigente, Ley Orgánica 15/1999, de Protección de Datos de Carácter Personal. Le rogamos que no imprima este correo ni sus documentos adjuntos, salvo que lo estime necesario. El jue., 29 ago. 2019 a las 3:32, Graeme Gellatly (<gdgellatly@gmail.com>) escribió:Hi,I don't like the idea personally, especially on OCA wide level. I often pick up abandoned PR's fix them up and resubmit them. At the very least I like to go through them when porting modules to see if anything in there is value that needs porting. If they are closed it is a hassle working out why it was closed (superseded, abandoned etc).Maybe for new to OCA modules, but for existing modules, a human should really determine whether it is worth reviving IMO. I think a much better application for a Bot is to find interested reviewers. Do some smart stuff likeWhen a PR is submitted, crawl history and cc any past reviewer or committer for that module (maybe even have a reviewer group so people can choose to opt in) (maybe in past 18 months)On Thu, Aug 29, 2019 at 10:41 AM Rafael Blasco <rafael.blasco@tecnativa.com> wrote:+1 18 months
De: Mignon, Laurent [mailto:laurent.mignon@acsone.eu]
Enviado el: martes, 27 de agosto de 2019 10:57
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Stale PR closing+1
On Tue, Aug 27, 2019 at 10:27 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hello Alexey,
+1
This is being tracked in: https://github.com/OCA/oca-github-bot/issues/10, awaiting PR :)
If someone wants to work on this at #OCADays, I'll be happy to help.
-sbi
On Tue, Aug 27, 2019 at 10:16 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear community,
In OCA repositories there are PRs that have not been updated for years, and are either abandoned by authors or by reviewers. Should we agree on policy (and implement it via OCA Bot) to close PR/issue if there was no activity for more than 6-12-18 months?
Kind regards,
Alexey
_______________________________________________
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
--camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDepartment HeadBusiness Solutions
by Joël Grand Guillaume - 06:16 - 29 Aug 2019 -
Re: Stale PR closing
If we do this, we need to make sure that closed PR really means that the PR was not merged.I see on the Odoo repo may closed PRs that had their code manually merged - not sure if we have this in the OCA.What if the bot just regularly (monthly?) pinged the followers.People would manually close a stale PR if that makes sense.DanielOr once it hit 12 months of inactivity, ocabot can auto assign to any active contributors (i..e, 2 person) to review it?After that like 3 months, if still no activity, close it.On Thu, Aug 29, 2019 at 4:17 PM Eduardo Magdalena <emagdalena@c2i.es> wrote:+1 12 months - 18 months. First add a comment or label as a warning, telling that the PR will be closed an the closed if there are no activity 6 months afterUn saludo,
Eduardo Magdalena
Fundador & CEO
✆ +34 678 713 373

C2i Change 2 improve
Optimización de procesos
Averigua a quién conocemos en común

Este correo y sus archivos asociados son privados y confidenciales y van dirigidos exclusivamente a su destinatario. Si recibe este correo sin ser el destinatario del mismo le rogamos proceda a su eliminación y lo ponga en conocimiento de su emisor. La difusión por cualquier medio de su contenido podría ser sancionada conforme a lo previsto en la legislación vigente, Ley Orgánica 15/1999, de Protección de Datos de Carácter Personal. Le rogamos que no imprima este correo ni sus documentos adjuntos, salvo que lo estime necesario. El jue., 29 ago. 2019 a las 3:32, Graeme Gellatly (<gdgellatly@gmail.com>) escribió:Hi,I don't like the idea personally, especially on OCA wide level. I often pick up abandoned PR's fix them up and resubmit them. At the very least I like to go through them when porting modules to see if anything in there is value that needs porting. If they are closed it is a hassle working out why it was closed (superseded, abandoned etc).Maybe for new to OCA modules, but for existing modules, a human should really determine whether it is worth reviving IMO. I think a much better application for a Bot is to find interested reviewers. Do some smart stuff likeWhen a PR is submitted, crawl history and cc any past reviewer or committer for that module (maybe even have a reviewer group so people can choose to opt in) (maybe in past 18 months)On Thu, Aug 29, 2019 at 10:41 AM Rafael Blasco <rafael.blasco@tecnativa.com> wrote:+1 18 months
De: Mignon, Laurent [mailto:laurent.mignon@acsone.eu]
Enviado el: martes, 27 de agosto de 2019 10:57
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Stale PR closing+1
On Tue, Aug 27, 2019 at 10:27 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hello Alexey,
+1
This is being tracked in: https://github.com/OCA/oca-github-bot/issues/10, awaiting PR :)
If someone wants to work on this at #OCADays, I'll be happy to help.
-sbi
On Tue, Aug 27, 2019 at 10:16 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear community,
In OCA repositories there are PRs that have not been updated for years, and are either abandoned by authors or by reviewers. Should we agree on policy (and implement it via OCA Bot) to close PR/issue if there was no activity for more than 6-12-18 months?
Kind regards,
Alexey
_______________________________________________
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 Daniel Reis - 02:35 - 29 Aug 2019 -
Re: Stale PR closing
Or once it hit 12 months of inactivity, ocabot can auto assign to any active contributors (i..e, 2 person) to review it?After that like 3 months, if still no activity, close it.On Thu, Aug 29, 2019 at 4:17 PM Eduardo Magdalena <emagdalena@c2i.es> wrote:+1 12 months - 18 months. First add a comment or label as a warning, telling that the PR will be closed an the closed if there are no activity 6 months afterUn saludo,
Eduardo Magdalena
Fundador & CEO
✆ +34 678 713 373

C2i Change 2 improve
Optimización de procesos
Averigua a quién conocemos en común

Este correo y sus archivos asociados son privados y confidenciales y van dirigidos exclusivamente a su destinatario. Si recibe este correo sin ser el destinatario del mismo le rogamos proceda a su eliminación y lo ponga en conocimiento de su emisor. La difusión por cualquier medio de su contenido podría ser sancionada conforme a lo previsto en la legislación vigente, Ley Orgánica 15/1999, de Protección de Datos de Carácter Personal. Le rogamos que no imprima este correo ni sus documentos adjuntos, salvo que lo estime necesario. El jue., 29 ago. 2019 a las 3:32, Graeme Gellatly (<gdgellatly@gmail.com>) escribió:Hi,I don't like the idea personally, especially on OCA wide level. I often pick up abandoned PR's fix them up and resubmit them. At the very least I like to go through them when porting modules to see if anything in there is value that needs porting. If they are closed it is a hassle working out why it was closed (superseded, abandoned etc).Maybe for new to OCA modules, but for existing modules, a human should really determine whether it is worth reviving IMO. I think a much better application for a Bot is to find interested reviewers. Do some smart stuff likeWhen a PR is submitted, crawl history and cc any past reviewer or committer for that module (maybe even have a reviewer group so people can choose to opt in) (maybe in past 18 months)On Thu, Aug 29, 2019 at 10:41 AM Rafael Blasco <rafael.blasco@tecnativa.com> wrote:+1 18 months
De: Mignon, Laurent [mailto:laurent.mignon@acsone.eu]
Enviado el: martes, 27 de agosto de 2019 10:57
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Stale PR closing+1
On Tue, Aug 27, 2019 at 10:27 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hello Alexey,
+1
This is being tracked in: https://github.com/OCA/oca-github-bot/issues/10, awaiting PR :)
If someone wants to work on this at #OCADays, I'll be happy to help.
-sbi
On Tue, Aug 27, 2019 at 10:16 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear community,
In OCA repositories there are PRs that have not been updated for years, and are either abandoned by authors or by reviewers. Should we agree on policy (and implement it via OCA Bot) to close PR/issue if there was no activity for more than 6-12-18 months?
Kind regards,
Alexey
_______________________________________________
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 Kitti Upariphutthiphong - 01:10 - 29 Aug 2019 -
Re: Stale PR closing
+1 12 months - 18 months. First add a comment or label as a warning, telling that the PR will be closed an the closed if there are no activity 6 months afterUn saludo,
Eduardo Magdalena
Fundador & CEO
✆ +34 678 713 373

C2i Change 2 improve
Optimización de procesos
Averigua a quién conocemos en común

Este correo y sus archivos asociados son privados y confidenciales y van dirigidos exclusivamente a su destinatario. Si recibe este correo sin ser el destinatario del mismo le rogamos proceda a su eliminación y lo ponga en conocimiento de su emisor. La difusión por cualquier medio de su contenido podría ser sancionada conforme a lo previsto en la legislación vigente, Ley Orgánica 15/1999, de Protección de Datos de Carácter Personal. Le rogamos que no imprima este correo ni sus documentos adjuntos, salvo que lo estime necesario. El jue., 29 ago. 2019 a las 3:32, Graeme Gellatly (<gdgellatly@gmail.com>) escribió:Hi,I don't like the idea personally, especially on OCA wide level. I often pick up abandoned PR's fix them up and resubmit them. At the very least I like to go through them when porting modules to see if anything in there is value that needs porting. If they are closed it is a hassle working out why it was closed (superseded, abandoned etc).Maybe for new to OCA modules, but for existing modules, a human should really determine whether it is worth reviving IMO. I think a much better application for a Bot is to find interested reviewers. Do some smart stuff likeWhen a PR is submitted, crawl history and cc any past reviewer or committer for that module (maybe even have a reviewer group so people can choose to opt in) (maybe in past 18 months)On Thu, Aug 29, 2019 at 10:41 AM Rafael Blasco <rafael.blasco@tecnativa.com> wrote:+1 18 months
De: Mignon, Laurent [mailto:laurent.mignon@acsone.eu]
Enviado el: martes, 27 de agosto de 2019 10:57
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Stale PR closing+1
On Tue, Aug 27, 2019 at 10:27 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hello Alexey,
+1
This is being tracked in: https://github.com/OCA/oca-github-bot/issues/10, awaiting PR :)
If someone wants to work on this at #OCADays, I'll be happy to help.
-sbi
On Tue, Aug 27, 2019 at 10:16 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear community,
In OCA repositories there are PRs that have not been updated for years, and are either abandoned by authors or by reviewers. Should we agree on policy (and implement it via OCA Bot) to close PR/issue if there was no activity for more than 6-12-18 months?
Kind regards,
Alexey
_______________________________________________
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 Eduardo Magdalena - 11:16 - 29 Aug 2019 -
Re: Stale PR closing
Hi,I don't like the idea personally, especially on OCA wide level. I often pick up abandoned PR's fix them up and resubmit them. At the very least I like to go through them when porting modules to see if anything in there is value that needs porting. If they are closed it is a hassle working out why it was closed (superseded, abandoned etc).Maybe for new to OCA modules, but for existing modules, a human should really determine whether it is worth reviving IMO. I think a much better application for a Bot is to find interested reviewers. Do some smart stuff likeWhen a PR is submitted, crawl history and cc any past reviewer or committer for that module (maybe even have a reviewer group so people can choose to opt in) (maybe in past 18 months)On Thu, Aug 29, 2019 at 10:41 AM Rafael Blasco <rafael.blasco@tecnativa.com> wrote:+1 18 months
De: Mignon, Laurent [mailto:laurent.mignon@acsone.eu]
Enviado el: martes, 27 de agosto de 2019 10:57
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Stale PR closing+1
On Tue, Aug 27, 2019 at 10:27 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hello Alexey,
+1
This is being tracked in: https://github.com/OCA/oca-github-bot/issues/10, awaiting PR :)
If someone wants to work on this at #OCADays, I'll be happy to help.
-sbi
On Tue, Aug 27, 2019 at 10:16 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear community,
In OCA repositories there are PRs that have not been updated for years, and are either abandoned by authors or by reviewers. Should we agree on policy (and implement it via OCA Bot) to close PR/issue if there was no activity for more than 6-12-18 months?
Kind regards,
Alexey
_______________________________________________
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 Graeme Gellatly - 03:31 - 29 Aug 2019 -
RE: Stale PR closing
+1 18 months
De: Mignon, Laurent [mailto:laurent.mignon@acsone.eu]
Enviado el: martes, 27 de agosto de 2019 10:57
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Stale PR closing+1
On Tue, Aug 27, 2019 at 10:27 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hello Alexey,
+1
This is being tracked in: https://github.com/OCA/oca-github-bot/issues/10, awaiting PR :)
If someone wants to work on this at #OCADays, I'll be happy to help.
-sbi
On Tue, Aug 27, 2019 at 10:16 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
Dear community,
In OCA repositories there are PRs that have not been updated for years, and are either abandoned by authors or by reviewers. Should we agree on policy (and implement it via OCA Bot) to close PR/issue if there was no activity for more than 6-12-18 months?
Kind regards,
Alexey
_______________________________________________
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 Rafael Blasco (Moduon) - 12:41 - 29 Aug 2019 -
Payment gateway
Dear all ,Hope you are wellI was wondering if someone use any payment gateway integration before with odoo in website or with sandbox direct !Can anyone help with this?Thank you.
by Esla Amer - 10:55 - 28 Aug 2019 -
Re: Re: Proposing Simone Orsi for Connectors PSC
Thanks!On Wed, Aug 28, 2019 at 8:46 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:I just added Simone to the team.-sbiOn Wed, Aug 28, 2019 at 7:37 AM Guewen Baconnier <guewen.baconnier@camptocamp.com> wrote:YesOn Tue, Aug 27, 2019 at 7:26 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:On Tue, Aug 27, 2019 at 7:01 PM Andrea Cometa - Apulia Software Srl <a.cometa@apuliasoftware.it> wrote:I'm not sure either, Joël...kidding+1 for SimoneInviato da BlueMailIl giorno 27 ago 2019, alle ore 18:32, "Joël Grand-Guillaume" <joel.grandguillaume@camptocamp.com> ha scritto:I am not sure about Simone.. He's not really reliable right?!Of course +1Le mar. 27 août 2019 à 13:46, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :+1 for Simone
Bruno Joliveau - Architecte applications - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, CanadaLe mar. 27 août 2019 à 03:26, Guewen Baconnier <guewen.baconnier@camptocamp.com> a écrit :Hi,Simone is a regular and engaged contributor of the connector and its subsidiary repositories (connector-interfaces, ...). I'd like to sponsor him as member of the PSC.--_______________________________________________
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 Guewen Baconnier - 08:56 - 28 Aug 2019 -
Re: Re: Proposing Simone Orsi for Connectors PSC
I just added Simone to the team.-sbiOn Wed, Aug 28, 2019 at 7:37 AM Guewen Baconnier <guewen.baconnier@camptocamp.com> wrote:YesOn Tue, Aug 27, 2019 at 7:26 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:On Tue, Aug 27, 2019 at 7:01 PM Andrea Cometa - Apulia Software Srl <a.cometa@apuliasoftware.it> wrote:I'm not sure either, Joël...kidding+1 for SimoneInviato da BlueMailIl giorno 27 ago 2019, alle ore 18:32, "Joël Grand-Guillaume" <joel.grandguillaume@camptocamp.com> ha scritto:I am not sure about Simone.. He's not really reliable right?!Of course +1Le mar. 27 août 2019 à 13:46, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :+1 for Simone
Bruno Joliveau - Architecte applications - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, CanadaLe mar. 27 août 2019 à 03:26, Guewen Baconnier <guewen.baconnier@camptocamp.com> a écrit :Hi,Simone is a regular and engaged contributor of the connector and its subsidiary repositories (connector-interfaces, ...). I'd like to sponsor him as member of the PSC.--_______________________________________________
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 Stéphane Bidoul - 08:45 - 28 Aug 2019 -
Re: Re: Proposing Simone Orsi for Connectors PSC
YesOn Tue, Aug 27, 2019 at 7:26 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:On Tue, Aug 27, 2019 at 7:01 PM Andrea Cometa - Apulia Software Srl <a.cometa@apuliasoftware.it> wrote:I'm not sure either, Joël...kidding+1 for SimoneInviato da BlueMailIl giorno 27 ago 2019, alle ore 18:32, "Joël Grand-Guillaume" <joel.grandguillaume@camptocamp.com> ha scritto:I am not sure about Simone.. He's not really reliable right?!Of course +1Le mar. 27 août 2019 à 13:46, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :+1 for Simone
Bruno Joliveau - Architecte applications - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, CanadaLe mar. 27 août 2019 à 03:26, Guewen Baconnier <guewen.baconnier@camptocamp.com> a écrit :Hi,Simone is a regular and engaged contributor of the connector and its subsidiary repositories (connector-interfaces, ...). I'd like to sponsor him as member of the PSC.--_______________________________________________
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 - 07:36 - 28 Aug 2019 -
Re: Re: Proposing Simone Orsi for Connectors PSC
On Tue, Aug 27, 2019 at 7:01 PM Andrea Cometa - Apulia Software Srl <a.cometa@apuliasoftware.it> wrote:I'm not sure either, Joël...kidding+1 for SimoneInviato da BlueMailIl giorno 27 ago 2019, alle ore 18:32, "Joël Grand-Guillaume" <joel.grandguillaume@camptocamp.com> ha scritto:I am not sure about Simone.. He's not really reliable right?!Of course +1Le mar. 27 août 2019 à 13:46, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :+1 for Simone
Bruno Joliveau - Architecte applications - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, CanadaLe mar. 27 août 2019 à 03:26, Guewen Baconnier <guewen.baconnier@camptocamp.com> a écrit :Hi,Simone is a regular and engaged contributor of the connector and its subsidiary repositories (connector-interfaces, ...). I'd like to sponsor him as member of the PSC.--_______________________________________________
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 - 07:25 - 27 Aug 2019 -
Re: optimisation of odoo frontend
Awesome!
Am 26. August 2019 14:57:05 MESZ schrieb "Mignon, Laurent" <laurent.mignon@acsone.eu>:Hi Frederik,Cool did you finally erase Angnolia in favor of Elasticsearch from the equitation ?
Yes, shopinvader now supports both Algolia and Elasticsearch. In the coming weeks, we will have two new sites in production based on shopinvader/elasticsearchCan we have another Demo during OCA days ?
I think Sébastien Beau plans to do a presentation during the OCA Days_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Dr.-Ing. Frederik Kramer
Geschäftsführer
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
Phone: +49 4105 56156-12
Fax: +49 4105 56156-10
Mobil: +49 179 3901819
Email: frederik.kramer@initos.com
Web: www.initos.com
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
by Frederik Kramer - 07:06 - 27 Aug 2019 -
Re: optimisation of odoo frontend
Seb,
I'd definitely love to hear / see it.
Best FrederikAm 27. August 2019 10:22:00 MESZ schrieb Sebastien Beau <sebastien.beau@akretion.com>:Hi during the OCA days I plan to do two things.Having a presentation of Shopinvader (it will be not the same as last year the aim is to present the news feature and the roadmap)Having a training to start with Shopinvader.The default template will new use elasticsearch so we will have by default a 100% opensource stack !Le lun. 26 août 2019 à 14:57, Mignon, Laurent <laurent.mignon@acsone.eu> a écrit :Hi Frederik,Cool did you finally erase Angnolia in favor of Elasticsearch from the equitation ?
Yes, shopinvader now supports both Algolia and Elasticsearch. In the coming weeks, we will have two new sites in production based on shopinvader/elasticsearchCan we have another Demo during OCA days ?
I think Sébastien Beau plans to do a presentation during the OCA Days_______________________________________________
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
--
Dr.-Ing. Frederik Kramer
Geschäftsführer
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
Phone: +49 4105 56156-12
Fax: +49 4105 56156-10
Mobil: +49 179 3901819
Email: frederik.kramer@initos.com
Web: www.initos.com
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
by Frederik Kramer - 07:06 - 27 Aug 2019 -
Re: Re: Proposing Simone Orsi for Connectors PSC
I'm not sure either, Joël...kidding+1 for SimoneInviato da BlueMailIl giorno 27 ago 2019, alle ore 18:32, "Joël Grand-Guillaume" <joel.grandguillaume@camptocamp.com> ha scritto:I am not sure about Simone.. He's not really reliable right?!Of course +1Le mar. 27 août 2019 à 13:46, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :+1 for Simone
Bruno Joliveau - Architecte applications - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, CanadaLe mar. 27 août 2019 à 03:26, Guewen Baconnier <guewen.baconnier@camptocamp.com> a écrit :Hi,Simone is a regular and engaged contributor of the connector and its subsidiary repositories (connector-interfaces, ...). I'd like to sponsor him as member of the PSC.--_______________________________________________
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 Andrea Cometa - 07:00 - 27 Aug 2019