Date index for Aug 2002

Hi,

Dave Nuttall wrote:

> For example, I decided that to be sure I don't conflict with mainstream
> development, my tables/fields/nodes/modules have a somewhat more "formal"
> appearance, although it makes them much harder to work with.  

I have no formal naming convention yet, but I know we definitely need 
one, once more people start contributing modules, and modules will be 
downloadable from the website.

Also, we need some convention on 'minimal documentation', with some 
rules saying that a module should at least have a header in the 
module.inc file with the author etc.

For naming conventions, I'm thinking about the following:

- table names: should be prepended with the modulename, example:
             pizza_pizzas
- field names: no convention, as they need not be unique

Furthermore, everything in lowercase (for database compatibility)

> So for starters, all of my stuff goes in $home/modules_addons.
> As you've seen in the e-mail postings, my table/field names are like:
> 	Technology_Classes

What exactly does your module do, what is a Technology Class?

> (if anyone other than themselves) would be responsible for change
> management.

Regarding change management, we can use Bugzilla for user contributed 
modules. That way, we can keep track of bugs in modules, and they would 
automatically be assigned to the author of the module.

Maybe we can even provide access to our CVS server, but our CVS server 
is still not ready for public use. :(

> Thanks for all your help so far, Ivo.  I'm very pleased with the way stuff
> works once I understand a little bit about what there is lurking in the way
> of "tools/functions", etc.

Once you know what to do and where to look, Achievo's backend is quite 
powerful. Unfortunately the 'once you know' part is very difficult. I 
hope to solve that with the guides.

Greetings,
Ivo