[8.0][WIP][event_product_logistics] Manage product delivery for event attendees

[yajo]

As asked by @dreispt in #21 (comment), I'm opening this PR. Bots will fail until #21 is merged. Target: OCA/l10n-spain#174. Design as discussed in #14.

Sometimes you want to give some products to your event's attendees. For example: a pen, a notebook, a book, etc.

This module extends the functionality of events to support setting products to deliver to event attendees and allow you to know if they have been already delivered to them.

[elicoidal]

have already been

[dreispt]

I'm not sure if this shouldn0t be "Event Management". Can you check?

[dreispt]

I have two main design questions:

• Why depend on event_product? AFAICS that could be avoided.
• Why the two modules? The second one repeats code from the first. Maybe it could depend on the first to avoid such repetition.

[yajo]

Yikes, I forgot to remove the old module! Thanks!

The relation between events and products in this module can be seen in method action_load_deliverable_products, where you can load that information from the linked product.

Indeed, I could just create 2 modules instead of one, but the second would be so small that I decided to avoid that for simplicity, but if you feel it's necessary I can split it.

[dreispt]

No need to split.
I have the feeling that the event_product dependency can be avoided. What do you think?

[yajo]

Normally, if e.g. your event is from product Odoo onsite training, you know you will give away notebook, pen and Odoo t-shirt. If you cannot define that in the product, you need to choose them manually in every event.

With current implementation, you give the user the chance to edit the deliverable products in the event, but to do it in the product to avoid repetition too.

How do you think we can get this without depending on event_product?

[dreispt]

Instead of adding event_deliverable_product_ids to product.template, add it directly to event.event.
AFAICS all the rest should work.

[yajo]

It already has it.

[dreispt]

So the same field is in the two models?
I'm confused; what's the point?

[yajo]

I think it will be clearer if you try it. Please open the runbot and follow all the steps in the usage section of the readme. Then please tell me what you don't understand.

[dreispt]

OK, will try that.

[dreispt]

I see the point.
In theory we could split the product-side features into another module, but as you say, in practice it would probably be an overkill. So OK: 👍

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.