Re: [kde-community] finding a clear vision for KDE - first draft for discussion

[Martin Graesslin]

On Friday, February 12, 2016 12:07:27 PM CET Alexander Dymo wrote:
> On Fri, Feb 12, 2016 at 1:04 AM, Martin Graesslin  
wrote:
> > Why should there be a line?
> 
> I've been managing software development organizations since 2008. I
> attest to the importance of drawing a line. There's so much you can do
> with software. Unless you learn to say "no", you will not make a good
> product.
> 
> By the way, I learned this the hard way in open source world too. Let
> me tell you a story.
> 
> When I was a KDevelop maintainer during 3.x cycle, I welcomed every
> single KDevelop plugin into the core.
> 
> End result? We did not attract new developers this way, but instead
> were forced to maintain a huge collection of barely useful software
> with a small team.
> 
> During 4.x development we clearly defined the core of KDevelop. It was
> to be a great C++ IDE. Any plugin that did not fit into the core was
> separated into its own repository. What remained received as much
> attention as possible.
> 
> End result? A much better product. New contributors. And guess what?
> Some of the plugins that were separated not only survived, but saw
> more development and usage.

I interpret your answer as "KWin should not go into the cloud".

Thank you for your answer.

Martin


signature.asc
Description: This is a digitally signed message part.
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

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

[Martin Graesslin]

On Wednesday, February 10, 2016 4:37:33 PM CET Alexander Dymo wrote:
> > So a vision which would ensure that also future technologies could be
> > served, would not harm that? Let's just not close doors.
> 
> Sure. But let's also not spread thin. Do you think it makes sense to
> find a middle ground between two proposals?

If we just look at the vision statement (which is in your draft not really 
defined) then yes I think they are extremely close. I see the explicit mention 
of GUI as a problem, because we already do more than GUI and saying GUI closes 
the door to any non GUI future technology.

On the mission side I think we are further apart, but that's a topic to 
discuss once the vision is settled.

Cheers
Martin

signature.asc
Description: This is a digitally signed message part.
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community