On Tue, 18 Jan 2011, Jukka Ruohonen wrote:
On Tue, Jan 18, 2011 at 11:34:23AM +1100, Simon Burge wrote:
Why was this removed when there was an active discussion about removing
it where no concensus was reached? This sort of thing where commis
occur before a discussion is finished seems to
On Wed, Jan 19, 2011 at 10:31 AM, Alan Barrett a...@cequrux.com wrote:
On Tue, 18 Jan 2011, Jukka Ruohonen wrote:
On Tue, Jan 18, 2011 at 11:34:23AM +1100, Simon Burge wrote:
Why was this removed when there was an active discussion about removing
it where no concensus was reached? This sort
On Wed, Jan 19, 2011 at 11:31:27AM +0200, Alan Barrett wrote:
I don't care much about /usr/share/misc/operator, but I do care about
people making changes without discussion, or making changes with too
little discussion, or making changes that go against the consensus of
the discussion.
For
On Wed, Jan 19, 2011 at 11:13:15AM +0100, haad wrote:
Truly I haven't seen any discussion which had more than 10mails where
clear consensus was made. Thats not going to happen.
It is possible and it has happened. IMHO it clearly depends on the
quality of the original proposal/question.
In this
On Wed, Jan 19, 2011 at 12:20:40PM +0200, Jukka Ruohonen wrote:
Being naive as I am, I believe a software project can adopt healthier and
more productive software engineering practices.
If you want to change established procedures, change them first.
Do not explicitly violate them and hope for
On 01/19/2011 03:13, haad wrote:
On Wed, Jan 19, 2011 at 10:31 AM, Alan Barretta...@cequrux.com wrote:
On Tue, 18 Jan 2011, Jukka Ruohonen wrote:
On Tue, Jan 18, 2011 at 11:34:23AM +1100, Simon Burge wrote:
Why was this removed when there was an active discussion about removing
it where no
On Wed, Jan 19, 2011 at 11:13:15AM +0100, haad wrote:
We need some proper way how to evaluate changes, discussion about them
is clearly not good way. Because most of best developers are not
talking in those never ending mail threads. In practice most active
never ending mail writers
On Wed, Jan 19, 2011 at 08:16:41PM +, David Holland wrote:
The most important lesson to learn in software is that it's ok to be
wrong and that when you are wrong, the sooner someone notices the
better. We all make mistakes; we all make lots of mistakes, all the
time. (Writing this post was
