[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-promo
Subject:    Re: Helping to clarify Promo scope & reponsibilities
From:       Aleix Pol <aleixpol () kde ! org>
Date:       2019-10-23 12:44:42
Message-ID: CACcA1RohfcHtyC+uWUVRZcHrirC09ZF55+QvJ16-mgpD+500Fg () mail ! gmail ! com
[Download RAW message or body]

On Wed, Oct 23, 2019 at 12:40 PM Roman Gilg <subdiff@gmail.com> wrote:
>
> On Wed, Oct 23, 2019 at 12:06 PM Eike Hein <hein@kde.org> wrote:
> >
> > Hi everyone,
> >
> > It's become clear that from time to time, uncertainty about the exact r=
esponsibilities and work scope of the Promo community rears its head, leadi=
ng to tension. An example is the communication around QtWS'19 earlier this =
week.
> >
> > Within KDE e.V., we've recently tried out a process to solve very simil=
ar problems around the e.V.'s working groups, which are similar to Promo in=
 that they form domain teams that work within a larger community. The e.V. =
Board is meeting with each working group to discuss questions around what t=
he working group is responsible for, what it isn't responsible for, reporti=
ng formats and a few other things. We've done this with several of the work=
ing groups now and the first results are very promising and leading to much=
 improved clarity (they'll eventually be worked into the e.V. website).
> >
> > We would like to help by applying the same process to KDE Promo and the=
n informing everybody about the results. This is not entirely pro-active fr=
om our side, as Promo, in particular Paul, have already asked us to do this=
.
> >
> > We'll be getting in touch with Promo soon about the details and coordin=
ating a meeting/call time.
> >
> >
> > Cheers,
> > Eike
> > -
> > KDE e.V. vice president, treasurer
> > Plasma, apps hacker
>
> Hi Eike,
>
> thanks for taking action. I support this clarification effort.
>
> It would be good to clarify in particular the responsibilities and
> authority of our paid contractors in relation to other community
> members of the Promo group.
>
> Are they "coordinators" in the sense that we can count on them
> managing Promo resources and processes and facilitating contact
> between Promo group members and other community members?
>
> Do they have rights different from other Promo community members in
> relation to our marketing resources? As far as I know yes, when
> thinking about online logins to Twitter and so on. Is there then a
> process defined to allow other members to acquire these rights such
> that they can help with this ground work and enable contractors again
> to do the coordination part (assuming that this is their
> responsibility to begin with).
>
> The Promo group behaves a bit different from other groups. Clarifying
> the scope & responsibility needs to look at both, paid contractors and
> the Promo community members while other groups normally only have
> community members.

Hi Roman,
I don't understand why you keep using this overly sarcastic and
confronting tone. It hurts all people involved and doesn't solve
anything.

I have the feeling you're asking things that have been discussed over
exhaustion in the past. Maybe the answer doesn't satisfy you but it's
the truth:
The marketing contractors don't have to coordinate. They were hired to
revive KDE's promotional initiatives that were fairly dormant when
they started. From this moment on, they're people who are contracted N
hours to work on KDE promotional subjects. The fact that they ended up
coordinating some tasks was just because there was little to no
structure.

Does KDE Promo really work differently than the rest of KDE or you
just picture it to work differently so it will serve your purpose?
If you ask me, paid contractors can't be looked at different to the
rest of community members. They are people like the rest of us who are
special in that their time is allocated onto the community.
For what it's worth, should we even build KDE Promo around the fact
that there's people paid to work on it who have a special status? I
don't think so.

Aleix
[prev in list] [next in list] [prev in thread] [next in thread]