Skip to Content

Contributors

  • Re: OCA module contributors and migrations
    Hello,

    I think it should be up to modules authors to decide if a contribution is worth getting mentioned or not as in any open source project. Don't like it? Then fork, but make sure you can do better or go back to your place. Indeed we already see some kind of "contribution squatting". I won't give names here but I have seen people forcing new pointless features into famous modules just to drive attention to their own company. This is very real already... Usually people doing this are not serious people, their trivial work won't be missed.

    And it didn't stop there, in some project you got noobs artificially inflating their image with non relevant contribs and starting to get their noob employee destroy serious modules... In Brazil so many companies failed their project because this kind of un responsable behaviors from noobs trying to auto promote them as expert at any cost to make a dent in the saas business...

    If you state rules like any tiny contrib is with a mention, soon enough you'll have contribution trolling exploding, just like during the Hacktober fest when gazillions of people were making pointless PRs to any project just to win a free T-shirt. Now think about getting it's company named along with Tecnativa or CamToCamp...

    This is sad, but this is the wild world we live in. Instead when module authors decide, then real efforts can be rewarded and notoriety squating may be avoided.

    Also bare in mind that one can always see the number of commits and lines changed in any git(hub) repo, so it's not like it's invisible either...


    On Wed, Jul 14, 2021, 6:26 AM Harald Panten Lopez <harald.panten@sygel.es> wrote:
    I think any migration should be considered as a contribution. As some of you said before, that may encourage more users to contribute.

    Any migration (even if it's a standard migration) needs an investment of time. On the other hand, when a user starts a migration he/she is "open" to receive suggestions, changes... Any migration is liable to become a headache.

    I agree that correcting a small typo (for example) wouldn't be enough for being considered as a contributor.

    Regards.

    El mié, 14 jul 2021 a las 9:17, Jairo Llopis (<jairo.llopis@tecnativa.com>) escribió:
    El mar, 13 de jul de 2021 a las 15:37:13 PM, David Beal <david.beal@akretion.com> escribió:
    A point of view could be that contributors should be someone who can answer any questions about the module in the future.
    Then it should have the expertise on the topic to do it.

    That sounds more like a maintainer.

    El mar, 13 de jul de 2021 a las 15:37:12 PM, Tom Blauwendraat <tom@sunflowerweb.nl> escribió:

    - The "authors" list in manifest is something you want to keep small and just for important companies which contributed to the development, since it's also ugly when it's very long

    - The contributors list in README can be as long as you want because it's not directly in anyone's view IMO - and I think any "thank you" that we can give people that invest their time in OCA, should be given

    Just if people themselves feel their contribution is not worth a lot they can just not add it


    100% agree.

    As a side note, remember that there are plenty of ways to contribute to a module without writing a single line of code.

    OCA should be generous in this kind of attribution. That will encourage people to contribute more.

    This should be hardcoded in the guidelines though.

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



    --

     

    Harald Panten López

    CEO

    Sygel Technology S.L

     
    +34 637 88 42 41
    harald.panten@sygel.es
    https://www.sygel.es
    C/ Àlaba 61, 5ª planta, 08005, Barcelona
     
     
     

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


    by "Raphaël Valyi" <rvalyi@akretion.com> - 07:41 - 14 Jul 2021
  • Re: Propose Alba Riera as PSC for Donation
    +1 It seems some more hands will help to manage the repository

    El mié, 14 jul 2021 a las 11:17, Enric Tobella Alomar (<etobella@creublanca.es>) escribió:
    I know, but in this specific case, there is only one member on the PSC and there is not many answers from there :(
     
     
     
    Enric Tobella Alomar
    Desarrollo
    Av. J. V. Foix 63
    08034 Barcelona
    Tlf.    932 522 522 (Ext. 1621)
     
     
    From: "Pedro M. Baeza (Tecnativa)" <pedro.baeza@tecnativa.com>
    To: "Contributors" <contributors@odoo-community.org>
    Date: Wed, 14 Jul 2021 07:37:17 -0000
    Subject: Re: Propose Alba Riera as PSC for Donation
     
    +1 as a general feeling, although only existing PSCs can vote for this.
     
    Regards.
    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe




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

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



    --
    Lois Rilo Antelo
    Odoo consultant at ForgeFlow S.L.

    by Lois Rilo Antelo - 11:25 - 14 Jul 2021
  • Re: OCA module contributors and migrations
    I think any migration should be considered as a contribution. As some of you said before, that may encourage more users to contribute.

    Any migration (even if it's a standard migration) needs an investment of time. On the other hand, when a user starts a migration he/she is "open" to receive suggestions, changes... Any migration is liable to become a headache.

    I agree that correcting a small typo (for example) wouldn't be enough for being considered as a contributor.

    Regards.

    El mié, 14 jul 2021 a las 9:17, Jairo Llopis (<jairo.llopis@tecnativa.com>) escribió:
    El mar, 13 de jul de 2021 a las 15:37:13 PM, David Beal <david.beal@akretion.com> escribió:
    A point of view could be that contributors should be someone who can answer any questions about the module in the future.
    Then it should have the expertise on the topic to do it.

    That sounds more like a maintainer.

    El mar, 13 de jul de 2021 a las 15:37:12 PM, Tom Blauwendraat <tom@sunflowerweb.nl> escribió:

    - The "authors" list in manifest is something you want to keep small and just for important companies which contributed to the development, since it's also ugly when it's very long

    - The contributors list in README can be as long as you want because it's not directly in anyone's view IMO - and I think any "thank you" that we can give people that invest their time in OCA, should be given

    Just if people themselves feel their contribution is not worth a lot they can just not add it


    100% agree.

    As a side note, remember that there are plenty of ways to contribute to a module without writing a single line of code.

    OCA should be generous in this kind of attribution. That will encourage people to contribute more.

    This should be hardcoded in the guidelines though.

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



    --

     

    Harald Panten López

    CEO

    Sygel Technology S.L

     
    +34 637 88 42 41
    harald.panten@sygel.es
    https://www.sygel.es
    C/ Àlaba 61, 5ª planta, 08005, Barcelona
     
     
     

    by Harald Panten Lopez - 11:25 - 14 Jul 2021
  • Re: Propose Alba Riera as PSC for Donation
    I know, but in this specific case, there is only one member on the PSC and there is not many answers from there :(
     
     
     
    Enric Tobella Alomar
    Desarrollo
    Av. J. V. Foix 63
    08034 Barcelona
    Tlf.    932 522 522 (Ext. 1621)
     
     
    From: "Pedro M. Baeza (Tecnativa)" <pedro.baeza@tecnativa.com>
    To: "Contributors" <contributors@odoo-community.org>
    Date: Wed, 14 Jul 2021 07:37:17 -0000
    Subject: Re: Propose Alba Riera as PSC for Donation
     
    +1 as a general feeling, although only existing PSCs can vote for this.
     
    Regards.
    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe




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

    by Enric Tobella Alomar - 11:16 - 14 Jul 2021
  • Re: Propose Alba Riera as PSC for Donation
    +1 as a general feeling, although only existing PSCs can vote for this.

    Regards.

    by Pedro M. Baeza - 09:36 - 14 Jul 2021
  • Re: Propose Alba Riera as PSC for Donation
    +1



    ----- Original message -----
    From: Enric Tobella Alomar <etobella@creublanca.es>
    Subject: Propose Alba Riera as PSC for Donation
    Date: Wednesday, July 14, 2021 10:31

    I would like to propose Alba as PSC on Donation. She has made some PRs for the migration to 13.0 and I think a new PSC would be great in order to minimize the open PRs
     
     
    Kind regards
     
    Enric Tobella Alomar




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

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



    by Yves Goldberg - 09:36 - 14 Jul 2021
  • Propose Alba Riera as PSC for Donation
    I would like to propose Alba as PSC on Donation. She has made some PRs for the migration to 13.0 and I think a new PSC would be great in order to minimize the open PRs
     
     
    Kind regards
     
    Enric Tobella Alomar




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

    by Enric Tobella Alomar - 09:31 - 14 Jul 2021
  • Re: OCA module contributors and migrations
    El mar, 13 de jul de 2021 a las 15:37:13 PM, David Beal <david.beal@akretion.com> escribió:
    A point of view could be that contributors should be someone who can answer any questions about the module in the future.
    Then it should have the expertise on the topic to do it.

    That sounds more like a maintainer.

    El mar, 13 de jul de 2021 a las 15:37:12 PM, Tom Blauwendraat <tom@sunflowerweb.nl> escribió:

    - The "authors" list in manifest is something you want to keep small and just for important companies which contributed to the development, since it's also ugly when it's very long

    - The contributors list in README can be as long as you want because it's not directly in anyone's view IMO - and I think any "thank you" that we can give people that invest their time in OCA, should be given

    Just if people themselves feel their contribution is not worth a lot they can just not add it


    100% agree.

    As a side note, remember that there are plenty of ways to contribute to a module without writing a single line of code.

    OCA should be generous in this kind of attribution. That will encourage people to contribute more.

    This should be hardcoded in the guidelines though.

    by Jairo Llopis - 09:16 - 14 Jul 2021
  • OCA Days 2021 - RFQ - Video Post Production
    Hello OCA Contributors,

    As you know we are gearing up for OCA Days 2021 Online.

    As we did last year we want to be able to share the presentations after the event, to do so we need video post production.
    Please find the link to the RFQ for OCA Days 2021 - Video Post Production here.

    To register your interest or ask any questions at all please send to rfq@odoo-community.org
     Warmest regards,
    Rebecca
    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association

    by Rebecca Gellatly - 01:40 - 14 Jul 2021
  • Re: OCA module contributors and migrations
    Hi,

    A point of view could be that contributors should be someone who can answer any questions about the module in the future.
    Then it should have the expertise on the topic to do it.

    If you don't want to be disturbed by any ping, you probably shouldn't add your name to this list even if you have fixed smth.

    I.E typo like updates shouldn't lead you to be appended to this list.

    It's just a point of view.
    If you find a consensus on this topic, it could be nice to explain it in README.rst template


    Regards

    David BEAL
    Consultant ERP Odoo


    Le mar. 13 juil. 2021 à 17:22, Simone Rubino <simone.rubino@agilebg.com> a écrit :
    Agree that any contribution should be worth being mentioned in Contributors.
    I think it can't be measured in Lines of Code: a perfect one-line fix can require as much work as 50 or more Lines of Code.
    Just think how much time we spend on finding typos! And then the fix is maybe just one character.

    On Tue, 13 Jul 2021 at 17:01, Frederik Kramer <frederik.kramer@initos.com> wrote:
    Hi Kevin, 
    
    this is not an easy question to have a definitive answer on.
     
    I'd say as long as the amount of work somebody put into 
    isn't negligable (say migrated 20 lines of small module) 
    he / she should be named as a contributor.
    
    I think we should probably more focus on how we can make the net
    amount of work somebody spent on the artifact(s) more transparent, so
    that it becomes a more visible to everybody if a contributor is 
    only contributing a few or a huge pile of work.
    
    But even then sometimes the smallest changes carefully thought and
    crafted do the largest impact. 
    
    Best Frederik
    
    Am Dienstag, den 13.07.2021, 14:47 +0000 schrieb Kevin Khao:
    
    
    
    > Hi,
    
    
    
    > 
    
    
    
    > This is about what counts as valid "contribution", that is, what you
    
    
    
    > need to do to be added in the CONTRIBUTORS.rst file.
    
    
    
    > 
    
    
    
    > In some (most?) cases, a migration is not a huge amount of work. In
    
    
    
    > some cases, it can represent a lot of work.
    
    
    
    > 
    
    
    
    > So it is arguable whether you should add yourself during migration
    
    
    
    > commits.
    
    
    
    > 
    
    
    
    > In discussions on Github, I have seen differing opinions on this
    
    
    
    > subject. Some think it "cheapens" the contributor list that you add
    
    
    
    > yourself if you just did a migration commit.
    
    
    
    > 
    
    
    
    > I would lean towards adding yourself in any case a contributor
    
    
    
    > anyways, since even if it's small it is still work, and should be
    
    
    
    > recognized. Commit history is still there if you're interested in how
    
    
    
    > much anyone contributed.
    
    
    
    > 
    
    
    
    > Maybe there is already a consensus that I'm not aware of ? What do
    
    
    
    > you think ?
    
    
    
    > 
    
    
    
    > _______________________________________________
    
    
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    
    
    > Post to: mailto:contributors@odoo-community.org
    
    
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    
    
    -- 
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    An der Eisenbahn 1
    21224 Rosengarten
            
    Phone:  +49 4105 56156-12
    Fax:    +49 4105 56156-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Rosengarten – Klecken
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155
    
    

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

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


    by David BEAL - 05:36 - 13 Jul 2021
  • Re: OCA module contributors and migrations

    In my opinion:

    - The "authors" list in manifest is something you want to keep small and just for important companies which contributed to the development, since it's also ugly when it's very long

    - The contributors list in README can be as long as you want because it's not directly in anyone's view IMO - and I think any "thank you" that we can give people that invest their time in OCA, should be given

    Just if people themselves feel their contribution is not worth a lot they can just not add it

    Op 7/13/21 om 5:22 PM schreef Simone Rubino:
    Agree that any contribution should be worth being mentioned in Contributors.
    I think it can't be measured in Lines of Code: a perfect one-line fix can require as much work as 50 or more Lines of Code.
    Just think how much time we spend on finding typos! And then the fix is maybe just one character.

    On Tue, 13 Jul 2021 at 17:01, Frederik Kramer <frederik.kramer@initos.com> wrote:
    Hi Kevin, 
    
    this is not an easy question to have a definitive answer on.
     
    I'd say as long as the amount of work somebody put into 
    isn't negligable (say migrated 20 lines of small module) 
    he / she should be named as a contributor.
    
    I think we should probably more focus on how we can make the net
    amount of work somebody spent on the artifact(s) more transparent, so
    that it becomes a more visible to everybody if a contributor is 
    only contributing a few or a huge pile of work.
    
    But even then sometimes the smallest changes carefully thought and
    crafted do the largest impact. 
    
    Best Frederik
    
    Am Dienstag, den 13.07.2021, 14:47 +0000 schrieb Kevin Khao:
    
    
    > Hi,
    
    
    > 
    
    
    > This is about what counts as valid "contribution", that is, what you
    
    
    > need to do to be added in the CONTRIBUTORS.rst file.
    
    
    > 
    
    
    > In some (most?) cases, a migration is not a huge amount of work. In
    
    
    > some cases, it can represent a lot of work.
    
    
    > 
    
    
    > So it is arguable whether you should add yourself during migration
    
    
    > commits.
    
    
    > 
    
    
    > In discussions on Github, I have seen differing opinions on this
    
    
    > subject. Some think it "cheapens" the contributor list that you add
    
    
    > yourself if you just did a migration commit.
    
    
    > 
    
    
    > I would lean towards adding yourself in any case a contributor
    
    
    > anyways, since even if it's small it is still work, and should be
    
    
    > recognized. Commit history is still there if you're interested in how
    
    
    > much anyone contributed.
    
    
    > 
    
    
    > Maybe there is already a consensus that I'm not aware of ? What do
    
    
    > you think ?
    
    
    > 
    
    
    > _______________________________________________
    
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    
    > Post to: mailto:contributors@odoo-community.org
    
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    
    -- 
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    An der Eisenbahn 1
    21224 Rosengarten
            
    Phone:  +49 4105 56156-12
    Fax:    +49 4105 56156-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Rosengarten – Klecken
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155
    
    

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

    _______________________________________________
    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 - 05:36 - 13 Jul 2021
  • Re: OCA module contributors and migrations
    Agree that any contribution should be worth being mentioned in Contributors.
    I think it can't be measured in Lines of Code: a perfect one-line fix can require as much work as 50 or more Lines of Code.
    Just think how much time we spend on finding typos! And then the fix is maybe just one character.

    On Tue, 13 Jul 2021 at 17:01, Frederik Kramer <frederik.kramer@initos.com> wrote:
    Hi Kevin, 
    
    this is not an easy question to have a definitive answer on.
     
    I'd say as long as the amount of work somebody put into 
    isn't negligable (say migrated 20 lines of small module) 
    he / she should be named as a contributor.
    
    I think we should probably more focus on how we can make the net
    amount of work somebody spent on the artifact(s) more transparent, so
    that it becomes a more visible to everybody if a contributor is 
    only contributing a few or a huge pile of work.
    
    But even then sometimes the smallest changes carefully thought and
    crafted do the largest impact. 
    
    Best Frederik
    
    Am Dienstag, den 13.07.2021, 14:47 +0000 schrieb Kevin Khao:
    
    
    > Hi,
    
    
    > 
    
    
    > This is about what counts as valid "contribution", that is, what you
    
    
    > need to do to be added in the CONTRIBUTORS.rst file.
    
    
    > 
    
    
    > In some (most?) cases, a migration is not a huge amount of work. In
    
    
    > some cases, it can represent a lot of work.
    
    
    > 
    
    
    > So it is arguable whether you should add yourself during migration
    
    
    > commits.
    
    
    > 
    
    
    > In discussions on Github, I have seen differing opinions on this
    
    
    > subject. Some think it "cheapens" the contributor list that you add
    
    
    > yourself if you just did a migration commit.
    
    
    > 
    
    
    > I would lean towards adding yourself in any case a contributor
    
    
    > anyways, since even if it's small it is still work, and should be
    
    
    > recognized. Commit history is still there if you're interested in how
    
    
    > much anyone contributed.
    
    
    > 
    
    
    > Maybe there is already a consensus that I'm not aware of ? What do
    
    
    > you think ?
    
    
    > 
    
    
    > _______________________________________________
    
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    
    > Post to: mailto:contributors@odoo-community.org
    
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    
    -- 
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    An der Eisenbahn 1
    21224 Rosengarten
            
    Phone:  +49 4105 56156-12
    Fax:    +49 4105 56156-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Rosengarten – Klecken
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155
    
    

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


    by Simone Rubino - 05:20 - 13 Jul 2021
  • Re: OCA module contributors and migrations
    Hi Kevin, 
    
    this is not an easy question to have a definitive answer on.
     
    I'd say as long as the amount of work somebody put into 
    isn't negligable (say migrated 20 lines of small module) 
    he / she should be named as a contributor.
    
    I think we should probably more focus on how we can make the net
    amount of work somebody spent on the artifact(s) more transparent, so
    that it becomes a more visible to everybody if a contributor is 
    only contributing a few or a huge pile of work.
    
    But even then sometimes the smallest changes carefully thought and
    crafted do the largest impact. 
    
    Best Frederik
    
    Am Dienstag, den 13.07.2021, 14:47 +0000 schrieb Kevin Khao:
    
    > Hi,
    
    > 
    
    > This is about what counts as valid "contribution", that is, what you
    
    > need to do to be added in the CONTRIBUTORS.rst file.
    
    > 
    
    > In some (most?) cases, a migration is not a huge amount of work. In
    
    > some cases, it can represent a lot of work.
    
    > 
    
    > So it is arguable whether you should add yourself during migration
    
    > commits.
    
    > 
    
    > In discussions on Github, I have seen differing opinions on this
    
    > subject. Some think it "cheapens" the contributor list that you add
    
    > yourself if you just did a migration commit.
    
    > 
    
    > I would lean towards adding yourself in any case a contributor
    
    > anyways, since even if it's small it is still work, and should be
    
    > recognized. Commit history is still there if you're interested in how
    
    > much anyone contributed.
    
    > 
    
    > Maybe there is already a consensus that I'm not aware of ? What do
    
    > you think ?
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    -- 
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    An der Eisenbahn 1
    21224 Rosengarten
            
    Phone:  +49 4105 56156-12
    Fax:    +49 4105 56156-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Rosengarten – Klecken
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155
    
    

    by Frederik Kramer - 05:01 - 13 Jul 2021
  • OCA module contributors and migrations
    Hi,

    This is about what counts as valid "contribution", that is, what you need to do to be added in the CONTRIBUTORS.rst file.

    In some (most?) cases, a migration is not a huge amount of work. In some cases, it can represent a lot of work.

    So it is arguable whether you should add yourself during migration commits.

    In discussions on Github, I have seen differing opinions on this subject. Some think it "cheapens" the contributor list that you add yourself if you just did a migration commit.

    I would lean towards adding yourself in any case a contributor anyways, since even if it's small it is still work, and should be recognized. Commit history is still there if you're interested in how much anyone contributed.

    Maybe there is already a consensus that I'm not aware of ? What do you think ?


    by "Kevin Khao" <kevin.khao@akretion.com.br> - 04:46 - 13 Jul 2021
  • Oracle to Odoo migration

    Hi Colleagues,

    I am looking for a successful project of migration from Oracle to Odoo.

    We are on the point of decision making and the Finance team would like to get a reference call with a such customer.

    Might be anybody can share the customer contacts details with whom we can arrange a call.  

    Thank you!

    Alexey

     

     


    by Alexey - 05:51 - 12 Jul 2021
  • Re: Import data from incoming email
    Hi Daniel. I mean to import records in a custom model from a CSV data sent by mail.
    Thank you
     --
    Yves Goldberg 
    odooOfficial Partner - OCA delegate
    Open Source ERP, CRM & CMS
    T +972 (3) 720 8818
    +972 (55) 966 1405
    +32 (2) 588 2500
    --


    ----- Original message -----
    Subject: Re: Import data from incoming email
    Date: Thursday, July 08, 2021 19:21

    Maybe clarification is needed, but I feel this is out of the box:
    Fetchmail will get email the email attachments and add them to the target record.

    /Daniel


    On 08/07/21 12:11, Yves Goldberg wrote:
    Hi,

    Do we have a module in OCA that can help importing data send as an email attachment?

    Thank you

     --
    Yves Goldberg
    --

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


    by Yves Goldberg - 06:31 - 8 Jul 2021
  • Re: Import data from incoming email
    Maybe clarification is needed, but I feel this is out of the box:
    Fetchmail will get email the email attachments and add them to the target record.

    /Daniel

    On 08/07/21 12:11, Yves Goldberg wrote:
    Hi,

    Do we have a module in OCA that can help importing data send as an email attachment?

    Thank you

     --
    Yves Goldberg
    --

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



    by Daniel Reis - 06:20 - 8 Jul 2021
  • MS Power BI Users Database

    Hi,

     

    We’d like to know if you’re interested in acquiring the Opt-in contacts of below-mentioned technologies users which will help you grab new clients for your business.

     

    ·         Microsoft Power BI

    ·         Tableau Desktop

    ·         Qlik Sense

    ·         SAP BusinessObjects BI Suite

    ·         Sisense

    ·         Microstrategy

    ·         TIBCO Spotfire

    ·         IBM Cognos Analytics and more

     

    Data can be filtered depending on the requirements (e.g. Job title, Verticals, Geography, etc.)

     

    Please review and let me know your interest and I will provide you with detailed information.

     

    Looking forward to hearing from you.

     

    Regards,

    Laura Bishop

    Demand Generation Head

     

    Not interested reply with “Opt-Out”


    by "Laura Bishop" <laura.bishop@infradatabase.com> - 06:01 - 8 Jul 2021
  • Import data from incoming email
    Hi,

    Do we have a module in OCA that can help importing data send as an email attachment?

    Thank you

     --
    Yves Goldberg
    --


    by Yves Goldberg - 01:11 - 8 Jul 2021
  • Re: Odoo automatic code documentation
    Dear, Tom, Daniel and David,

    Many thanks for your replies. 

    Generally it does work this way, and it nicely reveals which coding  artist is doing what amount of documentation to the extent of readability for the other developers. 

    However, we went into an issue, when it comes to recursions: here the running of the Python code is frequently running into an endless loop.

    Is there any kind of switch in odoo, that prevents this behavior like "maximum depth of recursion loops"


    Best, Joe


    -------- Ursprüngliche Nachricht --------
    Von: Daniel Reis <dreis@opensourceintegrators.com>
    Datum: 24.06.21 15:17 (GMT+01:00)
    An: Contributors <contributors@odoo-community.org>
    Betreff: Re: Odoo automatic code documentation

    Hello,

    Try "cd /path/to/odoo && pip install ."
    You will then be able to "import odoo"

    Thanks
    Daniel

    On 24/06/2021 09:42, Joerg Lorenz wrote:
    Hi Guys, today we are asking for your insightfullness.
    Our quest:  how the python code of odoo can be automatically documented from the code itself. 

    But the approach with the various toos that there are fails:  

    We have tested: 
    • pdoc, a simple Python 3 command line tool and library to auto-generate API documentation for Python modules. Supports Numpydoc / Google-style docstrings, doctests, reST directives, PEP 484 type annotations, custom templates ...

    • pdoc3, a fork of pdoc for Python 3 with support for Numpydoc / Google-style docstrings, doctests, LaTeX math, reST directives, PEP 484 type annotations, custom templates ...

    • PyDoc, a documentation browser (in HTML) and/or an off-line reference manual. Also in the standard library as pydoc.

    • pydoctor, a replacement for now inactive Epydoc, born for the needs of Twisted project.

    and all of them fail.  It has to do that odoo as such is not a python module itself and thus cannot be imported. 

    problem in models/res_company.py - <type 'exceptions.ImportError'>: No module named odoo

    If anyone has some experience, ideas, or pointer towards a solution, it would be highly appreaciated. 

    Best, Joe

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


    --
    Daniel Reis
    Managing Director
    M: +351 919991307
    E: DReis@OpenSourceIntegrators.com
    Av. Republica 3000, Edificio Estoril Office, B Piso 3 - 34 • 2649-517 Alcabideche, Portugal


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


    by "joergl" <joergl@itis.de> - 12:00 - 7 Jul 2021