On 05/03/2012 07:23 PM, Stefano Zacchiroli wrote:
I agree that's a problem too and I share your feeling that it has been
particularly bad in recent discussions like the init system ones.
To keep on the topic of the init systems, we had Patrick Lauer,
a Gentoo developer who I believe knows quite
Thomas Goirand z...@debian.org writes:
But that's not the problem. The issue is that there's no
outcome, and that it's demotivating. If I read others that
what we want to work on isn't a good idea, I will simply
not work on that, and external contributors will run away.
I agree with this.
On Wed, May 09, 2012 at 04:58:53PM +0800, Thomas Goirand wrote:
We should have had some enthusiastic replies and constructive
comments on how we could make this happen, how we could improve
OpenRC to fit our needs. Instead, I have read posts criticizing
without knowing. If I was Patrick, I'd
Russ, I flagged your message as one to respond to, but not to debate any
particular point you raise, but rather to thank you for raising it at all,
despite it being potentially controversial. I'd also like to thank you for
tirelessly participating on the list, especially in recent times: I find
On May 09, Arto Jantunen vi...@debian.org wrote:
In addition to that it would be nice if everyone could agree to not work
against a certain init implementation (for example by refusing to
include the startup file for that init when someone else has written one
and submited it as a wishlist
On Jue 03 May 2012 08:23:29 Stefano Zacchiroli escribió:
[snip]
3) public, but contributors-only list
This has been implemented by other FOSS projects. A notable example is
Ubuntu who have a split between ubuntu-devel (project members only +
whitelisting) and ubuntu-devel-discuss (free for
On Friday, May 04, 2012 11:17:24 PM Lisandro Damián Nicanor Pérez Meyer wrote:
Not enough information to check signature validity. Show Details
On Jue 03 May 2012 08:23:29 Stefano Zacchiroli escribió:
[snip]
3) public, but contributors-only list
This has been implemented by
On Fri, May 04, 2012 at 10:44:17PM -0400, Scott Kitterman wrote:
It was implemented because at the time ubuntu-devel had a very low signal to
noise ratio and developers were getting frustrated (sound familiar). My
opinion is that it worked pretty well.
Most of the noise immediately shifted
On Mon, Apr 30, 2012 at 10:11:23AM -0700, Russ Allbery wrote:
Given recent experiences, I'm also coming around to Ian's position that
aggressive and confrontational contributions from people who don't
otherwise seem to be contributing to Debian are part of the problem and
are not useful, and
On Thu, May 03, 2012 at 01:23:29PM +0200, Stefano Zacchiroli wrote:
3) public, but contributors-only list
This has been implemented by other FOSS projects. A notable example is
Ubuntu who have a split between ubuntu-devel (project members only +
whitelisting) and ubuntu-devel-discuss (free
Stefano Zacchiroli z...@debian.org writes:
On Sun, Apr 29, 2012 at 07:18:54PM +0200, Marco d'Itri wrote:
Unrelated: you have just shown what poisons Debian and has been keeping
us behind innovation for the last years. Not the flamewars themselves,
most of us are grown ups and can handle
11 matches
Mail list logo
