Re: hope to finish the coding standard

I think the jist of what is being suggested is that the rules stay, however there is a path where code that may be usefull to PEAR could be accepted on a basis that it would be 'pearified' in terms of tabs, {} etc. these are cosmetic changes, that could be applied by a formating script - I dont think anybody is really that passionate about this - if somebody tidied up code I'd written I'd be gratefull - normally my main focus is meeting a deadline, if some bits of the code are formated nicely its something that is pushed till after the deadline. in terms of Studlycaps that could be worked around by having underscore_wrappers extension classes applied for BC. the point is to attract more contributions, while keeping the standards in place - to this end it would be better if the PEAR community attempted to make this 'entry level' as easy as possible. (i dont really want to go into the bible bit) but, when you set down rules anywhere, good management always attempts to make it as easy as possible to comply with the rules that are set up... - Im sure there are lots of equivilants to that in the church..... In terms of you voluteers - your operation depends on them, yes fire them... - but if they keep comming back and help out on less 'essential areas' they're help is always appreciated........... The approach being taken is not to remove/break rules, but allow a process where by the rules can be applied in a gradual sense, with the premise that if Alexander didnt like the formating he was perfectly entitiled (if you considered the functionality of the code useful to you) to change it to standard formating as that was what the originaly contributor had agreed to by submitting their code as a possible PEAR module. regards alan Alexander Merz wrote:

It's late at night, hm, more early in the morning, so don't wonder... I'm working as a voluntary for a non-profit association, which organizes concerts and parties with newcomer bands. Every Spring since two years, we organize a festival over three days. During this days we had 80 voluntarily aids. Every of them had to subscribe a sheet of paper with strict rules ( no drugs and alcohol, to be punctually etc.). Some break this rules and we "fired" them. Why we do this? Yes they are spending time for your stuff and we fire them, are we ungratefully? Maybe yes! But this is necessarily. To organize this festival is not your profession, but we run in a lot of trouble, if we are not doing all professional. And to do anything professional, you need rules. Some of the your aids didn't like this rules (me too, i was resonsible for the beer bar). But we all know, breaking them, would lead in a big failure. Although we had worked three hard days, everybody would laught about us and get bad publicity. Ok, what has this to do PEAR? A lot :-) We all are voluntaries, we are working for PEAR without get payed. As a 'virtual community' we need rules too, we call this rules Coding Standard. Somebody, uninteressted who created this rules, i really believe he created this standards, because he used this standards already. And? Everybody has it own style, thats a fact, but in a bigger organisation like PEAR you need one unique. A unique standard has a big advantage for quality keeping and required for working together. Every company has it coding standard, do you ignore them, when you entering the company? No! Having a coding standard is a big sign of professionality. Yes, you are a voluntary, and when we request professional work, we should be able to pay for this. But, we can't pay, we earn no money for PEAR :-) But please think one minute, what are you in your company and what are you as a PEAR developer? Working in your company, means nobody outside of the company, see what you are doing. You could be a genius, but would nobody knows it. PEAR is already used all over the world, the name of the programmer stands in the programm files, is mentioned on the website, in the PEAR manual, if you are a genius everbody would know it. But only, when you write the PEAR stuff in a good quality or just 'professional'. :-) Ok, you said we can change the standard. Yes we can really do it, but when we do it once, we can do it again, and again. Uninteresting which standard you have, there is at least one, who wants a other rule changed. The existing rules are 2 years old, they didn't changed, the bible is more then 2000 years old and still unchanged. And the result? The christian church is not the biggest religion, but still one of the worlds religion. If somebody didn't want to follow the coding standards and didn't want to join PEAR, it is OK! You can go to another OpenSource project, PEAR is not the only PHP code library. PEAR has special rules, since 2 years more then 20 developer can live with this rules and produces a lot of stable and useful code. Cu, Alex