1 2 Previous Next

Jive Talks

28 Posts tagged with the eim tag

What's New at Ignite

Posted by Matt Tucker Apr 24, 2007

A lot has been happening in our Open Source community, igniterealtime.org over the past two months. In case you're not reading the Ignite blog or forums regularly, some highlights:

  • Openfire 3.3.0, Spark 2.5.1 and Smack 3.0.1 are the latest product releases. In particular, we've continued to polish the VoIP support in the products. We're also experimenting with a release train development process for Spark that may soon be applied to all Jive software product development.

  • Lots of interesting work is being done with Flash audio and video support via XMPP.

  • We're preparing a new beta of SparkWeb, our pure HTML/AJAX instant messaging client, which is part of Openfire Enterprise. A final release is due in the near future.

  • The IM Gateway plugin for Openfire is out of beta with the official 1.0 release. It provides connectivity to AIM, ICQ, Yahoo and MSN.

  • Asterisk-IM development has been kick-started by community members, lead by Stefan Reuter. Asterisk-IM is an Openfire plugin that provides integration with the Asterisk PBX, such as automatic "on the phone" presence updates.

 

0 Comments 0 References Permalink

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.

 

0 Comments 0 References Permalink

In my last icon blog, I mentioned the need to have some of the new proprietary Clearspace icons integrate well with the set of icons we were using in the rest of Clearspace. But I only showed the icons for discussion, wiki, and blog and didn't show the way they would work with some other user-facing features. Below are a few more icons a user would see. We think Firewheel Design did a good job of marrying their work with the Silk set.

 

 

3 Comments 0 References Permalink

The "Open" Organization

Posted by Dave Hersh Dec 12, 2006

One of the major recurring themes that came out of our Customer Advisory Group process around Clearspacewas the idea that opening your company up (both internally and externally) is now critical to a company's success and competitive advantage, and that this idea now has the support of the C-level execs.

 

The Idea

 

Historically, hoarding knowledge was key in order to preserve a company's "special sauce." But now the prevailing idea is that opening up the gates to share information, ideas, knowledge, and even to include partners and customers in the workflow, is pivotal to building loyalty, speeding up innovation and increasing mindshare. It's the process by which you manage the sharing of knowledge that is now becoming the real differentiator (i.e. how good are you at facilitating the flow of ideas and information). Smart companies are using communities externally to improve interactions with customers and internally to boost productivity and connectedness.

 

External communities

 

Customer and partner communities have been around for awhile, but it has mostly been just technology companies that have adopted it. Two reasons for this: 1) the primary driver is tech support (lowering incoming support calls) and tech firms are the only ones who have this problem; 2) technology companies are usually early adopters of other technologies because they have a high percentage of geeks.

 

Now however, all kinds of brick and mortar companies are seeing the benefits of community and rolling them out in the right way -- that is, with the support of the executive team, marketing and all the other stakeholders. And there is usually a visionary CIO or Marketing manager behind it (not all companies have caught on yet). A recent IBM study of Global CEO's found that "partners" and "customers" were numbers 2 and 3 on the top sources of innovation, behind employees (and before consultants, competitors, trade shows, etc.).

 

Internal communities

 

Just as important as sharing ideas with customers is the idea that "collaboration without borders" is critical to employees feeling connected to each other (and therefore loyal) and more productive. If people know who knows who, who knows what and who's working on what, they rely less on email to manage the workflow and are able to collaborate more efficiently.

 

Moreover, there are huge benefits to linking these different communities -- for example, if I'm an expert in "medical insurance claims", the customers I work with online should be aware of my reputation as well as the other employees. And if I build up expertise on the customer community, that should be represented internally.

*Summary

*

 

With C-level support, the idea of the "open" organization has momentum and structure. The companies we spoke to see this and are looking for massive productivity leaps (through good technology) and broad adoption (through elegance and ease-of-use). They believe they can chisel away at the technology silos (departmental blogs, customer communities, etc.) and turn up the volume on smarter collaboration.

 

2 Comments 0 References Permalink

On Friday, the U.S. Supreme Court's new rules on tracking e-mails and IMs went into effect. We've already had a number of people asking about the archiving features (nice to have the government help your sales efforts ).

For most companies, this likely just means an audit of their existing IT systems for capturing information and an acknowledgment of the risks (like people IM'ing using a public system over a web-based client). And that if they ever are in a lawsuit, they will be asked to turn over the IMs as part of the discovery process.

 

It seems like a reasonable step, but there is likely going to be a lot of headaches, process and cultural change...and likely some revolt by employees. I doubt it will last long though. When companies started archiving email, it was like banning smoking in restaurants -- a few painful months, and then back to business.

 

1 Comments 0 References Permalink

Wildfire eWeek Coverage

Posted by Matt Tucker Nov 8, 2006

!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!

 

2 Comments 0 References Permalink

Wildfire HTTP Binding

Posted by Alex Wenckus Oct 26, 2006

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.

 

7 Comments 0 References Permalink

Ink Corrale

Posted by Sam Lawrence Oct 20, 2006

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

*

 

  • * <stron

<strong> *

  • *

 

< </strong>< </strong>*

  • *

 

 

  • *

  • *

 

< <strong>>< </strong>*

 

 

  • * *

 

< </strong>< </strong>

 

 

  • * *

 

< <strong>>< </strong>

 

 

  • * *

 

< <strong>>< </strong>

 

 

  • * *

 

< </strong>< </strong>

 

 

  • * *

 

< <strong>>< </strong>

*****

<stron <strong> * * *

 

 

6 Comments 0 References Permalink

...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?

  1. 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.

  2. 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.

  3. 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.

  4. 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?

  1. 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.

  2. 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.

  3. 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.

  4. 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.

 

3 Comments 0 References Permalink

Intellijoin Launch

Posted by Matt Tucker Oct 5, 2006

Earlier this week, Jetbrains launched version 6.0 of their IntelliJ IDEA Java development tool. One new feature I'm particularly excited about is the ability to chat and collaborate with other developers from inside the IDE.  See the IDETalk section of their collaboration feature description -- the feature allows you to see the presence of co-workers, send code-pointers, and view one another's source files. It's all built on XMPP using our Smack library.

 

I'm happy to announce that we've partnered with Jetbrains to launch a free hosted service that allows IntelliJ users to take advantage of the feature: intellijoin.org. Just choose the "register new Jabber account" option inside IntelliJ and select intellijoin.org as the server (the default). You'll get a new account on the Intellijoin Wildfire server which will allow you to collaborate with anyone on the federated XMPP network (including Gmail contacts). Alternatively, you can install Wildfire for your own organization, which will also work great with IntelliJ.

 

This IntelliJ IDEA release is a good example of "contextual collaboration" (adding collaboration directly into an application where it makes sense). The IDETalk feature is already pretty useful and I'm excited to see how it will evolve. I expect to see many other business applications adopt contextual real-time collaboration over the next couple of years. I can only hope that others will be as visionary as Jetbrains in using an open standard (XMPP) to make it happen. The advantages to doing so are pretty clear: faster time to market with great tools like Smack and Wildfire, a huge existing install base, and interoperability with other applications that use the open standard.

 

3 Comments 0 References Permalink

Product Polish

Posted by Matt Tucker Sep 29, 2006

For me to really fall in love with an application, it's all about the little things. Not the major features that you might find in the product feature list, but all of the polish that makes an application a joy to use from day to day. We think a lot about this for Spark, so I wanted to highlight a few such polish items that have arrived with the 2.0.2 release.

 

The Ctrl-F Feature

 

[http://www.flickr.com/photos/50884898@N00/255206715/|Photo Sharing]If you have a huge contact list like I do, it can be a major pain to find someone that you want to chat with. Navigate to the right group, scan through the list of who's online, click. Instead, you can now type Ctrl-F in either the contact list or chat window. That will popup a "Find Users" widget with auto-complete. Start typing the name of the person you want to chat with and it presents you with choices. I find it to be a huge time saver, especially now that I have so many contacts with the gateways feature turned on.

 

Stale Chats

 

This one is technically not new for the 2.0.2 release (it's been around since 2.0.0). Still, it fits the "polish" theme and it's a feature that a lot of people probably aren't familiar with. If you're a typical IM user, you leave lots of chat tabs open. That can get unwieldy once there are too many. Worse, closing each chat tab can be a slow process since it takes time to figure out whether each conversation needs your continued attention or not. For Spark 2.0, we made this whole process a lot easier. Now, when a chat tab is inactive for a period of time (no messages sent or received), it will fade out slightly. That makes it easy to see which chats are "stale" and which are still active. Further, you can right click on any tab and close all stale chats. It's a quick way to clean up all your windows. Click the images below to get a better sense of how the feature works.

 

[http://www.flickr.com/photos/50884898@N00/255202871/|Photo Sharing] [http://www.flickr.com/photos/50884898@N00/255202872/|Photo Sharing]

 

Sorting in the Group Chat Browser

 

Some group chat servers such as conference.jabber.org host an enormous number of group chat rooms. That can make finding the right one a big pain. It's a simple change, but now you can sort the list of group chat rooms.

 

[http://www.flickr.com/photos/50884898@N00/255202870/|Photo Sharing]

 

Stay tuned -- we'll be adding lots more tweaks like these for future Spark releases.

 

0 Comments 0 References Permalink

Sometimes it can feel tough to get any actual work done at the office in between meetings, the deluge of email, and people interrupting to ask questions. The work done by software engineers requires concentration over long periods of time. Any engineer knows what it's like to be "in the zone" -- where your surroundings melt away and you're able to crank on code highly efficiently. The bad news is that "the zone" is a delicate state of mind. A co-worker's annoying cell-phone ringtone, an Outlook email alert, or someone stopping by your desk will snap you right out of productivity. Joel (from Joel on software) estimates that it takes about 15 minutes to achieve full concentration after an interruption. Factor in a typical engineer's salary, and the dollars of lost productivity add up quickly. In fact, some estimates peg the cost of interruptions in the workplace at 588 billion dollars per year.

 

Tips for Surviving Interruptions

  • Realize you're part of the problem. Most people say "I hate being interrupted" but will turn to their co-worker anytime they have a quick question. By being respectful of others' time and minimizing the interruptions that you initiate, you'll help foster a culture in your workplace that will allow you to work more efficiently. Other ways to be a good citizen in the office include setting your cellphone to vibrate, listening to music with headphones instead of speakers (seems obvious?), and not laughing out loud at jokes only you can see.

  • Create an office environment that's quiet and that minimizes visual distractions. At Jive, we use system furniture with tall glass partitions. This keeps the office feeling light and airy, but helps cut down on noise. If your office is noisy and you can't do anything about it, try headphones.
     
    [588 billion dollars per year|http://www.flickr.com/photos/50884898@N00/248520050/|Photo Sharing]

  • Use the best communication medium. Interrupting someone in person or by phone is the most intrusive. It forces the other person to focus their full attention on you. Everybody hates email and it just doesn't work for questions that need a quick answer. So, use instant messaging (IM). It's fast but also much less intrusive compared to other options. This is non-intuitive to some, who figure that instant messaging will only increase interruptions. We've found that IM may slightly increase the raw number of interruptions, but answering an IM is much better than having to answer a question in person since you can usually do so with only partial attention and at your own speed. IM's are also typically short and to the point (unlike email). IM is especially effective when combined with good presence management (more on that below).

  • Optimize your time. Do you really need to attend all those meetings? A good rule of thumb -- if the meeting can be held without you, you shouldn't be there. At Jive, we try to schedule all meetings that include engineers for the mornings (close to lunch time) so that afternoons are left open for focused work. We also make meetings as short as possible and have very few regularly scheduled meetings (instead only meeting when necessary). It's also helpful to block out time to get work done. For example, schedule an hour or more in your calendar to work on a tough problem, then politely communicate to your co-workers that you're heads-down.

  • Use on-line presence information. Communicating to co-workers when it's ok and not ok to be interrupted is critical. We've integrated our IM presence with our phone system using Asterisk-IM, so that we can see whenever somebody is on the phone. We've  also built a culture where people are reluctant to interrupt when they see someone's presence set to "Do Not Disturb" (DND). Although most IM clients will automatically toggle between "available" and "away" based on activity on your computer, be diligent about setting more complete presence information such as "Running errands, back at 2:30 PM".

The tips above include both technology and non-technology fixes to interruptions. Both are required to really mitigate the problem and there's no silver bullet. However, I'm a big believer that presence and instant messaging can make a big impact. What if your computer noticed you working in your IDE (programming environment) and automatically helped protect against interruptions by setting your presence and supressing non-urgent requests until you were finished? We're working on lots of interesting ideas like these.

 

How did I manage to actually get this blog post written? Headphones and the DND presence setting in Spark, of course!

 

 

4 Comments 0 References Permalink

Spark 2.0 Released

Posted by Matt Tucker Sep 11, 2006

I've previously announced Spark becoming Open Source and its source code appearing in SVN. Now, the first official Open Source release of Spark (version 2.0) is available. A lot of great stuff got packed into 2.0, including support for translations, URI mappings, gateways (for legacy IM networks), and numerous UI and performance improvements.

 

The release is the culmination of a big shift in our strategy around enterprise IM. Organizations that deploy IM don't think of the server and client as two totally separate applications. Instead, they're looking for an IM solution where both the client and server work together seamlessly to offer the best possible user experience. Our goal for Spark is ambitious but simple -- to create the best IM client for business. Why do most companies deploy Microsoft's email system? It's because their users prefer Outlook. When users demand Spark instead of Office Communicator, we'll know we're accomplishing our goal.

 

One aspect of the Spark story that I find particularly interesting is that we've built it using Java. It's been common knowledge for years that using Java for client-side applications "sucks". In fact, I personally remember having lots of worries about the platform as we started Spark development two years ago. Could we make it feel like a native application and get good performance? Well, times change and the common wisdom about client-side Java needs some updating. We've made Spark feel like a Windows app on Windows, a Mac app on OS X, etc. It's also speedy and we've even made some good strides with memory consumption. Memory usage is going to continue to be an issue for some, but computers keep shipping with more and more RAM and the Java platform keeps making big strides. Why do we use Java in Spark? We get a huge community of developers, fairly seamless cross-platform support, and great development productivity. One thing I'm excited about is the upcoming Java 6 release. It includes loads of improvements for client-side Java and will be a great platform for Spark.

 

Of course, the myriad other XMPP clients will continue to work great with Wildfire. Choice is a great thing about open standards. We hope you find Spark 2.0 to be a worthy option.

 

3 Comments 0 References Permalink

The Playa Community

Posted by Sam Lawrence Sep 8, 2006

This is my first week back in the office after attending my first Burning Man Festival.  My wife and I found it to be a powerful and inspiring experience. It's jaw-dropping to witness the amount of boundless engineering and creativity that people pour massive amounts of energy, time and money bringing to life for a week's time. The desert rockets from barren to the third most populous Nevada city, instantaneously. This year, 40,000 people came with no money or agenda to gather in the ancient lake bed.

 

It was interesting that when stripped of routine daily responsibility, how people assumed natural roles, like leaders, followers, chefs, or handimen. Even more impactful was how perfectly everything worked with 40,000 people self-managing themselves. Sorta like a real-life tag clouds. The experience did reinforce for me that communities can work amazingly well when given an open, clear space, full authority to manage themselves and when they have a powerful way to reward each other.

 

On another note, it was surprising to me to read the article that Dave sent to me about the Google guys using Burning Man as a recruiting event. At Burning Man everyone abandons their work ego. No one wants to talk or think about their career. Everyone is equal. For example, I learned later that one guy I drank coffee with had won three Academy Awards including work on Star Wars but when we talked he just shared which art he liked so far. I think it was the massive sculpture of the man on his hands and knees with gasoline pouring from his eyes into a pool of flame. That is, if I remember correctly.

 

 

5 Comments 0 References Permalink

Nimbuzz recently launched a beta version of their service. It provides free instant messaging as well as a very cool VOIP service for your mobile phone (like what Skype provides for your PC). Best of all (at least from my perspective), their IM back-end is powered by Wildfire. Nimbuzz is a great example of how communications are converging in innovative ways. As we're seeing with a number of customers, Wildfire is in the thick of that process.

 

My lame U.S. phone doesn't have J2ME support so I haven't been able to actually try the service yet. I'll have to hunt down somebody in the office with the required equipment...

 

2 Comments 0 References Permalink
1 2 Previous Next