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 »
Meta

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on To transfer, or not to, that is the question: whether 'tis nobler to let it stay or to take arms against Stack Overflow's dominance of FAQ canonicals

Post

To transfer, or not to, that is the question: whether 'tis nobler to let it stay or to take arms against Stack Overflow's dominance of FAQ canonicals

+13
−0

Some of you may know me from Stack Overflow or the broader network. In light of recent actions by the company, I finally decided to move over to Codidact. I am a subject matter expert on Google Apps Script (among other fields) and would like to move my canonical on extremely common errors developers encounter in its entirety.

As of now, the canonical is slowly rotting away there due to the split in opinion on what to do with it, cycling between closure and reopen with little incentive for me to keep it up to date or rekindle the discussion (especially now).

The question I have regarding the move consists of a couple of tightly coupled issues I would like to know the community's stance on before making the decision so as I know how to act:

  • Does the community feel the transferred content will be of enough value to it to warrant one?
  • Would the canonical be good as is (with some updates) or would it be better to split it into several self-answered canonicals?
  • Would it make more sense to make it an article (unfortunately, I am not sure if articles are enabled for the community in the first place)?1

I am aware of the Strategy to migrate meaningful content from Stack Overflow discussion which seems to have a conclusion that original content is preferred (for obvious reasons), so I have to note that my intention is to delete2 the Q&A there and do an extensive overhaul should the canonical be accepted.

With the personal concerns outlined, I would like this Q&A to serve as a basis for a broader discussion on how the community prefers such content to be transferred over (if at all, but from the discussions I've seen, it seems to be generally welcomed).


1 This issue stems from the Asking and answering FAQ style questions discussion and Monica Cellio's answer specifically.

2 It's been suggested in an outside channel that in case of the move it might be more beneficial to keep the original with a note that the up-to-date content can be found here, so that's another issue I would like to get input from the community.

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

2 comment threads

Article (4 comments)
Transfer, but split in Q&A for each specific issue (2 comments)
Transfer, but split in Q&A for each specific issue
Alexei‭ wrote 10 months ago

Transferring such content is a great idea. I am wondering if it makes sense to split in Q&As for each specific error/case.

Pros:

  • an answer is more to the point and does not mix somewhat unrelated errors/issues
  • easier to link to the answer in case of duplicate questions

Cons:

  • requires more work, but it is easier to point to an existing answer in case of duplicates
Oleg Valter‭ wrote 10 months ago

Yeah, that's a viable option that I am considering, especially given that it'll pretty much fill the whole niche of content if done properly. Requiring more work is basically a non-issue for me, as I'll be more than happy to do that work should that be the direction to go.