How to handle KDE not respecting YOUR distros requirements?

[Luca Beltrame]

In data giovedì 31 marzo 2016 18:19:16 CEST, Thomas Pfeiffer ha scritto:

> We're aware of that, and we're working on improving the communication of
> this. Does anyone here maybe have ideas on how we could make what Luca said
> above clearer to the public?

In my opinion this would include, among other things, ensuring that our own 
offering isn't "outdated": see www.kde.org for example. The rest would be to 
first let distros know that there is this distinction (we're doing this in 
openSUSE, not sure if it's succesful enough though ;). Perhaps provide a short 
"KDE software in a nutshell" document to distributions, too.

> Again: Any ideas on how we could improve this? Which information does
> distributions need and in which form?

For example: repo splitting. PIM had a huge number of splits this cycle. 
Something like mails to kde-distro-packagers at the start of the dev cycle 
like: "Hello people, we're going to reorganize our repositories, here's the 
new layout, and dependencies". 

I realize it is a lot harder than what I implied above, but I think if 
possible it wouldn't hurt. Having things to display dependencies (like done 
with Frameworks) would help too. 

> Is this maybe something that openSUSE could help us with? You guys seem to
> have much more experience with CI than we do, and you have infrastructure

This is more a question to Richard than me, I'm a very minor player in 
openSUSE. ;)

-- 
Luca Beltrame - KDE Forums team
KDE Science supporter
GPG key ID: A29D259B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/distributions/attachments/20160401/0e7eba02/attachment.sig>