14

I have a project I've been working on which I would like to push into a new, public Github repository as open source. After searching on StackExchange for the right license to use I've settled on the BSD license.

My question is: now what? Do I just need to copy the BSD license text into a file called LICENSE in the root of my repository and call it good? Is that the general rule for how all open source licenses work? Or do I need to notify some other organization that I'm using this license so I can 'enforce' it if necessary?

Robert Harvey
  • 200,592
Chris Smith
  • 5,258

2 Answers2

7

It is sufficient to attach the licence file in your work. However it is normally preferable to add a small comment stating who owns the copyright and where to find the full licence text at the top of each source file.

You do not need to notify any organisation to enforce your licence if someone breaks the terms, although it will require you to take them to court.

Dipan Mehta
  • 10,612
david4dev
  • 638
4

If you have decided on a particular license suits your needs, then putting a License.txt file in a prominent place in the distro should be sufficient. Also, you should make sure that the github metadata for your project, Maven POM files and so on also declare the licensing in the appropriate way.

Or do I need to notify some other organization that I'm using this license so I can 'enforce' it if necessary?

It is not necessary. Enforcement of the license is entirely your responsibility. (Not that there is a lot to enforce .... with a BSD license.)

However, if you were prepared to use a GNU license and assign copyright to the FSF (and your project is worth protecting), they would take care of enforcement of the license.

Stephen C
  • 25,388
  • 6
  • 66
  • 89