Path: csiph.com!news.mixmin.net!weretis.net!feeder1.news.weretis.net!news.solani.org!.POSTED!not-for-mail From: Asen Bozhilov Newsgroups: comp.lang.javascript Subject: Re: [FAQ] Repository on GitHub, license, review cycle Date: Wed, 16 Dec 2015 22:35:43 +0200 Organization: solani.org Lines: 75 Message-ID: References: <1578386.5B2p4gcX6K@PointedEars.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: solani.org 1450298143 19237 eJwFwQkBwDAIA0BL0JIw5PAM/xJ6h0tluxE0LNZHZrNGyegflVMWAcKlv1WgO/OEzdx2yHkz5xGT (16 Dec 2015 20:35:43 GMT) X-Complaints-To: abuse@news.solani.org NNTP-Posting-Date: Wed, 16 Dec 2015 20:35:43 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 X-User-ID: eJwNysERBDEIA7CW4DAGl5Mhof8S9vRWBp1TYBK5uS6eGcbzLalePrurqYVGEwf/+uMire3CXqsBusqbuCc+TP8UoQ== In-Reply-To: <1578386.5B2p4gcX6K@PointedEars.de> Cancel-Lock: sha1:GhzH5YlRj19dB8KBZ5g/Uc+MBHQ= X-NNTP-Posting-Host: eJwFwYEBACAEBMCV4ns0TsT+I3RHmFj5NtrmcBT9roNdVafi6EsYE0JvIj1uU51rSSsi4gMjOhCq Xref: csiph.com comp.lang.javascript:29019 Thomas 'PointedEars' Lahn wrote: > Hello all, > > some of you might have noticed already that, as I indicated recently [0], > this weekend I have migrated the code repository for the “FAQ for > comp.lang.javascript” (“the FAQ”) from SVN to Git, and published it on > GitHub: > > Great news! I have waited for years someone starts maintaining the FAQ. Hope with the community efforts FAQ to be improved and keep in good shape as it is. If I remember correct, the maintaining of FAQ was dropped in the time when ES5 was released. Today there is ES2015 a.k.a. ES6 is officially approved and I think there would be many new frequently asked questions. By today, the most common question is "How can I use ES6 in ES5 environment?". Babel transpiler fills that gap, and if you browse npm packages you can notice how many packages are written in ES6. > It is my intention (as explained in the README there), in addition to > considering FAQ contributions via the already known channels [1], to review > Pull Requests for the “dev” branch of that repository (as it is customary, > “master” is the name of the stable branch on which the live version is > based). I will continue to post here a summary of the suggestions for the > FAQ that I have and receive from you via those channels, and other *direct* > channels (like social media), for public discussion. The contributions process seems pretty straightforward, but I think before PR, it should be open for discussion either via a github issue or thread here. My predictions, since FAQ is available in github the common approach would be using github's bug tracking system. This would lead to fragmented discussion, so you have to consider how to prevent it. > ... via Markdown ... As we have discussed in twitter, as long FAQ is in github Markdown format would be pretty convenience and straightforward for github users, but of course every new entry and changes should be added after discussion here or in github, could be discussed in both places. > To make contributions even easier, I intend to publish the FAQ content under > the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International > (CC BY-NC-SA 4.0) License. AIUI, this change would only codify the existing > informal agreement, and it had some support [3]. > > Why that license? > > - Although it contains code examples, the FAQ content is more like a book > than a piece of software; so a software license is not the appropriate > type of license for it. Creative Commons fill that gap by providing > free *content* licenses. You are correct, but there are many examples of softwares which include their own FAQ and the FAQ is not separately licensed under other license than the main project. I think some entries of c.l.js FAQ could be included in some open source projects licensed under MIT, BSD and LGPL. Those licensed are pretty relaxed and the code can be used for commercial purposes, so if they use c.l.js FAQ entries, they have to distribute their FAQ or doc separately under (CC BY-NC-SA 4.0). Please reply with your thoughts about the above statement.