rubyonrailsin

great news and thanks for the effort!

i think the kramdown branch in my fork is ready to merge. let me know
if there are any issues and i'll clear them up shortly.

http://github.com/johnmuhl/radiant/tree/kramdown

On Mon, Mar 15, 2010 at 2:43 PM, Jim Gay <jim@saturnflyer.com> wrote:
> On Feb 9, 2010, at 11:20 PM, M. Scott Ford wrote:
>
>>
>>>> To summarize, I now retract my assertion that having radiant depend on kramdown would be permitted. We could only do that if we make radiant licensed under the > terms of GPLv3. If I have overlooked something, or made a poor logical leap, then please point it out.
>>>
>>> radiant has been distributed with bluecloth 1.0.0 for years now which
>>> as i understand it is GPLv2.
>>> http://github.com/radiant/radiant/blob/master/vendor/extensions/markdown_filter/vendor/bluecloth/LICENSE
>>
>> I did not realize that. In order to be compliant with the BlueCloth 1.x license, any codebase that depends on it also has to be licensed under the GPL. This means that radiant's license is not compliant.
>>
>>> what about the bluecloth 2 option? it appears to BSD licensed.
>>> http://deveiate.org/projects/BlueCloth/browser/LICENSE
>>
>> The BSD license is very similar is spirit to the MIT license. The BSD license does not have a provision that restricts derivative works. It basically states that you can do whatever you want with the, but you can't sue the authors or use the fact that it was written by the authors as a means of promotion.
>
> As far as I understand, we are in the clear with this. I contacted the Free Software Foundation and got this reply back:
>
> Begin forwarded message:
>
>> Jim,
>>
>> I'm assuming that the "MIT license" you're talking about is the one we
>> call the Expat license, at <http://www.jclark.com/xml/copying.txt>.  If
>> that's the case, then yes, you can release a program that uses a
>> GPL-covered library under this license.  The Expat license is
>> GPL-compatible (http://www.fsf.org/licensing/licenses/#Expat), and our
>> FAQ explains that when you distribute a program that uses a GPLed
>> library, you may do so using a GPL-compatible license
>> (http://www.fsf.org/licensing/licenses/gpl-faq.html/#IfLibraryIsGPL).
>>
>> Please note that distribution of the combined program will still be
>> subject to the GPL's terms.  In other words, people won't be able to
>> distribute a proprietary version of the combined program, even though
>> the Expat license allows it, because the GPL would prohibit it.
>> However, people who do not combine your program with any GPL-covered
>> libraries may be able to use all of the permissions granted by the Expat
>> license.
>>
>> Best regards,
>>
>> --
>> Brett Smith
>> Licensing Compliance Engineer, Free Software Foundation
>
> --
> Radiant CMS Dev Mailing List
> Post:        radiantcms-dev@googlegroups.com
> Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
> Group Site:  http://groups.google.com/group/radiantcms-dev/

--
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/