Return to Answer

You are correct that some of these questions may not technically be closed as an "exact duplicate" on the actual site — but for the purpose of presenting the strongest possible Definition for this proposal, the linked questions generally cover much the same topic space, even if they're not technically exact duplicates.

###Why "Top Example Questions" Matter

When a proposal nears the end of its "Definition" phase, it's about to undergo a final review by the Community Team to see if it should continue on towards becoming a Stack Exchange site. At this stage, it would be unwise to bulk up your "top example questions" with questions which do not add to your scope. Unfortunately, if the viability or breadth of a proposal comes into question, it is not physically possible for us to go back and "Let to fix that {problem} in Definition later." Once the proposal goes into "Commitment", there's no way to go back. It's a known short-coming in the process, but it IS a binary decision we have to live with — "pass" or "close".

That's why I spend so much time trying to assure we're not going to end up on the wrong end of a problem. There are only 40 example questions to justify the entire need for this site. That is why I combine similar questions before the proposal goes into final evaluation… to present the strongest possible case for creating this site.

You are correct that some of these questions may not technically be closed as an "exact duplicate" on the actual site — but for the purpose of presenting the strongest possible Definition for this proposal, the linked questions generally cover much the same topic space, even if they're not technically exact duplicates.

###Why "Top Example Questions" Matter

When a proposal nears the end of its "Definition" phase, it's about to undergo a final review by the Community Team to see if it should continue on towards becoming a Stack Exchange site. At this stage, it would be unwise to bulk up your "top example questions" with questions which do not add to your scope. Unfortunately, if the viability or breadth of a proposal comes into question, it is not physically possible for us to go back and "Let them fix that {problem} in Definition later." Once the proposal goes into "Commitment", there's no way to go back. It's a known short-coming in the process, but it IS a binary decision we have to live with — "pass" or "close".

That's why I spend so much time trying to assure we're not going to end up on the wrong end of a problem. There are only 40 example questions to justify the entire need for this site. That is why I combine similar questions before the proposal goes into final evaluation… to present the strongest possible case for creating this site.

You are correct that some of these questions may not technically be closed as an "exact duplicate" on the actual site — but for the purpose of presenting the strongest possible Definition for this proposal, the linked questions generally cover much the same topic space, even if they're not technically exact duplicates.

###Why "Top Example Questions" Matter

When a proposal nears the end of its "Definition" phase, it's about to undergo a final review by the Community Team to see if it should be allowed to proceed towards becoming a Stack Exchange site. At this stage, it would be unwise to bulk up your "top example questions" with questions which do not add to your scope. Unfortunately, if the viability or breadth of a proposal comes into question, it is not physically possible for us to go back and "Let to fix that {problem} in Definition later." Once the proposal goes into "Commitment", there's no way to go back. It's a known short-coming in the process, but it IS a binary decision we have to live with — "pass" or "close".

That's why I spend so much time trying to assure we're not going to end up on the wrong end of a problem. There are only 40 example questions to justify the entire need for this site. That is why I combine similar questions before the proposal goes into final evaluation… to present the strongest possible case for creating this site.

You are correct that some of these questions may not technically be closed as an "exact duplicate" on the actual site — but for the purpose of presenting the strongest possible Definition for this proposal, the linked questions generally cover much the same topic space, even if they're not technically exact duplicates.

###Why "Top Example Questions" Matter

When a proposal nears the end of its "Definition" phase, it's about to undergo a final review by the Community Team to see if it should continue on towards becoming a Stack Exchange site. At this stage, it would be unwise to bulk up your "top example questions" with questions which do not add to your scope. Unfortunately, if the viability or breadth of a proposal comes into question, it is not physically possible for us to go back and "Let to fix that {problem} in Definition later." Once the proposal goes into "Commitment", there's no way to go back. It's a known short-coming in the process, but it IS a binary decision we have to live with — "pass" or "close".

That's why I spend so much time trying to assure we're not going to end up on the wrong end of a problem. There are only 40 example questions to justify the entire need for this site. That is why I combine similar questions before the proposal goes into final evaluation… to present the strongest possible case for creating this site.

You are correct that some of these questions may not technically be closed as an "exact duplicate" on the actual site — but for the purpose of presenting the strongest possible Definition for this proposal, the linked questions generally cover much the same topic space, even if they're not technically exact duplicates.

###Why "Top Example Questions" Matter

When a proposal nears the end of its "Definition" phase, it's about to undergo a final review by the Community Team to see if it should be allowed to proceed towards becoming a Stack Exchange site. At this stage, it would be unwise to bulk up your "top example questions" with questions which do not add to your scope. Unfortunately, if the viability or breadth of a proposal comes into question, it is not physically possible for us to go back and "Let to fix that {problem} in Definition." Once the proposal goes into "Commitment", there's no way to go back. It's a known short-coming in the process, but it IS a binary decision we have to live with — "pass" or "close".

That's why I spend so much time trying to assure we're not going to end up on the wrong end of a problem. There are only 40 example questions to justify the entire need for this site. That is why I combine similar questions before the proposal goes into final evaluation… to present the strongest possible case for creating this site.

You are correct that some of these questions may not technically be closed as an "exact duplicate" on the actual site — but for the purpose of presenting the strongest possible Definition for this proposal, the linked questions generally cover much the same topic space, even if they're not technically exact duplicates.

###Why "Top Example Questions" Matter

When a proposal nears the end of its "Definition" phase, it's about to undergo a final review by the Community Team to see if it should be allowed to proceed towards becoming a Stack Exchange site. At this stage, it would be unwise to bulk up your "top example questions" with questions which do not add to your scope. Unfortunately, if the viability or breadth of a proposal comes into question, it is not physically possible for us to go back and "Let to fix that {problem} in Definition later." Once the proposal goes into "Commitment", there's no way to go back. It's a known short-coming in the process, but it IS a binary decision we have to live with — "pass" or "close".

That's why I spend so much time trying to assure we're not going to end up on the wrong end of a problem. There are only 40 example questions to justify the entire need for this site. That is why I combine similar questions before the proposal goes into final evaluation… to present the strongest possible case for creating this site.