Jive SBS Syndication Feed

XMPP and Web Progress: Google Wave

matt@jivesoftware.com — Wed, 30 Sep 2009 09:27:12 GMT

At this point, even my dad has asked me what I think about Google Wave (sorry Dad for any tech-savvy intimations!). Since Wave is in the process of rolling out to a much larger audience of testers and developers, it seemed like an appropriate time to jot down some thoughts about it. But first, an announcement: as widely discussed around the web, Wave uses the XMPP protocol under the hood and in particular works with the Openfire XMPP server (see Wave Federation install docs). Openfire was developed by Jive and we continue to sponsor it as an Open Source project. Up to this point, Openfire has been available under the GPL license. We've moved Openfire to the more liberal Apache 2.0 Open Source license, which is the same license used for the Google Wave Federation project. This change is already reflected in the Openfire source tree and an official release will be made soon. We hope and believe that the more liberal Apache 2.0 license will help unleash a new wave of innovation around Openfire (bad pun gleefully intended).

So, Wave itself -- though the project is still in the early stages (and far from ready for prime-time, especially in an enterprise setting) it's generated an enormous amount of buzz. No doubt a large part of that excitement is due to it being from Google. But more importantly, Wave is pushing the boundaries of what's possible in a web browser with a super rich and real-time user experience. It serves as inspiration to all of us that develop collaboration software. While it's still a bit early for Jive to have an official position on Wave, we're definitely following it closely and the Wave concepts align well with our roadmap. So much has been written about Wave already that I won't attempt to duplicate any of the existing detailed overviews. But I do have my personal three favorite things about Wave:

Wave will help drive adoption of HTML 5 by serving as such a compelling example of what that technology makes possible.
Wave uses XMPP as the back-end protocol. Yes, I'm a nerd for loving a protocol.
Federation is baked-in. This was a visionary move by Google and big win for an open internet in the new world of monolithic web sites/services.

It will be fun to watch where all of this goes.

Can Jive Help Make the Internet Better?

matt@jivesoftware.com — Tue, 01 Sep 2009 21:58:27 GMT

In a bid to make the internet a better place for web developers, there's been a big effort lately to kill IE 6. My favorite part of the story is Microsoft themselves, with a promise to donate food on behalf of people that upgrade from IE6 to IE8:

Our UI team regularly curses the large set of workarounds and compromises that IE6 support forces on them. Such is the reality of being an enterprise software vendor -- we still have many customers using the browser as a corporate standard (and believe it or not, there are some real reasons to delay the upgrade due to the expense of re-writing internal webapps that were specifically targeted at IE6).

On the other hand, I talk to plenty of customers and prospects that are clamoring for us to keep pushing the boundary of what's possible with social software in a web browser, especially after they've seen and tested Google Wave. Dropping IE6 will let us develop richer features faster and with less bugs. We're already committed to supporting it in our next release, but here's my question: should Jive drop official IE6 support in our release after next? No promises on timing of that release of course, but we're likely talking about late next Spring. We'll be conducting a more official survey, but your non-scientific opinion counts too! Leave a blog comment or tweet me @matttucker. And, cheers to a better internet for everyone.

JiveWorld 09 -- Technical Track Call for Speakers

matt@jivesoftware.com — Mon, 20 Jul 2009 22:27:36 GMT

The inaugural JiveWorld conference in October will include a technical track that will be chock-full of valuable content. I'm putting together the agenda for the track and am looking forward to starting to share details in the weeks ahead. But in order to make this conference great, we need your help. Are you the Jive technical guru at your organization? If so, we want you to participate in the tech track of the conference by becoming a speaker.

The conference will be a fantastic place to share tips and tricks as well as to learn how to get the most from the Jive platform. Interested in being a speaker but not sure about a topic? How about performance optimization tips or stories? Or, share details of the Jive customizations you've done. I'm looking forward to reading through your topic ideas and see you in October!

Jive at Engineering Events

matt@jivesoftware.com — Tue, 07 Jul 2009 22:00:44 GMT

We've been participating in and sponsoring several great engineering events in both Portland and the Bay Area that I wanted to highlight:

Recent Events

Portland JavaScript Admirers, June 24 -- a group of smart Javascript hackers that meets monthly to discuss cutting-edge Javascript techniques. We provided beer and pizza and look forward to participating in the future meetups.

Portland Cloud Camp, June 30 -- Portland's own iteration of the popular CloudCamp unconference series, which Jive sponsored. There were lots of great discussions and it's super relevant content for Jive given our expanding investment in cloud computing and specifically Amazon AWS. I also enjoyed attending the San Francisco CloudCamp on June 24.

Upcoming Events

CHIFOO, July 8 -- the Computer-Human Interaction Forum Of Oregon hosts monthly meetings at Jive's offices to discuss user experience, usability and interaction design.

Refresh Portland, July 23 -- a monthly event for designers interested in refreshing the creative, technical, and professional culture in the Portland area that's hosted at the Jive office.

We're adding more events to our calendar and are always interested in helping technical organizations in either Portland or the Bay Area with location space (or beer sponsorship!)

Jive's Bay Area Office

matt@jivesoftware.com — Thu, 18 Jun 2009 14:06:39 GMT

I'm pleased to report that Jive's Bay Area office is officially open! We're still getting unpacked and the office is definitely still un-finished (note the ugly cubes that were already there). But the Palo Alto location already feels like Jive and is going to be a great place to work. Some of the good and/or interesting highlights so far:

Explaining to people that there is in fact commercial space in the Town & Country center (and it's even nice)
Occasionally not being able to tell the difference between Paly High and Stanford students while at Pete's
The same snacks as the Portland office (including Red Bull and beer) -- definitely helps with the late-night coding sessions
The office "running club", which consists of me and Angela until we can hire more people that like running.

Why Palo Alto?

We're expanding our engineering team and looking for great people in the Bay (and Portland!). If you're passionate about social software and building incredible products for the world's biggest companies then we hope you'll reach out. You'll be joining the growing group in Palo Alto and the larger Jive team that's leading the social business software revolution. Please check out the job reqs for application information or drop me an email or DM.

Enterprise Cloud Computing: Announcing Jive Express

matt@jivesoftware.com — Mon, 04 May 2009 05:03:57 GMT

Today we launched Jive Express, a cloud service that lets enterprise business users get up and running with social business software within minutes. The cost is $3 a user/month and we're making the first three months or 100 users free for qualified companies. Departments and cross-company teams have never had such easy access to a collaborative social software product this powerful. It's the same incredibly rich platform that underlies our Jive SBS product along with features specifically targeted for teams like the success dashboard pictured at right. (Want to know how Jive Express stacks up to our full-blown Jive SBS platform? See the quick matrix). Other than being jazzed about the product and the fact that I got to be on the team at Jive that built it, I'm also excited about our first foray into cloud computing and the strategy we're building around it.

How is Jive approaching the cloud? We believe large organizations will embrace the cloud but that it will be a multi-year process. We want to be there to help with the transition in a pragmatic, realistic way. In the short-term, that means making it easy to transistion on and off the cloud using our single tenant architecture (see my last blog for more on single tenant cloud apps). We've used virtualization to drive amazing levels of cost efficiency while providing maximum security and data isolation. We know that enterprise companies are still in the intial stages of cloud adoption, so we're making it very easy to start there but then move to on-premise or to our more traditional hosted environment as the implementation scales. This hybrid approach is unique and we believe it's the best approach for enterprise cloud adoption. To implement all of this, we chose Amazon's AWS service as the backend cloud provider. Working with them has been a fantastic experience so far and they seem to be well on their way to solving many of the enterprise cloud concerns around security and compliance.

I plan to blog a lot more details about how we built the Jive Express service as well as our ongoing cloud ventures in the future. Also check out my interview with whurley at Infoworld for more details. In the meantime, be sure to check out the Jive Express site and signup.

Can single-tenant work for enterprise SaaS?

matt@jivesoftware.com — Mon, 30 Mar 2009 22:38:26 GMT

I spend a lot of time working on Jive's enterprise SaaS offerings. There's one question in particular we've invested quite a bit of engineering time in answering recently -- is it possible to leverage the cloud to build a scalable SaaS solution using a single tenant architecture? It's not so long ago that it felt embarrassing to say the words "Saas" and " single-tenant" in the same sentence. For years, it's been an industry mantra that it's simply impossible to have a scalable Saas business without multi-tenancy. But recent technology advances have eroded the multi-tenant advantage. And especially for the enterprise, there are important reasons why single-tenancy can actually be a better solution. I don't intend to start a flame-war over which approach is ultimately better, but I offer the top reasons my single-tenant shame is passing:

Cloud computing is changing the game. Cloud computing is anchored on virtuatlization and new levels of automation via api-based resource allocation. It's now possible to approach multi-tenant level cost efficiency with a single-tenant application. Although the cloud isn't ready for all Enterprise use-cases (due to security and compliance concerns), cloud computing is maturing very quickly.
Data isolation. Most multi-tenant applications use a single database to store all customer data. That means application bugs can put your data at risk by making it visible to other companies in the same SaaS environment. We use a separate database for each customer in addition to all the advanced data security features baked into the product, which provides much better isolation for critical data.
Migration. SaaS offers fast setup and a fantastic TCO. But current enterprise security and compliance polices around storing corporate data in the cloud can be too high of a hurdle to overcome as product usage expands from a single department to the whole organization. Because of our single-tenant architecture, we're able to offer the same product via SaaS or on-premise. Plus we make it really easy to move from one environment to the other. We believe it's the pragmatic approach, and the one best suited for enterprise.
Customization. One of our key selling points for public-facing communities is the ability to closely match an existing site's look and feel. Most multi-tenant applications end up looking cookie-cutter with just a few color changes. Jive offers much deeper levels of flexibility.

In an upcoming blog entry, I'll share further details about how we're leveraging the cloud including how we're using XMPP.

Platform Support in Clearspace 2.5

matt@jivesoftware.com — Mon, 15 Sep 2008 17:16:12 GMT

There's been some confusion (and not enough communication from us) about platform support for Clearspace 2.5, so I wanted to post details about how it all works. In order to focus QA efforts we're phasing in support for additional application servers and databases throughout the 2.5.x release cycle. The most critical thing to know is that you shouldn't attempt to upgrade to 2.5.x until your environment is supported. Or even better, consider migrating to our recommended platform configuration (see below).

The table below represents our current roadmap for platform support (the release column indicates where a particular platform is first supported). As with any roadmap, it's subject to changes based on shifting demands or unexpected issues:

Release	Application Servers	Databases	OS	Java Release
2.5.0	Tomcat 6	MySQL, Postgres	Linux	Sun JDK 1.6
2.5.1 (Sept 8)		Oracle 10 & 11
2.5.2 (Sept 29)	JBoss 4, WebSphere 6.1			IBM JDK 1.6
2.5.3 (Oct 20)	Weblogic 9.2	MS SQL Server 2005
2.5.4 (Nov 17)		IBM DB2	Windows Server 2003	IBM JDK 1.5
2.5.5 (Dec 15)			Solaris 10	Sun JDK 1.5

The breakdown of recommended and supported platforms for the 2.5.x release cycle:

	OS	JDK	Appserver	Database
Recommended	Linux (2.6 Kernel)	Sun Java 6 (Latest JDK 1.6)	Apache Tomcat 6.0.10 (or later in 6.0.x series)	Postgres 8.x
Supported	Windows Server 2003 SP2 Linux (2.6 Kernel) Solaris 10	Sun Java 6 (JDK 1.6) IBM Java 6 (JDK 1.6) Sun Java 5 (JDK 1.5) IBM Java 5 (JDK 1.5)	Apache Tomcat 6.0.10 (or later) IBM Websphere 6.1, Fixpack 11+ BEA Weblogic 9.2 JBoss 4.0.x, 4.2.x, or 4.3.x	MySQL 5.x Oracle 11.x Postgres 8.x Oracle 10.x IBM DB2 v9 MS SQL Server 2005

JDK

Appserver

Database

Recommended

Linux (2.6 Kernel)

Sun Java 6 (Latest JDK 1.6)

Apache Tomcat 6.0.10 (or later in 6.0.x series)

Postgres 8.x

Supported

Windows Server 2003 SP2
Linux (2.6 Kernel)
Solaris 10

Sun Java 6 (JDK 1.6)
IBM Java 6 (JDK 1.6)

Sun Java 5 (JDK 1.5)
IBM Java 5 (JDK 1.5)

Apache Tomcat 6.0.10 (or later)
IBM Websphere 6.1, Fixpack 11+
BEA Weblogic 9.2
JBoss 4.0.x, 4.2.x, or 4.3.x

MySQL 5.x
Oracle 11.x
Postgres 8.x
Oracle 10.x
IBM DB2 v9
MS SQL Server 2005

Finally, some information about language support roadmap in the 2.5.x series:

Release	Languages
2.5.1 (Sept 8)	English, Spanish
2.5.2 (Sept 29)	French, Simplified Chinese, German
2.5.3 (Oct 20)	Italian, Japanese

Clearspace 2.5 Officially Announced

matt@jivesoftware.com — Tue, 19 Aug 2008 04:17:46 GMT

Thanks to everyone that's participated in the 2.5 beta -- we're finally ready to officially announce Clearspace 2.5! Check out the main Jive website for details. Sam's blog entry also has a great overview of what's new in the release. You'll also notice that we updated Jivespace to 2.5, so you can trythe release here. We're doing final testing and will have the release bits available in the near future.

There's a lot in this release that's aimed at the developer crowd including many improvements to the plugin framework and a new theme resource kit for making easier changes to the UI. Check out the many new sections for developers in the Clearspace documentation. Also significant in the 2.5 release are big improvements to performance. Over the past several months, we've built out a performance test environment that's let us measure the many improvements we've been making to the code -- from a 15% improvement in some areas to over 700% in others. Overall, Clearspace 2.5 is at least a 200% faster than 2.0.

The Clearspace dev team is thrilled with the new release and we hope you'll be too. We're looking forward to your feedback!

Beta 4 Released

matt@jivesoftware.com — Wed, 13 Aug 2008 00:37:48 GMT

We just released beta 4 of Clearspace 2.5.0. Changes since the last beta:

(CS-1690) Add more field checking to the profanity filter; tags Improvements
(CS-8007) bulletted lists and outdenting
(CS-5369]) Remove developer upgrade tasks
(CS-8191) Guests can read blog posts even when they are not allowed
(CS-8109) Tasks lists are broken due to anonymous user changes
(CS-8060) Due Date not displayed when importing/exporting project tasks with combined js resources enabled
(CS-8040) Removed "hide profile fields from guests" setting
(CS-8026) Recent content shows "by" the author rather than person who recently updated
(CS-7361) Removing attachment on edit of document when document requires approval causes system error.
(CS-6697) Documents get published in moderated spaces if the user saves a draft first and then publishes it

Many thanks for all the feedback so far and please continue to help us test the release!

Beta Program Launched

matt@jivesoftware.com — Wed, 06 Aug 2008 19:22:58 GMT

We've just launched the public beta program for the next release of Clearspace. We'd love your help in making sure the code is as polished and bug-free as possible before the general release. This release is the third beta (after two private betas) of the 2.5 series. There are two ways to get involved: first, you can

download the release and install it on your own servers. You can also visit the beta sandbox site and create an account to test out a live instance and provide feedback. We're looking forward to hearing what you think!

Jive Acquires Jotlet

matt@jivesoftware.com — Mon, 07 Apr 2008 03:10:24 GMT

I'm pleased to announce that Jive Software has acquired Jotlet. Jotlet has built some amazing calendar technology that we'll be incorporating into Clearspace in a future release. The two super-talented guys behind Jotlet are joining our team in Portland from Texas.

One key way Jotlet has innovated is by building a super-rich API that allows calendars to be easily embedded into any webpage. That's a big improvement over the Google Calendar approach, which requires an iFrame and doesn't offer a customizable UI. Over time we'll be applying similar concepts to all of the collaborative tools in Clearspace so that it's easy to bring the right social and collaborative features to wherever they're needed. Visit the Jotlet website for more details about their technology and to see it in action.

Millions of downloads for Openfire and the Ignite Realtime products

matt@jivesoftware.com — Wed, 05 Mar 2008 23:28:38 GMT

We recently saw our Openfire downloads counter hit seven digits worth of downloads. The Openfire project is close to my heart and I first want to extend a sincere congratulations to my incredible team for developing the project into one that has hit 1 million downloads. Now the family of Ignite Realtime products have hit a collective download total of 3 million. The actual number of downloads is far greater because many of the Ignite products are now included in Linux distributions and are available for download from other sources. We are extremely pleased with the success of these projects and look forward to watching them grow more in the future.

I wanted to pull together numbers to provide some perspective for how significant these download numbers are. The only public number available for the other jabber servers was from ejabberd who is reporting around 160K downloads.

Openfire's ease of use and deep feature set is what's driving the downloads and installs. Here's how the Openfire features stack up vs. the others listed on jabber.org.

Products	No. of Features	No. of XEPs	No. of OSs Supported
Openfire	16	29	8
ejabberd	10	19	7
Jabber XCP	14	15	3
jabberd14	6	15	N/A
jabberd2	9	15	N/A
psyced	4	10	N/A
Tigase	7	21	8

Daniel posted about our milestone on the Ignite Realtime community, where one of our community members, Vchat20, had this to say:

Really you guys have a product that greatly stands out here. Granted, apps such as ejabberd for a flagship example have their place, but openfire is in its own class. Makes it TONS easier to configure a jabber system without having to bother digging into xml files and configuring everything from the ground up, has plenty of enterprise-class functionality, modular, and, of course, completely open.

Keep up the work on an awesome app guys.

Great work everybody and thank you to our Ignite Realtime community for all of your support! If you would like to play with our popular realtime communication software, you can download them here:

Openfire (beta of new version just released)
Spark
Smack
XIFF

XMPP (a.k.a. Jabber) is the future for cloud services

matt@jivesoftware.com — Wed, 23 Jan 2008 18:00:50 GMT

There's a new firestorm brewing in web services architectures. Cloud services are being talked up as a fundamental shift in web architecture that promises to move us from interconnected silos to a collaborative network of services whose sum is greater than its parts. The problem is that the protocols powering current cloud services; SOAP and a few other assorted HTTP-based protocols are all one way information exchanges. Therefore cloud services aren't real-time, won't scale, and often can't clear the firewall. So, it's time we blow up those barriers and come to Jesus about the protocol that will fuel the SaaS models of tomorrow--that solution is XMPP (also called Jabber) . Never heard of it? In just a couple of years Google, Apple, AOL, IBM, Livejournal and Jive have all jumped on board. Sounds good, right? So, what's the hold up? Why aren't we building out cloud services with XMPP now? And, if people are already providing cloud services without XMPP, what's the motivation to switch? The rest of this post will shed some light on the current landscape and provide some answers to those questions.

Polling isn't working anymore

Since the beginning of the Internet, if you wanted to sync services between two servers the most common solution was to have the client ping the host at regular intervals, which his known as polling. Polling is how most of us check our email. We ping our email server every few minutes to see if we got new mail. It's also how nearly all web services APIs work.

Take, for example, Twitter. High Scalability recently covered the load stats on Twitter reporting that they average 200-300 connections per second with spikes that climb to 800 connections per second. Their MySQL server handles 2,400 requests per second! Recently, the Macworld keynote became the most recent culprit for causing Twitter to cut off its API, which has 10x the load of their website. While Twitter is not a cloud service, nor the largest demand service on the internet (with a paltry 350,000ish users, which pales in comparison to a MySpace or Yahoo!), they do illustrate the kind of frustration a user experiences with polling based services. And, that's just Twitter! Imagine the impact on overall Internet traffic congestion polling creates worldwide.

Interestingly, the recent Twitter outage lead some influencers, like Dave Winer, to suggest that Twitter move to XMPP which we've already begun experimenting with

Some companies are trying to address the polling problem with existing protocols. I think that move is largely motivated by a significant investment in legacy systems that makes moving to another protocol difficult. Salesforce is a perfect example of a company attempting to address the polling problem with creative applications of the old one way protocols.

The latest version of Salesforce will send notifications back to your own webservice to avoid polling. But, that's a pain to setup for developers. Worse, its very difficult to wire up reverse webservices calls through a corporate firewall.

The hold up

XMPP's largest hurdle is that its not HTTP, and common wisdom states everything new that's built must be web-based. That means we won't see a widespread application of XMPP in cloud services until a few more brave pioneers clear the path for the rest of us.

I've been heavily involved in the XMPP world as a developer of Smack (client library) and Openfire (server) and have also helped craft the standard as a member of the XMPP Standards Foundation. XMPP was invented for instant messaging and presence, and is the dominant open protocol in that space. Instant messaging? Yep, it turns out that all of the problems that had to be solved for instant messaging make the protocol perfect for cloud computing:

It allows for easy two-way communication, so bye bye polling. It even has rich pub-sub functionality built-in.
It's XML-based and easily extensible, perfect for both new instant messaging features and custom cloud services.
It's efficient and proven to scale to millions of concurrent users on a single service (such as Google's GTalk). It also has a built-in worldwide federation model.

I'm not the only one to notice that XMPP is a great fit for cloud computing. Tivo is switching to XMPP as a more efficient alternative to their old architecture:

<div class="jive-quote">Today each TiVo polls TiVo’s severs roughly every 15 minutes to check for new scheduled recordings, TiVoCast downloads, Unbox downloads, etc. That’s highly inefficient - nearly all of those polling calls are for nothing. There is nothing waiting to be done. And it introduces a lag when you want to start a download - up to 15 minutes. And it doesn’t scale well as TiVo’s user base keeps growing.

So what’s changed? The polling system is gone. TiVo is using XMPP now instead. (...) Yep, TiVo is basically using instant messaging for real- time communication. Now when the TiVo server has a new recording to schedule, it will IM the TiVo to tell it. Or if there is a download to pull, it will IM the TiVo to tell it to do so. This is a much more efficient system and it eliminates latency. It is really a clever idea.

</div>

Fixing the polling and scaling problems with XMPP as Tivo has done is compelling, but the built-in presence functionality also offers tantalizing possibilities. Presence includes basic availability information, but is extensible and can also include things like geo-location. Imagine cloud services taking different actions based on where the client is connecting from.

More people, us included, will make the shift to XMPP, which will provide the missing evidence to create momentum toward a tipping point. In fact, I'm happy to announce that Clearspace 2.0 will include a feature that's powered by an XMPP-based cloud service. We'll be publishing a series of blog entries in the near future to discuss how we built it.

Resources for XMPP cloud service developers

There are a few places you can turn for help building cloud services around XMPP. Here is a list of a few:

XMPP Standards Foundation -- where the standard gets defined
Ignite Realtime -- Jive Software's Open Source XMPP projects
Jabber Website -- lists XMPP servers, libraries and clients

Enterprise software can be sexy AND useful

matt@jivesoftware.com — Tue, 11 Dec 2007 23:19:32 GMT

There was an interesting blogosphere battle this weekend over whether enterprise software should be "sexy". One camp says there's much to learn from the consumer space about focusing on the UI and ease of use. The other camp says there are more important fish to fry in the enterprise and that powering business processes is "sexy enough". One of my favorite links in the whole debate was to a jwz rant about how bad groupware is. Some snippets in his description of what went wrong in Netscape's evolution from a simple email client to an "enterprise" solution:

We had built this really nice entry-level mail reader in Netscape 2.0, and it was a smashing success. Our punishment for that success was that management saw this general-purpose mail reader and said, "since this mail reader is popular with normal people, we must now pimp it out to `The Enterprise', call it Groupware, and try to compete with Lotus Notes!" ...

Now the problem here is that the product's direction changed utterly. Our focus in the client group had always been to build products and features that people wanted to use. That we wanted to use. That our moms wanted to use.

"Groupware" is all about things like "workflow", which means, "the chairman of the committee has emailed me this checklist, and I'm done with item 3, so I want to check off item 3, so this document must be sent back to my supervisor to approve the fact that item 3 is changing from `unchecked' to `checked', and once he does that, it can be directed back to committee for review."

Nobody cares about that shit. Nobody you'd want to talk to, anyway. ...

If you want to do something that's going to change the world, build software that people want to use instead of software that managers want to buy.

When words like "groupware" and "enterprise" start getting tossed around, you're doing the latter. You start adding features to satisfy line-items on some checklist that was constructed by interminable committee meetings among bureaucrats, and you're coding toward an externally-dictated product specification that maybe some company will want to buy a hundred "seats" of, but that nobody will ever love. With that kind of motivation, nobody will ever find it sexy. It won't make anyone happy.There were probably lots of reasons that the Netscape releases failed, but losing focus on building software that people love had to be a major factor. Fast forward to an example from today -- have you ever met someone that actually likes using Sharepoint?

Another one of my favorite takes on this issue was Eddie Herrmann's discussion of the Enterprise Tyranny of the OR:

The enterprise question is not whether to choose between either process over people OR people over process. The answer is to be the genius that realizes that it can be both people AND process. Without this realization, you will see a change of heart in SAP's users of tomorrow that Dan talks about. If you leave people out of your priorities and omit them from your equation, they will find better tools to get their jobs done, even at the cost of your money saving, business process integration.Enterprise collaboration software has ignored the people part of collaboration for too long (which is pretty stupid isn't it?). In fact, it was an AND proposition that has made Clearspace 1.x so successful:

Its software that users love to use with features like wiki documents, blogs, and discussions, AND
It's software that works for the enterprise by combining all the next-gen tools in one product, providing integration with back-end systems, and by being available as on-premise software

Going forward, we're going to keep building out aggressively in both areas. But, it's people that have been most neglected by collaboration products in the past and we're out to prove there's a better way, which we illustrate with our positioning graph below. Look for an update from Bill next week with some hints about how Clearspace 2.0 will bring sexy back to enterprise software.