From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FRrWD-0002sx-KC for garchives@archives.gentoo.org; Fri, 07 Apr 2006 14:00:58 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.5) with SMTP id k37E0Bv1023931; Fri, 7 Apr 2006 14:00:11 GMT Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by robin.gentoo.org (8.13.6/8.13.5) with ESMTP id k37DvuYk028896 for ; Fri, 7 Apr 2006 13:57:56 GMT Received: from [172.23.170.136] (helo=anti-virus01-07) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1FRrTI-0001WB-5E for gentoo-dev@lists.gentoo.org; Fri, 07 Apr 2006 14:57:56 +0100 Received: from [82.32.206.2] (helo=[192.168.1.210]) by asmtp-out4.blueyonder.co.uk with esmtp (Exim 4.52) id 1FRrTH-0000dI-IT for gentoo-dev@lists.gentoo.org; Fri, 07 Apr 2006 14:57:55 +0100 Subject: Re: [gentoo-dev] Re: Improving Gentoo User Relations From: Christel Dahlskjaer To: gentoo-dev@lists.gentoo.org In-Reply-To: <20060407144328.14c49c80@snowdrop.home> References: <1144377010.5485.82.camel@gaspode> <9445dc2b0604070151t68e184fdo3601938bb52d0871@mail.gmail.com> <20060407100728.1a5a01d0@snowdrop.home> <1144419575.20252.24.camel@gaspode> <20060407144328.14c49c80@snowdrop.home> Content-Type: text/plain Date: Fri, 07 Apr 2006 15:57:44 +0100 Message-Id: <1144421864.20252.63.camel@gaspode> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 Content-Transfer-Encoding: 7bit X-Archives-Salt: 68682d80-9189-4015-a197-3c703402b750 X-Archives-Hash: c3cf2e0353c168df3ff4a2b4e302471e On Fri, 2006-04-07 at 14:43 +0100, Ciaran McCreesh wrote: > On Fri, 07 Apr 2006 15:19:35 +0100 Christel Dahlskjaer > wrote: > | So, from a developer pov Ciaran; if we could come up with some way of > | keeping up to date with what you guys do (without eating up any of > | your time or getting in your way) and then keep the masses informed, > | would that be more attractive? Obviously making sure that information > | is kept to a not exactly bare minimum, but presented in such a way > | that it doesn't in any way halt progress or potential change of > | direction? > > If it's information on things that are fine being public but aren't > simply because of lack of time to write them up, then that would be > great. If it's things that're being kept quiet purposefully, however, > then the last thing we want is to start telling people things. Yes, I agree with that entirely. If things are being kept quiet for a reason we will have no wish to attempt to push for these to be made public before the decision to do so is reached by the development teams in question. > > | > Hence why some of us don't announce non-trivial projects on public > | > mailing lists, and instead keep any discussion on -core and sekrit > | > IRC channels. That's how what's now known as eselect was developed, > | > and it turned out far nicer than the XML-laden aborted gentoo-config > | > project precisely because of the lack of end user 'input'. > | > | In more of a informative 'these are the exciting things we're doing' > | sort of way rather than a 'tell us why you disagree' sort of way > | maybe. > > See, that doesn't work. There's this strange notion that because we're > open source, users somehow have a right to a) see the code, b) make > suggestions, c) demand new features, d) get support and e) annoy other > developers or upstream when they break something that has a knock-on > effect of breaking an unrelated package. I was rather unclear, I think your previous passage had me rather spot on for what I was wanting to do. -- gentoo-dev@gentoo.org mailing list