Re: TinyMCE integration, finishing touches

Hi,

I'm +1 with your proposal.

I'm not very aware of legal issues, but IMO put tiny module outside of
lenya svn sucks. Tiny is a very good value for Lenya.

About automatic download, there is not something that change with the
large Maven adoption ?
With Maven, many dependencies outside of Apache Licence can be download
with no confirmation entry on each licence style, AFAIK.

Anyway, automatic unzipping during build is a nice thing.

Rainer, that for this non tiny improvements ! :)

++

On 11/24/2010 07:22 AM, Rainer Schöpf wrote:
> On Tue, 23 Nov 2010 at 14:04 -0600, Richard Frovarp wrote:
> 
>> On 11/23/2010 01:09 PM, Rainer Schöpf wrote:
>> > With a few extra touches, the TinyMCE integration is ready to go.
>> > > > 1. Can we add an automatic download and unpack of TinyMCE to the
> build
>> > process, so that people need only uncomment a line in
>> > local.build.properties. As an additional goody, another build property
>> > could be used to select the language packs to download.
>> > No, I don't believe that is possible. I think that would run afoul
> of license
>> issues.
> 
> Maybe, but see this:
> 
>  http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200508.mbox/%[email protected]%3E
> 
> 
> and possibly a lot of other messages in this thread. So, as I understand
> it, this is a policy issue rather than a legal issue.
> 
> As an aside, I found this statement by one of the TinyMCE developers:
> 
>  http://tinymce.moxiecode.com/punbb/viewtopic.php?id=18700
> 
> I'm aware that it doesn't help us, but maybe we could work something out
> with them?
> 
>> Plus we'd have to have some way of keeping up on the proper version
>> numbers, which would be a little difficult.
> 
> True.
> 
>> > 2. TinyMCE should be included in the default publication, the menu
> entry
>> > being disabled if the editor is not installed.
>> > > > Comments?
>> > > > We need to do license checks after it works. We can't distribute
> TinyMCE due
>> to license. Patches aren't allowed either. I don't know how what we have
>> falls in the spectrum.
> 
> Sorry, misunderstanding: I meant to include the TinyMCE _module_ in the
> default distribution. The only difference to now would be the menu entry
> in the Edit menu. No LGPL code being distributed.
> 
>> http://www.apache.org/licenses/GPL-compatibility.html
>> > I honestly think our best bet would be to take the TinyMCE module,
> remove it
>> from our code base and host it somewhere like Google Code that does allow
>> GPL. Then you could include TinyMCE with it. If we need to do this now, I
>> don't know.
> 
> TinyMCE is LGPL 2.1, not GPL.
> I fear that this would seriously reduce the number of people using it.
> 
> 
> Anyway, here is a modified proposal:
> 
> 1. Add an automatic unpack step for Tinymce to the build prcess. I.e. if
> the tinymce.zip files are there, it unpacks them during build.
> 
> 2. Add the TinyMCE module to the default distribution, with the TinyMCE
> menu entry grayed out, if the editor itself is not installed.
> 
>  Rainer
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]