[isf-wifidog] errors in fresh install of cvs head

[Max Horváth]

> This is the problem.  I have no idea what you guys consider  
> acceptable for me to checkin, but have no other process for  
> acceptance than check-in.  I am sitting on about 6000 lines of  
> changes to wifidog-auth dealing with installation, language  
> selection, database abstraction, logging, stylesheets and code  
> locating, all of it integrated, tested, working, and maintained up- 
> to-date with mergings from cvs head.  I am lacking guidelines,  
> coding standards, a clear definition of what is core (database  
> etc), a roadmap, where the project is heading, etc etc, and am  
> simply at a loss at what to do or if my work is of any relevance.   
> Here, this most tame, most innocuous of changes, a three line fix I  
> thought was a slam dunk, is rolled back for a few weeks of peer  
> review.
>
> Fine.
>
> Perhaps one of you would enlighten me as to what process I should  
> follow so as to contribute productively to wifidog.  You know,  
> things like what is welcome and what is unwelcome, what is friendly  
> and what is not, who's working on what and who's toes I might  
> possibly, likely, unknowingly, step on.  I mean, I feel like I'm  
> walking through a mine field here.  A map would be nice.

You speak my words!

And regarding the coding standards. As I wrote in my other emails  
there where no coding standards for WiFiDog.

Till now nobody said anything regarding not to use the PEAR coding  
standards. So please use them as they are - in my opinion - the best  
coding standards for PHP.

Here's the link again: http://pear.php.net/manual/en/standards.php

> 1.  Event logging
>
> 2. Style sheet
>
> 3. language selection

Great! Please commit those changes!

Cheers, Max!