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 »
Q&A

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.

Comments on What should we do about tagging in Site Proposals?

Parent

What should we do about tagging in Site Proposals?

+4
−0

We need to figure out tags in the "Site Proposals" category. I noticed that some proposals were tagged "suggestion" and some "new-communities" and started to replace the former with the latter, and then I stopped and said "wait, everything here is a suggestion for a new community!".

For technical reasons we need to have some tag right now, but what should the tag(s) there be? Adding a tag for launched communities makes sense, and maybe one for proposals we've agreed we're not going to do, but that doesn't help with the initial tagging.

Or maybe everything is a status-something tag -- proposals start at status-proposed, and then we might retag to status-something-else as it moves through the process?

Ideas?

Superseded by the new Proposals site.

I can't close this question as superseded, maybe because the target is an article or maybe because it's in a different category.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+5
−0

It's a little awkward using a Q&A engine for site proposals at all, really, at least not without some more guidance, as not only the tagging is unclear, but what exactly goes in the "questions" and what goes in the "answers" needs some direction and refinement, and what is required before a site gets "accepted".

But for tagging specifically (let's solve one problem at a time, I suppose), I like your suggestion to have a required status-* tag for everything.

Here's a rough list off the top of my head, please pick it apart and take only what makes sense:

  • status-proposed
  • status-shortlist or status-refinement or something. (Not sure what to call this, but when it's "yeah, that's a good idea, and will probably get implemented, we just need to nail down some specifics like on-topic scope, what if anything to import, who is moderating, that kind of thing.")
  • status-needs-to-find-more-users
  • status-declined
  • status-accepted (Yes we will, we just haven't yet)
  • status-beta (maybe not needed right now as everything is beta-ish, but we may want to distinguish at some point between beta sites and "completed" sites?)
  • status-completed

In terms of other tagging, we might want to also group proposals by type in some other way, like technical, recreation, science, etc.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (10 comments)
General comments
Monica Cellio‭ wrote over 4 years ago

Thanks for these suggestions! Eventually we might come up with a special post type for proposals, but if we use the question for the pitch and answers to identify and resolve issues, I think the tools we have now will work. Key to this is editing in updates as things get decided in those comment threads on all those answers. :-)

Masked Man‭ wrote over 4 years ago

I agree with this wholeheartedly. One of the main design defects of SE was the assumption that everything must be organized as Q&A. When you only have a hammer, everything looks like a finger. I am somewhat disappointed that Codidact chose to take the same path. A site proposal is a proposal, it is not a question. There's no need to fit a square peg in a round hole, except that round holes is all that we have got.

Masked Man‭ wrote over 4 years ago

As they say in SE world, this is an XY Problem. The question is not what tags we should use, it is why do we try to shoehorn a proposal into a question.

ArtOfCode‭ wrote over 4 years ago

Codidact hasn't chosen to take the same path, @MaskedMan - we recognised the downsides of that approach too. We just haven't got to that point of development yet; other features have been more important. It hasn't been forgotten.

Monica Cellio‭ wrote over 4 years ago

@MaskedMan, Codidact is building a lot more capabilities, including other post types beyond questions and answers. We're not there yet, but rather than waiting for everything to be done before launching anything, we decided to start with what we have, which is enough for immediate needs of communities that want to be here now, and we'll keep working on improving it. What you see now isn't the only stuff you'll ever see.

Masked Man‭ wrote over 4 years ago

@ArtOfCode Glad to know that Codidact is aware of the design defect. I'm still skeptical especially with "Q&A" mentioned 4 times on the home page. I do hope Codidact will "fix" it eventually, and also make Q&A optional for communities that don't need them. I will wait until everything is ready to comment on it further. The proof is in the pudding.

ArtOfCode‭ wrote over 4 years ago

@MaskedMan The basic idea is that Q&A is the core concept; it works really well for a lot of things, which is why you see it mentioned in a number of places - it's "Q&A-based" software. That doesn't mean we stop there, though - we have other types of post planned.

Masked Man‭ wrote over 4 years ago

If you think about it, there isn't much of a difference between "we will give you only Q&A" and "we will give you other things, only if you also take Q&A". I really wish Codidact would stop being SE-centric in their thinking. The other day, some SE veteran was wondering why downvote piling is a problem if we make "positive changes" so that it doesn't affect your rep. I do hope some day Codidact will come out with fresh ideas. Until then, retired in restricted mode, it is.

Mithrandir24601‭ wrote over 4 years ago

@MaskedMan I believe you're referring to me... And that's not what I was saying, which was that we had ideas for dealing with things like downvote piling, of which getting rid of rep entirely is one. I used the phrase "getting rid of rep", so I'd appreciate people not misrepresenting what I said. I very much agree that downvote piling is a problem and given that I also used the phrase "try and fix these issues", I'd like to know how I came across as disagreeing with that.

Mithrandir24601‭ wrote over 4 years ago

We have a lot of ideas, just because I didn't list them all doesn't mean they don't exist and to be honest, I felt frustrated and mocked enough at seeing phrases like "Oh dear, here we go again" that I had no wish to continue the discussion

Skipping 4 deleted comments.