Date: Fri, 30 Oct 1998 09:06:39 +0000 From: Scott Mitchell <scott@dcs.qmw.ac.uk> To: Drew Baxter <netmonger@genesis.ispace.com>, Wes Peters <wes@softweyr.com>, Greg Lehey <grog@lemis.com> Cc: Licia <licia@o-o.org>, "Jason C. Wells" <jcwells@u.washington.edu>, advocacy@FreeBSD.ORG Subject: Re: Let's get back on track. Message-ID: <19981030090639.L9354@dcs.qmw.ac.uk> In-Reply-To: <4.1.19981029184530.0097e790@genesis.ispace.com>; from Drew Baxter on Thu, Oct 29, 1998 at 06:47:48PM -0500 References: <Pine.BSF.4.05.9810281808020.7221-100000@s8-37-26.student.washington.edu> <Pine.BSF.3.96.981028205707.13136A-100000@o-o> <19981029161049.Q25247@freebie.lemis.com> <19981029100843.F9354@dcs.qmw.ac.uk> <19981029204848.W25247@freebie.lemis.com> <19981029105821.G9354@dcs.qmw.ac.uk> <19981030084254.Y25247@freebie.lemis.com> <3638F6A9.1D526912@softweyr.com> <4.1.19981029184530.0097e790@genesis.ispace.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 29, 1998 at 06:47:48PM -0500, Drew Baxter wrote: > At 04:13 PM 10/29/98 -0700, Wes Peters wrote: > >Scott Mitchell wrote: > > > >> > The credibility of any certification programme won't be enhanced if we go > >> > slapping logos all over products that require an inordinate amount of > >> > effort to install. If there's a port to automate it all, then great, > >> > otherwise you may be in for a nasty surprise when you get the box home. > >> > > >> > Please understand that I'm entirely in favour of a 'works with FreeBSD' > >> > programme -- just don't dilute its' worth by overdoing it! > >> > >Greg Lehey wrote: > >> > >> Agreed. Comments, you others? > > > >Yeah, let's see if we can get this discussion back on track. I've thought > >about this a lot overnight (instead of staying up all night scribing email > >messages ;^) and have decided that branding something that can't be > >installed by an ordinary, non-programmer "superuser" is not appropriate. > > > >Licia commented sometime yesterday that FreeBSD ports for these applications > >could be provided by users, and wouldn't necessarily have to come from the > >vendor. You could've knocked me over with a feather! I *NEVER* intended > >for vendors to write FreeBSD port kits; I had always imagined this to be > >the logical finishing point of the FreeBSD volunteers who test and install > >the application in the first place. > > > >So, let me re-propose the following two categories. I'll use my original > >names; we can fight about that later on. > > > >Works with FreeBSD: An application that was not written for FreeBSD, but > > can be made to run on FreeBSD *reliably.* A FreeBSD > > port kit has been developed and posted on the FTP > > server that will install the application from a > > download or from vendor-supplied media. > > > >Again, the classical example of this is the Linux version of Adobe Acrobat > >Reader. Since the port kit already exists, this logo could be awarded to > >Acrobat immediately. > > > >The port kit in this case is a requirement because it both verifies that > >the application can be run on FreeBSD as long as the precursor requirements > >are met, and because it enables any reasonably adept system administrator > >to install the application such that it will work. > > > > > >Designed for FreeBSD: An application with FreeBSD binaries and a FreeBSD > > installation program, from the vendor. A FreeBSD > > port kit (created by FreeBSD volunteers) that auto- > > mates the install process in a "standard" installation > > MAY be available to simplify installation. > > > >The classical example for this category is Communicator. Netscape provides > >FreeBSD executables and an install program for FreeBSD; a port kit is > >available that will automate the installation. > > > >The port kit in this case is not REQUIRED; the application already includes > >an installation program that will install the product on FreeBSD. A port > >kit, developed by FreeBSD volunteers, may make the product easier to install, > >and will be linked on the web page if present. > > > >The reason for two levels of "logoization" is to provide extra recognition > >for those vendors who have gone the extra mile and made their applications > >specifically for FreeBSD. This applies to Netscape, soon to be for Applix- > >ware, and for a number of other really cool companies. > > > >-- > > Where am I, and what am I doing in this handbasket? > > > >Wes Peters > +1.801.915.2061 > >Softweyr LLC > wes@softweyr.com > > I think you hit the nail on the head. sounds good. > > I Wonder if Netscape's Communicator CD carries the Unix versions at all, > let alone the FreeBSD version. I'd imagine they'd eat up some sort of a > logo to stick on the cd.. > > Oh and at the same time, kudos to Netscape, since we don't see Internet > Hygenist (er Explorer) being ported to anything but Mac and Windows. I > personally hope it stays that way as well. > Yeah, this sounds good. Scott -- =========================================================================== Scott Mitchell | PGP Key ID |"If I can't have my coffee, I'm just <scott@dcs.qmw.ac.uk> | 0x54B171B9 | like a dried up piece of roast goat" QMW College, London, UK | 0xAA775B8B | -- J. S. Bach. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981030090639.L9354>