Progress on the FEP for Event objects

The FEP-8a8e (Fediverse Enhancement Proposal) had at lot of progress in the last months. In the meantime, the document has become somewhat more extensive than originally planned, but contains not only instructions for new features that have to be tediously implemented, but also a lot of advice and points that should provide orientation for developers of Fediverse applications that support events.

It now covers:

  • Required attributes
  • Events with Open End
  • Timezone
  • Physical and Virtual Locations
  • Event status
  • RSVP (Attendee Management)
  • Event Banner and Poster Images
  • Event Categories
  • Discoverability
  • Event Organizers
  • Upcoming Events Collection for ActivityPub actors
  • Term Definitions

Many thanks again to all reviewers and co-editors:

@lesion @heiglandreas @naturzukunft @laurin

We warmly welcome further feedback from the communities of , , , and other Fediverse platforms supporting events.
If you’re working on such an application or are part of these communities, your insights would be very valuable! @developers @mobilizon


All posts are licensed under CC-BY-SA 4.0

Comments

3 responses to “Progress on the FEP for Event objects”

  1. @blog @lesion @heiglandreas @naturzukunft @laurin @developers @mobilizon

    I hope I don't forget to do it myself, but if I do, I'd like to request a short-ish custom text field. Maybe like a mastodon post.

    Unless there are already different methods of attaching custom text like comments.

    I'm sure there are future or custom use cases where additional info would be nice and there should be a place to put them.

    E.g. a uid to correlate to some other data source.

Leave a Reply

Your email address will not be published. Required fields are marked *