From owner-freebsd-advocacy@FreeBSD.ORG Wed Sep 17 15:55:19 2003 Return-Path: Delivered-To: freebsd-advocacy@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67A5816A4C1 for ; Wed, 17 Sep 2003 15:55:19 -0700 (PDT) Received: from zeus.acuson.com (ac17860.acuson.com [157.226.71.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69BC6442A2 for ; Wed, 17 Sep 2003 15:49:58 -0700 (PDT) (envelope-from DavidJohnson@Siemens.com) Received: from mvaexch02 ([157.226.230.209]:4007 helo=mvaexch02.acuson.com) by zeus.acuson.com with esmtp (Exim 4.14) id 19zl6w-0001yu-3w; Wed, 17 Sep 2003 15:49:22 -0700 Received: by mvaexch02.acuson.com with Internet Mail Service (5.5.2653.19) id ; Wed, 17 Sep 2003 15:47:06 -0700 Received: from dhcp-46-151.acuson.com ([157.226.46.151]) by mvaexch01.acuson.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id SXCQZRSF; Wed, 17 Sep 2003 15:46:15 -0700 From: Johnson David To: Michal Pasternak Organization: Siemens Medical Systems Date: Wed, 17 Sep 2003 15:48:22 -0700 User-Agent: KMail/1.5.3 References: <20030917160654.52ceb56c.kitbsdlist2@HotPOP.com> <20030917212259.GA12266@pasternak.w.lub.pl> In-Reply-To: <20030917212259.GA12266@pasternak.w.lub.pl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309171548.22742.DavidJohnson@Siemens.com> X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *19zl6w-0001yu-3w*TAZbINZVuKw* X-SA-Exim-Scanned: No; SAEximRunCond expanded to false cc: freebsd-advocacy@freebsd.org Subject: Re: Desktop FreeBSD X-BeenThere: freebsd-advocacy@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Evangelism List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2003 22:55:19 -0000 On Wednesday 17 September 2003 02:23 pm, Michal Pasternak wrote: > Just port it from Debian... and tell ports maintainers to update > their files. You need to have such "update-menu" description file - > and you need to know, which package is a windowmanager, to also > generate configuration for it. The Debian way is nice, but we already have some pieces of our own that we should work with. I would say use Debian as inspiration and a source of ideas, but still do it our own way. The more you have to tell port maintainers what to do, the more difficult it will be to get buy-in. So definitely get a prototype of something working first. It's an easier sell that way. > Python seems a correct language to code such task in. Network > infrastructure would be powered by Twisted Python > (www.twistedmatrix.com), GUI would be done via py-gtk2. Stuff to be hashed out. Personally I think C/C++ is the best to code this in. And if I had to go with an interpreted language, I would probably pick Ruby. See how contentious this stuff gets! David