[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-promo
Subject:    Re: [kde-promo]  Fwd: Reports from Brazilian Open Software Conference
From:       Mark Bucciarelli <mark () easymailings ! com>
Date:       2003-06-09 20:26:08
[Download RAW message or body]

On Monday 09 June 2003 4:18 pm, Mark Bucciarelli wrote:
> Those subscribed to -devel and -core already say this.
s/say/saw/

message cut and pasted below ...

From: "Aviram Alkalay" <aviram@br.ibm.com>
To: "Helio Chissini de Castro" <helio@conectiva.com.br>, 
kde-devel@kde.org, kde-core-devel@kde.org
CC: Thiago Macieira <thiagom@mail.com>

Helio, KDE-Developes, etc,
I'm a kind of KDE contributer also in Brazil. Soon CVS will receive 
some pieces of code I'm working on.

At a corporate level, here at IBM we are talking about a global 
desktop support offering, but it is mostly based on Ximian (read 
Gnome).  To let us say we globally "support a Linux Desktop", we need 
somebody to give us 3rd level support, somebody to call when a 
customer have a problem and a commitment that there is somebody to 
look and fix the bug. We (or a customer) can't depend on the 
kde-devel mailing list.

> From this perspective, Ximian represents a corporate endpoint for it, 
with solutions like red-carpet, etc. We can also sign a support 
contract with them.

I noticed there is a KDE::Enterprise initiative, but they look to me 
as inexpressive from a corporate perspective. I mean people that can 
come and talk in a business level with business people saying "sign 
this contract and I'll give you support", not just developers saying 
"subscribe this mailling list and you'll have free support from the 
source".

Personaly, I prefer KDE, and I believe it is a much more integrated, 
smooth and advanced desktop for the final user. I want KDE to be the 
winner of the Linux desktop (or any desktop). But a corporate 
commitment is vital.

As an example, few day ago I reported a design problem (bug #59285) 
regarding 100% unaccessible files when their names are non-UTF-8 
encoded. Many developers understood the severity but the position was 
"this is mainly unsupported, and will fix when we'll have time". I'm 
not blaming them, because I understand. But this is the kind of 
problem a company can't stand without help. There is many ways to 
workaround this particular situation, but I'm talking about the 
approach to the problem, and not the problem per-se.

Thank you,
Avi

Avi Alkalay <avi at br.ibm.com> :: SW & IT Architect
LA Linux Impact Team :: IBM Brazil :: http://ibm.com/linux
Tel: +55 11 2132-2327 | Mobile: 9659-9059 | Tie: 842-2327
> > Think Open : Think Linux ::

 
_______________________________________________
This message is from the kde-promo mailing list.

Visit http://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or \
temporarily stop your subscription.


[prev in list] [next in list] [prev in thread] [next in thread]