This is a feature request to deliberately add a canceled event, i.e. an event that was not previously on Meetable, as a heads-up to folks who may be expecting a regular event and wondering where the information is, or assuming it may still be on at the usual time and place. This is different from #86 which is about canceling an existing event.

Use-case: In the IndieWeb community we have several regular Homebrew Website Club (HWC) meetups, some every two weeks, some every month like the first Wednesday of the month. When one of these expectedly periodic events is missing (especially the less frequent ones like first Wednesday of the month, like what just happened with HWC Austin this week), we’re more likely to assume the organizer just forgot to post an official online event, rather than the regular event is not actually happening. Thus we need a way to explicitly create a canceled event when one has not yet been posted.

Editing: have an option to perhaps check when creating an event that this is a "cancelled" event, which means that it will not be accepting RSVPs, perhaps doesn’t need a venue.

Display: Similar to #86, a canceled event should be explicitly flagged as such in any listings, perhaps with a red CANCELLED label. It should also be listed in upcoming and past event listings per its datetime along with other events.

Again similar to #86, optional name prefix: consider prefixing the editable name of the event with the all-caps "CANCELED: " as part of the marked up p-name of the h-event.

It should also be possible to edit and uncancel a canceled event and turn it into a real event in case it turns out to actually be happening, perhaps by another organizer!

RSVP interaction: a canceled event should not accept RSVPs via the user interface, perhaps rejecting federated webmention RSVPs as well.

Meetable events should be editable to explicitly cancel them, yet keep them in the list of events (upcoming or past) so it is clear to folks who may have already RSVPd, or have been sent a link to view them that they were canceled.

Use-case: On the IndieWeb wiki we used to explicitly note on the wiki page for the Homebrew Website Club events for a particular day, if and when a particular city/location was canceled, usually by adding strike-through (s tag) or deletion (del tag) markup. This is particularly useful for when an organizer is unable to make it themselves and can’t be sure that anyone else will either.

Display: A canceled event should be explicitly flagged as such in any listings, perhaps with a red CANCELLED label.

Optional name prefix: consider prefixing the editable name of the event with the all-caps "CANCELED: " as part of the marked up p-name of the h-event.

It should also be possible to edit and uncancel an event in case it was canceled accidentally or errantly by someone.

RSVP interaction: a canceled event should no longer accept RSVPs via the user interface, perhaps rejecting federated webmention RSVPs as well.

A canceled event may send Webmentions back to the federated RSVP posts that it is listing (and or perhaps their author domains), so those posts can be updated, and authors notified.

For Meetable events which have one or more Code of Conduct links (per #84), when the user interacts with the RSVP user interface to confirm participation, Meetable should prompt the user with a dialog with one or more links to Codes of Conduct with checkboxes next to each that acknowledges that the user has read and agreed to them.

A minimum viable user interaction here would be just fine, and there is no need to create a whole ticketing and assignment system where different people would RSVP vs agree to the Code of Conduct link(s).

We can learn from the development, use, and iteration of this minimal user interface to then drive future protocol improvements in federated RSVPs via Webmention.

Typical communty events require agreeing to a Code of Conduct in order to RSVP and participate. Meetable should have a field to enter one or more Code of Conduct URLs, and then show them prominently on the event, preferably right before / next to any user interface to RSVP.

Use-case for a Code of Conduct field: IndieWeb events always require agreeing to the IndieWeb Code of Conduct.

Use-case for a field for multiple Code of Conduct URLs: IndieWeb events hosted at a Mozilla office require agreeing to both the IndieWeb Code of Conduct and the Mozilla Community Participation Guidelines.

The Code of Conduct link(s) should be prominently publicly displayed on Meetable event pages, preferably adjacent to / before any RSVP user interface or display.

Typical popular events sites and services (Google Calendar, Facebook) prominently show who created and is organizing events, as well as when they were created. Meetable should do this by default, at a minimum using the author’s personal site they used to sign-in via IndieAuth, and the datetime at which they created the event.

The author’s personal site can be parsed for a representative h-card to use for their display name and image (h-card name and logo or photo), though even showing the domain name of the author would be useful (absent an h-card display name or logo/photo).

This would at a minimum be very useful for the events.indieweb.org deployment of Meetable, as that was used to replace use of the wiki for events which had this information implicitly in the browsable edit history.

Who created it use-cases: knowing who created an event helps clarify the potential legitimacy of the event and/or how much help the organizer may need (is it a known organizer of such events, the usual person, or a new person but still known to the community, or a random person who may need help). Additionally, having a clear organizer helps provide at least a default contact for any Code of Conduct follow-ups.

When was it created use-cases: it is useful to know the when created information as a method for if an event was created long in advance and might not still be happening, or if it was created very recently and thus is much more likely to be happening.

This information should be prominently publicly displayed on Meetable event pages.