From kde-promo Wed Oct 23 10:05:44 2019 From: Eike Hein Date: Wed, 23 Oct 2019 10:05:44 +0000 To: kde-promo Subject: Helping to clarify Promo scope & reponsibilities Message-Id: <164AB119-501E-40F2-AAF6-45AD3955DA53 () kde ! org> X-MARC-Message: https://marc.info/?l=kde-promo&m=157182516228243 MIME-Version: 1 Content-Type: multipart/mixed; boundary="------E5GJUVE7U8OV61H4RJQY0XYKOAE87J" ------E5GJUVE7U8OV61H4RJQY0XYKOAE87J Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi everyone, It's become clear that from time to time, uncertainty about the exact resp= onsibilities and work scope of the Promo community rears its head, leading = to tension=2E An example is the communication around QtWS'19 earlier this w= eek=2E Within KDE e=2EV=2E, we've recently tried out a process to solve very simi= lar problems around the e=2EV=2E's working groups, which are similar to Pro= mo in that they form domain teams that work within a larger community=2E Th= e e=2EV=2E Board is meeting with each working group to discuss questions ar= ound what the working group is responsible for, what it isn't responsible f= or, reporting formats and a few other things=2E We've done this with severa= l of the working groups now and the first results are very promising and le= ading to much improved clarity (they'll eventually be worked into the e=2EV= =2E website)=2E We would like to help by applying the same process to KDE Promo and then i= nforming everybody about the results=2E This is not entirely pro-active fro= m our side, as Promo, in particular Paul, have already asked us to do this= =2E We'll be getting in touch with Promo soon about the details and coordinati= ng a meeting/call time=2E Cheers, Eike - KDE e=2EV=2E vice president, treasurer Plasma, apps hacker ------E5GJUVE7U8OV61H4RJQY0XYKOAE87J Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi everyone,

It's become clear that from time to time, uncertainty a= bout the exact responsibilities and work scope of the Promo community rears= its head, leading to tension=2E An example is the communication around QtW= S'19 earlier this week=2E

Within KDE e=2EV=2E, we've recently tried = out a process to solve very similar problems around the e=2EV=2E's working = groups, which are similar to Promo in that they form domain teams that work= within a larger community=2E The e=2EV=2E Board is meeting with each worki= ng group to discuss questions around what the working group is responsible = for, what it isn't responsible for, reporting formats and a few other thing= s=2E We've done this with several of the working groups now and the first r= esults are very promising and leading to much improved clarity (they'll eve= ntually be worked into the e=2EV=2E website)=2E

We would like to hel= p by applying the same process to KDE Promo and then informing everybody ab= out the results=2E This is not entirely pro-active from our side, as Promo,= in particular Paul, have already asked us to do this=2E

We'll be ge= tting in touch with Promo soon about the details and coordinating a meeting= /call time=2E


Cheers,
Eike
-
KDE e=2EV=2E vice presiden= t, treasurer
Plasma, apps hacker ------E5GJUVE7U8OV61H4RJQY0XYKOAE87J--