Skip to Content

Contributors

  • Re: Website HTTP 500 Internal Server Error if logged in
    Same for me!
    
    Le 24/09/2019 à 18:32, Paco Fernández Nogueira a écrit :
    
    > Hi,
    
    >
    
    > Website responses us a HTTP 500 Internal Server Error if we are logged in.
    
    >
    
    > It responses the same to you?
    
    >
    
    > Thanks,
    
    

    by Florent Cayré - 06:50 - 24 Sep 2019
  • Runbot builds HTTP 404 Page not found
    Hi,

    We have found runbot builds where build/base/all logs give an HTTP 404 Page not found. For example:


    Do you have any idea?

    Thanks,
    --

    Paco Fernández Nogueira
    Núm. Col. 1007 (COEINF)
    ffernandez@planetatic.com
    +34 931 81 78 91
    www.planetatic.com

    Aquest missatge i els seus arxius adjunts van dirigits exclusivament al seu destinatari, i pot contenir informació confidencial sotmesa a secret professional. No està permesa la seva reproducció o distribució sense l’autorització expressa de PENEDESTIC SOLUCIONS SLP. Si vostè no és el destinatari final, si us plau, el pot eliminar i informar-nos per aquest mateix mitjà. D’acord amb allò establert per la Llei Orgànica 15/1999, de 13 de desembre, de Protecció de Dades de Caràcter Personal (LOPD), li informem que les seves dades estan incorporades en un fitxer del qual és titular PENEDESTIC SOLUCIONS SLP amb la finalitat de realitzar la gestió administrativa, comptable i fiscal, així como enviar-li comunicacions comercials sobre els nostres productes i/o serveis. Tanmateix, li informem de la possibilitat d’exercir els drets d’accés, rectificació, cancel·lació i oposició de les seves dades al domicili fiscal de PENEDESTIC SOLUCIONS SLP situat a C/ Mare Ràfols, 3 2o 1a - 08720 Vilafranca del Penedès - Barcelona. Si vostè no desitja rebre la nostra informació, pot contactar amb nosaltres enviant un correu electrònic a la següent adreça: info@planetatic.com
     Abans d'imprimir aquest missatge, assegureu-vos que és necessari. Protegir el medi ambient està en mà de tots.


    Este mensaje y sus archivos adjuntos van dirigidos exclusivamente a su destinatario, pudiendo contener información confidencial sometida a secreto profesional. No está permitida su reproducción o distribución sin la autorización expresa de PENEDESTIC SOLUCIONS SLP. Si usted no es el destinatario final por favor elimínelo e infórmenos por esta vía. De acuerdo con lo establecido por la Ley Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter Personal (LOPD), le informamos que sus datos están incorporados en un fichero del que es titular PENEDESTIC SOLUCIONS SLP con la finalidad de realizar la gestión administrativa, contable y fiscal, así como enviarle comunicaciones comerciales sobre nuestros productos y/o servicios. Asimismo, le informamos de la posibilidad de ejercer los derechos de acceso, rectificación, cancelación y oposición de sus datos en el domicilio de PENEDESTIC SOLUCIONS SLP sito en C/ Mare Ràfols, 3 2o 1a - 08720 Vilafranca del Penedès - Barcelona. Si usted no desea recibir nuestra información, póngase en contacto con nosotros enviando un correo electrónico a la siguiente dirección: info@planetatic.com
     Antes de imprimir este mensaje, asegúrese de que es necesario. Proteger el medio ambiente está en mano de todos.


    by Francisco Fernández Nogueira - 06:46 - 24 Sep 2019
  • Website HTTP 500 Internal Server Error if logged in
    Hi,

    Website responses us a HTTP 500 Internal Server Error if we are logged in.

    It responses the same to you?

    Thanks,
    --

    Paco Fernández Nogueira
    Núm. Col. 1007 (COEINF)
    ffernandez@planetatic.com
    +34 931 81 78 91
    www.planetatic.com

    Aquest missatge i els seus arxius adjunts van dirigits exclusivament al seu destinatari, i pot contenir informació confidencial sotmesa a secret professional. No està permesa la seva reproducció o distribució sense l’autorització expressa de PENEDESTIC SOLUCIONS SLP. Si vostè no és el destinatari final, si us plau, el pot eliminar i informar-nos per aquest mateix mitjà. D’acord amb allò establert per la Llei Orgànica 15/1999, de 13 de desembre, de Protecció de Dades de Caràcter Personal (LOPD), li informem que les seves dades estan incorporades en un fitxer del qual és titular PENEDESTIC SOLUCIONS SLP amb la finalitat de realitzar la gestió administrativa, comptable i fiscal, així como enviar-li comunicacions comercials sobre els nostres productes i/o serveis. Tanmateix, li informem de la possibilitat d’exercir els drets d’accés, rectificació, cancel·lació i oposició de les seves dades al domicili fiscal de PENEDESTIC SOLUCIONS SLP situat a C/ Mare Ràfols, 3 2o 1a - 08720 Vilafranca del Penedès - Barcelona. Si vostè no desitja rebre la nostra informació, pot contactar amb nosaltres enviant un correu electrònic a la següent adreça: info@planetatic.com
     Abans d'imprimir aquest missatge, assegureu-vos que és necessari. Protegir el medi ambient està en mà de tots.


    Este mensaje y sus archivos adjuntos van dirigidos exclusivamente a su destinatario, pudiendo contener información confidencial sometida a secreto profesional. No está permitida su reproducción o distribución sin la autorización expresa de PENEDESTIC SOLUCIONS SLP. Si usted no es el destinatario final por favor elimínelo e infórmenos por esta vía. De acuerdo con lo establecido por la Ley Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter Personal (LOPD), le informamos que sus datos están incorporados en un fichero del que es titular PENEDESTIC SOLUCIONS SLP con la finalidad de realizar la gestión administrativa, contable y fiscal, así como enviarle comunicaciones comerciales sobre nuestros productos y/o servicios. Asimismo, le informamos de la posibilidad de ejercer los derechos de acceso, rectificación, cancelación y oposición de sus datos en el domicilio de PENEDESTIC SOLUCIONS SLP sito en C/ Mare Ràfols, 3 2o 1a - 08720 Vilafranca del Penedès - Barcelona. Si usted no desea recibir nuestra información, póngase en contacto con nosotros enviando un correo electrónico a la siguiente dirección: info@planetatic.com
     Antes de imprimir este mensaje, asegúrese de que es necesario. Proteger el medio ambiente está en mano de todos.


    by Francisco Fernández Nogueira - 06:31 - 24 Sep 2019
  • Re: Getting ready for the OCA Code Sprint in Louvain la Neuve
    Good morning,

    In the same spirit, make sure to sign and send the CLA:
    https://odoo-community.org/page/cla

    We won't bring printed copies of it for signature.

    Thank you.

    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236



    On Tue, Sep 24, 2019 at 9:02 AM Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:
    Hello all,
    
    It's this time of the year again :) We are expecting a lot of people to
    join for the OCA code sprint this year, and it will be in a new location
    (at least for us), so we can't know for sure how good the network
    connectivity will be (although the tennants promised it is good).
    
    For the address of the location, check
    https://odoo-community.org/event/louvain-la-neuve-oca-days-2019-2019-09-30-2019-10-01-104/register
    
    
    As always there are things you can do to ease the load on the bandwidth
    as we would like to avoid having 100 devs cloning the Odoo repository
    from scratch on day 1 of the sprint.
    
    I recommend you make sure BEFORE LEAVING FOR THE SPRINT that you have an
    up-to-date clone of Odoo and of all the OCA repository you plan to work
    on. In the maintainer-tools repository, you will find a clone-everything
    script which can help making clones of all the OCA repositories.
    
    Also, since Travis will end up loaded and the version for FLOSS has an
    organisation-wide concurrent build limit, I recommend that you enable
    travis builds on your forks of the OCA repositories. This way, you will
    get builds of your forks which are likely to be faster than the builds
    of the PRs and merges on the OCA repositories.
    
    That's all for now. I'm looking forward to meeting you during the code
    sprint.
    
    
    
    -- 
    Alexandre Fayolle
    Chef de Projet
    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
    

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


    by Maxime Chambreuil - 12:21 - 24 Sep 2019
  • Getting ready for the OCA Code Sprint in Louvain la Neuve
    Hello all,
    
    It's this time of the year again :) We are expecting a lot of people to
    join for the OCA code sprint this year, and it will be in a new location
    (at least for us), so we can't know for sure how good the network
    connectivity will be (although the tennants promised it is good).
    
    For the address of the location, check
    https://odoo-community.org/event/louvain-la-neuve-oca-days-2019-2019-09-30-2019-10-01-104/register
    
    
    As always there are things you can do to ease the load on the bandwidth
    as we would like to avoid having 100 devs cloning the Odoo repository
    from scratch on day 1 of the sprint.
    
    I recommend you make sure BEFORE LEAVING FOR THE SPRINT that you have an
    up-to-date clone of Odoo and of all the OCA repository you plan to work
    on. In the maintainer-tools repository, you will find a clone-everything
    script which can help making clones of all the OCA repositories.
    
    Also, since Travis will end up loaded and the version for FLOSS has an
    organisation-wide concurrent build limit, I recommend that you enable
    travis builds on your forks of the OCA repositories. This way, you will
    get builds of your forks which are likely to be faster than the builds
    of the PRs and merges on the OCA repositories.
    
    That's all for now. I'm looking forward to meeting you during the code
    sprint.
    
    
    -- 
    Alexandre Fayolle
    Chef de Projet
    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 - 09:01 - 24 Sep 2019
  • OCA Days / Odoo XP - Volunteers needed
    Dear OCA Contributors,

    Are you coming to OCA Days or Odoo Experience?

    Can you spare a bit of time to help out?

    We need volunteers to help things run smoothly at OCA Days 2019 and also volunteers to help 'man the stand' at Odoo Experience.
    If you can help out please add your name to the list above.

    Also, have you seen the agenda for discussion/training talks during OCA Days? It is up on the website.

    You can see a bit more detail about each talk here.

    We are looking forward to seeing those that are in LLN that week.
    Rebecca
    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association

    by Rebecca Gellatly - 12:40 - 24 Sep 2019
  • OCA Financial Auditors and Board Member Campaign 2019 - further extended till 16th October 2019
    Hello OCA Contributors,

    I am writing to share with you that the candidate campaign for the Board Members and Financial Auditors for next year has been further extended till Wednesday 16th October - this is due to the low number of applicants for the Board member positions - we currently only have 6 applications for the 9 positions.

    Please come along to the open discussion "The Future of the OCA and its Governance" at the OCA Days in Louvain-la-Neuve (Martin's Agora Hotel) at 5:30pm on Monday 30th September, to find out more about how you can be a part of the future. 

    Or, come visit the OCA stand during Odoo Experience, have a chat with us to get a feel for what is involved in becoming a Member and a Delegate next year with the view to potentially even becoming a Board member at some stage in the future.

    With the sad passing of Eric Caudal earlier this year, the OCA Board has run with 8 committed members since May, please feel free to talk with any of them next week in LLN:
    • Joël Grand-Guillaume
    • Maxime Chambreuil
    • Daniel Reis
    • Pedro M. Baeza
    • Stéphane Bidoul
    • Jordi Ballester
    • Alexandre Fayolle
    • Frederik Kramer
    The Financial Auditor candidate campaign is still open to members and non-members and will finish on the 16th of October with voting starting on 17th October till the 30th October. Announcement 1st November.

    To apply for 2019 OCA Financial Auditor, please fill in this form:

    For more information on responsibilities within the OCA, please read the Bylaws:

    We are looking forward to seeing you in LLN next week.
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association

    by Rebecca Gellatly - 01:41 - 23 Sep 2019
  • RE: Stale PR closing
    I would say again
    
    :+1 18 months (:-1 less than this time)
    
    PD: OCAbot could make auto-milestones PRs.... the work of labeling PRs for
    PSC is also work and it could be done by OCAbot
    
    
    
    > By the way, according to
    
    > https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst
    
    > it’s 6 months and no questions asked :)
    
    Yes, but this is not automatic. This rule could be applied by a human that
    is a PSC. OCABot must be much more cautious
    
    Let’s say a contributor XxX make PR, this contributor get reviews, fix
    everything, all bots green with 100% coverage and after this nobody review
    it. Futhermore this contributor XxX apply all the time the OCA Rule
    reviewing 3 PR per 1 PR the contributor XxX make. So XxX have 5 PRs without
    review all green and 100% coverage but XxX reviewed 15 PR to other
    contributors.
    
    After 1 year, one new contributor comes and say, hey! Travis is red because
    other different contributors make other PRS, merged and they did something
    wrong o just PR need to be rebased… The original author miss the email o
    just that PR was and is absolutely perfect and XxX, say automatic closing?
    “OCA is nor for me, I did everything I must but nobody review it”
    
    
    > We have 2 general cases:
    
    I would say we have quite more general cases.
    
    Off-topic for Odoo days: After thinking some time I think the solution it's
    not closing PRs is limit the PR that can be done based on revisions. No
    revision, no PR. The OCA Rule (3 review per PR) has sense, and the OCA grow
    because reviewers more than pull-requesters.
    
    
    Thank you!
    
    
    De: Alexey Pelykh [mailto:alexey.pelykh@gmail.com]
    Enviado el: jueves, 19 de septiembre de 2019 11:57
    Para: Contributors <contributors@odoo-community.org>
    Asunto: Re: Stale PR closing
    
    We have 2 general cases:
    1. There was no review at all, or not enough reviews. It’s very unfortunate,
    but it still makes a PR stale. And this should be somehow addressed by bot
    as well, e.g. calling for reviewers after 3 months and if no-one was
    interested - well, it is what it is?
    2. There were reviews that were not addressed - this one can just be closed
    as abandoned by author.
    
    
    On Sep 19, 2019, at 10:41, Graeme Gellatly <gdgellatly@gmail.com> wrote:
    
    You misread it by not checking the section it was under. Can be closed if no
    activity in response to the review. You can't just arbitrarily close an
    unreviewed PR. There is a big discussion somewhere where that was agreed,
    but it was years ago now.
    
    On Thu, Sep 19, 2019 at 8:02 PM Alexey Pelykh <alexey.pelykh@gmail.com>
    wrote:
    By the way, according to
    https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst
    it’s 6 months and no questions asked :)
    
    
    On Aug 29, 2019, at 18:16, Stéphane Bidoul <stephane.bidoul@acsone.eu>
    wrote:
    
    I'm in favor to move forward with this.
    
    Alexey was kind enough to do a PR, which includes adding a "stale 🗃" label
    so they are easy to find.
    
    Note PR merged by /ocabot merge (virtually all of them these days) are
    labeled as "merged 🎉" so they too are easy to find even in case a rebase
    has been done.
    
    12 months is a reasonably long time. And if anyone is still interested it's
    easy to (ask to) reopen to get a new one year lease.
    
    @Graeme Gellatly does this address your concerns?
    
    -sbi
    
    
    
    On Thu, Aug 29, 2019 at 6:27 PM Alexey Pelykh <alexey.pelykh@gmail.com>
    wrote:
    We can implement just-labeling initially, at least to see the amount of
    impact. Personally, I don’t see any harm in closing PR that had 0 comments
    for 12 months, assuming it’s valuable and reviewers are doing their part of
    the deal.
    
    
    On Aug 29, 2019, at 18:17, Joël Grand-Guillaume
    <joel.grandguillaume@camptocamp.com> wrote:
    
    For your case @Graeme Gellatly may be we can just add a label "Close by bot"
    so it's still pretty easy to find them right ?
    
    Because today, the fact so many PRs remain open for months if not years is a
    real issue I think.
    
    Any how, we all agree there is something to do here. The OCA days is
    probably the best place to discuss it right ;)
    
    On Thu, Aug 29, 2019 at 2:36 PM Daniel Reis <dgreis@sapo.pt> wrote:
    If we do this, we need to make sure that closed PR really means that the PR
    was not merged.
    I see on the Odoo repo may closed PRs that had their code manually merged -
    not sure if we have this in the OCA.
    
    What if the bot just regularly (monthly?) pinged the followers.
    People would manually close a stale PR if that makes sense.
    Daniel
    
    No dia 29/08/2019, às 12:12, Kitti Upariphutthiphong <kittiu@ecosoft.co.th>
    escreveu:
    Or once it hit 12 months of inactivity, ocabot can auto assign to any active
    contributors (i..e, 2 person) to review it?
    
    After that like 3 months, if still no activity, close it.
    
    
    On Thu, Aug 29, 2019 at 4:17 PM Eduardo Magdalena <emagdalena@c2i.es> wrote:
    +1 12 months - 18 months. First add a comment or label as a warning, telling
    that the PR will be closed an the closed if there are no activity 6 months
    after
    
    
    
    
    
    
    Un saludo,
    Eduardo Magdalena
    Fundador & CEO
    ✉   emagdalena@c2i.es
    ✆  +34 678 713 373
    
    C2i Change 2 improve
    Optimización de procesos
        www.c2i.es
    
    
       Averigua a quién conocemos en común
    
    
    
    
    
    ☑ ¿Por qué no organizamos una reunión online?
    
    
    Este correo y sus archivos asociados son privados y confidenciales y van
    dirigidos exclusivamente a su destinatario. Si recibe este correo sin ser el
    destinatario del mismo le rogamos proceda a su eliminación y lo ponga en
    conocimiento de su emisor. La difusión por cualquier medio de su contenido
    podría ser sancionada conforme a lo previsto en la legislación vigente, Ley
    Orgánica 15/1999, de Protección de Datos de Carácter Personal. Le rogamos
    que no imprima este correo ni sus documentos adjuntos, salvo que lo estime
    necesario.
    
    
    
    El jue., 29 ago. 2019 a las 3:32, Graeme Gellatly (<gdgellatly@gmail.com>)
    escribió:
    Hi,
    
    I don't like the idea personally, especially on OCA wide level. I often pick
    up abandoned PR's fix them up and resubmit them. At the very least I like to
    go through them when porting modules to see if anything in there is value
    that needs porting. If they are closed it is a hassle working out why it was
    closed (superseded, abandoned etc).
    
    Maybe for new to OCA modules, but for existing modules, a human should
    really determine whether it is worth reviving IMO. I think a much better
    application for a Bot is to find interested reviewers. Do some smart stuff
    like
    
    When a PR is submitted, crawl history and cc any past reviewer or committer
    for that module (maybe even have a reviewer group so people can choose to
    opt in) (maybe in past 18 months)
    
    On Thu, Aug 29, 2019 at 10:41 AM Rafael Blasco <rafael.blasco@tecnativa.com>
    wrote:
    +1 18 months
    
    De: Mignon, Laurent [mailto:laurent.mignon@acsone.eu]
    Enviado el: martes, 27 de agosto de 2019 10:57
    Para: Contributors <contributors@odoo-community.org>
    Asunto: Re: Stale PR closing
    
    +1
    
    On Tue, Aug 27, 2019 at 10:27 AM Stéphane Bidoul <stephane.bidoul@acsone.eu>
    wrote:
    Hello Alexey,
    
    +1
    
    This is being tracked in: https://github.com/OCA/oca-github-bot/issues/10,
    awaiting PR :)
    
    If someone wants to work on this at #OCADays, I'll be happy to help.
    
    -sbi
    
    On Tue, Aug 27, 2019 at 10:16 AM Alexey Pelykh <alexey.pelykh@gmail.com>
    wrote:
    Dear community,
    
    In OCA repositories there are PRs that have not been updated for years, and
    are either abandoned by authors or by reviewers. Should we agree on policy
    (and implement it via OCA Bot) to close PR/issue if there was no activity
    for more than 6-12-18 months?
    
    Kind regards,
    Alexey
    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    _______________________________________________
    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
    
    
    
    -- 
    
    camptocamp
    INNOVATIVE SOLUTIONS
    BY OPEN SOURCE EXPERTS
    
    Joël Grand-Guillaume
    Department Head
    Business Solutions
    
    +41 21 619 10 28
    www.camptocamp.com
    
    
    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    _______________________________________________
    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 Rafael Blasco (Moduon) - 05:51 - 22 Sep 2019
  • Re: Proposal of new Quality modules
    Hello Stefano,

    Can I ask to create an issue on the Github repo please?

    If you'll be at the OCA Days in Belgium in 2 weeks, we can discuss about it there.

    Cheers,

    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236



    On Wed, Sep 11, 2019 at 2:32 AM <stefano.consolaro@mymage.it> wrote:
    Hi all,
    I would like to have your opinion on the inclusion in a OCA repository of two modules relative to Quality Management System that we (PNLug - Odoo Group https://odoo.pnlug.it/) developed starting from a project for a customer.

    First module proposed as "Management System - Extend"
    It is an extension for management-system repository (https://github.com/OCA/management-system).
    It adds:
    - to Nonconformity: some fields often used in industrial company (e.g. department, workcenter, product), some aditional information like type and quantity managed;
    - to Actions: a templating option and efficacy evaluation;
    - to Partner: quality dedicated contact and Control Plan (see next module)

    Second module proposed as "Quality Control - Plan"
    It is an extension for manufacture/quality repository (https://github.com/OCA/manufacture).
    It adds control Plan management to automatically calculate how many goods have to be checked for a defined incoming quantity, and the option to associate a Plan to Product, Product Category and Partner.
    On an Inspection on incoming goods the quantity to be checked is automatically proposed; in case of scraps there is the possibility to associate (create) a new Nonconformity.


    Thanks in advance for your comments.

    Stefano Consolaro

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


    by Maxime Chambreuil - 03:26 - 20 Sep 2019
  • Re: Stale PR closing
    We have 2 general cases:
    1. There was no review at all, or not enough reviews. It’s very unfortunate, but it still makes a PR stale. And this should be somehow addressed by bot as well, e.g. calling for reviewers after 3 months and if no-one was interested - well, it is what it is?
    2. There were reviews that were not addressed - this one can just be closed as abandoned by author.

    On Sep 19, 2019, at 10:41, Graeme Gellatly <gdgellatly@gmail.com> wrote:

    You misread it by not checking the section it was under. Can be closed if no activity in response to the review. You can't just arbitrarily close an unreviewed PR. There is a big discussion somewhere where that was agreed, but it was years ago now.

    On Thu, Sep 19, 2019 at 8:02 PM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
    By the way, according to https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst it’s 6 months and no questions asked :)

    On Aug 29, 2019, at 18:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

    I'm in favor to move forward with this.

    Alexey was kind enough to do a PR, which includes adding a "stale 🗃" label so they are easy to find.

    Note PR merged by /ocabot merge (virtually all of them these days) are labeled as "merged 🎉" so they too are easy to find even in case a rebase has been done.

    12 months is a reasonably long time. And if anyone is still interested it's easy to (ask to) reopen to get a new one year lease.

    @Graeme Gellatly does this address your concerns?

    -sbi



    On Thu, Aug 29, 2019 at 6:27 PM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
    We can implement just-labeling initially, at least to see the amount of impact. Personally, I don’t see any harm in closing PR that had 0 comments for 12 months, assuming it’s valuable and reviewers are doing their part of the deal.

    On Aug 29, 2019, at 18:17, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:

    For your case @Graeme Gellatly may be we can just add a label "Close by bot" so it's still pretty easy to find them right ?

    Because today, the fact so many PRs remain open for months if not years is a real issue I think.

    Any how, we all agree there is something to do here. The OCA days is probably the best place to discuss it right ;)

    On Thu, Aug 29, 2019 at 2:36 PM Daniel Reis <dgreis@sapo.pt> wrote:
    If we do this, we need to make sure that closed PR really means that the PR was not merged.
    I see on the Odoo repo may closed PRs that had their code manually merged - not sure if we have this in the OCA.

    What if the bot just regularly (monthly?) pinged the followers.
    People would manually close a stale PR if that makes sense.

    Daniel

    No dia 29/08/2019, às 12:12, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> escreveu:

    Or once it hit 12 months of inactivity, ocabot can auto assign to any active contributors (i..e, 2 person) to review it?

    After that like 3 months, if still no activity, close it.


    On Thu, Aug 29, 2019 at 4:17 PM Eduardo Magdalena <emagdalena@c2i.es> wrote:
    +1 12 months - 18 months. First add a comment or label as a warning, telling that the PR will be closed an the closed if there are no activity 6 months after

    Un saludo,

    Eduardo Magdalena

    Fundador & CEO

    ✉   emagdalena@c2i.es

    ✆  +34 678 713 373

    C2i Change 2 improve

    C2i Change 2 improve

    Optimización de procesos

        www.c2i.es

    Perfil en LinkedIn   Averigua a quién conocemos en común
    Onshape. El futuro del CAD   Odoo. Mucho más que un ERP   Integración CAD-ERP. Control de proyectos en tiempo real

    ☑ ¿Por qué no organizamos una reunión online?

    Este correo y sus archivos asociados son privados y confidenciales y van dirigidos exclusivamente a su destinatario. Si recibe este correo sin ser el destinatario del mismo le rogamos proceda a su eliminación y lo ponga en conocimiento de su emisor. La difusión por cualquier medio de su contenido podría ser sancionada conforme a lo previsto en la legislación vigente, Ley Orgánica 15/1999, de Protección de Datos de Carácter Personal. Le rogamos que no imprima este correo ni sus documentos adjuntos, salvo que lo estime necesario.


    El jue., 29 ago. 2019 a las 3:32, Graeme Gellatly (<gdgellatly@gmail.com>) escribió:
    Hi,

    I don't like the idea personally, especially on OCA wide level. I often pick up abandoned PR's fix them up and resubmit them. At the very least I like to go through them when porting modules to see if anything in there is value that needs porting. If they are closed it is a hassle working out why it was closed (superseded, abandoned etc).  

    Maybe for new to OCA modules, but for existing modules, a human should really determine whether it is worth reviving IMO. I think a much better application for a Bot is to find interested reviewers. Do some smart stuff like

    When a PR is submitted, crawl history and cc any past reviewer or committer for that module (maybe even have a reviewer group so people can choose to opt in) (maybe in past 18 months)

    On Thu, Aug 29, 2019 at 10:41 AM Rafael Blasco <rafael.blasco@tecnativa.com> wrote:

    +1 18 months

     

    De: Mignon, Laurent [mailto:laurent.mignon@acsone.eu]
    Enviado el: martes, 27 de agosto de 2019 10:57
    Para: Contributors <contributors@odoo-community.org>
    Asunto: Re: Stale PR closing

     

    +1

     

    On Tue, Aug 27, 2019 at 10:27 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

    Hello Alexey,

     

    +1

     

    This is being tracked in: https://github.com/OCA/oca-github-bot/issues/10, awaiting PR :)

     

    If someone wants to work on this at #OCADays, I'll be happy to help.

     

    -sbi

     

    On Tue, Aug 27, 2019 at 10:16 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:

    Dear community,
     
    In OCA repositories there are PRs that have not been updated for years, and are either abandoned by authors or by reviewers. Should we agree on policy (and implement it via OCA Bot) to close PR/issue if there was no activity for more than 6-12-18 months?
     
    Kind regards,
    Alexey

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

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

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

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

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

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



    --

    camptocamp
    INNOVATIVE SOLUTIONS
    BY OPEN SOURCE EXPERTS

    Joël Grand-Guillaume
    Department Head
    Business Solutions

    +41 21 619 10 28



    _______________________________________________
    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 Alexey Pelykh <alexey.pelykh@gmail.com> - 11:55 - 19 Sep 2019
  • Re: Stale PR closing
    You misread it by not checking the section it was under. Can be closed if no activity in response to the review. You can't just arbitrarily close an unreviewed PR. There is a big discussion somewhere where that was agreed, but it was years ago now.

    On Thu, Sep 19, 2019 at 8:02 PM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
    By the way, according to https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst it’s 6 months and no questions asked :)

    On Aug 29, 2019, at 18:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

    I'm in favor to move forward with this.

    Alexey was kind enough to do a PR, which includes adding a "stale 🗃" label so they are easy to find.

    Note PR merged by /ocabot merge (virtually all of them these days) are labeled as "merged 🎉" so they too are easy to find even in case a rebase has been done.

    12 months is a reasonably long time. And if anyone is still interested it's easy to (ask to) reopen to get a new one year lease.

    @Graeme Gellatly does this address your concerns?

    -sbi



    On Thu, Aug 29, 2019 at 6:27 PM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
    We can implement just-labeling initially, at least to see the amount of impact. Personally, I don’t see any harm in closing PR that had 0 comments for 12 months, assuming it’s valuable and reviewers are doing their part of the deal.

    On Aug 29, 2019, at 18:17, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:

    For your case @Graeme Gellatly may be we can just add a label "Close by bot" so it's still pretty easy to find them right ?

    Because today, the fact so many PRs remain open for months if not years is a real issue I think.

    Any how, we all agree there is something to do here. The OCA days is probably the best place to discuss it right ;)

    On Thu, Aug 29, 2019 at 2:36 PM Daniel Reis <dgreis@sapo.pt> wrote:
    If we do this, we need to make sure that closed PR really means that the PR was not merged.
    I see on the Odoo repo may closed PRs that had their code manually merged - not sure if we have this in the OCA.

    What if the bot just regularly (monthly?) pinged the followers.
    People would manually close a stale PR if that makes sense.

    Daniel

    No dia 29/08/2019, às 12:12, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> escreveu:

    Or once it hit 12 months of inactivity, ocabot can auto assign to any active contributors (i..e, 2 person) to review it?

    After that like 3 months, if still no activity, close it.


    On Thu, Aug 29, 2019 at 4:17 PM Eduardo Magdalena <emagdalena@c2i.es> wrote:
    +1 12 months - 18 months. First add a comment or label as a warning, telling that the PR will be closed an the closed if there are no activity 6 months after

    Un saludo,

    Eduardo Magdalena

    Fundador & CEO

    ✉   emagdalena@c2i.es

    ✆  +34 678 713 373

    C2i Change 2 improve

    C2i Change 2 improve

    Optimización de procesos

        www.c2i.es

    Perfil en LinkedIn   Averigua a quién conocemos en común
    Onshape. El futuro del CAD   Odoo. Mucho más que un ERP   Integración CAD-ERP. Control de proyectos en tiempo real

    ☑ ¿Por qué no organizamos una reunión online?

    Este correo y sus archivos asociados son privados y confidenciales y van dirigidos exclusivamente a su destinatario. Si recibe este correo sin ser el destinatario del mismo le rogamos proceda a su eliminación y lo ponga en conocimiento de su emisor. La difusión por cualquier medio de su contenido podría ser sancionada conforme a lo previsto en la legislación vigente, Ley Orgánica 15/1999, de Protección de Datos de Carácter Personal. Le rogamos que no imprima este correo ni sus documentos adjuntos, salvo que lo estime necesario.


    El jue., 29 ago. 2019 a las 3:32, Graeme Gellatly (<gdgellatly@gmail.com>) escribió:
    Hi,

    I don't like the idea personally, especially on OCA wide level. I often pick up abandoned PR's fix them up and resubmit them. At the very least I like to go through them when porting modules to see if anything in there is value that needs porting. If they are closed it is a hassle working out why it was closed (superseded, abandoned etc).  

    Maybe for new to OCA modules, but for existing modules, a human should really determine whether it is worth reviving IMO. I think a much better application for a Bot is to find interested reviewers. Do some smart stuff like

    When a PR is submitted, crawl history and cc any past reviewer or committer for that module (maybe even have a reviewer group so people can choose to opt in) (maybe in past 18 months)

    On Thu, Aug 29, 2019 at 10:41 AM Rafael Blasco <rafael.blasco@tecnativa.com> wrote:

    +1 18 months

     

    De: Mignon, Laurent [mailto:laurent.mignon@acsone.eu]
    Enviado el: martes, 27 de agosto de 2019 10:57
    Para: Contributors <contributors@odoo-community.org>
    Asunto: Re: Stale PR closing

     

    +1

     

    On Tue, Aug 27, 2019 at 10:27 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

    Hello Alexey,

     

    +1

     

    This is being tracked in: https://github.com/OCA/oca-github-bot/issues/10, awaiting PR :)

     

    If someone wants to work on this at #OCADays, I'll be happy to help.

     

    -sbi

     

    On Tue, Aug 27, 2019 at 10:16 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:

    Dear community,
     
    In OCA repositories there are PRs that have not been updated for years, and are either abandoned by authors or by reviewers. Should we agree on policy (and implement it via OCA Bot) to close PR/issue if there was no activity for more than 6-12-18 months?
     
    Kind regards,
    Alexey

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

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

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

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

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

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



    --

    camptocamp
    INNOVATIVE SOLUTIONS
    BY OPEN SOURCE EXPERTS

    Joël Grand-Guillaume
    Department Head
    Business Solutions

    +41 21 619 10 28



    _______________________________________________
    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 - 11:40 - 19 Sep 2019
  • Re: Stale PR closing
    By the way, according to https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst it’s 6 months and no questions asked :)

    On Aug 29, 2019, at 18:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

    I'm in favor to move forward with this.

    Alexey was kind enough to do a PR, which includes adding a "stale 🗃" label so they are easy to find.

    Note PR merged by /ocabot merge (virtually all of them these days) are labeled as "merged 🎉" so they too are easy to find even in case a rebase has been done.

    12 months is a reasonably long time. And if anyone is still interested it's easy to (ask to) reopen to get a new one year lease.

    @Graeme Gellatly does this address your concerns?

    -sbi



    On Thu, Aug 29, 2019 at 6:27 PM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
    We can implement just-labeling initially, at least to see the amount of impact. Personally, I don’t see any harm in closing PR that had 0 comments for 12 months, assuming it’s valuable and reviewers are doing their part of the deal.

    On Aug 29, 2019, at 18:17, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:

    For your case @Graeme Gellatly may be we can just add a label "Close by bot" so it's still pretty easy to find them right ?

    Because today, the fact so many PRs remain open for months if not years is a real issue I think.

    Any how, we all agree there is something to do here. The OCA days is probably the best place to discuss it right ;)

    On Thu, Aug 29, 2019 at 2:36 PM Daniel Reis <dgreis@sapo.pt> wrote:
    If we do this, we need to make sure that closed PR really means that the PR was not merged.
    I see on the Odoo repo may closed PRs that had their code manually merged - not sure if we have this in the OCA.

    What if the bot just regularly (monthly?) pinged the followers.
    People would manually close a stale PR if that makes sense.

    Daniel

    No dia 29/08/2019, às 12:12, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> escreveu:

    Or once it hit 12 months of inactivity, ocabot can auto assign to any active contributors (i..e, 2 person) to review it?

    After that like 3 months, if still no activity, close it.


    On Thu, Aug 29, 2019 at 4:17 PM Eduardo Magdalena <emagdalena@c2i.es> wrote:
    +1 12 months - 18 months. First add a comment or label as a warning, telling that the PR will be closed an the closed if there are no activity 6 months after

    Un saludo,

    Eduardo Magdalena

    Fundador & CEO

    ✉   emagdalena@c2i.es

    ✆  +34 678 713 373

    C2i Change 2 improve

    C2i Change 2 improve

    Optimización de procesos

        www.c2i.es

    Perfil en LinkedIn   Averigua a quién conocemos en común
    Onshape. El futuro del CAD   Odoo. Mucho más que un ERP   Integración CAD-ERP. Control de proyectos en tiempo real

    ☑ ¿Por qué no organizamos una reunión online?

    Este correo y sus archivos asociados son privados y confidenciales y van dirigidos exclusivamente a su destinatario. Si recibe este correo sin ser el destinatario del mismo le rogamos proceda a su eliminación y lo ponga en conocimiento de su emisor. La difusión por cualquier medio de su contenido podría ser sancionada conforme a lo previsto en la legislación vigente, Ley Orgánica 15/1999, de Protección de Datos de Carácter Personal. Le rogamos que no imprima este correo ni sus documentos adjuntos, salvo que lo estime necesario.


    El jue., 29 ago. 2019 a las 3:32, Graeme Gellatly (<gdgellatly@gmail.com>) escribió:
    Hi,

    I don't like the idea personally, especially on OCA wide level. I often pick up abandoned PR's fix them up and resubmit them. At the very least I like to go through them when porting modules to see if anything in there is value that needs porting. If they are closed it is a hassle working out why it was closed (superseded, abandoned etc).  

    Maybe for new to OCA modules, but for existing modules, a human should really determine whether it is worth reviving IMO. I think a much better application for a Bot is to find interested reviewers. Do some smart stuff like

    When a PR is submitted, crawl history and cc any past reviewer or committer for that module (maybe even have a reviewer group so people can choose to opt in) (maybe in past 18 months)

    On Thu, Aug 29, 2019 at 10:41 AM Rafael Blasco <rafael.blasco@tecnativa.com> wrote:

    +1 18 months

     

    De: Mignon, Laurent [mailto:laurent.mignon@acsone.eu]
    Enviado el: martes, 27 de agosto de 2019 10:57
    Para: Contributors <contributors@odoo-community.org>
    Asunto: Re: Stale PR closing

     

    +1

     

    On Tue, Aug 27, 2019 at 10:27 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:

    Hello Alexey,

     

    +1

     

    This is being tracked in: https://github.com/OCA/oca-github-bot/issues/10, awaiting PR :)

     

    If someone wants to work on this at #OCADays, I'll be happy to help.

     

    -sbi

     

    On Tue, Aug 27, 2019 at 10:16 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:

    Dear community,
     
    In OCA repositories there are PRs that have not been updated for years, and are either abandoned by authors or by reviewers. Should we agree on policy (and implement it via OCA Bot) to close PR/issue if there was no activity for more than 6-12-18 months?
     
    Kind regards,
    Alexey

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

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

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

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

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

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



    --

    camptocamp
    INNOVATIVE SOLUTIONS
    BY OPEN SOURCE EXPERTS

    Joël Grand-Guillaume
    Department Head
    Business Solutions

    +41 21 619 10 28



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



    by Alexey Pelykh <alexey.pelykh@gmail.com> - 10:01 - 19 Sep 2019
  • Re: Proposing Alexey Pelykh for currency PSC
    It should be correct now.

    Regards.

    by Pedro M. Baeza - 12:36 - 17 Sep 2019
  • Re: Boxtal API module

    Hi Michel,

    the module was written for v10, with new API. Should you need it for v8, you would need to port the module backwards to be v8 compatible.

    Best Regards,


    Le Filament
    Rémi CAZENAVE
    ------
    SCOP LE FILAMENT
    06.87.23.26.04
    remi@le-filament.com
    On 16/09/2019 12:51, Michel Memeteau - EKIMIA wrote:
    Hi, 

    Le jeu. 16 mai 2019 à 11:17, Rémi CAZENAVE - Le Filament <remi@le-filament.com> a écrit :

    Hi Michel,

    sorry about that, we had to change the name of our account in bitbucket (and there is no redirection proposed).

    You can find it here : https://bitbucket.org/lefilament/export_boxtal



    Many thanks ! For some reason I cannot make odoo 8.0 detect , is there any dependency that would make it impossible to detect when I refresh module list ? 

     

    Best Regards,


    Rémi CAZENAVE
    ------
    SCOP LE FILAMENT
    06.87.23.26.04
    remi@le-filament.com
    On 16/05/2019 09:27, Michel Memeteau - EKIMIA wrote:

    _______________________________________________
    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 - 08:40 - 16 Sep 2019
  • Re: Boxtal API module
    Hi, 

    Le jeu. 16 mai 2019 à 11:17, Rémi CAZENAVE - Le Filament <remi@le-filament.com> a écrit :

    Hi Michel,

    sorry about that, we had to change the name of our account in bitbucket (and there is no redirection proposed).

    You can find it here : https://bitbucket.org/lefilament/export_boxtal



    Many thanks ! For some reason I cannot make odoo 8.0 detect , is there any dependency that would make it impossible to detect when I refresh module list ? 

     

    Best Regards,


    Rémi CAZENAVE
    ------
    SCOP LE FILAMENT
    06.87.23.26.04
    remi@le-filament.com
    On 16/05/2019 09:27, Michel Memeteau - EKIMIA wrote:

    by mm - 12:51 - 16 Sep 2019
  • Re: Proposing Alexey Pelykh for currency PSC
    Should this be revisited?
    

    by Alexey Pelykh <alexey.pelykh@gmail.com> - 10:55 - 16 Sep 2019
  • OCA Board Member and Financial Auditor Campaign - APPLICATION DATE EXTENDED - 22ND SEPTEMBER

    Dear OCA Contributors,


    I hope the week is starting well for you all.


    We currently only have a small number of applicants for the OCA Board Member campaign.


    Due to this, the close date of the campaign has been extended - the final date to have submitted an application is 5pm (CEST) Sunday 22nd September, 2019.

    Please see below to apply:

    To apply for 2019 OCA Board Member, please fill in this form:
    You need to be a valid (paid) OCA Delegate to apply to be a Board Member.

    To apply for 2019 OCA Financial Auditor, please fill in this form:
    You do not need to be a member to apply to be an Auditor.

    For more information on their responsibilities, please read the Bylaws:

    The campaign will now be closed on Sunday 22nd September, 2019, with voting running from Monday 23rd - Sunday 29th, September 2019.

    If you have any questions, please do not hesitate to reply on this list.

    Warm regards
    Rebecca
    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association

    by Rebecca Gellatly - 10:46 - 16 Sep 2019
  • OCA 2019 Financial Auditor Campaign - Still Open
    Hello Contributors,

    I just wanted to remind our Contributors that the Financial Auditor Campaign is still open. You do not need to be an OCA Member to apply.

    You can apply via this link: https://odoo-community.org/survey/start/2019-oca-financial-auditors-candidates-31

    If you have any questions please don't hesitate to get in touch on this list.

    Warm regards,
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association

    by Rebecca Gellatly - 02:10 - 13 Sep 2019
  • Request for review: web_widget_dropdown_dynamic
    Dear community,

    I’d like to present https://github.com/OCA/web/pull/1371 that adds web_widget_dropdown_dynamic, a widget that supports resolving options from backend of:

     * `fields.Char`
     * `fields.Integer`
     * `fields.Selection`

    It’s useful when on-the-fly generation of m2m fields with dynamic options is an overkill, yet default static selection field is not applicable.

    Kind regards,
    Alexey


    by Alexey Pelykh <alexey.pelykh@gmail.com> - 11:11 - 12 Sep 2019
  • Proposal of new Quality modules
    Hi all,
    I would like to have your opinion on the inclusion in a OCA repository of two modules relative to Quality Management System that we (PNLug - Odoo Group https://odoo.pnlug.it/) developed starting from a project for a customer.

    First module proposed as "Management System - Extend"
    It is an extension for management-system repository (https://github.com/OCA/management-system).
    It adds:
    - to Nonconformity: some fields often used in industrial company (e.g. department, workcenter, product), some aditional information like type and quantity managed;
    - to Actions: a templating option and efficacy evaluation;
    - to Partner: quality dedicated contact and Control Plan (see next module)

    Second module proposed as "Quality Control - Plan"
    It is an extension for manufacture/quality repository (https://github.com/OCA/manufacture).
    It adds control Plan management to automatically calculate how many goods have to be checked for a defined incoming quantity, and the option to associate a Plan to Product, Product Category and Partner.
    On an Inspection on incoming goods the quantity to be checked is automatically proposed; in case of scraps there is the possibility to associate (create) a new Nonconformity.

    You can find the modules here: https://gitlab.com/PNLUG/Odoo/management-system-improvements/tree/11.0

    Thanks in advance for your comments.

    Stefano Consolaro


    by Stefano Consolaro - 09:31 - 11 Sep 2019