<br />
<b>Deprecated</b>:  Assigning the return value of new by reference is deprecated in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-settings.php</b> on line <b>512</b><br />
<br />
<b>Deprecated</b>:  Assigning the return value of new by reference is deprecated in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-settings.php</b> on line <b>527</b><br />
<br />
<b>Deprecated</b>:  Assigning the return value of new by reference is deprecated in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-settings.php</b> on line <b>534</b><br />
<br />
<b>Deprecated</b>:  Assigning the return value of new by reference is deprecated in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-settings.php</b> on line <b>570</b><br />
<br />
<b>Deprecated</b>:  Assigning the return value of new by reference is deprecated in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/cache.php</b> on line <b>103</b><br />
<br />
<b>Deprecated</b>:  Assigning the return value of new by reference is deprecated in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/query.php</b> on line <b>61</b><br />
<br />
<b>Deprecated</b>:  Assigning the return value of new by reference is deprecated in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/theme.php</b> on line <b>1109</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/post.php</b> on line <b>2872</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/post.php</b> on line <b>2833</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/classes.php</b> on line <b>345</b><br />
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>

<channel>
	<title>JLP's Blog</title>
	<atom:link href="http://jlp.holodeck1.com/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://jlp.holodeck1.com/blog</link>
	<description>A blog about computers, science and some other things</description>
	<pubDate><br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/post.php</b> on line <b>2872</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Wed, 28 Apr 2010 11:24:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>GSoC 2010 with KDE - Improving multi-display support</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2010/04/28/gsoc-2010-with-kde-improving-multi-display-support/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2010/04/28/gsoc-2010-with-kde-improving-multi-display-support/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Wed, 28 Apr 2010 10:22:15 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[GSoC]]></category>

		<category><![CDATA[KDE]]></category>

		<category><![CDATA[Linux]]></category>

		<category><![CDATA[Programming]]></category>

		<category><![CDATA[Software]]></category>

		<category><![CDATA[gsoc kde xrandr xorg kephal desktop linux opensource software programming]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/?p=442</guid>
		<description><![CDATA[Are you also one of those who find setting up multiple displays in KDE workspace is not as good as it could be. The part that handles this is called Kephal, which provides KDE apps with a unified interface to various display configuration backends. On GNU/Linux this means XRandR and if is not available it [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2008/01/kde4logo.png" alt="KDE 4 Logo" style="float: right;" />Are you also one of those who find setting up multiple displays in KDE workspace is not as good as it could be. The part that handles this is called <a href="http://api.kde.org/4.x-api/kdebase-workspace-apidocs/libs/kephal/html/annotated.html"><strong>Kephal</strong></a>, which provides KDE apps with a unified interface to various display configuration backends. On GNU/Linux this means <a href="http://www.x.org/wiki/Projects/XRandR">XRandR</a> and if is not available it uses Qt&#8217;s <a href="http://doc.qt.nokia.com/4.6/qdesktopwidget.html">QDesktopWidget</a> as a read-only fallback. Currently Kephal doesn&#8217;t support all the latest and greatest features available in XRandR and the graphical configuration tool, available in System Settings, is also not so nice to use. More streamlined integration into KDE workspace would also be nice.</p>
<p>And here is where <a href="http://socghop.appspot.com/">Google Summer of Code</a> comes in. This year I&#8217;ve been selected as one of the <a href="http://socghop.appspot.com/gsoc/org/home/google/gsoc2010/kde">50 students</a> who will be working hard on improving various KDE parts. And as you guessed it, I&#8217;ll be working on improving Kephal. The main direction I envisioned is that Kephal should become smarter so that it would be able to configure most of the display related settings on its own, in a way a user would expect. This way the need for user intervention would be reduced to a minimum, and only if there is a special configuration needed, user would open the tool to adjust settings (accessible for example from Devices notification widget, in a similar way as actions for storage media). These settings would be saved and then later loaded as needed automatically, depending on the detected display combinations, or maybe even depending on location/activity other KDE services provide. Details about everything will be decided next week when I&#8217;ll have my first meeting with my mentor <a href="http://www.kdedevelopers.org/blog/77">Will &quot;bille&quot; Stephenson</a>,</p>
<p>At this point I also have to thank <a href="http://gustavoboiko.org/blog/">Gustavo Pichorin Boiko</a>, who was helping me put my GSoC proposal into shape.</p>
<p>BTW, if you have any comments about multi-display support (what you miss, what you don&#8217;t like, any nice ideas about improvements) you&#8217;re welcome to add them to this blog post.</p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2010/04/28/gsoc-2010-with-kde-improving-multi-display-support/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>KDE SC 4.4.2 for Mandriva Linux 2010</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2010/04/03/kde-sc-442-for-mandriva-linux-2010/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2010/04/03/kde-sc-442-for-mandriva-linux-2010/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Sat, 03 Apr 2010 14:45:32 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[KDE]]></category>

		<category><![CDATA[Linux]]></category>

		<category><![CDATA[Mandriva]]></category>

		<category><![CDATA[Software]]></category>

		<category><![CDATA[desktop]]></category>

		<category><![CDATA[open source]]></category>

		<category><![CDATA[opensource]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/?p=439</guid>
		<description><![CDATA[In addition to packaging KDE SC 4.4.2 for the just released Mandriva Linux 2010 Spring Beta 1, the hard-working Mandriva KDE Team, lead by Nicolas Lécureuil (neoclust), have also prepared packages for current stable version of the distribution. To get the latest version of your favourite desktop and applications first add the packages repository by [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://photos7.flickr.com/8733217_ee920a5fe4_o.png" alt="Mandriva Linux logo" style="float: right;" />In addition to packaging <a href="http://www.kde.org/announcements/announce-4.4.2.php" title="KDE Software Compilation 4.4.2 Release Announcement">KDE SC 4.4.2</a> for the just released <a href="http://wiki.mandriva.com/en/2010.1_Beta1" title="Mandriva Linux 2010 Spring Beta 1 Release Information">Mandriva Linux 2010 Spring Beta 1</a>, the hard-working Mandriva KDE Team, lead by Nicolas Lécureuil (neoclust), have also prepared packages for current stable version of the distribution. To get the latest version of your favourite desktop and applications first add the packages repository by issuing this command from Konsole (as root user of course):</p>
<p>If you&#8217;re using a <strong>64-bit</strong> edition:<br /><code>urpmi.addmedia KDE-4.4 ftp://ftp.kde.org/pub/kde/stable/4.4.2/Mandriva/2010.0/x86_64</code></p>
<p>If you&#8217;re using a <strong>32-bit</strong> edition:<br /><code>urpmi.addmedia KDE-4.4 ftp://ftp.kde.org/pub/kde/stable/4.4.2/Mandriva/2010.0/i586</code></p>
<p>If possible use <a href="http://www.kde.org/mirrors/" title="List of KDE mirrors">KDE mirror</a> that is closest to your location. In case you already have a repository for an older KDE SC 4.4 release, you can just edit the URL from Mandriva Control Center. After the repository is configured use the following command to automatically update all repositories, select all updates and perform a test update:</p>
<p><code>urpmi --auto-update --test</code></p>
<p>If all goes well the updated packages should get downloaded and you should get a message that the installation of updates is possible. Now <u>run the previous command again. this time without the &quot;&#8211;test&quot; switch</u>, wait a few minutes and the latest and greatest of KDE software should be installed. Don&#8217;t forget to logout and login and all will be ready. Enjoy!</p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2010/04/03/kde-sc-442-for-mandriva-linux-2010/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>KDE SC 4.4 Release Party in Ljubljana, Slovenia</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2010/02/07/kde-sc-44-release-party-in-ljubljana-slovenia/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2010/02/07/kde-sc-44-release-party-in-ljubljana-slovenia/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Sun, 07 Feb 2010 09:00:32 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[Fun]]></category>

		<category><![CDATA[KDE]]></category>

		<category><![CDATA[Linux]]></category>

		<category><![CDATA[Slovenia]]></category>

		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/?p=437</guid>
		<description><![CDATA[Just a reminder to everyone from KDE Community (or others interested in or work), who will be around Ljubljana, Slovenia on February 9. Encouraged by the big success of the KDE party last year, and a lot of exciting new features in KDE SC 4.3 and 4.4, we&#8217;ve decided to organize another KDE release party [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2008/01/kde4logo.png" alt="KDE 4 Logo" style="float: right;" />Just a reminder to everyone from KDE Community (or others interested in or work), who will be around <strong>Ljubljana, Slovenia on February 9</strong>. Encouraged by the <a href="http://jlp.holodeck1.com/blog/2009/01/28/kde-42-release-party-in-slovenia-a-big-success/" title="KDE 4.2 Release (Party in Slovenia) a Big Success">big success of the KDE party last year</a>, and a lot of exciting new features in KDE SC 4.3 and 4.4, we&#8217;ve decided to organize another KDE release party this year. It will start <strong>at 18:00 local time</strong> and you&#8217;ll be able to hear about some of the cool new developments that have happend in the KDE land since the last party. So don&#8217;t miss this get-together and put this party on your calendars. If you are comming, please add yourself on the list on the <a href="http://community.kde.org/Promo/ReleaseParties/4.4#Ljubljana" title="KDE SC 4.4 Release Party in Ljubljana, Slovenia">KDE SC 4.4 Release parties Wiki</a> and/or <a href="http://www.facebook.com/event.php?eid=270528632745" title="Zabava ob izidu KDE SC 24.4">party page on Facebook</a>. Invite your friends too. Don&#8217;t worry if you are not around Ljubljana on that day and time, we&#8217;ll most probably have a live streaming video during presentations (check this blog, or previously mentioned wiki/Facebook page, later for more info). In case you are even further away from Ljubljana (or don&#8217;t understand Slovenian) there are 26<a href="http://community.kde.org/Promo/ReleaseParties/4.4" title="KDE SC 4.4 Release Parties"> other parties in 15 different countries around the world</a>. Get ready to party!</p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2010/02/07/kde-sc-44-release-party-in-ljubljana-slovenia/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>[SLO] Qt 4.6 in Qt Creator 1.3 tudi v slovenščini</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/12/03/slovenski-qt-46-in-qt-creator-13/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/12/03/slovenski-qt-46-in-qt-creator-13/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Wed, 02 Dec 2009 23:20:36 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[KDE]]></category>

		<category><![CDATA[Programming]]></category>

		<category><![CDATA[Software]]></category>

		<category><![CDATA[Translation]]></category>

		<category><![CDATA[c++]]></category>

		<category><![CDATA[ide]]></category>

		<category><![CDATA[prevajanje]]></category>

		<category><![CDATA[prevod]]></category>

		<category><![CDATA[programiranje]]></category>

		<category><![CDATA[qt]]></category>

		<category><![CDATA[razvoj]]></category>

		<category><![CDATA[slovenščina]]></category>

		<category><![CDATA[slovenski]]></category>

		<category><![CDATA[slovensko]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/?p=415</guid>
		<description><![CDATA[No, včeraj je Nokia končno izdala novo različico svojega odprtokodnega razvojnega ogrodja: Qt 4.6. Istočasno je na dan prišla tudi nova različica preprostega integriranega razvojnega okolja (IDE-ja po domače): Qt Creator 1.3. Poleg veliko novosti, izboljšav in drugih dobrot sta to tudi prvi različici Qt in Qt Creator, ki vsebujeta slovenske prevode. Ni mi sicer [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2009/12/qt-logo.png" alt='Qt Logo' style="float: right; margin-left: 5px; height: 128px; width: 107px" />No, včeraj je Nokia končno izdala novo različico svojega odprtokodnega razvojnega ogrodja: <a href="http://qt.nokia.com/">Qt 4.6</a>. Istočasno je na dan prišla tudi nova različica preprostega integriranega razvojnega okolja (IDE-ja po domače): <a href="http://qt.nokia.com/products/developer-tools/developer-tools">Qt Creator 1.3</a>. Poleg <a href="http://qt.nokia.com/products/whats-new-in-qt">veliko novosti, izboljšav in drugih dobrot</a> sta to tudi prvi različici Qt in Qt Creator, ki vsebujeta <strong>slovenske prevode</strong>. Ni mi sicer uspelo posloveniti povsem vsega in nekaj prevodov je malenkost nerodnih, a mislim, da mi je prvi prevod uspel kar dobro. Ni kaj, novih nizov je bilo pač ogromno in tudi izredno koristen pomnilnik prevodov v <a href="http://userbase.kde.org/Lokalize">Lokalize</a>, napolnjen s prevodi KDE-jevih programov, ni pomagal dovolj.</p>
<p>Za pokušino sta tu dva zaslonska posnetka:<br /><div id="attachment_428" class="wp-caption alignnone" style="width: 310px"><a href="http://jlp.holodeck1.com/blog/wp-content/uploads/2009/12/qt-creator-slo.png"><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2009/12/qt-creator-slo-300x225.png" alt="Slovenski Qt Creator" title="Slovenski Qt Creator (kliknite za povečavo)" width="300" height="225" class="size-medium wp-image-428" /></a><p class="wp-caption-text">Slovenski Qt Creator</p></div> <div id="attachment_430" class="wp-caption alignnone" style="width: 310px"><a href="http://jlp.holodeck1.com/blog/wp-content/uploads/2009/12/qt-designer-slo.png"><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2009/12/qt-designer-slo-300x225.png" alt="Slovenski Qt Designer" title="Slovenski Qt Designer (kliknite za povečavo)" width="300" height="225" class="size-medium wp-image-430" /></a><p class="wp-caption-text">Slovenski Qt Designer</p></div></p>
<p><a href="http://qt.nokia.com/downloads">Prenesite si Qt 4.6 in Qt Creator 4.6</a> (oba skupaj sta zapakirana v novem Qt SDK-ju) in ju preizkusite. Ob tem upam, da boste malo bolj pozorni tudi na slovenske prevode. Če najdete kake napake ali pa imate predlog za izboljšave, pišite na <a href="http://liste2.lugos.si/cgi-bin/mailman/listinfo/lugos-slo">dopisni seznam Lugosovih prevajalcev</a>. Seveda so dobrodošle tudi pohvale. Še najbolj vesel pa bi bil, če bi se mi še kdo pridružil pri prevajanju.</p>
<p>Sedaj pa je čas za prevajanje programov za prihajajoči KDE Software Compilation 4.4 &#8230;</p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/12/03/slovenski-qt-46-in-qt-creator-13/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>Thousand Parsec mentoring for Google Summer of Code 2009</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/03/21/thousand-parsec-mentoring-for-google-summer-of-code-2009/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/03/21/thousand-parsec-mentoring-for-google-summer-of-code-2009/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Sat, 21 Mar 2009 18:01:46 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[GSoC]]></category>

		<category><![CDATA[Games]]></category>

		<category><![CDATA[Programming]]></category>

		<category><![CDATA[Software]]></category>

		<category><![CDATA[Thousand Parsec]]></category>

		<category><![CDATA[4x]]></category>

		<category><![CDATA[free software]]></category>

		<category><![CDATA[game]]></category>

		<category><![CDATA[gamedev]]></category>

		<category><![CDATA[gaming]]></category>

		<category><![CDATA[google]]></category>

		<category><![CDATA[open source]]></category>

		<category><![CDATA[soc]]></category>

		<category><![CDATA[strategies]]></category>

		<category><![CDATA[strategy]]></category>

		<category><![CDATA[summer of code]]></category>

		<category><![CDATA[tbs]]></category>

		<category><![CDATA[turn-based]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/?p=408</guid>
		<description><![CDATA[It&#8217;s the fifth year in a row that Google is running their Summer of Code program, and the third time Thousand Parsec is participating as a mentoring organization. We did great last year and we will sure try to do at least as well this time around.
So, if you are into turn-based 4X space strategy [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2006/12/thousandparsec.png" alt="Thousand Parsec logo" style="width: 128px; height: 128px; margin-left: 5px; float: right"/>It&#8217;s the fifth year in a row that Google is running their <a href="http://socghop.appspot.com/">Summer of Code</a> program, and the third time <a href="http://www.thousandparsec.net/">Thousand Parsec</a> is participating as a mentoring organization. We did <a href="http://www.thousandparsec.net/tp/news.php/2008-10-16-1400">great last year</a> and we will sure try to do at least as well this time around.</p>
<p>So, if you are into turn-based <a href="http://en.wikipedia.org/wiki/4x_game">4X</a> space strategy games and would like to help in game development, this is your chance. Take a look at our <a href="http://www.thousandparsec.net/wiki/Google_Summer_of_Code">Google Summer of Code</a> and <a href="http://www.thousandparsec.net/wiki/Ideas_for_Programmers">Ideas for Programmers</a> pages and get involved. There is even US$ 4500 to encourage you to take that step into the world of open source software programming.</p>
<p>Interested students now have a few days to get to know us better. You can chat with us on IRC (<a href="irc://irc.freenode.org/#tp">Freenode network, #tp channel</a>) or write to our <a href="http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel">development mailing list</a>. After that, <strong>starting from March 23 and ending April 3</strong>, student applications must be submitted. I&#8217;m looking forward to be a mentor again.</p>
<p class="tags-line">Tags: <a href="http://technorati.com/tag/games" rel="tag">games</a>, <a href="http://technorati.com/tag/game" rel="tag">game</a>, <a href="http://technorati.com/tag/gaming" rel="tag">gaming</a>, <a href="http://technorati.com/tag/gamedev" rel="tag">gamedev</a>, <a href="http://technorati.com/tag/4x" rel="tag">4x</a>, <a href="http://technorati.com/tag/strategy" rel="tag">strategy</a>, <a href="http://technorati.com/tag/turn-based" rel="tag">turn-based</a>, <a href="http://technorati.com/tag/strategies" rel="tag">strategies</a>, <a href="http://technorati.com/tag/tbs" rel="tag">tbs</a>, <a href="http://technorati.com/tag/programming" rel="tag">programming</a>, <a href="http://technorati.com/tag/google" rel="tag">google</a>, <a href="http://technorati.com/tag/summer+of+code" rel="tag">summer of code</a>, <a href="http://technorati.com/tag/soc" rel="tag">soc</a>, <a href="http://technorati.com/tag/gsoc" rel="tag">gsoc</a>, <a href="http://technorati.com/tag/open+source" rel="tag">open source</a>, <a href="http://technorati.com/tag/free+software" rel="tag">free software</a></p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/03/21/thousand-parsec-mentoring-for-google-summer-of-code-2009/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>Mandriva Assembly Cooker Chef for Translation Says &#8220;Hi!&#8221;</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/03/09/mandriva-assembly-cooker-chef-for-translation-says-hi/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/03/09/mandriva-assembly-cooker-chef-for-translation-says-hi/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Mon, 09 Mar 2009 01:58:03 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[Linux]]></category>

		<category><![CDATA[Mandriva]]></category>

		<category><![CDATA[Software]]></category>

		<category><![CDATA[Translation]]></category>

		<category><![CDATA[community]]></category>

		<category><![CDATA[free software]]></category>

		<category><![CDATA[localisation]]></category>

		<category><![CDATA[localization]]></category>

		<category><![CDATA[open source]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/?p=401</guid>
		<description><![CDATA[In the beginning of February Mandriva announced the creation of Mandriva Linux Assembly with aim of improving communication between users, contributors and Mandriva company. All to make Mandriva Linux distribution even better than it already is. I candidated as a representative of translators, although I also try to help as much as I can with [...]]]></description>
			<content:encoded><![CDATA[<p><img style="float: right; margin-left: 5px; width: 116px; height: 83px" src="http://photos7.flickr.com/8733217_ee920a5fe4_o.png" alt="Mandriva Linux logo"/>In the beginning of February <a href="http://www.mandriva.com/">Mandriva</a> <a href="http://www.mandriva.com/enterprise/en/company/press/mandriva-announces-the-creation-of-mandriva-linux-assembly">announced</a> the creation of <strong><a href="http://www.mandriva.com/en/community/assembly">Mandriva Linux Assembly</a></strong> with aim of improving communication between users, contributors and Mandriva company. All to make Mandriva Linux distribution even better than it already is. I candidated as a representative of translators, although I also try to help as much as I can with testing development versions. Well a few days ago the results of the vote came in and after some shuffling of positions, to better represent different parts of community, I became a Cooker Chef, representing translators. Thanks to all who voted for me and thanks to <a href="http://www.linux-wizard.net/blog-cooker_chef_representative_vote_result-259.html">Fabrice Facorat</a> for transferring his spot to me. I&#8217;ll try my very best to do my job well. If any of you have any problem with translating and localising Mandriva Linux or have an idea for improving the process, do not hesitate to get in contact with us. You can find us on translation <a href="http://forum.mandriva.com/viewforum.php?f=20">forum</a> or <a href="http://lists.mandriva.com/cooker-i18n/">mailing list</a>.</p>
<p>Since this is my first blog post on <a href="http://planetmandriva.zarb.org/">Planet Mandriva</a>, let me also say &#8220;Hi!&#8221; and introduce myself. I&#8217;m a 28 years old <a href="http://www.gnu.org/philosophy/free-sw.html">Free Software</a> enthusiast from <a href="http://en.wikipedia.org/wiki/Bohinjska_Bistrica" rel="tag">Bohinjska Bistrica</a>, <a href="http://en.wikipedia.org/wiki/Slovenia" rel="tag">Slovenia</a>. As far as Mandriva Linux goes&#8230; I&#8217;ve started using Mandrake with version 7.0, sometime around the year 2000. I began contributing to Mandriva Linux in 2003 by testing beta versions and reporting bugs. A few years later I also started helping translate it into Slovenian language and in 2008 I became the Slovenian translations coordinator. I&#8217;ve also tried to learn some packaging but didn&#8217;t have much time yet, maybe sometime later <img src='http://jlp.holodeck1.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> Besides this, I also contribute to two more Free Software projects: <a href="http://www.thousandparsec.net/">Thousand Parsec</a> (a framework for creating space-empire-building <a href="http://en.wikipedia.org/wiki/4X" rel="tag">4X</a> strategy games) and <a href="http://www.kde.org/">KDE</a>. Additionally, I&#8217;m an active member of <a href="http://www.lugos.si/">Linux Users Group of Slovenia</a> (LUGOS).</p>
<p>Enough about me. Now let&#8217;s get back to making Mandriva Linux the best translated and localised distribution available.</p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/03/09/mandriva-assembly-cooker-chef-for-translation-says-hi/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>KDE 4.2 Release (Party in Slovenia) a Big Success</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/01/28/kde-42-release-party-in-slovenia-a-big-success/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/01/28/kde-42-release-party-in-slovenia-a-big-success/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Wed, 28 Jan 2009 16:04:38 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[Fun]]></category>

		<category><![CDATA[KDE]]></category>

		<category><![CDATA[Linux]]></category>

		<category><![CDATA[Slovenia]]></category>

		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/?p=383</guid>
		<description><![CDATA[Everyone, at least in the free software world, probably knows by now that KDE 4.2 has been released yesterday. It was released just a few moments after the release party started in Kiberpipa/Cyberpipe multimedia centre here in Ljubljana, Slovenia. Just in case you still don&#8217;t know about KDE 4.2 release, you should definitely read KDE [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2008/01/kde4logo.png" alt="KDE 4 Logo" style="width: 128px; height: 128px; float: right; margin-left: 5px"/>Everyone, at least in the free software world, probably knows by now that <strong><a href="http://www.kde.org/announcements/4.2/">KDE 4.2</a></strong> has been released yesterday. It was released just a few moments after the release party started in <a href="http://www.kiberpipa.org/">Kiberpipa/Cyberpipe multimedia centre</a> here in Ljubljana, Slovenia. Just in case you still don&#8217;t know about KDE 4.2 release, you should definitely read <strong><a href="http://www.kde.org/announcements/4.2/">KDE 4.2 release announcement</a></strong> and take a look at the excellent <strong><a href="http://www.kde.org/announcements/4.2/guide.php">visual guide to new features in KDE 4.2</a></strong>. You&#8217;ll see that the solid new foundations laid out with KDE 4.0 are really showing through now and the work invested into them is starting to pay off heavily. At this fast rate of development it is hard to imagine what KDE 4.3 will bring us. And it&#8217;s only 6 months away.</p>
<p><a href="http://jlp.holodeck1.com/blog/2009/01/21/kde-42-release-party-in-ljubljana-slovenia/">The party in Kiberpipa</a> was also a similar success. Everything was not perfect, though. Computers that would be used for workshops didn&#8217;t have KDE 4 installed on them, but this got solved quickly and after the presentations ended all was ready for participants with most interest into KDE 4. Hopefully some of them become contributors in the future. Oh, talking about attendance&#8230; When the idea about the party started to grow inside my head, I was expecting about 20 people coming to the party. Well I was pleasantly surprised in the end. Somewhere <strong>between 40 and 50 people</strong> joined the party. Maybe the number was exactly 42 <img src='http://jlp.holodeck1.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> Well in the following photo you can see some of us who were partying late into the night:</p>
<p style="text-align: center"><a href="http://www.flickr.com/photos/sad_refusals/3231598439/" title="KDE 4.2 Release party, Kiberpipa, Ljubljana Slovenia"><img src="http://farm4.static.flickr.com/3513/3231598439_af0dda0147.jpg?v=0" alt="KDE 4.2 Release party, Kiberpipa, Ljubljana Slovenia" title="KDE 4.2 Release party, Kiberpipa, Ljubljana Slovenia"/></a></p>
<p>The presentations were recorded. When videos become available I&#8217;ll let you know. The slides will also be published together with videos. In the meantime you can read presentation notes about <a href="http://www.jurecuhalev.com/blog/2009/01/27/whats-new-in-kde-42-kdepipa-notes/">What&#8217;s New in KDE 4.2</a> and <a href="http://www.jurecuhalev.com/blog/2009/01/27/plasma-kdepipa-notes/">Plasma</a>, which were taken by <a href="http://www.jurecuhalev.com/blog/">Jure Čuhalev</a>, one of the participants on the party. Thanks to all who came to the party and thanks to all helping to organise it. Who knows, maybe we meet again in six months. Best wishes to all the <strong><a href="http://wiki.kde.org/tiki-index.php?page=KDE+4.2+Release+Party">KDE 4.2 release parties</a></strong> that are still coming. We&#8217;re up to 22 party locations now. Also twice as much as I expected when I started pushing for parties. And if there is no party near you, join people <strong><a href="http://forum.kde.org/kde-4-2-released-t-28742.html">partying on KDE Forum</a></strong>.</p>
<p><strong>Update 1:</strong> Photos from the party are available in <a href="http://www.kiberpipa.org/modules/gallery/album432">Kiberpipa&#8217;s KDE 4.2 Release Party Gallery</a></p>
<p><strong>Update 2:</strong> Videos from the party are available: <a href="http://video.kiberpipa.org/media/POT_KDE_4.2._Release_Party/play.html">Video 1</a> (<a href="http://www.youtube.com/watch?v=26WGtNXzxLc">Youtube</a>), <a href="http://video.kiberpipa.org/media/POT_Gasper_Fele-D-Bus_KDE42RP/play.html">Video 2</a> (<a href="http://www.youtube.com/watch?v=btKwGQ6qiYo">Youtube</a>).</p>
<p class="tags-line">Tags: <a href="http://technorati.com/tag/kde" rel="tag" target="_blank">kde</a>, <a href="http://technorati.com/tag/kde4" rel="tag" target="_blank">kde4</a>, <a href="http://technorati.com/tag/kde42" rel="tag" target="_blank">kde42</a>, <a href="http://technorati.com/tag/desktop" rel="tag" target="_blank">desktop</a>, <a href="http://technorati.com/tag/free+software" rel="tag" target="_blank">free software</a>, <a href="http://technorati.com/tag/prosto+programje" rel="tag" target="_blank">prosto programje</a>, <a href="http://technorati.com/tag/open+source" rel="tag" target="_blank">open source</a>, <a href="http://technorati.com/tag/odprta+koda" rel="tag" target="_blank">odprta koda</a>, <a href="http://technorati.com/tag/slovenia" rel="tag" target="_blank">slovenia</a>, <a href="http://technorati.com/tag/slovenija" rel="tag" target="_blank">slovenija</a>, <a href="http://technorati.com/tag/linux" rel="tag" target="_blank">linux</a>, <a href="http://technorati.com/tag/lugos" rel="tag" target="_blank">lugos</a>, <a href="http://technorati.com/tag/cyberpipe" rel="tag" target="_blank">cyberpipe</a>, <a href="http://technorati.com/tag/kiberpipa" rel="tag" target="_blank">kiberpipa</a></p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/01/28/kde-42-release-party-in-slovenia-a-big-success/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>KDE 4.2 Release Party in Ljubljana, Slovenia</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/01/21/kde-42-release-party-in-ljubljana-slovenia/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/01/21/kde-42-release-party-in-ljubljana-slovenia/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Wed, 21 Jan 2009 16:18:35 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[Education]]></category>

		<category><![CDATA[Fun]]></category>

		<category><![CDATA[KDE]]></category>

		<category><![CDATA[Linux]]></category>

		<category><![CDATA[Slovenia]]></category>

		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/?p=374</guid>
		<description><![CDATA[Who would have thought that my enquiring about the probability of releasing KDE 4.2 on January 27, as scheduled, would lead to 12 registered KDE 4.2 release parties all around the world. It all started just so we could determine the best date for one short KDE 4.2 presentation in Kiberpipa/Cyberpipe, here in Slovenia. With [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://mdic.sourceforge.net/counters/counter.php?color=blue&#038;lang=english&#038;size=2" alt="The real change starts on January 27" title="The real change starts on January 27" style="margin-left:5px; float:right; width:125px; height:125px"/>Who would have thought that my enquiring about the probability of <a href="http://techbase.kde.org/Schedules/KDE4/4.2_Release_Schedule">releasing KDE 4.2 on January 27, as scheduled</a>, would lead to <strong><a href="http://wiki.kde.org/tiki-index.php?page=KDE+4.2+Release+Party">12 registered KDE 4.2 release parties</a></strong> all around the world. It all started just so we could determine the best date for one short KDE 4.2 presentation in <a href="http://www.kiberpipa.org/">Kiberpipa/Cyberpipe</a>, here in <a href="http://en.wikipedia.org/wiki/Slovenia" rel="tag">Slovenia</a>. With encouragement from KDE Promo team this evolved into a <a href="http://dot.kde.org/1231109318/">call for organisation of KDE 4.2 release parties</a> and now&#8230; well, everyone knows about the parties now.</p>
<p>Regarding the Slovenian party, the one short presentation expanded into a nice event with four presentations (about KDE 4.2, Plasma, Amarok 2 and, D-Bus), three workshops (creating a Plasma theme, creating a Plasma widget, and helping with translation), and after that some free socialising with some snacks and drinks. We tried to get Mr. Lancelot (Ivan Čukić) from Serbia as our guest speaker, but unfortunately there was not enough time to get the visa. Next time we sure have to start getting papers in order earlier.</p>
<p>What follow is the announcement of the party in Slovenian.</p>
<hr />
<h2>Zabava ob izidu KDE 4.2</h2>
<p>Kdaj: <strong>27. januarja 2009</strong><br />Kje: <strong>Kiberpipa</strong>, Kersnikova 6, Ljubljana - <a href="http://bit.ly/T1Oj">zemljevid</a></p>
<p>27. januarja bo izšel KDE 4.2, ki je končno primeren tudi za širše občinstvo in ne le za razvijalce in preizkusne uporabnike. KDE 4.2 predstavlja pomemben mejnik v razvoju KDE in skupnost KDE bo pripravila vrsto prireditev in zabav ob izidu te nove različice.</p>
</p>
<p>Tudi v Sloveniji bomo organizirali <strong><a href="http://www.lugos.si/dogodki/druzenje-ob-izidu-KDE-4.2">prireditev ob izidu KDE 4.2</a></strong>, in sicer v torek 27. januarja ob 18:00 v okviru Pipinih odprtih terminov.</p>
<h3>Program</h3>
<p>
<ul>
<li>18:00 - Predstavitev KDE 4(.2) (Andrej Vernekar)</li>
<li>18:30 - Plasma (Jure Repinc)</li>
<li>19:00 - Amarok 2 (Andraž Sraka)</li>
<li>19:15 - Adijo, DCOP; zdravo, D-Bus! (Gašper Fele-Žorž)</li>
<li>19:30 - Delavnice
<ul>
<li>Izdelava teme za Plazmo (Jure Repinc)</li>
<li>Izdelava gradnika za Plazmo (Ambrož Bizjak)</li>
<li>Kako pomagati s prevajanjem (Andrej Vernekar)</li>
</ul>
</li>
<li>20:30 - Pogostitev/druženje/pijača/zabava</li>
</ul>
<p>Če nameravate obiskate katero izmed delavnic, se je nanjo potrebno <a href="https://wiki.lugos.si/kde42">prijaviti na tej strani</a>.</p>
<p><strong>Update 1:</strong> Photos from the party are available in <a href="http://www.kiberpipa.org/modules/gallery/album432">Kiberpipa&#8217;s KDE 4.2 Release Party Gallery</a></p>
<p><strong>Update 2:</strong> Videos from the party are available: <a href="http://video.kiberpipa.org/media/POT_KDE_4.2._Release_Party/play.html">Video 1</a> (<a href="http://www.youtube.com/watch?v=26WGtNXzxLc">Youtube</a>), <a href="http://video.kiberpipa.org/media/POT_Gasper_Fele-D-Bus_KDE42RP/play.html">Video 2</a> (<a href="http://www.youtube.com/watch?v=btKwGQ6qiYo">Youtube</a>).</p>
<p class="tags-line">Tags: <a href="http://technorati.com/tag/kde" rel="tag" target="_blank">kde</a>, <a href="http://technorati.com/tag/kde4" rel="tag" target="_blank">kde4</a>, <a href="http://technorati.com/tag/kde42" rel="tag" target="_blank">kde42</a>, <a href="http://technorati.com/tag/desktop" rel="tag" target="_blank">desktop</a>, <a href="http://technorati.com/tag/free+software" rel="tag" target="_blank">free software</a>, <a href="http://technorati.com/tag/prosto+programje" rel="tag" target="_blank">prosto programje</a>, <a href="http://technorati.com/tag/open+source" rel="tag" target="_blank">open source</a>, <a href="http://technorati.com/tag/odprta+koda" rel="tag" target="_blank">odprta koda</a>, <a href="http://technorati.com/tag/slovenia" rel="tag" target="_blank">slovenia</a>, <a href="http://technorati.com/tag/slovenija" rel="tag" target="_blank">slovenija</a>, <a href="http://technorati.com/tag/linux" rel="tag" target="_blank">linux</a>, <a href="http://technorati.com/tag/lugos" rel="tag" target="_blank">lugos</a>, <a href="http://technorati.com/tag/cyberpipe" rel="tag" target="_blank">cyberpipe</a>, <a href="http://technorati.com/tag/kiberpipa" rel="tag" target="_blank">kiberpipa</a></p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2009/01/21/kde-42-release-party-in-ljubljana-slovenia/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>I&#8217;m ready for Akademy 2008</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/07/14/im-ready-for-akademy-2008/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/07/14/im-ready-for-akademy-2008/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Mon, 14 Jul 2008 20:25:58 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[Education]]></category>

		<category><![CDATA[Fun]]></category>

		<category><![CDATA[KDE]]></category>

		<category><![CDATA[Linux]]></category>

		<category><![CDATA[Personal]]></category>

		<category><![CDATA[Programming]]></category>

		<category><![CDATA[Software]]></category>

		<category><![CDATA[akademy]]></category>

		<category><![CDATA[belgium]]></category>

		<category><![CDATA[desktop]]></category>

		<category><![CDATA[free software]]></category>

		<category><![CDATA[lugos]]></category>

		<category><![CDATA[open source]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/?p=366</guid>
		<description><![CDATA[There&#8217;s less than one month left until the beginning of this year&#8217;s Akademy conference in Sint-Katelijne-Waver, Belgium. Just a few moments ago I&#8217;ve finally arranged everything for the trip. The room at youth hostel Domein Roosendael is paid for and the plane ticket is registered. One more time I have to thank Linux Users Group [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2008/01/kde4logo.png" alt="KDE 4 Logo" style="width: 128px; height: 128px; float: right; margin-left: 5px"/>There&#8217;s less than one month left until the beginning of this year&#8217;s <strong><a href="http://akademy2008.kde.org/">Akademy</a></strong> conference in <a href="http://en.wikipedia.org/wiki/Sint-Katelijne-Waver" rel="tag">Sint-Katelijne-Waver</a>, <a href="http://en.wikipedia.org/wiki/Belgium">Belgium</a>. Just a few moments ago I&#8217;ve finally arranged everything for the trip. The room at youth hostel <a href="http://www.roosendael.be/NL/verblijfsaccommodatie_voor_groepen_en_trekkers/vol_en_half_pension/koetshuis">Domein Roosendael</a> is paid for and the plane ticket is registered. One more time I have to thank <a href="http://www.lugos.si/">Linux Users Group of Slovenia (Lugos)</a>, who are paying for the flight. This will be my second time to Akademy and this time I&#8217;m staying for the whole week. The only thing left now is to decide which talks from the <a href="http://akademy2008.kde.org/conference/program.php">two parallel tracks</a> I will be attending. Looking forward to meet cool <a href="http://www.kde.org/">KDE</a> contributors!</p>
<p style="text-align:center"><img src="http://commit-digest.org/issues/2008-06-08/files/akademy2008.png" alt="I'm going to Akademy 2008" style="width:320px;height:178px"/></p>
<p class="tags-line">Tags: <a href="http://technorati.com/tag/kde" rel="tag" target="_blank">kde</a>, <a href="http://technorati.com/tag/desktop" rel="tag" target="_blank">desktop</a>, <a href="http://technorati.com/tag/akademy" rel="tag" target="_blank">akademy</a>, <a href="http://technorati.com/tag/akademy+2008" rel="tag" target="_blank">akademy 2008</a>, <a href="http://technorati.com/tag/free+software" rel="tag" target="_blank">free software</a>, <a href="http://technorati.com/tag/open+source" rel="tag" target="_blank">open source</a>, <a href="http://technorati.com/tag/belgium" rel="tag" target="_blank">belgium</a>, <a href="http://technorati.com/tag/linux" rel="tag" target="_blank">linux</a>, <a href="http://technorati.com/tag/lugos" rel="tag" target="_blank">lugos</a></p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/07/14/im-ready-for-akademy-2008/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>Thousand Parsec GSoC 2008 Blogs</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/23/thousand-parsec-gsoc-2008-blogs/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/23/thousand-parsec-gsoc-2008-blogs/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Wed, 23 Apr 2008 12:50:30 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[GSoC]]></category>

		<category><![CDATA[Games]]></category>

		<category><![CDATA[Programming]]></category>

		<category><![CDATA[Software]]></category>

		<category><![CDATA[Thousand Parsec]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/?p=365</guid>
		<description><![CDATA[A couple of days have passed since eight students found out they will be hacking on Thousand Parsec as part of Google Summer of Code 2008. All have come to Thousand Parsec IRC channel to say Hi in and all of them posted their introductions to Thousand Parsec Development mailing list. Each and every student [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2006/12/thousandparsec.png" alt="Thousand Parsec logo" style="width: 128px; height: 128px; margin-left: 5px; float: right"/>A couple of days have passed since <a href="http://jlp.holodeck1.com/blog/2008/04/22/gsoc-2008-projects-for-thousand-parsec/">eight students</a> found out they will be hacking on <a href="http://www.thousandparsec.net/">Thousand Parsec</a> as part of Google Summer of Code 2008. All have come to <a href="irc://irc.freenode.org/#tp">Thousand Parsec IRC channel</a> to say Hi in and all of them posted their introductions to <a href="http://news.gmane.org/gmane.comp.games.tp.devel">Thousand Parsec Development mailing list</a>. Each and every student now also has a spot on the web where they will blog about their experiences and progress.</p>
<p>I&#8217;ve created a <strong><a href="http://thousand-parsec.blogspot.com/">Thousand Parsec Blog</a></strong> on <a href="http://www.blogger.com/">Blogger</a> which links to all the blogs of our students. The page will also serve as the blog for everyone who would like to write about Thousand Parsec but doesn&#8217;t feel like setting up his or her own blog just for that. So, if you are interested to see what we at Thousand Parsec are up to this summer, <strong><a href="http://thousand-parsec.blogspot.com/">this</a></strong> is the place to start. Of course we will also make sure that feeds from our blogs are aggregated on <a href="http://planet-soc.com/">Planet SoC</a>. You will then be able to see <strong><a href="http://planet-soc.com/organization/Thousand+Parsec/planet">all GSoC  posts from our blogs in one place</a></strong> and add <a href="http://planet-soc.com/organization/Thousand+Parsec/planet/feed">the feed</a> to your favourite feed reader.</p>
<p class="tags-line">Tags: <a href="http://technorati.com/tag/games" rel="tag">games</a>, <a href="http://technorati.com/tag/game" rel="tag">game</a>, <a href="http://technorati.com/tag/gaming" rel="tag">gaming</a>, <a href="http://technorati.com/tag/gamedev" rel="tag">gamedev</a>, <a href="http://technorati.com/tag/4x" rel="tag">4x</a>, <a href="http://technorati.com/tag/strategy" rel="tag">strategy</a>, <a href="http://technorati.com/tag/turn-based" rel="tag">turn-based</a>, <a href="http://technorati.com/tag/strategies" rel="tag">strategies</a>, <a href="http://technorati.com/tag/tbs" rel="tag">tbs</a>, <a href="http://technorati.com/tag/programming" rel="tag">programming</a>, <a href="http://technorati.com/tag/google" rel="tag">google</a>, <a href="http://technorati.com/tag/summer+of+code" rel="tag">summer of code</a>, <a href="http://technorati.com/tag/soc" rel="tag">soc</a>, <a href="http://technorati.com/tag/gsoc" rel="tag">gsoc</a>, <a href="http://technorati.com/tag/open+source" rel="tag">open source</a>, <a href="http://technorati.com/tag/free+software" rel="tag">free software</a></p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/23/thousand-parsec-gsoc-2008-blogs/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>GSoC 2008 projects for Thousand Parsec</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/22/gsoc-2008-projects-for-thousand-parsec/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/22/gsoc-2008-projects-for-thousand-parsec/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Tue, 22 Apr 2008 00:40:47 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[Fun]]></category>

		<category><![CDATA[GSoC]]></category>

		<category><![CDATA[Games]]></category>

		<category><![CDATA[Programming]]></category>

		<category><![CDATA[Thousand Parsec]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/?p=364</guid>
		<description><![CDATA[A couple of hours ago Google published the final list of 1125 students who will be working on free and open source projects as part of Google Summer of Code 2008 program. This year 8 students will work with us at Thousand Parsec project. This is twice the number of students we had last year. [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2006/12/thousandparsec.png" alt="Thousand Parsec logo" style="width: 128px; height: 128px; margin-left: 5px; float: right"/>A couple of hours ago Google published the final list of 1125 students who will be working on free and open source projects as part of <a href="http://code.google.com/soc/2008/">Google Summer of Code 2008</a> program. This year 8 students will work with us at <strong><a href="http://www.thousandparsec.net/">Thousand Parsec</a></strong> project. This is twice the number of students we had last year. Here&#8217;s what they will be working on this summer:</p>
<ul>
<li><a href="http://code.google.com/soc/2008/parsec/appinfo.html?csaid=678C2C068DCE83AE">3D Client for Thousand Parsec</a> - <a href="http://devhobby.blogspot.com/">Blog</a> - Eugene Tan Jie Ming</li>
<li><a href="http://code.google.com/soc/2008/parsec/appinfo.html?csaid=E1CE7382099D727C">Tigris and Euprhates Ruleset Adaptation</a> - <a href="http://nuleren.blogspot.com/">Blog</a> - Dustin E. White</li>
<li><a href="http://code.google.com/soc/2008/parsec/appinfo.html?csaid=9F7AC048F3DAC4C4">Genetic Conquest: An AI Client for Thousand Parsec (RFTS ruleset)</a> - <a href="http://vi1985.blogspot.com/">Blog</a> - Victor Ivri</li>
<li><a href="http://code.google.com/soc/2008/parsec/appinfo.html?csaid=E83FEA7BC9DC4560">DroneSec: A simple, one hour game for tpserver-py</a> - <a href="http://juangsoc.blogspot.com/">Blog</a> - Juan Lafont</li>
<li><a href="http://code.google.com/soc/2008/parsec/appinfo.html?csaid=5B1B1C8E204530AD">A Modified Risk ruleset for the Thousand Parsec C++ server</a> - <a href="http://www.hammerofcode.com/">Blog</a> - Ryan Neufeld</li>
<li><a href="http://code.google.com/soc/2008/parsec/appinfo.html?csaid=7731B9B4B375E2E5">Remote Server Configuration Protocol and Single-Player Mode</a> - <a href="http://ezod.livejournal.com/">Blog</a> - Aaron Mavrinac</li>
<li><a href="http://code.google.com/soc/2008/parsec/appinfo.html?csaid=AD885F56FE726D6C">AI for RFTS</a> - <a href="http://thousand-parsec.blogspot.com/">Blog</a> - Vincent Verhoeven</li>
<li><a href="http://code.google.com/soc/2008/parsec/appinfo.html?csaid=39055FB6EAC6D799">Schemepy</a> - <a href="http://pluskid.lifegoo.com/">Blog</a> - Chiyuan Zhang</li>
</ul>
<p>You can be sure that all of us, students and mentors, will do our very best to complete these projects successfully. Exciting months for open source 4X games are ahead of us. I hope you look forward to the results as much as we at Thousand Parsec do.</p>
<p class="tags-line">Tags: <a href="http://technorati.com/tag/games" rel="tag">games</a>, <a href="http://technorati.com/tag/game" rel="tag">game</a>, <a href="http://technorati.com/tag/gaming" rel="tag">gaming</a>, <a href="http://technorati.com/tag/gamedev" rel="tag">gamedev</a>, <a href="http://technorati.com/tag/4x" rel="tag">4x</a>, <a href="http://technorati.com/tag/strategy" rel="tag">strategy</a>, <a href="http://technorati.com/tag/turn-based" rel="tag">turn-based</a>, <a href="http://technorati.com/tag/strategies" rel="tag">strategies</a>, <a href="http://technorati.com/tag/tbs" rel="tag">tbs</a>, <a href="http://technorati.com/tag/programming" rel="tag">programming</a>, <a href="http://technorati.com/tag/google" rel="tag">google</a>, <a href="http://technorati.com/tag/summer+of+code" rel="tag">summer of code</a>, <a href="http://technorati.com/tag/soc" rel="tag">soc</a>, <a href="http://technorati.com/tag/gsoc" rel="tag">gsoc</a>, <a href="http://technorati.com/tag/open+source" rel="tag">open source</a>, <a href="http://technorati.com/tag/free+software" rel="tag">free software</a></p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/22/gsoc-2008-projects-for-thousand-parsec/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>STC TransAlpine Chapter Conference 2008</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/20/stc-transalpine-chapter-conference-2008/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/20/stc-transalpine-chapter-conference-2008/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Sat, 19 Apr 2008 22:27:01 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[Education]]></category>

		<category><![CDATA[KDE]]></category>

		<category><![CDATA[Slovenia]]></category>

		<category><![CDATA[Software]]></category>

		<category><![CDATA[Translation]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/?p=363</guid>
		<description><![CDATA[During the past two days I&#8217;ve been at this year&#8217;s conference of TransAlpine Chapter (TAC) of the Society for Technical Communication (STC). It was hosted by HERMES SoftLab here in Ljubljana. Since I work quite a lot on translating KDE and other open source software and sometimes also help with documentation I sure thought it [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2008/04/stc.png" alt="STC" title="STC" style="width:127px; height:128px; margin-left:5px; float:right" />During the past two days I&#8217;ve been at this year&#8217;s <a href="http://www.hermes-softlab.com/news/20080416.html">conference</a> of <a href="http://stc-on.org/transalpine/">TransAlpine Chapter</a> (TAC) of the <a href="http://www.stc.org/">Society for Technical Communication</a> (STC). It was hosted by <a href="http://www.hermes-softlab.com/">HERMES SoftLab</a> here in <a href="http://en.wikipedia.org/wiki/Ljubljana" rel="tag">Ljubljana</a>. Since I work quite a lot on translating <a href="http://www.kde.org/">KDE</a> and other open source software and sometimes also help with documentation I sure thought it would be interesting to attend the conference. One other reason for me to be there is that, as of late, I&#8217;m more and more thinking about how it would be to have a career in <a href="http://en.wikipedia.org/wiki/Technical_communication" rel="tag">technical communication</a> (translating, writing documentation and all things related). At first it looked like I wouldn&#8217;t be able to be at the conference because the attendance fee (195€) was quite high for a student. Luckily <a href="http://www.lugos.si/">Linux Users Group of Slovenia</a> (Lugos) stepped in and sponsored me.</p>
<p>The conference itself was well above my expectations. I anticipated to meet more or less older and more reserved people, but it turned out they are relaxed, fun, overall cool and in average younger than expected. The talks were also very interesting and they covered a broad range of subjects. Just goes to show how wide the spectre of technical communicators&#8217; knowledge can be. To me the three most interesting presentations were:</p>
<dl>
<dt><strong>Pictures and profits: how visual information design and simple usability studies can save your company millions</strong> by Patrick Hofmann</dt>
<dd>Very interesting how creative you often must be to convey some mesage or concept in a graphical way. A lot also depends on culture an end user comes from. In the end all makes users of documentation happier, because it is easier to understand. This, together with reduction of messages to translate, can save companies a lot of money.</dd>
<dt><strong>Brave new world: How one writing team moved to DITA-based authoring</strong> by Helen O&#8217;Shea</dt>
<dd><a href="http://en.wikipedia.org/wiki/Darwin_Information_Typing_Architecture" rel="tag">DITA</a> is not only a new XML format for technical documentation. It also brings a new way of thinking in topics as basic and complete chunks of information. Topics can later be assembled into different deliverables like books and online help. During this presentation I was constantly thinking how DITA could be used for documentation in KDE. Is there need (and will) for another conversion?</dd>
<dt><strong>Improving the quality and usability of error messages</strong> by Katarzyna Kostorz</dt>
<dd>Yet another presentation where I was thinking about how all that was said could apply to KDE. First we were shown some examples of bad and good error messages and what are the properties that make them bad or good. Next we could see how error messages are handled by IBM. Not only is the short version shown in GUI, the longer explanation and possible further actions to be taken (by different type of users) are all part of the documentation.</dd>
</dl>
<p>At the end of the conference I was asked if all that I&#8217;ve learnt has scared me away from thinking about being a technical writer. I answered that I don&#8217;t get scared so easily. Quite the opposite, I can now say that I&#8217;m interested in a technical communication career even more. STC membership application is already filled out and ready to be sent across the Atlantic Ocean.</p>
<p>Congrats to the organisers for such a great conference. Hopefully I will be able to meet all the people once again next year.</p>
<p style="text-align:center"><img src="http://www.hermes-softlab.com/SLO/news/rel/att/20080417.jpg" alt="STC TAC Conference 2008"  style="width: 448px; height: 299px" /></p>
<p class="tags-line">Tags: <a href="http://www.technorati.com/tag/transalpine+chapter" rel="tag">transalpine chapter</a>, <a href="http://www.technorati.com/tag/tac" rel="tag">tac</a>, <a href="http://www.technorati.com/tag/society+for+technical+communication" rel="tag">society for technical communication</a>, <a href="http://www.technorati.com/tag/stc" rel="tag">stc</a>, <a href="http://www.technorati.com/tag/technical+communication" rel="tag">technical communication</a>, <a href="http://www.technorati.com/tag/technical+writing" rel="tag">technical writing</a>, <a href="http://www.technorati.com/tag/documentation" rel="tag">documentation</a>, <a href="http://www.technorati.com/tag/translation" rel="tag">translation</a>, <a href="http://www.technorati.com/tag/dita+NOT+teese" rel="tag">dita</a>, <a href="http://www.technorati.com/tag/kde" rel="tag">kde</a></p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/20/stc-transalpine-chapter-conference-2008/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>Mandriva Linux 2008 Spring Released</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/10/mandriva-linux-2008-spring-released/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/10/mandriva-linux-2008-spring-released/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Thu, 10 Apr 2008 00:49:03 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[Linux]]></category>

		<category><![CDATA[Mandriva]]></category>

		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/?p=360</guid>
		<description><![CDATA[A new version of one of the most user-friendly distributions of free and open source operating system Linux has just been released. Mandriva Linux 2008 Spring (or 2008.1 if you wish) packs quite a lot of goodies. It brings official full support for the highly popular ASUS Eee PC laptop, has easier synchronisation with various [...]]]></description>
			<content:encoded><![CDATA[<p><img style="float: right; margin-left: 5px; width: 116px; height: 83px" src="http://photos7.flickr.com/8733217_ee920a5fe4_o.png" alt="Mandriva Linux logo"/>A new version of one of the most user-friendly distributions of free and open source operating system <a href="http://en.wikipedia.org/wiki/Linux" rel="tag">Linux</a> has just been released. <strong><a href="http://www.mandriva.com/en/download/">Mandriva Linux 2008 Spring</a></strong> (or 2008.1 if you wish) packs quite a lot of goodies. It brings official full support for the highly popular <a href="http://eeepc.asus.com/">ASUS Eee PC</a> laptop, has easier synchronisation with various mobile devices, a new parental control utility, <a href="http://elisa.fluendo.com/">Elisa</a> multimedia centre is there, so is <a href="http://fedoraproject.org/wiki/Multimedia/Codeina" rel="tag">Codeina</a> for easy multimedia codecs installation. They have also switched to <a href="http://pulseaudio.org/">PulseAudio</a> sound server, updated software to latest versions (yes even <a href="http://www.kde.org/announcements/announce-4.0.3.php">KDE 4.0.3</a> is available) and given the distribution a fresh new look. Go <strong><a href="http://www.mandriva.com/en/download/">download it from here</a></strong> (or <a href="http://torrent.mandriva.com/public/">via BitTorrent</a>) and while downloading be sure to check out a <a href="http://wiki.mandriva.com/en/2008.1_Tour">visual guide to what&#8217;s new in Mandriva Linux 2008 Spring</a>.</p>
<p>As with previous releases I also did my fair share of beta testing and <a href="http://qa.mandriva.com/">bug reporting</a> this time. In addition this is also the first release where I have been the coordinator of <a href="https://wiki.lugos.si/slovenjenje:mandriva:mandriva">Slovenian translation team</a>. We did a great job and almost everything is translated. The only thing left are initscript messages (which are hidden most of the time).</p>
<p>Even during beta testing this release proved to be of very high quality. Looks like after some hiccups a year or two ago Mandriva have put their act together and the quality of releases is increasing every year now. They are also doing a great job with improving their relationship and interaction with community. If they continue in this direction they can soon be back at the top, although it will be hard since unfortunately there is not so much hype surrounding Mandriva as there is around some other very popular Linux distribution.</p>
<p class="tags-line">Tags: <a href="http://www.technorati.com/tag/mandriva" rel="tag">mandriva</a>, <a href="http://www.technorati.com/tag/linux" rel="tag">linux</a>, <a href="http://www.technorati.com/tag/distributions" rel="tag">distributions</a>, <a href="http://www.technorati.com/tag/eee+pc" rel="tag">eee pc</a>, <a href="http://www.technorati.com/tag/eeepc" rel="tag">eeepc</a>, <a href="http://www.technorati.com/tag/free+software" rel="tag">free software</a>, <a href="http://www.technorati.com/tag/open+source" rel="tag">open source</a>, <a href="http://www.technorati.com/tag/operating+systems" rel="tag">operating systems</a></p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/10/mandriva-linux-2008-spring-released/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>Parsek, 4X game client for KDE 4, now in SVN</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/07/parsek-4x-game-client-for-kde-4-now-in-svn/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/07/parsek-4x-game-client-for-kde-4-now-in-svn/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Mon, 07 Apr 2008 12:00:34 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[Games]]></category>

		<category><![CDATA[KDE]]></category>

		<category><![CDATA[Programming]]></category>

		<category><![CDATA[Thousand Parsec]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/2008/04/07/parsek-4x-game-client-for-kde-4-now-in-svn/</guid>
		<description><![CDATA[Parsek is a KDE 4 client for turn-based strategy games where your goal is to build a space empire. These games are known as 4X games (from four primary goals: eXplore, eXpand, eXploit and eXterminate). Specifically, Parsek is a client for games created using Thousand Parsec framework.
I&#8217;ve started working on Parsek a little more then [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2008/04/hi128-app-parsek.png" alt="Parsek Logo" style="width: 128px, height: 128px; margin-left: 5px; float: right" /><strong>Parsek</strong> is a <a href="http://www.kde.org/">KDE 4</a> client for turn-based strategy games where your goal is to build a space empire. These games are known as <a href="http://en.wikipedia.org/wiki/4X_games" rel="tag">4X games</a> (from four primary goals: eXplore, eXpand, eXploit and eXterminate). Specifically, Parsek is a client for games created using <a href="http://www.thousandparsec.net/tp/gettingstarted.php">Thousand Parsec</a> framework.</p>
<p>I&#8217;ve started working on Parsek a little more then a year ago. It was one of my ways of learning Qt and KDE programming. Unfortunately I didn&#8217;t have much time to work on Parsek since then. Well yesterday I&#8217;ve imported Parsek into KDE&#8217;s Subversion repository, into <a href="http://websvn.kde.org/trunk/playground/games/parsek/">playground/games/parsek</a>.</p>
<p>Parsek can&#8217;t be used to actually play games yet. It can connect to the server, download properties of objects in a Universe and display objects in a simple tree and it can download the messages and display them in a simple table. Two of the main things to be done before Parsek is usable is to make it possible to view and add orders to objects and to display a nice map of the Universe. Anyways, here is how Parsek currently looks like:</p>
<p style="text-align: center"><a href="http://jlp.holodeck1.com/blog/wp-content/uploads/2008/04/parsek.png" title="Parsek screenshot (click to enlarge)"><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2008/04/parsek-small.png" alt="Parsek screenshot - small" style="width: 400px; height: 278px" /></a></p>
<p>If you find this interesting and would like to <strong>help</strong> in any way, you are <strong>more than welcome</strong>. The basic instructions on how to compile Parsek are on its <a href="http://www.thousandparsec.net/wiki/Parsek">Wiki page</a>.</p>
<p>Yesterday I have also been browsing through the history of posts on <a href="http://planetkde.org/">Planet KDE</a> and I found a post about <a href="http://weblog.obso1337.org/2008/the-1-problem-in-oss-usability-and-what-im-going-to-do-about-it/">lack of user research</a> by <a href="http://weblog.obso1337.org/">Celeste Paul</a>. She also put together a <a href="http://techbase.kde.org/index.php?title=User:Seele/Project_User_Research_Template">user research template</a> which I will try to fill out as soon as possible and will then put it into Wiki and in plain text form also into the Parsek&#8217;s source code folder.</p>
<p class="tags-line">Tags: <a href="http://technorati.com/tag/games" rel="tag" target="_blank">games</a>, <a href="http://technorati.com/tag/gaming" rel="tag" target="_blank">gaming</a>, <a href="http://technorati.com/tag/strategy+games" rel="tag" target="_blank">strategy games</a>, <a href="http://technorati.com/tag/4x+games" rel="tag" target="_blank">4x games</a>, <a href="http://technorati.com/tag/kde" rel="tag" target="_blank">kde</a>, <a href="http://technorati.com/tag/kde4" rel="tag" target="_blank">kde4</a>, <a href="http://technorati.com/tag/free+software" rel="tag" target="_blank">free software</a>, <a href="http://technorati.com/tag/open+source" rel="tag" target="_blank">open source</a></p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/07/parsek-4x-game-client-for-kde-4-now-in-svn/feed/</wfw:commentRss>
		</item>
	<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
	<item>
		<title>1st Day of Open Source in Maribor</title>
		<link><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/06/1st-day-of-open-source-in-maribor/</link>
		<comments><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/06/1st-day-of-open-source-in-maribor/#comments</comments>
		<pubDate><br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>50</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>52</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>54</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>55</b><br />
<br />
<b>Warning</b>:  mktime() [<a href='function.mktime'>function.mktime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/functions.php</b> on line <b>41</b><br />
Sun, 06 Apr 2008 12:07:16 +0000</pubDate>
		<dc:creator>JLP</dc:creator>
		
		<category><![CDATA[Computers]]></category>

		<category><![CDATA[Education]]></category>

		<category><![CDATA[Linux]]></category>

		<category><![CDATA[Personal]]></category>

		<category><![CDATA[Slovenia]]></category>

		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://jlp.holodeck1.com/blog/2008/04/06/1st-day-of-open-source-in-maribor/</guid>
		<description><![CDATA[I&#8217;ve been to Maribor last Thursday where the 1st Day of Open Source event was organised at the Faculty of Electrical Engineering and Computer Science. This was my first time visiting Maribor and my first impression was that it is a very nice, clean and lively city.
At the event itself you could attend various interesting [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://jlp.holodeck1.com/blog/wp-content/uploads/2008/04/prvi-dan-odprte-kode.jpg" alt="1. dan odprte kode" style="width: 100px, height: 100px; margin-left: 5px; float: right"/>I&#8217;ve been to <a href="http://en.wikipedia.org/wiki/Maribor" rel="tag">Maribor</a> last Thursday where the <strong><a href="http://dok.ds-feri.net/">1st Day of Open Source</a></strong> event was organised at the <a href="http://www.feri.uni-mb.si/podrocje.aspx?id=0&#038;langid=1033">Faculty of Electrical Engineering and Computer Science</a>. This was my first time visiting Maribor and my first impression was that it is a very nice, clean and lively city.</p>
<p>At the event itself you could attend various interesting talks about Linux and Open Source Software in general. I even had the honor to be the very first speaker. I presented FLOSS, it&#8217;s history, licensing and after that talked a bit about <a href="http://www.lugos.si/">Lugos</a>, the Linux User Group of Slovenia. Too bad I missed the talks at the end of the day but I had to catch the last train back to <a href="http://en.wikipedia.org/wiki/Ljubljana" rel="tag">Ljubljana</a>.</p>
<p>I must say I was pleasantly surprised by the number of attendance. A quick count showed that there were constantly at least 150 people in the room. By comparison, the day before this event Microsoft organised a similar event, where there were only 30-50 people. Despite Microsoft having better promotion and they even tried to bribe students by some expensive prizes.</p>
<p>Anyways, hats off to <a href="http://www.heapsoft.com/">Oto Brglez jr.</a> and the <a href="http://ds-feri.net/">Students Group</a>. They did an excellent job organizing the event and I sure look forward to the 2nd Day of Open Source.</p>
<p class="tags-line">Tags: <a href="http://technorati.com/tag/open+source" rel="tag" target="_blank">open source</a>, <a href="http://technorati.com/tag/free+software" rel="tag" target="_blank">free software</a>, <a href="http://technorati.com/tag/floss" rel="tag" target="_blank">floss</a>, <a href="http://technorati.com/tag/linux" rel="tag" target="_blank">linux</a>, <a href="http://technorati.com/tag/lugos" rel="tag" target="_blank">lugos</a>, <a href="http://technorati.com/tag/maribor" rel="tag" target="_blank">maribor</a>, <a href="http://technorati.com/tag/slovenia" rel="tag" target="_blank">slovenia</a></p>
]]></content:encoded>
			<wfw:commentRss><br />
<b>Warning</b>:  strtotime() [<a href='function.strtotime'>function.strtotime</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in <b>/var/www/jlp.holodeck1.com/htdocs/blog/wp-includes/link-template.php</b> on line <b>132</b><br />
http://jlp.holodeck1.com/blog/2008/04/06/1st-day-of-open-source-in-maribor/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
