Re: Yet unannounced Plasma TV UI project

Carl Schwan <[email protected]> Mon, 23 Mar 2020 16:24:38 +0000

Newsgroups	gmane.comp.kde.events
Message-ID	<RZmaYWFdx0vRB8pHsllMSP4Fhv-k9-zkR-mhQ1is2xkya-uv5Qj8d9QcNtTwGXdnhJfPaX53sNz4ogeK5qCSqiiW9pl51pJR7s9skwM1H1Y=@carlschwan.eu>

Hi,
Le lundi, mars 23, 2020 3:51 PM, Eike Hein <[email protected]> a écrit :

> Hi,
> 

> > as the product itself is not ready for release
> 

> I would agree.
> 

> Just from a cursory look:
> 

> -   The proposed Plasma Bigscreen website links to a not-KDE company bug tracker for issue tracking and not-KDE forums.
> -   It's not clear to me where this website is hosted and whether it's been aligned with KDE's WWW team, who have worked hard in recent months to make our websites more consistent. Collaboration would I think be welcome there, especially for a satellite project to an existing community brand (Plasma).

It isn't hosted on KDE infrastrucure, otherwise it would have at least been using https. #kde-www wasn't contacted and I was unaware of the website existence until yesterday. In term of the websites, I'm a bit disapointed that we have now three Plasma products with a website and each website use a completely different themes. See https://kde.org/plasma-desktop, https://plasma-mobile.org and http://plasma-bigscreen.org/.

> -   From a product marketing POV, I'm surprised at the proposed announcement text calling out "Plasma Nano" as the thing for embedded Plasma development. I'm not aware of a conversation where it was established that Plasma needs a sub-brand for embedded (brand != code bits; saying you need something called Plasma Nano for embedded makes Plasma un-embedded). It invites questions I don't see prep for - Plasma Nano has no website or FAQ anywhere.

There was some discussion about the Plasma Nano brand here: https://phabricator.kde.org/T10597 but I see that this discussion didn't include the Plasma team :/

Cheers,
Carl

> -   Between the website and the announcement, there's a concept of "Bigscreen Apps" enabled by a distinct API set from Plasma's APIs (the Mycroft APIs). This also has implications and begs questions - is the Plasma API set (we've used terms like "mini-apps" for Plasma widgets before) insufficient for this use case? Why? This may have pragmatic answers related to integrating two technologies, but those answers need to be written out or they dilute messaging around the Plasma brand
> -   On the Telemetry/Privacy front it's a similar story of "at the very least, have the answers ready". We have other projects that depend on Google APIs (e.g. kio-gdrive), but they need less careful communication as they're inherently tied to Google products/brands. With something like the Bigscreen case it needs a message how this related to the Telemetry policy and what mitigations are there (e.g. an architecture not tied to those APIs and allowing for other backends).
>     

>     This all feels a bit hodge-podge and very rushed. My suggestion would be that instead of taking the project to the public under the KDE mantle as very first step, this needs a starter period of being introduced to the KDE/Plasma community and for the community to decide whether it wants to embrace it (or can embrace it - the announcement cites Mycroft as a participant, but the divison of governance is unclear to me) and help develop a product narrative around it that appears to incomplete-to-missing.
>     

>     Cheers,
>     Eike
>     

>     March 23, 2020 4:18 PM, "Paul Brown" [email protected] wrote:
>     

> 

> > Hello,
> > As it turns out, the discussion about the name of the product is premature at
> > this moment, as the product itself is not ready for release, at least not
> > officially as a KDE product, with its dot article and posts through the official
> > KDE social media accounts.
> > The product uses proprietary Google technology so, as it stands, it would not
> > pass the FLOSS smell test and can be seen by people outside our orbit as a
> > front-end to Google spyware.
> > We already had quite a bit of (unjustified) negative press regarding the
> > telemetry options shipped with 5.18. If we make an official announcement about
> > this product now, it would be further proof for the anti-KDE crowd that we are
> > sliding down the slippery slope of spying on our users.
> > My recommendation is this: the developers make it a blog post, the blog post
> > can go through the planet and Promo can echo it, re-tweet it, boost it, or
> > whatever, explaining that this is a project that is WiP. This will still
> > attract the intention of users and companies who are interested in these kind
> > of things.
> > I would also recommend that the blog post include the information about the
> > Google back-end explicitly and clearly, explaining how this is a temporary
> > solution, and information about how developers intend to solve this problem
> > down the line.
> > When the product manages to remove the Google back-end and uses, for example,
> > Mozilla's voice data, we can confidently make an official announcement via KDE's
> > own outlets and not have to put up with any blowback.
> > Cheers
> > 

> > Paul
> > 

> > -----
> > 

> > Promotion & Communication
> > www: http://kde.org
> > Mastodon: https://mastodon.technology/@kde
> > Facebook: https://www.facebook.com/kde/
> > Twitter: https://twitter.com/kdecommunity
> > LinkedIn: https://www.linkedin.com/company/kde
> 

> Best regards,
> Eike Hein
> 

> --------------------------
> 

> KDE e.V. vice president, treasurer

publickey - [email protected] - 0x7F564CB5.asc (application/pgp-keys, 3.1 KB)

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: OpenPGP.js v4.10.1
Comment: https://openpgpjs.org

xsFNBFxVsQgBEAC1ojOPmZkM0UKXNWXYq1eNZeJh9nj8tYVNBDDBoXyyq+HC
Qfw7R51Al2VSZYeMNLT4d1kFzGB4tjx3CcgAyCwHHzYP5Ys69leArgP9Hs0E
lcJsoM//BRG8YIrypOwujRmVeIb7r60mzlhEVpWephWB1O5yKUBcxrLjFSRz
SQD4O3iiJxGxavM6A1f3DgNfjih2nWtGJXLJOzWFU8bYqDnwbByFQMdm7KQl
njjrRN3Fl+vC6tILcUJ55mUF8Wry5Ah0fE+RsB+47KT3uAaDbFsp6lgmNE/Y
1yP2TDMZoAsJx/mlRD572dRz87fTcraxhwiCPTEq5w3IN1QzYj0S+g6xFgRK
RGlY4Hm/NF9Oa/cLsCVrr893OdwIgXDvrmA9+sAFdPIO4eBX9ctLYV+p+B9X
A9Kt0nJC18hC8BrOz9nmTq6RGsgvxRMYkiTzFZx/mXjndl4L2wwatoXAMuah
lfYuubKyGD2xfNYPFqh4iqMLMc/pfk6esy7PTy77PTmJVyegRD1ObUrF8OPg
1zXL0ctqvt+PXwnYh/IfDN6MytjLBUvR/38d6NA2+8Vbb0gLZHwa8aT5r1LR
ab5ELDlamx27NG8z8PnGB8twmCDBFudF91dlRcVqK5mpUep0nvTdu4daxl88
m+pt4CbPS0vstvszIH6UBWk6U+hlKomEqrvfwQARAQABzSkiY2FybEBjYXJs
c2Nod2FuLmV1IiA8Y2FybEBjYXJsc2Nod2FuLmV1PsLBdQQQAQgAHwUCXFWx
CAYLCQcIAwIEFQgKAgMWAgECGQECGwMCHgEACgkQATBHGy6kioOasQ/+L3GN
WOsjayYMkqZMYv2W8LABL/NboAgAQyghYsGlVAtUvt/s1ike42Kuu9FKV4PQ
z6jDtz3IoO26sw/ZqGPeZKarjfSb9Pvc3czh1ewsdPf3/9AJKrRPCLrlytvN
iz/P9Pb29iSE0Pd1yOaJyt7O8OkWHXmvqXU6eDgeYC1b9ajCmiyCtNSc7WQi
jcRUFKDF2sMje5pNHSEZVHZsrax4Zmg0o7j2cHg85MYFOPIn4DCCBoBz1EOu
37Fw6DSNxF66r2wlKe6UALgZ2IEi3tdvG4vmk1meZT3m5helxIdZW/2O0ggE
O9zv53OTfla2yorEPRr/rhyI5E4UegP+YjBtcIm++e7Mfmd9MtO25B+Cebip
W+ZOjWgj1N/j7X9F3A0GBZXafq7rZdCjh6ppEMdFc7bljsIYXF7tNQ9vu/6h
o40hXiRMzlqdz0uPUojmIKO8tkaS5HzJgWlM9/3m8h7x5C8JTZsXbKi4uZsp
0Hw6F14fS1/qgV0qVmJybuvzL+yXGp/oWsCBXyfl5wRvW0ZZvHku5uczELvV
uEwbqbkKxPc8oggEG5vGNSqlCsxje4pJ4fllqBRU4r3UZtK9/OkbizPdZYEa
OZqSYAaXqnJXq9aEWyoTq7eHPzXGDLs9U6rdqpG5voPyQcrftnej1OLxbLvP
Dz8VCu8I7HA58ti2DIbOwU0EXFWxCAEQAM1fva8niljpZrhIYgAfIIsjrAOt
DoTH51hCWyZFFR13nbljN/KrnQFc4JHN1Vhm1h7Mxg7/jvLCw8uuvhGVJoqn
QWuAhWF3Q/ZkiYqDFr3wTfRB3xJNlZSu0X4CYyGyG2g8OLfhWJuMd4zPyxuw
aZTRNSVXPNbk6ndCoIX7ZVmLAJlW7ujjErYL2xJt+tE5PVRDC0l6MCWCh+ht
v86Pp1GM2pc5vIMDOHlWqAMYKt2KtQTut/E/whtwPLGU7QP6/Kd5JUY4vxew
9BufsYPHDeqS+gfBo+lBovvA1kfszmbRYVO7RJsuJTqgGKwAYvVGSY6Th5Cu
EPNnRdvGL6JFBa+6S3yFoSYFirMZaYUThSxBXCiafqOjcZ1Q7Wf4T/rvZgbX
J8z2Yf8JVtEOHBqxVzdhfscmNGfjRi/AwokRctlE4DIdY+9Z5ffJSTHWzF8N
iM/S1kAx3tK6QYqTbGYloZctRahbNqyijGYwXT/n84RhaWaaaeBBGKioqViH
YHFxGAkGZtz4VOgkg6K0NTg0uh+crfvoAm+G13WK2jK1U+s6KE/PWccN0xV/
g1qTokmEhjh815EgbPTCrz4aZp6NCSfcYVasURAu3WFWWIVjRQJ7Owv8qy+w
5bnXSKFUGoVUNJDndFblNelUKz+tRQXCeVNDaf/W224y1dn3OQn9po0ZABEB
AAHCwV8EGAEIAAkFAlxVsQgCGwwACgkQATBHGy6kioNffxAArUWDrFrUaRaI
q+fU7P7pX4OvP8Tz+2auoZ5eiw7f98JuxD4cXkq4fGDXHSJNvAMkp4vYJRNb
IfOzrrpkj0haDlY4FZrsuxaAhgR/DfYwhtGqG+8G1thd0zY9UNfCnc8AM7vD
xZatPRxJ8WrTYtwaSebeFP6f8KxeFo8Sc/L2Gs6JsbczYQl3oeDWX8HFYSuB
Vr7pYq3XTiTmqex13/IpFA33AacgwklqDrSa3zFMye2wFGDmskZcXil6y6pv
73AKjZ9xt3GRbWJ8ui1XY1zsSPnT3yaaywVDl7Z3GSgB/FhLsYMo99laMW9x
ho3nmS++fcAw9IOi1wIt9xqBBbqnFkYRKqi2HP9T7JgWn0y3vivGq4qW8pQk
LXXFiZohaY8RDpNRMKH2/AEFkGP1mxGIZ/LE7qKRFeix7w5dPIIsjOVfpdkO
JLgkF7bNfaly1wO7KchOQD9KJMll7USyZBgUP4f3gpplLXrzlTFlq/wXPJFb
6XkR6yGU0AHqZiNArgM7/qKj3B6ZP/qPqmm6PPBEENe2hdd1Ney1ut5E0gYv
fJCPCn1/Q7Hhie+TXHC7cIJHggjBjDypxP+TvgNeGnUqpFlikiEox8DjVdQJ
HNsk2fPVhxdGcJlexh0oxfgmSpLrIcVJHCQ4TIn7nFJLZw00jA9M9KkRWeXG
z/19LtJQ/1c=
=aByX
-----END PGP PUBLIC KEY BLOCK-----

signature.asc (application/pgp-signature, 823 B)