Authorship¶

The asker must be an author or maintainer, and an emotional owner of the code.
- If the author is not an author or maintainer; the author is unlikely to be able to legally license the code under the current user contributions license.
  
  As a site we don’t want to encourage a situation where anyone will seek legal action against users of the site.
- If the author is not an emotional owner; the advice we give can be dismissed as someone else’s mistake.
  
  As such the site would not be creating the learning environment we want.
- I found some code on the internet; please review the code.
The author should rewrite the code from scratch. Changing some variable names and reorganizing the code is not allowed.
1. What topics can I ask about here?
  
  Am I an author or maintainer of the code?
The asker must license the code under Code Review’s current user contributions license.
By posting on Code Review you are licensing all contributions under the user contributions license.

If the author don’t post the code in the question then we as a site can’t review the code.
1. Code Review’s Terms of Service under “Subscriber Content”
2. User contributions license
The asker must understand how the code works.
1. Answer to Why is only my own written code on-topic? by rolfl © CC BY-SA 4.0
  
  In real life, a code review happens as a routine part of the development cycle. It happens after the code is designed, developed, and tested and in the process of being committed to the code base in preparation for release. The person doing the review sits with the person who wrote the code, and they go through it together. If the reviewer has questions like “why are you doing it this way?” then the developer is right there to give the appropriate answer. In Code Review, as an online resource, in a Q&A format, the expectation is that the text describing the code should explain why the code does things the way it does.
The asker must be able to explain how the code works.

Extra¶