[kde-community] KDE Mission - let's do this!

Thomas Pfeiffer thomas.pfeiffer at kde.org
Sun Apr 24 13:15:17 UTC 2016


On Sonntag, 24. April 2016 11:36:54 CEST Clemens Toennies wrote:
> Am 23.04.2016 um 22:36 schrieb Alexander Neundorf:
> > Hi,
> > 
> > On Wednesday, March 30, 2016 22:43:03 Thomas Pfeiffer wrote:
> >> Hi everyone,
> >> now that we've finally agreed on a vision for KDE [1] and have that out
> >> of
> >> the way, we can fully focus on how we want work towards that vision.
> >> Alex has already set up a Wiki page for brainstorming notes [2], so it
> >> would be great if everyone who has opinions or ideas about how we can
> >> nudge the world towards the one we envision could add them to it.
> >> It's really just brainstorming, no ideas are "bad" or anything, everyone
> >> and everything is welcome!
> >> 
> >> I'd suggest that we let the brainstorming phase last until Friday and
> >> then
> >> start discussing the ideas collected on that Wiki page.
> >> 
> >> So now let's focus our brains on the KDE Mission and please fill the wiki
> >> page! Thanks,
> >> Thomas
> > 
> > there is somehow not much going here...
> > Ideas how do we get this going ?
> 
> I would go with the 4 points you mentioned:
> 
>   * end-user applications
>   * a "classic" UNIX desktop
>   * an SDK (currently mainly KF5)
>   * a user interface for mobile/embedded Linux systems (currently Plasma
>     Mobile)
> 
> 
> Two suggestions:
> How about combining the two points "classic unix desktop" and
> "mobile/embedded", to clarify the team working "on the desktop" is
> really sharing ~80% of the code via one base (plasma) and people could
> use that plasma even in tv, car or aviation systems:
> * a modern (unix) shell, that targets the classic desktop and can
> converge towards mobile/embedded [somewhat like unity / android /
> windows10]?

I would not go into too much detail about Plasma in KDE's mission. That's what 
Plasma's product vision is for.
If we go into so much detail about the destkop in KDE's mission, it reinforces 
the popular perception that KDE is all about the desktop (or still /is/ the 
desktop), and those creating applications which are not tied to the desktop 
may not feel like they're part of KDE's mission.
 
I do agree that we should put convergence in our mission, though, because that 
applies to the desktop as well as applications.

> Also let's mention "end-user webservices" to be included, as subpoint
> under "end-user applications" (owncloud or wiki2learn), then this
> mission imo would still very focused and clear with our goals laid out
> in our vision.

+1
We could even say that our /primary/ technology is Qt (because it is) if we 
want to position ourselves as the go-to community for everything Qt, without 
excluding non-Qt applications.




More information about the kde-community mailing list