Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52209
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zikula.org designates 74.125.82.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4DC9081C.3020808@php.net>
References: <4DC729EE.9090600@sugarcrm.com> <4DC75FFF.40008@lerdorf.com>
 <4DC7A7F0.4000504@sugarcrm.com> <BANLkTinn3+MCrSd7BAJCU03FMkuRAeydvA@mail.gmail.com>
 <4DC819D0.5010008@lerdorf.com> <BANLkTimn9teRbkAYxGcGCz9djDsvPY+WfQ@mail.gmail.com>
 <3680807C-229A-4889-9181-8953303425EC@stefan-marr.de> <4DC9081C.3020808@php.net>
Date: Tue, 10 May 2011 16:07:12 +0545
Message-ID: <BANLkTikM9uGybV=6=Lq=nZS1M62PjZJMqg@mail.gmail.com>
To: Sebastian Bergmann <sebastian@php.net>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] 5.4 again
From: drak@zikula.org (Drak)

On 10 May 2011 15:25, Sebastian Bergmann <sebastian@php.net> wrote:
> Am 09.05.2011 21:33, schrieb Stefan Marr:
>> That is how open source works.
>
> =C2=A0Traits is a perfect example, indeed: you came to the list with a cl=
ear
> =C2=A0specification of the feature as well as arguments for why you think=
 the
> =C2=A0feature is useful. Moreover, you provided tests that reflected the
> =C2=A0specification and a patch that implemented the specification and
> =C2=A0satisfied 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