The promo team is overloaded work once again! (aren’t we all?)
However, should you be one of the lucky few who might be interested in finding something to keep you busy, as Jos mentioned in one of his previous blog posts we really need more help with writing the Feature Guide for the 4.4 Software Compilation (SC) release. Yeah, I know…that link is mostly about release parties…now you see where the minds of us promo people really are I suppose.
Anyways, some of you might be wondering what exactly this Feature Guide is. I guess it’s mostly obvious that it’s about features but what is the scope of the document, you might ask? Well for those of you that are newer to the community like I am, I’ll explain what I’ve learned.
So when we do releases of the SC one of the things we (the whole community) do is have a plan for what features will be in the next release (http://techbase.kde.org/Schedules/KDE4/4.4_Feature_Plan). One of the things the Promo team does is write up a nice document for end users who are interested in all of the new features for the upcoming SC to translate into simple terms what all of this means to them. It’s a great way to tell the world all the awesome things that our developers are doing in greater detail than what you’d find in a typical, and much more brief, release announcement. That said, if you took a second to look at the feature plan you can see that all of you crazy developer types keep quite busy! And that means there is lots for us Promo folks to write about. So if any KDE users are out there reading this and want to help support your favorite application please know that you can do this simply by taking the bullet points in that Feature Plan I linked above and turning them into sentences for part of this feature guide. Contact the Promo team, email me, or leave a comment and we can get you access to the Feature Guide document to see what still needs to be done.
Changing gears, I’d like to remind everyone that Camp KDE is now nearly upon us at last and from what I hear we’ve got over 80 people coming! There’s still some space left so if you can make it out to sunny San Diego, CA for some or all of Camp KDE be sure to register and come join us.
I remember sitting around at the Promo sprint back in November and hearing Cornelius say how we only had 12 people registered so far and that if we can’t get 100 people to an event in the USA (without just sending our whole European community overseas) we might want to reconsider the idea of a yearly North American conference. Well…we may not hit 100 North Americans this time but that’s at least partially because the venue can only hold 100 people. I know at least personally I have started to tone down my efforts to get more people to register a little for fear of bringing in more folks than we can handle. Next year I say we think bigger all around. With several months lead time, another good location, and a venue to hold 200 people I’m totally convinced we could exceed his expectations
In less successful news, I’ve gotten very little response from anyone who is willing to help design some new KDE gear (shirts/hats/coffee mugs/etc) for our official store. I’m really surprised by this actually. If I had any artistic ability whatsoever I would definitely be creating some cool KDE gear. Hell, I may give it a try anyways even though I’m terrible at graphic design. I mean how awesome would it be to visit Akademy this year and see everyone wearing around clothes that I had designed. Again, let me know if anyone wants to help with this.
Last but not least the mailing list cleanup is still happening…just very, very slowly. So if you haven’t heard from me yet about your potentially outdated or unused mailing list…just wait longer
I will write a follow up post whenever this activity is complete summarizing the results of what we’re going to get rid of and providing information about how we’ll notify people that would potentially be affected. Where possible we’ll definitely refer people to other lists that allow for the same discussions. Though in some cases it’s clear that there was just no need to have even created a list for it in the first place.