Re[2]: [PEAR-DEV] Looking docs on a site. QA

Hello bertrand, bG> Could you resume your message ? Ask. I'll answer. bG> What's the will in it? The will to make PEAR better by making QA on a PEAR services first and only after that on releases. I wanted to contribute a package for PEAR and was looking into documents how to do it, but now I'm hesitating. bG> Explain what is karma ? bG> (I'm no QA) Karma is a natural mechanizm for access regulation. That means in real world if the people trust you, you have a karma to do the things and they will allow you to do so. Even if people don't know anything about you and if you making something what is generally usefull they will not hamper. In a world of bureacracy there are elections / votings / approval / disapproval where others decide for you what to do limiting your freedom. And so it is with CVS. I believe that developers can decide on their own who can make changes to the original code they've commited to the world. That doesn't concern PFC, since there are other rules. And I believe that the reasons QA should be created are - PFC QA at first, help and developers support as a secondary objective and not for limits and developers control. Maybe I exaggerate, but I think the main point is clear. To me QA will not be helpful in it's current RFC state as decribed on a page I mentioned earlier. -- TiP