Re: [Framework-Team] [Plone 4] PLIP #9249 Add TinyMCE as the default visual editor
On 7/30/09 2:00 AM, Martin Aspeli wrote: 2009/7/30 Erik Rose: 1) The current code base is located in the Collective. Since TinyMCE will be the default editor in Plone 4 should I move (copy) the code base to Plone SVN? -1. Why make it harder for people to contribute? By that argument, we'd have nothing in the Plone svn repository, and nothing covered by the contributor agreement. That's just silly. The contrib agreement and Foundation ownership are there for good reasons. Indeed: to protect code that makes up the Plone CMS application. I don't think a wrapper for a third party javascript editor is really that important that we require it be owned by the foundation. Wichert. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] [Plone 4] PLIP #9249 Add TinyMCE as the default visual editor
2009/7/30 Erik Rose : >> 1) The current code base is located in the Collective. Since TinyMCE will >> be >> the default editor in Plone 4 should I move (copy) the code base to Plone >> SVN? > > -1. Why make it harder for people to contribute? By that argument, we'd have nothing in the Plone svn repository, and nothing covered by the contributor agreement. That's just silly. The contrib agreement and Foundation ownership are there for good reasons. Martin ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] [Plone 4] PLIP #9249 Add TinyMCE as the default visual editor
1) The current code base is located in the Collective. Since TinyMCE will be the default editor in Plone 4 should I move (copy) the code base to Plone SVN? -1. Why make it harder for people to contribute? 2) I'm currently using the Products namespace for the package. Would it be better to switch to the plone(.app) namespace for Plone 4 (and keep the Products.TinyMCE for Plone 3)? -1. As Ross says, unless we have something to gain by changing it, let's not mess up people's imports, buildouts, etc. We can still change the license if we need to. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] [Plone 4] PLIP #9249 Add TinyMCE as the default visual editor
On 7/27/09 1:38 PM, Rob Gietema wrote: Hi, I'm currently working on TinyMCE for Plone 4 and would like some feedback on two issues: 1) The current code base is located in the Collective. Since TinyMCE will be the default editor in Plone 4 should I move (copy) the code base to Plone SVN? -0 I see no reason to move it. 2) I'm currently using the Products namespace for the package. Would it be better to switch to the plone(.app) namespace for Plone 4 (and keep the Products.TinyMCE for Plone 3)? -1 There is no benefit to moving, and this will make it harder to maintain Plone 3 and 4 trees in parallel. Wichert. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] [Plone 4] PLIP #9249 Add TinyMCE as the default visual editor
Hi, I'm currently working on TinyMCE for Plone 4 and would like some feedback on two issues: 1) The current code base is located in the Collective. Since TinyMCE will be the default editor in Plone 4 should I move (copy) the code base to Plone SVN? 2) I'm currently using the Products namespace for the package. Would it be better to switch to the plone(.app) namespace for Plone 4 (and keep the Products.TinyMCE for Plone 3)? Cheers, Rob Gietema Four Digits ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
