I'll certainly do that if need arises, though I think it would be better if the release actually had them in there from the start. But if the lead developer is set against it, I'm not going to keep whining about it.
Nevertheless, I would strongly recommend *at least* putting licensing information on the JavaScript files, even if only using the one-liner approach. Since the JavaScript will usually be served through a Web server, it will be impossible for Web users to tell that it is freely licensed code. Code with unclear licensing is no better than proprietary code for practical purposes. On 03/11/2017 02:23 AM, Jakob Eriksson wrote: > > What I do when incorporating a source file which has no license or > copyright information at the top: > > I just add it... it takes a couple of minutes, tops and then I'm done. > > > > -- https://qlfiles.net -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
