Technical merit only has value when it advances one or more goals, as in a vision statement. Technical merit without direction is efficient chaos.

On 24 Jun 2015 8:42 pm, Gareth Williams <gacrux@gmail.com> wrote:
On Thu, Jun 25, 2015 at 10:07 AM, Milly Bitcoin <milly@bitcoins.info>
wrote:
<snip>
> Also, the incentive for new
> developers to come in is that they will be paid by companies who want to
> influence the code and this should be considered
<snip>
> Now you are left with a broken, unwritten/unspoken process.

Your former statement is a great example of why "rough consensus and
running code" is superior to design by committee.
An argument should be assessed on its technical merit alone, not on
the number of people advancing it -- a process that would be open to
exactly the type of external manipulation you say you are concerned
about.
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev