So we've already been operating with slightly modified coding guidelines but we should formalise those. I have created a patch of the coding-guidelines.html file which you can find here. The changes are:

Looks pretty good. But what about the class naming proposal, which also includes things like "there should only be one class per file"?

+ <p>If an array is defined with each element on its own line, you still have to modify the previous line to add a comma when appending a new element. PHP allows for trailing (useless) commas in array definitions. These should always be used so each element including the comma can be appended with a single line</p>

eviL3 wrote:Looks pretty good. But what about the class naming proposal, which also includes things like "there should only be one class per file"?

Added that. Including the singular/plural thing.

eviL3 wrote:

+ <p>If an array is defined with each element on its own line, you still have to modify the previous line to add a comma when appending a new element. PHP allows for trailing (useless) commas in array definitions. These should always be used so each element including the comma can be appended with a single line</p>

You might want to add a trailing full stop there for consistency.

Trailing full stops are a syntax error, so I don't quite see the point?