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

75%

+7 −1

Meta Importing Selected Q&A?

Just mass-importing from elsewhere is generally bad. Look at the mess this has made of the Outdoors and Scientific Speculation sites, for example. Bringing over your own content is a bit different...

posted 4y ago by Olin Lathrop‭ · edited 4y ago by Olin Lathrop‭

Answer

#3: Post edited by

Olin Lathrop‭ · 2020-08-11T13:26:18Z (over 4 years ago)

Copy Link

Raw

Markdown

~~Importing from elsewhere is generally bad. Look at the mess this has made of the Outdoors and Scientific Speculation sites, for example.~~
However, bringing over your own content is a bit different. I did this in a few cases to get the EE site going. However, don't just copy the whole Q&A. Here are some guidelines:<ol>
<li>Only do it if your contribution is the major content. The best case is if the source is a canonical question that you both asked and answered.
<li>If you wrote an in-depth answer to someone else's question, then paraphrase the question yourself here. Since you know what parts are relevant, and what the eventual answer is, you should be able to do a better job of asking the right question than the OP.
Don't copy the text, but re-write it on your own, using only the meaning in your head as a guide.
<li>Don't just copy your answer. In this case, since you wrote it, it's OK to start with the original text. However, there is always something that can be said better. Read everything over like the original is a rough draft. Fix spellings, awkward wording, maybe re-arrange the order of thoughts to make them answer easier to follow, add headings, maybe a diagram, etc.
</ol>
The point is to make the post here better than the original, not just a copy of it.
For example, I started with <a href="https://electronics.stackexchange.com/questions/23645/how-do-i-calculate-the-required-value-for-a-pull-up-resistor">this SE post</a> and created <a href="https://electrical.codidact.com/questions/276136">this Codadict post</a> from it. In that case, I didn't write the original question, so I wrote it more to the point in my own words, and with a diagram. It is less obvious, but I also did a few edits on my answer before posting it here.

Just mass-importing from elsewhere is generally bad. Look at the mess this has made of the Outdoors and Scientific Speculation sites, for example.
Bringing over your own content is a bit different. I did this in a few cases to get the EE site going. However, don't just copy the whole Q&A. Here are some guidelines:<ol>
<li>Only do it if your contribution is the major content. The best case is if the source is a canonical question that you both asked and answered.
<li>If you wrote an in-depth answer to someone else's question, then paraphrase the question yourself here. Since you know what parts are relevant, and what the eventual answer is, you should be able to do a better job of asking the right question than the OP.
Don't copy the text, but re-write it on your own, using only the meaning in your head as a guide.
<li>Don't just copy your answer. In this case, since you wrote it, it's OK to start with the original text. However, there is always something that can be said better. Read everything over like the original is a rough draft. Fix spellings, awkward wording, maybe re-arrange the order of thoughts to make them answer easier to follow, add headings, maybe a diagram, etc.
</ol>
The point is to make the post here better than the original, not just a copy of it.
For example, I started with <a href="https://electronics.stackexchange.com/questions/23645/how-do-i-calculate-the-required-value-for-a-pull-up-resistor">this SE post</a> and created <a href="https://electrical.codidact.com/questions/276136">this Codadict post</a> from it. In that case, I didn't write the original question, so I wrote it more to the point in my own words, and with a diagram. It is less obvious, but I also did a few edits on my answer before posting it here.

#2: Post edited by

Olin Lathrop‭ · 2020-08-11T13:25:18Z (over 4 years ago)

Copy Link

Raw

Markdown

Importing from elsewhere is generally bad. Look at the mess this has made of the Outdoors and Scientific Speculation sites, for example.
However, bringing over your own content is a bit different. I did this in a few cases to get the EE site going. However, don't just copy the whole Q&A. Here are some guidelines:<ol>
<li>Only do it if your contribution is the major content. The best case is if the source is a canonical question that you both asked and answered.
<li>If you wrote an in-depth answer to someone else's question, then paraphrase the question yourself here. Since you know what parts are relevant, and what the eventual answer is, you should be able to do a better job of asking the right question than the OP.
Don't copy the text, but re-write it on your own, using only the meaning in your head as a guide.
<li>Don't just copy your answer. In this case, since you originally wrote it, it's OK to start with the original text. However, there is always something that can be said better. Read everything over like the original is a rough draft. Fix spellings, awkward wording, maybe re-arrange the order of thoughts to make them answer easier to follow, add headings, maybe a diagram, etc.
</ol>
The point is to make the post here better than the original, not just a copy of it.
For example, I started with <a href="https://electronics.stackexchange.com/questions/23645/how-do-i-calculate-the-required-value-for-a-pull-up-resistor">this SE post</a> and created <a href="https://electrical.codidact.com/questions/276136">this Codadict post</a> from it. In that case, I didn't write the original question, so I wrote it more to the point in my own words, and with a diagram. It is less obvious, but I also did a few edits on my answer before posting it here.

Importing from elsewhere is generally bad. Look at the mess this has made of the Outdoors and Scientific Speculation sites, for example.
However, bringing over your own content is a bit different. I did this in a few cases to get the EE site going. However, don't just copy the whole Q&A. Here are some guidelines:<ol>
<li>Only do it if your contribution is the major content. The best case is if the source is a canonical question that you both asked and answered.
<li>If you wrote an in-depth answer to someone else's question, then paraphrase the question yourself here. Since you know what parts are relevant, and what the eventual answer is, you should be able to do a better job of asking the right question than the OP.
Don't copy the text, but re-write it on your own, using only the meaning in your head as a guide.
<li>Don't just copy your answer. In this case, since you wrote it, it's OK to start with the original text. However, there is always something that can be said better. Read everything over like the original is a rough draft. Fix spellings, awkward wording, maybe re-arrange the order of thoughts to make them answer easier to follow, add headings, maybe a diagram, etc.
</ol>
The point is to make the post here better than the original, not just a copy of it.
For example, I started with <a href="https://electronics.stackexchange.com/questions/23645/how-do-i-calculate-the-required-value-for-a-pull-up-resistor">this SE post</a> and created <a href="https://electrical.codidact.com/questions/276136">this Codadict post</a> from it. In that case, I didn't write the original question, so I wrote it more to the point in my own words, and with a diagram. It is less obvious, but I also did a few edits on my answer before posting it here.

#1: Initial revision by

Olin Lathrop‭ · 2020-08-11T13:22:35Z (over 4 years ago)

Copy Link

Raw

Markdown

Importing from elsewhere is generally bad. Look at the mess this has made of the Outdoors and Scientific Speculation sites, for example.

However, bringing over your own content is a bit different. I did this in a few cases to get the EE site going. However, don't just copy the whole Q&A. Here are some guidelines:<ol>

<li>Only do it if your contribution is the major content. The best case is if the source is a canonical question that you both asked and answered.

<li>If you wrote an in-depth answer to someone else's question, then paraphrase the question yourself here. Since you know what parts are relevant, and what the eventual answer is, you should be able to do a better job of asking the right question than the OP.

Don't copy the text, but re-write it on your own, using only the meaning in your head as a guide.

<li>Don't just copy your answer. In this case, since you originally wrote it, it's OK to start with the original text. However, there is always something that can be said better. Read everything over like the original is a rough draft. Fix spellings, awkward wording, maybe re-arrange the order of thoughts to make them answer easier to follow, add headings, maybe a diagram, etc.

</ol>

The point is to make the post here better than the original, not just a copy of it.

For example, I started with <a href="https://electronics.stackexchange.com/questions/23645/how-do-i-calculate-the-required-value-for-a-pull-up-resistor">this SE post</a> and created <a href="https://electrical.codidact.com/questions/276136">this Codadict post</a> from it. In that case, I didn't write the original question, so I wrote it more to the point in my own words, and with a diagram. It is less obvious, but I also did a few edits on my answer before posting it here.

Communities

Post History