Needs decision meeting (#291)

* Add Needs: decision meeting
* Tweak events template

Author: keunes

_events/0_A meeting template.md

@@ -6,7 +6,7 @@ summary:
 image: 
 # Optional. Displayed on Events overview page and the event detail page.
 permalink: 
-# Optional. "/events/short-text" recommended for recurring events, to avoid that the event gets a date-based URL.
+# Optional. "/events/:slug" recommended for recurring events, to avoid that the event gets a date-based URL.
 uid: 
 # Required. Don't edit after publishing. Get one here: https://www.random.org/strings/?num=1&len=20&digits=on&upperalpha=on&unique=on&format=html&rnd=new
 sequence: 
@@ -18,7 +18,7 @@ datetime-start:
 datetime-end: 
 # Required. Format: yyyy-mm-dd hh:mm. If recurring, this end time is applied also to all occurrences of the generated recurrence set
 recurring: 
-# Optional
+# Optional. Can be "yes"
 recurrence-text: 
 # Required if "recurring: yes". Displayed on Events overview page and the event detail page. View & add strings in _i18n/en.yml 
 recurrence-rule: 

_events/needs-decision.md

@@ -0,0 +1,30 @@
+---
+title: "Needs: Decision - AntennaPod UX discussions"
+summary: A bi-weekly meeting where core contributors discuss feature requests & make tough choices.
+permalink: /events/:slug
+uid: TDL9-28GB-50YV-P6X4-D48Y
+sequence: 
+# Optional. Defaults to 0 if left empty. Should be increased with 1 on every big event edit.
+timezone: Europe/Brussels
+datetime-start: 2023-12-27 21:00
+datetime-end: 2023-12-27 22:30
+recurring: yes
+recurrence-text: 2nd-4th-wednesday
+recurrence-rule: FREQ=WEEKLY;INTERVAL=2;BYDAY=WE
+recurrence-exceptions:
+- 2023-01-10
+- 2024-01-24
+recurrence-additions: 
+# List of date-times on which the event is additionally taking place. Format:
+# - start: yyyy-mm-dd hh:mm
+#   end: yyyy-mm-dd hh:mm
+location: online
+more-information: https://github.com/AntennaPod/AntennaPod/labels/Needs%3A%20decision
+meeting-room: https://meet.antennapod.org/needsdecision
+---
+
+We are very careful about AntennaPod's User Experience (UX). The [project's goal](/about) here is to balance simplicity with feature-richness. Sometimes that requires some hard thinking on how to implement a feature request.
+
+Where do we place this button? What would most users expect AntennaPod to do here? Which impact does this choice have on other settings? How can we implement this without making the UI or code complex?
+
+In these meetings @ByteHamster and @Keunes get together to do just that: discuss the options for a given feature request, and try to reach a decision. One [issue](https://github.com/AntennaPod/AntennaPod/labels/Needs%3A%20decision) at a time. You're most welcome to listen in as a fly on the wall, or jump in and share your thoughts.

_i18n/en.yml

@@ -201,6 +201,7 @@ events:
     watch-recording: "Watch recording"
   recurrence:
     every-2nd-saturday: "every second Saturday of the month"
+    2nd-4th-wednesday: "(almost every) second & fourth Wednesday of the month"
 
 ## Footer
 footer: