Re: Things to be done

[Micah Yoder <LYoder@cyberis.net>]

> > * Q & A - we need the system put in place that lets a user click yes or
> > no, this article has helped.  If they click they are presented with a page
> > that allows them to place further comments.  These comments go for
> > moderator review and the yes/no is logged.

I can work on that.  I guess we'd add a link to this from article.php3. 
As far as logging yes/no responses, how about logging it to a file
instead of to a DB?  Then a nightly cron job could tally up the totals
for the day and update the DB.  I *think* that would be more efficient
than a select/update pair each time.

> > * Article Ammendment - the system that allows users to suggest ammendments
> > to articles (for peculiar situations, etc).  These suggested ammendments
> > go for moderator review.  The Ammendment is then marked live or deleted by
> > the moderator.  Articles dislpay links to, or within the article approved
> > ammendments.

Seems like this could be done using mostly just E-mail.  Amendments are
fine in some cases, but we should also give the author of the article a
chance to just edit it into the original article.

That brings up another point:  Once someone authors an article, is it
always "theirs"?  Under what circumstances would we transfer ownership
to someone else?  Could someone other than the owner edit in additional
information as it becomes available?

> > * Article Maintenance - A system needs to be put in place that allows
> > moderators / admins to change the status of articles, update articles,
> > remove articles, modify the categories an article is a mamber of, etc.

I could help with that - but better not commit to the whole thing, it
could be big.

> > * Signup Forms - Micah has completed to some extent.  They need to be
> > modified to look like the layout I have designed on dev.  They need to be
> > examined and fully fleshed out.

Continuing to work on them... (signup and useredit)

> > * User Maintenance Forms - a system needs to be in place that allows each
> > user to modify there user "profile" and options, as well as allow admins
> > with proper security to modify any user status, etc.

Hmm... yeah, that should be added to useredit.

> > * User tracking - a generic system needs to be put in place that any page
> > can include to figure out what user is accessing the page, and set proper
> > variables based on that users options.

Is anyone working on this?  I've been using $PHP_AUTH_USER and selecting
the DB row.  Yes, it really should be standard and automated.

> > * Login Forms - forms need to be created to allow a user to login.

Not needed with HTTP authentication.  But if we want to track the number
of logins, what constitutes a login?  HTTP is stateless.  Is each page
request a login???

> > * Category/Application Maintenance - a system needs to be put in place
> > that allows proper security level people to maintain categories as in
> > add/remove, change hiearchy, change des's, etc.

I can do this if it's more important than the above stuff.