[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-promo
Subject: Re: [kde-promo] Changing how we market the workspace
From: "Jos Poortvliet" <jospoortvliet () gmail ! com>
Date: 2008-10-16 17:30:59
Message-ID: 5847e5cf0810161030h77db5827o4e2445a9e4a648b () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Thu, Oct 16, 2008 at 7:09 PM, Aaron J. Seigo <aseigo@kde.org> wrote:
> On Thursday 16 October 2008, Jos Poortvliet wrote:
> > No, it's a great idea, and I've tried it a couple of times - keeping the
> > wiki page with new stuff and all, so writing the alpha and beta
> > anouncements was fast and easy. Later, I didn't have much time left, and
>
> perhaps we should also shift some resources away from alpha/beta
> announcements
> and invest more heavily into final announcements?
>
> a simple boilerplate announcement for alpha/beta with a few notes about big
> 'n
> obvious stuff (just cherry pick from recent commit digests?) would probably
> suffice.
>
> i mean, this is very impressive and makes sense given the dynamics around
> 4.1:
>
> http://www.kde.org/announcements/announce-4.1-beta1.php
> http://dot.kde.org/1211898836/
> http://www.kde.org/info/4.0.80.php
>
> but if we keep future beta announcements simpler and invested that effort
> into
> final announcements, maybe we could afford to do more with them and spread
> it
> out over a greater period of time by working on the final announcement all
> through the alphas/betas and limiting the resources put into alpha/beta
> announcements.
>
> thoughts?
Nothing wrong with that. And it essentially just takes one good day of hard
work to get it (mostly) right. For me, working on it 30 min/1 hour a day
(after work) doesn't really work, so it comes down to weekends - I'll try :D
>
>
> --
> 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 Software
>
>
>
> _______________________________________________
> 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.
>
[Attachment #5 (text/html)]
<div dir="ltr">On Thu, Oct 16, 2008 at 7:09 PM, Aaron J. Seigo <span dir="ltr"><<a \
href="mailto:aseigo@kde.org">aseigo@kde.org</a>></span> wrote:<br><div \
class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid \
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div \
class="Ih2E3d">On Thursday 16 October 2008, Jos Poortvliet wrote:<br> </div><div \
class="Ih2E3d">> No, it's a great idea, and I've tried it a couple of \
times - keeping the<br> > wiki page with new stuff and all, so writing the alpha \
and beta<br> > anouncements was fast and easy. Later, I didn't have much time \
left, and<br> <br>
</div>perhaps we should also shift some resources away from alpha/beta \
announcements<br> and invest more heavily into final announcements?<br>
<br>
a simple boilerplate announcement for alpha/beta with a few notes about big \
'n<br> obvious stuff (just cherry pick from recent commit digests?) would \
probably<br> suffice.<br>
<br>
i mean, this is very impressive and makes sense given the dynamics around 4.1:<br>
<br>
<a \
href="http://www.kde.org/announcements/announce-4.1-beta1.php" \
target="_blank">http://www.kde.org/announcements/announce-4.1-beta1.php</a><br> \
<a href="http://dot.kde.org/1211898836/" \
target="_blank">http://dot.kde.org/1211898836/</a><br> <a \
href="http://www.kde.org/info/4.0.80.php" \
target="_blank">http://www.kde.org/info/4.0.80.php</a><br> <br>
but if we keep future beta announcements simpler and invested that effort into<br>
final announcements, maybe we could afford to do more with them and spread it<br>
out over a greater period of time by working on the final announcement all<br>
through the alphas/betas and limiting the resources put into alpha/beta<br>
announcements.<br>
<br>
thoughts?</blockquote><div><br>Nothing wrong with that. And it essentially just takes \
one good day of hard work to get it (mostly) right. For me, working on it 30 min/1 \
hour a day (after work) doesn't really work, so it comes down to weekends - \
I'll try :D<br> </div><blockquote class="gmail_quote" style="border-left: \
1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br> \
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="Wj3C7c">Aaron J. Seigo<br>
humru othro a kohnu se<br>
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43<br>
<br>
KDE core developer sponsored by Qt Software<br>
<br>
</div></div><br><br>
_______________________________________________<br>
This message is from the kde-promo mailing list.<br>
<br>
Visit <a href="https://mail.kde.org/mailman/listinfo/kde-promo" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-promo</a> to unsubscribe, \
set digest on or temporarily stop your subscription.<br></blockquote></div> \
<br></div>
_______________________________________________
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic