<?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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tracking Time &#187; updates</title>
	<atom:link href="http://blog.tracking-time.com/category/updates/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tracking-time.com</link>
	<description>time and performance management on demand</description>
	<lastBuildDate>Fri, 29 Jan 2010 17:02:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>We are back on Track!</title>
		<link>http://blog.tracking-time.com/2010/01/we-are-back-on-track/</link>
		<comments>http://blog.tracking-time.com/2010/01/we-are-back-on-track/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 00:50:55 +0000</pubDate>
		<dc:creator>the Tracking Time team</dc:creator>
				<category><![CDATA[updates]]></category>

		<guid isPermaLink="false">http://blog.tracking-time.com/?p=140</guid>
		<description><![CDATA[Yeah baby! After a few months of struggling with some performance issues, and with some deserved vacations (for some of us, some time in rehab…), We are back on track! Don’t expect big changes…these are the first steps on improving some of the big issues that we have (thanks Phil, Jana, Shani!) so here they [...]]]></description>
			<content:encoded><![CDATA[<p>Yeah baby!<strong><br />
</strong>After a few months of struggling with some performance issues, and with some deserved vacations (for some of us, some time in rehab…), <strong><br />
<strong>We are back on track!</strong></strong></p>
<p>Don’t expect big changes…these are the first steps on improving some of the big issues that we have (thanks Phil, Jana, Shani!) so here they are:</p>
<ol>
<li>We changed      wires, hired some mega-servers…changed mysql connections and some other      geek stuff to deliver a stable service.</li>
</ol>
<ol>
<li>Many of      you fell asleep in front of the computer, and forgot to turn your widget      off …and, the day after, you couldn’t edit your tasks because of our lame      time editor. Well that won’t happen any more…now you can edit your napping      time.</li>
</ol>
<ol>
<li>We have moved      the time editor to a visible spot…yes, we weren’t so proud of it so it was      a bit hidden at the beginning; yet, we understand it is and important      feature.</li>
</ol>
<ol>
<li>No more opening      a dialog box to create a Skill or a Service. Just write it down and they will      be automatically created (if they haven’t been created before).</li>
</ol>
<ol>
<li>We      implemented a message box in the dashboard to stay in touch.</li>
</ol>
<ol>
<li>Each time      you create a new user, he is going to receive an email with the      download link so he can start tracking right away. This seems obvious…but it’s      our first step into email communication.</li>
</ol>
<ol>
<li>We      corrected some typos, but not all of them. Ha!</li>
</ol>
<p><strong>Well that’s it for this week, we are aware that you are expecting more, so there will be more!</strong></p>
<p>Next week, we hope to implement weekly email updates with a summary of the work you or your team have done.<br />
We are also redefining our little friend (the widget) so you can make more out of your working day.</p>
<p>That’s it for now, until next week!<br />
The Tracking Time Team.</p>
<p>P.S. We also added a Pay Pal donation option… That is up to you  (this is serious <img src='http://blog.tracking-time.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  ).</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.tracking-time.com/2010/01/we-are-back-on-track/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

