{"id":1262,"date":"2007-11-29T19:53:02","date_gmt":"2007-11-29T17:53:02","guid":{"rendered":"http:\/\/vizZzion.org\/blog\/2007\/11\/you-are-press\/"},"modified":"2007-11-29T19:53:02","modified_gmt":"2007-11-29T17:53:02","slug":"you-are-press","status":"publish","type":"post","link":"https:\/\/vizZzion.org\/blog\/2007\/11\/you-are-press\/","title":{"rendered":"You are press."},"content":{"rendered":"

My previous blogentry<\/a> caught quite some attention.
\n Within 36 hours, I burnt 90GB of traffic (thanks jorik for bearing with me!), and at first apache
\n choked on the number of incoming request. But that was only a configuration problem, apache needed
\n its maximum number of concurrent connections increased. I blame the web-2.0 buzzword for this.<\/p>\n

\n So most of the users were eager to see screenshots of what’s going to become KDE 4.0, Aaron’s
\n changed to parts of the plasma user interface (panel and krunner theming were updated shortly
\n before) probably helped a bit. Right before my blogentry, we released KDE 4.0 rc1, which didn’t
\n have those new looks, and we didn’t really bother posting screenshots along with the announcement.
\n So why that? It has everything to do with our current release process. Dirk usually tags the next
\n release on wednesday, then it gets roughly a week of testing, making compile and fixing obviously
\n stupid things you inevitably get when snapshotting an source code repository that’s heavily worked
\n on. So it takes about a week to prepare the release and distribute it to the packagers of various
\n distributions to give them some time to build the code. The announcement is usually done the week
\n thereafter on Tuesdays. And in this case, those running KDE trunk have the more recent code when
\n the release that has been tagged one week before is announced. This will probably change once we
\n branch 4.0 and trunk\/ becomes KDE 4.1-in-progress. This, however, will also still take some time.
\n It has been shortly discussed in the release team, and most people think that we should not distract
\n ourselves by branching off 4.1 too quickly.<\/p>\n

\n So you are press.<\/strong> A lot of KDE’s PR comes from people within the community. It’s
\n quite natural, given the interesting blogposts on PlanetKDE.<\/p>\n

We can make it even more popular by reaching out and being more verbose about the cool desktop,
\n apps and libraries we create.
\n I gather that KDE is also read by quite some people who might not
\n be following the traffic on various mailinglists, and it’s always beneficial for us if we know
\n better what’s going on in other parts of the project. Let’s feel encouraged by the amount of
\n people eagerly waiting for information to pop up. Create screenshots of cool things in KDE,
\n explain them shortly and blog it. We can probably also amaze ourselves quite a bit by all those
\n tricks that can be done with our new KDE — such blogs also make nice additions to the
\n documentation and might also enlighten those people longing for this handy feature to dump their
\n proprietary platform and switch to KDE.<\/p>\n

\n My favourite feature this week was the “undo close tab” which konqueror now has. When logging
\n into my KDE 4 desktop, konqueror friendly asked when starting up if it should also restore the
\n previously opened tabs. Sure, do it. Works like a charm! :-)<\/p>\n

\n Last week, my favourite feature certainly was Kate’s sessions. It’s not a new thing, but I
\n never bothered looking at it and considering it. Now, my kate has a couple of sessions that
\n save me the tedious work of opening 5 documents (that often are located in different
\n directories). Now it’s two clicks away and I can get to work right away.<\/p>\n","protected":false},"excerpt":{"rendered":"

My previous blogentry caught quite some attention. Within 36 hours, I burnt 90GB of traffic (thanks jorik for bearing with me!), and at first apache choked on the number of incoming request. But that was only a configuration problem, apache needed its maximum number of concurrent connections increased. I blame the web-2.0 buzzword for this.… Continue reading You are press.<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-1262","post","type-post","status-publish","format-standard","hentry","category-kde"],"_links":{"self":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1262","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/comments?post=1262"}],"version-history":[{"count":0,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1262\/revisions"}],"wp:attachment":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/media?parent=1262"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/categories?post=1262"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/tags?post=1262"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}