Date: Mon, 7 Feb 2005 11:47:19 +0000 From: Joseph Koshy <joseph.koshy@gmail.com> To: Robert Watson <rwatson@freebsd.org> Cc: Scott Long <scottl@freebsd.org> Subject: Re: The case for FreeBSD Message-ID: <84dead7205020703474f9add1@mail.gmail.com> In-Reply-To: <Pine.NEB.3.96L.1050206132109.55669F-100000@fledge.watson.org> References: <4205F382.8020404@freebsd.org> <Pine.NEB.3.96L.1050206132109.55669F-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
rw> -- your list of features would make the great beginnings of a white paper
White papers are an excellent idea.
These are some of the questions that I have faced when talking about
FreeBSD:
The initial set:
* What is FreeBSD? What is it being used for? What kind of products are
being built with it? Which organizations are using FreeBSD? Why should
we choose FreeBSD over other alternatives?
Most folk haven't heard about FreeBSD.
Then:
* How does one *use* FreeBSD? How does one architect a solution
around it? What are its strengths, and what weaknesses should we
be aware of? What hardware is supported?
And then when people look at the long-term, along comes another bunch
of questions:
* How does the project work? How do users get heard?
Who supports us? Is the "free" support any good?
Is there a way to pay someone to support us?
Another set:
* Where do we find FreeBSD savvy developers? Is there training
available? Is there anything like FreeBSD certification for developers?
Is a FreeBSD based product maintainable?
It would be great to be able to hand over people a bunch of PDFs instead
of having to talk :).
--
FreeBSD Volunteer, http://people.freebsd.org/~jkoshy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?84dead7205020703474f9add1>