Archives
Contributors
contributors@odoo-community.org
-
Re: OCA Server appears to be down 2026/01/24 9:40 AM Mountain
I tried it just now and it was workinh on my end.
--Daniel
From: Landis Arnold <notifications@odoo-community.org>
Sent: Saturday, January 24, 2026 9:57:26 PM
To: Contributors <contributors@odoo-community.org>
Subject: OCA Server appears to be down 2026/01/24 9:40 AM MountainI was looking for a way to post this somewhere besides on the "down" OCA site.
perhaps in Github.
Anyway, all returns I am finding for OCA t his morning (USA Colorado Time) are returning
As an example:https://odoo-community.org/blog/news-updates-1/oca-mailing-lists-216
Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
Perhaps this would best be posted to GitHub but did not find a General "Issues" area that is not related to a specific repository.
Anyway, I thought to get the note out to those who might fix.
Often an easy fix, but who knows from the outside.
Best to all.
I appreciate your great work.
Landis Arnold
Nomadic, Inc.
Niwot, CO 80503
USA
larnold@nomadic.net
_______________________________________________
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 - 11:20 - 24 Jan 2026 -
OCA Server appears to be down 2026/01/24 9:40 AM Mountain
I was looking for a way to post this somewhere besides on the "down" OCA site.
perhaps in Github.
Anyway, all returns I am finding for OCA t his morning (USA Colorado Time) are returning
As an example:https://odoo-community.org/blog/news-updates-1/oca-mailing-lists-216
Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
Perhaps this would best be posted to GitHub but did not find a General "Issues" area that is not related to a specific repository.
Anyway, I thought to get the note out to those who might fix.
Often an easy fix, but who knows from the outside.
Best to all.
I appreciate your great work.Landis Arnold
Nomadic, Inc.
Niwot, CO 80503
USA
larnold@nomadic.net
by Landis Arnold - 10:54 - 24 Jan 2026 -
Re: Weighing scales
Hi,
El 22/1/26 a las 20:11, Kristof Gommers escribió:
These scales are sometimes too expensive for customers , did anyone else had success with other scales which also work with an IOT box or any other connection.We are installing Epelsa scales, this model most: https://grupoepelsa.com/en/basic-range-scales/77083-56-ppi-balanza-6-kg.html
We have integrated Epelsa driver in a IOT Box image to support it: https://github.com/criptomart/iotbox-epelsa
Regards.
santi noreña
criptomart servicios informáticos Sll
by Santiago Noreña Sobrado - 02:51 - 24 Jan 2026 -
Re: Reciprocity in PR opening vs reviews; banning contributors
And an option less intrusive but maybe more effective as setting a priority on a rating of the contributor? Computed on reviews, porting, modules etc or whatever.Then show the PRs on this priority and set in the guidelines that they will be prioritized?Sergio CoratoIl ven 23 gen 2026, 21:41 Adam Heinz <notifications@odoo-community.org> ha scritto:I understand where this is coming from, but have trouble believing that punishment will yield additional reviews. A small number of my own pull requests have been fixes for modules that I don't even use, because they were breaking the repository build. Under the proposed system, I would have to spend additional time reviewing pull requests (that I don't care about) to earn the privilege of fixing modules (that I don't care about).Speaking outside of my own experience, some of my colleagues who entered academia have lamented a similar sort of tendency in graduate students to favor the creation and publication of novel work for their theses, rather than review or reproduce the work of their peers.My best successes have been when another contributor and I accidentally worked on a fix or migration in parallel, then noticed each other and reviewed the better of the two prototypes. This suggests to me that perhaps a more granular ability to Watch a specific module instead of an entire repository could more easily put like-minded individuals in a position of mutual benefit (Jita Kyoei 自他共栄).On Fri, Jan 23, 2026 at 2:58 PM Holger Brunn <notifications@odoo-community.org> wrote:Hi all, on the OCA days, we discussed that the current situation with having way too much input for way too few reviewers is untenable. This has not improved since, quite the opposite. It's really hard to find the gems in the noise. Back then, I called for better automation for this, so here my proposal: Have a github action that counts lines of PRs somebody opened in a repo, vs the lines of PRs the person reviewed in that repo. Everyone must review at least twice as much as they submit. If after asking for more reviews, no reviews come, close the user's PRs automatically (in the repo, not all OCA) after some time. Also add a manual mechanism for banning users who try to cheat with bullshit reviews or otherwise undesirable behavior. PRs by banned users are closed automatically. I implemented both in https://github.com/hbrunn/social/blob/18.0/.github/workflows/reciprocity.yml resp https://github.com/hbrunn/social/blob/18.0/.github/workflows/ban.yml You can test this by creating PRs against my fork after cloning my version of the 18.0 branch. Banning works by adding a handle to a file .banned.txt in the repo's root. Before proposing this to oca-addons-repo-template, I'd like to hear some input from you. Best regards, Holger -- Your partner for the hard Odoo problems https://hunki-enterprises.com
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Sergio Corato - 11:51 - 23 Jan 2026 -
Re: Reciprocity in PR opening vs reviews; banning contributors
I understand where this is coming from, but have trouble believing that punishment will yield additional reviews. A small number of my own pull requests have been fixes for modules that I don't even use, because they were breaking the repository build. Under the proposed system, I would have to spend additional time reviewing pull requests (that I don't care about) to earn the privilege of fixing modules (that I don't care about).Speaking outside of my own experience, some of my colleagues who entered academia have lamented a similar sort of tendency in graduate students to favor the creation and publication of novel work for their theses, rather than review or reproduce the work of their peers.My best successes have been when another contributor and I accidentally worked on a fix or migration in parallel, then noticed each other and reviewed the better of the two prototypes. This suggests to me that perhaps a more granular ability to Watch a specific module instead of an entire repository could more easily put like-minded individuals in a position of mutual benefit (Jita Kyoei 自他共栄).On Fri, Jan 23, 2026 at 2:58 PM Holger Brunn <notifications@odoo-community.org> wrote:
Hi all, on the OCA days, we discussed that the current situation with having way too much input for way too few reviewers is untenable. This has not improved since, quite the opposite. It's really hard to find the gems in the noise. Back then, I called for better automation for this, so here my proposal: Have a github action that counts lines of PRs somebody opened in a repo, vs the lines of PRs the person reviewed in that repo. Everyone must review at least twice as much as they submit. If after asking for more reviews, no reviews come, close the user's PRs automatically (in the repo, not all OCA) after some time. Also add a manual mechanism for banning users who try to cheat with bullshit reviews or otherwise undesirable behavior. PRs by banned users are closed automatically. I implemented both in https://github.com/hbrunn/social/blob/18.0/.github/workflows/reciprocity.yml resp https://github.com/hbrunn/social/blob/18.0/.github/workflows/ban.yml You can test this by creating PRs against my fork after cloning my version of the 18.0 branch. Banning works by adding a handle to a file .banned.txt in the repo's root. Before proposing this to oca-addons-repo-template, I'd like to hear some input from you. Best regards, Holger -- Your partner for the hard Odoo problems https://hunki-enterprises.com
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Adam Heinz - 09:41 - 23 Jan 2026 -
Reciprocity in PR opening vs reviews; banning contributors
Hi all, on the OCA days, we discussed that the current situation with having way too much input for way too few reviewers is untenable. This has not improved since, quite the opposite. It's really hard to find the gems in the noise. Back then, I called for better automation for this, so here my proposal: Have a github action that counts lines of PRs somebody opened in a repo, vs the lines of PRs the person reviewed in that repo. Everyone must review at least twice as much as they submit. If after asking for more reviews, no reviews come, close the user's PRs automatically (in the repo, not all OCA) after some time. Also add a manual mechanism for banning users who try to cheat with bullshit reviews or otherwise undesirable behavior. PRs by banned users are closed automatically. I implemented both in https://github.com/hbrunn/social/blob/18.0/.github/workflows/reciprocity.yml resp https://github.com/hbrunn/social/blob/18.0/.github/workflows/ban.yml You can test this by creating PRs against my fork after cloning my version of the 18.0 branch. Banning works by adding a handle to a file .banned.txt in the repo's root. Before proposing this to oca-addons-repo-template, I'd like to hear some input from you. Best regards, Holger -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 08:56 - 23 Jan 2026 -
Re: Request for Removal from Mailing List – Persistent Unsubscribe Issue
As a note to anyone else reading, this was handled.
On 1/23/26 7:17 AM, Rob A wrote:
Dear Odoo Community Team, I am writing to request removal of my email address from the contributors mailing list. Despite multiple attempts to unsubscribe using the provided unsubscribe link (https://odoo-community.org/groups/unsubscribe), I continue to receive emails from this list. I want to switch for my professional address nls@robin4consulting.com Details: Email Address: rob.a@posteo.net Issue: Continued receipt of contributor updates despite attempting to unsubscribe Frequency: Receiving unwanted emails on a recurring basis The standard unsubscribe mechanism does not appear to be functioning correctly for my address. I would appreciate it if a moderator could manually remove my email from the distribution list. Thank you for your prompt attention to this matter. Best regards, Robin Angelé
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Tom Blauwendraat - 12:21 - 23 Jan 2026 -
Request for Removal from Mailing List – Persistent Unsubscribe Issue
Dear Odoo Community Team, I am writing to request removal of my email address from the contributors mailing list. Despite multiple attempts to unsubscribe using the provided unsubscribe link (https://odoo-community.org/groups/unsubscribe), I continue to receive emails from this list. I want to switch for my professional address nls@robin4consulting.com Details: Email Address: rob.a@posteo.net Issue: Continued receipt of contributor updates despite attempting to unsubscribe Frequency: Receiving unwanted emails on a recurring basis The standard unsubscribe mechanism does not appear to be functioning correctly for my address. I would appreciate it if a moderator could manually remove my email from the distribution list. Thank you for your prompt attention to this matter. Best regards, Robin Angelé
by Robin Angelé - 07:16 - 23 Jan 2026 -
Weighing scales
Hey Everyone,
I'm a fairly new member to the OCA (joined half 2025) and I didn't had much time to catch up.
I've been in the mailing and I see sometimes questions popping up & people helping eachother, which is great !
At the moment when you want a weighscale for the POS system for odoo EE a IOT is recommended and a ariva-S model.
These scales are sometimes too expensive for customers , did anyone else had success with other scales which also work with an IOT box or any other connection.
Mind you i'm looking for SaaS solutions also, so while i'm open to costume modules for other scales.
I'm also looking for scales that would work with SaaS enterprise solution.
Thank you all , and keep up the good work !
Sincerely
Kristof
--Kristof GommersGomworx BVT: +3215141242E: kristof@gomworx.comW: www.gomworx.com
by Kristof Gommers - 08:11 - 22 Jan 2026 -
Re: OCA will be at FOSDEM (31Jan/1st Feb)--> help us on the booth
Hello,
Please people fill the spreadsheet with the hours you can help at the OCA booth!
https://docs.google.com/spreadsheets/d/1xmOLcXD1uG3TvIXDs4X7wx9_I9-nmR5kCP5uTG6uVVo/edit?gid=0#gid=0
Virginie: might it help if the granularity is one hour shifts, so it will be easier for people to put in a shift between talks they want to attend?
Kind regards, Ronald
On 18-01-2026 15:42, Virginie Dewulf wrote:
Hello dear OCA members and contributors,
I hope 2026 is starting good for you, your business and your families!
I am happy to share that the OCA will be officially represented for the first time during the biggest open source event in the world, the well known FOSDEM. If you don't know about it, you'll find more about it here : https://fosdem.org/2026/
It's in Brussels (Belgium), on Saturday 31st January and Sunday 1st February.
It's a great experience, even if you are not a developer. I've been attending this event for many years and it's something to see once in your life: the city of Brussels become full of geeks and open source enthusiasts. The event takes place in the university (ULB) in many different rooms in 6 different buildings. It's also a good way to take your 10.000 steps a day ;) I particularly appreaciate the Community Dev Room, as well as the "Funding the FOSS ecosystem" Dev Room. There is a Python Dev Room, topics about Securyity, Performance, Testing... so many interesting things to learn!
For the first time, the OCA will be at FOSDEM with a booth (a stand), located in " F-02" together with Dolibarr ERP CRM.
I am looking for volunteers to help on the booth. That means: you need to be there for one or more shifts of 2h and talk to people who ask questions about Odoo, the OCA and open source ERP in general. We are already a small bunch of people (I can name hugues from Coop IT Easy, Sébastien Beau and Benoit Guillot from Akretion France, and even a developer working at Odoo, Stéphane Bidoul might join for a bit on Sunday.. and you?!)
Even if you are new in the community, your perspective will be good to share at the booth. No need to be an old-timer to come and help. It's also a nice way to meet other people of the community in real life.
Julie helped me set up this shared document so that you can indicate when you are happy to join the booth:
https://docs.google.com/spreadsheets/d/1xmOLcXD1uG3TvIXDs4X7wx9_I9-nmR5kCP5uTG6uVVo/edit?gid=0#gid=0
I'll get in touch with the volunteers a bit before the event starts.
Have a nice week, everyone!
--
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Ronald Portier - 03:36 - 22 Jan 2026 -
Re: OCA will be at FOSDEM (31Jan/1st Feb)--> help us on the booth
Hi,
I scrapped one session to at least do one full two hour shift.
Kind regards, Ronald
On 21-01-2026 15:51, Ronald Portier wrote:
Hi Virginie,
I will be attending FOSDEM, and would like to help at the booth. Only there are also a lot
of talks I would like to attend, not leaving any two hour gap.
But I can help on Saturday afternoon from 17:00 to 18:00 (in between PyInfra and sovereign digital workplace). And Sunday morning from opening to about 10:20 (after that going to the GnuPG talk). And Sunday afternoon from 15:45 to 16:45 (in between Jupyter Books and IBM 3278).
I hope that is still useful, and anyway look forward to see you and the other OCA friends!
Kind regards, Ronald
On 18-01-2026 15:42, Virginie Dewulf wrote:
Hello dear OCA members and contributors,
I hope 2026 is starting good for you, your business and your families!
I am happy to share that the OCA will be officially represented for the first time during the biggest open source event in the world, the well known FOSDEM. If you don't know about it, you'll find more about it here : https://fosdem.org/2026/
It's in Brussels (Belgium), on Saturday 31st January and Sunday 1st February.
It's a great experience, even if you are not a developer. I've been attending this event for many years and it's something to see once in your life: the city of Brussels become full of geeks and open source enthusiasts. The event takes place in the university (ULB) in many different rooms in 6 different buildings. It's also a good way to take your 10.000 steps a day ;) I particularly appreaciate the Community Dev Room, as well as the "Funding the FOSS ecosystem" Dev Room. There is a Python Dev Room, topics about Securyity, Performance, Testing... so many interesting things to learn!
For the first time, the OCA will be at FOSDEM with a booth (a stand), located in " F-02" together with Dolibarr ERP CRM.
I am looking for volunteers to help on the booth. That means: you need to be there for one or more shifts of 2h and talk to people who ask questions about Odoo, the OCA and open source ERP in general. We are already a small bunch of people (I can name hugues from Coop IT Easy, Sébastien Beau and Benoit Guillot from Akretion France, and even a developer working at Odoo, Stéphane Bidoul might join for a bit on Sunday.. and you?!)
Even if you are new in the community, your perspective will be good to share at the booth. No need to be an old-timer to come and help. It's also a nice way to meet other people of the community in real life.
Julie helped me set up this shared document so that you can indicate when you are happy to join the booth:
https://docs.google.com/spreadsheets/d/1xmOLcXD1uG3TvIXDs4X7wx9_I9-nmR5kCP5uTG6uVVo/edit?gid=0#gid=0
I'll get in touch with the volunteers a bit before the event starts.
Have a nice week, everyone!
--
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Ronald Portier - 03:35 - 22 Jan 2026 -
Re: OCA will be at FOSDEM (31Jan/1st Feb)--> help us on the booth
Hi Virginie,
I will be attending FOSDEM, and would like to help at the booth. Only there are also a lot
of talks I would like to attend, not leaving any two hour gap.
But I can help on Saturday afternoon from 17:00 to 18:00 (in between PyInfra and sovereign digital workplace). And Sunday morning from opening to about 10:20 (after that going to the GnuPG talk). And Sunday afternoon from 15:45 to 16:45 (in between Jupyter Books and IBM 3278).
I hope that is still useful, and anyway look forward to see you and the other OCA friends!
Kind regards, Ronald
On 18-01-2026 15:42, Virginie Dewulf wrote:
Hello dear OCA members and contributors,
I hope 2026 is starting good for you, your business and your families!
I am happy to share that the OCA will be officially represented for the first time during the biggest open source event in the world, the well known FOSDEM. If you don't know about it, you'll find more about it here : https://fosdem.org/2026/
It's in Brussels (Belgium), on Saturday 31st January and Sunday 1st February.
It's a great experience, even if you are not a developer. I've been attending this event for many years and it's something to see once in your life: the city of Brussels become full of geeks and open source enthusiasts. The event takes place in the university (ULB) in many different rooms in 6 different buildings. It's also a good way to take your 10.000 steps a day ;) I particularly appreaciate the Community Dev Room, as well as the "Funding the FOSS ecosystem" Dev Room. There is a Python Dev Room, topics about Securyity, Performance, Testing... so many interesting things to learn!
For the first time, the OCA will be at FOSDEM with a booth (a stand), located in " F-02" together with Dolibarr ERP CRM.
I am looking for volunteers to help on the booth. That means: you need to be there for one or more shifts of 2h and talk to people who ask questions about Odoo, the OCA and open source ERP in general. We are already a small bunch of people (I can name hugues from Coop IT Easy, Sébastien Beau and Benoit Guillot from Akretion France, and even a developer working at Odoo, Stéphane Bidoul might join for a bit on Sunday.. and you?!)
Even if you are new in the community, your perspective will be good to share at the booth. No need to be an old-timer to come and help. It's also a nice way to meet other people of the community in real life.
Julie helped me set up this shared document so that you can indicate when you are happy to join the booth:
https://docs.google.com/spreadsheets/d/1xmOLcXD1uG3TvIXDs4X7wx9_I9-nmR5kCP5uTG6uVVo/edit?gid=0#gid=0
I'll get in touch with the volunteers a bit before the event starts.
Have a nice week, everyone!
--
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Ronald Portier - 03:55 - 21 Jan 2026 -
Re: addon name length limit for weblate
Component length is defined as a constant in https://github.com/WeblateOrg/weblate/blob/main/weblate/trans/defines.pyCOMPONENT_NAME_LENGTH = 100Since Weblate is a django application:python manage.py makemigrations
python manage.py migrateshould be enough to fix the issueThe main drawback is that it should be reapplied after each update--
Yann PAPOUINLe dim. 18 janv. 2026 à 19:56, Moises Lopez <notifications@odoo-community.org> a écrit :Excellent!Check the following new check:And the following dummy PR to test it:El dom, 18 ene 2026 a la(s) 11:57 a.m., Stéphane Bidoul (notifications@odoo-community.org) escribió:Hi Moises,Nice!Here is the one that caused problem: stock-logistics-release-channel-18.0-sale_stock_release_channel_delivery_date_plan_shipment_lead_timeBest regards,-StéphaneOn Sun, Jan 18, 2026 at 6:41 PM Moises Lopez <notifications@odoo-community.org> wrote:Hi Stéphane,I can do the linter.Could you share me the result of a "addon_component_name" in order to know what words are considered (team/repo or only repo)?El dom, 18 ene 2026 a la(s) 10:57 a.m., Stéphane Bidoul (notifications@odoo-community.org) escribió:Hi everyone,While investigating weblate issues I found that the component names are limited to 100 characters.I don't think there is a workaround for that so at the moment the component generator is skipping them.If anyone feels like implementing a linter for addon names length this could be helpful. For weblate the addon name + repo name should not be over 90 characters or so.Best regards,-Stéphane_______________________________________________
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 Yann Papouin - 05:36 - 19 Jan 2026 -
Re: addon name length limit for weblate
Excellent!Check the following new check:And the following dummy PR to test it:El dom, 18 ene 2026 a la(s) 11:57 a.m., Stéphane Bidoul (notifications@odoo-community.org) escribió:Hi Moises,Nice!Here is the one that caused problem: stock-logistics-release-channel-18.0-sale_stock_release_channel_delivery_date_plan_shipment_lead_timeBest regards,-StéphaneOn Sun, Jan 18, 2026 at 6:41 PM Moises Lopez <notifications@odoo-community.org> wrote:Hi Stéphane,I can do the linter.Could you share me the result of a "addon_component_name" in order to know what words are considered (team/repo or only repo)?El dom, 18 ene 2026 a la(s) 10:57 a.m., Stéphane Bidoul (notifications@odoo-community.org) escribió:Hi everyone,While investigating weblate issues I found that the component names are limited to 100 characters.I don't think there is a workaround for that so at the moment the component generator is skipping them.If anyone feels like implementing a linter for addon names length this could be helpful. For weblate the addon name + repo name should not be over 90 characters or so.Best regards,-Stéphane_______________________________________________
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 Moisés López Calderón - 07:56 - 18 Jan 2026 -
Update weblate
Hi everyone,I just upgraded https://translation.odoo-community.org to weblate 5.15.I could not pinpoint the root cause of recent instabilities, so I hope the upgrade will resolve the issue. If not, I'll dig deeper.Best regards,-Stéphane
by Stéphane Bidoul - 06:56 - 18 Jan 2026 -
Re: addon name length limit for weblate
Hi Moises,Nice!Here is the one that caused problem: stock-logistics-release-channel-18.0-sale_stock_release_channel_delivery_date_plan_shipment_lead_timeBest regards,-StéphaneOn Sun, Jan 18, 2026 at 6:41 PM Moises Lopez <notifications@odoo-community.org> wrote:Hi Stéphane,I can do the linter.Could you share me the result of a "addon_component_name" in order to know what words are considered (team/repo or only repo)?El dom, 18 ene 2026 a la(s) 10:57 a.m., Stéphane Bidoul (notifications@odoo-community.org) escribió:Hi everyone,While investigating weblate issues I found that the component names are limited to 100 characters.I don't think there is a workaround for that so at the moment the component generator is skipping them.If anyone feels like implementing a linter for addon names length this could be helpful. For weblate the addon name + repo name should not be over 90 characters or so.Best regards,-Stéphane
_______________________________________________
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 - 06:56 - 18 Jan 2026 -
Re: addon name length limit for weblate
Hi Stéphane,I can do the linter.Could you share me the result of a "addon_component_name" in order to know what words are considered (team/repo or only repo)?El dom, 18 ene 2026 a la(s) 10:57 a.m., Stéphane Bidoul (notifications@odoo-community.org) escribió:Hi everyone,While investigating weblate issues I found that the component names are limited to 100 characters.I don't think there is a workaround for that so at the moment the component generator is skipping them.If anyone feels like implementing a linter for addon names length this could be helpful. For weblate the addon name + repo name should not be over 90 characters or so.Best regards,-Stéphane
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Moisés López Calderón - 06:40 - 18 Jan 2026 -
addon name length limit for weblate
Hi everyone,While investigating weblate issues I found that the component names are limited to 100 characters.I don't think there is a workaround for that so at the moment the component generator is skipping them.If anyone feels like implementing a linter for addon names length this could be helpful. For weblate the addon name + repo name should not be over 90 characters or so.Best regards,-Stéphane
by Stéphane Bidoul - 05:56 - 18 Jan 2026 -
OCA will be at FOSDEM (31Jan/1st Feb)--> help us on the booth
Hello dear OCA members and contributors,
I hope 2026 is starting good for you, your business and your families!
I am happy to share that the OCA will be officially represented for the first time during the biggest open source event in the world, the well known FOSDEM. If you don't know about it, you'll find more about it here : https://fosdem.org/2026/
It's in Brussels (Belgium), on Saturday 31st January and Sunday 1st February.
It's a great experience, even if you are not a developer. I've been attending this event for many years and it's something to see once in your life: the city of Brussels become full of geeks and open source enthusiasts. The event takes place in the university (ULB) in many different rooms in 6 different buildings. It's also a good way to take your 10.000 steps a day ;) I particularly appreaciate the Community Dev Room, as well as the "Funding the FOSS ecosystem" Dev Room. There is a Python Dev Room, topics about Securyity, Performance, Testing... so many interesting things to learn!
For the first time, the OCA will be at FOSDEM with a booth (a stand), located in " F-02" together with Dolibarr ERP CRM.
I am looking for volunteers to help on the booth. That means: you need to be there for one or more shifts of 2h and talk to people who ask questions about Odoo, the OCA and open source ERP in general. We are already a small bunch of people (I can name hugues from Coop IT Easy, Sébastien Beau and Benoit Guillot from Akretion France, and even a developer working at Odoo, Stéphane Bidoul might join for a bit on Sunday.. and you?!)
Even if you are new in the community, your perspective will be good to share at the booth. No need to be an old-timer to come and help. It's also a nice way to meet other people of the community in real life.
Julie helped me set up this shared document so that you can indicate when you are happy to join the booth:
https://docs.google.com/spreadsheets/d/1xmOLcXD1uG3TvIXDs4X7wx9_I9-nmR5kCP5uTG6uVVo/edit?gid=0#gid=0
I'll get in touch with the volunteers a bit before the event starts.
Have a nice week, everyone!
--
by Konsilia SRL - 03:40 - 18 Jan 2026
