{"action":"created","issue":{"url":"https://api.github.com/repos/sm00th/bitlbee-discord/issues/30","repository_url":"https://api.github.com/repos/sm00th/bitlbee-discord","labels_url":"https://api.github.com/repos/sm00th/bitlbee-discord/issues/30/labels{/name}","comments_url":"https://api.github.com/repos/sm00th/bitlbee-discord/issues/30/comments","events_url":"https://api.github.com/repos/sm00th/bitlbee-discord/issues/30/events","html_url":"https://github.com/sm00th/bitlbee-discord/issues/30","id":147296460,"number":30,"title":"Use of libwebsockets is GPL-incompatible","user":{"login":"EionRobb","id":1063865,"avatar_url":"https://avatars.githubusercontent.com/u/1063865?v=3","gravatar_id":"","url":"https://api.github.com/users/EionRobb","html_url":"https://github.com/EionRobb","followers_url":"https://api.github.com/users/EionRobb/followers","following_url":"https://api.github.com/users/EionRobb/following{/other_user}","gists_url":"https://api.github.com/users/EionRobb/gists{/gist_id}","starred_url":"https://api.github.com/users/EionRobb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/EionRobb/subscriptions","organizations_url":"https://api.github.com/users/EionRobb/orgs","repos_url":"https://api.github.com/users/EionRobb/repos","events_url":"https://api.github.com/users/EionRobb/events{/privacy}","received_events_url":"https://api.github.com/users/EionRobb/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-04-11T02:27:53Z","updated_at":"2016-04-13T18:51:15Z","closed_at":null,"body":"libwebsockets has an advertising clause in it that makes it GPL-incompatible. https://github.com/warmcat/libwebsockets/blob/master/LICENSE#L18-L23 is the part of the license in question, and http://www.gnu.org/licenses/gpl-faq.en.html#OrigBSD probably explains why it's incompatible.\r\n\r\nUsing an OpenSSL-compiled version of libwebsockets would be GPL-incompatible too, but the licensing terms are probably more bad than the use of OpenSSL."},"comment":{"url":"https://api.github.com/repos/sm00th/bitlbee-discord/issues/comments/209592665","html_url":"https://github.com/sm00th/bitlbee-discord/issues/30#issuecomment-209592665","issue_url":"https://api.github.com/repos/sm00th/bitlbee-discord/issues/30","id":209592665,"user":{"login":"dequis","id":94108,"avatar_url":"https://avatars.githubusercontent.com/u/94108?v=3","gravatar_id":"","url":"https://api.github.com/users/dequis","html_url":"https://github.com/dequis","followers_url":"https://api.github.com/users/dequis/followers","following_url":"https://api.github.com/users/dequis/following{/other_user}","gists_url":"https://api.github.com/users/dequis/gists{/gist_id}","starred_url":"https://api.github.com/users/dequis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dequis/subscriptions","organizations_url":"https://api.github.com/users/dequis/orgs","repos_url":"https://api.github.com/users/dequis/repos","events_url":"https://api.github.com/users/dequis/events{/privacy}","received_events_url":"https://api.github.com/users/dequis/received_events","type":"User","site_admin":false},"created_at":"2016-04-13T18:51:14Z","updated_at":"2016-04-13T18:51:14Z","body":"I emailed licensing@fsf.org about this, as suggested by the GPL FAQ. Their reply:\r\n\r\n> Hello and thank you for writing in.\r\n>\r\n>> Hi. The libwebsockets project uses a license that is based on LGPL 2.1\r\n>> with a few exceptions.\r\n>\r\n>> The full text is available here:\r\n>\r\n>> https://github.com/warmcat/libwebsockets/blob/master/LICENSE\r\n>\r\n>> The second exception reads:\r\n>\r\n>> >2) You do not have to provide a copy of the libwebsockets license with\r\n>> >programs that are linked to the libwebsockets library, nor do you have to\r\n>> >identify the libwebsockets license in your program or documentation as\r\n>> >required by section 6 of the LGPL.\r\n>> >\r\n>> >However, programs must still identify their use of libwebsockets. The\r\n>> >following example statement can be included in user documentation to\r\n>> >satisfy this requirement:\r\n>> >\r\n>> >\"[program] is based in part on the work of the libwebsockets  project\r\n>> >(https://libwebsockets.org)\"\r\n>\r\n>> Someone pointed out that this is equivalent to the BSD advertising\r\n>> clause. I think this is closer to the following part of the\r\n>> Independent JPEG Group license, which is included in the list of GPL\r\n>> compatible licenses in the GNU website.\r\n>\r\n>> >(2) If only executable code is distributed, then the accompanying\r\n>> >documentation must state that \"this software is based in part on the work of\r\n>> >the Independent JPEG Group\".\r\n>\r\n>> So, is it safe to use libwebsockets in a GPL project? Should they make\r\n>> any changes to the wording of the exception to make it unambiguous?\r\n>\r\n>> Thanks for your time.\r\n>\r\n> My reading of the text is that they have only provided exceptions to the\r\n> terms of the LGPL. The requirement to provide notice with each copy of\r\n> the work that the Library is used in it is already a part of the LGPL,\r\n> so they aren't adding a new requirement by merely spelling that out.\r\n>\r\n> So with the disclaimer that I am not a lawyer and cannot provide you\r\n> with a legal opinion or assurance, I hope this is of help."}}