I'm creating a package for Laravel based on a code that uses the BSD license ( link ).
How exactly should I reference it? Should I keep the license file unchanged? Or maybe keep the original and add my license ...? How is this usually done?
I'm creating a package for Laravel based on a code that uses the BSD license ( link ).
How exactly should I reference it? Should I keep the license file unchanged? Or maybe keep the original and add my license ...? How is this usually done?
See what the original license says about it:
Redistribution and use in source and binary forms, with or without modification, the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and / or other materials provided with the distribution.
That is, you can redistribute, but should keep the above copyright and the disclaimer below those paragraphs, regardless of everything else.
The standard I see on some projects is to keep licenses for all the components they use, and add their own. I think it would be ideal to have your own license in addition to the license file of that project that you will use.
I took a look at MojoPortal, which is one of these project types. Each component it uses, even if binary (that is, not the source, but the compiled component), is in its own folder. And within that folder Mojo has a .txt file with the component license. These files are unchanged. Take a look at their general licensing page to get an idea of how to do it: they list each program that has a different license of Mojo. I think it's worth getting inspired by the writing you have there.