Timeline for Can similarity between a software paper and the software's documentation cause the paper to be rejected?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2022 at 13:54 | vote | accept | Mohammadreza Khoshbin | ||
| Jan 6, 2022 at 0:04 | comment | added | Buffy | That sounds right. Of course a publisher might balk if you overlap the paper too much with the docs - hence the paraphrasing advice. | |
| Jan 6, 2022 at 0:01 | comment | added | Mohammadreza Khoshbin | Understandable. What I gather from your answer is that not only this is not a problem, but if the documentation is published prior to submission a number of copyright headaches can be avoided. Is that right? | |
| Jan 5, 2022 at 23:51 | comment | added | Buffy | Sorry, but I don't press links. If you create the pictures then you have copyright to them also, just like the text. But if they come from other sources you may need permission, as well as cite the source. | |
| Jan 5, 2022 at 23:44 | comment | added | Mohammadreza Khoshbin | Thanks for the answer! Does this also hold for pictures? I'm thinking something like the following link from my other work: pyauxetic.readthedocs.io/en/latest/unit-cell-library/… | |
| Jan 5, 2022 at 23:41 | history | answered | Buffy | CC BY-SA 4.0 |