You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- 3For #1: Until your source code is subpoenaed by the judge and you sheepishly grin at the jury as they see your "rewrite".Jarrod Nettles– Jarrod Nettles2011-06-24 19:05:40 +00:00Commented Jun 24, 2011 at 19:05
- 2For #2: Copyright infringement is normally a civil matter, so there is legally no such thing as "guilty". If the preponderance of the evidence indicates that the OP infringed, that's all that's needed. For #3: That's not what the original question said.David Thornley– David Thornley2011-06-24 21:25:25 +00:00Commented Jun 24, 2011 at 21:25
- 1(1) It's not hard to spot a blatant plagiarism without seeing the source code. Besides, we're not in the habit here of advising people on how to get away with illegal and highly unethical acts. (2) Ignorantia juris non excusat (ignorance is not a defense) (3) Rewriting line-per-line is not learning. Rewriting line-per-line is definitely not just finding inspiration either. It's blatant plagiarism, plain and simple. I won't rehash it all here, but there are boatloads of legal documents and precedent supporting this.Greg Jackson– Greg Jackson2011-06-25 10:10:59 +00:00Commented Jun 25, 2011 at 10:10
- OK, so if I didn't rewrite line by line, but understood the algorithm, and then re implemented it in my own way. Ie a one man clean room operation. Is that different? If not, am I therefor not allowed to learn from any open source project?Chris Barry– Chris Barry2011-06-25 10:16:15 +00:00Commented Jun 25, 2011 at 10:16
- 4@Chris The whole point of a clean room operation is that people implementing the algorithm haven't seen the original source code at all. There's no such thing as a "one man clean room".Adam Lear– Adam Lear ♦2011-06-25 20:57:31 +00:00Commented Jun 25, 2011 at 20:57
| Show 1 more comment
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you