- Mailing Lists
- Contributors
- Re: oca/oca.recipe.odoo repository?
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/oca.recipe.odoo repository?
> Could somebody with the appropriate permissions make the settings accessible > to the maintainers (StefanRijnhart+hbrunn at the moment)? > Currently permissions are managed via a GitHub team sync script, from the > PSC members database. The current policy is that only PSC representatives > and board have admin access to the repos. I'm not sure it still makes sense > for tooling repos such as this one, but it's the way it is now. I gave you > access, but it may only last until the team sync script kicks in again. thanks Stéphane, I changed the bits that need changing currently, so it won't be super problematic if we lose access again. > Generally, who is the address to ask about OCA github permission stuff? I > try to avoid asking Alexandre about everything. > I guess it's support@odoo-community.org [3] , but it will mostly end up with > Alexandre and myself anyway ;) That's also something we'll need to work on, > i.e. manage the bus factor for the OCA infrastructure. Cheers, indeed, that's an important one. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 11:30 - 22 Dec 2021
Reference
-
oca/oca.recipe.odoo repository?
Hi all, I'd like to fork https://github.com/anybox/anybox.recipe.odoo which has been inactive/externally maintained (amongst others by Stefan Rijnhart and me) to a repo under the OCA umbrella, namely oca/oca.recipe.odoo. We had the discussion before in https://odoo-community.org/groups/contributors-15/contributors-27171 where the issue of branding was raised, that's why I suggest the new name. This way we also don't clash with the original on pypi etc. Please don't let this devolve into a discussion about what to use for builds/ deployment, OCA can host various alternatives in my opinion. The fork will probably happen anyways, but I prefer to have it under the OCA organization rather than some specific one just for that. Best regards, Holger Brunn -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 11:01 - 4 Feb 2021