- Mailing Lists
- Contributors
- Re: New repositories : cooperative and participative supermarket
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: New repositories : cooperative and participative supermarket
Hi Robin,
That's great to hear this!
My two cents on this. Maybe you should refine the topics the repositories you want to create will cover (it does not help saying they are in beta). Especially for the first one.
For the third, we usually don't create 'temporary' repositories. I suggest you to create issues/PR's directly on OCA specific repos for modules you want to move. It will be more efficient and avoiding creation of one that will be deleted actually.
Don't hesitate if you have more technical questions, but for sure you have a good OCA contact person near you !
On Fri, Jan 14, 2022 at 11:27 AM <robin@coopiteasy.be> wrote:
Hi all,
At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :
- cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
- beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.
We will need to
- remove all references to Obeesdoo and Easy My Coop (debranding) ;
- split modules by features ;
- cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.
Based on the OCA repository policy, we would like to propose to create these 3 new repositories :
- cooperative with all modules in beta-stage while we debrand them.
- shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
- vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?
You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.
All inputs welcome,
Robin Keunen
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Denis Roussel - 06:31 - 14 Jan 2022
Reference
-
New repositories : cooperative and participative supermarket
Hi all,
At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :- cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
- beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.
We will need to- remove all references to Obeesdoo and Easy My Coop (debranding) ;
- split modules by features ;
- cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.
Based on the OCA repository policy, we would like to propose to create these 3 new repositories :- cooperative with all modules in beta-stage while we debrand them.
- shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
- vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?
You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.
All inputs welcome,
Robin Keunen
Robin KeunenCoop IT Easyrobin@coopiteasy.be+32 488 86 57 40
by Robin Keunen - 11:26 - 14 Jan 2022