<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities Blog</title>
    <link>http://communities.vmware.com/blogs/communities</link>
    <description>Status updates and the behind-the-scenes story of VMware Communities</description>
    <pubDate>Thu, 22 Nov 2007 02:49:23 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2007-11-22T02:49:23Z</dc:date>
    <item>
      <title>November 21 Update</title>
      <link>http://communities.vmware.com/blogs/communities/2007/11/21/november-21-update</link>
      <description>&lt;br /&gt;
Last update before we Americans go stuff ourselves over the Thanksgiving holiday weekend: performance and stability appear to be fine for the fifth straight day. Given this, and a combination of VMware's scheduled maintenance windows plus holiday vacation schedules for critical team members, we have decided to postpone the deployment of a second node to our cluster until first week of December.&lt;br /&gt;
&lt;p /&gt;
Thank you, and will be back online on Monday, November 26!&lt;br /&gt;
&lt;p /&gt;
Badsah Mukherji, Sr. Community Manager, VMware</description>
      <category domain="http://communities.vmware.com/blogs/communities/tags">status</category>
      <category domain="http://communities.vmware.com/blogs/communities/tags">update</category>
      <pubDate>Thu, 22 Nov 2007 02:49:00 GMT</pubDate>
      <author>Badsah</author>
      <guid>http://communities.vmware.com/blogs/communities/2007/11/21/november-21-update</guid>
      <dc:date>2007-11-22T02:49:00Z</dc:date>
      <clearspace:dateToText>2 years, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
      <wfw:comment>http://communities.vmware.com/blogs/communities/comment/november-21-update</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/communities/feeds/comments?blogPostID=1252</wfw:commentRss>
    </item>
    <item>
      <title>November 20 Update: Note U.S. Holiday, Nov. 22-23 (Thanksgiving)</title>
      <link>http://communities.vmware.com/blogs/communities/2007/11/20/november-20-update-note-us-holiday-nov-2223-thanksgiving</link>
      <description>NOTICE: Due to the U.S. Thanksgiving holiday, the VMware's U.S. offices will be closed Thursday and Friday, November 22 and 23, 2007.&lt;br /&gt;
&lt;br /&gt;
Well, we are cautiously optimistic that we've reached a period of stability on the site. We have enjoyed four plus days of continuous uptime, and the performance has been consistently reasonable. We are still targeting end of next week (last week of November) for adding the second server to the cluster, to enhance the performance.&lt;br /&gt;
&lt;p /&gt;
If you still encounter sporadic error messages, reload/refresh the page and you will usually see the error disappear. If the problem persists, please bring it to our attention. Details such as timing, page information, and specifics of what you were doing at the time are helpful, as always.&lt;br /&gt;
&lt;p /&gt;
Thank you.&lt;br /&gt;
&lt;p /&gt;
Badsah Mukherji, Sr. Community Manager, VMware</description>
      <category domain="http://communities.vmware.com/blogs/communities/tags">status</category>
      <category domain="http://communities.vmware.com/blogs/communities/tags">update</category>
      <pubDate>Tue, 20 Nov 2007 23:31:00 GMT</pubDate>
      <author>Badsah</author>
      <guid>http://communities.vmware.com/blogs/communities/2007/11/20/november-20-update-note-us-holiday-nov-2223-thanksgiving</guid>
      <dc:date>2007-11-20T23:31:00Z</dc:date>
      <clearspace:dateToText>2 years, 3 days ago</clearspace:dateToText>
      <wfw:comment>http://communities.vmware.com/blogs/communities/comment/november-20-update-note-us-holiday-nov-2223-thanksgiving</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/communities/feeds/comments?blogPostID=1248</wfw:commentRss>
    </item>
    <item>
      <title>October 30 Update</title>
      <link>http://communities.vmware.com/blogs/communities/2007/10/29/october-30-update</link>
      <description>We are working on an issue where the application eventually runs out of session resources on the database connection pool.  We've set minimum connections = maximum connections as a short-term fix so that the pool size doesn't change, because we believe the leak occurs when the pool is resized.  We are also working on the long-term fix, which is to put in a JNDI configuration to replace Jive's connection provider.  Meanwhile, Jive is investigating a higher-level locking function on the connection.  And we are running load tests on an iGate JDBC driver, which we hope to deploy this week for better compatibility with our SQL Server database.  We are making these changes because the thread dumps indicate problems with database connectivity.&lt;br /&gt;
&lt;br /&gt;
At the same time, we installed a new community test environment with Tomcat on a 32 win2003 platform. We are configuring that and will begin testing later in the week. If the driver replacement doesn't solve our problem, we will move replace Linux/Tomcat with the Win2003/Tomcat in order to run on a completely different JDBC environment which is more compatible with our Win2003 SQLServer database cluster.&lt;br /&gt;
&lt;br /&gt;
We are also going to reset the system tonight at 5:00am to attempt to make it through the European peak demand.&lt;br /&gt;
&lt;br /&gt;
Rich Text Editor (RTE): We plan to move the JavaScript for the RTE onto our Akamai service.  Currently, most of the functionality is in a gzipped JavaScript library that is served from the Jive platform and unzipped by the browser.  It appears that IE calls these JavaScript functions before they are fully unzipped, which results in the object not found errors many of you have reported.  This problem is worse when the application is running slowly.  By moving the files to Akamai, we will be able to serve them unzipped, and we believe this will greatly improve the editor loading issues.&lt;br /&gt;
&lt;br /&gt;
Thank you for your patience as we work through these issues.</description>
      <category domain="http://communities.vmware.com/blogs/communities/tags">status</category>
      <pubDate>Tue, 30 Oct 2007 04:44:00 GMT</pubDate>
      <author>RDellimmagine</author>
      <guid>http://communities.vmware.com/blogs/communities/2007/10/29/october-30-update</guid>
      <dc:date>2007-10-30T04:44:00Z</dc:date>
      <clearspace:dateToText>2 years, 3 weeks ago</clearspace:dateToText>
      <wfw:comment>http://communities.vmware.com/blogs/communities/comment/october-30-update</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/communities/feeds/comments?blogPostID=1176</wfw:commentRss>
    </item>
    <item>
      <title>Feature Fix Released</title>
      <link>http://communities.vmware.com/blogs/communities/2007/10/24/feature-fix-released</link>
      <description>We just rolled out a new VMware Communities platform release that fixes some of the top feature issues identified by the community: &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Threaded display mode for discussions.&lt;/b&gt; On My Content -&amp;gt; Preferences, you can set either threaded or flat view. Your default is the setting you had in the old VMTN forums; guests always see flat view.  In threaded view, all posts display on a single page; in flat view, 15, 30, or 50 messages display per page (see Set Posts Per Page below).  In addition, if threaded discussions go more than 20 levels deep, all threads at level 20 and beyond display at level 20.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;View all posts from a user.&lt;/b&gt; If you go to on any community member's profile -&amp;gt; Discussions tab, you will see all messages the member posted. Each member's Overview tab still displays just the threads the member started.  And we did discover a bug too late to fix:  the links in the Discussions tab point to the top of each thread, not to the individual message within the thread.  We will fix this next week.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Set posts per page.&lt;/b&gt; On My Content -&amp;gt; Preferences, you can set 15, 30, or 50 posts per page.  Your default is the setting you had in the old VMTN forums. This one setting determines both the number of discussions or documents that display on a community homepage and the number of messages that display in a thread (in flat view only).&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Search in this community.&lt;/b&gt; The search box will by default search just within the current community (and child communities, if there are any) as it did in the old VMTN forums. Once you've done a search, the results page displays with the advanced options open and the appropriate community and its children selected to remind you where the results are from.  If you wish to broaden the search, you can then specify other communities and rerun the search. &lt;i&gt;Tip for Windows: use shift-click or control-click to select multiple communities.&lt;/i&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Legibility tweaks.&lt;/b&gt; We tweaked the UI to make community pages and threads easier to scan. &lt;i&gt;Note: To see this fix, you may need to refresh your browser so it loads the new CSS.&lt;/i&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Mark as read.&lt;/b&gt; If you click 'Mark as read' in a parent community, it marks the message as read in all child communities as well.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Blog permalinks.&lt;/b&gt; Blog permalinks for guests now link to the proper blog post. Blog permalink pages now display with proper width.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
I've updated the &lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-1000"&gt;VMware Communities Known Issues&lt;/a&gt; with today's fixes.&lt;br /&gt;
&lt;br /&gt;
We continue to spec out additional functional and u/i improvements, and we will blog about them here later.  Search improvements are at the top of the list.&lt;br /&gt;
&lt;br /&gt;
Meanwhile, we continue to work on reducing the system slowdowns and restarts, which we believe is a key source of the browser and text editor issues some of you are experiencing.</description>
      <category domain="http://communities.vmware.com/blogs/communities/tags">deployment</category>
      <category domain="http://communities.vmware.com/blogs/communities/tags">features</category>
      <category domain="http://communities.vmware.com/blogs/communities/tags">status</category>
      <pubDate>Wed, 24 Oct 2007 23:49:00 GMT</pubDate>
      <author>RDellimmagine</author>
      <guid>http://communities.vmware.com/blogs/communities/2007/10/24/feature-fix-released</guid>
      <dc:date>2007-10-24T23:49:00Z</dc:date>
      <clearspace:dateToText>2 years, 1 month ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
      <wfw:comment>http://communities.vmware.com/blogs/communities/comment/feature-fix-released</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/communities/feeds/comments?blogPostID=1164</wfw:commentRss>
    </item>
    <item>
      <title>Features in the pipeline</title>
      <link>http://communities.vmware.com/blogs/communities/2007/10/11/features-in-the-pipeline</link>
      <description>We're continuing to do performance tuning and monitoring on the system. In parallel, we are continuing our software development, both in-house here at VMware as well as at Jive. We've got several features and UI changes in the pipeline.&lt;br /&gt;
&lt;br /&gt;
In the shorter term, we are reintroducing several useful features that we used to have in the old VMTN based on Jive Forums that were not present in the Jive Clearspace platform we're now using. These features are in testing and we hope to have them out to you next week. (I hope early next week.) &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Threaded display mode for discussions.&lt;/b&gt; This will add a preference to display discussions as a tree of indented replies. People have strong feelings about this, one way or another. For most forums, I actually prefer a flat display, and as an admin, I think flat displays help keep a thread on topic. However, for the intense discussions and the demographic we have here, and because we are all used to it, I think a threaded display is absolutely necessary. It's actually very useful as an moderator as well if we have to delete a message or branch a thread.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;View all posts from a user.&lt;/b&gt; This will show all the messages posted by a user in a tab on their profile. Right now, in your profile you can only see the threads you've started, not the ones you've replied to. This is useful to keep track of your current conversations, and it's also useful to get more context about others in the community and what all they're participating in.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Set posts per page.&lt;/b&gt; This is a real convenience function to be able to set 50 instead of 15 posts/page. Right now, the default is 15 and you have to keep resetting it. This will be a preference, as it was in Forums.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Search in this community.&lt;/b&gt; The search box will by default search just within the community you're in, as it did in Forum. Once you're doing a search, you can specify other communities. &lt;i&gt;Tip: you can select multiple communities -- for Windows, use shift-click or control-click.&lt;/i&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Legibility tweaks.&lt;/b&gt; We will be tweaking the UI for fonts and colors to make it more readable.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Outstanding high-priority issues that will be addressed, but not by early next week:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Rich Text Editor.&lt;/b&gt; It doesn't load all the time, and is frustrating when it loads. This is the highest priority item for which I don't have a scheduled fix date. &lt;i&gt;Tip: try out the Plain Text editor -- it's faster, and it has automatic spell-check.&lt;/i&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Search.&lt;/b&gt; Results are per-message, not per-thread; there is no user filter (although you will be able to see all posts by a user now); some syntax isn't working; search results can be poor in general. &lt;i&gt;Tip: use Boolean syntax (foo AND bar, foo || bar), not Google-style syntax. Also, you can use Google and add the term "(site:communities.vmware.com OR site:www.vmware.com/community)" -- works pretty well. Google still has a mix of old and new pages in its index.&lt;/i&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Front page.&lt;/b&gt; We want to simplify the front page and add indications there when there are unread messages within a community.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Right sidebar.&lt;/b&gt; The right sidebar was designed as a way of adding contextual resources to each community -- links to docs, latest builds, kb articles, white papers, security alerts, blog postings from the team. For performance reasons, every community shows the same sidebar, and it takes up too much room on the page. We will address this.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Favorites/Watches.&lt;/b&gt; Have some graphical way in the communities of indicating which threads you're interested in, instead of having to go to your profile.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
A fuller list of outstanding issues is &lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-1000"&gt;VMware Communities Known Issues&lt;/a&gt;. I think soon we'll be faster and more powerful than where we were, so we can get back to the business of virtualization. (Oh, and there are some very interesting new community topics and blogs in the pipeline, but that's for another day.)</description>
      <category domain="http://communities.vmware.com/blogs/communities/tags">status</category>
      <category domain="http://communities.vmware.com/blogs/communities/tags">update</category>
      <category domain="http://communities.vmware.com/blogs/communities/tags">features</category>
      <pubDate>Fri, 12 Oct 2007 01:55:00 GMT</pubDate>
      <author>JohnTroyer</author>
      <guid>http://communities.vmware.com/blogs/communities/2007/10/11/features-in-the-pipeline</guid>
      <dc:date>2007-10-12T01:55:00Z</dc:date>
      <clearspace:dateToText>2 years, 1 month ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
      <wfw:comment>http://communities.vmware.com/blogs/communities/comment/features-in-the-pipeline</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/communities/feeds/comments?blogPostID=1123</wfw:commentRss>
    </item>
    <item>
      <title>Monitoring and IE Performance</title>
      <link>http://communities.vmware.com/blogs/communities/2007/10/08/monitoring-and-ie-performance</link>
      <description>&lt;h5&gt;Monitoring Issues&lt;/h5&gt;
On Sunday night into Monday morning, we had unexpected downtime on VMware Communities.  As soon as we realized, we immediately rebooted VMware Communities and performance returned to reasonable levels, but that was after many community members in time zones other than Pacific experienced several hours of poor performance.  We had been checking the site manually all weekend, but from Sunday night to Monday morning Pacific, the site was unusably slow.  We are sorry for that, especially since we are aware how many of you rely on VMware Communities professionally and personally.  We’ve now shortened the acceptable response time for our monitoring system to 20 seconds – if a page loads slower than 20 seconds, we get an alert and will examine system statistics and respond appropriately.&lt;br /&gt;
&lt;br /&gt;
&lt;h5&gt;New Build Environment&lt;/h5&gt;
On Thursday, we recreated our build environment by rolling in a series of performance patches we had made since going live.  Recreating our build environment is a necessary step before we can roll out the additional usability and performance fixes that we have been (and continue to be) working on.  The build appears to have caused some issues with the order of posts on the various community pages (although the timestamps are still correct).  Jive Software is working on identifying a fix, and I will give an update here tomorrow.&lt;br /&gt;
&lt;br /&gt;
&lt;h5&gt;Today's Fixes&lt;/h5&gt;
The advantage of having a new build environment is that we are able today to roll out a set of usability and performance fixes:&lt;br /&gt;
&lt;blockquote&gt;&lt;b&gt;Internet Explorer Performance&lt;/b&gt;: We replaced the JavaScript-based top menus with CSS-based ones, which makes them faster on Internet Explorer, both IE6 and IE7. Since people’s experiences have varied depending on their hardware, software, and location, please let us know if these menus now work for you.&lt;/blockquote&gt;
&lt;blockquote&gt;&lt;b&gt;Private Message notifications&lt;/b&gt;: The “My Content” in your menu bar now turns orange when you have a private message waiting for you.&lt;/blockquote&gt;
&lt;blockquote&gt;&lt;b&gt;Blog formatting&lt;/b&gt;: Some blog pages didn’t format correctly, and these are now fixed.&lt;/blockquote&gt;
&lt;br /&gt;
Meanwhile, we are continuing to work on performance, including the issues that caused the outage Sunday night / Monday morning.  This week we are also working on the top features that were lost in the move from VMTN Forums to VMware Communities, as well as some other usability improvements.  I expect some good news on those two areas as well as performance over the course of the week.&lt;br /&gt;
&lt;br /&gt;
I promise to keep you all informed more frequently of progress.</description>
      <category domain="http://communities.vmware.com/blogs/communities/tags">status</category>
      <category domain="http://communities.vmware.com/blogs/communities/tags">update</category>
      <pubDate>Tue, 09 Oct 2007 06:43:00 GMT</pubDate>
      <author>RDellimmagine</author>
      <guid>http://communities.vmware.com/blogs/communities/2007/10/08/monitoring-and-ie-performance</guid>
      <dc:date>2007-10-09T06:43:00Z</dc:date>
      <clearspace:dateToText>2 years, 1 month ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
      <wfw:comment>http://communities.vmware.com/blogs/communities/comment/monitoring-and-ie-performance</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/communities/feeds/comments?blogPostID=1105</wfw:commentRss>
    </item>
    <item>
      <title>One step at a time -- site update</title>
      <link>http://communities.vmware.com/blogs/communities/2007/10/04/one-step-at-a-time-site-update</link>
      <description>&lt;br /&gt;
You may notice some small changes in the Communities today. &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Discussion tabs are now selected by default. From there, you can more easily see unread posts (bold) and link directly to the last reply (last column)&lt;/li&gt;
&lt;li&gt;Status icons are back in threads&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
We are targeting another update by early next week.&lt;br /&gt;
&lt;br /&gt;
We continue to experience slow performance at certain times. We're working closely with Jive to identify the root cause and resolve these issues. We have monitoring in place that will automatically restart the application when it becomes unresponsive. IE performance, both with IE6 and IE7, remains problematic. Along with overall slow behavior, the editor seems to load with difficulty. Once it loads, try clicking on the Plain Text tab and then clicking on 'Always use this editor'. The Plain Text editor may load more reliably.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Today's update.&lt;/b&gt; During the launch, we patched the application several times. We needed ensure our source control system was in sync with these changes and to do regression testing so that future updates would not break anything. This why you haven't seen a lot of changes this week. Today we switched to this new version of the code  -- and we also slipped in those two features.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;UI update.&lt;/b&gt; While we were waiting, we've already queued up a number of fixes, including faster CSS-based menus to replace the slow Javascript menus and many other UI changes. One of the major goals is to make IE more usable with this update. We'll be testing that build Friday but may wait until after the weekend to release.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Feature update.&lt;/b&gt; We also have developers working on the most important missing features from this list: &lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-1000"&gt;VMware Communities Known Issues&lt;/a&gt;. We'll have a better estimate tomorrow, but I am hoping the first batch them will also appear next week.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Ongoing work.&lt;/b&gt; We expect to continue the bug fixes and improvements for several more weeks. After that we hope changes will happen less frequently, and we can start to experiment and learn what we can do with our new collaboration tools. See &lt;a class="jive-link-blogpost" href="http://communities.vmware.com/blogs/communities/2007/10/02/whats-it-all-about"&gt;What's It All About?&lt;/a&gt; for more information on why we upgraded the Communities.</description>
      <category domain="http://communities.vmware.com/blogs/communities/tags">community</category>
      <category domain="http://communities.vmware.com/blogs/communities/tags">status</category>
      <category domain="http://communities.vmware.com/blogs/communities/tags">update</category>
      <pubDate>Fri, 05 Oct 2007 00:47:00 GMT</pubDate>
      <author>JohnTroyer</author>
      <guid>http://communities.vmware.com/blogs/communities/2007/10/04/one-step-at-a-time-site-update</guid>
      <dc:date>2007-10-05T00:47:00Z</dc:date>
      <clearspace:dateToText>2 years, 1 month ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
      <wfw:comment>http://communities.vmware.com/blogs/communities/comment/one-step-at-a-time-site-update</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/communities/feeds/comments?blogPostID=1098</wfw:commentRss>
    </item>
    <item>
      <title>Performance Tuning &amp;#38; Usability</title>
      <link>http://communities.vmware.com/blogs/communities/2007/09/26/performance-tuning-38-usability</link>
      <description>&lt;b&gt;Performance&lt;/b&gt;: We implemented performance fixes today, which have decreased load times of pages and removed the intermittent delays many users were experiencing. &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Configuration changes on the proxy&lt;/li&gt;
&lt;li&gt;Increased cache size on the application server&lt;/li&gt;
&lt;li&gt;Removal of Javascript from the homepage dropdowns and the right column&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
We are working to further reduce the amount of Javascript in the next few days, especially on the homepage.  And we are continuing to monitor performance and work with Jive Software to resolve issues.  &lt;br /&gt;
&lt;br /&gt;
We are now turning our focus to the many usability fixes and improvements you all have been reporting.  &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Lost in Transition&lt;/b&gt;:  To start off, we are working on the following Forums features missing in Clearspace:&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;Threaded view&lt;/li&gt;
&lt;li&gt;See all posts from user -- now you can only see the new threads started by a user, not all posts and replies&lt;/li&gt;
&lt;li&gt;View communities with unread threads at a glance, so users can scan the list of communities and see which ones have new posts since they last visited&lt;/li&gt;
&lt;li&gt;Visible indicator of watches/favorites so users can track threads they were researching or working on answering.&lt;/li&gt;
&lt;li&gt;Set # of posts per page as a per-user configurable preference&lt;/li&gt;
&lt;li&gt;Search returns per-Message results, i.e. if a search term shows up in several messages of a thread, it should return one result instead of one result per message&lt;/li&gt;
&lt;li&gt;Turn off the editor and use a plain text editor&lt;/li&gt;
&lt;li&gt;User filter in search, i.e. ability to search by user&lt;/li&gt;
&lt;li&gt;Code markup missing, e.g. for [code], &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=+pre+"&gt; pre &lt;/a&gt;, and [url]{noformat}&lt;/li&gt;
&lt;li&gt;Search in this community (currently only search in all communities)&lt;/li&gt;
&lt;li&gt;Advanced search so users don't have to do a blank search to get to the advanced search functionality&lt;/li&gt;
&lt;li&gt;No PM notification if private email&lt;/li&gt;
&lt;/ol&gt;
&lt;br /&gt;
These are roughly in priority order, although we may increase the priority of the editor fix, since that prevents some users from posting.  We will update here and in the &lt;a class="jive-link-thread" href="http://communities.vmware.com/thread/104202"&gt;Missing Features&lt;/a&gt; thread.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Other Usability Fixes&lt;/b&gt;: We are also looking at other usability fixes, and will have a fully-prioritized list tomorrow. Among others, we are looking at the following:&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Making Discussions the default tab (not All Content), which will make read tracking of threads more visible&lt;/li&gt;
&lt;li&gt;Fixing OR search&lt;/li&gt;
&lt;li&gt;Turn off default email notification&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;b&gt;Low-Hanging Fruit&lt;/b&gt;: While we investigated the more important issues, we slipped in some easy fixes:&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Fixing of Reply button so it doesn't fall off the page -- we enclosed those pages in a &amp;lt;table&amp;gt;&lt;/li&gt;
&lt;li&gt;We will add tables to a few other pages with similar problems&lt;/li&gt;
&lt;li&gt;Put "Up to Discussions" link at the bottom of threads as well -- they were only at the top&lt;/li&gt;
&lt;li&gt;Put points in Top Members boxes&lt;/li&gt;
&lt;li&gt;Ensure all listings have Previous and Next buttons -- listings on All Contents tab did not&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
I know many of you continue to be frustrated, but I ask you to bear with us while we fix these issues. With a little patience, I still firmly believe the benefits of the new features will become more and more apparent.  One is already apparent to us behind the scenes -- this platform is much easier to customize and bug-fix than Forums.  We are working to push out fixes as fast as we can.</description>
      <category domain="http://communities.vmware.com/blogs/communities/tags">status</category>
      <pubDate>Thu, 27 Sep 2007 06:34:00 GMT</pubDate>
      <author>RDellimmagine</author>
      <guid>http://communities.vmware.com/blogs/communities/2007/09/26/performance-tuning-38-usability</guid>
      <dc:date>2007-09-27T06:34:00Z</dc:date>
      <clearspace:dateToText>2 years, 1 month ago</clearspace:dateToText>
      <wfw:comment>http://communities.vmware.com/blogs/communities/comment/performance-tuning-38-usability</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/communities/feeds/comments?blogPostID=1036</wfw:commentRss>
    </item>
    <item>
      <title>Performance Update</title>
      <link>http://communities.vmware.com/blogs/communities/2007/09/24/performance-update</link>
      <description>The site is fast enough to use, but we continue to experience periodic issues.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;We will be rebooting at the top of every hour. Please don't submit posts around this time.&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Thank you for your extreme patience as we return the site to a useful state.&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-community" href="http://communities.vmware.com/community/vmtn/general/feedback" title="Feedback on VMware Communities website (no VMware product questions please)"&gt;give feedback&lt;/a&gt; | &lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-1000"&gt;known issues&lt;/a&gt; | &lt;a class="jive-link-external" href="http://www.vmware.com/communities/content/quicktour.html"&gt;quick tour&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/blogs/communities/tags">deployment</category>
      <category domain="http://communities.vmware.com/blogs/communities/tags">status</category>
      <pubDate>Tue, 25 Sep 2007 05:40:00 GMT</pubDate>
      <author>JohnTroyer</author>
      <guid>http://communities.vmware.com/blogs/communities/2007/09/24/performance-update</guid>
      <dc:date>2007-09-25T05:40:00Z</dc:date>
      <clearspace:dateToText>2 years, 1 month ago</clearspace:dateToText>
      <wfw:comment>http://communities.vmware.com/blogs/communities/comment/performance-update</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/communities/feeds/comments?blogPostID=1021</wfw:commentRss>
    </item>
  </channel>
</rss>

