- Mailing Lists
- Contributors
- Re: OCA module contributors and migrations
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
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
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
Reference
-
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