|Soon time to start to test things IRL|
But we need them! A while back I started a thread about it and it needs a reboot - the reception was luke warm at best and I thought "a proper competition - with fabulous prizes, like a car is whats needed!". Then I remembered that I'm not Oprah and this is Open Source and scaled it down a bit. With the help of the KDE eV we got funding so we can get the three winners the awesome book "Design Elements - a graphic style manual" (which is a brilliant and accessible book about graphic design that everyone should read) and the plan is to dig out some tshirts and stuff to to throw in the mix.
So how will this work? Essentially this is the deal - a group of community organizers/VDG people will pick out the ones that work, rank them into three piles and then let the community decide through a poll. "Wait wut?" you might say, why not let the community decide from scratch? Weeeeeell this is the catch with this competition. Some distros and DE's has had a not great experience with these things and as much as I think "come one, come all" is a relevant point - we also need to have a quality check of the wallpapers. The cruel bit is: if the VDG/Community Organizers don't feel like any are up to snuff - no one will win. They will try to make certain that all entries get help to get up to snuff, but if nothing happens - no wallpaper will be chosen.
More on the competition in the thread HERE.
Ask-a-dev is another idea but this is about increasing the exchange between the design community, the community-at-large and devs. Essentially every week we will pick a dev, introduce the poor man or woman - and start a thread where we can ask technical or design questions to that dev to help introduce the "behind the scenes" work. The thread will then remain BUT with the edit that "Dev has left building" meaning the dev might not answer more questions - that way the threads can be used as a FAQ section for the future and a place to talk about that specific work.
Now before that kick off please bare in mind I will monitor these threads like George RR Martin writes books - the devs have agreed on the condition that we play nice. This is not an opportunity for people to scream "Why did you remove X feature!!!111" and I will go all Red Wedding on anyone who does.
You can ask him anything HERE.
But lets get into Plasma Next again - what does the future hold? Remember when we talked about "bit-by-bit" implementation? Somewhere like 10 Monday Reports ago? Yeah this is when we talk some more about it. For the next version of Plasma we will keep some of the most experimental things as "Opt-In" instead of "Opt-Out". Essentially the issue is as follows: Aurorae is not a viable option to ship for many good technical reasons (which may be answered in full by Martin Grässlin in the Ask-a-dev thread of the future) so we will, for the time being ship with the Oxygen windec theme (please not the difference between Widget and Windec). So essentially the first version this June will ship with mostly Oxygen and then change over time as things get finished up.
So how will that work? Well hopefully we will ship with an aurorae theme and qtquick as well but let it be something you can pick during settings instead of something set by default - simply because it may be too heavy and clunky for now.
Aside from all that there is work on the fonts, the Plasma theme, the porting and work on icon themes. This summer the first version shipped for testing will contain a large chunk of the work but not that which we don't feel confident shipping by default just yet.
This is key: Opt-in is ALWAYS better than opt-out and I will defend this stand point to death. If we're not sure, we wont push it on you (tbh we don't push anything on you but ... yeah) :)
Next time we will try to talk some more about real world examples, show some screen shots and essentially some more pretty pictures :)