[webdev] Re: State of Website

[<thull2@xxxxxxx>]

Thanks for the report. However, I'm out of town at the
moment -- until Oct. 6, more or less -- so I can't really
look into this until then, much less debate it. It seems,
though, that if you're still convinced that PostNuke is
the way to go, you should upgrade the demo site to the
new release and try to keep it upgraded.

FWIW, I've been working on a new website toolkit, based
on PHP/PostgreSQL. My emphasis is on building document
stores, but it will include multiuser support, community
collaboration tools, etc. One of the things that I did
was to take a real close look at PostNuke's data model,
which I found to be almost completely useless. Pretty
disappointing, as is this news of the project falling
apart.

> 
> From: "Dale W Hodge" <dwh@xxxxxxxxxxxxxxxx>
> Date: 2002/09/27 Fri PM 01:15:17 EDT
> To: <webdev@xxxxxxxxx>
> Subject: [webdev] State of Website
> 
> 
> Greetings!
> 
> I thought I should bring everyone up to date on what is happening with our
> website, or more correctly, why little has been done in the last couple 
> months.
> 
> In late July ~ early August, we made the decision to move to the PostNuke CMS
> system.  As a significant version upgrade was due in late August, I suggested
> waiting before deploying the new site.  Unfortunately, that release broke the
> majority of the 3rd party packages, several of which Aclug was planning to
> deploy.
> 
> A flame war broke out on the PostNuke development list, which ended in the
> resignation of the project leader, followed by resignations from 90% of the
> development team.  At this point, the future of PostNuke was in question.  The
> sole remaining founder of the PostNuke project attempted to rally the 
> remaining
> troops while fighting a battle of words with those who thought he was a major
> cause of the developer walkout.
> 
> Finally, cooler heads prevailed, and PostNuke started a re-organization 
> process
> which is still ongoing.  The previous broken release was recalled and
> re-released minus the changes that had broken all the 3rd party packages.  A
> couple of bug-fixes have been released, but full development has yet to 
> restart.
> I'm fairly confident that development will continue, but I'm unsure as to the
> timetable.
> 
> That leaves us with a few choices to make.  Do we hold off making any changes
> until things settle down, or do we make the move and develop on our own if
> necessary?  If we do the move now, do we stay with the P166 running RedHat, or
> do we find a faster box and while doing so move to something easier to secure
> and upgrade, like Debian?
> 
> Comments? Questions?
> 
> --dwh
> 
> ---
> Dale W Hodge - dwh@xxxxxxxxxxxxxxxx
> Vice Chairman & Secretary - info@xxxxxxxxx
> Air Capital Linux User's Group  (ACLUG)