On Donnerstag, 11. Februar 2016 22:46:46 CET Alexander Neundorf wrote: > > The vision may leave quite a bit of room for interpretation, especially > since it will be short. Some may understand one thing, some may understand > another thing. This will lead to more conflicts later on due to > misunderstandings (like "we cannot put this into the mission because it > contradicts the vision, which we already agreed on.")
We should be clear about what the vision is. It's not a legal or technical document, it's about expressing our idea of our purpose, our common dream. The vision alone won't keep people together or give complete criteria about what to do. This always have to be done by people willing to cooperate, to constructively interpret, and to realize the emotional value of a vision in more practical terms. There is more to it which has to accompany the vision, common values, missions, strategy, plans, etc. No vision document, however well it is written, will prevent conflicts or give definitive answers, and there always will be projects which will only tangentially be touched by the vision. As it already was mentioned in the thread we should not focus on criteria who and what to keep out, but we should focus on what drives us forward. -- Cornelius Schumacher <[email protected]> _______________________________________________ kde-community mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-community
