[webdev] Re: Next steps

["Dale W Hodge" <dwh@xxxxxxxxxxxxxxxx>]

> -----Original Message-----
> From: webdev-bounce@xxxxxxxxx [mailto:webdev-bounce@xxxxxxxxx]On Behalf
> Of Tom Hull


> I think the big
> thing to do there is to come up with a plan for organizing
> content, and secondly define a set of roles for updating the
> website. Probably the best way to do that would be to get
> a meeting together and do some brainstorming.

Our next Monthly Aclug meeting on July 8 is currently scheduled to cover
organizational 'stuff', so we could have some time to ask our members for
input on what they want to see on the site. Otherwise, we need to schedule a
meeting.

> One bug I found (haven't put into bugzilla but should) is
> that the procedure that rounds up all of the static pages
> doesn't follow symlinks, which is a problem given the way
> the website files have been broken into openacs/aclug chunks
> and stitched together using a symlink. I'm not sure whether
> to just fix the tcl code, or rethink the way the website is
> put together.

To me, that's a big bug, at least in the way I currently do my sites.
Mostly, that's because I want some of the same content available across
multiple virtual sites.

> I'm not sure where we stand on backups;
> the postgresql db is being dumped, bug we also need cvs and
> bugzilla and probably /usr/local/aolserver and some other
> odds and ends

Hum... I could probably figure out a script to tar them up and run it as a
cron job. What files/directories need to be included, and where do you want
them dumped?

> also log rotation is a potential problem
> with aolserver.

How does RedHat handle log rotation?

> and setting up ssl.

It shouldn't be too hard to set up ssl. Just need to generate a key and set
the options in the config file, IIRC.

> The main page needs a bugzilla link in the developers
> section, and the events notices connected. We need a
> privacy statement, a copyright statement, a mail list
> page. Some modules are probably easy to set up and
> useful -- class ad is one that comes to mind.

Some of this we can pull from the current site, the rest we'll have to sit
down and draft ourselves.

> We need a link from the old website to the new one. (I've
> written John Goerzen about this, and suggested some wording
> if he'd be kind enough to do it.) We need the activities and
> presentations people to start using the events system.

I don't know if John has done this. If I can find the time, I'll sit down
and figure out how to do it myself.  It isn't hard, it just tends to be a
bit obscure.

> I'd like to see a spec for the RSS news feed thing -- this
> was on Dale's request list and is something he's been looking
> into. I'm more interested in how it would be used than just
> how to do it.

The "how" is that it would allow us to be a portal, perhaps people's home
page, somewhere they come first to learn about what is going on in the Linux
world. While the links do lead off site, we get the opportunity to show them
what we have to offer first.

--dwh

---
Dale W Hodge - dwh@xxxxxxxxxxxxxxxx
Vice Chairman & Secretary - info@xxxxxxxxx
Air Capital Linux User's Group  (ACLUG)
---