Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: New repositories : cooperative and participative supermarket

Re: Lots of our modules do not handle multi-company correctly with Odoo >= 13

Re: New repositories : cooperative and participative supermarket

Acsone SA/NV, Stéphane Bidoul

- 09/02/2022 18:31:06

Ok, so what do we do in terms of PSC, PSC Representative, and PSC Members ?

I don't immediately see an existing PSC to cover this scope.

So shall we create one new PSC (named Ccooperative?) for the 3 repos ?

Who would be the PSC representative (Robin?). Who would be the first members ?

-sbi

On Wed, Feb 9, 2022 at 10:47 AM Valentin Vinagre Urteaga <valentin.vinagre@sygel.es> wrote:

+1 :D
El mié, 9 feb 2022 a las 10:02, Enrico Stano (<enrico.stano@coopdevs.org>) escribió:
Hi,

+1 and a big thank you!

Bye,

Enrico Stano

coopdevs.org

On 1/27/22 18:57, Roussel, Denis wrote:

Hi Robin,

+1 for the three repos.

On Thu, Jan 27, 2022 at 6:22 PM <robin@coopiteasy.be> wrote:

Hi Denis,

Thank you for your answer, it looks like my last email did not go through. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :

The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.

The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.

As for refining the topics, I can try to rephrase :-)

- oca/cooperative would hold the modules allowing to
- Subscribe to a share, transfer a share or sell a share from the cooperative,
- Share subscription can be done online,
- Manage the cooperator registry of a cooperative,
- Generate legal reports for company and cooperators.

- oca/shift-planning would hold the modules allowing to
- Create a planning template of work shifts of the company
- Generate the shifts based on these templates,
- Allow partners to subscribe to regular tasks,
- Allow partners to subscribe to any task with available spot,
- Track the attendance to the shifts.

- oca/vertical-cooperative-supermarket* glues all these together to
- Track who can work in the cooperative
- Track who can shop in the cooperative
- welcome screens and member cards

* once cleaned up from all sale, purchase, pos, ... customisations.

I hope it’s clearer that way,

Robin Keunen
Coop IT Easy

robin@coopiteasy.be

+32 488 86 57 40

On 17 Jan 2022, 18:25 +0100, robin@coopiteasy.be, wrote:

Hi Denis,

Thank you for your answer. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :

The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.

The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.

As for refining the topics, I can try to rephrase :-)
• oca/cooperative would hold the modules allowing to
• Subscribe to a share, transfer a share or sell a share from the cooperative,
• Share subscription can be done online,
• Manage the cooperator registry of a cooperative,
• Generate legal reports for company and cooperators.
• oca/shift-planning would hold the modules allowing to
• Create a planning template of work shifts of the company
• Generate the shifts based on these templates,
• Allow partners to subscribe to regular tasks,
• Allow partners to subscribe to any task with available spot,
• Track the attendance to the shifts.
• oca/vertical-cooperative-supermarket* glues all these together to
• Track who can work in the cooperative
• Track who can shop in the cooperative
* once cleaned up from all sale, purchase, pos, ... customisations.

I hope it’s clearer that way,

Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
On 14 Jan 2022, 18:32 +0100, Roussel, Denis <denis.roussel@acsone.eu>, wrote:

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

Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe

--

Denis RousselSoftware EngineerT : +32 2 888 31 49M : +32 472 22 00 57
Val Benoit, Quai Banning 6 | B-4000 Liège | BelgiumAtrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post 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

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium

Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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

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

Valentín Vinagre Urteaga
CTO
Sygel Technology S.L

+34 662 68 78 95
valentin.vinagre@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