[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Sun, 30 Dec 2012 17:06:05 +0000 paul sutton <zleap@xxxxxxxxx> wrote: > On 30/12/12 17:01, Gordon Henderson wrote: > > On Mon, 31 Dec 2012, Kai Hendry wrote: > > > >> I'm happy to put it into a github account, much like I've done with > >> http://www.prazefarm.co.uk/ and make it a static site. Doesn't sound like a static site is what members want currently, or ever did as I remember things. Don't forget, github itself is 100% proprietary sofware with a habit of removing services without any notice. (e.g. the downloads service was "replaced" and the "notice" posted *after* the links had been deleted, breaking several dozen Debian packages in the process.) > 1. sign up pagfe here http://mailman.dcglug.org.uk/listinfo/list will > need to be maintaned > 2. do we want to give EVERYONE access to the site, or would people > prefer to be able to e-mail someone with content and have a few of us > upload content etc That's a question which only the server admins can answer - my answer as the one paying the bill for this current server is no. Restricted access is the only way to do it. Spammers just have too many resources, are too persistent and are too fond of delivering malware as well as spam. There is enough to do avoiding exploits in the front-end code itself without allowing random user accounts in a CMS. Simon does most/all of the current work for the dcglug server. IIRC the default answer will be along the lines that the server admins have to do the work of cleaning up after such attacks and therefore set the security policy - restricted access, known individuals only typically. > 3. How does this affect the actual mailing lisdt Not compatible with any CMS, hosted separately, maintained by Alex. Quite a different maintenance beast than drupal, wordpress or any other CMS. > 4. Lug archive Not directly compatible with any CMS - it has to be "fitted in" manually, including custom server setup at each end requiring real root access. It's no easier to do that with any hosting solution as it would be to adapt the current Drupal setup. Note: I'm not proposing to do that work this time. I do *not* have free time to do it and certainly not before 1st Jan 13. From doing it last time, I'd estimate a couple of days of concerted work by someone with a reasonable expertise in CSS. Cross-browser CSS hasn't got any easier with the advances in CMS eye candy. Answering the original email: > 3. Would it be technically possible to update the current site with the > one I have here, so we can start 2013 with a fresh new look. No. Drupal is one thing, there's no way I'm going to support anything wordpress on the current server. Despite Gordon's comments, I've seen wordpress from the inside and whilst Drupal isn't exactly pretty, Wordpress is a gargoyle covered in gangrenous warts by comparison. Changing the CSS of the current site via a Drupal theme involves creating a suitable CSS setup for the archive which somehow fits in *without* changing *anything* in the HTML of the current millions of HTML files of the archive itself. Either that or sacrifice the archive. What is the objective? What is the reason for considering a change? Websites don't need to change on any arbitrary time frame. Don't underestimate the amount of work involved here. There is a lot more to do than just playing with a CMS theme. I've done two re-brandings of the dcglug website already. I'd need a very good reason to consider another. -- Neil Williams <linux@xxxxxxxxxxxxxx>
Attachment:
pgpa3rkrevJO2.pgp
Description: PGP signature
-- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq