Make service method explicit

[rinkp]

What would you like?

Some way of indicating the service method more explicitly. Currently there is a limited capacity checkbox which I am happy about, but I get the impression that it does not always is stated explicitly what is the case.

In my opinion, the best solution would be that the board makes a few options that can always be applied for an activity, records these in the Activity policy and those get explicitly listed

Why is this needed?

There are various service methods in use which are not always explicitly explained. See below for examples

Other information

Examples of implemented policies

1. first come, first serve -- the de facto standard
2. first paid, first served -- parties/SNiC/events with ticket sales
3. draw if (full before YYYY-mm-dd hh:ii:ss) else 1 -- which is a generalisation of 'draw on signup close' and 'draw after one hour' -- used for popular activites/weekends
4. no capacity limit -- which technically is a more specific form of first come, first serve

And then we have the specific cases:

5. freshmen first, seniors second
   -- typically used for e.g. [educational activities for freshmen](https://gewis.nl/en/activity/view/6627), the FYC barbecue, certain [freshmen bonding activities](https://gewis.nl/en/activity/view/5450)
6. master students first, bachelor's second
   -- sometimes used for [master bonding activities](https://gewis.nl/en/activity/view/6342)
7. draw with drivers prioritised above passengers
   -- sometimes used for [weekends](https://gewis.nl/en/activity/view/6162): a draw is done, if there are not enough drivers in the first X, the first driver after X replaces the last non-driver; that non-driver will get waiting list position 1
8. draw with skippers prioritised
   -- sometimes used for [specific weekends](https://gewis.nl/en/activity/view/6182): see above for how it works
9. external party policies (e.g. Wervingsdagen)

Then, usually also members > graduates > others is implemented for 1 and sometimes for 3 as well