Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
What are the steps between community proposal and the actual spawn of that community?
Codidact features a list of communities, but none of them seems to address software development.
I have seen Professional coding proposal and I think Monica's proposal makes even more sense since we do not want to copy Stack Overflow and at the beginning, it might be wiser to start with broader scopes.
However, it is not clear what happens after the proposal has been made. What should I do if I think Software Development deserves to be a community?
Question: What are the steps between community proposal and the actual spawn of that community?
1 answer
This answer can be considered semi-official. It's a mix of "what we currently appear to be doing" and "how I'd want it do be".
-
There is a site suggestion category here on Meta, where everyone with a community can suggest a new site by using the [proposal] tag. If you have a nice idea but no community and you want to do some kind "interest-check", there is the [idea] tag for you. Your proposal should contain stuff like some statement defining the scope, a site name, where you got a community from and whether the community will need something special.
-
These proposals can be voted on by other users, who like (or dislike) the proposal. Comments and answers can be used to discuss the merits and details of the community. Potential community members are asked to join in there, so that we can estimate, how many people support a proposal.
-
At the same time, the Codidact team will initially review the proposal and look, whether it is viable at all or whether there is some reason, we can't host such a community. If the proposal seems to have merit, it'll get a [status-definition] tag, otherwise it becomes [status-declined] with an explanation of the reasons.
-
Proposals with a [status-definition] tag will be continously reviewed by the team. When we see, that all major questions before launch (see below) are resolved and that a large-enough community1 is there to give it a try, we'll change the tag to [status-pending]. If there are still open issues, we'll probably comment here and there to start some useful discussions.
There is no time-limit for the definition phase, but we'll probably slap [status-declined] on some posts that have been in definition for a few months. :)
-
Once the proposal is pending, we'll consider the last details (mostly URLs, logo and primary header color). If there are suggestions from the community, we'll take them into account, too.
-
Once this internal process is finished, we'll launch this site. As all of our devs are volunteers (and only few people have access to the production systems), this might take some time. Once done, we'll edit the post to link to the new site and add a [status-launched] tag to the suggestion.
The questions communities need to answer are:
- site name (ex. Cooking or Writing, not potential brand names)
- site scope -- what's on- and off-topic (only overview, details will be clarified later in the meta category)
- special features needed (more categories, MathJax, Syntax highlighting, ...)2
These questions can but needn't be clarified before launching. If they aren't, we'll make preliminary decisions:
- URLs (X.codidact.com)
- logo ideas
- who should be the initially appointed moderators
-
Factors we take into account are mostly count of users engaging at the proposal (should be around or more than 10) and count of site "kickstarters" (should be at least 2-3). This will likely be higher for a niché community like RPG than one everyone can contribute to like Cooking. ↩
-
If this needs some development time, the launch might be delayed. If it's too complex, we'll probably ask, whether it can be deferred until after launch. ↩
0 comment threads
1 comment thread