Date: Sat, 11 Oct 2003 02:13:10 -0700 (PDT) From: Mike Hoskins <mike@adept.org> To: advocacy@freebsd.org Subject: Re: A case of FreeBSD users shooting all FreeBSD users in the foot? Message-ID: <20031011015915.D56283@fubar.adept.org> In-Reply-To: <200310110148.42949.j.e.drews@worldnet.att.net> References: <002801c38fb1$95e804e0$0200a8c0@sbcgolbal.net> <200310110148.42949.j.e.drews@worldnet.att.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 11 Oct 2003, Jonathan wrote: > I read a few of the comments and they paint a very unflattering view of the > FreeBSD community. actually, they paint an unflattering view of IRC. that's nothing new. > 1) Most newbies require CD's to do an install yet FreeBSD mall has terrible > advertising for it's CD's. There are no screenshots of Gnome or Kde and no > package descriptions whatsoever. You don't see anything like this (GNOME) > http://www.FreeBSD.org/gnome/screenshots.html or this (KDE) > http://freebsd.kde.org/screenshots.php at FreeBSD mall. Furthermore > OpenOffice is not on the RELEASE Cd's. That is a huge mistake. screenshots have marginal value. (since some of us don't want gnome or kde environments installed, the screenshots would tell us nothing about the specific operating environment we would configure.) still, it can't hurt and it seems like it'd be easy enough for freebsdmall to link to screenshots if they're already hosted on freebsd.org. how big is openoffice again? how much space are free on the release CDs? i wouldn't want to second guess packaging decissions like that without having all the facts. > 2) The documentation is sometimes too vague and aimed at computer > professionals. I tried to configure a firewall using "Dialup firewalling with > FreeBSD" and I could not get it to work ( http://www.freebsd.org/doc/ this is a result of starting as a "server OS" (that's really still the goal, it just happens to make a great desktop too). a lot of the system and misc docs are written by computer professionals. :) the best way to get a plethora of docs at various reading levels/styles is to have a lot of people writing documentation. if possible, document (from your perspective) what you have to do to get things working and submit that back to the doc project. http://www.freebsd.org/docproj/index.html (of course you can also host docs yourself of submit articles to any of the bsd/opensource pubs.) > 3) While FreeBSD ports are generally very good there is little coordination > amongst the ports maintainers. That is if the ghostscript port gets changed, > I find out about it when it breaks printing in the word processors. For a > hobbyist it's an annoyance, for a company using FreeBSD desktops it's a > disaster. this is a complex issue to manage, but i'm sure there's always room for improvement. how would you propose increasing coordination or the effectiveness of communication amongst ports maintainers? for a company using opensource desktops, you should be installing standardized packages from your gold/build server(s). don't build randomly updated ports resulting in differing files/libraries/bins on each machine. ;) packages are you friend. at times there are problems with packages too, but that's the case on every OS... and most people i know that have strict requirements build their own packages so they can roll any machine with known results. -mrh -- From: "Spam Catcher" <spam-catcher@adept.org> To: spam-catcher@adept.org Do NOT send email to the address listed above or you will be added to a blacklist!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031011015915.D56283>