[kde-community] finding a clear vision for KDE - an alternative draft for discussion

[Martin Graesslin]

Hi,

thank you for your replies. Unfortunately I don't find these satisfying 
answers. I asked for explanations why not. This is completely missing. A we 
should do GUI is no explanation on why we should not be a leader in the next 
big thing. So please explain in more detail, why you think KDE should not be a 
leader in future technologies.

Please also consider how you want to attract new developers, young students to 
work on KDE? How are we going to get in new developers if we discourage 
working on the new shiny stuff everybody wants? That's how we all got into 
KDE. We worked on the new shiny stuff. How are we going to attract students to 
work on desktop apps, when they maybe have never seen a desktop? How will they 
know at all about KDE which is currently non-existing on mobile even?

Furthermore how are you convincing the existing developer base to continue to 
work on KDE software if there is no prospect of leading in the next big thing? 
How do you convince me to continue to develop the desktop when I don't see a 
future for KDE due to not willing to go to the next thing?

Cheers
Martin

On Friday, February 5, 2016 4:54:31 PM CET Alexander Dymo wrote:
> A couple of years ago everybody though people will do all their tasks
> through the web browser. That turned out not to be the case.
> Applications made a huge comeback to mobile, and now to desktop. I
> agree with AlexN that this is where KDE's opportunity lies. Not in a
> cloud, not in knowledge management. It's here, in app development, the
> area of our expertise.
> 
> PS: not to say we should ignore the cloud. There are myriad of ways of
> integrating with cloud services which individual apps should
> definitely explore and implement.
> 
> On Fri, Feb 5, 2016 at 4:44 PM, Alexander Neundorf <neundorf at kde.org> wrote:
> > Hi,
> > 
> > ...
> > 
> >> Thus now my question: How will this vision provide us guidance for the
> >> next
> >> disruption? How will we be able to use this vision to be a leader in the
> >> next disruption? Please explain why you think that the vision will help
> >> in
> >> the next disruption. If you don't think that the vision is for that
> >> please
> >> also explain why you think that. E.g. if you think we shouldn't care
> >> about
> >> the next disruption, please explain the reasoning for it.
> > 
> > just answering for myself: for me, KDE actually doesn't have to be the
> > leader in the next disruption. For me, it is ambitious enough to become
> > the leader in a defined, but still wide area. Also in the future there
> > will be the need for local GUI software on normal PCs, notebooks,
> > tablets, smartphones, maybe projected interfaces. I want KDE to stay
> > focused on that for now, this is where we have expertise, we don't need
> > to throw that away.
> > Once such local software is not needed anymore (will that happen ? I don't
> > know), something will happen with KDE. Either it will fade away, or it
> > will
> > have slowly shifted by itself into some new direction. As I wrote, this
> > draft is not for eternity, it gives a focus for today.
> > 
> > And today, I still see so much work to do for the next few years. I don't
> > want us to give up on mobile. I have an awful mix of various apps on my
> > personal tablet/smartphones. We as KDE can do so much better than that:
> > free software, no ads, consistent user interfaces, reliable quality, etc.
> > 
> > Alex
> > 
> > _______________________________________________
> > kde-community mailing list
> > kde-community at kde.org
> > https://mail.kde.org/mailman/listinfo/kde-community
> 
> _______________________________________________
> kde-community mailing list
> kde-community at kde.org
> https://mail.kde.org/mailman/listinfo/kde-community

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20160208/168c451f/attachment.sig>