Structuring the per-protocol watchlists on the wiki
The various watchlists in this GitLab project's wiki are being curated primarily to help guide the ongoing development of the fediverse.party website. As such, they exist to gather research about new developments in the fediverse; new apps, which protocol(s) they implement or aim to, progress on inter-operation with other apps etc.
As the ActivityPub watchlist has got longer and longer, we've come up with various ideas about the best way to structure them. The AP watchlist - by far the largest - is mainly organized by app type; micro-blog, blog, events etc. There are separate sections for 'Proposed Projects' (rumours, initial commit only etc), and 'Dead Projects'. The Zot watchlist has separate categories for 'known to federate' and 'may be implementing'.
The issue for discussion here is what is the best way to structure the watchlists to:
- maintain a consistent and coherent format
- communicate as much information as possible, as clearly as possible
- be as easy to update and extend as possible