People person, technology enthusiast and all-things-open evangelist. I have managed and marketed communities for over a decade, getting started in the KDE community, followed by working as openSUSE Community Manager at SUSE and now managing community matters at ownCloud. I'm busy growing the ownCloud community, speaking at and organizing conferences and writing about my passions ranging from psychology and people in communities to innovative technology. I take care of my dog together with my wife in beautiful Berlin and you can find me also on Twitter and Diaspora!
10 August, 2007
Yet, every time I write about nice stuff done in KDE, I'm left with the nagging feeling I MUST have missed a lot. And I'm sure I did miss some great things. It's mostly due to the unstructured, ad-hoc way of writing the announcements. OK, I tried to go through a lot of blogs and all KDE commit digests since the second alpha (boy, is that a lot of work) but even then, stuff is missed.
Now it's not just that the release announcement is thus incomplete. It's also that people don't get the credit they deserve, and those reading the announcements miss out on some great stuff which has been done.
So I came up with the idea to create a space on techbase where everyone can help collect stuff for the next announcement. And with everyone, I mean EVERYONE. If you just saw a cool thing being checked in to KDE-EDU, or you read a blog about a new fun feature in Kwrite - or you do a test of KWin and discover new stuff - go ahead. It's worthy. When the release announcement has to be written we (the promo team) will go through it, filter the good stuff, write the text all the while thanking each and every contributor silently ;-)
You don't have to write anything, just say what it's about ('Cool KWin stuff' is enough) and provide a link...
Where? here you go: http://techbase.kde.org/Schedules/KDE4/4.0_Announcements
I already threw in some things, and I'm sure I forgot stuff already. So, developers: if you did something amazing, put a link there. To a blog, commit message, mailinglist email, anything. And to all those reading all the blogs and stuff in the community: please, help a little. It's not much work at all, and it'll not only help us - but also ensure the completeness of the release announcements!!!