[kde-community] RFC: Distribution outreach program

[Martin Graesslin]

On Wednesday, February 3, 2016 1:46:16 PM CET Luca Beltrame wrote:
> Il Wed, 03 Feb 2016 11:40:58 +0100, Martin Graesslin ha scritto:
> > to use a specific technology. It's totally fine if we go ahead and say
> > our technology stack includes systemd, networkmanager and apparmor. If
> > your distro cannot do that it's not providing the best expected
> > experience. In reality we don't have the manpower to test multiple
> 
> I'm answering you but this is a point more general, which I overlooked
> before: don't forget that distributions ship other software!
> 
> And said software has to work and coexist with KDE software. So as a
> distribution, often we have to take compromises to ensure everything works
> as intended.

Yes I know, that's the obvious reply you get from distros. And I call BULLSHIT 
to that. If a distribution ships with a broken bluetooth setup, because 
another desktop requires an outdated version there is something broken in this 
so deeply that I cannot find words about it.

That's the nonesense which has to stop. I get that distros have problem with 
that, but then the users should know about it. And we can do that by saying 
which requirements we want and which distros can serve it. So that users can 
do an educated evaluation of the situation. Hey I need bluetooth and $DISTRO 
cannot, so I go for $OTHERDISTRO.

Also I think there is always a way to solve it if the distros really tried. 
It's so awesome that users can install multiple DEs, but is that a reason to 
ship them all broken? If they need different conflicting technologies one can 
conflict in the packages.

Cheers
Martin
-------------- 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/20160203/6e886f54/attachment.sig>