Discuss mailing list

[Dustin <nfhostnet AT gmail.com>]

On Tue, Feb 21, 2012 at 9:12 AM, Niels Dettenbach <nd AT syndicat.com> wrote:

Am Dienstag, 21. Februar 2012, 08:44:01 schrieb Dustin:

> Plone is sloooow. Real slow.  I can't stress this enough.

This is nonsense expect you did a suboptimal setup.

 

I don't care enough about what CMS OpenNic uses to start a skills debate based on two peoples anecdotal experiences or to start a flame thread, so instead I'll say the following... 

The OpenNic page is sort of ugly and it should get a face lift.  But I don't see it needing to have tons of bells and whistles.  Not to be negative, but I can't imagine it ever being a heavily trafficked site and it's never going to be a place with lots of social interaction.  End users need to know what our mission is and how to change their DNS servers to a close by and reliable T2. T2 Ops need instructions on how to configure servers and how to mark them as down, etc.  We need links to register domains and some notes about how email and hosting on them can be challenging.   Finally, we need an email address or something that ISPs and other people can use to contact us to talk about joining or integrating into our alt-root.  

Past all of those simple things, that we pretty much already have, what does the site really need to do?  If you think lots of people will be creating content and sharing things with one another or sourcing RSS feeds, etc, I think you are sadly mistaken.  The couple times I used OpenDns or Googles Public DNS, it was a simple search for IP, copy paste, never go back to the site again ordeal.  Hell, if you even think the internal opennic CMS editors will be changing things very often, you are probably mistaken.  In my mind, the kind of info we provide is relatively static and serves a single purpose. The group sections on the wiki may be the exception to this.  

With that simplicity in mind, I think nearly any CMS/News Site/Blog would serve our needs.  Hell flat html could just about serve our needs.  But all of this is just my opinion, so if the organization or the web team has different ideas, by all means explore them.  Maybe a website needs/wants discussion would be more appropriate than a CMS debate?  I certainly don't think people judge the worth of a company or organization based on what CMS system or web language they use.  Web page layout and look maybe a little, but even that I think is small.  

My previous rants on Plone were meant more or less to say this--

Managing a plone environment is very different than managing a PHP MySQL environment.  If the sysadmin managing the web server hosting the site is used to that, cool.  If not, PHP or whatever language they prefer may be a better choice.  

Also keep in mind that if that person leaves the group finding someone with specialized skills to manage the Plone setup or the JSP setup or whatever more "obscure" system you choose will be harder than finding somebody that can sysadmin a LAMP stack, simply because its older and more widespread.  

Dustin