KDE/Mission/Brainstorming: Difference between revisions
Line 10: | Line 10: | ||
AlexN: | AlexN: | ||
* the main | * I'd like the mission to state clearly the main fields/products we are working on, Add attributes for each ? So, the list is IMO: | ||
** a complete set | ** end-user applications, possible attributes: | ||
** a "classic" UNIX desktop, | *** a complete set | ||
** | *** cross-platform, all major OS | ||
** a user interface for mobile/embedded Linux systems (currently Plasma Mobile). | *** well-integrated with the host OS. | ||
*** reliable (includes stable) | |||
*** easy-to-use, consistent user interfaces | |||
*** goal: become the number 1 in end-user/GUI applications on all major operating systems | |||
** a "classic" UNIX desktop, possible attributes: | |||
*** easy-to-use | |||
*** flexible, highly configurable | |||
*** beautiful | |||
** an SDK (currently mainly KF5), possible attributes: | |||
*** cross-platform | |||
*** easy-to-use, Qt-like API | |||
*** robust, stable | |||
*** fit for FLOSS- and also proprietary development | |||
*** Goal: become the number 1 provider for Qt-based libraries (also in the commercial Qt community) | |||
** a user interface for mobile/embedded Linux systems (currently Plasma Mobile), possible attributes: | |||
*** you know better than me... | |||
*** goal: best FLOSS solution in class. | |||
Ruphy: | Ruphy: | ||
* Additionally software for open knowledge and non-LCD devices | |||
* The democratic and inclusive process of development | * The democratic and inclusive process of development | ||
* Pragmatic mindset when technological questions have to be answered | * Pragmatic mindset when technological questions have to be answered |
Revision as of 19:15, 4 April 2016
This page is for brainstorming topics related to KDE's mission. For KDE's vision see KDE/Vision.
TODO |
---|
A few important notes are already covered at KDE/Vision/Drafts/A. They should be condensed and be used here. |
Things that are important to me for the mission
- add your notes here
AlexN:
- I'd like the mission to state clearly the main fields/products we are working on, Add attributes for each ? So, the list is IMO:
- end-user applications, possible attributes:
- a complete set
- cross-platform, all major OS
- well-integrated with the host OS.
- reliable (includes stable)
- easy-to-use, consistent user interfaces
- goal: become the number 1 in end-user/GUI applications on all major operating systems
- a "classic" UNIX desktop, possible attributes:
- easy-to-use
- flexible, highly configurable
- beautiful
- an SDK (currently mainly KF5), possible attributes:
- cross-platform
- easy-to-use, Qt-like API
- robust, stable
- fit for FLOSS- and also proprietary development
- Goal: become the number 1 provider for Qt-based libraries (also in the commercial Qt community)
- a user interface for mobile/embedded Linux systems (currently Plasma Mobile), possible attributes:
- you know better than me...
- goal: best FLOSS solution in class.
- end-user applications, possible attributes:
Ruphy:
- Additionally software for open knowledge and non-LCD devices
- The democratic and inclusive process of development
- Pragmatic mindset when technological questions have to be answered
- Do-ocracy and respect-based system for decision making
Thomas:
- Pioneering human-focused/usable security and privacy in the FOSS world
- Offering Free alternatives to popular proprietary tools which are superior to their proprietary counterparts
- Supporting proprietary services to pick up people where they are, but trying to offer the best experience with FOSS services (e,g, ownCloud vs. Dropbox, Kolab vs. Exchange, diaspora vs. Facebook/G+ etc.) in order to make changing to them an easy choice for users
- Convergence across device classes
- Convincing organizations to switch to (our) Free software
Olaf:
- “KDE aims tot offer complete, well-integrated solutions – while connecting different platforms, devices and online services.”
- clear relation to vision: How does the mission help achieve the vision?
- Open for collaboration: Cooperation with partners that fit our goals and strategies
- important question: How will do we go into the future? (less important: documenting what we currently do)
Things that I think should not be in our mission
- add your notes here
Olaf:
- goals that are unrelated to the vision
AlexN:
- things which are better mentioned somewhere else, e.g. in the manifesto