Blog Posts From Jive Talks Tagged With planet-jabber

XMPP and Web Progress: Google Wave

matt@jivesoftware.com — Wed, 30 Sep 2009 15:42:32 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.

Millions of downloads for Openfire and the Ignite Realtime products

matt@jivesoftware.com — Fri, 14 Mar 2008 00:24:05 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 — Thu, 24 Jan 2008 23:02:04 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

Jive code to be in millions of phones

greg@jivesoftware.com — Wed, 16 Jan 2008 16:16:32 GMT

Recently Gato, the lead engineer for Jive's Real Time team, came across this post from Davanum Srinivas that talks about how to use the Smack XMPP library built into Android. Smack's inclusion in Android was news to us, but we're honored that our work will be included in one of the most anticipated technology releases in the mobile world since the iPhone.

In case you haven't heard of either Android or Smack, Android is Google and the Open Handset Alliance's project to create "the first complete, open, and free mobile platform." Smack is our open source XMPP library for instant messaging and presence implemented in Java.

We're pretty excited that Smack will be used on millions of phones around the world. Thanks, Android, for picking Smack!

Only 2 Weeks Left to win $$, iPhone, and other prizes in the Clearspace Plugin Contest!

communities@jivesoftware.com — Wed, 10 Oct 2007 21:42:59 GMT

We wanted to remind everyone that you only have two weeks left to enter our Clearspace plugin contest and win cash, iPhone, t-shirts, free licenses and more!

All you have to do is submit an awesome plugin (fine print) for Clearspace by October 25th.

What can you win?

iPhone
Cash prizes up to $5000
Free 25 user license of Clearspace
Jivespace T-shirt

You can learn more about the judging / submission process and some additional prizes on Jivespace.

The Release Train

matt@jivesoftware.com — Wed, 01 Aug 2007 21:18:48 GMT

Back in April, I blogged about how we were adopting a release train model for our Open Source projects. Since then, we've rolled out the same process to our commercial products Clearspace and Jive Forums. The release train is a fairly fundamental departure from how we've done releases in the past, so we wanted to provide more details about exactly how it works.

Why did we make a switch in how we build our software? There were many motivating factors, but the general theme is "move as fast as possible with high quality". For end users of our products, the key thing to know is that there will be a new release every three weeks. Each version contains bug fixes and new features and we're committed to maintaining high quality for every release (no more rushed bug fixes a week after a release). The graphic below illustrates how this process works:

Each release (from top to bottom of the graphic) takes a total of nine weeks: three weeks of planning, three weeks of development, and three weeks of QA. All three processes run in parallel, which leads to the three week release cycle.

Answers to common questions:

Q: Do we expect customers to upgrade every three weeks?

A: No, that's unreasonable in most environments. We've made it as easy to do upgrades as possible, and we hope you'll upgrade at least once per quarter to take advantage of all the great changes. When you do upgrade, the release train process will help ensure you're on high quality code.

Q: How will version numbers work?

A: Each release will get a minor version number: 1.5, 1.6., 1.7, etc. Major version numbers will change approximately once per year.

Q: How will you develop major new features that take more than three weeks?

A: Good question. No model is perfect and we're already working on new features that will take more than one train cycle to fully finish. In those cases, we're breaking the projects into milestones and using code branches as necessary.

Other Release Train Fun

The release train has had a deeper cultural impact than just being a way that we engineer our software. The marketing team now times a lot of their work on the train, and even our major happy hours are now on the three week cycle. Late afternoon of every third Friday, we gather the company for a demo of the new features and then adjourn for partying.

Time will tell how well this new process works, but we're excited about it and the results so far are promising.

I want to put a competitive matrix on our website and our CEO doesn't

communities@jivesoftware.com — Thu, 05 Jul 2007 21:31:47 GMT

I see Dave's point. He's worried we're going to burn bridges. Not that it's a heated debate. It's not. Dave and I just thought it would be good to voice our perspectives and get feedback. Regardless, we strongly believe in how Clearspace stands up to other choices.

My idea is to have a place on our website that compares us to other applications and then allows for public comments. If people have other information or opinions they could just post them right under the matrix. Everyday, we get the "how do you compare" question. I bet your company does, too. If you're like us, there aren't any really good places to go to get that sort of information, short of consumer reports. Is the fact that no one else puts up comparison charts reason enough to not do it? What would you think of a company that did have that information public?

I do realize that it will be hard to capture everything accurately and stay on top of it, I know we'd make mistakes. But I think it's worth the risk to give it a shot. Perhaps the other idea is to just buy all those applications and host them so that people can test drive them all in one place. I mean, Saturn is doing it. You can go to their lot and test drive their competitor's cars, too.

I'd rather focus on providing customers with the information they want then to worry about potential relationship conflicts. No doubt, as much as the matrix wouldn't be intended as a commentary on other people's products it would be perceived that way. Not to mention how objective could we be, right?

My opinion is that we shouldn't worry about upsetting potential partners or other friendly companies. These are risks worth taking. We will make some people upset and some people happy.

What do you think?

Win a Trip to OSCON on Jive Software!

communities@jivesoftware.com — Fri, 29 Jun 2007 19:54:09 GMT

Win a trip to OSCON (O'Reilly's Open Source Convention) in Portland, Oregon, July 23 - 27, 2007 by creating the best blog entry about how Jive Software products have helped your organization. Your blog should be entertaining and creative while describing how you've used Jive software to make your organization better in some way. Blogs will be judged by a panel of Jive experts on the following criteria:

Thoroughness of solution description
Creativity of description
Entertainment value
Number / Quality of screen shots (minimum of two)
Number / Quality of video clips

How do I win?

Post your entry on a publicly accessible blog before 7/12/07
Send the link to your blog entry to OSCONTrip2007@jivesoftware.com no later than July 12, 2007 at 11:59 PM Pacific Time
Include your name, organization name, email, phone number, and address in the submission email
The winner will be announced on 7/13/07 and the winning submission will be posted on the Jive Talks blog

Exactly what do I win?

Jive Software will reimburse you for either

Trip costs: airfare and hotel for July 23 - 27, 2007 in Portland, Oregon USA (up to $2000 USD)

OSCON Convention Sessions Plus Tutorials (up to $1990 USD)

You should also read the fine print and content rules before entering.

Our advice to you is to do something cool with this contest and have fun! Keep in mind that our panel of judges is made up of humans, not mindless automatons, and we like to be entertained.

At ETel Launch Pad next week

communities@jivesoftware.com — Thu, 22 Feb 2007 22:00:03 GMT

Just a quick note that I'll be doing one of the seven Launch Pad Presentations next Tuesday as part of the ETel Conference. It's a pretty significant shift to add VoIP to Wildfire (not to mention all the other major features) and the ETel conference is the perfect venue.

If you'll be at the conference, please stop by the booth or grab me. I'll be with Greg Unrein, the product manager for all of our RTC applications.

IM Usage at Jive

matt@jivesoftware.com — Tue, 30 Jan 2007 01:30:06 GMT

Just for fun, I ran a usage report on our Wildfire server over the weekend. Using the archiving feature in Wildfire Enterprise, I logged how many conversations each Jive employee has participated in since we turned on stats tracking at the end of May last year. We use the light-weight archiving mode, which only records metadata about each conversation and not the actual messages being sent back and forth. Organizations subject to compliance requirements can also turn on full message archiving.

A conversation is defined as the string of messages sent back and forth without a significant time gap (15 minutes by default). The top ten users are as follows:

Name	Conversation Count
Matt T	8,198
Megan R	6,038
Derek D	5,676
Bill L	5,433
Kerry L	4,898
Sarah D	4,613
Sam L	4,488
Kelly P	4,242
Greg U	3,687
Scott C	3,661

Yes, I'm totally addicted to IM, with an average of about 47 conversations every business day. The rest of the company isn't far behind, with almost everyone else not in the top ten falling between two to three thousand conversations. It represents a staggering amount of email that we didn't have to send, as we've found that each IM conversation can represent several emails (getting a question answered over email can take several messages back and forth). That also means we've saved a lot of time, which means we've all worked more efficiently. We already think "email is the new snail mail" here at Jive. How does your company use IM?

Jivesoftware.org is now Igniterealtime.org

matt@jivesoftware.com — Tue, 05 Dec 2006 19:17:31 GMT

We just launched a new home for jivesoftware.org: igniterealtime.org. The new site has an improved UI, community blog, and better content. Why the change?

Having jivesoftware.org along with jivesoftware.com was simply confusing. The new site helps us articulate the Open Source business model more clearly and is a better home for the community.
We've been growing a lot lately -- from feature set, to community involvement, to download numbers. Both Wildfire and Spark are moving beyond the "awkward teenager" phase and ignite realtime helps us spread that message.

As always, launching a new site is way more work than one would expect and many people helped out. However, I'd like to specifically thank Contegix. They host all Jive websites and generously sponsor hosting of igniterealtime.org. Their professionalism and expert help were appreciated at 1:00 am last night as we put on the finishing site touches.

Please check out the site and let us know what you think!

Wildfire eWeek Coverage

matt@jivesoftware.com — Wed, 08 Nov 2006 18:10:45 GMT

!http://jivesoftware.com/blog/wp-content/uploads/2006/11/eweek.gif!Wildfire was just reviewed by eWeek. It's the first product review we've had that has the potential to reach 400k IT buyers, so we're pretty excited. Overall, I think we stacked up very well. They definitely got things right with the coverage of the plugin architecture and ease of use of the server. However, I wish eWeek had discussed Open Source and the vibrant Wildfire/Spark community more; I personally feel that the community is a huge driver for Wildfire's success and that it provides a lot of value to business users.

There's one other thing in the review that I wanted to specifically address, which is the claim that the Wildfire Enterprise archiving feature is not rich enough to meet regulatory compliance requirements (SOX, HIPPA, etc). We definitely don't think that's the case, so we'll have to try to follow up with the reviewer to get more information. In any case, check out the review and let us know what you think!

Wildfire HTTP Binding

alex@jivesoftware.com — Thu, 26 Oct 2006 20:39:18 GMT

We've been hard at work on one of the most requested features for Wildfire, HTTP Binding. This feature will allow clients to connect and communicate with Wildfire over HTTP, including AJAX web clients. There are several popular clients out there already utilizing the HTTP binding protocol, such as JWChat. All of these clients will benefit as they'll be able to connect to Wildfire without any extra configuration or external components as were needed before.

Performance

One of the things we've focused on in developing this feature is performance. With AJAX growing ever more popular, HTTP performance has become a huge concern for server administrators. Traditionally, HTTP servers are optimized for large numbers of short-lived requests (people clicking from web page to web page). AJAX breaks that model since web connections are held open for long periods of time. This problem directly applies to HTTP Binding since virtually all web IM client implementations use AJAX. To help improve the performance of the HTTP Binding component, we've upgraded our embedded Jetty server to its latest version, 6.0, which includes support for Java NIO ("New I/O") and continuations.

One of the main benefits of NIO is that you can have a small pool of threads handling I/O operations instead of one thread per a socket, which allows much greater scalability for large numbers of client connections. Jetty 6 also includes a continuations feature which further optimizes thread handling in the server. The standard Ajax programming model is to connect to the server and then wait until data is ready (such as a new IM message). Continuations allow the server to free up internal resources while the client is waiting. These two optimizations should allow Wildfire to handle a huge number of HTTP clients (significantly more than any other HTTP Binding implementation). We're just starting performance testing now, so stay tuned for actual numbers. We also added HTTP Binding support to connection managers, which provides furthers performance and scalability options.

Ease of Use

Like any other Wildfire feature we wanted HTTP Binding to be easy to use. The configuration of the feature is automatic -- no patching and no external components are necessary to get it up and running. The server administrator can configure the ports that is runs on and also various other settings such as how often clients can forward requests to Wildfire and how long to wait before Wildfire will consider a session inactive and invalidate it.

What's Next

The HTTP Binding feature is only one part of the equation, as it just provides the building blocks for XMPP web clients. But we're also working on direct web client support and will have more to announce soon, along with a timeframe for when HTTP Binding will make it into an official Wildfire release.

Ink Corrale

communities@jivesoftware.com — Fri, 20 Oct 2006 21:57:38 GMT

Just thought I'd round up some of the recent ink-of-note for those interested in what others are saying.

* <stron

*

< < *

**Intranet Journal Q&A with Jive Software Intranet Journal * *

< >< *

<  Open Source Enterprise IM *I * * *

< < 

***Matt Tucker on Instant Messaging (IM) in the EnterpriseEContent (podcast)* * * *

< >< 

***[Jive Software: Instant Messaging Beyond AOL, Yahoo or Microsoft |http://www.smallbiztechnology.com/avantgo/2006/10/jive-software-instant-messaging-beySmallbiztechnology * * *

< >< 

***Java Solution Provider Jive Software's Support Forums Now Available on AppExchange< Java News Desk * * *

< < 

***The market is ready***Port * * *

< >< 

***[Insider Threats Apply to SMBs|http://www.smallbizresource.com/blog.asp?blo***S
****[Instant Messaging in Java Made Easy: The Smack API|http://today.java.net/pub/a/today/2006/10/05/instant-messaging-for-jabber-with-

*****

<stron * * *

**<  [Messaging Solutions for SMBs|http://www.smallbizresource.com/documen***<strong</li>
***[Jive Software Closes Multi-Year OEM Agreement with SAP|http://www.econtentmag.com/Articles/ArticleReader.aspx?ArticleID=18037&Query=jive<stron[http://www.econtentmag.com/Articles/ArticleReader.aspx?ArticleID=18037&Query=jive]
***[Jive Software CTO, Matt Tucker, Discusses the Future of Corporate IM|http://www.ebizq.net/blogs/firstlook/2006/08/jives_open_source_corporate_im.php*<stro[http://www.ebizq.net/blogs/firstlook/2006/08/jives_open_source_corporate_im.php]
***[Wildfire Sure to Spread in Enterprises|http://www.serverwatch.com/sreviews/article.php/3628301***Serverw
***[Jive Software signs OEM deal with SAP|http://www.echannelline.com/usa/brief.cfm?item=13568**http://www.echannelline.com/usa/brief.cfm?item=13568
***[Reality Check: IM as a unified collaboration platform|http://www.computerworld.com.au/ind<strong* **<s</li>
***[Wildfire Server and Spark Client for powerful corporate Instant Messaging|http://www.davidrussell.org/2006/07/05/office-im-wildfire-server-and-spark-client/**<s</li>

Open Source Business Model: chapter 2

communities@jivesoftware.com — Mon, 09 Oct 2006 15:16:03 GMT

...in which we learn what's working with the commercial edition and make some changes. See my first post on our Open Source Philosophy for background.

I want to keep sharing how the Wildfireproject is doing from a financial perspective, and what we're doing to tweak the model so you can understand why we make decisions with the product. Unlike a lot of the larger company-sponsored open source projects, we're a bootstrapped company, so profitability is the only path to success. Plus, EIM is a very small market compared to a lot of other OSS applications (BI, CRM, etc.), so careful execution of the business model is critical.

This last quarter was an interesting one for Wildfire, most notably with the launch of Enterprise Edition in July. With the number of downloads of the OSS edition, we had expected to get a fair number of users interested in converting to the commercial edition -- this would be our first real metric in figuring out the symbiotic relationship between the two applications. We didn't expect the phone to be ringing off the hook, but (perhaps naively) expected a 1% rate of download (i.e. 1% of OSS downloaders would check out Enterprise) and a reasonable conversion process (after all, just the support and indemnity alone makes it worthwhile to a lot of companies).

The actual figure, unfortunately, was closer to .0001%. D'oh!

What happened and what have we learned?

Features: Since it was the first launch, the commercial feature set was not unique enough to convince a large number of people to try it out. EIM is an emerging market, and many people seek a basic solution. Just adding additional features like reporting and archiving is important, but it's the big value-add features (like Fastpath) that truly give the Enterprise Edition legs.
Process: The process for learning about and downloading the commercial application has been a bit cumbersome. People didn't always know that it could be easily installed as a plugin, and it was difficult for people to learn about it and why it could be really valuable to them.
Pricing: The pricing is very appealing to mid and large-sized organizations, but our smaller customers have told us it's a bit high for them.
Name: Our community have told us that they expect a product named "Enterprise" to have features that are only valuable to Fortune 1000 companies. But we had designed the product to be just as valuable to small and mid-sized organizations.

What did we do?

Name: We're keeping it as-is for now, but may change it in the near future after some more conversations with customers. Please feel free to share ideas.
Process: We have added a tab called "Enterprise" to the latest version. This makes it easy for people to learn about the features and try it out. We also want to be able to show people the usefulness of features in the context of tasks (coming later). The goal is to make it very clear what value people get by upgrading. Again, feedback is welcome.
Features: This is always improving, but we're working hard to put some great new stuff into Enterprise (and the OSS edition for that matter), but ultimately it needs to transform into a larger value-add business solution to be successful -- not just bells and whistles.
Pricing: We'll be releasing new pricing soon to make it easier for small groups to get up and running.

So, we're constantly trying to tweak the model for growth. It's a difficult process, but the OSS community (ours and other companies doing the same thing) are great at sharing what works. We'll keep you posted. In the meantime, please keep the ideas coming.