Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Users Search
Help Dashboard Sign In Sign Up
Q&A Blog
Q&A
Posts Tags Edits
Ask Question

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

42%
+1 −2
Q&A Our site incubator concept needs a re-think

I don't know whether I like the following idea better or worse than the current approach with a tag for each proposed community, but I agree we could benefit from discussion of new ideas, so here's...

posted 1mo ago by trichoplax‭  ·  edited 1mo ago by trichoplax‭

Answer
#4: Post edited by user avatar trichoplax‭ · 2024-09-14T21:30:14Z (about 1 month ago)
Typo
  • I don't know whether I like the following idea better or worse than the current approach with a tag for each proposed community, but I agree we could benefit from discussion of new ideas, so here's an idea to discuss. Maybe discussion will lead to something better than either.
  • ## Category per proposed community
  • ### Process
  • - If I have an idea for a new community, I add a description to the Descriptions category (as currently).
  • - A moderator sees the new description and responds by creating a new category with that name, with the first paragraph of the description as the category description at the top of the page.
  • - A link can now be added from the post in the Descriptions category to its new dedicated category.
  • - Anyone can now add example questions to this category, and answer them and vote and comment on them.
  • ### Less Codidact experience needed
  • This means that the category only contains questions for this specific proposed community, and there is a community-specific description at the top of the category page, so people unfamiliar with Codidact can be given a link directly to the category and not have to find their way from the Descriptions category.
  • ### Meta
  • Should Meta questions be asked
  • - In the existing Meta category
  • - In the relevant proposed community category with the tag "meta"?
  • - In an individual community-name-meta category per proposed community?
  • I'd lean towards one of the first two, to keep the number of categories down.
  • ### Tags
  • Currently all questions are in one category, so a tag name that happens to apply to two or more proposed communities will either have a description that only applies to one of them (whoever edited first), or has sections for different communities, making it confusing for people not experienced with how Proposals works.
  • With a category per community, there could also be a tag set per category (the software already supports this - it's an option an admin can select). This way, a tag in the Invasive Species category has a description unique to that category, even if a tag with the same name also exists in Board Games or Politics.
  • I don't know whether I like the following idea better or worse than the current approach with a tag for each proposed community, but I agree we could benefit from discussion of new ideas, so here's an idea to discuss. Maybe discussion will lead to something better than either.
  • ## Category per proposed community
  • ### Process
  • - If I have an idea for a new community, I add a description to the Descriptions category (as currently).
  • - A moderator sees the new description and responds by creating a new category with that name, with the first paragraph of the description as the category description at the top of the page.
  • - A link can now be added from the post in the Descriptions category to its new dedicated category.
  • - Anyone can now add example questions to this category, and answer them and vote and comment on them.
  • ### Less Codidact experience needed
  • This means that the category only contains questions for this specific proposed community, and there is a community-specific description at the top of the category page, so people unfamiliar with Codidact can be given a link directly to the category and not have to find their way from the Descriptions category.
  • ### Meta
  • Should Meta questions be asked
  • - In the existing Meta category
  • - In the relevant proposed community category with the tag "meta"?
  • - In an individual community-name-meta category per proposed community?
  • I'd lean towards one of the first two, to keep the number of categories down.
  • ### Tags
  • Currently all questions are in one category, so a tag name that happens to apply to two or more proposed communities will either have a description that only applies to one of them (whoever edited first), or have sections for different communities, making it confusing for people not experienced with how Proposals works.
  • With a category per community, there could also be a tag set per category (the software already supports this - it's an option an admin can select). This way, a tag in the Invasive Species category has a description unique to that category, even if a tag with the same name also exists in Board Games or Politics.
#3: Post edited by user avatar trichoplax‭ · 2024-09-14T21:28:08Z (about 1 month ago)
Mention link from description post to its new category
  • I don't know whether I like the following idea better or worse than the current approach with a tag for each proposed community, but I agree we could benefit from discussion of new ideas, so here's an idea to discuss. Maybe discussion will lead to something better than either.
  • ## Category per proposed community
  • ### Process
  • - If I have an idea for a new community, I add a description to the Descriptions category (as currently).
  • - A moderator sees the new description and responds by creating a new category with that name, with the first paragraph of the description as the category description at the top of the page.
  • - Anyone can now add example questions to this category, and answer them and vote and comment on them.
  • ### Less Codidact experience needed
  • This means that the category only contains questions for this specific proposed community, and there is a community-specific description at the top of the category page, so people unfamiliar with Codidact can be given a link directly to the category and not have to find their way from the Descriptions category.
  • ### Meta
  • Should Meta questions be asked
  • - In the existing Meta category
  • - In the relevant proposed community category with the tag "meta"?
  • - In an individual community-name-meta category per proposed community?
  • I'd lean towards one of the first two, to keep the number of categories down.
  • ### Tags
  • Currently all questions are in one category, so a tag name that happens to apply to two or more proposed communities will either have a description that only applies to one of them (whoever edited first), or has sections for different communities, making it confusing for people not experienced with how Proposals works.
  • With a category per community, there could also be a tag set per category (the software already supports this - it's an option an admin can select). This way, a tag in the Invasive Species category has a description unique to that category, even if a tag with the same name also exists in Board Games or Politics.
  • I don't know whether I like the following idea better or worse than the current approach with a tag for each proposed community, but I agree we could benefit from discussion of new ideas, so here's an idea to discuss. Maybe discussion will lead to something better than either.
  • ## Category per proposed community
  • ### Process
  • - If I have an idea for a new community, I add a description to the Descriptions category (as currently).
  • - A moderator sees the new description and responds by creating a new category with that name, with the first paragraph of the description as the category description at the top of the page.
  • - A link can now be added from the post in the Descriptions category to its new dedicated category.
  • - Anyone can now add example questions to this category, and answer them and vote and comment on them.
  • ### Less Codidact experience needed
  • This means that the category only contains questions for this specific proposed community, and there is a community-specific description at the top of the category page, so people unfamiliar with Codidact can be given a link directly to the category and not have to find their way from the Descriptions category.
  • ### Meta
  • Should Meta questions be asked
  • - In the existing Meta category
  • - In the relevant proposed community category with the tag "meta"?
  • - In an individual community-name-meta category per proposed community?
  • I'd lean towards one of the first two, to keep the number of categories down.
  • ### Tags
  • Currently all questions are in one category, so a tag name that happens to apply to two or more proposed communities will either have a description that only applies to one of them (whoever edited first), or has sections for different communities, making it confusing for people not experienced with how Proposals works.
  • With a category per community, there could also be a tag set per category (the software already supports this - it's an option an admin can select). This way, a tag in the Invasive Species category has a description unique to that category, even if a tag with the same name also exists in Board Games or Politics.
#2: Post edited by user avatar trichoplax‭ · 2024-09-14T21:25:17Z (about 1 month ago)
Remove ambiguity
  • I don't know whether I like this idea better or worse than the current approach with a tag for each proposed community, but I agree we could benefit from discussion of new ideas, so here's an idea to discuss. Maybe discussion will lead to something better than either.
  • ## Category per proposed community
  • ### Process
  • - If I have an idea for a new community, I add a description to the Descriptions category (as currently).
  • - A moderator sees the new description and responds by creating a new category with that name, with the first paragraph of the description as the category description at the top of the page.
  • - Anyone can now add example questions to this category, and answer them and vote and comment on them.
  • ### Less Codidact experience needed
  • This means that the category only contains questions for this specific proposed community, and there is a community-specific description at the top of the category page, so people unfamiliar with Codidact can be given a link directly to the category and not have to find their way from the Descriptions category.
  • ### Meta
  • Should Meta questions be asked
  • - In the existing Meta category
  • - In the relevant proposed community category with the tag "meta"?
  • - In an individual community-name-meta category per proposed community?
  • I'd lean towards one of the first two, to keep the number of categories down.
  • ### Tags
  • Currently all questions are in one category, so a tag name that happens to apply to two or more proposed communities will either have a description that only applies to one of them (whoever edited first), or has sections for different communities, making it confusing for people not experienced with how Proposals works.
  • With a category per community, there could also be a tag set per category (the software already supports this - it's an option an admin can select). This way, a tag in the Invasive Species category has a description unique to that category, even if a tag with the same name also exists in Board Games or Politics.
  • I don't know whether I like the following idea better or worse than the current approach with a tag for each proposed community, but I agree we could benefit from discussion of new ideas, so here's an idea to discuss. Maybe discussion will lead to something better than either.
  • ## Category per proposed community
  • ### Process
  • - If I have an idea for a new community, I add a description to the Descriptions category (as currently).
  • - A moderator sees the new description and responds by creating a new category with that name, with the first paragraph of the description as the category description at the top of the page.
  • - Anyone can now add example questions to this category, and answer them and vote and comment on them.
  • ### Less Codidact experience needed
  • This means that the category only contains questions for this specific proposed community, and there is a community-specific description at the top of the category page, so people unfamiliar with Codidact can be given a link directly to the category and not have to find their way from the Descriptions category.
  • ### Meta
  • Should Meta questions be asked
  • - In the existing Meta category
  • - In the relevant proposed community category with the tag "meta"?
  • - In an individual community-name-meta category per proposed community?
  • I'd lean towards one of the first two, to keep the number of categories down.
  • ### Tags
  • Currently all questions are in one category, so a tag name that happens to apply to two or more proposed communities will either have a description that only applies to one of them (whoever edited first), or has sections for different communities, making it confusing for people not experienced with how Proposals works.
  • With a category per community, there could also be a tag set per category (the software already supports this - it's an option an admin can select). This way, a tag in the Invasive Species category has a description unique to that category, even if a tag with the same name also exists in Board Games or Politics.
#1: Initial revision by user avatar trichoplax‭ · 2024-09-14T21:24:41Z (about 1 month ago) 
I don't know whether I like this idea better or worse than the current approach with a tag for each proposed community, but I agree we could benefit from discussion of new ideas, so here's an idea to discuss. Maybe discussion will lead to something better than either.

## Category per proposed community
### Process
- If I have an idea for a new community, I add a description to the Descriptions category (as currently).
- A moderator sees the new description and responds by creating a new category with that name, with the first paragraph of the description as the category description at the top of the page.
- Anyone can now add example questions to this category, and answer them and vote and comment on them.

### Less Codidact experience needed
This means that the category only contains questions for this specific proposed community, and there is a community-specific description at the top of the category page, so people unfamiliar with Codidact can be given a link directly to the category and not have to find their way from the Descriptions category.

### Meta
Should Meta questions be asked
- In the existing Meta category
- In the relevant proposed community category with the tag "meta"?
- In an individual community-name-meta category per proposed community?

I'd lean towards one of the first two, to keep the number of categories down.

### Tags
Currently all questions are in one category, so a tag name that happens to apply to two or more proposed communities will either have a description that only applies to one of them (whoever edited first), or has sections for different communities, making it confusing for people not experienced with how Proposals works.

With a category per community, there could also be a tag set per category (the software already supports this - it's an option an admin can select). This way, a tag in the Invasive Species category has a description unique to that category, even if a tag with the same name also exists in Board Games or Politics.