--===============1353477582907491870==
Content-Type: multipart/signed; boundary="nextPart14980694.gE2NANfKAG"; micalg="pgp-sha1"; protocol="application/pgp-signature"


--nextPart14980694.gE2NANfKAG
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

On Tuesday 18 February 2014 14:40:27 Aaron J. Seigo wrote:
> On Monday, February 17, 2014 16:50:17 Jens Reuterberg wrote:
> > So whatever we do have to be done quickly, decided even faster and
> > implemented by all. Which is the nasty bit. The upside with Plasma =
Next
> > is
> > that there actually is a real chance to rebrand things and that can=
 spill
> > over to other areas (Like Frameworks).
> >=20
> > The downside is that if we do that then the tie between
> > KDE/Frameworks/Plasma will get even stronger... so its not a total
> > victory
> > or anything.
>=20
> Getting visual unity for Plasma is already a big project to tackle, a=
nd
> given the fundamentally different audiences for Frameworks and Plasma=

> getting something that works for both is a big ask.
>=20
> As you note, having something that is fundamentally the same for both=

> Frameworks and Plasma would create a stronger visual tie between them=
 which
> is the opposite goal we started out to achieve.
>=20
> But there=E2=80=99s a way forward, I think: Frameworks does not requi=
re the same
> kind of marketing push that Plasma does. The desktop shell(s) is some=
thing
> of a flagship product for KDE and it is *very* public facing and alre=
ady
> has an existing public identity.
>=20
> Frameworks, by contrast, is new as a stand-alone product. Its marketi=
ng
> needs to focus not on general public but developers. It has little to=
 no
> user visible visual identity. So it is possible to get away with a
> =E2=80=98weaker=E2=80=99 branding for it and work it into strong shap=
e later on.
>=20
> So if you focus the scope of these efforts on just Plasma and forget =
about
> Frameworks for now, that will allow people to make the most of the ti=
me
> frame we do have without an overly large scope.
>=20
> Plasma may even consider scheduling its release in part around when t=
he
> Plasma branding is ready and implemented so that it can be completed.=
 This
> would allow the branding to work more effectively on first release. T=
his
> is not something we=E2=80=99ve done in the past, but would probably b=
e a useful
> improvement. Obviously, this alignment of release-to-branding is not
> something that needs doing with every incremental release; it probabl=
y
> only makes sense on major releases such as the upcoming Qt5/KF5 based=

> effort.

+1
--nextPart14980694.gE2NANfKAG
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.22 (GNU/Linux)

iEYEABECAAYFAlMDvw4ACgkQ+wgQ1AD35iw6jACgwEB0dVD8hVBcVTK5e1blrh1u
qOkAoMiIIwRfM05uxFmDGMbXGc80igBd
=hW4b
-----END PGP SIGNATURE-----

--nextPart14980694.gE2NANfKAG--


--===============1353477582907491870==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


_______________________________________________
This message is from the kde-promo mailing list.

Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.
--===============1353477582907491870==--