On 10 May 2011 15:25, Sebastian Bergmann <sebast...@php.net> wrote: > Am 09.05.2011 21:33, schrieb Stefan Marr: >> That is how open source works. > > Traits is a perfect example, indeed: you came to the list with a clear > specification of the feature as well as arguments for why you think the > feature is useful. Moreover, you provided tests that reflected the > specification and a patch that implemented the specification and > satisfied the tests.
That is the way to meet with the least resistance for sure, however, it's better to sound out the idea beforehand before you waste time on something that might get stone-walled. But, even a lone well thought-out specification may be picked apart by group scrutinisation. Overall in OSS, the problem is if you don't sound out an idea first, you might be wasting your time if it's stonewalled, but if you don't immediately provide a specification and patch, you get resistance because "it's yet another feature request" to an already overworked, and over burdened core development team. Contrasting, if you propose something that is generally liked by the core development team, you may not even have to write a patch for it to materialise. Getting something approved is therefore not so straightforward - you need some luck and who's reading the list at the time... Probably what is missing is some sort of crowd sourcing to really gauge opinion on a wider basis. Something like this http://ideas.joomla.org makes it very clear what is important to the wider community or not. Regards, Drak -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
