The development environment is easy to set up: just run the installer. If you want to run it in a production environment, there's a few hoops to jump through. Zope's web server was not intended to directly face the Internet (read the Plone docs), it needs to be behind either an HTTP load balancer or HTTP reverse proxy. So you need to set up the URL rewriting rules and reverse proxy config in Apache to handle that. Also there's some configuration work with VirtualHostMonster if you are using Plone as part of a virtual host. If you're going to have mutiple Plone/Zope instances share the load, then you need to grok Zope Enterprise Objects and its configuration.

Wow, what a blast from the past! I got on the Plone train back in the 0.9.x version days and continued to build sites on it until 2006. It had it's peak between '04 - '06. I moved on to Rails and LAMP because clients wanted something that ran on a low-end shared hosting account or low-end Xen virtual machine. I'm surprised it's still around and at version 4. I still think it's better in some ways than Drupal but it's a pain in the ass to set up a proper hosting environment for it.

So far as the name Plone, it was derived from the electronica band Plone as the developers were fans of the band.

rant warning: This a very clear illustration why no one should ever "mod" their Amateur mobile or HT to transmit out of band. If that modded rig gets out of your hands into some punk-ass kid, this is exactly what happens.

I don't think the problem with encrypted radios is an issue of "range" or coverage". Granted it's expensive to put up a few more repeaters but if I can do it by purchasing a bunch of Moto radios from a hamfester, it's not that big of a problem for the CTA. P25 is a fairly open codec and the equipment isn't that expensive. The bottom line is that the CTA failed to be proactive by choosing not to secure their land mobile communications.