Archives
Contributors
-
Re: Goodbye runbot, welcome runboat
Hooray! Welcome, runboat!Thanks a lot for the outstanding work!On Thu, Jan 27, 2022 at 6:07 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:Dear contributors,As you may have noticed, a new tool arrived in the OCA landscape: runboat.It is a runbot replacement that is specially tailored to OCA needs. Its key feature is that it prepares Odoo environments from GitHub commits, and once they are initialized they are kept in a dormant state, ready to start in seconds when needed for testing. This way we can have a very large number of environments ready to use (up to 10 000 on our current machine), so there is a great chance that the branch you want to test is readily available and there is no wait for functional people wanting to contribute.If you are curious about the technology behind it, the runboat source code is available on GitHub, and this twitter thread highlights some tools used to create it.It is currently enabled for branches 10 to 15. And the test environment corresponding to each PR or commit is linked as part of the GitHub checks (look at the red cross or green check mark).Soon, links to runboat will be added to the README.md files of all repos for branches 13, 14 and 15.You can also open it for a repo and Odoo version with a link like this: https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branch=14.0It is currently not enabled for branches older than 10, although in principle it should work for 8 and 9 too. If you need it and want to help make it happen, do not hesitate to get in touch on discord.Since runboat is proving to work very well and is much more resource efficient than runbot, while at the same time providing a better user experience, we can now shutdown runbot, in order to save on OCA server costs.With the help of Alexandre Fayolle, we are going to do that in the coming weeks, so prepare to say goodbye to runbot!Most existing links to runbot.odoo-community.org will then redirect to runboat.In the meantime, if you notice issues do not hesitate to get in touch by @ mentioning me on the PRs for which the runboat build would fail and you don't readily understand why or how to fix it. This will also help prepare for the move from Travis to GitHub actions which we are also planning in the first part of 2022.I also monitor the OCA Infrastructure discord channel from time to time.Best regards, and happy testing!-sbi--Stéphane BidoulOperations Director
M: +32 498 72 46 54
_______________________________________________
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. - 02:21 - 28 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Le ven. 28 janv. 2022 à 11:57, Raphaël Reverdy <raphael.reverdy@akretion.com> a écrit :Thanks ! It's a huge improvement.Le ven. 28 janv. 2022 à 09:26, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :It works like a charm! I can start an environment instantly, it is a huge improvement.Thanks a lot Stéphane!On Fri, 28 Jan 2022 at 09:16, Radovan Skolnik <radovan@skolnik.info> wrote:Thaks a million, Stephane! Magnificient work indeed! Best regards, Radovan Skolnik On štvrtok 27. januára 2022 18:07:31 CET Stéphane Bidoul wrote: > Dear contributors, > As you may have noticed, a new tool arrived in the OCA landscape: runboat. > It is a runbot replacement that is specially tailored to OCA needs. Its key > feature is that it prepares Odoo environments from GitHub commits, and once > they are initialized they are kept in a dormant state, ready to start in > seconds when needed for testing. This way we can have a very large number > of environments ready to use (up to 10 000 on our current machine), so > there is a great chance that the branch you want to test is readily > available and there is no wait for functional people wanting to contribute. > If you are curious about the technology behind it, the runboat source code > is available on GitHub [1] , and this twitter thread highlights some tools > used to create it [2] . It is currently enabled for branches 10 to 15. And > the test environment corresponding to each PR or commit is linked as part > of the GitHub checks (look at the red cross or green check mark). > > Soon, links to runboat will be added to the README.md files of all repos for > branches 13, 14 and 15. You can also open it for a repo and Odoo version > with a link like this: > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [3] It is currently not enabled for branches older than 10, although > in principle it should work for 8 and 9 too. If you need it and want to > help make it happen, do not hesitate to get in touch on discord. Since > runboat is proving to work very well and is much more resource efficient > than runbot, while at the same time providing a better user experience, we > can now shutdown runbot, in order to save on OCA server costs. With the > help of Alexandre Fayolle, we are going to do that in the coming weeks, so > prepare to say goodbye to runbot! Most existing links to > runbot.odoo-community.org [4] will then redirect to runboat. In the > meantime, if you notice issues do not hesitate to get in touch by @ > mentioning me on the PRs for which the runboat build would fail and you > don't readily understand why or how to fix it. This will also help prepare > for the move from Travis to GitHub actions which we are also planning in > the first part of 2022. I also monitor the OCA Infrastructure discord > channel from time to time. Best regards, and happy testing! > -sbi > -- Stéphane Bidoul Operations Director > M: +32 498 72 46 54 None [5] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [6] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7] > > > > [1] https://github.com/sbidoul/runboat > [2] https://twitter.com/SBidoul/status/1467143341083086864 > [3] > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [4] http://runbot.odoo-community.org > [5] http://acsone.eu/ > [6] https://odoo-community.org/groups/contributors-15 > [7] 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
--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by David BEAL - 01:21 - 28 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Thanks ! It's a huge improvement.Le ven. 28 janv. 2022 à 09:26, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :It works like a charm! I can start an environment instantly, it is a huge improvement.Thanks a lot Stéphane!On Fri, 28 Jan 2022 at 09:16, Radovan Skolnik <radovan@skolnik.info> wrote:Thaks a million, Stephane! Magnificient work indeed! Best regards, Radovan Skolnik On štvrtok 27. januára 2022 18:07:31 CET Stéphane Bidoul wrote: > Dear contributors, > As you may have noticed, a new tool arrived in the OCA landscape: runboat. > It is a runbot replacement that is specially tailored to OCA needs. Its key > feature is that it prepares Odoo environments from GitHub commits, and once > they are initialized they are kept in a dormant state, ready to start in > seconds when needed for testing. This way we can have a very large number > of environments ready to use (up to 10 000 on our current machine), so > there is a great chance that the branch you want to test is readily > available and there is no wait for functional people wanting to contribute. > If you are curious about the technology behind it, the runboat source code > is available on GitHub [1] , and this twitter thread highlights some tools > used to create it [2] . It is currently enabled for branches 10 to 15. And > the test environment corresponding to each PR or commit is linked as part > of the GitHub checks (look at the red cross or green check mark). > > Soon, links to runboat will be added to the README.md files of all repos for > branches 13, 14 and 15. You can also open it for a repo and Odoo version > with a link like this: > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [3] It is currently not enabled for branches older than 10, although > in principle it should work for 8 and 9 too. If you need it and want to > help make it happen, do not hesitate to get in touch on discord. Since > runboat is proving to work very well and is much more resource efficient > than runbot, while at the same time providing a better user experience, we > can now shutdown runbot, in order to save on OCA server costs. With the > help of Alexandre Fayolle, we are going to do that in the coming weeks, so > prepare to say goodbye to runbot! Most existing links to > runbot.odoo-community.org [4] will then redirect to runboat. In the > meantime, if you notice issues do not hesitate to get in touch by @ > mentioning me on the PRs for which the runboat build would fail and you > don't readily understand why or how to fix it. This will also help prepare > for the move from Travis to GitHub actions which we are also planning in > the first part of 2022. I also monitor the OCA Infrastructure discord > channel from time to time. Best regards, and happy testing! > -sbi > -- Stéphane Bidoul Operations Director > M: +32 498 72 46 54 None [5] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [6] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7] > > > > [1] https://github.com/sbidoul/runboat > [2] https://twitter.com/SBidoul/status/1467143341083086864 > [3] > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [4] http://runbot.odoo-community.org > [5] http://acsone.eu/ > [6] https://odoo-community.org/groups/contributors-15 > [7] 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
--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60
by Raphaël Reverdy - 11:56 - 28 Jan 2022 -
Re: Goodbye runbot, welcome runboat
It works like a charm! I can start an environment instantly, it is a huge improvement.Thanks a lot Stéphane!On Fri, 28 Jan 2022 at 09:16, Radovan Skolnik <radovan@skolnik.info> wrote:Thaks a million, Stephane! Magnificient work indeed! Best regards, Radovan Skolnik On štvrtok 27. januára 2022 18:07:31 CET Stéphane Bidoul wrote: > Dear contributors, > As you may have noticed, a new tool arrived in the OCA landscape: runboat. > It is a runbot replacement that is specially tailored to OCA needs. Its key > feature is that it prepares Odoo environments from GitHub commits, and once > they are initialized they are kept in a dormant state, ready to start in > seconds when needed for testing. This way we can have a very large number > of environments ready to use (up to 10 000 on our current machine), so > there is a great chance that the branch you want to test is readily > available and there is no wait for functional people wanting to contribute. > If you are curious about the technology behind it, the runboat source code > is available on GitHub [1] , and this twitter thread highlights some tools > used to create it [2] . It is currently enabled for branches 10 to 15. And > the test environment corresponding to each PR or commit is linked as part > of the GitHub checks (look at the red cross or green check mark). > > Soon, links to runboat will be added to the README.md files of all repos for > branches 13, 14 and 15. You can also open it for a repo and Odoo version > with a link like this: > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [3] It is currently not enabled for branches older than 10, although > in principle it should work for 8 and 9 too. If you need it and want to > help make it happen, do not hesitate to get in touch on discord. Since > runboat is proving to work very well and is much more resource efficient > than runbot, while at the same time providing a better user experience, we > can now shutdown runbot, in order to save on OCA server costs. With the > help of Alexandre Fayolle, we are going to do that in the coming weeks, so > prepare to say goodbye to runbot! Most existing links to > runbot.odoo-community.org [4] will then redirect to runboat. In the > meantime, if you notice issues do not hesitate to get in touch by @ > mentioning me on the PRs for which the runboat build would fail and you > don't readily understand why or how to fix it. This will also help prepare > for the move from Travis to GitHub actions which we are also planning in > the first part of 2022. I also monitor the OCA Infrastructure discord > channel from time to time. Best regards, and happy testing! > -sbi > -- Stéphane Bidoul Operations Director > M: +32 498 72 46 54 None [5] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [6] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7] > > > > [1] https://github.com/sbidoul/runboat > [2] https://twitter.com/SBidoul/status/1467143341083086864 > [3] > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [4] http://runbot.odoo-community.org > [5] http://acsone.eu/ > [6] https://odoo-community.org/groups/contributors-15 > [7] 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
--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869
by Aarón Henríquez - 09:25 - 28 Jan 2022 -
Re: Spanish Payroll
Hola Harald,
Gracias por tu respuesta, estaba pensando en contactar la asociación a ver si habían más empresas para ejecutar algo así.Por lo complicado que se ve el tema, habría que analizar que alternativa o planteamiento podemos hacer con este cliente particular.
Un saludo !El 28/01/2022 8:01 Harald Panten Lopez <harald.panten@sygel.es> escribió:
Hi Jorge,
What an ambitious project! We've been talking about Spanish payrolls for years but this project didn't continue over.
You can contact https://www.aeodoo.org and ask them about that. Maybe they can help you coordinating a working group, or helping you to find other companies interested in order to carry on the work.
Regards.
El jue, 27 ene 2022 a las 16:52, Jorge Elena Poblet (<j.elena@binhex.es>) escribió:
Hi all,
Does enyone have experience in Spanish Payroll app ?
We have a very interesting Odoo project, but we lack the experience required for this module in particular.
We are looking for working with someone to help us implement this particular app.
Regards
Jorge Elena Poblet
Consultor Tecnológico
Gerente | Binhex Systems Solutions S.L.
+34 822 179 267 | +34 622 40 08 08 
j.elena@binhex.es 
https://binhex.es 
Calle Lepanto, 3A, Santa Cruz de Tenerife, Islas Canarias, España 
Aviso legal:
Protección de datos. - Binhex Systems Solutions, S.L. le informa que su dirección de correo electrónico, así como el resto de sus datos personales serán usados para nuestra relación y poder prestarle nuestros servicios. Dichos datos son necesarios para poder relacionarnos con usted, lo que nos permite el uso de su información dentro de la legalidad. Asimismo, podrán tener conocimiento de su información aquellas entidades que necesiten tener acceso a la misma para que podamos prestarle nuestros servicios. Conservaremos sus datos durante nuestra relación y mientras nos obliguen las leyes aplicables. En cualquier momento puede dirigirse a nosotros para saber qué información tenemos sobre usted, rectificarla si fuese incorrecta y eliminarla una vez finalizada nuestra relación. También tiene derecho a solicitar el traspaso de su información a otra entidad (portabilidad). Para solicitar alguno de estos derechos, deberá realizar una solicitud escrita a nuestra dirección, junto con una fotocopia de su DNI:
Binhex Systems Solutions, S.L., con dirección en Calle Lepanto 3, 2A, CP 38005, Santa Cruz de Tenerife (Santa Cruz de Tenerife). En caso de que entienda que sus derechos han sido desatendidos, puede formular una reclamación en la Agencia Española de Protección de Datos (www.agpd.es).
Confidencialidad. - El contenido de esta comunicación, así como el de toda la documentación anexa, es confidencial y va dirigida al destinatario del mismo. En el supuesto de que usted no fuera el destinatario, le solicitamos que nos lo indique y no comunique su contenido a terceros, procediendo a su destrucción.
Exención de responsabilidad. - El envío de la presente comunicación no implica la obligación por parte del remitente de controlar la ausencia de virus, gusanos, troyanos y/o cualquier otro programa informático dañino, correspondiendo al destinatario disponer de las herramientas de hardware y software necesarias para garantizar tanto la seguridad de su sistema de información como la detección y eliminación de programas informáticos dañinos. Binhex Systems Solutions, S.L. no se responsabiliza de los daños y perjuicios que tales programas informáticos puedan causar al destinatario._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41 harald.panten@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Jorge Elena Poblet - 09:21 - 28 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Thaks a million, Stephane! Magnificient work indeed! Best regards, Radovan Skolnik On štvrtok 27. januára 2022 18:07:31 CET Stéphane Bidoul wrote: > Dear contributors, > As you may have noticed, a new tool arrived in the OCA landscape: runboat. > It is a runbot replacement that is specially tailored to OCA needs. Its key > feature is that it prepares Odoo environments from GitHub commits, and once > they are initialized they are kept in a dormant state, ready to start in > seconds when needed for testing. This way we can have a very large number > of environments ready to use (up to 10 000 on our current machine), so > there is a great chance that the branch you want to test is readily > available and there is no wait for functional people wanting to contribute. > If you are curious about the technology behind it, the runboat source code > is available on GitHub [1] , and this twitter thread highlights some tools > used to create it [2] . It is currently enabled for branches 10 to 15. And > the test environment corresponding to each PR or commit is linked as part > of the GitHub checks (look at the red cross or green check mark). > > Soon, links to runboat will be added to the README.md files of all repos for > branches 13, 14 and 15. You can also open it for a repo and Odoo version > with a link like this: > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [3] It is currently not enabled for branches older than 10, although > in principle it should work for 8 and 9 too. If you need it and want to > help make it happen, do not hesitate to get in touch on discord. Since > runboat is proving to work very well and is much more resource efficient > than runbot, while at the same time providing a better user experience, we > can now shutdown runbot, in order to save on OCA server costs. With the > help of Alexandre Fayolle, we are going to do that in the coming weeks, so > prepare to say goodbye to runbot! Most existing links to > runbot.odoo-community.org [4] will then redirect to runboat. In the > meantime, if you notice issues do not hesitate to get in touch by @ > mentioning me on the PRs for which the runboat build would fail and you > don't readily understand why or how to fix it. This will also help prepare > for the move from Travis to GitHub actions which we are also planning in > the first part of 2022. I also monitor the OCA Infrastructure discord > channel from time to time. Best regards, and happy testing! > -sbi > -- Stéphane Bidoul Operations Director > M: +32 498 72 46 54 None [5] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [6] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7] > > > > [1] https://github.com/sbidoul/runboat > [2] https://twitter.com/SBidoul/status/1467143341083086864 > [3] > https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branc > h=14.0 [4] http://runbot.odoo-community.org > [5] http://acsone.eu/ > [6] https://odoo-community.org/groups/contributors-15 > [7] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 09:16 - 28 Jan 2022 -
Re: Spanish Payroll
Hi Jorge,What an ambitious project! We've been talking about Spanish payrolls for years but this project didn't continue over.You can contact https://www.aeodoo.org and ask them about that. Maybe they can help you coordinating a working group, or helping you to find other companies interested in order to carry on the work.Regards.El jue, 27 ene 2022 a las 16:52, Jorge Elena Poblet (<j.elena@binhex.es>) escribió:Hi all,
Does enyone have experience in Spanish Payroll app ?
We have a very interesting Odoo project, but we lack the experience required for this module in particular.
We are looking for working with someone to help us implement this particular app.
Regards
Jorge Elena Poblet
Consultor Tecnológico
Gerente | Binhex Systems Solutions S.L.
+34 822 179 267 | +34 622 40 08 08 j.elena@binhex.es https://binhex.es Calle Lepanto, 3A, Santa Cruz de Tenerife, Islas Canarias, España
Aviso legal:
Protección de datos. - Binhex Systems Solutions, S.L. le informa que su dirección de correo electrónico, así como el resto de sus datos personales serán usados para nuestra relación y poder prestarle nuestros servicios. Dichos datos son necesarios para poder relacionarnos con usted, lo que nos permite el uso de su información dentro de la legalidad. Asimismo, podrán tener conocimiento de su información aquellas entidades que necesiten tener acceso a la misma para que podamos prestarle nuestros servicios. Conservaremos sus datos durante nuestra relación y mientras nos obliguen las leyes aplicables. En cualquier momento puede dirigirse a nosotros para saber qué información tenemos sobre usted, rectificarla si fuese incorrecta y eliminarla una vez finalizada nuestra relación. También tiene derecho a solicitar el traspaso de su información a otra entidad (portabilidad). Para solicitar alguno de estos derechos, deberá realizar una solicitud escrita a nuestra dirección, junto con una fotocopia de su DNI:
Binhex Systems Solutions, S.L., con dirección en Calle Lepanto 3, 2A, CP 38005, Santa Cruz de Tenerife (Santa Cruz de Tenerife). En caso de que entienda que sus derechos han sido desatendidos, puede formular una reclamación en la Agencia Española de Protección de Datos (www.agpd.es).
Confidencialidad. - El contenido de esta comunicación, así como el de toda la documentación anexa, es confidencial y va dirigida al destinatario del mismo. En el supuesto de que usted no fuera el destinatario, le solicitamos que nos lo indique y no comunique su contenido a terceros, procediendo a su destrucción.
Exención de responsabilidad. - El envío de la presente comunicación no implica la obligación por parte del remitente de controlar la ausencia de virus, gusanos, troyanos y/o cualquier otro programa informático dañino, correspondiendo al destinatario disponer de las herramientas de hardware y software necesarias para garantizar tanto la seguridad de su sistema de información como la detección y eliminación de programas informáticos dañinos. Binhex Systems Solutions, S.L. no se responsabiliza de los daños y perjuicios que tales programas informáticos puedan causar al destinatario._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41 harald.panten@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Harald Panten Lopez - 09:00 - 28 Jan 2022 -
Re: Goodbye runbot, welcome runboat
On Fri, Jan 28, 2022 at 2:42 AM Yoshi Tashiro <tashiro@quartile.co> wrote:I somehow can't see this thread on the OCA website for a 403 error, though: https://odoo-community.org/groups/contributors-15/contributors-234170I have noticed too. There is apparently a bug with our mailing list software when there are images in messages. I applied the latest patches but it did not help.Best regards,-sbi
by Stéphane Bidoul - 08:35 - 28 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Very nice tool.
Thanks Stéphane
Antonio M. Vigliotti
Mobile (+39) 342.8740910
Il 27/01/22 18:07, Stéphane Bidoul ha scritto:
Dear contributors,
As you may have noticed, a new tool arrived in the OCA landscape: runboat.
It is a runbot replacement that is specially tailored to OCA needs. Its key feature is that it prepares Odoo environments from GitHub commits, and once they are initialized they are kept in a dormant state, ready to start in seconds when needed for testing. This way we can have a very large number of environments ready to use (up to 10 000 on our current machine), so there is a great chance that the branch you want to test is readily available and there is no wait for functional people wanting to contribute.
If you are curious about the technology behind it, the runboat source code is available on GitHub, and this twitter thread highlights some tools used to create it.
It is currently enabled for branches 10 to 15. And the test environment corresponding to each PR or commit is linked as part of the GitHub checks (look at the red cross or green check mark).
Soon, links to runboat will be added to the README.md files of all repos for branches 13, 14 and 15.
You can also open it for a repo and Odoo version with a link like this: https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branch=14.0
It is currently not enabled for branches older than 10, although in principle it should work for 8 and 9 too. If you need it and want to help make it happen, do not hesitate to get in touch on discord.
Since runboat is proving to work very well and is much more resource efficient than runbot, while at the same time providing a better user experience, we can now shutdown runbot, in order to save on OCA server costs.
With the help of Alexandre Fayolle, we are going to do that in the coming weeks, so prepare to say goodbye to runbot!
Most existing links to runbot.odoo-community.org will then redirect to runboat.
In the meantime, if you notice issues do not hesitate to get in touch by @ mentioning me on the PRs for which the runboat build would fail and you don't readily understand why or how to fix it. This will also help prepare for the move from Travis to GitHub actions which we are also planning in the first part of 2022.
I also monitor the OCA Infrastructure discord channel from time to time.
Best regards, and happy testing!
-sbi
--
Stéphane BidoulOperations Director
M: +32 498 72 46 54
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Antonio M. Vigliotti - 07:40 - 28 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Thanks Stéphane, it is indeed a great step forward to involve functional people !On Fri, Jan 28, 2022 at 12:07 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:Dear contributors,As you may have noticed, a new tool arrived in the OCA landscape: runboat.It is a runbot replacement that is specially tailored to OCA needs. Its key feature is that it prepares Odoo environments from GitHub commits, and once they are initialized they are kept in a dormant state, ready to start in seconds when needed for testing. This way we can have a very large number of environments ready to use (up to 10 000 on our current machine), so there is a great chance that the branch you want to test is readily available and there is no wait for functional people wanting to contribute.If you are curious about the technology behind it, the runboat source code is available on GitHub, and this twitter thread highlights some tools used to create it.It is currently enabled for branches 10 to 15. And the test environment corresponding to each PR or commit is linked as part of the GitHub checks (look at the red cross or green check mark).Soon, links to runboat will be added to the README.md files of all repos for branches 13, 14 and 15.You can also open it for a repo and Odoo version with a link like this: https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branch=14.0It is currently not enabled for branches older than 10, although in principle it should work for 8 and 9 too. If you need it and want to help make it happen, do not hesitate to get in touch on discord.Since runboat is proving to work very well and is much more resource efficient than runbot, while at the same time providing a better user experience, we can now shutdown runbot, in order to save on OCA server costs.With the help of Alexandre Fayolle, we are going to do that in the coming weeks, so prepare to say goodbye to runbot!Most existing links to runbot.odoo-community.org will then redirect to runboat.In the meantime, if you notice issues do not hesitate to get in touch by @ mentioning me on the PRs for which the runboat build would fail and you don't readily understand why or how to fix it. This will also help prepare for the move from Travis to GitHub actions which we are also planning in the first part of 2022.I also monitor the OCA Infrastructure discord channel from time to time.Best regards, and happy testing!-sbi--Stéphane BidoulOperations Director
M: +32 498 72 46 54_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Jean-Charles Drubay - 03:10 - 28 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Thank you very much!I somehow can't see this thread on the OCA website for a 403 error, though: https://odoo-community.org/groups/contributors-15/contributors-234170--Yoshi TashiroOn Fri, Jan 28, 2022 at 2:07 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:Dear contributors,As you may have noticed, a new tool arrived in the OCA landscape: runboat.It is a runbot replacement that is specially tailored to OCA needs. Its key feature is that it prepares Odoo environments from GitHub commits, and once they are initialized they are kept in a dormant state, ready to start in seconds when needed for testing. This way we can have a very large number of environments ready to use (up to 10 000 on our current machine), so there is a great chance that the branch you want to test is readily available and there is no wait for functional people wanting to contribute.If you are curious about the technology behind it, the runboat source code is available on GitHub, and this twitter thread highlights some tools used to create it.It is currently enabled for branches 10 to 15. And the test environment corresponding to each PR or commit is linked as part of the GitHub checks (look at the red cross or green check mark).Soon, links to runboat will be added to the README.md files of all repos for branches 13, 14 and 15.You can also open it for a repo and Odoo version with a link like this: https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branch=14.0It is currently not enabled for branches older than 10, although in principle it should work for 8 and 9 too. If you need it and want to help make it happen, do not hesitate to get in touch on discord.Since runboat is proving to work very well and is much more resource efficient than runbot, while at the same time providing a better user experience, we can now shutdown runbot, in order to save on OCA server costs.With the help of Alexandre Fayolle, we are going to do that in the coming weeks, so prepare to say goodbye to runbot!Most existing links to runbot.odoo-community.org will then redirect to runboat.In the meantime, if you notice issues do not hesitate to get in touch by @ mentioning me on the PRs for which the runboat build would fail and you don't readily understand why or how to fix it. This will also help prepare for the move from Travis to GitHub actions which we are also planning in the first part of 2022.I also monitor the OCA Infrastructure discord channel from time to time.Best regards, and happy testing!-sbi--Stéphane BidoulOperations Director
M: +32 498 72 46 54_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Yoshi Tashiro. - 02:40 - 28 Jan 2022 -
RE: Goodbye runbot, welcome runboat
Thank you so much for this great work!
De: Stéphane Bidoul <stephane.bidoul@acsone.eu>
Enviado el: jueves, 27 de enero de 2022 18:08
Para: Contributors <contributors@odoo-community.org>
Asunto: Goodbye runbot, welcome runboatDear contributors,
As you may have noticed, a new tool arrived in the OCA landscape: runboat.
It is a runbot replacement that is specially tailored to OCA needs. Its key feature is that it prepares Odoo environments from GitHub commits, and once they are initialized they are kept in a dormant state, ready to start in seconds when needed for testing. This way we can have a very large number of environments ready to use (up to 10 000 on our current machine), so there is a great chance that the branch you want to test is readily available and there is no wait for functional people wanting to contribute.
If you are curious about the technology behind it, the runboat source code is available on GitHub, and this twitter thread highlights some tools used to create it.
It is currently enabled for branches 10 to 15. And the test environment corresponding to each PR or commit is linked as part of the GitHub checks (look at the red cross or green check mark).
Soon, links to runboat will be added to the README.md files of all repos for branches 13, 14 and 15.
You can also open it for a repo and Odoo version with a link like this: https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branch=14.0
It is currently not enabled for branches older than 10, although in principle it should work for 8 and 9 too. If you need it and want to help make it happen, do not hesitate to get in touch on discord.
Since runboat is proving to work very well and is much more resource efficient than runbot, while at the same time providing a better user experience, we can now shutdown runbot, in order to save on OCA server costs.
With the help of Alexandre Fayolle, we are going to do that in the coming weeks, so prepare to say goodbye to runbot!
Most existing links to runbot.odoo-community.org will then redirect to runboat.
In the meantime, if you notice issues do not hesitate to get in touch by @ mentioning me on the PRs for which the runboat build would fail and you don't readily understand why or how to fix it. This will also help prepare for the move from Travis to GitHub actions which we are also planning in the first part of 2022.
I also monitor the OCA Infrastructure discord channel from time to time.
Best regards, and happy testing!
-sbi
--
Stéphane Bidoul
Operations Director
M: +32 498 72 46 54_______________________________________________
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) - 07:06 - 27 Jan 2022 -
Re: New repositories : cooperative and participative supermarket
Hi Robin,+1 for the three repos.On Thu, Jan 27, 2022 at 6:22 PM <robin@coopiteasy.be> wrote:Hi Denis,
Thank you for your answer, it looks like my last email did not go through. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
As for refining the topics, I can try to rephrase :-)
- oca/cooperative would hold the modules allowing to
- Subscribe to a share, transfer a share or sell a share from the cooperative,
- Share subscription can be done online,
- Manage the cooperator registry of a cooperative,
- Generate legal reports for company and cooperators.
- oca/shift-planning would hold the modules allowing to
- Create a planning template of work shifts of the company
- Generate the shifts based on these templates,
- Allow partners to subscribe to regular tasks,
- Allow partners to subscribe to any task with available spot,
- Track the attendance to the shifts.
- oca/vertical-cooperative-supermarket* glues all these together to
- Track who can work in the cooperative
- Track who can shop in the cooperative
- welcome screens and member cards
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
On 17 Jan 2022, 18:25 +0100, robin@coopiteasy.be, wrote:Hi Denis,
Thank you for your answer. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
As for refining the topics, I can try to rephrase :-)
• oca/cooperative would hold the modules allowing to
• Subscribe to a share, transfer a share or sell a share from the cooperative,
• Share subscription can be done online,
• Manage the cooperator registry of a cooperative,
• Generate legal reports for company and cooperators.
• oca/shift-planning would hold the modules allowing to
• Create a planning template of work shifts of the company
• Generate the shifts based on these templates,
• Allow partners to subscribe to regular tasks,
• Allow partners to subscribe to any task with available spot,
• Track the attendance to the shifts.
• oca/vertical-cooperative-supermarket* glues all these together to
• Track who can work in the cooperative
• Track who can shop in the cooperative
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
On 14 Jan 2022, 18:32 +0100, Roussel, Denis <denis.roussel@acsone.eu>, wrote:
Hi Robin,
That's great to hear this!
My two cents on this. Maybe you should refine the topics the repositories you want to create will cover (it does not help saying they are in beta). Especially for the first one.
For the third, we usually don't create 'temporary' repositories. I suggest you to create issues/PR's directly on OCA specific repos for modules you want to move. It will be more efficient and avoiding creation of one that will be deleted actually.
Don't hesitate if you have more technical questions, but for sure you have a good OCA contact person near you !
On Fri, Jan 14, 2022 at 11:27 AM <robin@coopiteasy.be> wrote:
Hi all,
At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :
cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.
We will need to
remove all references to Obeesdoo and Easy My Coop (debranding) ;
split modules by features ;
cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.
Based on the OCA repository policy, we would like to propose to create these 3 new repositories :
cooperative with all modules in beta-stage while we debrand them.
shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?
You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.
All inputs welcome,
Robin Keunen
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe
--
Denis RousselSoftware EngineerT : +32 2 888 31 49M : +32 472 22 00 57
Val Benoit, Quai Banning 6 | B-4000 Liège | BelgiumAtrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post 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 Denis Roussel - 06:56 - 27 Jan 2022 -
Re: New repositories : cooperative and participative supermarket
Hi Robin,With this explanation, the 3 repos you propose sound good to me, with a well-defined scope that does not seem to overlap with anything else in OCA.+1-sbiOn Thu, Jan 27, 2022 at 6:22 PM <robin@coopiteasy.be> wrote:Hi Denis,
Thank you for your answer, it looks like my last email did not go through. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
As for refining the topics, I can try to rephrase :-)
- oca/cooperative would hold the modules allowing to
- Subscribe to a share, transfer a share or sell a share from the cooperative,
- Share subscription can be done online,
- Manage the cooperator registry of a cooperative,
- Generate legal reports for company and cooperators.
- oca/shift-planning would hold the modules allowing to
- Create a planning template of work shifts of the company
- Generate the shifts based on these templates,
- Allow partners to subscribe to regular tasks,
- Allow partners to subscribe to any task with available spot,
- Track the attendance to the shifts.
- oca/vertical-cooperative-supermarket* glues all these together to
- Track who can work in the cooperative
- Track who can shop in the cooperative
- welcome screens and member cards
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
On 17 Jan 2022, 18:25 +0100, robin@coopiteasy.be, wrote:Hi Denis,
Thank you for your answer. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
As for refining the topics, I can try to rephrase :-)
• oca/cooperative would hold the modules allowing to
• Subscribe to a share, transfer a share or sell a share from the cooperative,
• Share subscription can be done online,
• Manage the cooperator registry of a cooperative,
• Generate legal reports for company and cooperators.
• oca/shift-planning would hold the modules allowing to
• Create a planning template of work shifts of the company
• Generate the shifts based on these templates,
• Allow partners to subscribe to regular tasks,
• Allow partners to subscribe to any task with available spot,
• Track the attendance to the shifts.
• oca/vertical-cooperative-supermarket* glues all these together to
• Track who can work in the cooperative
• Track who can shop in the cooperative
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
On 14 Jan 2022, 18:32 +0100, Roussel, Denis <denis.roussel@acsone.eu>, wrote:
Hi Robin,
That's great to hear this!
My two cents on this. Maybe you should refine the topics the repositories you want to create will cover (it does not help saying they are in beta). Especially for the first one.
For the third, we usually don't create 'temporary' repositories. I suggest you to create issues/PR's directly on OCA specific repos for modules you want to move. It will be more efficient and avoiding creation of one that will be deleted actually.
Don't hesitate if you have more technical questions, but for sure you have a good OCA contact person near you !
On Fri, Jan 14, 2022 at 11:27 AM <robin@coopiteasy.be> wrote:
Hi all,
At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :
cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.
We will need to
remove all references to Obeesdoo and Easy My Coop (debranding) ;
split modules by features ;
cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.
Based on the OCA repository policy, we would like to propose to create these 3 new repositories :
cooperative with all modules in beta-stage while we debrand them.
shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?
You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.
All inputs welcome,
Robin Keunen
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe
--
Denis RousselSoftware EngineerT : +32 2 888 31 49M : +32 472 22 00 57
Mailing-List: https://odoo-community.org/groups/contributors-15Post 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 - 06:50 - 27 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Great ! Looking forward to see the runboat in action !
Robin KeunenCoop IT Easyrobin@coopiteasy.be+32 488 86 57 40On 27 Jan 2022, 18:16 +0100, Roussel, Denis <denis.roussel@acsone.eu>, wrote:
Great news Stéphane!
I'm sure it will help us for faster developments/testing.Many thanks!
On Thu, Jan 27, 2022 at 6:07 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:Dear contributors,As you may have noticed, a new tool arrived in the OCA landscape: runboat.It is a runbot replacement that is specially tailored to OCA needs. Its key feature is that it prepares Odoo environments from GitHub commits, and once they are initialized they are kept in a dormant state, ready to start in seconds when needed for testing. This way we can have a very large number of environments ready to use (up to 10 000 on our current machine), so there is a great chance that the branch you want to test is readily available and there is no wait for functional people wanting to contribute.If you are curious about the technology behind it, the runboat source code is available on GitHub, and this twitter thread highlights some tools used to create it.It is currently enabled for branches 10 to 15. And the test environment corresponding to each PR or commit is linked as part of the GitHub checks (look at the red cross or green check mark).Soon, links to runboat will be added to the README.md files of all repos for branches 13, 14 and 15.You can also open it for a repo and Odoo version with a link like this: https://runboat.odoo-community.org/builds?repo=oca/mis-builder&target_branch=14.0It is currently not enabled for branches older than 10, although in principle it should work for 8 and 9 too. If you need it and want to help make it happen, do not hesitate to get in touch on discord.Since runboat is proving to work very well and is much more resource efficient than runbot, while at the same time providing a better user experience, we can now shutdown runbot, in order to save on OCA server costs.With the help of Alexandre Fayolle, we are going to do that in the coming weeks, so prepare to say goodbye to runbot!Most existing links to runbot.odoo-community.org will then redirect to runboat.In the meantime, if you notice issues do not hesitate to get in touch by @ mentioning me on the PRs for which the runboat build would fail and you don't readily understand why or how to fix it. This will also help prepare for the move from Travis to GitHub actions which we are also planning in the first part of 2022.I also monitor the OCA Infrastructure discord channel from time to time.Best regards, and happy testing!-sbi--Stéphane BidoulOperations Director
M: +32 498 72 46 54_______________________________________________
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 Robin Keunen - 06:30 - 27 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Great work! Congratulations and thanks!!El jue, 27 ene 2022 a la(s) 14:16, Pedro M. Baeza (Tecnativa) (pedro.baeza@tecnativa.com) escribió:Thanks for the excellent work, Stéphane and Alexandre.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 Juan José Scarafía - 06:26 - 27 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Nice!Congratz for the launch of runboat.Did you break a bottle on it before launching it to the ocean? :)Yannick VaucherBusiness Solutions ArchitectCamptocamp SAPSE A, CH-1015 LausannePhone: +41 21 619 10 30Office: +41 21 619 10 10On Thu, 27 Jan 2022 at 18:16, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:Thanks for the excellent work, Stéphane and Alexandre.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 Yannick Payot - 06:26 - 27 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Really good job, guys! 👏👏El jue, 27 ene 2022 a las 18:16, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:Thanks for the excellent work, Stéphane and Alexandre.Regards.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41 harald.panten@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Harald Panten Lopez - 06:26 - 27 Jan 2022 -
Re: New repositories : cooperative and participative
supermarket
Hi Denis,
Thank you for your answer, it looks like my last email did not go through. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
As for refining the topics, I can try to rephrase :-)
- oca/cooperative would hold the modules allowing to
- Subscribe to a share, transfer a share or sell a share from the cooperative,
- Share subscription can be done online,
- Manage the cooperator registry of a cooperative,
- Generate legal reports for company and cooperators.
- oca/shift-planning would hold the modules allowing to
- Create a planning template of work shifts of the company
- Generate the shifts based on these templates,
- Allow partners to subscribe to regular tasks,
- Allow partners to subscribe to any task with available spot,
- Track the attendance to the shifts.
- oca/vertical-cooperative-supermarket* glues all these together to
- Track who can work in the cooperative
- Track who can shop in the cooperative
- welcome screens and member cards
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
Robin KeunenCoop IT Easyrobin@coopiteasy.be+32 488 86 57 40On 17 Jan 2022, 18:25 +0100, robin@coopiteasy.be, wrote:Hi Denis,
Thank you for your answer. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :
The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
As for refining the topics, I can try to rephrase :-)
• oca/cooperative would hold the modules allowing to
• Subscribe to a share, transfer a share or sell a share from the cooperative,
• Share subscription can be done online,
• Manage the cooperator registry of a cooperative,
• Generate legal reports for company and cooperators.
• oca/shift-planning would hold the modules allowing to
• Create a planning template of work shifts of the company
• Generate the shifts based on these templates,
• Allow partners to subscribe to regular tasks,
• Allow partners to subscribe to any task with available spot,
• Track the attendance to the shifts.
• oca/vertical-cooperative-supermarket* glues all these together to
• Track who can work in the cooperative
• Track who can shop in the cooperative
* once cleaned up from all sale, purchase, pos, ... customisations.
I hope it’s clearer that way,
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
On 14 Jan 2022, 18:32 +0100, Roussel, Denis <denis.roussel@acsone.eu>, wrote:
Hi Robin,
That's great to hear this!
My two cents on this. Maybe you should refine the topics the repositories you want to create will cover (it does not help saying they are in beta). Especially for the first one.
For the third, we usually don't create 'temporary' repositories. I suggest you to create issues/PR's directly on OCA specific repos for modules you want to move. It will be more efficient and avoiding creation of one that will be deleted actually.
Don't hesitate if you have more technical questions, but for sure you have a good OCA contact person near you !
On Fri, Jan 14, 2022 at 11:27 AM <robin@coopiteasy.be> wrote:
Hi all,
At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :
cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.
We will need to
remove all references to Obeesdoo and Easy My Coop (debranding) ;
split modules by features ;
cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.
Based on the OCA repository policy, we would like to propose to create these 3 new repositories :
cooperative with all modules in beta-stage while we debrand them.
shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?
You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.
All inputs welcome,
Robin Keunen
Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe
--
Denis RousselSoftware EngineerT : +32 2 888 31 49M : +32 472 22 00 57
Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Robin Keunen - 06:21 - 27 Jan 2022 -
Re: Goodbye runbot, welcome runboat
Thanks for the excellent work, Stéphane and Alexandre.Regards.
by Pedro M. Baeza - 06:16 - 27 Jan 2022
