|Main||News||Doc||People||Events & timeline||pcb-rnd|
More dedicated users can join in scheduled, systematic testing. Such testing is split up into independent chunks that each can be done in an hour.
Even more dedicated users can join developing the documentation.
None of the above requires or assumes any programming skill.
Developer freedom promptly granted:
Coding style/indentation: there's an unified style in core and core plugins. If you work on those parts, try to stick to it. If you are working on a new plugin, it's still the preferred style but you can use a different style. However, the rule is that if someone else starts hacking that part too, he is allowed to convert the code to the unified format; but unified format can not be converted to anything else. So it's a one way process which long term grants unified style while not demotivates a plugin developer by forcing a style on him in the early, "when the bulk of the code is written" phase.