You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Rainer Schöpf <ra...@gmx.net> on 2010/11/23 20:09:56 UTC
TinyMCE integration, finishing touches
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.
2. TinyMCE should be included in the default publication, the menu entry being
disabled if the editor is not installed.
Comments?
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: TinyMCE integration, finishing touches
Posted by Richard Frovarp <rf...@apache.org>.
On 11/24/2010 12:22 AM, Rainer Schöpf wrote:
>
> Maybe, but see this:
>
> http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200508.mbox/%3Cc5e63255050802170438fce46e@mail.gmail.com%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.
But we still have to follow the policies.
>
> TinyMCE is LGPL 2.1, not GPL.
LGPL is still on the category X list. However, what you outline does
seem to follow the policy, so your proposed action should be good.
>
>
> 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.
So long as this can be done without system calls.
>
> 2. Add the TinyMCE module to the default distribution, with the TinyMCE
> menu entry grayed out, if the editor itself is not installed.
>
Sounds good.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: TinyMCE integration, finishing touches
Posted by florent andré <fl...@4sengines.com>.
Ok, thanks for this lights !
On 11/24/2010 05:16 PM, Richard Frovarp wrote:
> On 11/24/2010 04:04 AM, florent andré wrote:
>> 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.
>>
>
> It depends. You still can't have dependencies with incompatible
> licenses. That's where you get into trouble with something like
> Hibernate. You need Hibernate for the project to work, and it probably
> won't work without it.
>
> For something line TinyMCE, it's an optional dependency. You don't need
> TinyMCE to run Lenya, or even edit documents. When it's an optional,
> alternative, or value added dependency the rules are more permissive.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: TinyMCE integration, finishing touches
Posted by Richard Frovarp <rf...@apache.org>.
On 11/24/2010 04:04 AM, florent andré wrote:
> 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.
>
It depends. You still can't have dependencies with incompatible
licenses. That's where you get into trouble with something like
Hibernate. You need Hibernate for the project to work, and it probably
won't work without it.
For something line TinyMCE, it's an optional dependency. You don't need
TinyMCE to run Lenya, or even edit documents. When it's an optional,
alternative, or value added dependency the rules are more permissive.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: TinyMCE integration, finishing touches
Posted by florent andré <fl...@4sengines.com>.
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/%3Cc5e63255050802170438fce46e@mail.gmail.com%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: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: TinyMCE integration, finishing touches
Posted by Andreas Hartmann <an...@apache.org>.
Am 24.11.10 07:22, schrieb Rainer Schöpf:
> 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.
+1
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: TinyMCE integration, finishing touches
Posted by ru...@uniklinik-freiburg.de.
Rainer Schöpf <ra...@gmx.net> schrieb am 24.11.2010 07:22:58:
> 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
>
+1
Rudolf
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: TinyMCE integration, finishing touches
Posted by Rainer Schöpf <ra...@gmx.net>.
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/%3Cc5e63255050802170438fce46e@mail.gmail.com%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
Re: TinyMCE integration, finishing touches
Posted by Richard Frovarp <rf...@apache.org>.
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. Plus we'd have to have some way of keeping up on the
proper version numbers, which would be a little difficult.
>
> 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.
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.
WDOT?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org