| || |
* add your notes here
* add your notes here
| || |
Latest revision as of 13:18, 8 April 2016
This page is for brainstorming topics related to KDE's mission. For KDE's vision see KDE/Vision.
|The mission tells us how we want to achieve our vision. It should not be confused with the vision (what we aspire to do) or the manifesto (who we are).|
|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
- KDE's software should by default not share information with third parties
- Software should be attractive to use *AND* support privacy, the user should not have to choose between "nice, easy to use and beautiful" and his digital privacy
- end-user focus in functionality
- Online services that are important to the user should be supported, but if they are bound to share data (breach privacy), they may not be enabled by default
- KDE software should not be limited to a single class of devices, applications may support one or more form factors at the same time
- Responding to AlexN: it seems that "cross-platform, all major OS" and "well-integrated with the host OS" will often be conflicting goals, so in my opinion the mission statement should clearly state how KDE wants to prioritize one over the other when both can't be achieved with reasonable effort and development time.
- AlexN: let me put it like this: let's prioritize following the host OS standards. Users shouldn't have to buy in into "KDE" if they just want to use e.g. kate, and kate shouldn't feel out of place under OSX or Windows (and they are working towards that). IMO the standalone kate-installer for Windows is a much better approach than the all-integrated KDE-on-Windows appraoch.
- should we think about who we target mainly ? Geeks, developers, home users, business users, etc ?
- I guess we are all here because we believe FLOSS is better for users. What does that mean ? Are we working towards our goal if we enable users to use FLOSS for more of their tasks ? Or are we only working towards our goal if we get more users to use full FLOSS systems ?
- 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:
- flexible, highly configurable
- an SDK (currently mainly KF5), possible attributes:
- 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.
- 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
- 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
- “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
- goals that are unrelated to the vision
- things which are better mentioned somewhere else, e.g. in the manifesto
- all corner cases we do too, IMO it is better if we just point out our strengths
- unrealistic exaggerations
Other mission documents we should look at
This page was last modified on 8 April 2016, at 13:18. Content is available under Creative Commons License SA 4.0
unless otherwise noted.