I agree that stable, user friendly are more important than features.
The RPI is for education and so flakey basic services is going to switch a lot off.
I was not arguing against user friendly etc though, rather for better quality.
No-one is forcing Unity. I am on LTS, quite happy with that. Hell of a lot cheaper than Windows Server anyway!
The point I was making is that documentation styles should evolve and that its right for the development teams behind them to determine that evolution.
We help and speed that process if we call crap crap, or refuse to use of course.
I would value a trained, experienced and motivated (in reverse order!) team who will take charge of quality over a standard any day.
There's another thread discussing an app store which reached the dilemma; who will take responsibility for quality?
So you end up with geniuses who develop free applications supported by those who write Wordpress guides. Its not great but no-ones is paying for more.
The OP suggested a coding standard:
I would hold this 'standard' above any other, it is educational and engages in a humerus way.
A standard standard would just become another documentation lag, you cannot improve until the standard is updated.
Replace 'standard' with 'best practice guide' then I am with the programme!
BTW There are plenty of 'good' standards which may be used as guidance. You don't need a new one. If you want a development standard then download 12207. Once you start your project you then start thinking, do I need to apply this section to this problem?
You could liken it to the quote; planning is everything, plans are useless.
So I agree, quality must improve. Standards are not the way though.