From: Milly Bitcoin <milly@bitcoins•info>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] A summary list of all concerns related to rising the block size
Date: Wed, 12 Aug 2015 13:08:43 -0400 [thread overview]
Message-ID: <55CB7D9B.2060203@bitcoins.info> (raw)
In-Reply-To: <2133828.JttggH90JM@pluto>
> I have never heard of "develop-by-concerns"? Is that similar to
> fire fighting management?
> To that I have this reply;
> http://www.aleanjourney.com/2009/07/stop-fighting-fires.html
A set of goals is needed and then you develop road maps. At that point
you can propose specific changes that fit within a road map.
Russ
next prev parent reply other threads:[~2015-08-12 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 10:28 Jorge Timón
2015-08-12 16:41 ` Thomas Zander
2015-08-12 17:08 ` Milly Bitcoin [this message]
2015-08-14 22:01 ` Jorge Timón
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55CB7D9B.2060203@bitcoins.info \
--to=milly@bitcoins$(echo .)info \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox