Support d->m scheduled events #2

New Issue

Open

opened 2023-10-03 10:34:25 +00:00 by cadence · 0 comments

cadence commented

2023-10-03 10:34:25 +00:00

Owner

Events should be bridged into a dedicated events room. The events room should only exist if an event was ever created.

Events have a start time, end time, title, location, description, image, and interested users. Interested users could be indicated through reactions on Matrix or through a single-option poll. Reactions are probably more intuitive and more widely supported. It won't be possible for interested Matrix users to be listed on Discord-side, but that's okay.

At the start time of the event, interested Matrix users could be notified.

After the event has finished, it should be deprioritised in some way (greyed out, compacted, or disclosed) in the events room.

Events should be bridged into a dedicated events room. The events room should only exist if an event was ever created. Events have a start time, end time, title, location, description, image, and interested users. Interested users could be indicated through reactions on Matrix or through a single-option poll. Reactions are probably more intuitive and more widely supported. It won't be possible for interested Matrix users to be listed on Discord-side, but that's okay. At the start time of the event, interested Matrix users could be notified. After the event has finished, it should be deprioritised in some way (greyed out, compacted, or disclosed) in the events room.

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cadence/out-of-your-element#2

No description provided.