Archives
Contributors
contributors@odoo-community.org
-
Weblate UX research
Hi everyone,I just met some weblate folks at FOSDEM and learned they are running a UX research survey.You can find it a https://weblate.org/FOSDEM.So if you are a translator and have a few minutes to spare, your participation will be super helpful to them.Best regards,-Stéphane
by Stéphane Bidoul - 10:10 - 1 Feb 2026 -
Re: [SPAM] Re: [SPAM] Re: Connecting weight scales to Odoo
My understanding was that this was actually a standard Odoo feature and that no extra module is needed, but Hugues would know better, i didnt actually implement this for anyone myself
by Tom Blauwendraat - 11:25 - 31 Jan 2026 -
Re: [SPAM] Re: [SPAM] Re: Connecting weight scales to Odoo
Thanks Hugues 🙏Le sam. 31 janv. 2026, 19:11, hugues de keyzer <notifications@odoo-community.org> a écrit :not yet, but it should work fine.
Le 31 janvier 2026 18:32:16 GMT+01:00, Houssine BAKKALI <notifications@odoo-community.org> a écrit :Hi Hugue,Great news :) It's already used for production ?Thanks !HoussineLe sam. 31 janv. 2026 à 18:22, hugues de keyzer <notifications@odoo-community.org> a écrit :hi houssine,
we ported it to 16.0 (and added features) here: https://github.com/OCA/pos/pull/1397
kind regards,
huguesLe 31 janvier 2026 18:06:51 GMT+01:00, Houssine BAKKALI <notifications@odoo-community.org> a écrit :Hi Tom,I'm searching for a module allowing self-service weighing and I found your email.Could you please point me to the repo of such a module ? I have knowledge of this module of coop it easy from v12 https://github.com/coopiteasy/addons/tree/12.0/pos_self_service_base but nothing newer than that.Greetings,HoussineLe jeu. 6 févr. 2025 à 11:43, Tom Blauwendraat <notifications@odoo-community.org> a écrit :Note that there is also the option to use self-service weighing which prints out a barcode sticker, which can then be scanned at the checkout using standard Odoo barcode nomenclature.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Houssine BAKKALI - 08:00 - 31 Jan 2026 -
Re: [SPAM] Re: Connecting weight scales to Odoo
Hi Hugue,Great news :) It's already used for production ?Thanks !HoussineLe sam. 31 janv. 2026 à 18:22, hugues de keyzer <notifications@odoo-community.org> a écrit :
hi houssine,
we ported it to 16.0 (and added features) here: https://github.com/OCA/pos/pull/1397
kind regards,
huguesLe 31 janvier 2026 18:06:51 GMT+01:00, Houssine BAKKALI <notifications@odoo-community.org> a écrit :Hi Tom,I'm searching for a module allowing self-service weighing and I found your email.Could you please point me to the repo of such a module ? I have knowledge of this module of coop it easy from v12 https://github.com/coopiteasy/addons/tree/12.0/pos_self_service_base but nothing newer than that.Greetings,HoussineLe jeu. 6 févr. 2025 à 11:43, Tom Blauwendraat <notifications@odoo-community.org> a écrit :Note that there is also the option to use self-service weighing which prints out a barcode sticker, which can then be scanned at the checkout using standard Odoo barcode nomenclature.
_______________________________________________
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 Houssine BAKKALI - 06:30 - 31 Jan 2026 -
Re: Connecting weight scales to Odoo
Hi Tom,I'm searching for a module allowing self-service weighing and I found your email.Could you please point me to the repo of such a module ? I have knowledge of this module of coop it easy from v12 https://github.com/coopiteasy/addons/tree/12.0/pos_self_service_base but nothing newer than that.Greetings,HoussineLe jeu. 6 févr. 2025 à 11:43, Tom Blauwendraat <notifications@odoo-community.org> a écrit :
Note that there is also the option to use self-service weighing which prints out a barcode sticker, which can then be scanned at the checkout using standard Odoo barcode nomenclature.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Houssine BAKKALI - 06:06 - 31 Jan 2026 -
Re: W0223 (abstract-method) warning in pylint-odooHi
Hi, I'm not quite sure if this one should be ignored for Odoo or not, but for examples of Pylint configurations you can look at the OCA CI template: https://github.com/OCA/oca-addons-repo-template/blob/master/version-specific/mqt-compat/.pylintrc-mandatory.jinja Or how it works out in actual repositories: https://github.com/OCA/server-tools/blob/18.0/.pylintrc-mandatory -Tom On 1/31/26 9:42 AM, Serhii Miroshnychenko wrote: > > Hello, everyone. > > When I check any Odoo module using pylint-odoo, I always get the > warning “W0223: Method ‘onchange’ is abstract in class ‘BaseModel’ but > is not overridden in child class ‘...’ (abstract-method)” for any class. > > Please advise if this is a false warning. If not, what is the reason > for it? > > Also, please tell me if there are any recommended .pylintrc settings > for high-quality Odoo development. > > Thank you! > > _______________________________________________ > 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 - 10:41 - 31 Jan 2026 -
W0223 (abstract-method) warning in pylint-odoo
Hello, everyone.
When I check any Odoo module using pylint-odoo, I always get the warning “W0223: Method ‘onchange’ is abstract in class ‘BaseModel’ but is not overridden in child class ‘...’ (abstract-method)” for any class.
Please advise if this is a false warning. If not, what is the reason for it?
Also, please tell me if there are any recommended .pylintrc settings for high-quality Odoo development.
Thank you!
by Serhii Miroshnychenko - 09:41 - 31 Jan 2026 -
Propose of a module to handle stock evaluation
Hi all,there is a wip proposal from a member of the Italian community for a module to manage the stock evaluation with the standard methods (FIFO/LIFO continuous or periodic, AVG, standard) here:https://github.com/OCA/stock-logistics-reporting/pull/442 which supports many useful functions, like making evaluations with different methods, exporting deeply, show details of the evaluation by single records, etc.We were wondering if there are any interests from other countries in this module, if not, we'll move this PR on our localization for a better and faster integration.Best regards,Sergio Corato
by Sergio Corato - 10:20 - 30 Jan 2026 -
Re: OCA will be at FOSDEM (31Jan/1st Feb)--> help us on the booth
Hello everyone,
This is a reminder in case you come to FOSDEM this weekend, come and see us at the OCA booth (F-02)!
And if you can join and spare 1 or 2 hours with us, please add your name here:
https://docs.google.com/spreadsheets/d/1xmOLcXD1uG3TvIXDs4X7wx9_I9-nmR5kCP5uTG6uVVo/edit?gid=0#gid=0
Have a nice end of week,
Virginie
Le 18/01/26 à 15:37, Virginie Dewulf a écrit :
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 - 10:51 - 29 Jan 2026 -
-
Re: Reciprocity in PR opening vs reviews; banning contributors
On Mon, Jan 26, 2026 at 11:42 PM Graeme Gellatly <notifications@odoo-community.org> wrote:This might sound like a crazy way to handle, but how about solving by setting a PR limit per repo. So a PSC can set a policy of say, at any given time, only 10 open PR's are allowed, and no PR can be older than say 4 months. Once limit is hit, no new PR can be accepted until limits resolved.This is basically kanban? I'd be willing to participate in a trial of this on any of the repositories that I follow.
by Adam Heinz - 02:00 - 27 Jan 2026 -
Re: Reciprocity in PR opening vs reviews; banning contributors
> Holger, what do you make of this inverted carrot approach rather than a > stick? seeing it fail for 10+ years -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 09:50 - 27 Jan 2026 -
Re: Reciprocity in PR opening vs reviews; banning contributors
On 1/27/26 9:37 AM, Enric Tobella Alomar wrote: > So if we decide to use this data, I think it should be for promotion > and visibility, not for banning contributors. ...but what about for kindly, politely and lovingly ranking/labeling PR's? Also rather not?
by Tom Blauwendraat - 09:50 - 27 Jan 2026 -
Re: Reciprocity in PR opening vs reviews; banning contributors
Hello!I like the idea of using statistics to show the path we expect contributors to follow. However, I don’t think we should ban or limit users who don’t follow that path.In my experience, newcomers rarely meet these expectations at the beginning. It often takes around a year before people start collaborating the way we would like (doing reviews, participating in discussions, etc.). Some people get there faster, others slower, but we shouldn’t limit them because of that.Obviously, we can enforce rules like a 2 reviews : 1 PR ratio for PSCs or maintainers (and IMO, we should), but not for everyone.Collaboration data is very interesting, but relying only on data can be counterproductive and, in some cases, unfair. Reviews and contributions are hard to evaluate properly. Should we ban someone who does 3 high-quality reviews (with thoughtful comments and valuable points) and 10 fix PRs (including migrations), while promoting someone who does 10 reviews with no comments and 1 PR that creates a lot of extra work for others due to their way of working?This kind of data can be useful when looking at large numbers and trends, but with smaller samples, it’s easy to draw the wrong conclusions. IMO, using it can be a double-edged sword.So if we decide to use this data, I think it should be for promotion and visibility, not for banning contributors.My 2 cents.El mar, 27 ene 2026 a las 9:12, Tom Blauwendraat (<notifications@odoo-community.org>) escribió:On 1/27/26 8:57 AM, Jairo Llopis wrote: > IMHO statistics should be used as a prize, not as a weapon. Agreed! And it still could achieve the same: if a PR or contributor is valued very highly, his/her PR's float to the top of the sorting/filtering of reviewers anyway. And also the message to the contributors is clear: *this* is how you can get a higher ranking. So it still might achieve the same. Holger, what do you make of this inverted carrot approach rather than a stick?_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Enric Tobella AlomarCEO & Founder
by Enric Tobella Alomar - 09:35 - 27 Jan 2026 -
Re: Reciprocity in PR opening vs reviews; banning contributors
On 1/27/26 8:57 AM, Jairo Llopis wrote: > IMHO statistics should be used as a prize, not as a weapon. Agreed! And it still could achieve the same: if a PR or contributor is valued very highly, his/her PR's float to the top of the sorting/filtering of reviewers anyway. And also the message to the contributors is clear: *this* is how you can get a higher ranking. So it still might achieve the same. Holger, what do you make of this inverted carrot approach rather than a stick?
by Tom Blauwendraat - 09:11 - 27 Jan 2026 -
Re: Reciprocity in PR opening vs reviews; banning contributors
Hello folks!El vie, 23 ene 2026 a las 19:58, Holger Brunn (<notifications@odoo-community.org>) escribió: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.The solution you're proposing is quite dramatic. Really, are we going to ban someone that contributes too much? We already have few contributions...IMHO statistics should be used as a prize, not as a weapon.
by Jairo Llopis - 08:55 - 27 Jan 2026 -
Re: Reciprocity in PR opening vs reviews; banning contributors
This might sound like a crazy way to handle, but how about solving by setting a PR limit per repo. So a PSC can set a policy of say, at any given time, only 10 open PR's are allowed, and no PR can be older than say 4 months. Once limit is hit, no new PR can be accepted until limits resolved.On Tue, Jan 27, 2026 at 3:47 PM Raphaël Valyi <notifications@odoo-community.org> wrote:Hello,I think Enric metrics could be a good basis. But sadly they are also easy to hack, some organizations already put some juniors to approve everything they can to brag about how well ranked in the OCA they are (yup), so sadly any metric will be cheated... That's why it's important we could have a human based process to ban people who are obviously trying to cheat the metrics.But in fact, I would suggest changing Enric metrics: Yes we want to value reviews because we need people to review instead of only expecting others to spend time reviewing their very own stuff for free.But what about stopping to count positive reviews once there are more than say 5 positive reviews for 1 negative. Say we agree we find it sane that at least 20% of the PR should detect problems and not just be lenient approval of the company PRs. People will still be able to approve more than 80% of the PRs they review, but at least they won't receive more points for that. And if we see juniors inventing non existing problems to boost their negative reviews quota, we can probably easily catch them.I don't know, any metric is easily a tyranny, but at some point we will have to play cats and mouses with these KPIs because it will be the only way to scale beyond the usual 50 historical committers. And yes, as Holger explained, generative AI is going to quickly put a huge burden on the already overworked real OCA contributors.On Mon, Jan 26, 2026 at 9:32 PM Tom Blauwendraat <notifications@odoo-community.org> wrote:For me it would be too much at once, and a bit of a blunt instrument.
It could also be hacked by someone giving out two blind LGTM reviews in the repo per each PR he/she wants to do.
What about an organisation-wide karma rating based on Enric's contribution statistics, perhaps adding more metrics there where needed, which the oca-git-bot then can read and apply labels to PR's that people then can choose to filter on? There are also some new tools out there that can detect AI contributions, so if someone does a lot of those, that could also negatively impact the karma score. When going below a certain karma rate, it then could lead to auto closing or banning, but that's something we could rather phase in gently.
-Tom
On 1/26/26 6:12 PM, Holger Brunn wrote:
Thanks for your points. > 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 and wouldn't it have saved us several replication crises if you simply don't get to publish original work without attaching two replication papers? What I want to do here is shift incentives. We have to recognize that many companies use publishing to OCA as a way of externalizing costs of QA and maintenance, and as free stamp of quality. The individual employee then has the problem that they can use work time for publishing code, but not for reviewing. Tying those two together hopefully changes that. > And an option less intrusive but maybe more effective as setting a priority > on a rating of the contributor? I'd like that too, but we're constrained by the possibilities github offers, and that's simply not in the cards. If too many see autoclosing as too much of a problem (obviously I don't, we really need to lessen cognitive load on maintainers), I could imagine a label "reviewing contributor" that is set on PRs of people who do enough reviews, and then other reviewers can focus on those PRs. But that won't be as powerful for the incentive shifting I talk about above. > Can we give a way to appeal as well as a way to see what a > PR reviewed line count is for the repo? the action I've linked posts a message containing the line counts. Would be easy to add to the closing message too. Appeal goes the same way as other cases like stale autoclosing: Ask maintainers to reopen/apply a label to exempt from autoclosing. There is a class of janitorial PRs that should be exempted anyways, like fixing CI or updating from copier, but I wouldn't want to trust a stochastic parrot making that decision. And given those PRs tend to be merged fast, they don't strain your "line budget" for long. Note I propose to only count *open* PRs, once some PR is merged, it's off the ledger. -- 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
--Raphaël ValyiFounder and consultant_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Graeme Gellatly - 05:41 - 27 Jan 2026
