Archives
Contributors
contributors@odoo-community.org
-
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 -
Re: Reciprocity in PR opening vs reviews; banning contributors
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
by Raphaël Akretion - 03:46 - 27 Jan 2026 -
Re: Reciprocity in PR opening vs reviews; banning contributors
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
by Tom Blauwendraat - 10:30 - 26 Jan 2026 -
Re: Reciprocity in PR opening vs reviews; banning contributors
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
by Holger Brunn - 06:10 - 26 Jan 2026 -
Re: Weighing scales
El 26/1/26 a las 11:52, Kristof Gommers escribió:
So just to be clear , even if I have a certified weighing scale, odoo itself isn't certified enough as POS in european setting?
AFAIK, there is not an european cert for PoS, at least for weighing, in some regions of Spain we must certificate our accounting software in local tax authority but in others regions not...
When a client of ours (a supermarket) has had an inspection by the consumer authority, they have checked with a known weight the scale and the final result in the PoS, they validate the whole set is measuring fine in display and final ticket. They asked for the certificates of the scales, but they didn't say anything about the software.
I think we are mixing two different legal issues in PoS:
1. Accounting, each region has its own rules.
2. Consumers, each scale must be certificated, revised properly, measuring fine and must communicate reliably with PoS software.
Regards.
santi noreña
criptomart servicios informáticos
by Santiago Noreña Sobrado - 04:11 - 26 Jan 2026 -
Accrual for Annual Bonus
Hello everyone
I'm seeking advice on an accounting workflow for the 13th month salary or annual bonus within Odoo.
I need to know if there's an Odoo standard workflow or an OCA module that can help book this expense monthly, as we are not using a payroll module.
Any suggestions would be greatly appreciated.
Many thanks,
Lin
by Lin Nur Inayati - 02:05 - 26 Jan 2026 -
Re: Weighing scales
Hey All,
Already thank you for the replies.
I was under the impression if the scale is certified it should not be a problem?
Connect a scale — Odoo 19.0 documentation
The only requirement is that it is intregrated no?
I could be wrong since I don't have any knowledge about the legal info about scales.
As far as I know every scale has to be "checked" every 4 years by company that is registered as official by the goverment(in Belgium)
So just to be clear , even if I have a certified weighing scale, odoo itself isn't certified enough as POS in european setting?
Sincerely
Kristof
--Kristof GommersGomworx BVT: +3215141242E: kristof@gomworx.comW: www.gomworx.com
From: Frederik Kramer <notifications@odoo-community.org>
Sent: Monday, January 26, 2026 10:22
To: Contributors <contributors@odoo-community.org>
Subject: Re: Weighing scalesHi all,
well the latest i heard on this was from fellow Odooer Laurence Labusch (and his company Labiso GmbH). He has spent considerable time to narrow down that issue with the authorities and afaik it is still not allowed to use an electronic wheiging scale even if the POS itself is working according to the national standard which in Germany is implemented using fiskaly TSE unless the whole POS is certified with the weighing scale but maybe Laurence (which i am putting on copy can answer himself).
Best Frederik
P.S.: Jan-Marten maybe you can make Laurence aware of the Hamburg OCA Sprint ;-)
Am 26.01.26 um 10:12 schrieb Jan-Marten Veddeler:
My latest information (more a guess/feeling) from Odoo customer service (and some online research) on this was that if the POS is certified (like e.g. Odoo POS via fiscaly is in Germany), then the scale itself does not need to have an additional certification, and that this may explain why Odoo removed the below notice from its later documentation from v18 on
"Odoo is not certified in several countries, including France, Germany, and Switzerland. If you reside in one of these countries, you can still use a scale but without integration into your Odoo database. Alternatively, you can acquire a non-integrated certified scale that prints certified labels, which can then be scanned into your Odoo database."
Anyone has more clarity on this scale certification part in Germany or other EU countries?
Best
JanOn 1/26/2026 11:37 AM, hugues de keyzer wrote:
, to use a scale connected to a
--
Jan-Marten Veddeler
+49 15158887067
j.veddeler@humanilog.org
linkedin.com/in/jmveddeler
Berlin | Germany
Humanitarian Logistics Organisation e.V. | Humanilog
Tel.: Zentrale +49 40228686750
Post: Winsbergring 2 | 22525 Hamburg | Germany
Büro: Schnackenburgallee 11 | 22525 Hamburg | Germany
www.humanilog.orgGemeinsam können wir mehr erreichen.
Unterstützen Sie uns: humanilog.org/spenden_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Kristof Gommers - 11:51 - 26 Jan 2026 -
Re: Weighing scales
Hi all,
well the latest i heard on this was from fellow Odooer Laurence Labusch (and his company Labiso GmbH). He has spent considerable time to narrow down that issue with the authorities and afaik it is still not allowed to use an electronic wheiging scale even if the POS itself is working according to the national standard which in Germany is implemented using fiskaly TSE unless the whole POS is certified with the weighing scale but maybe Laurence (which i am putting on copy can answer himself).
Best Frederik
P.S.: Jan-Marten maybe you can make Laurence aware of the Hamburg OCA Sprint ;-)
Am 26.01.26 um 10:12 schrieb Jan-Marten Veddeler:
My latest information (more a guess/feeling) from Odoo customer service (and some online research) on this was that if the POS is certified (like e.g. Odoo POS via fiscaly is in Germany), then the scale itself does not need to have an additional certification, and that this may explain why Odoo removed the below notice from its later documentation from v18 on
"Odoo is not certified in several countries, including France, Germany, and Switzerland. If you reside in one of these countries, you can still use a scale but without integration into your Odoo database. Alternatively, you can acquire a non-integrated certified scale that prints certified labels, which can then be scanned into your Odoo database."
Anyone has more clarity on this scale certification part in Germany or other EU countries?
Best
JanOn 1/26/2026 11:37 AM, hugues de keyzer wrote:
, to use a scale connected to a
--
Jan-Marten Veddeler
+49 15158887067
j.veddeler@humanilog.org
linkedin.com/in/jmveddeler
Berlin | Germany
Humanitarian Logistics Organisation e.V. | Humanilog
Tel.: Zentrale +49 40228686750
Post: Winsbergring 2 | 22525 Hamburg | Germany
Büro: Schnackenburgallee 11 | 22525 Hamburg | Germany
www.humanilog.orgGemeinsam können wir mehr erreichen.
Unterstützen Sie uns: humanilog.org/spenden_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
by Frederik Kramer. - 10:20 - 26 Jan 2026 -
Re: Weighing scales
My latest information (more a guess/feeling) from Odoo customer service (and some online research) on this was that if the POS is certified (like e.g. Odoo POS via fiscaly is in Germany), then the scale itself does not need to have an additional certification, and that this may explain why Odoo removed the below notice from its later documentation from v18 on
"Odoo is not certified in several countries, including France, Germany, and Switzerland. If you reside in one of these countries, you can still use a scale but without integration into your Odoo database. Alternatively, you can acquire a non-integrated certified scale that prints certified labels, which can then be scanned into your Odoo database."
Anyone has more clarity on this scale certification part in Germany or other EU countries?
Best
JanOn 1/26/2026 11:37 AM, hugues de keyzer wrote:
, to use a scale connected to a
--
Jan-Marten Veddeler
+49 15158887067
j.veddeler@humanilog.org
linkedin.com/in/jmveddeler
Berlin | Germany
Humanitarian Logistics Organisation e.V. | Humanilog
Tel.: Zentrale +49 40228686750
Post: Winsbergring 2 | 22525 Hamburg | Germany
Büro: Schnackenburgallee 11 | 22525 Hamburg | Germany
www.humanilog.orgGemeinsam können wir mehr erreichen.
Unterstützen Sie uns: humanilog.org/spenden
by Jan-Marten Veddeler. - 10:11 - 26 Jan 2026 -
Re: OCA Server appears to be down 2026/01/24 9:40 AM Mountain
On 1/24/26 11:52 PM, Pierre Verkest wrote: > As far as I can tell, Odoo couldn't connect to the database, I've no > access to the database logs to investigate more, we probably reached > the connection pool limit. Same here, I see Postgres crashed, but I don't have enough rights to know what happened.
by Tom Blauwendraat - 11:36 - 25 Jan 2026 -
Re: OCA Server appears to be down 2026/01/24 9:40 AM Mountain
Thanks for reporting.This mailing list is managed by our Odoo itself so it's a bit of a chicken and eggs problem !Feel free to open an issue in https://github.com/OCA/oca-custom (at least I follow that repo) or you could ping the "Internal Tools" github team https://github.com/orgs/OCA/teams/internal-tools/membersAs far as I can tell, Odoo couldn't connect to the database, I've no access to the database logs to investigate more, we probably reached the connection pool limit.Regards,PierreLe sam. 24 janv. 2026 à 23:37, Landis Arnold <notifications@odoo-community.org> a écrit :Yes,
I noted just a bit ago it was just working again.
Several hours differential now. (5 hours) as 15:26 PM
After sending here, I found an "issue" location that might work for such posts but doubt that is an "immediate action" area.https://github.com/OCA/odoo-community.org/issues/255
I closed the issue which I created there after sending out the email here earlier today.
Glad it is running now,
Landis
Landis ArnoldFrom: "Daniel Reis" <notifications@odoo-community.org>
To: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Sent: Saturday, January 24, 2026 3:21:45 PM
Subject: Re: OCA Server appears to be down 2026/01/24 9:40 AM MountainI 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.
_______________________________________________
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 Pierre Verkest - 11:50 - 24 Jan 2026 -
Re: OCA Server appears to be down 2026/01/24 9:40 AM Mountain
Yes,
I noted just a bit ago it was just working again.
Several hours differential now. (5 hours) as 15:26 PM
After sending here, I found an "issue" location that might work for such posts but doubt that is an "immediate action" area.https://github.com/OCA/odoo-community.org/issues/255
I closed the issue which I created there after sending out the email here earlier today.
Glad it is running now,
Landis
Landis ArnoldFrom: "Daniel Reis" <notifications@odoo-community.org>
To: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Sent: Saturday, January 24, 2026 3:21:45 PM
Subject: Re: OCA Server appears to be down 2026/01/24 9:40 AM MountainI 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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Landis Arnold - 11:35 - 24 Jan 2026
