Forking over from the discussion from @jamesbradbury, @tremblap, and @groma in that thread, it would be worthwhile having a separate thread for this kind of discussion (particularly for when new users arrive).
The definition (found here):
Copyright {YEAR} {COPYRIGHT HOLDER}
Redistribution and use in source and binary forms, with or without modification, are permitted provided that 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.
Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS āAS ISā AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
So when distributing things, for example, the M4L device I linked in this thread, does that require the inclusion of a read-me file with the bundles (which can get confused with a generic read-me for the device itself), or does the āā¦in the documentation and/or other materials provided with the distributionā cover having them in the device as links/information and/or on the webpage where they can download it.
Iām mainly thinking of distributing single devices like this, where Iām unlikely to make a whole manual or comprehensive documentation for them, since they are fairly straightforward and self-contained (unlike some of my other patches). Particularly since there are no externals or dependencies to install, it would make the most sense as existing as a single .amxd
that people can download and use. So can I have the info embedded in the code and/or on the webpage where it can be downloaded from?