> There are those that might argue that, like it or not, PHP is in the > application server and/or CMS space. And there are justifications > for that argument. But at some point, Plone has to draw a > line in the sand and say: "That's our target." And we can't > engineer down to PHP and up to, say, Stellent at the same time. > > I humbly suggest that this list steer its signal-to-noise > ratio away from generic Plone discussions, towards NGOs and > how we can get them engaged. There's a lot of good stuff to > talk about there, such as ideas from Ploneability. I want to > make sure we don't scare off the original non-technical > audience that was looking for a place to organize and cooperate.
Paul, I don't think it's an issue of "Plone vs. PHP" which I agree is something of a dead-end. I think the issue that is of immediate relevance to small-to-medium NGOs (and others) is that it is currently quite difficult to find quality, reasonably priced, Plone hosting services that are approachable for new site administrators who need something less than a dedicated server. This is due to the non-LAMPy nature of Plone/Zope (and is a huge issue for Ruby On Rails, Django, Turbogears, etc., too!). I have personally seen this be barrier to nonprofits entering the Plone ecosystem, and more importantly to NGO-friendly consultants who are looking to get their feet wet with their first few projects. I suspect (but lack the technical expertise to be sure) that some sort of control panel packaging would help a lot. Maybe this is something to take up to the developers list. best, jon best, jon _______________________________________________ NGO mailing list [email protected] http://lists.plone.org/mailman/listinfo/ngo
