From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C1vkC-0007Og-Jb for qemu-devel@nongnu.org; Mon, 30 Aug 2004 19:39:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C1vkB-0007Nh-E7 for qemu-devel@nongnu.org; Mon, 30 Aug 2004 19:39:24 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C1vkB-0007NN-AP for qemu-devel@nongnu.org; Mon, 30 Aug 2004 19:39:23 -0400 Received: from [216.254.0.201] (helo=mail1.speakeasy.net) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1C1vfG-0001Tv-T4 for qemu-devel@nongnu.org; Mon, 30 Aug 2004 19:34:19 -0400 Received: from dsl081-088-222.lax1.dsl.speakeasy.net (HELO [192.168.111.2]) ([64.81.88.222]) (envelope-sender ) by mail1.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 30 Aug 2004 23:34:17 -0000 Subject: Re: [Qemu-devel] Qemu development schedule? From: "John R. Hogerhuis" In-Reply-To: <002101c48ee5$46b2e280$20389c3f@computername> References: <000501c48eda$a026ab40$20649c3f@computername> <200408310107.07350.hetz@witch.dyndns.org> <002101c48ee5$46b2e280$20389c3f@computername> Content-Type: text/plain Message-Id: <1093908872.26682.76.camel@aragorn> Mime-Version: 1.0 Date: Mon, 30 Aug 2004 16:34:32 -0700 Content-Transfer-Encoding: 7bit Reply-To: jhoger@pobox.com, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Mon, 2004-08-30 at 15:59, Jeebs wrote: > So basically, there's no roadmap or schedule for features, etc. And it's > basically going to be a "free for all" for the foreseeable future. And I'd argue that this is a completely normal, effective, proven pattern for FOSS projects. Given this is volunteer work it is completely natural that the developer(s) organize work fun-down. Can you name any projects that don't operate this way and also do not have corporate sponsorship? Thankfully, the fun-down approach actually means the heavy lifting gets done early by characters like Fabrice. Polish (nice frontend) is something that can be thrown on later once the core functionality is in (that means speed, accuracy, and hardware emulation, in that order, IMHO...) If you need it now, contribute to the front end projects in some way; report bugs, talk to the developers, or fork it (last resort). Front end code isn't the hardest stuff to develop. As proof look at the VB programmer infestation in any corporate office. When Fabrice thinks that the software is too big to maintain alone, I'm sure he will delegate work. He doesn't seem to be at his breaking point yet. For now he seems to accept good patches, or writes patches himself when he doesn't like the way something was done. -- John.