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

List:       kde-promo
Subject:    Re: [kde-promo] [dot] KDE Frameworks 5.2.0 release
From:       David Faure <faure () kde ! org>
Date:       2014-09-11 21:00:15
Message-ID: 1606780.trZ64CZxEq () asterix
[Download RAW message or body]

On Thursday 11 September 2014 12:10:39 Carl Symons wrote:
> Your response made me think of this in more depth. I think that your 
> take on it is correct. The announcements about the frequent releases 
> should be tailored to developers.
> 
> Jos has been pushing promotion of Frameworks 5 and the KDE/Qt 
> relationship. This topic has more to do with developers than users. It's 
> trivial to tell users that, for example, they won't be bothered by 
> missing default shortcuts. We should have a different storyline for 
> users...maybe something more conceptual and over a longer period of time 
> that the release cycles.
> 
> Further to your point, developers are more likely to see the value in 
> the individual improvements, and more often than not, they are earning 
> money with their work. So this is a better avenue to sponsorships and 
> fundraising than trying to get individual users to pony up for the value 
> they receive.

Agreed.

Now more concretely, what do you suggest we do at each release, and who does 
what?

E.g. can someone write info/kde-frameworks-5.2.0.php
based on the input I gave, or shall I do my own thing there as fallback (won't 
be as good but better than nothing) ?

I see there's also announcements/kde-frameworks-5.2.php
and then kde-announce@. I would also add kde-core-devel@.
I think it was said that a dot story is fine too, and then there's social 
media.
My question is: are we doing all this every month, and is there a volunteer 
for doing it?

-- 
David Faure, faure@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5


_______________________________________________
This message is from the kde-promo mailing list.

Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on \
or temporarily stop your subscription.


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