Post History

### 1. Limiting people who can create and vote on proposals

Besides everything, this is great. First, I suggest making a limit [^1] for people who can propose proposals. [^2] Because before suggesting new communities, you should already have a *fair knowledge* of interacting with Codidact communities, this will prove that you are capable of managing a successful community and to prevent [proposals like this](https://meta.codidact.com/posts/279809).

I can also suggest a limit [^3] for people who vote on proposals not everyone should be able to vote, this will greatly prevent sockpuppets and proposals. Other than reputation, maybe gaining abilities like [Edit Posts](https://meta.codidact.com/abilities/edit_posts) or higher across your network profile is also fair enough to give you the ability to vote. [^4] I just want to make sure that people have spent a fair time here helping the community and know how to deal with it.

### 2. A large number of users

Besides all these limits, you shouldn't launch proposals with less than 50 users [^5] who are willing to contribute. 9 or 10 people like what I've seen in proposals isn't great to launch a whole community, they're not superusers, just normal ones. So wait until the proposal has *a lot* of people who are willing to spend some time around. And don't focus on moderators. Focus on finding the *right people* and, eventually you will find people who are willing to moderate.

### 3. Accurately know the scope before the launch [^6]

The scope should also be pre-defined (almost complete) accurately before launching the community. A great community is a community that knows *who they are*. Not being able to identify the scope accurately before launch indicates that this's not going to be a successful community.

### 4. Emailing people

Emailing people upon the launch of the community is *necessary* because life is busy and we can even forget that we wanted to participate in such a community also because proposals may take years before they're ready to launch.

### 5. Proposals duration

Personally, I don't mind if a successful proposal takes up to 10 years to launch better than a 2-year or less community that isn't successful.

[^1]: While reputation is not a metric for me but it's an *indicator* that you have some quality posts here.

[^2]: I think 200 reputation (total reputation across all communities aka [network profile](https://meta.codidact.com/posts/285414/285415)) is a great, fair limit. Numbers are subject to change.

[^3]: 50 reputation across your network profile is great enough. Again, numbers are subject to change, I'm just proposing the idea as a whole. But I find those numbers are pretty fair.

[^4]: Or maybe creating a new ability called "Vote on Proposals" that once you gain can vote on any proposal, probably a combination of some quality posts and edits across the network.

[^5]: Probably even more, I can't find any reason to launch a community with less than 50 users.

[^6]: I'm writing this because I've saw posts in some communities that are still discussing their scope to this day while it's great to have discussions, something like scope should've been pretty known and defined before launch.