Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Setting up a Higher education ERP with Odoo Community version
    Good morning, 
    I am new to Odoo and would like to learn and set up an ERP with the Odoo community version using the OpenEducate modules. Can anyone help with a guide on how to install an Odoo instance with a cloud service provider?
    Thank you 
    Gabriel
    by Gabriel Aloho - 07:56 - 9 Jun 2024

    2 replies 2 replies

    • Re: Setting up a Higher education ERP with Odoo Community version
      Thank you for your email. It does help me a lot 

      On Mon, 10 Jun 2024 at 12:17, Tom Blauwendraat <notifications@odoo-community.org> wrote:
      Hi Gabriel,

there are a whole lot of ways to set up Odoo on a VM - there's Odoo's 
Docker image, there's Doodba which is a well-documented Docker method by 
Tecnativa, there's "dob" which is also a Docker method, .. there's also 
a script by Yenthe van Ginneken that some people like to use, ... all of 
which are easily found via your favourite search engine.

You could also consider contacting OpenEducat themselves to set up a 
demo instance for you.

Hope this helps,

-Tom

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

      by Gabriel Aloho - 12:20 - 10 Jun 2024
    • Re: Setting up a Higher education ERP with Odoo Community version 
      Hi Gabriel,

there are a whole lot of ways to set up Odoo on a VM - there's Odoo's 
Docker image, there's Doodba which is a well-documented Docker method by 
Tecnativa, there's "dob" which is also a Docker method, .. there's also 
a script by Yenthe van Ginneken that some people like to use, ... all of 
which are easily found via your favourite search engine.

You could also consider contacting OpenEducat themselves to set up a 
demo instance for you.

Hope this helps,

-Tom
      by Tom Blauwendraat - 12:16 - 10 Jun 2024
  • Importing v17 Journal Entries with analytic account info
    Hello, I might be missing something obvious, but here it goes:

    Odoo 17 uses the Analytic Distribution to store analytic account information on Journal Items.
    I would expect to be able to import journal entries including this analytic information.
    But it looks like the Analytic Distribution field is a JSON format and I can't find a user friendly way to import it.

    Is this an oversight on the Analytic Distribution  design, or am I missing something?
    Any recipe out there that can help with this?

    Thank you!

    --
    DANIEL REIS
    MANAGING PARTNER

    Meet with me.
    M: +351 919 991 307
    E: dreis@OpenSourceIntegrators.com
    A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

    [Logo OpenSourceIntegrators.com]

    by Daniel Reis - 05:07 - 7 Jun 2024

    1 replies 1 replies

  • Paperformat issues (Odoo14)

    Hi, 


    I am using this module report_qweb_element_page_visibility to be able to show footer conditionally in reports, but I'm having issues with paperformat.


    I need to define  a "margin botton" paperformat parameter in order to let the footer get the proper space when it needs to be rendered, although by defining a static paperformat margin bottom the space of the footer will always be occupied in the report, even if the footer is not displayed by the class last-page/first-page


    So the OCA module works properly, but I think that the margin bottom paperformat parameter is not flexible enough to support this situation.

    Did you ever come up with a solution to this ? Any kind of workaround is fine :)

    Thank you
    --
    Francesco Ballerini

    by Francesco Ballerini - 12:11 - 7 Jun 2024

    5 replies 5 replies

    • Re: Paperformat issues (Odoo14)
      Hi Tom, I've never looked closely at wkhtmltopdf and odoo report rendering methods so I've found your answer useful, at least I get a more precise idea of the limitations.
      Thanks for the detailed explanation.

      --
      Francesco Ballerini


      Il giorno ven 7 giu 2024 alle ore 20:03 Tom Blauwendraat <notifications@odoo-community.org> ha scritto:

      Hi Francesco,

      thanks for the more detailed explanation, I get your wish now, I didn't before. You basically want the margin-bottom to differ per page.

      I think that's not easy because of the way things are implemented in Odoo - header, content and footer are passed to wkhtmltopdf as separate html blobs, and the margins are global parameters that define the space between them. The header and footer are repeated on each page and get passed a page numbering variable, which is what enables report_qwb_element_page_visibility to work. For the content, it flows across the whole document and generally you don't know while rendering on which page you are.

      So in essence, these are constraints of wkhtmltopdf.

      -Tom


      On 6/7/24 15:02, Francesco Ballerini wrote:
      One last note I forgot to report: it might be obvious, but although this issue might not be really problematic on standard report layouts, It will become an issue when you manage 4x or 5x higher footers, as the occupied space becomes relevant. 
      I posted an example with standard reports only for reproducibility.

      --
      Francesco Ballerini

      Il giorno ven 7 giu 2024 alle ore 14:44 Francesco Ballerini <francescobl.lavoro@gmail.com> ha scritto:

      Hi Tom,


      Thanks for the super quick response.

      AFAIK the report_qweb_element_page_visibility operates on the area outside the margins of the "content area" so the two things should be clearly separated


      That actually make sense for me, so since I was testing a custom report I've tried to reproduced the situation on OCA/reporting-engine odoo14 instance, unfortunately I must confirm what I've said in previous message: if you leave paper format margin bottom value to 0px the footer will not be rendered with or without the installation of module report_qweb_element_page_visibility .

      I've taken notes of all steps to reproduce this behaviour, you can read detailed steps below. Is there anything we can do? Should I open an issue for the module?

      I don't think it's strictly related, so I'm not sure what to do here.


      Steps to reproduce (example with sale order report)


      ADD VISIBILITY CLASS (render footer only in last page)

      - go on Settings > search for > search for "Document Layout", ensure the "external_layout_standard" or another layout is set

      - open the document layout by "external-link" window, find the "div" with footer class and add class "last-page"


      ENSURE PAPER FORMAT USAGE ON REPORT

      - go on Technical > Actions > Reports , select the one named "Quotation / Order"

      - set "A4" record as value for "Paperperformat" field, then click to open the paperformat (or go on Technical > Reporting > Paper Format, and select the A4 paperformat)


      CHANGE PAPER FORMAT PARAMETER

      - set margin bottom to 0px


      PREPARE SALE ORDER DOCUMENT

      - make a sale order that will have enough products to generate a report of at least 2 pages (around 25 products should be fine for the standard report)


      PRINT DOCUMENT

      - on the sale order click "Print" > Quotation / Order


      CURRENT BEHAVIOUR

      Footer will not be rendered on last page (I posted the report in attachments)


      Thank you,
      Francesco Ballerini
      --------------

      Il giorno ven 7 giu 2024 alle ore 12:22 Tom Blauwendraat <notifications@odoo-community.org> ha scritto:

      It sounds a bit paradoxical that you define a bottom margin for the report which is then occupied :)

      AFAIK the report_qweb_element_page_visibility operates on the area outside the margins of the "content area" so the two things should be clearly separated

      Do you perhaps have a screenshot with some arrows and circles highlighting what you mean

      On 6/7/24 12:13, Francesco Ballerini wrote:

      Hi, 


      I am using this module report_qweb_element_page_visibility to be able to show footer conditionally in reports, but I'm having issues with paperformat.


      I need to define  a "margin botton" paperformat parameter in order to let the footer get the proper space when it needs to be rendered, although by defining a static paperformat margin bottom the space of the footer will always be occupied in the report, even if the footer is not displayed by the class last-page/first-page


      So the OCA module works properly, but I think that the margin bottom paperformat parameter is not flexible enough to support this situation.

      Did you ever come up with a solution to this ? Any kind of workaround is fine :)

      Thank you
      --
      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

      _______________________________________________
      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 Francesco Ballerini - 10:31 - 10 Jun 2024
    • Re: Paperformat issues (Odoo14)

      Hi Francesco,

      thanks for the more detailed explanation, I get your wish now, I didn't before. You basically want the margin-bottom to differ per page.

      I think that's not easy because of the way things are implemented in Odoo - header, content and footer are passed to wkhtmltopdf as separate html blobs, and the margins are global parameters that define the space between them. The header and footer are repeated on each page and get passed a page numbering variable, which is what enables report_qwb_element_page_visibility to work. For the content, it flows across the whole document and generally you don't know while rendering on which page you are.

      So in essence, these are constraints of wkhtmltopdf.

      -Tom


      On 6/7/24 15:02, Francesco Ballerini wrote:
      One last note I forgot to report: it might be obvious, but although this issue might not be really problematic on standard report layouts, It will become an issue when you manage 4x or 5x higher footers, as the occupied space becomes relevant. 
      I posted an example with standard reports only for reproducibility.

      --
      Francesco Ballerini

      Il giorno ven 7 giu 2024 alle ore 14:44 Francesco Ballerini <francescobl.lavoro@gmail.com> ha scritto:

      Hi Tom,


      Thanks for the super quick response.

      AFAIK the report_qweb_element_page_visibility operates on the area outside the margins of the "content area" so the two things should be clearly separated


      That actually make sense for me, so since I was testing a custom report I've tried to reproduced the situation on OCA/reporting-engine odoo14 instance, unfortunately I must confirm what I've said in previous message: if you leave paper format margin bottom value to 0px the footer will not be rendered with or without the installation of module report_qweb_element_page_visibility .

      I've taken notes of all steps to reproduce this behaviour, you can read detailed steps below. Is there anything we can do? Should I open an issue for the module?

      I don't think it's strictly related, so I'm not sure what to do here.


      Steps to reproduce (example with sale order report)


      ADD VISIBILITY CLASS (render footer only in last page)

      - go on Settings > search for > search for "Document Layout", ensure the "external_layout_standard" or another layout is set

      - open the document layout by "external-link" window, find the "div" with footer class and add class "last-page"


      ENSURE PAPER FORMAT USAGE ON REPORT

      - go on Technical > Actions > Reports , select the one named "Quotation / Order"

      - set "A4" record as value for "Paperperformat" field, then click to open the paperformat (or go on Technical > Reporting > Paper Format, and select the A4 paperformat)


      CHANGE PAPER FORMAT PARAMETER

      - set margin bottom to 0px


      PREPARE SALE ORDER DOCUMENT

      - make a sale order that will have enough products to generate a report of at least 2 pages (around 25 products should be fine for the standard report)


      PRINT DOCUMENT

      - on the sale order click "Print" > Quotation / Order


      CURRENT BEHAVIOUR

      Footer will not be rendered on last page (I posted the report in attachments)


      Thank you,
      Francesco Ballerini
      --------------

      Il giorno ven 7 giu 2024 alle ore 12:22 Tom Blauwendraat <notifications@odoo-community.org> ha scritto:

      It sounds a bit paradoxical that you define a bottom margin for the report which is then occupied :)

      AFAIK the report_qweb_element_page_visibility operates on the area outside the margins of the "content area" so the two things should be clearly separated

      Do you perhaps have a screenshot with some arrows and circles highlighting what you mean

      On 6/7/24 12:13, Francesco Ballerini wrote:

      Hi, 


      I am using this module report_qweb_element_page_visibility to be able to show footer conditionally in reports, but I'm having issues with paperformat.


      I need to define  a "margin botton" paperformat parameter in order to let the footer get the proper space when it needs to be rendered, although by defining a static paperformat margin bottom the space of the footer will always be occupied in the report, even if the footer is not displayed by the class last-page/first-page


      So the OCA module works properly, but I think that the margin bottom paperformat parameter is not flexible enough to support this situation.

      Did you ever come up with a solution to this ? Any kind of workaround is fine :)

      Thank you
      --
      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

      _______________________________________________
      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 Tom Blauwendraat - 08:02 - 7 Jun 2024
    • Re: Paperformat issues (Odoo14)
      One last note I forgot to report: it might be obvious, but although this issue might not be really problematic on standard report layouts, It will become an issue when you manage 4x or 5x higher footers, as the occupied space becomes relevant. 
      I posted an example with standard reports only for reproducibility.

      --
      Francesco Ballerini

      Il giorno ven 7 giu 2024 alle ore 14:44 Francesco Ballerini <francescobl.lavoro@gmail.com> ha scritto:

      Hi Tom,


      Thanks for the super quick response.


      AFAIK the report_qweb_element_page_visibility operates on the area outside the margins of the "content area" so the two things should be clearly separated


      That actually make sense for me, so since I was testing a custom report I've tried to reproduced the situation on OCA/reporting-engine odoo14 instance, unfortunately I must confirm what I've said in previous message: if you leave paper format margin bottom value to 0px the footer will not be rendered with or without the installation of module report_qweb_element_page_visibility .


      I've taken notes of all steps to reproduce this behaviour, you can read detailed steps below. Is there anything we can do? Should I open an issue for the module?


      I don't think it's strictly related, so I'm not sure what to do here.


      Steps to reproduce (example with sale order report)


      ADD VISIBILITY CLASS (render footer only in last page)

      - go on Settings > search for > search for "Document Layout", ensure the "external_layout_standard" or another layout is set

      - open the document layout by "external-link" window, find the "div" with footer class and add class "last-page"


      ENSURE PAPER FORMAT USAGE ON REPORT

      - go on Technical > Actions > Reports , select the one named "Quotation / Order"

      - set "A4" record as value for "Paperperformat" field, then click to open the paperformat (or go on Technical > Reporting > Paper Format, and select the A4 paperformat)


      CHANGE PAPER FORMAT PARAMETER

      - set margin bottom to 0px


      PREPARE SALE ORDER DOCUMENT

      - make a sale order that will have enough products to generate a report of at least 2 pages (around 25 products should be fine for the standard report)


      PRINT DOCUMENT

      - on the sale order click "Print" > Quotation / Order


      CURRENT BEHAVIOUR

      Footer will not be rendered on last page (I posted the report in attachments)


      Thank you,
      Francesco Ballerini
      --------------

      Il giorno ven 7 giu 2024 alle ore 12:22 Tom Blauwendraat <notifications@odoo-community.org> ha scritto:

      It sounds a bit paradoxical that you define a bottom margin for the report which is then occupied :)

      AFAIK the report_qweb_element_page_visibility operates on the area outside the margins of the "content area" so the two things should be clearly separated

      Do you perhaps have a screenshot with some arrows and circles highlighting what you mean

      On 6/7/24 12:13, Francesco Ballerini wrote:

      Hi, 


      I am using this module report_qweb_element_page_visibility to be able to show footer conditionally in reports, but I'm having issues with paperformat.


      I need to define  a "margin botton" paperformat parameter in order to let the footer get the proper space when it needs to be rendered, although by defining a static paperformat margin bottom the space of the footer will always be occupied in the report, even if the footer is not displayed by the class last-page/first-page


      So the OCA module works properly, but I think that the margin bottom paperformat parameter is not flexible enough to support this situation.

      Did you ever come up with a solution to this ? Any kind of workaround is fine :)

      Thank you
      --
      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

      _______________________________________________
      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 - 03:01 - 7 Jun 2024
    • Re: Paperformat issues (Odoo14)

      Hi Tom,


      Thanks for the super quick response.


      AFAIK the report_qweb_element_page_visibility operates on the area outside the margins of the "content area" so the two things should be clearly separated


      That actually make sense for me, so since I was testing a custom report I've tried to reproduced the situation on OCA/reporting-engine odoo14 instance, unfortunately I must confirm what I've said in previous message: if you leave paper format margin bottom value to 0px the footer will not be rendered with or without the installation of module report_qweb_element_page_visibility .


      I've taken notes of all steps to reproduce this behaviour, you can read detailed steps below. Is there anything we can do? Should I open an issue for the module?


      I don't think it's strictly related, so I'm not sure what to do here.


      Steps to reproduce (example with sale order report)


      ADD VISIBILITY CLASS (render footer only in last page)

      - go on Settings > search for > search for "Document Layout", ensure the "external_layout_standard" or another layout is set

      - open the document layout by "external-link" window, find the "div" with footer class and add class "last-page"


      ENSURE PAPER FORMAT USAGE ON REPORT

      - go on Technical > Actions > Reports , select the one named "Quotation / Order"

      - set "A4" record as value for "Paperperformat" field, then click to open the paperformat (or go on Technical > Reporting > Paper Format, and select the A4 paperformat)


      CHANGE PAPER FORMAT PARAMETER

      - set margin bottom to 0px


      PREPARE SALE ORDER DOCUMENT

      - make a sale order that will have enough products to generate a report of at least 2 pages (around 25 products should be fine for the standard report)


      PRINT DOCUMENT

      - on the sale order click "Print" > Quotation / Order


      CURRENT BEHAVIOUR

      Footer will not be rendered on last page (I posted the report in attachments)


      Thank you,
      Francesco Ballerini
      --------------

      Il giorno ven 7 giu 2024 alle ore 12:22 Tom Blauwendraat <notifications@odoo-community.org> ha scritto:

      It sounds a bit paradoxical that you define a bottom margin for the report which is then occupied :)

      AFAIK the report_qweb_element_page_visibility operates on the area outside the margins of the "content area" so the two things should be clearly separated

      Do you perhaps have a screenshot with some arrows and circles highlighting what you mean

      On 6/7/24 12:13, Francesco Ballerini wrote:

      Hi, 


      I am using this module report_qweb_element_page_visibility to be able to show footer conditionally in reports, but I'm having issues with paperformat.


      I need to define  a "margin botton" paperformat parameter in order to let the footer get the proper space when it needs to be rendered, although by defining a static paperformat margin bottom the space of the footer will always be occupied in the report, even if the footer is not displayed by the class last-page/first-page


      So the OCA module works properly, but I think that the margin bottom paperformat parameter is not flexible enough to support this situation.

      Did you ever come up with a solution to this ? Any kind of workaround is fine :)

      Thank you
      --
      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

      _______________________________________________
      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 - 02:46 - 7 Jun 2024

      1 attachments 1 attachments

      Quotation - S00023 (2).pdf
    • Re: Paperformat issues (Odoo14)

      It sounds a bit paradoxical that you define a bottom margin for the report which is then occupied :)

      AFAIK the report_qweb_element_page_visibility operates on the area outside the margins of the "content area" so the two things should be clearly separated

      Do you perhaps have a screenshot with some arrows and circles highlighting what you mean

      On 6/7/24 12:13, Francesco Ballerini wrote:

      Hi, 


      I am using this module report_qweb_element_page_visibility to be able to show footer conditionally in reports, but I'm having issues with paperformat.


      I need to define  a "margin botton" paperformat parameter in order to let the footer get the proper space when it needs to be rendered, although by defining a static paperformat margin bottom the space of the footer will always be occupied in the report, even if the footer is not displayed by the class last-page/first-page


      So the OCA module works properly, but I think that the margin bottom paperformat parameter is not flexible enough to support this situation.

      Did you ever come up with a solution to this ? Any kind of workaround is fine :)

      Thank you
      --
      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

      by Tom Blauwendraat - 12:21 - 7 Jun 2024
  • e-Commerce categories template on another page (Odoo14)
    Hi,

    I'd like to bring the category template of e-Commerce (this one) on the Homepage route.

    Did someone else ever did it on public repository? (currently working on odoo14 so nearest versions are fine)

    I think I could literally re-use the original template and a new controller in order to send categories data on the home page, but having an example of implementation would be great.

    Regards,
    --
    Francesco Ballerini

    by Francesco Ballerini - 04:41 - 6 Jun 2024
  • Mass ir.attachment export 
    Greetings,

I'm looking for a module that could export all attachments from bills and invoices, preferably sorted by month - for archival purposes. Any in existence?

Cheers,
Alexey
    by Alexey Pelykh - 09:22 - 5 Jun 2024

    3 replies 3 replies

  • Outgoing quantity from draft/sent or not fully delivered confirmed orders (odoo14)
    Hi,

    I am looking for way to compute a field on products that shows the "free quantity" in a slightly different way compared to Odoo:
    Odoo will show free quantity as "qty on hand - reserved qty", but the reserved quantity is related to stock moves so the evaluation involves an order confirmation.

    I have been asked to add a new "free quantity" field that is computed instead as "qty on hand - outgoing qty" where the outgoing quantity should be computed from

    •  'draft' (quotations) orders
    • 'sent' (e-Commerce) orders
    • 'confirm' orders but only for those lines that hasn't been fully delivered

    I might have found an approach to this, which I'll describe below, but I'd like to ask if you have a better suggestion (in best case a field that I've missed or maybe a module introducing this), as I was looking for an easier or better way to achieve this task. 

    Otherwise I think I can do the following:

    I think I can use this module maybe in combination with its parent sale_delivery_state, in order to filter out the majority of orders and evaluate the remaining order lines, filtered by active product: 
    the sum of `demanded quantity - delivered quantity` for all those lines should match the needed computation I need for the "outgoing" quantity at this point.

    Do you have any hint for a shorter and/or better way?

    Thanks in advance

    --
    Francesco Ballerini
    by Francesco Ballerini - 05:21 - 4 Jun 2024

    4 replies 4 replies

  • Contracts for different subsequent prices 
    Hi!
We sell a service contract which costs more in the first year (because 
of installation service) and less in subsequent years (license costs 
only). Ideally this would be configured as a single product which can 
simply be offered in the online shop. Is it possible to configure these 
different prices with Contracts?

Best regards
Jan
    by Jan Suhr - 06:45 - 3 Jun 2024

    4 replies 4 replies

    • Re: Contracts for different subsequent prices

      Hello Jan,

      Do you use the product_contract module to make contract subscription available in the webshop ?

      If yes, you should be able to set up the contract template linked to the product with different lines with different recurrence/end date.  

      Victor Champonnois - Coop IT Easy
Tel : +32 475 81 01 12
      On 4/06/24 09:59, Jan Suhr | Nitrokey wrote:
      Hi Pablo!
Yes, I see this is possible in a sales order. But can this be configured 
in the product or contract or contract template so that it automatically 
applies to all products/contracts bought in the online shop?

Best regards
Jan

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

      by Victor - 11:16 - 5 Jun 2024
    • Re: Contracts for different subsequent prices
      Jan, with OCA Contracts you use a Contract Template, whith Recurrence at Line Level, and specific Date End for that line only for one year.




      El 2024-06-04 04:59, Jan Suhr | Nitrokey escribió:
      Hi Pablo!
      Yes, I see this is possible in a sales order. But can this be configured
      in the product or contract or contract template so that it automatically
      applies to all products/contracts bought in the online shop?
      Best regards
      Jan

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



      [1] https://odoo-community.org/groups/contributors-15
      [2] https://odoo-community.org/groups?unsubscribe
      by info - 09:45 - 4 Jun 2024

      1 attachments 1 attachments

      6de5bac3.png
    • Re: Contracts for different subsequent prices 
      Hi Pablo!
Yes, I see this is possible in a sales order. But can this be configured 
in the product or contract or contract template so that it automatically 
applies to all products/contracts bought in the online shop?

Best regards
Jan
      by Jan Suhr - 09:58 - 4 Jun 2024
    • Re: Contracts for different subsequent prices 
      Hello Jan

Yes, you can specify diferente recurrence for each line, and you can set 
an end date for each individual line.

Regards



El 2024-06-03 13:47, Jan Suhr | Nitrokey escribió:

> Hi!

> We sell a service contract which costs more in the first year (because

> of installation service) and less in subsequent years (license costs

> only). Ideally this would be configured as a single product which can

> simply be offered in the online shop. Is it possible to configure these

> different prices with Contracts?

> Best regards

> Jan

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [1]

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]

> 

> 

> 

> [1] https://odoo-community.org/groups/contributors-15

> [2] https://odoo-community.org/groups?unsubscribe
      by info - 05:03 - 4 Jun 2024
  • Intercompany confirmations 
    Hi OCA,

Enterprise sale_purchase_intercompany modules are not that great.

Does anyone know of an alternative?

-Tom
    by Tom Blauwendraat - 02:51 - 30 May 2024

    2 replies 2 replies

  • Tracking packagings in stock
    Dear OCA members,

    I have been confronted with the following issue, and made a module with the link below for something of a fix.

    Here is the use case: in addition to knowing how many units of products we have in stock, we want to know under what packagings there products are. For example: not only do I want to know I have 95 units in stock, I want to know that I have 5 packages of 10 units and 2 packages of 25 (because one has been opened and 5 units taken out from it).

    It seems modifying the stock.quant model to take into account these packagings would be a hairy task as it is a core model that is read to/written to in a bunch of places.

    Our simple solution is to create an intermediary model and a computed field on stock.quants and products that will store this information: 


    This allows to preserve native Odoo functionality but also serves our requirement (we only care about showing this, for some data that we receive from a connector to another WMS). It works in our situation but someone out there might have thought of a more general approach, what do you think ?

    Best regards,
    by "Kevin Khao" <kevin.khao@akretion.com.br> - 07:16 - 27 May 2024

    2 replies 2 replies

    • Re: Tracking packagings in stock
      Probably I am missing something here.

      However, please let me offer my 2c by asking the following:
      - wouldn't it be that the natural solution is to manage the type of packaging in parallel to the type of products? In my experience, dealing with products in various physical structures (solid, gas, liquid, powder) and not having the various types of packaging is "insane" :-).
      Certainly, I am missing something in the initial question.

      Best regards,

      ( apmcservice@gmail.com )



      On Tue, May 28, 2024 at 12:17 AM Kevin Khao <notifications@odoo-community.org> wrote:
      Dear OCA members,

      I have been confronted with the following issue, and made a module with the link below for something of a fix.

      Here is the use case: in addition to knowing how many units of products we have in stock, we want to know under what packagings there products are. For example: not only do I want to know I have 95 units in stock, I want to know that I have 5 packages of 10 units and 2 packages of 25 (because one has been opened and 5 units taken out from it).

      It seems modifying the stock.quant model to take into account these packagings would be a hairy task as it is a core model that is read to/written to in a bunch of places.

      Our simple solution is to create an intermediary model and a computed field on stock.quants and products that will store this information: 


      This allows to preserve native Odoo functionality but also serves our requirement (we only care about showing this, for some data that we receive from a connector to another WMS). It works in our situation but someone out there might have thought of a more general approach, what do you think ?

      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

      by milori2006 - 12:21 - 28 May 2024
    • Re: Tracking packagings in stock 
      On 27/05/2024 19:17, Kevin Khao wrote:

> Dear OCA members,

> 

> I have been confronted with the following issue, and made a module with 

> the link below for something of a fix.

> 

> Here is the use case: in addition to knowing how many units of products 

> we have in stock, we want to know under what packagings there products 

> are. For example: not only do I want to know I have 95 units in stock, I 

> want to know that I have 5 packages of 10 units and 2 packages of 25 

> (because one has been opened and 5 units taken out from it).

> 

> It seems modifying the stock.quant model to take into account these 

> packagings would be a hairy task as it is a core model that is read 

> to/written to in a bunch of places.

> 

> Our simple solution is to create an intermediary model and a computed 

> field on stock.quants and products that will store this information:

> 

> https://github.com/OCA/stock-logistics-warehouse/pull/2050/files 

> <https://github.com/OCA/stock-logistics-warehouse/pull/2050/files>

> 

> This allows to preserve native Odoo functionality but also serves our 

> requirement (we only care about showing this, for some data that we 

> receive from a connector to another WMS). It works in our situation but 

> someone out there might have thought of a more general approach, what do 

> you think ?

Did you check 
https://github.com/OCA/stock-logistics-warehouse/tree/16.0/stock_product_qty_by_packaging 
?



-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
      by Alexandre Fayolle - 12:11 - 28 May 2024
  • Application for PSC Role - OCA Helpdesk Repository
    Hello everyone,

    I would like to apply to become one of the PSCs for the OCA Helpdesk repository.

    Currently, I am a member of the PSC for the Brazilian localization and have been actively contributing to various OCA repositories for a considerable time.

    Over the years, I have been working extensively with Odoo, developing modules, performing migrations, and contributing to the community. I believe my experience can add significant value to the Helpdesk project.

    Thank you for your consideration. I am available for any questions or further discussions.

    Best regards,

    Marcel Savegnago





    by "Marcel Savegnago" <marcel.savegnago@gmail.com> - 06:06 - 27 May 2024

    2 replies 2 replies

  • Encrypt personal data in French/European Medical legislations (GPDR++)
    Dear all

    What you be your advice to encrypt personal data at low level ?

    Thanks in advance

    --------------------------------
    Cyril VINH-TUNG
    INVITU
    Computer & Network Engineering
    BP 32 - 98713 Papeete - French Polynesia
    Tél: +689 40 46 11 99
    contact@invitu.com
    www.invitu.com
    by Cyril VINH-TUNG - 04:41 - 25 May 2024
  • field extraction rule for funny date format 
    Hi!
The module account_invoice_import_simple_pdf allows to define field 
extraction rules. UPS sends invoices with date in format "02.April 2024" 
so the first separator is a dot and the second a space. Is it possible 
to define a field extraction rule for such format?

Best regards
Jan
    by Jan Suhr - 02:32 - 23 May 2024

    1 replies 1 replies

    • Re: field extraction rule for funny date format

      Hi,


      reading the source there probably isn't but I haven't tested it. Looking at it I see 2 ways going forward:

      1) Extending the options for date formats with this specific one - may be a bit tricky

      2) Adding an option for usage of dateparser library and possible mask


      Regarding dateparser it's quite easy:

      >>> dateparser.parse('02.April 2024', date_formats=['%d.%B %Y'])
      datetime.datetime(2024, 4, 2, 0, 0)

      I would even suggest reworking the date handling using the library...


      Best regards


          Radovan


      On štvrtok 23. mája 2024 14:32:10 CEST Jan Suhr | Nitrokey wrote:

      > Hi!

      > The module account_invoice_import_simple_pdf allows to define field

      > extraction rules. UPS sends invoices with date in format "02.April 2024"

      > so the first separator is a dot and the second a space. Is it possible

      > to define a field extraction rule for such format?

      > Best regards

      > Jan

      >

      > _______________________________________________

      > Mailing-List: https://odoo-community.org/groups/contributors-15 [1]

      > Post to: mailto:contributors@odoo-community.org

      > Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]

      >

      >

      >

      > [1] https://odoo-community.org/groups/contributors-15

      > [2] https://odoo-community.org/groups?unsubscribe



      by Radovan Skolnik - 02:50 - 23 May 2024
  • Addendas for Audi, Mabe, Ford, Whirlpool, Volkswagen
    Hello

    We have a client that needs the addendas for Audi, Mabe, Ford, Whirlpool and Volkswagen. 

    Does anyone have any of these? For what version? Please get in contact with us with a quotation for your services.

    Thank you!

    --

    SAMUEL MACIAS OROPEZA

    TECH LEAD

    smacias@opensourceintegrators.com

    P.O. BOX 940, HIGLEY, AZ 85236

    by Samuel Macias Oropeza - 04:26 - 20 May 2024

    3 replies 3 replies

    • Re: Addendas for Audi, Mabe, Ford, Whirlpool, Volkswagen

      Have a look here: https://github.com/OCA/edi There are some modules implementing for example Factur-X or UBL standards. It would be helpful if you found out what the actual standard for these addendas was.


      Best regards


          Radovan Skolnik


      On utorok 21. mája 2024 15:27:21 CEST Samuel Macias Oropeza wrote:

      > Addenda are complements to mexican electronic invoices. They don't affect

      > the invoice itself, but provide additional commercial information requested

      > by the client. Some large companies require their providers to issue an

      > addendum with every invoice, and the information required in the addendum

      > varies from company to company On Mon, May 20, 2024 at 8:37 AM Radovan

      > Skolnik < notifications@odoo-community.org [1] > wrote: Hello,

      > what are "addends" if I may ask.

      > Best regards,

      > Radovan Skolnik

      > On May 20, 2024 16:27, Samuel Macias Oropeza <

      > notifications@odoo-community.org [2] > wrote:  Hello We have a client that

      > needs the addendas for Audi, Mabe, Ford, Whirlpool and Volkswagen. Does

      > anyone have any of these? For what version? Please get in contact with us

      > with a quotation for your services. Thank you!

      > --

      > SAMUEL MACIAS OROPEZA

      > TECH LEAD

      > smacias@opensourceintegrators.com [3]

      > P.O. BOX 940, HIGLEY, AZ 85236

      >

      > _______________________________________________

      > Mailing-List: https://odoo-community.org/groups/contributors-15 [4]

      > Post to: mailto: contributors@odoo-community.org [5]

      > Unsubscribe: https://odoo-community.org/groups?unsubscribe [6]

      >

      >

      > _______________________________________________

      > Mailing-List: https://odoo-community.org/groups/contributors-15 [7]

      > Post to: mailto: contributors@odoo-community.org [8]

      > Unsubscribe: https://odoo-community.org/groups?unsubscribe [9]

      >

      >

      > _______________________________________________

      > Mailing-List: https://odoo-community.org/groups/contributors-15 [10]

      > Post to: mailto:contributors@odoo-community.org

      > Unsubscribe: https://odoo-community.org/groups?unsubscribe [11]

      >

      >

      >

      > [1] mailto:notifications@odoo-community.org

      > [2] mailto:notifications@odoo-community.org

      > [3] mailto:smacias@opensourceintegrators.com

      > [4] https://odoo-community.org/groups/contributors-15

      > [5] mailto:contributors@odoo-community.org

      > [6] https://odoo-community.org/groups?unsubscribe

      > [7] https://odoo-community.org/groups/contributors-15

      > [8] mailto:contributors@odoo-community.org

      > [9] https://odoo-community.org/groups?unsubscribe

      > [10] https://odoo-community.org/groups/contributors-15

      > [11] https://odoo-community.org/groups?unsubscribe



      by Radovan Skolnik - 03:51 - 21 May 2024
    • Re: Addendas for Audi, Mabe, Ford, Whirlpool, Volkswagen
      Addenda are complements to mexican electronic invoices. They don't affect the invoice itself, but provide additional commercial information requested by the client. Some large companies require their providers to issue an addendum with every invoice, and the information required in the addendum varies from company to company

      On Mon, May 20, 2024 at 8:37 AM Radovan Skolnik <notifications@odoo-community.org> wrote:
      Hello, 

      what are "addends" if I may ask.

      Best regards, 

        Radovan Skolnik 

      On May 20, 2024 16:27, Samuel Macias Oropeza <notifications@odoo-community.org> wrote:
      Hello

      We have a client that needs the addendas for Audi, Mabe, Ford, Whirlpool and Volkswagen. 

      Does anyone have any of these? For what version? Please get in contact with us with a quotation for your services.

      Thank you!

      --

      SAMUEL MACIAS OROPEZA

      TECH LEAD

      smacias@opensourceintegrators.com

      P.O. BOX 940, HIGLEY, AZ 85236

      _______________________________________________
      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 Samuel Macias Oropeza - 03:26 - 21 May 2024
    • Re: Addendas for Audi, Mabe, Ford, Whirlpool, Volkswagen
      Hello, 

      what are "addends" if I may ask.

      Best regards, 

        Radovan Skolnik 

      On May 20, 2024 16:27, Samuel Macias Oropeza <notifications@odoo-community.org> wrote:
      Hello

      We have a client that needs the addendas for Audi, Mabe, Ford, Whirlpool and Volkswagen. 

      Does anyone have any of these? For what version? Please get in contact with us with a quotation for your services.

      Thank you!

      --

      SAMUEL MACIAS OROPEZA

      TECH LEAD

      smacias@opensourceintegrators.com

      P.O. BOX 940, HIGLEY, AZ 85236

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


      by Radovan Skolnik - 04:36 - 20 May 2024
  • Session storage in S3
    Hello OCA community,

    As part of a multi-tenant deployment with several replicas, we are looking to persist Odoo sessions elsewhere than in the container.

    We recently tested the OCA/session_db module with success, but if anyone had any experience to share on the multi-tenant side we'd be more confident ;-).

    Nevertheless, since we also use the OCA/fs_storage and OCA/fs_attachment modules to store attached files in an S3 environment, we'd be tempted to use S3 instead of the DB.
    Do any of you know of such a module? Is it a good idea?

    I'm sure I'll have other questions about multi-tenant deployment with k8s, but I'd rather keep this to one subject per e-mail.

    Thank you in advance for any help you can provide.

    Stéphane Van Erp for iMio



    by Stéphane Van Erp - 10:15 - 19 May 2024

    3 replies 3 replies

    • Re: Session storage in S3
      Hello Stéphane,

      > We recently tested the OCA/session_db module with success, but if anyone had any experience to share on the multi-tenant side we'd be more confident ;-).

      We have good experience with session_db. It has the advantage of being simple to deploy.
      Multi-tenant is not an issue provided you use a dedicated db for sessions.
      Do you have specific worries regarding multi tenancy?

      Intuitively I suspect session_db or session_redis would have better performance than an s3 solution, but I'd be interested about the results if you do any measurements.

      Best regards,

      --
      Stéphane Bidoul

      On Sun, May 19, 2024 at 10:16 PM Stéphane Van Erp <notifications@odoo-community.org> wrote:
      Hello OCA community,

      As part of a multi-tenant deployment with several replicas, we are looking to persist Odoo sessions elsewhere than in the container.

      We recently tested the OCA/session_db module with success, but if anyone had any experience to share on the multi-tenant side we'd be more confident ;-).

      Nevertheless, since we also use the OCA/fs_storage and OCA/fs_attachment modules to store attached files in an S3 environment, we'd be tempted to use S3 instead of the DB.
      Do any of you know of such a module? Is it a good idea?

      I'm sure I'll have other questions about multi-tenant deployment with k8s, but I'd rather keep this to one subject per e-mail.

      Thank you in advance for any help you can provide.

      Stéphane Van Erp for iMio



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

      by Stéphane Bidoul - 11:16 - 21 May 2024
    • Re: Session storage in S3 
      We use session_redis

https://github.com/camptocamp/odoo-cloud-platform/tree/16.0/session_redis

Alexandre Fayolle

On 19/05/2024 22:16, Stéphane Van Erp wrote:

> Hello OCA community,

> 

> As part of a multi-tenant deployment with several replicas, we are 

> looking to persist Odoo sessions elsewhere than in the container.

> 

> We recently tested the OCA/session_db module with success, but if anyone 

> had any experience to share on the multi-tenant side we'd be more 

> confident ;-).

> 

> Nevertheless, since we also use the OCA/fs_storage and OCA/fs_attachment 

> modules to store attached files in an S3 environment, we'd be tempted to 

> use S3 instead of the DB.

> Do any of you know of such a module? Is it a good idea?

> 

> I'm sure I'll have other questions about multi-tenant deployment with 

> k8s, but I'd rather keep this to one subject per e-mail.

> 

> Thank you in advance for any help you can provide.

> 

> Stéphane Van Erp for iMio <https://imio.be>

> 

> 

> 

> _______________________________________________

> 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>

> 


-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
      by Alexandre Fayolle - 08:53 - 21 May 2024
    • Re: Session storage in S3
      Hello

      Not tested but I would mount session folder (as we actually do with filestore in our infra) with nfs in your containers
      Maybe there will be some security issues with that...
      I let experts give their pov

      Best regards

      --------------------------------
      Cyril VINH-TUNG
      INVITU
      Computer & Network Engineering
      BP 32 - 98713 Papeete - French Polynesia
      Tél: +689 40 46 11 99
      contact@invitu.com
      www.invitu.com

      Le dim. 19 mai 2024, 10:16, Stéphane Van Erp <notifications@odoo-community.org> a écrit :
      Hello OCA community,

      As part of a multi-tenant deployment with several replicas, we are looking to persist Odoo sessions elsewhere than in the container.

      We recently tested the OCA/session_db module with success, but if anyone had any experience to share on the multi-tenant side we'd be more confident ;-).

      Nevertheless, since we also use the OCA/fs_storage and OCA/fs_attachment modules to store attached files in an S3 environment, we'd be tempted to use S3 instead of the DB.
      Do any of you know of such a module? Is it a good idea?

      I'm sure I'll have other questions about multi-tenant deployment with k8s, but I'd rather keep this to one subject per e-mail.

      Thank you in advance for any help you can provide.

      Stéphane Van Erp for iMio



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

      by Cyril VINH-TUNG - 10:46 - 19 May 2024
  • CI and oca_dependencies.txt
    Hello,

    I'm trying to recreate a CI environment for testing our modules on our GitLab instance.
    In the documentation [1], it is stated that we could use a custom repo URL and branch using oca_dependencies.txt.
    But after searching in oca-ci repo [2] and test.yml in modules repositories, I don't find any use of the oca_dependencies.txt.
    Am I missing something or all dependencies are only managed by setuptools-odoo and installed via pip instead of cloning modules repositories ?

    If oca_dependencies.txt is no longer supported, do you remember where this file was parsed and processed ?


    Best regards,
    Yann Papouin.
    by Yann Papouin - 12:06 - 16 May 2024

    2 replies 2 replies

  • Migration of App "Email Tracking" to Odoo Version 17

    Dears

    I hope this email finds you well. I am reaching out to inquire about the migration status of the following app to Odoo Version 17:

    1. Email tracking: https://apps.odoo.com/apps/modules/16.0/mail_tracking/

    We are currently in need of this app for our new client, and it's crucial for us to have them compatible with the latest version of Odoo.

    Could you please provide an update on when these apps are expected to be migrated to Odoo Version 17?

    Thank you so much for you valuable help

    --
    Melhores Cumprimentos | Best Regards
    Person Banner
    Website www.arxi.pt Phone +351 244 237 810
    (chamada para a rede fixa nacional)         		Linkedin Facebook
    Person
    Warning Esta mensagem contém informação de natureza confidencial e é exclusivamente dirigida ao(s) destinatário(s) indicado(s). Se por engano receber este e-mail agradecemos que não o copie nem o reenvie e que nos notifique do ocorrido através do email de resposta. Qualquer uso do seu conteúdo é um ato ilegal.
    Warning This message contains confidential information and is addressed exclusively to the designated addressee. If you received this email by mistake we appreciate that you do not copy or resend it and that you notify us of via the reply email. Any use of its content is strictly illegal.
    by Andrea Delgado - 05:00 - 9 May 2024

    1 replies 1 replies

  • Free courses

    Hi

     

    We offer free online tutorials (with no subscriptions needed) on a YouTube channel with over 200,000 subscribers here:

     

    https://www.wiseowl.co.uk/videos/

     

    We also have full online-tutorials (again free, and with no log-in needed) in VBA and SQL:

     

    https://www.wiseowl.co.uk/guides/

     

    Would any of the readers of your site be interested in either of these ideas?

     

    Regards

     

    Andy (Brown)

     

    Telephone:     +44 (0) 161 883 3606
         Website:         https://www.wiseowl.co.uk

      Follow us:        

     

    by "Andy Brown" <andy.brown@wiseowl.co.uk> - 05:16 - 8 May 2024

    4 attachments 4 attachments

    image004.png
    image003.png
    image002.png
    image001.png
  • Mabe addenda for Mexican Localization
    Hello!

    We would like to know if anyone in the community has any module or development for the addenda for Mabe. Please reach out to us if you do

    Thank you!

    --

    SAMUEL MACIAS OROPEZA

    TECH LEAD

    smacias@opensourceintegrators.com

    P.O. BOX 940, HIGLEY, AZ 85236

    by Samuel Macias Oropeza - 07:31 - 3 May 2024
  • Github runners
    Hi all folks,

    @OCA/board Is there something changed about github runners configuration? 

    Since yesterday, runners seems to take a long time to get available resource:

    image.png


    Thanks for your support.
    --

    Denis Roussel
    Software Engineer
    T    : +32 2 888 31 49
    M : +32 472 22 00 57


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg
    by Denis Roussel - 09:45 - 30 Apr 2024

    1 attachments 1 attachments

    image.png

    3 replies 3 replies

  • The OCA Functional Working Group asks for your help!
    Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?

    Hello everybody!


    During the last OCA Days, the OCA Functional Working Group (FWG) presented the work made on the Documentation Project.


    This project was created by the FWG to help and attract functional people to contribute to modules documentation.


    2 main options were analyzed


    • Using the existing Read Me file in the code so we have only one module documentation which regroups technical and functional information.

    • Using the GitHub Wiki on the repositories which could be really easy to put in place and use.


    The decision was made to use the existing Read Me but to convert it into Markdown so it could be easier to use and to add images.


    Following this decision, an issue was opened in GitHub about the use of the Wiki instead of Read Me : https://github.com/OCA/maintainer-tools/issues/606



    BUT, we still have a big issue regarding this solution: the process to contribute to Read Me is really, really complicated for non-technicals.  


    1. You need to have a Github account and sign the OCA CLA

    2. You would have to fork the repository (well, here we already have lost most of the non-technical people).

    3. Then edit the files of the Read Me using the Web Editor (so you can add images).

    4. Download your images in the right folder than insert them into the file by Drag & Drop

    5. Create a commit and a PR.

    6. Finally, the changes would need to be approved by contributors who have those access rights.



    So, we were thinking: if we add a Markdown tool that can be used to edit Read Me files and automatically push the changes into GitHub a little bit like the Weblate tool, we could combine the PROS of both options analyzed.



    Does anyone have any idea of this kind of tool?


    Thank you in advance for your help.



    The OCA Functional Working Group

    fwg@odoo-community.org



    by Julie LeBrun - 07:31 - 23 Apr 2024

    7 replies 7 replies

    • Re: The OCA Functional Working Group asks for your help!
      Hello everyone,

      Given that documentation is the first interaction many have with our modules, it's crucial that the READMEs for each module and repository are clear, informative, and standardized. Currently, each README serves as an essential introduction to its respective module or repository, but many could benefit from further review and content enrichment.

      With the advancement of AI technologies, we have a great opportunity to use these tools to efficiently review and generate content. This will not only improve the quality of our documentation but also make the modules more accessible and easier to use for new users and contributors.

      I suggest we start a project to review the existing READMEs. This project could include the following steps:
      1. **Initial assessment of all existing READMEs** to identify those that need urgent improvements.
      2. **Development of a style guide or template** to ensure all READMEs follow a consistent format and contain all necessary information.
      3. **Use of AI tools** to assist in content review and generation where applicable, ensuring accuracy and quality.
      4. **Peer review**, where community members can contribute feedback before finalizing the documents.

      After completing this initial phase of reviewing and standardizing our READMEs, it would then be worthwhile to pursue a platform or a new process for building out the documentation further. This would ensure that our foundational documents are strong before we expand our documentation infrastructure.

      Best regards,

      Marcel Savegnago (https://escodoo.com.br)


      Em qui., 2 de mai. de 2024 às 10:02, Julie LeBrun <notifications@odoo-community.org> escreveu:
      Thank you everybody for taking the time to answer and help.

      We will be analyzing those options and communicating with some of you to have more information.


       
      Julie LeBrun
      Formatrice & Analyste en applications de gestion intégrée
      +1 514-317-7944
      LinkedIn Twitter Facebook YouTube
       
        Nouveau
      Choisir un nom de projet comme un pro       		  Découvrir


      Le jeu. 25 avr. 2024 à 11:17, Raphaël Valyi <notifications@odoo-community.org> a écrit :
      Hello,

      just a word to also encourage mkdocs if we aim at something additional to the current README markdown system. As Graeme said mkdocs is popular, capable and simple to manage (we really need to avoid big new tools that would be an infrastructure burden to manage). I think the README are slowly being improved, even if it's still by the module tech authors. In OCA/l10n-brazil we try to slowly improve these README for instance. At some point improving these README is lowering the entry barrier to the OCA and it somewhat makes sense that this entry barrier is lowered at the same time than the code is cleaned up and migrated so that non alien people will eventually succeed in their project with the OCA instead of just accumulating frustration by trying to attract at all cost people which will not make it with the current ecosystem (something that Odoo SA does quite a lot themselves in fact). So I mean it is not that bad if that documentation pace isn't as fast as some people who don't use to deliver real projects may dream...

      On Wed, Apr 24, 2024 at 11:27 AM Graeme Gellatly <notifications@odoo-community.org> wrote:
      I second mkdocs. All my non technical staff use it to build docs. Most.jist write markdown bit some use a specialised markdown editor although that seems to fail lintimg quite a bit.

      It is trivial to automate linting and deploy on merge.

      On Wed, 24 Apr 2024, 6:52 am Victor Champonnois, <notifications@odoo-community.org> wrote:

      Hello Julie,

      >Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?

      I think Weblate directly commits on the main branch, it does not create a PR.

      As Andreas says, the edit functionality in Github seems like the simplest approach. However, it requires to create a fork of the repo, and to make a PR, so it's still a big barrier. 

      Victor Champonnois - Coop IT Easy
Tel : +32 475 81 01 12
      On 24/04/24 07:44, Andreas Perhab wrote:
      Hi Julie,

      I think the edit button in github does most of the forking work for you and even helps with creating a PR when one is finished editing the readme (really any markdown file).
      FireShot Capture 260 - OCA_maintainer-tools_ Odoo Maintainers Tools & conventions for OCA me_ - github.com.png

      It puts images into /assets/{number}/{uuid} so that might need changing or we could just accept this additional directory.

      regards Andreas



      On Tue, 23 Apr 2024 at 19:32, Julie LeBrun <notifications@odoo-community.org> wrote:
      Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?

      Hello everybody!


      During the last OCA Days, the OCA Functional Working Group (FWG) presented the work made on the Documentation Project.


      This project was created by the FWG to help and attract functional people to contribute to modules documentation.


      2 main options were analyzed


      • Using the existing Read Me file in the code so we have only one module documentation which regroups technical and functional information.

      • Using the GitHub Wiki on the repositories which could be really easy to put in place and use.


      The decision was made to use the existing Read Me but to convert it into Markdown so it could be easier to use and to add images.


      Following this decision, an issue was opened in GitHub about the use of the Wiki instead of Read Me : https://github.com/OCA/maintainer-tools/issues/606



      BUT, we still have a big issue regarding this solution: the process to contribute to Read Me is really, really complicated for non-technicals.  


      1. You need to have a Github account and sign the OCA CLA

      2. You would have to fork the repository (well, here we already have lost most of the non-technical people).

      3. Then edit the files of the Read Me using the Web Editor (so you can add images).

      4. Download your images in the right folder than insert them into the file by Drag & Drop

      5. Create a commit and a PR.

      6. Finally, the changes would need to be approved by contributors who have those access rights.



      So, we were thinking: if we add a Markdown tool that can be used to edit Read Me files and automatically push the changes into GitHub a little bit like the Weblate tool, we could combine the PROS of both options analyzed.



      Does anyone have any idea of this kind of tool?


      Thank you in advance for your help.



      The OCA Functional Working Group

      fwg@odoo-community.org



      _______________________________________________
      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



      --
      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



      --

      Visite o nosso site
        Marcel Savegnago
      marcel.savegnago@escodoo.com.br
      +55 16 99122-7649

      A informação transmitida destina-se apenas a pessoa ou entidade a quem foi endereçada e pode conter informação confidencial, legalmente protegida e para conhecimento exclusivo do destinatário. Se o leitor desta advertência não for o seu destinatário, fica ciente de que sua leitura, divulgação, distribuição ou copia é estritamente proibida. Caso a mensagem tenha sido recebida por engano, favor comunicar ao remetente e apagar o texto do computador. 

      The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
      by Marcel Savegnago - 02:36 - 3 May 2024
    • Re: The OCA Functional Working Group asks for your help!
      Thank you everybody for taking the time to answer and help.

      We will be analyzing those options and communicating with some of you to have more information.


       
      Julie LeBrun
      Formatrice & Analyste en applications de gestion intégrée
      +1 514-317-7944
      LinkedIn Twitter Facebook YouTube
       
        Nouveau
      Choisir un nom de projet comme un pro       		  Découvrir


      Le jeu. 25 avr. 2024 à 11:17, Raphaël Valyi <notifications@odoo-community.org> a écrit :
      Hello,

      just a word to also encourage mkdocs if we aim at something additional to the current README markdown system. As Graeme said mkdocs is popular, capable and simple to manage (we really need to avoid big new tools that would be an infrastructure burden to manage). I think the README are slowly being improved, even if it's still by the module tech authors. In OCA/l10n-brazil we try to slowly improve these README for instance. At some point improving these README is lowering the entry barrier to the OCA and it somewhat makes sense that this entry barrier is lowered at the same time than the code is cleaned up and migrated so that non alien people will eventually succeed in their project with the OCA instead of just accumulating frustration by trying to attract at all cost people which will not make it with the current ecosystem (something that Odoo SA does quite a lot themselves in fact). So I mean it is not that bad if that documentation pace isn't as fast as some people who don't use to deliver real projects may dream...

      On Wed, Apr 24, 2024 at 11:27 AM Graeme Gellatly <notifications@odoo-community.org> wrote:
      I second mkdocs. All my non technical staff use it to build docs. Most.jist write markdown bit some use a specialised markdown editor although that seems to fail lintimg quite a bit.

      It is trivial to automate linting and deploy on merge.

      On Wed, 24 Apr 2024, 6:52 am Victor Champonnois, <notifications@odoo-community.org> wrote:

      Hello Julie,

      >Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?

      I think Weblate directly commits on the main branch, it does not create a PR.

      As Andreas says, the edit functionality in Github seems like the simplest approach. However, it requires to create a fork of the repo, and to make a PR, so it's still a big barrier. 

      Victor Champonnois - Coop IT Easy
Tel : +32 475 81 01 12
      On 24/04/24 07:44, Andreas Perhab wrote:
      Hi Julie,

      I think the edit button in github does most of the forking work for you and even helps with creating a PR when one is finished editing the readme (really any markdown file).
      FireShot Capture 260 - OCA_maintainer-tools_ Odoo Maintainers Tools & conventions for OCA me_ - github.com.png

      It puts images into /assets/{number}/{uuid} so that might need changing or we could just accept this additional directory.

      regards Andreas



      On Tue, 23 Apr 2024 at 19:32, Julie LeBrun <notifications@odoo-community.org> wrote:
      Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?

      Hello everybody!


      During the last OCA Days, the OCA Functional Working Group (FWG) presented the work made on the Documentation Project.


      This project was created by the FWG to help and attract functional people to contribute to modules documentation.


      2 main options were analyzed


      • Using the existing Read Me file in the code so we have only one module documentation which regroups technical and functional information.

      • Using the GitHub Wiki on the repositories which could be really easy to put in place and use.


      The decision was made to use the existing Read Me but to convert it into Markdown so it could be easier to use and to add images.


      Following this decision, an issue was opened in GitHub about the use of the Wiki instead of Read Me : https://github.com/OCA/maintainer-tools/issues/606



      BUT, we still have a big issue regarding this solution: the process to contribute to Read Me is really, really complicated for non-technicals.  


      1. You need to have a Github account and sign the OCA CLA

      2. You would have to fork the repository (well, here we already have lost most of the non-technical people).

      3. Then edit the files of the Read Me using the Web Editor (so you can add images).

      4. Download your images in the right folder than insert them into the file by Drag & Drop

      5. Create a commit and a PR.

      6. Finally, the changes would need to be approved by contributors who have those access rights.



      So, we were thinking: if we add a Markdown tool that can be used to edit Read Me files and automatically push the changes into GitHub a little bit like the Weblate tool, we could combine the PROS of both options analyzed.



      Does anyone have any idea of this kind of tool?


      Thank you in advance for your help.



      The OCA Functional Working Group

      fwg@odoo-community.org



      _______________________________________________
      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



      --
      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 Julie LeBrun - 03:01 - 2 May 2024
    • Re: The OCA Functional Working Group asks for your help!
      Hello,

      just a word to also encourage mkdocs if we aim at something additional to the current README markdown system. As Graeme said mkdocs is popular, capable and simple to manage (we really need to avoid big new tools that would be an infrastructure burden to manage). I think the README are slowly being improved, even if it's still by the module tech authors. In OCA/l10n-brazil we try to slowly improve these README for instance. At some point improving these README is lowering the entry barrier to the OCA and it somewhat makes sense that this entry barrier is lowered at the same time than the code is cleaned up and migrated so that non alien people will eventually succeed in their project with the OCA instead of just accumulating frustration by trying to attract at all cost people which will not make it with the current ecosystem (something that Odoo SA does quite a lot themselves in fact). So I mean it is not that bad if that documentation pace isn't as fast as some people who don't use to deliver real projects may dream...

      On Wed, Apr 24, 2024 at 11:27 AM Graeme Gellatly <notifications@odoo-community.org> wrote:
      I second mkdocs. All my non technical staff use it to build docs. Most.jist write markdown bit some use a specialised markdown editor although that seems to fail lintimg quite a bit.

      It is trivial to automate linting and deploy on merge.

      On Wed, 24 Apr 2024, 6:52 am Victor Champonnois, <notifications@odoo-community.org> wrote:

      Hello Julie,

      >Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?

      I think Weblate directly commits on the main branch, it does not create a PR.

      As Andreas says, the edit functionality in Github seems like the simplest approach. However, it requires to create a fork of the repo, and to make a PR, so it's still a big barrier. 

      Victor Champonnois - Coop IT Easy
Tel : +32 475 81 01 12
      On 24/04/24 07:44, Andreas Perhab wrote:
      Hi Julie,

      I think the edit button in github does most of the forking work for you and even helps with creating a PR when one is finished editing the readme (really any markdown file).
      FireShot Capture 260 - OCA_maintainer-tools_ Odoo Maintainers Tools & conventions for OCA me_ - github.com.png

      It puts images into /assets/{number}/{uuid} so that might need changing or we could just accept this additional directory.

      regards Andreas



      On Tue, 23 Apr 2024 at 19:32, Julie LeBrun <notifications@odoo-community.org> wrote:
      Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?

      Hello everybody!


      During the last OCA Days, the OCA Functional Working Group (FWG) presented the work made on the Documentation Project.


      This project was created by the FWG to help and attract functional people to contribute to modules documentation.


      2 main options were analyzed


      • Using the existing Read Me file in the code so we have only one module documentation which regroups technical and functional information.

      • Using the GitHub Wiki on the repositories which could be really easy to put in place and use.


      The decision was made to use the existing Read Me but to convert it into Markdown so it could be easier to use and to add images.


      Following this decision, an issue was opened in GitHub about the use of the Wiki instead of Read Me : https://github.com/OCA/maintainer-tools/issues/606



      BUT, we still have a big issue regarding this solution: the process to contribute to Read Me is really, really complicated for non-technicals.  


      1. You need to have a Github account and sign the OCA CLA

      2. You would have to fork the repository (well, here we already have lost most of the non-technical people).

      3. Then edit the files of the Read Me using the Web Editor (so you can add images).

      4. Download your images in the right folder than insert them into the file by Drag & Drop

      5. Create a commit and a PR.

      6. Finally, the changes would need to be approved by contributors who have those access rights.



      So, we were thinking: if we add a Markdown tool that can be used to edit Read Me files and automatically push the changes into GitHub a little bit like the Weblate tool, we could combine the PROS of both options analyzed.



      Does anyone have any idea of this kind of tool?


      Thank you in advance for your help.



      The OCA Functional Working Group

      fwg@odoo-community.org



      _______________________________________________
      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



      --
      Raphaël Valyi
      Founder and consultant

      by "Raphaël Valyi" <rvalyi@akretion.com> - 05:16 - 25 Apr 2024
    • Re: The OCA Functional Working Group asks for your help!
      I second mkdocs. All my non technical staff use it to build docs. Most.jist write markdown bit some use a specialised markdown editor although that seems to fail lintimg quite a bit.

      It is trivial to automate linting and deploy on merge.

      On Wed, 24 Apr 2024, 6:52 am Victor Champonnois, <notifications@odoo-community.org> wrote:

      Hello Julie,

      >Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?

      I think Weblate directly commits on the main branch, it does not create a PR.

      As Andreas says, the edit functionality in Github seems like the simplest approach. However, it requires to create a fork of the repo, and to make a PR, so it's still a big barrier. 

      Victor Champonnois - Coop IT Easy
Tel : +32 475 81 01 12
      On 24/04/24 07:44, Andreas Perhab wrote:
      Hi Julie,

      I think the edit button in github does most of the forking work for you and even helps with creating a PR when one is finished editing the readme (really any markdown file).
      FireShot Capture 260 - OCA_maintainer-tools_ Odoo Maintainers Tools & conventions for OCA me_ - github.com.png

      It puts images into /assets/{number}/{uuid} so that might need changing or we could just accept this additional directory.

      regards Andreas



      On Tue, 23 Apr 2024 at 19:32, Julie LeBrun <notifications@odoo-community.org> wrote:
      Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?

      Hello everybody!


      During the last OCA Days, the OCA Functional Working Group (FWG) presented the work made on the Documentation Project.


      This project was created by the FWG to help and attract functional people to contribute to modules documentation.


      2 main options were analyzed


      • Using the existing Read Me file in the code so we have only one module documentation which regroups technical and functional information.

      • Using the GitHub Wiki on the repositories which could be really easy to put in place and use.


      The decision was made to use the existing Read Me but to convert it into Markdown so it could be easier to use and to add images.


      Following this decision, an issue was opened in GitHub about the use of the Wiki instead of Read Me : https://github.com/OCA/maintainer-tools/issues/606



      BUT, we still have a big issue regarding this solution: the process to contribute to Read Me is really, really complicated for non-technicals.  


      1. You need to have a Github account and sign the OCA CLA

      2. You would have to fork the repository (well, here we already have lost most of the non-technical people).

      3. Then edit the files of the Read Me using the Web Editor (so you can add images).

      4. Download your images in the right folder than insert them into the file by Drag & Drop

      5. Create a commit and a PR.

      6. Finally, the changes would need to be approved by contributors who have those access rights.



      So, we were thinking: if we add a Markdown tool that can be used to edit Read Me files and automatically push the changes into GitHub a little bit like the Weblate tool, we could combine the PROS of both options analyzed.



      Does anyone have any idea of this kind of tool?


      Thank you in advance for your help.



      The OCA Functional Working Group

      fwg@odoo-community.org



      _______________________________________________
      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 "Graeme Gellatly" <graeme@moahub.nz> - 04:26 - 24 Apr 2024
    • Re: The OCA Functional Working Group asks for your help!

      Hello Julie,

      >Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?

      I think Weblate directly commits on the main branch, it does not create a PR.

      As Andreas says, the edit functionality in Github seems like the simplest approach. However, it requires to create a fork of the repo, and to make a PR, so it's still a big barrier. 

      Victor Champonnois - Coop IT Easy
Tel : +32 475 81 01 12
      On 24/04/24 07:44, Andreas Perhab wrote:
      Hi Julie,

      I think the edit button in github does most of the forking work for you and even helps with creating a PR when one is finished editing the readme (really any markdown file).
      FireShot Capture 260 - OCA_maintainer-tools_ Odoo Maintainers Tools & conventions for OCA me_ - github.com.png

      It puts images into /assets/{number}/{uuid} so that might need changing or we could just accept this additional directory.

      regards Andreas



      On Tue, 23 Apr 2024 at 19:32, Julie LeBrun <notifications@odoo-community.org> wrote:
      Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?

      Hello everybody!


      During the last OCA Days, the OCA Functional Working Group (FWG) presented the work made on the Documentation Project.


      This project was created by the FWG to help and attract functional people to contribute to modules documentation.


      2 main options were analyzed


      • Using the existing Read Me file in the code so we have only one module documentation which regroups technical and functional information.

      • Using the GitHub Wiki on the repositories which could be really easy to put in place and use.


      The decision was made to use the existing Read Me but to convert it into Markdown so it could be easier to use and to add images.


      Following this decision, an issue was opened in GitHub about the use of the Wiki instead of Read Me : https://github.com/OCA/maintainer-tools/issues/606



      BUT, we still have a big issue regarding this solution: the process to contribute to Read Me is really, really complicated for non-technicals.  


      1. You need to have a Github account and sign the OCA CLA

      2. You would have to fork the repository (well, here we already have lost most of the non-technical people).

      3. Then edit the files of the Read Me using the Web Editor (so you can add images).

      4. Download your images in the right folder than insert them into the file by Drag & Drop

      5. Create a commit and a PR.

      6. Finally, the changes would need to be approved by contributors who have those access rights.



      So, we were thinking: if we add a Markdown tool that can be used to edit Read Me files and automatically push the changes into GitHub a little bit like the Weblate tool, we could combine the PROS of both options analyzed.



      Does anyone have any idea of this kind of tool?


      Thank you in advance for your help.



      The OCA Functional Working Group

      fwg@odoo-community.org



      _______________________________________________
      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 Victor - 03:51 - 24 Apr 2024