Re: State of Website

I think somebody should make an executive decision on what to use... and
start using it.  If/when others want to contribute, they can learn to use
the tool that's already in place, and/or, as appropriate/convenient, use
other tools along side what already exists.

I would encourage the people who are doing active web development to decide
who will make this decision.  As I believe Tom Hull is still the chairperson
for the web group, it would make sense that it be him.  If he feels he's not
actively involved enough at the moment to force his view on others, then I'd
be happy for him to delegate that responsibility to Dale or Jeff or someone
else.

If nobody wants to make this sort of decision, I can do it myself, as
general chairperson of ACLUG.  I'd rather not have to make a decision on
something I'm not directly involved with, though :)

I think we'd be best to pick something and stick with it until completion.
Once the new site is up and running, if we want to start playing with other
tools on a test/developmental basis, by all means we can.  But until we make
a final decision, we'll never have a rough draft to work from anyway!

The lack of conversation since this original post suggests to me what I
already suspected: That everybody is either ignorant or apathetic of the web
tools.  If we're going to wait for a consensus, we'll be waiting forever.

So... as ACLUG chairperson, I'm asking for any final discussion before I
move and second a motion to delegate this decision to Tom or his chosen
deligate :)

-- Jonathan


----- Original Message -----
From: "Dale W Hodge" <[email protected]>
To: <[email protected]>
Sent: Friday, September 27, 2002 12:15 PM
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 - [email protected]
> Vice Chairman & Secretary - [email protected]
> Air Capital Linux User's Group  (ACLUG)
> ---
>
>
>
>
>
>
> ---
> Dale W Hodge - [email protected]
> Vice Chairman & Secretary - [email protected]
> Air Capital Linux User's Group  (ACLUG)
> ---
>
>
>
>