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
Parent
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
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.
It would be much better split into separate questions. - Users have to scroll, ctrl-f search, or wade through a lot …
1y ago
Hi and welcome to the site. :) I think the idea of a canonical like the one you linked is great. A lot of newbies hav …
1y ago
You are a thoughtful person, aren't you? /me bows in thanks I for one think it would be valuable, even if you were to …
1y ago
I would recommend to post it anew here as a self-answered Q&A and update it if needed. You can use the "works for me" re …
1y ago
Perhaps the best way to deal with your SO content is to note in a comment that the canonical answer is no longer maintai …
1y ago
Post
Perhaps the best way to deal with your SO content is to note in a comment that the canonical answer is no longer maintained by the canonical author, and / or maybe change your username to "username - no longer updating answers since dd/mm/yyyy" if that's your stance across the whole site, to get the message across. That way you protect your own reputation by highlighting that the content is being allowed to go stale and should no longer be relied on, but at the same time by allowing it to rot you do nothing to help SO (because frankly a deleted answer can be better than one that has been allowed to become horribly out of date, and if others follow a similar approach eventually the SO rot will start to show and their reputation will suffer.
2 comment threads