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.
Post History
This answer builds on Peter's answer (thanks!). I think we need to approach tags along two axes. One is tracking status of proposals, as suggested by Peter. We did this informally when I added "...
Answer
#2: Post edited
by
Monica Cellio
·
2020-05-14T22:54:14Z (over 4 years ago)
This answer builds on Peter's answer (thanks!).- I think we need to approach tags along two axes. One is tracking status of proposals, as suggested by Peter. We did this informally when I added "status-launched" to the Photography post, but we can and should track status through earlier stages too.
- The other axis is proposals versus ideas. We've been getting both types of suggestions. Proposals are more fully worked out; ideas are more like "can we have a site about X?". Ideas aren't ready to move forward yet because we need to find out if there's a community behind them -- but how do we find out if there's already a community here if not through a post? So I suggest having two tags, "ideas" and "proposals", with a requirement to use one or the other. Ideas can gather support and be refined into proposals, and people can more easily see what stage each suggestion is in.
- This answer builds on [Peter's answer](https://meta.codidact.com/a/74925/74934) (thanks!).
- I think we need to approach tags along two axes. One is tracking status of proposals, as suggested by Peter. We did this informally when I added "status-launched" to the Photography post, but we can and should track status through earlier stages too.
- The other axis is proposals versus ideas. We've been getting both types of suggestions. Proposals are more fully worked out; ideas are more like "can we have a site about X?". Ideas aren't ready to move forward yet because we need to find out if there's a community behind them -- but how do we find out if there's already a community here if not through a post? So I suggest having two tags, "ideas" and "proposals", with a requirement to use one or the other. Ideas can gather support and be refined into proposals, and people can more easily see what stage each suggestion is in.
#1: Initial revision
by
Monica Cellio
·
2020-05-14T21:34:18Z (over 4 years ago)
This answer builds on Peter's answer (thanks!). I think we need to approach tags along two axes. One is tracking status of proposals, as suggested by Peter. We did this informally when I added "status-launched" to the Photography post, but we can and should track status through earlier stages too. The other axis is proposals versus ideas. We've been getting both types of suggestions. Proposals are more fully worked out; ideas are more like "can we have a site about X?". Ideas aren't ready to move forward yet because we need to find out if there's a community behind them -- but how do we find out if there's already a community here if not through a post? So I suggest having two tags, "ideas" and "proposals", with a requirement to use one or the other. Ideas can gather support and be refined into proposals, and people can more easily see what stage each suggestion is in.