Archives
Contributors
-
Re: Apply to community PSC
Hola, +1 :)On Wed, Dec 29, 2021 at 1:47 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:Hi all,I want to request your approval to be part of the community PSC, which is in charge of OCA infrastructure and stuff like CI, for me and my colleague Joao, as we both intervene in these processes and can contribute with quick reactions over some events like the one happened yesterday.Thanks.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi - 02:01 - 29 Dec 2021 -
Re: Apply to community PSC
+1El mié, 29 dic 2021 a las 13:47, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:Hi all,I want to request your approval to be part of the community PSC, which is in charge of OCA infrastructure and stuff like CI, for me and my colleague Joao, as we both intervene in these processes and can contribute with quick reactions over some events like the one happened yesterday.Thanks.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Valentín Vinagre Urteaga
CTO
Sygel Technology S.L
+34 662 68 78 95 
valentin.vinagre@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Valentín Vinagre - 01:55 - 29 Dec 2021 -
Re: Apply to community PSC
+1El mié, 29 dic 2021 a las 13:47, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:Hi all,I want to request your approval to be part of the community PSC, which is in charge of OCA infrastructure and stuff like CI, for me and my colleague Joao, as we both intervene in these processes and can contribute with quick reactions over some events like the one happened yesterday.Thanks.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41 harald.panten@sygel.es https://www.sygel.es C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Harald Panten Lopez - 01:55 - 29 Dec 2021 -
Re: Apply to community PSC
Ofcourse +1.On Wed, Dec 29, 2021 at 6:17 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:Hi all,I want to request your approval to be part of the community PSC, which is in charge of OCA infrastructure and stuff like CI, for me and my colleague Joao, as we both intervene in these processes and can contribute with quick reactions over some events like the one happened yesterday.Thanks.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Technology Services @ www.serpentcs.comBusiness Solutions @ www.serpentcs.inEnterprise Mobile Apps @ www.odooonline.comQuality Assurance @ www.odooqa.comSAP Hana @ www.prozone-tech.comPortal & DMS @ www.alfray.inRegards,----------------------------------------------------------------------------------------------------------------------------Jay Vora Managing Director 
Direct: +91-9879354457 Office: +91-9033472982 Skype: jaynvora Twitter : jaynvora -------------------------------------------------------------------------------------------------
Visit our website : http://www.serpentcs.com
by Jay Vora - 01:51 - 29 Dec 2021 -
Apply to community PSC
Hi all,I want to request your approval to be part of the community PSC, which is in charge of OCA infrastructure and stuff like CI, for me and my colleague Joao, as we both intervene in these processes and can contribute with quick reactions over some events like the one happened yesterday.Thanks.Regards.
by Pedro M. Baeza - 01:45 - 29 Dec 2021 -
Re: Boolean grouped line label
I don't know any about that, but for me it hasn't been something annoying.Regards.
by Pedro M. Baeza - 03:51 - 24 Dec 2021 -
Boolean grouped line label
Hi there,Do you know any module to improve the display of the grouped lines on a boolean field ?In the following example I'd like to see "Active: Yes (5)" (or "Active: True (5)" where true can be translated) instead of "true (5)".If not, I'm thinking of creating a new PR on the web repo which could be named web_boolean_group_label.Your comments are appreciated !Regards,
--
by Pierre Verkest - 02:36 - 24 Dec 2021 -
Re: oca/oca.recipe.odoo repository?
> Could somebody with the appropriate permissions make the settings accessible > to the maintainers (StefanRijnhart+hbrunn at the moment)? > Currently permissions are managed via a GitHub team sync script, from the > PSC members database. The current policy is that only PSC representatives > and board have admin access to the repos. I'm not sure it still makes sense > for tooling repos such as this one, but it's the way it is now. I gave you > access, but it may only last until the team sync script kicks in again. thanks Stéphane, I changed the bits that need changing currently, so it won't be super problematic if we lose access again. > Generally, who is the address to ask about OCA github permission stuff? I > try to avoid asking Alexandre about everything. > I guess it's support@odoo-community.org [3] , but it will mostly end up with > Alexandre and myself anyway ;) That's also something we'll need to work on, > i.e. manage the bus factor for the OCA infrastructure. Cheers, indeed, that's an important one. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 11:30 - 22 Dec 2021 -
Re: oca/oca.recipe.odoo repository?
we're busy with this currently, but don't have access to the settings tab of https://github.com/OCA/oca.recipe.odoo Could somebody with the appropriate permissions make the settings accessible to the maintainers (StefanRijnhart+hbrunn at the moment)?
Currently permissions are managed via a GitHub team sync script, from the PSC members database.The current policy is that only PSC representatives and board have admin access to the repos.I'm not sure it still makes sense for tooling repos such as this one, but it's the way it is now.I gave you access, but it may only last until the team sync script kicks in again.Generally, who is the address to ask about OCA github permission stuff? I try to avoid asking Alexandre about everything.
I guess it's support@odoo-community.org, but it will mostly end up with Alexandre and myself anyway ;)That's also something we'll need to work on, i.e. manage the bus factor for the OCA infrastructure.Cheers,-sbi
by Stéphane Bidoul - 11:01 - 22 Dec 2021 -
Re: oca/oca.recipe.odoo repository?
Hi all, we're busy with this currently, but don't have access to the settings tab of https://github.com/OCA/oca.recipe.odoo Could somebody with the appropriate permissions make the settings accessible to the maintainers (StefanRijnhart+hbrunn at the moment)? Generally, who is the address to ask about OCA github permission stuff? I try to avoid asking Alexandre about everything. Thanks in advance, Holger -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 10:45 - 22 Dec 2021 -
Re: Move purchase_request* and purchase_work_acceptance*
We can use readme to store this information. One file, all the info.Il giorno mar 21 dic 2021 alle ore 13:32 Yann Papouin <ypa@decgroupe.com> ha scritto:As I was in that case, why not creating a file with the same name for each moved module with a text content:Module moved to repository xxxxx--
Yann PAPOUIN, Ingénieur R&D | DECLe mar. 21 déc. 2021 à 11:27, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Now that having a lot of runboat instances is not too much of a problem, I think it's better to split the maximum repos for smaller sets of modules, so I will go to all of them that we are talking about. Reducing the number of them will:- Avoid potential conflicts between them.- Reduce tests size.On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.
by Francesco Apruzzese - 02:01 - 21 Dec 2021 -
Re: Move purchase_request* and purchase_work_acceptance*
El mar, 21 dic 2021 a las 13:32, Yann Papouin (<ypa@decgroupe.com>) escribió:As I was in that case, why not creating a file with the same name for each moved module with a text content:Module moved to repository xxxxxIn my experience, that's more maintenance burden on our part with no reward because people still don't look.Regards.
by Pedro M. Baeza - 01:41 - 21 Dec 2021 -
Re: Move purchase_request* and purchase_work_acceptance*
As I was in that case, why not creating a file with the same name for each moved module with a text content:Module moved to repository xxxxx--
Yann PAPOUIN, Ingénieur R&D | DECLe mar. 21 déc. 2021 à 11:27, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Now that having a lot of runboat instances is not too much of a problem, I think it's better to split the maximum repos for smaller sets of modules, so I will go to all of them that we are talking about. Reducing the number of them will:- Avoid potential conflicts between them.- Reduce tests size.On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Yann Papouin - 01:31 - 21 Dec 2021 -
Re: Move purchase_request* and purchase_work_acceptance*
I agree with Pedro.The amount of modules is not the only factor to take into account.The aim of a repository is also to group functionally modules that do 'quite' the same things and has a specific meaning (I don't like *-workflow stuff as it is too generic - @kitti don't create purchase-extra-workflow as it adds abstraction and has no meaning).To find modules, we have our shop that leads to the good repository (we maybe need to do marketing on this)On Tue, Dec 21, 2021 at 11:27 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:Now that having a lot of runboat instances is not too much of a problem, I think it's better to split the maximum repos for smaller sets of modules, so I will go to all of them that we are talking about. Reducing the number of them will:- Avoid potential conflicts between them.- Reduce tests size.On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
by Denis Roussel - 11:50 - 21 Dec 2021 -
Re: Move purchase_request* and purchase_work_acceptance*
Hi,I don't have a strong opinion on this one, if you want to split purchase-workflow, I'm fine with that.For me the real problem, and to bring another consideration to the table, are the repos with "rebel" addons that forces you to have multiple pipelines with some addons excluded and other with them included, it happens often that a contributor ends having to fix other modules tests when you opening a new PR of a new module. This happens in purchase-workflow but also in sale-workflow.Regards,El mar, 21 dic 2021 a las 11:27, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:Now that having a lot of runboat instances is not too much of a problem, I think it's better to split the maximum repos for smaller sets of modules, so I will go to all of them that we are talking about. Reducing the number of them will:- Avoid potential conflicts between them.- Reduce tests size.On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Lois Rilo AnteloOdoo consultant at ForgeFlow S.L.
by Lois Rilo Antelo - 11:46 - 21 Dec 2021 -
Re: Move purchase_request* and purchase_work_acceptance*
Now that having a lot of runboat instances is not too much of a problem, I think it's better to split the maximum repos for smaller sets of modules, so I will go to all of them that we are talking about. Reducing the number of them will:- Avoid potential conflicts between them.- Reduce tests size.On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.Regards.
by Pedro M. Baeza - 11:26 - 21 Dec 2021 -
Re: Move purchase_request* and purchase_work_acceptance*
I don't think purchase-workflow has too many modules, but if it slows down runbots and CI we could split it.
What about moving all modules whose features are previous to an RFQ/Purchase creation, to a repo called..., for instance,
purchase-procurement
Or a more convenient repo name
Regards,El mar, 21 dic 2021 a las 11:06, Kitti U. (<kittiu@ecosoft.co.th>) escribió:Hi,1) reduce purchase-workflow sizepurchase_request and purchase_work_acceptance each has now 4-5 modules each, and they shouldn't grow more than that. They both "extra" documents to standard purchase order. Should both be together 1 repo, i.e., purchase-extra-workflow?2) I think tier-validation deserves its own repo. There are 19 related modules now. Similar to operating-unit.On Tue, Dec 21, 2021 at 3:41 PM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:+1On Fri, Dec 17, 2021 at 9:12 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:+1 to split purchase_workflow.Le mar. 14 déc. 2021 à 11:52, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :+1, although maybe others can be more useful, like OCA/tier-validation, that groups better other functional areas._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDepartment HeadBusiness Solutions_______________________________________________
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
--Héctor Villarreal OrtegaTechnical Consultanttwitter: /h_vior | Linkedin: /hectorvior
The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.
by Héctor Villarreal Ortega - 11:16 - 21 Dec 2021 -
Re: Move purchase_request* and purchase_work_acceptance*
Hi,1) reduce purchase-workflow sizepurchase_request and purchase_work_acceptance each has now 4-5 modules each, and they shouldn't grow more than that. They both "extra" documents to standard purchase order. Should both be together 1 repo, i.e., purchase-extra-workflow?2) I think tier-validation deserves its own repo. There are 19 related modules now. Similar to operating-unit.On Tue, Dec 21, 2021 at 3:41 PM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:+1On Fri, Dec 17, 2021 at 9:12 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:+1 to split purchase_workflow.Le mar. 14 déc. 2021 à 11:52, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :+1, although maybe others can be more useful, like OCA/tier-validation, that groups better other functional areas._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDepartment HeadBusiness Solutions_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Kitti Upariphutthiphong - 11:05 - 21 Dec 2021 -
Re: Move purchase_request* and purchase_work_acceptance*
+1On Fri, Dec 17, 2021 at 9:12 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:+1 to split purchase_workflow.Le mar. 14 déc. 2021 à 11:52, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :+1, although maybe others can be more useful, like OCA/tier-validation, that groups better other functional areas._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDepartment HeadBusiness Solutions
by Joël Grand Guillaume - 09:41 - 21 Dec 2021 -
Re: Odoo 14 bank statement reconciliation
One more point I don't like is that it doesn't behave the same if you pay the invoice from statement or you make payment before:A) Paying from invoice:1) one payment with journal entry for the payment2) one more entry on the statement when reconciling.B) paying an invoice directly from the statement:1) only one journal entry (not payment) created.So actually, if you use payment menus you will only find payment that were done there but not the ones created from statements.El vie, 17 dic 2021 a la(s) 10:47, Kitti U. (kittiu@ecosoft.co.th) escribió:Hi Jordi,Yes, I think the same with you, https://twitter.com/kittiup/status/1315301997810130944Our accountant freakouts everytime this kind of thing happens. For our accounting standard, journal entries must not change once posted.I was learning from Odoo that, many countries don't take it seriously like we do. But this just make Odoo looks bad for auditors.On Thu, Nov 25, 2021 at 2:16 PM Jordi Ballester Alomar <jordi.ballester@forgeflow.com> wrote:Hello,I hope this email finds you well. Today I was stuck with the way Odoo handles the bank statement reconciliation in v14 and saw Frederic's tweet from a year ago: https://twitter.com/Frederic_C2C/status/1313521444106706944What really stuck me is not the use of a suspense account during the bank reconciliation, but the fact that once the bank statement line journal entry has been posted to a suspense account, the posted journal entry is modified once you have matched that statement line with an invoice. Changing a posted journal entry??What do you think?--Jordi Ballester AlomarCEO & FounderSpain: (+34) 629 53 07 07 | USA: (+1) 646 980 46 59 | Denmark: (+45) 78 78 21 89
The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future._______________________________________________
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 Juan José Scarafía - 09:00 - 17 Dec 2021
