From kde-community Thu Aug 22 23:10:09 2013 From: "Aaron J. Seigo" Date: Thu, 22 Aug 2013 23:10:09 +0000 To: kde-community Subject: Re: [kde-community] Why were there no talks about Ubuntu Mobile at Akademy? Message-Id: <2091828.5ca5ACPge4 () freedom> X-MARC-Message: https://marc.info/?l=kde-community&m=137721303027685 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============6577225909516136032==" --===============6577225909516136032== Content-Type: multipart/signed; boundary="nextPart45924813.UmfCk9zaAc"; micalg="pgp-sha1"; protocol="application/pgp-signature" --nextPart45924813.UmfCk9zaAc Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" On Wednesday, August 21, 2013 09:14:58 Michael Zanetti wrote: > - Not all areas can be shared. This is true. So let=E2=80=99s focus on the many things that can be ins= tead of=20 focusing on what can=E2=80=99t be done :) > I for one work on Unity8, which just works > and looks so different in every way than plasma does. We don't need > Plasmoid containers, you don't need search scopes.=20 How do you know we don=E2=80=99t need search scopes? The functional similarity between =E2=80=9Csearch scopes=E2=80=9D and P= lasma::AbstractRunner=20 is pretty stunning, actually. > - Once there is something which might make sense to be shared, it req= uires > the exact people working on it having interest in collaborating. Whic= h Yes .. and no. If we leave it up to each and every individual to make a decision on th= eir own=20 in a vacuum, then you are correct. If we make thoughtful community/corporate encompassing goals then it is= not=20 left up to each individual: there will be a point of guidance that peop= le can=20 use to guide their decisions. > means, the responsive KDE person needs to accept that a certain API n= eeds > to change for requirements NOT needed by KDE This is a non-sequitor. If someone is using KDE libraries, then their=20= requirements become part of what is needed by KDE. KDE is not a castle = on a=20 hill with a moat around it; it is an open marketplace where the edges a= re=20 defined by participation. > and the responsive person in > Canonical needs to have interest in pulling in something that most li= kely > can do way more than Ubuntu needs at this stage, There is that word again: =E2=80=9Clikely=E2=80=9D :) Every time I see = that I think =E2=80=9C.. it=20 means we haven=E2=80=99t done the necessary homework to know for sure a= nd so people=20 are making assumptions=E2=80=9D There are two important points to consider: a) Probably most libraries used do more than Ubuntu needs. Is every gli= bc call=20 used by Ubuntu software written by Canonical? Is every Qt API used? (QW= idget,=20 e.g.) b) If a library in KF5 is poorly modularized, resulting in something th= at does=20 so much more than it ought to that we should reconsider the division li= nes=20 within it, we need to know *now*. So if there is a KF5 library that wou= ld make=20 sense being used in Unity (e.g.) but it does =E2=80=9Cway too much=E2=80= =9D, we can fix that.=20 But we need to know. > needed. It is not possible for me or Albert to go to some API guys an= d tell > them: You have to share code with KDE. This needs to happen from insi= de the > team. The person doing the work must drive it. There must be leadership that can set engineering mandates? > Now, coming from the Gnome/Gtk area, Canonical's people mostly are aw= are > what code could be shared with Gnome, but not many of them have a clu= e what > KDE frameworks actually is. I=E2=80=99d just echo Thiago=E2=80=99s questions here, as they are trul= y insightful and key .. > Same the other way round. I'm quite sure very > few here know how the Ubuntu's architecture is built up. Not many, I=E2=80=99m sure, but they exist. We have the Kubuntu folks a= nd then there=20 are crazy people like me who do look at what ends up in Canonical=E2=80= =99s public=20 repos and who have even done things like port apps written for Ubuntu T= ouch to=20 other QML component sets. So the ignorance can be dissipated through ef= fort! > Then again, we actually do share and reuse some code. Take all the li= ghtdm > stuff for example, the dbusmenu stuff and many more libs which in his= tory > have flown into both directions already. The status notifier stuff was a success, yes. I=E2=80=99d like to see t= hat built upon so=20 we have many more like that. --=20 Aaron J. Seigo --nextPart45924813.UmfCk9zaAc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iEYEABECAAYFAlIWmlEACgkQ1rcusafx20P8mACcCqY+5b5YbWDUfSwuBct5+vmo HnIAn1BzE+v6DNTyaIPaWAecJGiD7cEl =RdBR -----END PGP SIGNATURE----- --nextPart45924813.UmfCk9zaAc-- --===============6577225909516136032== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community --===============6577225909516136032==--