From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gordan Bobic Subject: Re: [Xen-users] xen forum Date: Wed, 22 May 2013 07:55:00 +0100 Message-ID: <519C6BC4.2050506@bobich.net> References: <20130521142917.GO492@phenom.dumpdata.com> <1369148674.21246.92.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Bartek Krawczyk Cc: xen-users , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 05/22/2013 07:18 AM, Bartek Krawczyk wrote: > On 21 May 2013 17:04, Ian Campbell wrote: >> On Tue, 2013-05-21 at 15:57 +0100, Gordan Bobic wrote: >>> On Tue, 21 May 2013 10:29:17 -0400, Konrad Rzeszutek Wilk >>> wrote: >>>> On Sun, May 19, 2013 at 09:09:00AM -0600, jacek burghardt wrote: >>>>> I believe both mailing lists are great but there are so may postings >>>>> that >>>>> many issues get missed. There are some bugs that hand never been >>>>> resolved >>>>> because developers are unaware of it. I just setup forum for xen >>>>> users at >>>>> sam.hebe.us/forums please be free to join >>>> >>>> It would be easier for us if the bug reports and such were posted on >>>> xen-devel. >>>> Please consult http://www.chiark.greenend.org.uk/~sgtatham/bugs.html >>>> when >>>> doing it. >>> >>> Surely a bug-tracking system that emails all reports to xen-devel >>> automatically would cover the best of both worlds, would it not? >> >> Not unless developers can reply to the bug by hitting reply in their >> MUA. > > Please drop the forum idea. Xen should use a proper bug tracking > system like Bugzilla (which allows replying to bugs by clicking > "Reply" in MUA). > Take a look at: http://www.bugzilla.org/docs/4.0/en/html/api/email_in.html +1 Along with a wiki for documentation that is actually kept updated when features are added/removed/changed and more importantly, that clearly states if/when obvious features are unexpectedly and conspicuously missing (e.g. domU config file method of passing multiple USB devices to domU). Gordan