[TYPO3-dev] Confusing 'Naming error'

[Tapio Markula]

Hi

I have found that words 'naming error'
have creted much confusions and unnecessary fear.

People have regarded them as actual bugs.
IMO word *error* is misleading in this connections.
Error in applications means commonly real bug and
functionality problems.
People are in many times asked if it is safe to install
a plugin, which has naming errors.
They have feared functionality bugs.

Naming "error" is not at all error at the mean of
functionality. Word *error* is in this connection *too strong*.
Even *warning* is too strong because it might mean potential 
functionality problem.

If some issue doesn't follow the naming convention of Typo3,
the issue is worth on *note*.

For example.

"Note. Following class names don't follow the naming conventions of Typo3".

That is *just information* because naming convention difference is *not 
an actual error* but just a difference in the naming conventions.
People don't need to fear about possible functionality problems.
IMO the word 'note' gives the correct information.