--===============0669806455== Content-Type: multipart/signed; boundary="nextPart1639468.UYgT5djpJK"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1639468.UYgT5djpJK Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sunday, December 26, 2010, Martin Gr=C3=A4=C3=9Flin wrote: > let me break the Christmas silence by writing a long post about the curre= nt > state of KWin and where we are heading towards in 2011. As this also is thanks for sharing; these kind of "look ahead" communications are so useful= to=20 ensuring things stay on track and to encourage renewed energy and commitmen= t.=20 so: thanks :) > Sorry that it is that long. compared to my average "where we are" emails, you are a study in brevity an= d=20 clarity. ;) =20 > *Plasma and KWin* > I consider Plasma and KWin as the integrated product of the KDE workspace= s. > Both products depend on each other and do not make much sense without the > other. i'd word this slightly differently: they make the most sense when used=20 together, and we shouldn't be afraid to get more benefits out of that=20 relationship. i do think it makes complete sense to use kwin without plasma-desktop, and= =20 plasma-desktop without kwin. i also think that when people do that, it's=20 acceptable that there will be a degredation of features. the basics should = all=20 still work, something that will keep us honest as developers and not start= =20 taking shortcuts that violate principles of encapsulation and focus, but i = am=20 completely fine with the idea of charging ahead with great integration to=20 bring all the really great features we can imagine to the front. > This is also reflected when looking at our developer base: we have > almost a 100 percent match. We currently see great improvements on the > syncing of our working procedures. Using reviewboard, having common > processes for git and so on. I hope with the switch to kdelibs coding > style (scheduled for directly after import of KWin-GLES) and removing bug > mails for KWin mailinglist to have improved the situation for Plasma devs. this all fills me with great hope for the future of our projects. this is s= o=20 obviously the best path we can hope for and it is so great that we have fou= nd=20 ourselves a way to get onto it. :) > If there is anything from a Plasma perspective to improve it even more, > please let me know, I am open to all suggestions. and the other way around from the plasma perspective, too. having the input= of=20 kwin on plasma is just as valuable to us as hopefully our input is to kwin.= :) > *GSoC* you're going through the same pains we have in plasma and reaching very=20 similar conclusions :) i think it's useful to have a few speculative projec= ts,=20 but keep most of them focused, building on what's already there and with=20 people who have had some interface with the project already. > *Manpower* > Manpower is in my opinion the biggest problem of KWin. We are just three > developers + Chani and Ivan working on activity related code. I would like > to get more Plasma developers working on KWin. It should be a natural > thing to touch KWin code and to add new features in KWin if it makes > sense. Here I would like to know from the developers sometimes working on > KWin what needs to be improved.=20 from my perspective, it's all the things you already touched on: modularity= so=20 it's easy to get moving, code readability (i find the current style very=20 difficult to read, tbh) and in some places documentation (even just basic=20 outlines, hand holding isn't strictly necessary :) > Where are things missing to grab the code more easily. we really need projects.kde.org to ship xml descriptions and for those to b= e=20 referencable from kdesrc-build. once we have that, we can bang the drums=20 repeatedly to the testing+developers audience about how easy it is to get a= =20 KDE build up and running. that remains one of the most daunting tasks to da= te. > I am currently trying to recruit a new developer and I would like to see i have found that the easiest (though not necessarily "easy" ;) way to do t= his=20 is to have an intriguing story for people which gets them interested and a = set=20 of concrete tasks they can dive right into. we could as a combined kdebase- workspace dev community start in on a subtle developer recruitment campaign= in=20 our blogs and elsewhere in 2011. we all need more and new blood :) > With Wayland many things have to be moved into the compositor, like what's > today kdm, screensavers, etc etc. So we really need to get Plasma devs > starting working on KWin ;-) before we hit kdm and screensavers (widening the scope even further), i'd l= ike=20 to see us get our plasma-desktop house in order. the presentation of the=20 dashboard and wallpapers, screen edge handling and effects (e.g. the panel= =20 glow), etc. we've done great work to date with pushing more and more into=20 kwin, but we have a few remaining "great ideas, just shouldn't be in the=20 plasma shell" features :) =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 Development Frameworks --nextPart1639468.UYgT5djpJK Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEABECAAYFAk0XiTMACgkQ1rcusafx20O6gQCeK6oQ1zTjRa9NKN7LA+oLvI/9 HtQAnAyst13PEE/l+QYlWmT9s7Ce0mQs =mPsK -----END PGP SIGNATURE----- --nextPart1639468.UYgT5djpJK-- --===============0669806455== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kwin mailing list kwin@kde.org https://mail.kde.org/mailman/listinfo/kwin --===============0669806455==--