Archives
Contributors
-
Re: OCA Codesprint - around FOSDEM - are you keen?
Hi all,The event is live on the website.You can register online when you are ready: https://odoo-community.org/event/oca-codeprint-brussels-2025-01-30-2025-02-01-158/registerOptions to attend for one or two days or both!!We hope to see you in Brussels.RebeccaOn Fri, 20 Dec 2024 at 16:05, Rebecca Gellatly <rebecca@o4sb.com> wrote:Hello Peter,Yes, we are planning the Thursday/Friday 30th Jan/31st Jan before FODSEM.We are just confirming the venue and will be ready to share the details in the next week or so!Merry Christmas to you.RebeccaOn Fri, 20 Dec 2024 at 09:12, Peter Niederlag <notifications@odoo-community.org> wrote:Hi, is there any result from this discussion? Well, at least I have now planned a trip to Brussels :-> So count me in for some OCA-Booth at the Fosdem and I'd be happy to join some codesprint as well. best regards, Peter On 26.11.24 01:27, Rebecca Gellatly wrote: > Hello OCA Contributors, > You may have seen on our social media that we are weighing up if there is enough interest to organise an OCA Codesprint around the FOSDEM event [1] next year. > If this is something that is of interest to you, please let us know on our survey here. [2] Depending on interest we will make a decision about what to do. > The FOSDEM event [3] is on the 1st and 2nd of February in Brussels. We are considering a sprint a day or two on either side. > Have a great week. Rebecca > -- > Rebecca Gellatly General Secretary *Odoo Community Association* > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [4] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [5] > > > > [1] https://fosdem.org/2025/ > [2] https://odoo-community.org/survey/start/21bbf780-379b-48e8-ae0b-0c9e01da8be1 > [3] https://fosdem.org/2025/ > [4] https://odoo-community.org/groups/contributors-15 > [5] 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
--Rebecca GellatlyGeneral SecretaryOdoo Community Association--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 01:01 - 31 Dec 2025 -
Re: PSC responsabilities
Hi everyone,
I think the first step would be to create a system to automate or measure the contributions of PSC members. This would provide transparency and help ensure that everyone is contributing fairly. By tracking contributions, we can identify areas where PSCs or individual members may need more support or encouragement. This system could also serve as a foundation for rewarding contributors and giving them the visibility they deserve.
The goal should be to make contributors feel valued and motivated to keep up their involvement.
I think it's essential that we address this issue to ensure the strength and credibility of the community.
Kind regards,On Mon, Dec 30, 2024 at 9:28 AM Pedro M. Baeza <notifications@odoo-community.org> wrote:I agree that some PSCs are not exercising their obligations and are just there for their rights when there are selfish interests. Others are just because they are now on other things and have become obsolete.In summary, I agree that a PSC lifecycle should be implemented somehow.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Jorge Elena Poblet
Founder & CEO
Binhex
j.elena@binhex.cloud
Office (Spain) : +34 622 40 08 08
Office (USA): +1 561 403 4406Offices:
Miami | 8325 NE 2nd Ave, Miami, FL 33138, United States
Texas | 27027 Westheimer Pkwy Katy, TX 77494, United States
Tenerife | Street Subida al Mayorazgo, 13, Office 15-2
Las Palmas | Edificio Polivalente IV Campus de Tafira Parque Tecnológico de Gran Canaria
Start for free: Try Odoo Community in the cloud This email is confidential and intended only for the recipient. If you are not the intended recipient, please notify the sender and delete it immediately.
Privacy Policy
by Jorge Elena Poblet - 12:16 - 30 Dec 2025 -
Re: [SPAM] PSC responsabilities
I'm afraid images are not shown when attached in Odoo mailing groups.Regards.
by Pedro M. Baeza - 11:31 - 30 Dec 2025 -
Re: [SPAM] PSC responsabilities
Hi,I am exporting data directly from github pr information and exporting it to an elasticsearch index. There I cross the repo with the psc in order to get the information.Actually, your data is there (this year information):I get all the modified PRs in order to increase the data each day. For the analysis, I usually check by the closure date in order to avoid modifications of the KPIs (by creation date, we might need to wait 6 months to get the last year perspective).As participation, I checked if the user reviewed, commented or created the PR. We could increase the information by checking issues (right now, it is checking PRs only, but I can handle that)Kind regards,El lun, 30 dic 2024 a las 11:07, Jacques-Etienne Baudoux (<notifications@odoo-community.org>) escribió:Hello Enric,Can you share how this ranking is performed? What do you consider as participating?Does having a github profile configured as private (like me) have any incidence on the information you collect?krJ-ELe lun. 30 déc. 2024 à 10:17, Enric Tobella Alomar <notifications@odoo-community.org> a écrit :Hi everyone,I was preparing this year Ranking of contributors and I am concerned on some information I found when crossing this data with PSCs.I found several PSCs that are not involved into their respective repositories. For example, I found a PSC team that has 5 members, 3 of them participated in 1% of the PR, on of them on the 15% and the last one on 98%. The repository was big (more than 400 PR on one year). In other examples, the PSC only participated in their team PRs.Even in my case, I think I need to improve my collaboration as a PSC.I think we need to improve this situation as a Community, otherwise, people will loose faith in the PSCs and how OCA works. Some ideas I can think about:- Control PSCs on big repositories (it is hard to set a proper KPI on small repos)- Demote PSCs that are not contributing properly accor ding to this KPIs- Review this KPIs yearly- Split bigger PSCs in order to avoid too much work- Avoid people to be PSC of more than 3 big PSC Teams- Give PSCs some extra benefits (lower fees on OCA days, special t-shirts...)- Give PSCs recognition of their work (easy to say, hard to think about it)Maybe I am dramatic here, but I think it is important. WDYT? Shall we do something about it?Kind regards,--Enric Tobella AlomarCEO & Founder_______________________________________________
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
--Enric Tobella AlomarCEO & Founder
by Enric Tobella Alomar - 11:25 - 30 Dec 2025 -
Re: [SPAM] PSC responsabilities
Hello Enric,Can you share how this ranking is performed? What do you consider as participating?Does having a github profile configured as private (like me) have any incidence on the information you collect?krJ-ELe lun. 30 déc. 2024 à 10:17, Enric Tobella Alomar <notifications@odoo-community.org> a écrit :Hi everyone,I was preparing this year Ranking of contributors and I am concerned on some information I found when crossing this data with PSCs.I found several PSCs that are not involved into their respective repositories. For example, I found a PSC team that has 5 members, 3 of them participated in 1% of the PR, on of them on the 15% and the last one on 98%. The repository was big (more than 400 PR on one year). In other examples, the PSC only participated in their team PRs.Even in my case, I think I need to improve my collaboration as a PSC.I think we need to improve this situation as a Community, otherwise, people will loose faith in the PSCs and how OCA works. Some ideas I can think about:- Control PSCs on big repositories (it is hard to set a proper KPI on small repos)- Demote PSCs that are not contributing properly accor ding to this KPIs- Review this KPIs yearly- Split bigger PSCs in order to avoid too much work- Avoid people to be PSC of more than 3 big PSC Teams- Give PSCs some extra benefits (lower fees on OCA days, special t-shirts...)- Give PSCs recognition of their work (easy to say, hard to think about it)Maybe I am dramatic here, but I think it is important. WDYT? Shall we do something about it?Kind regards,--Enric Tobella AlomarCEO & Founder_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Jacques-Etienne Baudoux - 11:05 - 30 Dec 2025 -
Re: PSC responsabilities
I agree that some PSCs are not exercising their obligations and are just there for their rights when there are selfish interests. Others are just because they are now on other things and have become obsolete.In summary, I agree that a PSC lifecycle should be implemented somehow.Regards.
by Pedro M. Baeza - 10:26 - 30 Dec 2025 -
PSC responsabilities
Hi everyone,I was preparing this year Ranking of contributors and I am concerned on some information I found when crossing this data with PSCs.I found several PSCs that are not involved into their respective repositories. For example, I found a PSC team that has 5 members, 3 of them participated in 1% of the PR, on of them on the 15% and the last one on 98%. The repository was big (more than 400 PR on one year). In other examples, the PSC only participated in their team PRs.Even in my case, I think I need to improve my collaboration as a PSC.I think we need to improve this situation as a Community, otherwise, people will loose faith in the PSCs and how OCA works. Some ideas I can think about:- Control PSCs on big repositories (it is hard to set a proper KPI on small repos)- Demote PSCs that are not contributing properly according to this KPIs- Review this KPIs yearly- Split bigger PSCs in order to avoid too much work- Avoid people to be PSC of more than 3 big PSC Teams- Give PSCs some extra benefits (lower fees on OCA days, special t-shirts...)- Give PSCs recognition of their work (easy to say, hard to think about it)Maybe I am dramatic here, but I think it is important. WDYT? Shall we do something about it?Kind regards,--Enric Tobella AlomarCEO & Founder
by Enric Tobella Alomar - 10:16 - 30 Dec 2025 -
Migrating sign_oca to 18.0
best wishes for all :)I also suggest if the description and usage be modified to guide very new users.I would like some members to review and tell me if there is any bug.I am not 100% sure about perfect functionality, I have never used it before.I am delighted to share that I could finally migrate sign_oca module from version 17.0 to version 18.0.I exerted a lot of effort as:32 files changed+300 -262 lines changed
https://github.com/OCA/sign/pull/74
by Mohamed Alkobrosly - 12:21 - 28 Dec 2024 -
Re: [18.0] Project Task Git integration
Hi Quentin, thanks for your help!Ideally I'd like to have task sync with commits, pull requests and branches, also we're mainly focusing on github rather than gitlab. I will keep using https://github.com/OCA/project/pull/1390 as base for the implementation but I might definitely take some from your project. I see that you already have a task-pullrequest module published at https://github.com/Numigi/odoo-git-addons/tree/14.0/github_pull_request_project , will be interesting to see the other part.Thank you!Il giorno ven 20 dic 2024 alle ore 14:42 Quentin Lavallee <notifications@odoo-community.org> ha scritto:Hi,
We use the following modules to define a Pull Request object and update it via Github webhooks:
https://github.com/Numigi/odoo-git-addons/tree/14.0
It is in the process of being migrated to v16.
We then have a simple module (not published) that links Pull Requests in Odoo to tasks, we could open it if interested. The matching is done by looking for a task ID in Pull Request titles.
Cheers,Le dim. 15 déc. 2024 à 14:42, Francesco Ballerini <notifications@odoo-community.org> a écrit :Hi Janik, thank you so much for sharing! I took a look at the connector, and from what I can see, it allows to sync repositories in your local environment by providing terminal access directly within the Odoo interface, along with some useful shortcuts and pre-configured commands. It's an interesting approach, and I might draw some inspiration from it.For this task in particular I was especially interested in automatizing commit and pull requests behaviour by using git webhooks, and today I succeded setting up an environment to debug and extend the PR posted by Alan. It took me a while since I had to find a way to test webhooks with a localhost (never did it before), I finally succeded with a pretty simple Ngrok tunneling configuration.I take the opportunity to keep you update, at the moment my "roadmap" is:with the module webhook_gitlab that Alan provided in https://github.com/OCA/project/pull/13901 - setting up a developement environment in order to be able to debug, test, analyze code, extend the module on the version it was designed for (17.0) -- Done2 - extend "webhook_gitlab" module to incorporate desired behaviour, which is at least a sync of the commit history (and maybe pull requests) linked to a task providing a list with links to the task related commits.I'll share some notes on this step: as a general idea a commit should automatically be linked to the project task (when "push event webhook" triggers) if the commit message contains the name of any "project.task" from the Odoo Project linked with the repo where the push event triggered.E.g. I have Odoo Project named "Project X" linked to https://github.com/MyOrganization/ProjectX GitHub repo. When I push a commit into ProjectX GitHub repository I will notify Odoo server by setting a webhook that calls webhook processing controller . We should add a structured push processing method (at the moment only merging is processed I think) that compare every "project.task" name related to ProjectX and check if "project.task" name is found in the commit message. In that case the commit ID should be stored in a git.commit (new) model related to the project task and will be used to build a clickable url which is probably stored in a computed field. There should probably also be a commit resync button. -- TODO, doesn't seem too hard, but will require some time to be done.3 - when the functionality will be working on 17.0 I will migrate it on the 18.0 version (which is the version I need to work with this feature). The migration should not be hard in this case since most of the code will be methods to process github webhook requests and simply store some data in models, there shouldn't be huge changes in the code -- TODOI plan to proceed with these steps over the next few weeks. If you have any recommendations, please feel free to share them. I believe the hardest part for me will be writing tests, as I'm not very familiar with it. Thankfully, I think I’ll find substantial help in https://github.com/OCA/interface-github/tree/16.0/github_connectorIl giorno gio 12 dic 2024 alle ore 10:18 Janik von Rotz <notifications@odoo-community.org> ha scritto:Hi Francesco, I have developed a module to manage git repositories: https://github.com/Mint-System/Odoo-Apps-Connector/tree/16.0/git_base And here are the docs: https://www.odoo-wiki.org/git-base.html I will eventually develop a "project_git" module that connects projects with git repos and supports creating feature branches from tasks. All Mint System modules live up to the OCA standards. Cheers, Janik On 12/6/24 6:48 PM, Francesco Ballerini wrote: > Hi, > > we're looking for an Odoo 18 project task git integration. > > Specifically we need the feature that allows linking PR and commits to > the task by branch name/commit name containing the name of the task, > basically like Atlassian/Jira git integration. > > If you have any open source resource to provide as example we we might > try to migrate it to version 18.0. > > Thanks > > --Francesco Ballerini > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > -- We are hiring: https://www.mint-system.ch/jobs Send application to: jobs@mint-system.ch CTO Mint System GmbH Tel: +41 44 244 7222
_______________________________________________
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
--
Quentin Lavallée-BourdeauChargé de projets+1 514-317-7944
Nouveau
Essayez l'IA OpenSource pendant 30 joursDécouvrir _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Francesco Ballerini - 12:26 - 24 Dec 2024 -
The OCA is looking for a Content Creator & Training Manager (Deadline 24th January)
Hello everyone,With the OCA Board, we are organizing new projects for 2025. To do so, we will need more people to help out on a regular basis, hence the creation of this new position within the team (there are currently 2 people working for the OCA with a fee: Rebecca, General Secretary and Event Manager, and myself Virginie, Executive Director.We are looking for a Content Creator & Training Manager. The details are available here:The RFQ process is available here:Deadline to answer is on January, 23th, with the objective of getting started with this new role in the begin of February.Thanks a lot for sharing and applying if you are interested!A side note: I remind you that there is another Call for Participation ongoing: propose your content to share your knowledge and expertise with the other OCA members in 2025 through webinars.Deadline is on the 16th January.I wish you a happy end of 2024 and begin of 2025,
by Virginie Dewulf - 09:46 - 23 Dec 2024 -
Re: [18.0] Project Task Git integration
Hi,
We use the following modules to define a Pull Request object and update it via Github webhooks:
https://github.com/Numigi/odoo-git-addons/tree/14.0
It is in the process of being migrated to v16.
We then have a simple module (not published) that links Pull Requests in Odoo to tasks, we could open it if interested. The matching is done by looking for a task ID in Pull Request titles.
Cheers,Le dim. 15 déc. 2024 à 14:42, Francesco Ballerini <notifications@odoo-community.org> a écrit :Hi Janik, thank you so much for sharing! I took a look at the connector, and from what I can see, it allows to sync repositories in your local environment by providing terminal access directly within the Odoo interface, along with some useful shortcuts and pre-configured commands. It's an interesting approach, and I might draw some inspiration from it.For this task in particular I was especially interested in automatizing commit and pull requests behaviour by using git webhooks, and today I succeded setting up an environment to debug and extend the PR posted by Alan. It took me a while since I had to find a way to test webhooks with a localhost (never did it before), I finally succeded with a pretty simple Ngrok tunneling configuration.I take the opportunity to keep you update, at the moment my "roadmap" is:with the module webhook_gitlab that Alan provided in https://github.com/OCA/project/pull/13901 - setting up a developement environment in order to be able to debug, test, analyze code, extend the module on the version it was designed for (17.0) -- Done2 - extend "webhook_gitlab" module to incorporate desired behaviour, which is at least a sync of the commit history (and maybe pull requests) linked to a task providing a list with links to the task related commits.I'll share some notes on this step: as a general idea a commit should automatically be linked to the project task (when "push event webhook" triggers) if the commit message contains the name of any "project.task" from the Odoo Project linked with the repo where the push event triggered.E.g. I have Odoo Project named "Project X" linked to https://github.com/MyOrganization/ProjectX GitHub repo. When I push a commit into ProjectX GitHub repository I will notify Odoo server by setting a webhook that calls webhook processing controller . We should add a structured push processing method (at the moment only merging is processed I think) that compare every "project.task" name related to ProjectX and check if "project.task" name is found in the commit message. In that case the commit ID should be stored in a git.commit (new) model related to the project task and will be used to build a clickable url which is probably stored in a computed field. There should probably also be a commit resync button. -- TODO, doesn't seem too hard, but will require some time to be done.3 - when the functionality will be working on 17.0 I will migrate it on the 18.0 version (which is the version I need to work with this feature). The migration should not be hard in this case since most of the code will be methods to process github webhook requests and simply store some data in models, there shouldn't be huge changes in the code -- TODOI plan to proceed with these steps over the next few weeks. If you have any recommendations, please feel free to share them. I believe the hardest part for me will be writing tests, as I'm not very familiar with it. Thankfully, I think I’ll find substantial help in https://github.com/OCA/interface-github/tree/16.0/github_connectorIl giorno gio 12 dic 2024 alle ore 10:18 Janik von Rotz <notifications@odoo-community.org> ha scritto:Hi Francesco, I have developed a module to manage git repositories: https://github.com/Mint-System/Odoo-Apps-Connector/tree/16.0/git_base And here are the docs: https://www.odoo-wiki.org/git-base.html I will eventually develop a "project_git" module that connects projects with git repos and supports creating feature branches from tasks. All Mint System modules live up to the OCA standards. Cheers, Janik On 12/6/24 6:48 PM, Francesco Ballerini wrote: > Hi, > > we're looking for an Odoo 18 project task git integration. > > Specifically we need the feature that allows linking PR and commits to > the task by branch name/commit name containing the name of the task, > basically like Atlassian/Jira git integration. > > If you have any open source resource to provide as example we we might > try to migrate it to version 18.0. > > Thanks > > --Francesco Ballerini > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > -- We are hiring: https://www.mint-system.ch/jobs Send application to: jobs@mint-system.ch CTO Mint System GmbH Tel: +41 44 244 7222
_______________________________________________
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
--
Quentin Lavallée-BourdeauChargé de projets+1 514-317-7944
Nouveau
Essayez l'IA OpenSource pendant 30 joursDécouvrir
by Quentin Lavallée-Bourdeau - 02:41 - 20 Dec 2024 -
Re: OCA Codesprint - around FOSDEM - are you keen?
Hello Peter,Yes, we are planning the Thursday/Friday 30th Jan/31st Jan before FODSEM.We are just confirming the venue and will be ready to share the details in the next week or so!Merry Christmas to you.RebeccaOn Fri, 20 Dec 2024 at 09:12, Peter Niederlag <notifications@odoo-community.org> wrote:
Hi, is there any result from this discussion? Well, at least I have now planned a trip to Brussels :-> So count me in for some OCA-Booth at the Fosdem and I'd be happy to join some codesprint as well. best regards, Peter On 26.11.24 01:27, Rebecca Gellatly wrote: > Hello OCA Contributors, > You may have seen on our social media that we are weighing up if there is enough interest to organise an OCA Codesprint around the FOSDEM event [1] next year. > If this is something that is of interest to you, please let us know on our survey here. [2] Depending on interest we will make a decision about what to do. > The FOSDEM event [3] is on the 1st and 2nd of February in Brussels. We are considering a sprint a day or two on either side. > Have a great week. Rebecca > -- > Rebecca Gellatly General Secretary *Odoo Community Association* > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [4] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [5] > > > > [1] https://fosdem.org/2025/ > [2] https://odoo-community.org/survey/start/21bbf780-379b-48e8-ae0b-0c9e01da8be1 > [3] https://fosdem.org/2025/ > [4] https://odoo-community.org/groups/contributors-15 > [5] 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
--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 04:06 - 20 Dec 2024 -
Re: OCA Codesprint - around FOSDEM - are you keen?
Hi, is there any result from this discussion? Well, at least I have now planned a trip to Brussels :-> So count me in for some OCA-Booth at the Fosdem and I'd be happy to join some codesprint as well. best regards, Peter On 26.11.24 01:27, Rebecca Gellatly wrote: > Hello OCA Contributors, > You may have seen on our social media that we are weighing up if there is enough interest to organise an OCA Codesprint around the FOSDEM event [1] next year. > If this is something that is of interest to you, please let us know on our survey here. [2] Depending on interest we will make a decision about what to do. > The FOSDEM event [3] is on the 1st and 2nd of February in Brussels. We are considering a sprint a day or two on either side. > Have a great week. Rebecca > -- > Rebecca Gellatly General Secretary *Odoo Community Association* > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [4] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [5] > > > > [1] https://fosdem.org/2025/ > [2] https://odoo-community.org/survey/start/21bbf780-379b-48e8-ae0b-0c9e01da8be1 > [3] https://fosdem.org/2025/ > [4] https://odoo-community.org/groups/contributors-15 > [5] https://odoo-community.org/groups?unsubscribe >
by Peter Niederlag - 09:06 - 19 Dec 2024 -
Re: [Odoo CE 17.0] Fields related to custom fields don't save any values
Hi Redes,Could you try to set read-only attribute to False on the fields of product.measures ?Le ven. 13 déc. 2024, 09:07, Redes Sociales JLBBERP <notifications@odoo-community.org> a écrit :Hello Houssine,Of course, I'm sending you the link to the custom code in GitHub:The custom code is inside the "models" folder.Best regards.El 12/12/2024 15:17 CET Houssine BAKKALI <notifications@odoo-community.org> escribió:Hi,Could you show the custom code to allow us to have a better view of what you did ?Don't hesitate to put your question on the odoo forum and share the link with us.Regards,Houssine
Le mar. 10 déc. 2024, 10:58, Redes Sociales JLBBERP <notifications@odoo-community.org> a écrit :Hello Jesus,I don't fully understand what you mean by "add the name field in the module". Do you mean giving the module a name field like "_name="product.example""?El 10/12/2024 10:32 CET Jesus Sokamby <notifications@odoo-community.org> escribió:Hi, there,
I suggest you add the name field in the model and also the security/ir.model.access.csv file in the module.
Le mar. 10 déc. 2024 à 10:08, Francesco Ballerini <notifications@odoo-community.org> a écrit :Hello, add parameter `store=True` on those related fields. Update module after it.Regards--Francesco Ballerini
Il giorno mar 10 dic 2024 alle ore 09:38 Redes Sociales JLBBERP <notifications@odoo-community.org> ha scritto:Hello everyone,I am writing this message because I need help with making fields related to custom fields store values into the database.Some days ago, I made a custom model through Python called "product_measures", which is inside a model called "product_dimension". Said model not only has three Many2one fields, each one for the product's measures, but is also inside another model of "product_dimension" called "product_template", which has the same fields but with the related field section and different names. The problem is that whenever I write anything on the fields, it doesn't save anything. Also, I'm trying to make it so every value that is created and is a number is converted into a Float.I'm sending the module in a zip file because I have been stuck with this problem for quite some time, and I would like to solve this problem as soon as possible.Thanks in advance for anyone who answers.Best regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Houssine BAKKALI - 04:11 - 19 Dec 2024 -
RE: [Odoo CE 17.0] Fields related to custom fields don't save any values
Dear,
You use many2one field. That are pointers to an record in a different model. See https://www.odoo.com/documentation/18.0/developer/reference/backend/orm.html#fields. In this field, odoo stores an ID of the related record in the different model. Here you define a link to the same model. I guess you better use basic fields than. So make product_measures_length = fields.Integer(“Largo”). Now you can store a length as 100 in this field. I guess a field name length is sufficient. In an other model, you can reference your field as product.measures.lenght. Now you need product.measures.product_measures_length…
With kind regards,
Van Hirtum Johan
Van: Redes Sociales JLBBERP [mailto:notifications@odoo-community.org]
Verzonden: donderdag 19 december 2024 10:02
Aan: Contributors
Onderwerp: Re: [Odoo CE 17.0] Fields related to custom fields don't save any valuesHello everyone,
Since my first message related to the problem seen in the title, I made some progress, but I'm still not able to store values on the custom fields.
But recently, thanks to another OCA addon I had installed in the odoo server, I noticed that the only thing I needed to store the values is just the custom model (which is called "product.measures"), so I don't need to create custom fields inside the custom model, because they are already created outside the custom model.
To sum up, I will reupload the link to my company's GitHub repository, which has been recently updated, so anyone can see the module I modified:
Any help is appreciated, because right now, I'm in a "stand-by" situation.
Best regards
El 13/12/2024 9:04 CET Redes Sociales JLBBERP <redes_sociales@jlbberp.com> escribió:
Hello Houssine,
Of course, I'm sending you the link to the custom code in GitHub:
The custom code is inside the "models" folder.
Best regards.
El 12/12/2024 15:17 CET Houssine BAKKALI <notifications@odoo-community.org> escribió:
Hi,
Could you show the custom code to allow us to have a better view of what you did ?
Don't hesitate to put your question on the odoo forum and share the link with us.
Regards,
Houssine
Le mar. 10 déc. 2024, 10:58, Redes Sociales JLBBERP <notifications@odoo-community.org> a écrit :
Hello Jesus,
I don't fully understand what you mean by "add the name field in the module". Do you mean giving the module a name field like "_name="product.example""?
El 10/12/2024 10:32 CET Jesus Sokamby <notifications@odoo-community.org> escribió:
Hi, there,
I suggest you add the name field in the model and also the security/ir.model.access.csv file in the module.Le mar. 10 déc. 2024 à 10:08, Francesco Ballerini <notifications@odoo-community.org> a écrit :
Hello, add parameter `store=True` on those related fields. Update module after it.
Regards
--Francesco Ballerini
Il giorno mar 10 dic 2024 alle ore 09:38 Redes Sociales JLBBERP <notifications@odoo-community.org> ha scritto:
Hello everyone,
I am writing this message because I need help with making fields related to custom fields store values into the database.
Some days ago, I made a custom model through Python called "product_measures", which is inside a model called "product_dimension". Said model not only has three Many2one fields, each one for the product's measures, but is also inside another model of "product_dimension" called "product_template", which has the same fields but with the related field section and different names. The problem is that whenever I write anything on the fields, it doesn't save anything. Also, I'm trying to make it so every value that is created and is a number is converted into a Float.
I'm sending the module in a zip file because I have been stuck with this problem for quite some time, and I would like to solve this problem as soon as possible.
Thanks in advance for anyone who answers.
Best regards.
Fout! Bestandsnaam niet opgegeven.
_______________________________________________
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?unsubscribeFout! Bestandsnaam niet opgegeven.
_______________________________________________
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 johan - 12:41 - 19 Dec 2024 -
Re: [Odoo CE 17.0] Fields related to custom fields don't save any values
Hello everyone,Since my first message related to the problem seen in the title, I made some progress, but I'm still not able to store values on the custom fields.But recently, thanks to another OCA addon I had installed in the odoo server, I noticed that the only thing I needed to store the values is just the custom model (which is called "product.measures"), so I don't need to create custom fields inside the custom model, because they are already created outside the custom model.To sum up, I will reupload the link to my company's GitHub repository, which has been recently updated, so anyone can see the module I modified:Any help is appreciated, because right now, I'm in a "stand-by" situation.Best regardsEl 13/12/2024 9:04 CET Redes Sociales JLBBERP <redes_sociales@jlbberp.com> escribió:Hello Houssine,Of course, I'm sending you the link to the custom code in GitHub:The custom code is inside the "models" folder.Best regards.El 12/12/2024 15:17 CET Houssine BAKKALI <notifications@odoo-community.org> escribió:Hi,Could you show the custom code to allow us to have a better view of what you did ?Don't hesitate to put your question on the odoo forum and share the link with us.Regards,Houssine
Le mar. 10 déc. 2024, 10:58, Redes Sociales JLBBERP <notifications@odoo-community.org> a écrit :Hello Jesus,I don't fully understand what you mean by "add the name field in the module". Do you mean giving the module a name field like "_name="product.example""?El 10/12/2024 10:32 CET Jesus Sokamby <notifications@odoo-community.org> escribió:Hi, there,
I suggest you add the name field in the model and also the security/ir.model.access.csv file in the module.
Le mar. 10 déc. 2024 à 10:08, Francesco Ballerini <notifications@odoo-community.org> a écrit :Hello, add parameter `store=True` on those related fields. Update module after it.Regards--Francesco Ballerini
Il giorno mar 10 dic 2024 alle ore 09:38 Redes Sociales JLBBERP <notifications@odoo-community.org> ha scritto:Hello everyone,I am writing this message because I need help with making fields related to custom fields store values into the database.Some days ago, I made a custom model through Python called "product_measures", which is inside a model called "product_dimension". Said model not only has three Many2one fields, each one for the product's measures, but is also inside another model of "product_dimension" called "product_template", which has the same fields but with the related field section and different names. The problem is that whenever I write anything on the fields, it doesn't save anything. Also, I'm trying to make it so every value that is created and is a number is converted into a Float.I'm sending the module in a zip file because I have been stuck with this problem for quite some time, and I would like to solve this problem as soon as possible.Thanks in advance for anyone who answers.Best regards._______________________________________________
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 Alejandro Párraga Alcázar - 10:01 - 19 Dec 2024 -
Re: "The plan" to help non technical to contribute documentation on OCA modules
seedsBest regards,
Ivan Sokolov
Cetmix Odoo Solutionscetmix.com 
This message is sent using Mail Messages Easy app ----- Original message -----
Date: Dec 18, 2024, 9:12:51 PM
From: Notifications
Subject: Re: "The plan" to help non technical to contribute documentation on OCA moduleshttps://www.odoo.com/event/odoo-experience-2024-4662/track/test-odoo-ui-with-tours-6320 will be best 10 minutes of your odoo lifeOn Thu, Dec 19, 2024 at 2:16 AM Adam Heinz <notifications@odoo-community.org> wrote:_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Powered by Messages Easy Pro
by "Ivan Sokolov via Cetmix OÜ" <team@cetmix.com> - 10:40 - 18 Dec 2024 -
Re: "The plan" to help non technical to contribute documentation on OCA modules
https://www.odoo.com/event/odoo-experience-2024-4662/track/test-odoo-ui-with-tours-6320 will be best 10 minutes of your odoo lifeOn Thu, Dec 19, 2024 at 2:16 AM Adam Heinz <notifications@odoo-community.org> wrote:We've attempted to go this route ourselves, but have struggled to make our less technical users self-sufficient in tour creation. Is recording tours a new feature of a recent version of Odoo?On Wed, Dec 18, 2024 at 6:13 AM Graeme Gellatly <notifications@odoo-community.org> wrote:For me the fastest way to document most OCA modules AND have them apply across versions AND have them always current is to use tours which can now simply be recorded, exported, played and could apply per version, I am asking my team to do that for everything now. It not only has the benefit of allowing the user a guided how to of how to use the module, but it also becomes a test across versions and actually makes reviewing PR's easier. IOW, your documentation (tour in this case) becomes part of your test suite. Your test suite becomes part of documentation. Because every version would have its own tour, then you just need to click the version in whatever service/website. You can link whatever version to runboat to try the tour._______________________________________________
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 - 09:11 - 18 Dec 2024 -
Re: demo data and tests
Hello,
On my projects I try to use demo data for master data, for the following reasons:
- It results in code that is more readable.
- I disagree that creating object in the fixture makes it easier to ensure tests are simple. It's much simpler to include a «self.data_name = self.env.ref("")» statement in the fixture that to include a full create({}) call, which often requires the programmer to specify fields that have nothing to do with the features being tested (like the object's name, etc).
- Simple code make it easier to avoid creating a common
setUpClass() method for every testcase in a module, which WILL
have unintended consequences when you need to test some novel
codepath that depends on some flags.
- Small setup differences that a testcase may need can be encoded in instructions following the «self.data_name = self.env.ref("")» statement, like this:
- self.bank_journal_01 = self.env.ref("account_bugfixes.demo_bank_journal_01")
- self.bank_journal_01.code = "MYCODE01"
- Makes it easier to compare fixtures used in unrelated tests,
seeing in what they defer, etc.
- I disagree that not depending on demo data makes it easier to ensure tests will run no matter how demo data might be touched by other modules. Invariants about fixture, in my opinion, must be enforced by including additional tests that assert that the test data begins as expected. Also, it's a design principle that new modules must not break existing functionality, and so must happen for demo data (i.e. in general, one should avoid patching existing demo records in dependencies).
- Tests that depend on demo data also run faster, because demo data is created only once.
This is my opinion.
João Jerónimo
Às 15:52 de 12/12/2024, Raphaël Valyi escreveu:
Hello Odoo community,
More and more the OCA contributors avoid writing tests which depend on demo data and so does Odoo SA. This makes it easier to ensure tests are simple and will run no matter how demo data might be touched by other modules.
But eventually this could bring other benefits such as the ability to run these standard tests in the CI with production database dumps (that is where the demo data cannot be loaded in general).
In this case, I have a first question: probably some customization's might add required fields. What would be the best practice to be able to run these "native" or OCA tests that might fail to create records with such new constraints? We could imagine some monkey patches and standard hooks to help... We kind of face this already today by running tests with all repo modules installed, but with production dumps, much more modules would be installed together along with some non OCA customization which also need to be developed more cheaply...
But more important is my second question: if we set it as a good practice that OCA tests shouldn't depend on demo data, why are we still running the OCA CI with demo data enabled (still the case with Odoo 18 CI) ? Or is it planned we stop doing this in Odoo 19? I mean we could also save a good deal of server resources/time by not loading the gazillions of catchy Odoo CE demo data in each test run...
Thank you very much for your answers.
--
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 j_j_b_o_devel - 03:16 - 18 Dec 2024
