General discussion

Update: an installer finally got into Drupal 5

Over the last few weeks, I have been attempting to simplify the deeper intricacies of installing, and maintaining a drupal system, while allowing for a more centralized/controlled method of providing database scripts for contributed modules.

A good example of the intended result would be quotes and menus in the contrib modules. The modules contain the neccesary SQL to create, and update the tables required for operaton/installation of the module directly within the .module code. This makes them incredibly userfriendly, and simple for even the greenest newbie to install a contributed module without needing to know anything about MySQL, PostgreSQL an ssh connection and yes , even phpmyadmin.

I wrote up a document that talks about Drupal Permissions Control. A lot of people have been requesting it, and I'm beginning some implementation, but I thought that I'd write out exactly what I thought (based on experience, on reading other forum posts, etc.) permissions was. It's been called "access control", "security model", and so forth, but I lumped it under "permissions" in this document.

What I need is someone to help me review it - to get some comments and some feedback to be sure that this is exactly what people want to see. If we do it well, then we won't have to go back and fix it when people complain. I know that we're not trying to IMPRESS anyone, nor do we have any kind of deadline, but I personally think it's nice to know what we're doing before we go do it. So please take a look here and leave a comment as to what you think.