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.

Post History

62%
+3 −1
Meta Strategy to migrate meaningful content from Stack Overflow

Please note that migrate in this context means grabbing the exact post as-is from a SE site and importing it here. This is allowed, with attribution given, as per licensing model. Codidact staff c...

posted 4y ago by Lundin‭  ·  edited 4y ago by Lundin‭

Answer
#3: Post edited by user avatar Lundin‭ · 2020-09-09T13:22:27Z (about 4 years ago)
  • Please note that _migrate_ in this context means grabbing the exact post as-is from a SE site and importing it here. This is allowed, with attribution given, as per licensing model. Codidact staff can help out with this. Check out the Writing or Scientific Speculation communities for examples, imported posts get a little "hamburger" SO logo tag.
  • Do you actually mean migrating or do you just mean asking the question anew here? The latter is of course perfectly fine.
  • I think that the only meaningful content to actually migrate would be canonical reference materials posts. Of which there probably exist some 10 to 50 posts per major programming language or framework, no more.
  • The vast majority of closed posts on SO, no matter the close reason, are actually crap. Digging through that sewer in search for things that might be valuable doesn't sound like something anyone should waste time on.
  • In case you do find something valuable there, that's closed but unanswered, then I'd just re-formulate the question and ask it anew here. Because it is very likely that the question had other more fundamental problems than just being subjective or opinion-based. Too broad questions would be too broad here as well, for example.
  • Please note that _migrate_ in this context means grabbing the exact post as-is from a SE site and importing it here. This is allowed, with attribution given, as per licensing model. Codidact staff can help out with this. Check out the Writing or Scientific Speculation communities for examples, imported posts get a little "hamburger" SO logo tag.
  • Do you actually mean migrating or do you just mean asking the question anew here? The latter is of course perfectly fine.
  • I think that the only meaningful content to actually migrate would be canonical reference materials posts. Of which there probably exist some 10 to 50 posts per major programming language or framework, not more.
  • The vast majority of closed posts on SO, no matter the close reason, are actually crap. Digging through that sewer in search for things that might be valuable doesn't sound like something anyone should waste time on.
  • In case you do find something valuable there, that's closed but unanswered, then I'd just re-formulate the question and ask it anew here. Because it is very likely that the question had other more fundamental problems than just being subjective or opinion-based. Too broad questions would be too broad here as well, for example.
#2: Post edited by user avatar Lundin‭ · 2020-09-09T13:22:17Z (about 4 years ago)
  • Please note that _migrate_ in this context means grabbing the exact post as-is from a SE site and importing it here. This is allowed, with attribution given, as per licensing model. Codidact staff can help out with this. Check out the Writing or Scientific Speculation communities for examples, imported posts get a little "hamburger" SO logo tag.
  • Do you actually mean migrating or do you just mean asking the question anew here? The latter is of course perfectly fine.
  • I think that the only meaningful content to actually migrate would be canonical reference materials posts. Of which there probably exist some 10 to 50 posts per major programming language or framework.
  • The vast majority of closed posts on SO, no matter the close reason, are actually crap. Digging through that sewer in search for things that might be valuable doesn't sound like something anyone should waste time on.
  • In case you do find something valuable there, that's closed but unanswered, then I'd just re-formulate the question and ask it anew here. Because it is very likely that the question had other more fundamental problems than just being subjective or opinion-based. Too broad questions would be too broad here as well, for example.
  • Please note that _migrate_ in this context means grabbing the exact post as-is from a SE site and importing it here. This is allowed, with attribution given, as per licensing model. Codidact staff can help out with this. Check out the Writing or Scientific Speculation communities for examples, imported posts get a little "hamburger" SO logo tag.
  • Do you actually mean migrating or do you just mean asking the question anew here? The latter is of course perfectly fine.
  • I think that the only meaningful content to actually migrate would be canonical reference materials posts. Of which there probably exist some 10 to 50 posts per major programming language or framework, no more.
  • The vast majority of closed posts on SO, no matter the close reason, are actually crap. Digging through that sewer in search for things that might be valuable doesn't sound like something anyone should waste time on.
  • In case you do find something valuable there, that's closed but unanswered, then I'd just re-formulate the question and ask it anew here. Because it is very likely that the question had other more fundamental problems than just being subjective or opinion-based. Too broad questions would be too broad here as well, for example.
#1: Initial revision by user avatar Lundin‭ · 2020-09-09T13:21:53Z (about 4 years ago)
Please note that _migrate_ in this context  means grabbing the exact post as-is from a SE site and importing it here. This is allowed, with attribution given, as per licensing model. Codidact staff can help out with this. Check out the Writing or Scientific Speculation communities for examples, imported posts get a little "hamburger" SO logo tag.

Do you actually mean migrating or do you just mean asking the question anew here? The latter is of course perfectly fine.

I think that the only meaningful content to actually migrate would be canonical reference materials posts. Of which there probably exist some 10 to 50 posts per major programming language or framework.

The vast majority of closed posts on SO, no matter the close reason, are actually crap. Digging through that sewer in search for things that might be valuable doesn't sound like something anyone should waste time on. 

In case you do find something valuable there, that's closed but unanswered, then I'd just re-formulate the question and ask it anew here. Because it is very likely that the question had other more fundamental problems than just being subjective or opinion-based. Too broad questions would be too broad here as well, for example.