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.
In general I lean towards being more careful about community creation, especially as we find our feet. I’m fine with tangential stuff that doesn’t have a better home, but would certainly draw the line before general topics (memes, gaming, politics) for many reasons.
I agree that not having to wade through loads of stuff to find genuine XMPP communities here would be good, and to me that’s kind of the entire promise and purpose of this instance.
Good points; this is roughly what I was thinking too and sounds good to me.