[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Cobalt Wish List
- Subject: RE: [cobalt-users] Cobalt Wish List
- From: "Dan" <dan@xxxxxxxxxxxxx>
- Date: Mon May 15 11:10:47 2000
>
> * BUG FIXES!
>
> * ALPHABETICAL
> * FRONTPAGE.
Agree with the above.
>
> * KNOWLEDGEBASE, as in, updated (some basic DNS info,
> MySQL and PHP3 instructions would be nice; better yet,
> how about a MySQL/PHP3 .pkg file for us non-tech guys?
> yes, it's not supported and voids our warranty; just
> fixing half the 'bugs' has put most of us there...)
What kind of basic DNS info, as it relates to the Cobalt server are you
looking for?
Regarding the PHP/MySQL, I think they'd open themselves up to a lawsuit by
the first person that says since they had it on their page, it should be
supported and they need to fix my broken server since the installation
screwed it up.
>
> * TECH SUPPORT, aka lack thereof, or how to reduce call
> volumes so Cobalt can actually answer phone calls or
> respond to emails (see previous point for solution).
Buy from a reseller that offers support for the product I think would be the
way to go. I'd be curious to see from this list, the people that are calling
Cobalt for support, where they bought their unit and what they paid. It
would be interesting to compare that to some of the VARs that have been
mentioned on the list that support their customers and what they charge for
the servers.
>
> * FEATURES. How about an online suggestion page, where
> Cobalt owners can submit feature requests. The Top
> 10 could be listed and users could vote on them (gee,
> what a novel idea - listen to the customer!)
Can you imagine a restaurant with a list of customer complaints posted on
the door? Why would they want to post that on their site? Listening to
customers doesn't require informing future customers of other customer's
complaints. I've never seen a business that does this, except via
newsgroups.
>
> * SIMPLICITY. When a problem does arises through the fault
> of Cobalt (ie: patch conflict, software bug), can we
> just admit a mistake has occured and try to fix it?
>
> Removing the patch/file and pretending it never existed
> doesn't help anyone. And if possible, trying to involve
> fewer than a half dozen people always makes it easier
> for the customer.
Hopefully they've learned by their past screwups in this regard. I know I'm
not the first to install a Cobalt patch.
--
Dan Kriwitsky