Skip to main content
Software Engineering

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.

Required fields*

6
  • 2
    possible duplicate of Is a license header in source-files required? Commented Apr 28, 2016 at 14:17
  • 5
    The question that @gnat linked to addresses the Apache license. What license are you applying? For the Apache license, as mentioned in that question, the answer is "you should". For a different license, the answer may be "you must". Commented Apr 28, 2016 at 14:23
  • 2
    The advantage of doing so is that even if someone uses just one file from your library, they still include the licence, unless they make the effort to remove it. If the licence is in a separate file, they must make the effort to include the licence. The disadvantage is that every file now has an ugly lump of crap at the top that one must scroll past to get to the code. Your choice... Commented Apr 28, 2016 at 17:02
  • producingoss.com/en/license-quickstart.html Commented May 1, 2016 at 23:46
  • 9
    Possible duplicate of Do you have to include a license notice with every source file? Commented May 2, 2016 at 14:58