From kde-core-devel Fri Mar 13 16:45:04 2009 From: "Aaron J. Seigo" Date: Fri, 13 Mar 2009 16:45:04 +0000 To: kde-core-devel Subject: Re: Fullscreen interfaces Message-Id: <200903131045.07547.aseigo () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=123696274410126 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart3192911.3xAeT0H43P" --nextPart3192911.3xAeT0H43P Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Friday 13 March 2009, Torsten Rahn wrote: > > actually benefit the user experience in any way, it would be brilliant = if > > you could participate, utilize and help spread the results. > > Sorry, I'm busy enough to do the same for Marble. then who am i writing this document for? if you aren't going to use it or=20 spread it around, who will? why should i bother? i agree with you that coordination is great, communication is terrific and = we=20 should aim for a coherent set of results. what i fail to see is where there is that desire for coherency when we face= =20 criticism for doing exactly that (see this thread and the other one about=20 kcm's in workspace using the monitor preview widget) and how we will go fro= m=20 "here, i've documented it" to "ok, now we're coordinating" when we have no= =20 commitment nor process in place to take those documents and do something=20 meaningful with them. i see no point in spending my time writing something that won't be used.=20 people love to ask for stuff that they then just ignore later because they= =20 really didn't actually have any plans for it in the first place. so before i give you (and the others in this thread) what you want, i'm mak= ing=20 some simple requests in return as a pre-condition, namely: make some=20 commitment to a set of processes that stand a chance in producing results=20 we'll all be proud of. that means defining those processes, and then committing to them. as a star= t,=20 it would be nice if we: * posted these documents on techbase with one page pointing to all of them * actually read the relevant bits * commented / got involved with clarifying the bits that are important to o= ur=20 projects and direct interests, but only those bits if that's not a realistic set of commitments you can make, there's really n= o=20 point in spending my time placating you by writing long documents and keepi= ng=20 them up to date. > > this particular bit of your email also borders on "let's start a general > > bitch fest about anything we don't like, understand or get about plasma > > and any code around that project". > > There's no bitching involved (I would have kept it less constructive and > would have added sarcasm and irony otherwise). And I don't have a reason = to > bitch as I like much of the plasma development. > > I only tried to express where I think Plasma urgently and critically needs > to improve my simple request is to keep this thread focused on one issue, and hopefull= y=20 the issue relevant to kde-core-devel. everything else should go into separate threads on the correct mailing list= s. > > please don't throw around terms like "map in the spatial memory" unless > > you're prepared to offer some actual evidence to the fact that we are > > talking about spatial memory, mapping, etc. > > That is trivial to show - especially once a user got lost in one of the > virtual desktops of his activities (or was it the other way around?) and > asks himself "WHERE the hell did I put this window -- or was it a plasmoid > ... ?" find me on irc and we can talk about this. i don't think you understood wha= t i=20 wrote, which may be because i wrote it in an unclear manner or we're simply= =20 talking about something from different perspectives. either way, it doesn't= =20 belong in this thread, but i'm happy to discuss it elsewhere in an appropri= ate=20 context so that we can sort it out. =2D-=20 Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software --nextPart3192911.3xAeT0H43P Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAkm6jZMACgkQ1rcusafx20PCZgCeItw72cVTZu1QXtfdIPyImzfW 4p8Ani9sptP0hbbaRbiOjEQ8+P3QaTLo =sFM9 -----END PGP SIGNATURE----- --nextPart3192911.3xAeT0H43P--