--nextPart3751296.LEvlXTyPlv Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Hello lists, First of all, I'd like to apologize to everyone here as (so far) I didn= 't live=20 up to previous commitments made. Indeed, shortly after Platform 11, I=20= identified that the road the KDE Platform to the KDE Frameworks would r= equire=20 focused stewardship in a way we didn't need before. I volunteered to do= the=20 job, but due to my life outside of KDE Frameworks, I felt short on the=20= organization and communication which needed to be put in place. That is= partly=20 why the effort is perceived to be stagnating, is not moving as quickly = as it=20 could, why kde-frameworks-devel never got announced properly (understan= dably=20 leading to some conspiracy theories), and why everyone is wondering whe= n?=20 (although I'm not going to provide an answer to that). Now it turns out the planets are almost aligned correctly now for me to= resume=20 the efforts and as such I'm back to work on KDE Frameworks. While I wil= l be=20 doing some coding on frameworks (I'm an addict!), the main way I will b= e=20 contributing is to tackle the general stewardship and communication of = KDE=20 frameworks. Now, let me introduce the two major assets which got created to organiz= e the=20 KDE Frameworks development. =3D kde-frameworks-devel@kde.org =3D At last, we're announcing properly the creation of kde-frameworks- devel@kde.org! This list was created mainly to drive the efforts of the= =20 creation of KDE Frameworks. A separate channel of communication was cho= sen to=20 avoid some of the signal/noise shortcomings of kde-core-devel, can't re= ally be=20 denied... But it is also here to avoid disrupting kde-core-devel day to= day=20 operation regarding kdelibs. For now, it should really be seen as similar in its birth to our releas= e-team=20 list. Except that instead of cross-teams release topics, it's right now= =20 focusing on KDE Frameworks specific coordination and organization for i= ts=20 first release. It is what it has been used for so far and not more. Which means people= are=20 sharing tips or seeking solutions when some dependency change is needed= . Those=20 tips will get over time consolidated in the community wiki (more on tha= t=20 below). Will kde-frameworks-devel stay around after KDE Frameworks 5.0 is relea= sed?=20 Hard to tell for now, we will see how the customs evolved around the ti= me of=20 release and decide based on that. My gut feeling is that long term kde-= core- devel will stay around for patch reviews and day to day feature level=20= operations and interaction with the broader community (where plasma mee= t=20 dolphin for instance), while kde-frameworks-devel will be more about lo= nger=20 term planning and design across the whole KDE Frameworks offering. But = again,=20 that's pure conjecture at that point and we shouldn't set it in stone. Both are needed for now, let's see how it evolves. For now I'm trying t= o make=20 sure the important information will be relayed to both mailing lists, w= hich=20 means in the short term I'll simply cross-post (first example right now= ), and=20 over time we'll move toward a bi-monthly or weekly digest of what's goi= ng on=20 in KDE Frameworks to be sent on kde-core-devel. =3D community.kde.org/Frameworks =3D Let me introduce now what I consider the most important resource to the= =20 service of the community to reach the KDE Frameworks 5.0 landmark: the=20= Frameworks area in the community.kde.org wiki! Its main purpose is to give an idea of the on-going efforts in KDE Fram= eworks=20 land. It's very oriented into communicating and driving work, it also c= ontains=20 the policies in place. For now because of KDE Frameworks status it focu= ses=20 almost exclusively on the transversal issues, but at some point we'll a= lso=20 open per-framework sections. If you look at the wiki right now you will see only three transversal e= fforts=20 (named epics later on) which are active, they are the critical ones for= a KDE=20 Frameworks 5.0 release, none of the other ones are scheduled yet. They'= re nice=20 to have but not essential to a release. Also you will see that the intent of this section is not to focus exclu= sively=20 on "producing libraries", I want a whole product approach to KDE Framew= orks=20 because that's one of the clear outcomes of the Platform 11 discussions= which=20 touched more than just kdelibs in the end (leading to the creation of i= nqlude,=20 discussions on a broader developer story, etc.). So KDE Frameworks as a= =20 product will be about more than just library development and API design= even=20 if it is a very important aspect of it obviously. Of course, it is supposed to be a living document, it's still young and= =20 probably not complete yet. That said it already helped a lot into uncov= ering=20 some precious information which were buried in meeting notes or giving = a=20 clearer picture on where we stand and what we need to reach our goals. In fact, I'd like to point out the obvious result of collecting data in= the=20 wiki: we need more hands to help moving things forward code-wise, we al= so need=20 more people volunteering to act as framework maintainers. One of the=20= consequences of KDE Frameworks 5.0 is that it will be easier to act as = such=20 because of the more modular nature (it's one case of technical change=20= impacting the social structure). It makes obvious the lack of responsib= ility=20 in most of kdecore, kdeui and a few others libraries which have instead= the=20 "David Faure as fallback maintainer" mechanism which we shouldn't rely = on=20 anymore. You want fame and help the community at large? Here is your chance! It = can be=20 a tough job, but very rewarding in my opinion, most of the KDE products= use=20 kdelibs and will use the KDE Frameworks in the future. =3D=3D Now at that point some of you might still wonder about when will we hav= e a KDE=20 Frameworks 5.0? My reply would be that a) it will be after Qt 5.0, so f= irst=20 ask the Qt project when they will release and b) when it is ready. :-) Now jokes aside, there's some things we cannot avoid before making a 5.= 0=20 release, and those are the three epics I selected for this milestone. S= till, I=20 strongly believe in regular releases and I'll push for them to happen a= s soon=20 as we're in a position to have them, they will be alphas for a while of= =20 course. The exact rythm is something I don't want to force on the Frame= works=20 maintainers, and I hope to build consensus on that during tomorrow's IR= C=20 meeting (which results will be relayed on mailing-lists). Thanks for your attention, now let's focus on preparing a great KDE Fra= meworks=20 5.0 release! Regards. --=20 K=E9vin Ottens, http://ervin.ipsquad.net KDAB - proud patron of KDE, http://www.kdab.com --nextPart3751296.LEvlXTyPlv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEABECAAYFAk7ahycACgkQB0u7y43syeJwSQCgo/UcyEor65/f8GoV/bCooT0s oBYAoJIfK09N+kL1NQOalDahq8X63HVv =mW50 -----END PGP SIGNATURE----- --nextPart3751296.LEvlXTyPlv--