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

List:       koffice-devel
Subject:    separating Koffice
From:       Sulyok Attila <sulyok () mfa ! kfki ! hu>
Date:       2008-03-03 13:58:25
Message-ID: 200803031458.25297.sulyok () mfa ! kfki ! hu
[Download RAW message or body]

My reflection on letters for "NlNet wants to sponsor KOffice logo design"

Reading the debate about the way the Koffice be sectioned into parts, it seems 
that you, developers, missed the grounds regarding the Koffice purposes.

Traditionally Office packages contain those sotware tools that fulfill the 
demands appearing in a common office workplace.
These demands are:
-writing some text with text-forming capability
-simple, however extended working with numbers
-some graphical ability for completing the results of the previous two
-not an ancient demand (however recently becoming very common): creating a 
  presentation using the previous three

I am convinced, any software package that want to be called Koffice should aim these 
user demands. 
Basically, doesn't matter , which version of the components are included in the \
package and  at which rate the components fit  together/integrated. It's only a 2nd \
or 3rd point. That matters what a user can do with the components.

The logical consequence of the above is that if the developers need to issue a \
Koffice 2.0 package before  all the components reach the proper reliability, there is \
two solution: 1. To communicate (similar to KDE 4.0) that it is a not fully complete \
issue and those users whose demands  are not met within 2.0, are encouraged to use \
the proper component of the previous version (etc 1.5.9) of Koffice,  2. To publish a \
mixed package that contains 1.5.9 and 2.0 components.

best regards

devians
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


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