Re: implication of removing portal_skins

Just because we say we want to focus on one sector does not mean to abandon
the other.


On Wed, Jul 3, 2013 at 1:31 PM, Wichert Akkerman <[email protected]> wrote:

>
> On Jul 3, 2013, at 20:17, Nathan Van Gheem <[email protected]> wrote:
>
> > Hi all,
> >
> > Kim Nguyen is wanting to take up the effort of making sure we fill the
> functionality hole correctly when we remove the use of portal_skins in
> Plone 5.
> >
> > He, and many others, are concerned that doing quick edits on
> functionality in plone will become very difficult with the removal of
> portal_skins. When managing MANY sites, as he does, being able to do quick
> edits through the ZMI is very important to the power of Plone and his
> deployment.
>
> I think your first step is identifying who the target audience for Plone
> is. The last time we did such an exercise  we concluded that Plone is
> targeted towards larger more complex sites, and the
> many-small-sites-in-a-single-instance was not compatible with and should
> not hold anything back. I get the impression that the there are currently
> still too many opinions on what exactly Plone's target audience is, with
> the result that progress is very slow to impossible since too many people
> want/need too many different things. Making a clear decision will mean
> alienating part of the current audience, but I feel that is a necessary
> step that needs to be taken at some point.
>
> Wichert.
>
>
>

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers