From owner-freebsd-chat Fri Jun 8 17: 5:47 2001 Delivered-To: freebsd-chat@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id EA05F37B406 for ; Fri, 8 Jun 2001 17:05:42 -0700 (PDT) (envelope-from jason.anderson@windriver.com) Received: from peale.wrs.com (peale [147.11.36.41]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id RAA03499; Fri, 8 Jun 2001 17:03:44 -0700 (PDT) Message-Id: <5.0.2.1.2.20010608092020.02a09410@mail.wrs.com> X-Sender: jasona@mail.wrs.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Fri, 08 Jun 2001 10:34:52 -0700 To: j mckitrick , Jordan Hubbard From: "Jason S. Anderson" Subject: Re: BSD direction/Damonnews article Cc: brett@lariat.org, freebsd-chat@FreeBSD.ORG, grog@lemis.com In-Reply-To: <20010607143457.B42170@dogma.freebsd-uk.eu.org> References: <20010607061351Z.jkh@osd.bsdi.com> <20010607134347.A41764@dogma.freebsd-uk.eu.org> <20010607055051K.jkh@osd.bsdi.com> <20010607140103.A42170@dogma.freebsd-uk.eu.org> <20010607061351Z.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm a Wind River employee (actually the engineering manager responsible for Wind's FreeBSD development activities), but the comments and opinions below are my own. :) First, the most direct question: What has directly changed as a result of the Wind/BSDi transaction? Ownership of some equipment and contractual relationships, the transfer of some personnel (a small percentage of the total FreeBSD community), and the introduction of a new corporate sponsor. The core concern I am hearing from reading mailing lists and whatnot seems to be whether Wind will help or hinder the project. Personally, I believe that's up to you, me, Jordan, and everybody else at Wind River and in the community to determine. It's not something that either side is going to be able to independently resolve. Wind River wants to find ways to support and enhance FreeBSD and its value chain in a way that delivers returns to its own commercial efforts; the community wants to find ways to leverage Wind's position in various industries to gain visibility and capabilities. These are not mutually exclusive goals, and I'm confident that we'll be able to find some very creative and compelling new ideas on how to make that happen. At 02:34 PM 6/7/01 +0100, j mckitrick wrote: >What can be done to more effectively direct the volunteer effort, and who >should take the lead in doing so? I have some ideas about this, but I haven't been working with FreeBSD for very long so I'm not sure whether or not they are things that would be truly useful. I'm VERY interested in hearing ideas from others on some pragmatic things that Wind could do to support the community, but doing so in a way that doesn't push a corporate message down the throat of the technology. One possible scenario would be for Wind River to provide some common infrastructure and "glue" to make it easier to publicize and coordinate development activities underway in FreeBSD; there may be specific technology areas that Wind has a strong interest in making happen and in those scenarios we could provide more direction and management. Installation and packaging technologies. Web-based development collaboration. Robust test automation and quality assurance capabilities. Anyway, I just thought I'd dip my toe in the waters. You'll all undoubtedly see more of me in the future but we're still internally sorting out some of the integration details so I'm not prepared (yet) to answer many questions. Cheers, -Jason ---------------------------------------------------------------------------- Jason Anderson email: jason.anderson@windriver.com Manager, Platforms Operations Programs ph: 510-749-2202 Manager, FreeBSD Engineering fax: 510-749-2010 Wind River cell: 510-708-3588 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message