Skip to Content

Contributors

  • Re: Mail cc

    Le mar. 1 déc. 2020 à 12:02, Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> a écrit :
    I agree.

    Antonio M. Vigliotti

    Mobile (+39) 342.8740910



    Il 01/12/20 10:47, Sergio Corato ha scritto:
    Hi all,

    AFAIK there isn't a generic approach to send mail with CC instead of A, or I miss something?

    The use case would be something like: if a mail is sent to 1 recipient, go with A. If there are multiple recipients, 1 go with A and the other with CC.

    So an 'integrated' logic, without user intervention (except to optionally change the A recipient, or something other).

    Thanks in advance!

    Sergio Corato

    _______________________________________________
    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 Raphaël Reverdy - 03:41 - 1 Dec 2020
  • Advanced(?) use of calendar view in 13.0

    Hello,

     

    we use calendar view for displaying project tasks using color="user_id" - standard thing. However we have created an additional field on project.task that is Many2one reference to assistant (a second guy that participates in the task).

     

    Now I would like to achieve these 2 things but no amount of searching helped me in any way:

     

    1) When selecting a user_id checkobox on the right be able to display also tasks where that user is an assistant. Is it possible somehow?

     

    2) Cutomize the content of the entry (task) box. It only shows name, all the configured attributes appear in that popup box tha tappears on the click like this:

    Whereas in 12.0 you had all the information inside the box:

     

    Can I achieve something similar? I want to have additional visual information present on the record, not just name.

     

    Thank you very much. Best regards

     

    Radovan Skolnik


    by Radovan Skolnik - 12:55 - 1 Dec 2020
  • Re: Mail cc
    I agree.

    Antonio M. Vigliotti

    Mobile (+39) 342.8740910



    Il 01/12/20 10:47, Sergio Corato ha scritto:
    Hi all,

    AFAIK there isn't a generic approach to send mail with CC instead of A, or I miss something?

    The use case would be something like: if a mail is sent to 1 recipient, go with A. If there are multiple recipients, 1 go with A and the other with CC.

    So an 'integrated' logic, without user intervention (except to optionally change the A recipient, or something other).

    Thanks in advance!

    Sergio Corato

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    by Antonio M. Vigliotti - 12:01 - 1 Dec 2020
  • Re: Mail cc
    Hello Sergio,
    
    Completely agree, when you are a follower on some PO or SO or whatever 
    Odoo document, you should be cc of the email.  This is a major drawback 
    for me, but I've never came across any solution to this issue...
    
    Even Fabien P. seems to not understand the issue for the end user.
    
    Best use case : open an issue on Odoo : https://www.odoo.com/fr_FR/help
    
    Copy some colleagues
    
    When you get an answer from Odoo, you never know if your colleagues 
    received the answer or not... So everybody starts forwarding the email 
    to everybody...
    
    Regards
    
    Vincent Regouby
    
    
    Le 01/12/2020 à 10:47, Sergio Corato a écrit :
    
    > Hi all,
    
    >
    
    > AFAIK there isn't a generic approach to send mail with CC instead of 
    
    > A, or I miss something?
    
    >
    
    > The use case would be something like: if a mail is sent to 1 
    
    > recipient, go with A. If there are multiple recipients, 1 go with A 
    
    > and the other with CC.
    
    >
    
    > So an 'integrated' logic, without user intervention (except to 
    
    > optionally change the A recipient, or something other).
    
    >
    
    > Thanks in advance!
    
    >
    
    > Sergio Corato
    
    >
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 
    
    > <https://odoo-community.org/groups/contributors-15>
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe 
    
    > <https://odoo-community.org/groups?unsubscribe>
    
    >
    

    by v.regouby - 11:31 - 1 Dec 2020
  • Mail cc
    Hi all,

    AFAIK there isn't a generic approach to send mail with CC instead of A, or I miss something?

    The use case would be something like: if a mail is sent to 1 recipient, go with A. If there are multiple recipients, 1 go with A and the other with CC.

    So an 'integrated' logic, without user intervention (except to optionally change the A recipient, or something other).

    Thanks in advance!

    Sergio Corato

    by Sergio Corato - 10:46 - 1 Dec 2020
  • Re: Decrease invoiced quantities on Sale Order when credit note validated
    Hi,

    If the credit comes from the sale then in general the sale is affected. Otherwise if it is created from the invoice it isn't.

    It is too problematic to do any other way IMO. Especially if stock is involved. I mean generally, if you follow a basic guideline for Sales depending on policy that Invoiced means Ordered = Invoiced or Delivered > 0 and Delivered = Invoiced then the relevant Credits and Invoices can always be created from the Sale using Create Invoice button there is no need and in fact it is detrimental for the Invoice Refund button to affect the sale..

    From memory the Credit Note options are something like.

    Draft Refund - very often these should have no effect on invoiced qty as they can be simply price adjustments.
    Modify - well now you have 2 problems. Because also the newly created invoice also won't affect the sale. If it is just a price adjustment similar to above then it won't matter.
    Cancel - I just can't think of a reasonable use case to reduce the sale invoiced quantity without also having to affect stock. In any case Cancel is just shorthand for Create Draft Refund -> Validate.
      If I double invoiced something and need to issue a credit note, and the sale invoiced quantities are wrong then Create Invoice in sale is the correct method.
      If goods were returned, then create refund in the return picking wizard will decrement the delivered quantities and again Create Invoice.

    On Thu, Nov 26, 2020 at 11:17 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
    I would say that it's decreased if you select option 2 or 3 of the credit note, but not on option 1 (draft refund).

    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 Graeme Gellatly - 01:26 - 30 Nov 2020
  • Re: Decrease invoiced quantities on Sale Order when credit note validated

    Thanks Pedro,

    that's also what I would have expected but none of the option lead to a decrease of invoiced quantities on sale order...

    I think this is probably because account_invoice_line(s) created on credit note from original invoice do not copy all related fields and in particular do not keep the link with sale_order_lines.
    But still I would need to workaround this behaviour !

    Has anyone solved this ? (on Odoo version 12.0 or previous ones)

    Le Filament
    Rémi CAZENAVE
    ------
    SCOP LE FILAMENT
    06.87.23.26.04
    remi@le-filament.com
    Le 26/11/2020 à 11:17, Pedro M. Baeza (Tecnativa) a écrit :
    I would say that it's decreased if you select option 2 or 3 of the credit note, but not on option 1 (draft refund).

    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 Rémi Cazenave - 12:31 - 26 Nov 2020
  • Re: Decrease invoiced quantities on Sale Order when credit note validated
    I would say that it's decreased if you select option 2 or 3 of the credit note, but not on option 1 (draft refund).

    Regards.

    by Pedro M. Baeza - 11:16 - 26 Nov 2020
  • Re: New PSC role_policy
    Hello Luc,

    I have created the repo https://github.com/OCA/role-policy

    Please feel free to transfer your modules.

    We are looking forward to start contributing!

    On Thu, Oct 15, 2020 at 8:17 PM Jay Vora <vora.jay@serpentcs.com> wrote:
    +1 for PSC members and new repo.

    On Thu, 15 Oct 2020 at 11:32 PM, Jesús Alan Ramos Rodríguez <alan.ramos@jarsa.com.mx> wrote:
    +1


    El jue., 15 de oct. de 2020 a la(s) 11:32, Kitti Upariphutthiphong (kittiu@ecosoft.co.th) escribió:
    +1

    On Thu, 15 Oct 2020, 22:57 , <luc.demeyer@noviat.com> wrote:

    The Role Policy suite of modules are really completely different and will imho better be maintained via a separate PSC focusing on this game changer (until hopefully one day Odoo implenents the concepts adopted here).

     

    Regards,

    Luc

     

    From: Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com>
    Sent: Thursday, 15 October 2020 17:38
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: New PSC role_policy

     

    Shouldn't this be part of OCA/server-auth?

     

    What are the overlaps with base_user_role?

     

    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.com
    Business Solutions @ www.serpentcs.in
    Enterprise Mobile Apps @ www.odooonline.com 
    Quality Assurance @ www.odooqa.com
    Portal & DMS @ www.alfray.in



    Regards,
    ----------------------------------------------------------------------------------------------------------------------------
    Jay Vora
    Managing Director


     
    Direct: +91-9879354457
    Office: +91-9033472982
    Skype: jaynvora
    Twitter : jaynvora
       
    -------------------------------------------------------------------------------------------------
    Visit our website : http://www.serpentcs.com

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Jordi Ballester Alomar
    CEO & Founder | ForgeFlow

    by Jordi Ballester Alomar - 05:06 - 25 Nov 2020
  • Decrease invoiced quantities on Sale Order when credit note validated

    Dear all,

    I just discovered that when creating a credit note on an invoice generated from a sale order, the invoiced quantities would not decrease on sale order.

    Therefore if I need to invoice these again, I need to artificially increase delivered or ordered quantities (depending on product invoicing policy configuration), causing side effects on sales analysis.


    Has any of you find a way to workaround this issue ?


    This problem seems to be present up to v12, not anymore on v13 and v14.

    I have found https://github.com/odoo/odoo/issues/37549 on this topic but without much feedback.


    Thank you,

    Best Regards,

    --

    Le Filament
    Rémi CAZENAVE
    ------
    SCOP LE FILAMENT

    by Rémi Cazenave - 03:06 - 25 Nov 2020
  • Re: OCA rental solution and rental vertical repository request
    Olaf,

    I think something has been miscommunicated. Talk to Frederik, but as far as I knew if not approved, it was already way down that track. Better to pick that up than restart. I think the main issue was just resolving a conflict with the existing repository.



    On Wed, 25 Nov 2020, 12:47 am Olaf Wagner, <wagner@elegosoft.com> wrote:
    Hello everybody,
    
    this year we have been busy implementing a complete rental solution based
    on Odoo CE v12 and lots of OCA modules for a German customer. It is already
    in production use since July. We explicitly agreed on contributing all the
    code to the OCA, but due to COVID-19 restrictions and several personal
    complications this work was considerably delayed.
    
    We already asked in March this year for a repository to check-in
    all the code directly at OCA, but IIRC there was not much interest back
    then. Ben Brich was also involved in the design and implementation of
    parts of the code, and Frederik Kramer should know about it, too.
    
    The solution we have has been designed for a German customer business
    renting large machines and vehicles, but it should be useful for other
    lines of business as well. Considerable efforts have been invested to
    make it really useful from the pragmatic point of view of the customer.
    
    There is a short presentation video at Youtube:
    --> https://www.youtube.com/watch?v=CzO5NqgJWD0
    
    Currently we've got 31 modules for rental extensions and 3 for shipment
    extensions based on a module that was present on Odoo v8:
    
    rental_base/
    rental_contract/
    rental_contract_insurance/
    rental_contract_month/
    rental_contract_toll_collect/
    rental_forward_shipment_plan/
    rental_loan/
    rental_menu_crm/
    rental_offday/
    rental_pricelist/
    rental_product_instance/
    rental_product_instance_appointment/
    rental_product_instance_repair/
    rental_product_insurance/
    rental_product_pack/
    rental_product_set/
    rental_product_variant/
    rental_purchase_order_type/
    rental_quality_control/
    rental_repair/
    rental_reporting/
    rental_routing/
    rental_sale/
    rental_timeline/
    rental_timeline_offday/
    rental_timeline_product_instance/
    rental_timeline_product_instance_appointment/
    rental_timeline_product_variant/
    rental_timeline_repair/
    rental_timeline_transport/
    rental_toll_collect/
    
    shipment_plan/
    shipment_plan_rental/
    shipment_plan_sale/
    
    Base for the work is the module sale_rental from the sale-workflow
    repository; it has been renamed in our code as rental_sale with some
    slight modifications in order to avoid conflicts when using code from
    both repositories. All other rental modules above are new.
    
    We've synchronized the code to a Github repository now at
    https://github.com/elego/rental-vertical/tree/v12 where you can inspect
    it. It is still missing some documentation and the test coverage is only
    at 73% so there is still room for improvements. We're going to continue
    to work on that, but would also like your opinions an comments on
    everything.
    
    We're using the v12 branch as internal integration branch there and
    could merge from there to an 'official' 12.0 branch now and then.
    
    The structure of everything should be according to the OCA conventions
    as far as we know and understand them; some adaptations may of course
    be necessary.
    
    Please let us know how to proceed with contributing this code to the
    OCA. I think it should be fit at least for an alpha-status in a new
    repo.
    
    Greetings from Berlin,
    
    Olaf
    
    
    -- 
    Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com 
                   Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
    Geschäftsführer: Olaf Wagner | Sitz: Berlin
    Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
    

    _______________________________________________
    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 - 07:41 - 24 Nov 2020
  • Re: Issues with Travis
    Thanks for the lightning-fast resolution!

    Too bad we didn't get the renewable OSS only credits (https://docs.travis-ci.com/user/billing-overview/#credits-vs-oss-only-credits).
    Looking forward to the global switch to Github actions

    On Tue, 24 Nov 2020 at 14:42, David Beal <david.beal@akretion.com> wrote:
    +1

    Bonne journée


    David BEAL - akretion.com
    Consultant
    Odoo Intégration / Développement


    Le mar. 24 nov. 2020 à 14:36, Raphaël Valyi <rvalyi@akretion.com> a écrit :
    I got another idea:

    why not just simply test using Odoo on odd days and on OCB on even days?

    Given the very low discrepancies between OCB and Odoo today, it could be a nice trade off between detecting OCB regressions and doing half the test load we do today.
    What do you think? If you think it's a good idea I volunteer to change the test scripts for doing it.


    On Tue, Nov 24, 2020 at 8:51 AM Raphaël Valyi <rvalyi@akretion.com> wrote:


    On Tue, Nov 24, 2020, 7:06 AM David Beal <david.beal@akretion.com> wrote:
    Hi all,

    [...]

    If we could reduce these by 2, environmental impact will be reduced by 2
    Ci tests:
    - OCB
    - odoo

    What about testing OCB (or Odoo) only once day per week or something like that? (say unless some special variable to force the test is set).

    I think it is easy to do in the test script and it could probably be an acceptable trade off to detect compatibility issues soon often without doubling the number of builds all the time. What do you think?

    Raphaël.

    _______________________________________________
    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 Valyi
    Founder 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

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Simone Rubino - 04:11 - 24 Nov 2020
  • Re: Issues with Travis
    +1

    Bonne journée


    David BEAL - akretion.com
    Consultant
    Odoo Intégration / Développement


    Le mar. 24 nov. 2020 à 14:36, Raphaël Valyi <rvalyi@akretion.com> a écrit :
    I got another idea:

    why not just simply test using Odoo on odd days and on OCB on even days?

    Given the very low discrepancies between OCB and Odoo today, it could be a nice trade off between detecting OCB regressions and doing half the test load we do today.
    What do you think? If you think it's a good idea I volunteer to change the test scripts for doing it.


    On Tue, Nov 24, 2020 at 8:51 AM Raphaël Valyi <rvalyi@akretion.com> wrote:


    On Tue, Nov 24, 2020, 7:06 AM David Beal <david.beal@akretion.com> wrote:
    Hi all,

    [...]

    If we could reduce these by 2, environmental impact will be reduced by 2
    Ci tests:
    - OCB
    - odoo

    What about testing OCB (or Odoo) only once day per week or something like that? (say unless some special variable to force the test is set).

    I think it is easy to do in the test script and it could probably be an acceptable trade off to detect compatibility issues soon often without doubling the number of builds all the time. What do you think?

    Raphaël.

    _______________________________________________
    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 Valyi
    Founder 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 David BEAL - 02:40 - 24 Nov 2020
  • Re: Product Safety Datasheet
    Hi Alberto,

    Thanks for your contribution.

    Seems it's a generic subject.
    Maybe it could go towards OCA.

    As I have seen, you may split your models.py file by models.

    Otherwise an idea not sure that it's relevant but you could use this module

    because information of this kind is quite related to Product Information Management.

    It could avoid to manage some too many additional modules

    odoo-pim will join OCA in next weeks

    Regards

    David BEAL - akretion.com
    Consultant
    Odoo Intégration / Développement


    Le jeu. 19 nov. 2020 à 13:01, Alberto Carollo <baba75@gmail.com> a écrit :
    Hello contributors,
    I wrote a module to fill in the safety data sheets following the 16 points of the European Commission Regulation. I thought maybe it might be useful to someone.


    Any feedback or help would be appreciated.

    Ciao,
    Alberto

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by David BEAL - 02:40 - 24 Nov 2020
  • Re: Issues with Travis
    I got another idea:

    why not just simply test using Odoo on odd days and on OCB on even days?

    Given the very low discrepancies between OCB and Odoo today, it could be a nice trade off between detecting OCB regressions and doing half the test load we do today.
    What do you think? If you think it's a good idea I volunteer to change the test scripts for doing it.


    On Tue, Nov 24, 2020 at 8:51 AM Raphaël Valyi <rvalyi@akretion.com> wrote:


    On Tue, Nov 24, 2020, 7:06 AM David Beal <david.beal@akretion.com> wrote:
    Hi all,

    [...]

    If we could reduce these by 2, environmental impact will be reduced by 2
    Ci tests:
    - OCB
    - odoo

    What about testing OCB (or Odoo) only once day per week or something like that? (say unless some special variable to force the test is set).

    I think it is easy to do in the test script and it could probably be an acceptable trade off to detect compatibility issues soon often without doubling the number of builds all the time. What do you think?

    Raphaël.

    _______________________________________________
    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 Valyi
    Founder and consultant


    by "Raphaël Valyi" <rvalyi@akretion.com> - 02:36 - 24 Nov 2020
  • Re: [26699] Open Source Shift Management
    Dear All:

    Everything we do is open source, accessible for anybody who enters into and honors our bidirectional joint partner agreement.
    CampToCamp, which we perceive the source of OCA, did sign up, btw. 
    Frederik, I think you got a copy that I gave you personally. If you cant find it I am happy to resend. 

    And yes, therefore we do think this -  and other information about itiseasy.business - shall belong into this community list.
    Thanks for all who have looked into it already, we are grateful for the resonance over the last month. And we welcome anyone who is happily wanting to give it a try. 

    All the best, Joe


    Von: "frederik kramer" <frederik.kramer@initos.com>
    An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
    Gesendet: Freitag, 20. November 2020 16:21:45
    Betreff: Re: [26699] Open Source Shift Management

    Hi Joe, 
    
    thanks for the hint. As this is for a public municipality in Eastern
    Germany and mainly to organise their shifts during he Corona pandemics,
    they would like to have it full Open Source. 
    
    Is your solution Open Source and if yes where can i review / download
    the code ?
    
    If this is not or not fully Open Source please still consider DM me as
    this would certainly not be of general interest on the OCA mailing list
    then but probably still for the municipality at stake
    
    Best and have a nice weekend
    
    Frederik
    
    
    Am Freitag, den 20.11.2020, 15:07 +0000 schrieb Joerg Lorenz:
    
    
    > Hi Frederik
    
    
    > 
    
    
    > you might consider itiseasy.business for this task. We have a long
    
    
    > standing track record of hr with odoo. And as of 2020 we now have a
    
    
    > much extensive hr and shift management in place, ranging into all
    
    
    > different areas of the product, wheter it is projects, timesheets,
    
    
    > attendance, and manufacturing. 
    
    
    > 
    
    
    > If you are ready for a demo, let me know, but you are also free to
    
    
    > look into https://www.itis.de/itis-easy-business 
    
    
    > 
    
    
    > Thanks, Joe
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > Von: "frederik kramer" <frederik.kramer@initos.com>
    
    
    > An: "Odoo Community Association, (OCA) Contributors" <
    
    
    > contributors@odoo-community.org>
    
    
    > Gesendet: Freitag, 20. November 2020 15:02:46
    
    
    > Betreff: [26699] Open Source Shift Management
    
    
    > 
    
    
    > Hi folks, 
    
    
    > 
    
    
    > while looking for something pragmatic in terms of Open Source shift
    
    
    > management,  i recently came across 
    
    
    > 
    
    
    > https://edgeryders.eu/t/list-open-source-software-for-resource-scheduling-and-booking/6629
    
    
    > 
    
    
    > Even though i know Odoo has HR functions, i didn't really  took that
    
    
    > into consideration. Now that the aforementioned source mentions Odoo
    
    
    > as
    
    
    > well, i thought, ok lets give it a try. 
    
    
    > 
    
    
    > Unfortunately, i got reaffirmend why i haven't had Odoo in mind in
    
    
    > the
    
    
    > first place. This is because the suggested Odoo app "planning" is of
    
    
    > course EE (as the GANTT chart view as well). I did a quick research
    
    
    > on
    
    
    > the app store (apps.odoo.com) as well as our own (
    
    
    > https://www.odoo-code-search.com/). I found out that many apps do
    
    
    > exist
    
    
    > with the suite OpenHRMS by Cybrosys being he most prominent of
    
    
    > those. 
    
    
    > 
    
    
    > Of course i also gave the OCA repositories a glance and found that at
    
    
    > least the GANTT functions (of course also EE) are somewhat replacable
    
    
    > by CE OCA code of project_timeline. 
    
    
    > 
    
    
    > My question: Does anybody believe or know if shift management can be
    
    
    > done with only Standard Odoo CE and OCA code and has any suggestions
    
    
    > what modules to look at? Is anybody aware of any attempt of a
    
    
    > community
    
    
    > member working on this or am i really hooked and need to go for EE to
    
    
    > fulfull this requirement / develop all from scratch ;-)
    
    
    > 
    
    
    > Thank for any suitable hint on the matter in advance.
    
    
    > 
    
    
    > Best Frederik 
    
    
    > 
    
    
    > 
    
    
    > -- 
    
    
    > Dr.-Ing. Frederik Kramer
    
    
    > Geschäftsführer
    
    
    >         
    
    
    > initOS GmbH
    
    
    > An der Eisenbahn 1
    
    
    > 21224 Rosengarten
    
    
    >         
    
    
    > Phone:  +49 4105 56156-12
    
    
    > Fax:    +49 4105 56156-10
    
    
    > Mobil:  +49 179 3901819
    
    
    >         
    
    
    > Email: frederik.kramer@initos.com
    
    
    > Web:   www.initos.com
    
    
    >         
    
    
    > Geschäftsführung:
    
    
    > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    
    > 
    
    
    > Sitz der Gesellschaft: Rosengarten – Klecken
    
    
    > Amtsgericht Tostedt, HRB 205226
    
    
    > Steuer-Nr: 15/200/53247
    
    
    > USt-IdNr.: DE815580155
    
    
    > 
    
    
    > _______________________________________________
    
    
    > 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
    
    
    -- 
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    An der Eisenbahn 1
    21224 Rosengarten
            
    Phone:  +49 4105 56156-12
    Fax:    +49 4105 56156-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Rosengarten – Klecken
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    by Joerg Lorenz. - 01:31 - 24 Nov 2020
  • Re: Issues with Travis


    On Tue, Nov 24, 2020, 7:06 AM David Beal <david.beal@akretion.com> wrote:
    Hi all,

    [...]

    If we could reduce these by 2, environmental impact will be reduced by 2
    Ci tests:
    - OCB
    - odoo

    What about testing OCB (or Odoo) only once day per week or something like that? (say unless some special variable to force the test is set).

    I think it is easy to do in the test script and it could probably be an acceptable trade off to detect compatibility issues soon often without doubling the number of builds all the time. What do you think?

    Raphaël.

    by "Raphaël Valyi" <rvalyi@akretion.com> - 12:50 - 24 Nov 2020
  • OCA rental solution and rental vertical repository request
    Hello everybody,
    
    this year we have been busy implementing a complete rental solution based
    on Odoo CE v12 and lots of OCA modules for a German customer. It is already
    in production use since July. We explicitly agreed on contributing all the
    code to the OCA, but due to COVID-19 restrictions and several personal
    complications this work was considerably delayed.
    
    We already asked in March this year for a repository to check-in
    all the code directly at OCA, but IIRC there was not much interest back
    then. Ben Brich was also involved in the design and implementation of
    parts of the code, and Frederik Kramer should know about it, too.
    
    The solution we have has been designed for a German customer business
    renting large machines and vehicles, but it should be useful for other
    lines of business as well. Considerable efforts have been invested to
    make it really useful from the pragmatic point of view of the customer.
    
    There is a short presentation video at Youtube:
    --> https://www.youtube.com/watch?v=CzO5NqgJWD0
    
    Currently we've got 31 modules for rental extensions and 3 for shipment
    extensions based on a module that was present on Odoo v8:
    
    rental_base/
    rental_contract/
    rental_contract_insurance/
    rental_contract_month/
    rental_contract_toll_collect/
    rental_forward_shipment_plan/
    rental_loan/
    rental_menu_crm/
    rental_offday/
    rental_pricelist/
    rental_product_instance/
    rental_product_instance_appointment/
    rental_product_instance_repair/
    rental_product_insurance/
    rental_product_pack/
    rental_product_set/
    rental_product_variant/
    rental_purchase_order_type/
    rental_quality_control/
    rental_repair/
    rental_reporting/
    rental_routing/
    rental_sale/
    rental_timeline/
    rental_timeline_offday/
    rental_timeline_product_instance/
    rental_timeline_product_instance_appointment/
    rental_timeline_product_variant/
    rental_timeline_repair/
    rental_timeline_transport/
    rental_toll_collect/
    
    shipment_plan/
    shipment_plan_rental/
    shipment_plan_sale/
    
    Base for the work is the module sale_rental from the sale-workflow
    repository; it has been renamed in our code as rental_sale with some
    slight modifications in order to avoid conflicts when using code from
    both repositories. All other rental modules above are new.
    
    We've synchronized the code to a Github repository now at
    https://github.com/elego/rental-vertical/tree/v12 where you can inspect
    it. It is still missing some documentation and the test coverage is only
    at 73% so there is still room for improvements. We're going to continue
    to work on that, but would also like your opinions an comments on
    everything.
    
    We're using the v12 branch as internal integration branch there and
    could merge from there to an 'official' 12.0 branch now and then.
    
    The structure of everything should be according to the OCA conventions
    as far as we know and understand them; some adaptations may of course
    be necessary.
    
    Please let us know how to proceed with contributing this code to the
    OCA. I think it should be fit at least for an alpha-status in a new
    repo.
    
    Greetings from Berlin,
    
    Olaf
    
    -- 
    Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com 
                   Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
    Geschäftsführer: Olaf Wagner | Sitz: Berlin
    Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
    

    by Olaf Wagner <wagner@elegosoft.com> - 12:46 - 24 Nov 2020
  • Re: Issues with Travis
    Great! Thanks a lot!


    On Tue, Nov 24, 2020 at 10:16 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
    Hi,

    The board has decided to activate the $249/month Travis plan, which gives us 5 concurrent builds.

    We will be evaluating options in the coming weeks

    In the meantime, Travis is back and should work as before.

    Best regards,

    -sbi

    --
    Stéphane Bidoul | @SBidoul
    Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

    On Sat, Nov 21, 2020 at 11:07 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
    Dear contributors,

    As some of you have noticed, Travis has stopped running OCA jobs, as we very quickly exhausted the 10 000 credits they allocated after enabling the new pricing plan.

    I have contacted Travis support to enquire about options and will be discussing with the board about a short term solution while we investigate longer term options.

    I'll keep you posted.

    Have a nice week-end,

    -sbi


    On Mon, Oct 26, 2020 at 2:02 PM Enric Tobella <etobella@creublanca.es> wrote:
    Count with me, I think your way is cleaner than my proposal of script (was using the maintainer-quality-tools in order to keep the same logic).
     
    Thanks for your work
     
    Enric Tobella Alomar
     
    Centros Médicos Creu Blanca
    Tel: 902 202 230
     
    Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
    pueden contener información reservada y/o confidencial, destinada exclusivamente
    para el uso del destinatario o la persona responsable de entregarlo al mismo,
    estando su uso no autorizado prohibido legalmente.
    Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
    salvo ratificación escrita por ambas partes. En caso de su recepción por error,
    rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
    o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
    a su eliminación.
     
    From: Stéphane Bidoul <stephane.bidoul@acsone.eu>
    To: "Contributors" <contributors@odoo-community.org>
    Date: Mon, 26 Oct 2020 12:42:15 -0000
    Subject: Re: Issues with Travis
     
    On Sat, Oct 24, 2020 at 9:07 AM <etobella@creublanca.es> wrote:
    
    
    
    >
    
    
    
    > Let's see if the new travis solves the problem, as that will be easier to maintain. If it doesn't work we still can use github actions
    
    All projects have been migrated to travis-ci.com.
    
    That said I see the backlog is growing again. Travis is capping at 550
    OSS jobs and the OCA queue seems to be at 60 or so right now.
    
    If this situation persists we'll have to do something. I've started to
    refresh previous experiments with GitHub actions
    and I begin to see a path forward (some ideas in an example here
    https://github.com/acsone/mis-builder/pull/3).
    If it comes to it I'm willing to coordinate the work but I'll need
    volunteers to help with the transition, as there will be many
    different things to do.
    
    Let's see how Travis evolves in the coming days.
    
    -sbi
    
    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe




    Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
    pueden contener información reservada y/o confidencial, destinada exclusivamente
    para el uso del destinatario o la persona responsable de entregarlo al mismo,
    estando su uso no autorizado prohibido legalmente.
    Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
    salvo ratificación escrita por ambas partes. En caso de su recepción por error,
    rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
    o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
    a su eliminación.

    _______________________________________________
    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 Alex Comba. - 11:05 - 24 Nov 2020
  • Re: Issues with Travis
    Hi all,

    Yes thanks for this quick reaction once again.

    It seems travis helps us with a workaround to make us think that every cycle CI has an environmental impact.

    If we could reduce these by 2, environmental impact will be reduced by 2
    Ci tests:
    - OCB
    - odoo

    It's very comfortable, all our use cases are tested.

    Yes we really need odoo tests too ...

    ... except if finally we accept compromise to only recommend and test OCB in OCA.

    yes we can

    It's an idea, let's the board decide, surely other possible ideas for environment.

    Regards


    David BEAL - akretion.com
    Consultant
    Odoo Intégration / Développement


    Le mar. 24 nov. 2020 à 10:37, Yannick Vaucher <yannick.vaucher@camptocamp.com> a écrit :
    Looks like we have now a $249/month incentive to switch to github actions.

    Yannick Vaucher
    Business Solutions Architect

    Camptocamp SA
    PSE A, CH-1015 Lausanne
    Phone: +41 21 619 10 30
    Office: +41 21 619 10 10


    On Tue, 24 Nov 2020 at 10:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
    Hi,

    The board has decided to activate the $249/month Travis plan, which gives us 5 concurrent builds.

    We will be evaluating options in the coming weeks

    In the meantime, Travis is back and should work as before.

    Best regards,

    -sbi

    --
    Stéphane Bidoul | @SBidoul
    Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

    On Sat, Nov 21, 2020 at 11:07 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
    Dear contributors,

    As some of you have noticed, Travis has stopped running OCA jobs, as we very quickly exhausted the 10 000 credits they allocated after enabling the new pricing plan.

    I have contacted Travis support to enquire about options and will be discussing with the board about a short term solution while we investigate longer term options.

    I'll keep you posted.

    Have a nice week-end,

    -sbi


    On Mon, Oct 26, 2020 at 2:02 PM Enric Tobella <etobella@creublanca.es> wrote:
    Count with me, I think your way is cleaner than my proposal of script (was using the maintainer-quality-tools in order to keep the same logic).
     
    Thanks for your work
     
    Enric Tobella Alomar
     
    Centros Médicos Creu Blanca
    Tel: 902 202 230
     
    Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
    pueden contener información reservada y/o confidencial, destinada exclusivamente
    para el uso del destinatario o la persona responsable de entregarlo al mismo,
    estando su uso no autorizado prohibido legalmente.
    Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
    salvo ratificación escrita por ambas partes. En caso de su recepción por error,
    rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
    o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
    a su eliminación.
     
    From: Stéphane Bidoul <stephane.bidoul@acsone.eu>
    To: "Contributors" <contributors@odoo-community.org>
    Date: Mon, 26 Oct 2020 12:42:15 -0000
    Subject: Re: Issues with Travis
     
    On Sat, Oct 24, 2020 at 9:07 AM <etobella@creublanca.es> wrote:
    
    
    
    
    >
    
    
    
    
    > Let's see if the new travis solves the problem, as that will be easier to maintain. If it doesn't work we still can use github actions
    
    All projects have been migrated to travis-ci.com.
    
    That said I see the backlog is growing again. Travis is capping at 550
    OSS jobs and the OCA queue seems to be at 60 or so right now.
    
    If this situation persists we'll have to do something. I've started to
    refresh previous experiments with GitHub actions
    and I begin to see a path forward (some ideas in an example here
    https://github.com/acsone/mis-builder/pull/3).
    If it comes to it I'm willing to coordinate the work but I'll need
    volunteers to help with the transition, as there will be many
    different things to do.
    
    Let's see how Travis evolves in the coming days.
    
    -sbi
    
    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe




    Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
    pueden contener información reservada y/o confidencial, destinada exclusivamente
    para el uso del destinatario o la persona responsable de entregarlo al mismo,
    estando su uso no autorizado prohibido legalmente.
    Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
    salvo ratificación escrita por ambas partes. En caso de su recepción por error,
    rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
    o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
    a su eliminación.

    _______________________________________________
    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 David BEAL - 11:05 - 24 Nov 2020