Re: Re: [metabase-dev] MDB news

> Try to understand that you will never get people to agree on one style > that is good. It is unrealistic to ask everybody to switch to a > particular style, especially if they always used a single style for many > years consistently. If you switched to a style that you agreed that was > better, good for you. You can't just expect that will happen with > everybody, especially those that are using another style for a long time. That's right and i don't expect it. > I think the goal of attracting more capable people to contribute will > useful and rock solid components to PEAR is more important than > remaining unflexible and pushing only one style for adoption for > everybody because that simply will never happen and the whole PHP > community looses opportunities. > Keep up those demands on style will always keep out many capable > programmers from contributing. The truth is that there is not a single > way to certain things right. Yes, that is true. That applies to you too ;) (note the smiley i am just *kidding*) > Your opinion is not based on very humble principles. While it is a good > thing that more capable developers contribute to PEAR, you insist on > pushing unrealistic requirements as if having other developers to > contribute would be like you were doing them a favor. I was more thinking aloud then enumerating my principles. I don't insist on pushing requirements, I 'm just trying to understand why they are there. Based on my short experience it is good for a team to follow the same coding standards. We can argue that it is a not team which works on pear but that's not the point. Arnaud.