If someone creates a community for their XMPP project, that should obviously be allowed. But what about tangentially related technologies or XMPP-focused general discussion communities? Eg. would an IETF KITTEN Working Group community be disallowed because it’s not specific to XMPP (not that they’re likely to create a group, I was just trying to think of something tangentially related)? What about a group to discuss XMPP Security or XMPP UX that’s not specifically tied to a project or group? It may be worth us developing a policy on this early on to stop conflicts before they arise and to stop having to grandfather in to many groups if we decide later that they’re out of scope.
Also: should we require applications to create a new community? If spam becomes a problem this is an option, but someone else suggested it might be worth while just to have a higher quality list of communities. We should decide how we’re going to handle this.
deleted by creator
Yah, I tend to agree that general purpose rooms are good; I’ll be curious if anyone has reasons not to though.
Third thing that might be worth thinking about: do we allow “unofficial” communities. Eg. if someone who’s not a Gajim author or maintainer or what not wants to come along and make a /c/gajim, do we allow it? Do we require it to have “Unofficial” or similar in the display name?
deleted by creator
I don’t think it needs “unofficial” in the name, it’s not like that on reddit and other social media as well, right? Also what @poVoq@lemmy.ml says
I’m wondering what to do with other languages? I’d like not to shutdown attempts at creating language-specific communities. Is this something that we want to manage on this instance?
Seems okay to me, but I’d bet existing ones are already established and probably other instances will have a wider user base. But I don’t see any reason to forbid it, personally.
