muni-town/roomy

First of all we need to update the opengraph meta-data for roomy.space Let’s start with: Roomy Cozy community spaces; cultivate your digital gardens. plus our new door logo. Secondly, we would ideally display custom meta-data for each space, using their own title and description, but that’s a bigger task.

When a new event is created in Roomy (OpenMeet) that event should be mirrored to Discord. Remains to be seen how feasible this is. Discord-to-Roomy is less interesting because we want to encourage protocol-first events creation.

The Roomy team does 90% of its project management in chat. We make sure to properly track the most essential/long-standing 10% on GitHub, but the rest of the work is tracked individually while the priorities of our respective TODOs are continuously updated by the running consensus of the team-chat. It's already a well-functioning workflow, but it could be a whole lot better if Roomy automagically tracked most of those TODOs for us, as a team. As a team we are constantly @-mentioning and replying to each other with various kinds of offers/prompts/requests that should be easy to 'add to [person's] TODO's with various kinds of just-in-time UI facilities, similar to the Assignees system of GitHub but more deeply integrated into the flow of our group chat. Design Todos would be an opt-in item in the index-menu, like Events #575 but opted into on an individual basis. Also it's not an external API, it can be achieved natively. It can however interop with the likes of skyboard by @disnet My pe

Our /index as well as every threads-view of a channel needs a ‘new thread’ button. Right now the only way to make a new thread is to convert a chat message. Except for the post-selection though the new-thread UX we’ve already got should be a good baseline. New threads created from the index will also require a channel-selector. Also have to ensure that threads created outside the chat stream still get posted in there as an event.

Not to be confused with the now operational Discord bridge, we also want to support importing from Discourse, the forum platform. I say specifically import and not bridge because Discourse is unlikely to be a common bridging target; any community that has successfully scaled up to needing Discourse doesn’t have a dire need to scale down to Roomy. But for the small handful of communities that tried to expand into forum-scale but couldn’t, this import will enable them to migrate their Discourse community into a lighter-weight Roomy instance. Therefore the most basic TODO here is a one-off import. However, since Discourse has an open API it may be equally doable to set up a one-way sync from Discourse to Roomy, which could facilitate a continuously up-to-date demo of a to-be migrated instance. Additionally there’s one unique case we want to accommodate, namely the atproto dev-community forum: https://discourse.atprotocol.community/ This is already a very healthy Discourse instance,