<br><br><div class="gmail_quote">2009/11/3 Aaron J. Seigo <span dir="ltr"><<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
hi all ..<br>
<br>
i spent some time today thinking about challenges as well as opportunities<br>
that exist for our little Plasma baby who is growing up at an amazing pace.<br>
<br>
just to give you an idea of where we're at in terms of raw code production,<br>
here are some sloccount counts:<br>
<br>
kdelibs: 42,121<br>
runtime: 4,190<br>
workspace: 83,332<br>
addons: 55,792<br>
<br>
and we have so many little buds of progress elsewhere too:<br>
<br>
kdereview: 8,365<br>
media center components: 6,608<br>
plasmate: 4,518<br>
networkmanager: 27,029<br>
lionmail: 2,009<br>
mobile shell: 1,147<br>
<br>
we have been pounding out feature packed release after feature packed release<br>
and 4.4 will be no different in that regard.<br>
<br>
of course, it's not the only way we're growing. were also growing the user<br>
base as more of our desktop users come online and we start to reach out into<br>
new areas of the market such as netbooks and phones. we're also growing in<br>
*dum de dum dum* bug count. right now we have 745 open bug reports, not<br>
counting wishlist items. that's not as bad as it might sound; it's somewhere<br>
around one bug per 240 lines of code. but it's still substantial.<br>
<br>
as i mentioned at T3, plasma has developed a bit of a rhythm from release to<br>
release: January brings lots of new features (esp big ones) and some polish,<br>
July brings lots of polish and some new features (mostly smaller ones).<br>
<br>
4.4 will certainly be a big feature release: netbook, remote plasmoids, new<br>
widget explorer, containment action plugins, lots more javascript in a number<br>
of places, nepomuk integration .... but what about 4.5?<br>
<br>
well, i'm seriously considering putting a moratorium on new features in 4.5<br>
and instead focusing on making it a polishing release.<br>
<br>
when we started out with KDE 4, one of our goals was to create an object of<br>
desire that people would pick over the "high end competition" such as MacOS.<br>
we achieved so much towards that goal, and now our biggest sore points are the<br>
little details.<br>
<br>
such a polishing release would consist of:<br>
<br>
* completing features that have made it thus far in a "mostly done" state but<br>
not quite finished<br>
<br>
* cataloging and improving families of (mis-)features like this:<br>
<a href="http://techbase.kde.org/Projects/Plasma/Plasmoid-Issues" target="_blank">http://techbase.kde.org/Projects/Plasma/Plasmoid-Issues</a><br>
<br>
* a concentration on killing bugs right from the start of the release cycle<br>
<br>
* measuring memory and cpu performance and improving on both<br>
<br>
* tightening down our artwork and configuration UIs for consistency and extra<br>
sparkle<br>
<br>
if we go ahead with this, then our pre-release IRC meetings and T4 would be<br>
the where we would mark out our targets and decide how to tackle them.<br>
<br>
my concerns in such a move are:<br>
<br>
* it would destroy people's desire to work on plasma by making it more boring<br>
and difficult than it currently is with all the emphasis on great new things<br>
<br>
* people would ignore this set of goals and work on features anyways,<br>
splitting our community up and causing some tensions we don't have with our<br>
"wide open" policy<br>
<br>
* we wouldn't have enough to show at the end of it for our users to go "wow"<br>
over<br>
<br>
if we decide that this is something we would like to take on, we would need to<br>
make it fun and cool to do this hard work. i'd be sure to share bug count<br>
stats, performance measurements and track our goals on a regular basis to keep<br>
us moving. if new people came along with new features or we found we Really,<br>
Really(tm) needed something (e.g. if we got some kick ass bluetooth work<br>
donated), we'd have to be flexible enough to allow some of that to happen but<br>
disciplined enough not to get sidetracked ourselves.<br>
<br>
now, i'm still working through all of the implications of this and really<br>
haven't decided yet whether it's the best of ideas yet. and it would<br>
absolutely require that the overwhelming majority of our team here would want<br>
to see this through.<br>
<br>
so i put the question to you: what do you think? should we do this? should we<br>
not? why? why not?<br>
<br>
(and just to head off all the "oh yes, please do!" comments from the people on<br>
the list here who follow the threads but who aren't active contributors to<br>
some part of plasma: let's keep this discussion to those who are working on<br>
the code and artwork for now. thanks :)<br>
<font color="#888888"><br>
</font><br></blockquote><div><br>I think this is a excellent idea for a number of reasons. It will shows users that KDE4 is not just all about new features and more features and more......<br>Plasma does seem have issues that get missed, such as Plasmoids acting nasty when moving out of the panel or resizing. Knocking out these types of bugs is important or just getting a number of Plasmoids acting properly and ship these only.<br>
<br>I'm sure users will appreciate optimization since they bang on about "polish" and speed more than features a lot of the time. Slow down a bit and polish up for a release seems like a good idea to me.<br>
<br>I'd be willing to help debug and look for nasties, so count me in!<br><br>Regards<br><br>Sean W<br></div></div>