Support having a single membership

[BerglundDaniel]

Many makerspaces only have one typ of membership instead of one for the association and one for the premise. I think the main work here is too have another registration page as an option and have one membership that adds both memership days and labaccess days.

[amrsoll]

Is it realistic to have db entries that describe all of these?

• Subscription name
• cost
• recurrence
• binding
• description (including emojis would be nice)
• discounts
• dependency (fx. lab access requires basic membership?)

Then there would be a possibility to have multiple memberships.

See #331

I might have mentioned that I find a config file to be just as good a place to have info as a database. It is easier to migrate/recreate the website if the subscriptions are fully described in a config file.

Example subscriptions.yml

membership:
  price: 200
  recurrence: yearly
  description:
    - "line 1"
    - "line 2"
makerspace_access:
  price: 300
  recurrence: monthly
  binding: 2 # 2 * recurrence, fx 2 months here
  depends: membership
  description:
    - "line A"
    - "line B"

[BerglundDaniel]

I think we should probably put in a database so that it is easier to update through an admin interface. Maybe subscriptions shouldn't be a Product but rather have their own table, model and admin interface.

@amrsoll Do you have time for a short meeting sometime? Would be interesting to talk about makeradmin

[amrsoll]

@BerglundDaniel of course, I think you can reach me by mail? :)