Slashdot Mirror

tenchiken writes "Zimbra, an Open Source enterprise messaging app, just scored a major win. Comcast will be moving mail services to Zimbra for all of their customers. Zimbra has been picking up steam for a while now, and appears to really be challenging Microsoft in a area that Exchange has been dominated in. Add in support for Samba Domain Controllers and Linux Authentication, Offline Access and Evolution Support and we might finally have our long desired Open Source Exchange killer."

tenchiken writes "Zimbra, an Open Source enterprise messaging app, just scored a major win. Comcast will be moving mail services to Zimbra for all of their customers. Zimbra has been picking up steam for a while now, and appears to really be challenging Microsoft in a area that Exchange has been dominated in. Add in support for Samba Domain Controllers and Linux Authentication, Offline Access and Evolution Support and we might finally have our long desired Open Source Exchange killer."

tenchiken writes "Zimbra, an Open Source enterprise messaging app, just scored a major win. Comcast will be moving mail services to Zimbra for all of their customers. Zimbra has been picking up steam for a while now, and appears to really be challenging Microsoft in a area that Exchange has been dominated in. Add in support for Samba Domain Controllers and Linux Authentication, Offline Access and Evolution Support and we might finally have our long desired Open Source Exchange killer."

tenchiken writes "Zimbra, an Open Source enterprise messaging app, just scored a major win. Comcast will be moving mail services to Zimbra for all of their customers. Zimbra has been picking up steam for a while now, and appears to really be challenging Microsoft in a area that Exchange has been dominated in. Add in support for Samba Domain Controllers and Linux Authentication, Offline Access and Evolution Support and we might finally have our long desired Open Source Exchange killer."

Chris Beard was "point" on this interview, but got help writing his answers to your questions from other Mozilla and Firefox people. (Since this was sort of a "companion" interview to one we did just before it with MSIE dude Dean Hachamovitch, you might want to look at the two Q&A posts side by side and compare the way they answered.)

1) cake
by Anonymous Coward

How was the cake from MS?

Chris: It was a nice surprise actually, and we think it's great that Microsoft is taking an interest in browser development again. Of course there wasn't nearly enough of it to go around since there are thousands of people worldwide working together to make Firefox possible, but those of us at the Mountain View office made sure to enjoy it for everybody :) .

2) FireFox 2 Rendering Speed Compared to IE7
by MSTCrow5429

Dear Chris Beard, I have used Firefox since before 1.0, and one thing that Internet Explorer has always beaten FF on is rendering speed. With the release of IE7, Microsoft has made IE at least feel faster than before, and it certainly has adopted many features that made FF such a stand-out, security not withstanding. I would like to know if Mozilla has made it a priority in the past to give FF a rendering speed competitive with or faster than IE, and if we will see FF becoming competitive with or faster than IE in rendering web pages in future releases? Thanks.

Chris: Performance continues to be a high priority for us, and we test every nightly build to make sure that we're getting faster, not slower than our previous releases. We're really happy with Firefox 2, it's a very solid release with three or four times the amount of fixes and work as went into 1.5. We're hearing a lot of positive feedback about the performance of Firefox 2 as compared to Internet Explorer 7, especially on interactive web sites (even Robert Scoble recently blogged that "Firefox 2 was a LOT faster on AJAX". Zimbra, who makes a really rich web-based productivity suite also recently posted that by their internal tests, "Firefox was more than twice as fast as IE 7 and four times faster than IE 6".

But we're still looking to do better, and the next version of Gecko (the platform which is used for rendering web pages) has several improvements to our graphics infrastructure and layout engine which should continue to speed up our page rendering time. Brendan Eich recently blogged about Mozilla 2, which will contain even more improvements for performance. So yes, it's definitely something we have as a continual priority.

3) Competition
by Phroggy

What do you feel are the greatest strengths and weaknesses of Opera?

What do you feel are the greatest strengths and weaknesses of Safari?

What do you feel are the greatest strengths of IE7? (I won't ask about weaknesses...)

Chris: First of all, I just want to say that we're totally thrilled to see a revitalized ecosystem around the Web experience. That was our primary goal from the inception of Mozilla (to promote choice and innovation on the Web) and I think it's clear that users now have more choice and the Web is a much more innovative place.

Specifically and personally, I think that Opera is a great tool for fans of those really big swiss-army knives. It's an everything-in-one approach, much like the original Mozilla Suite and Seamonkey, and that totally works for some people. However, the experience can be quite overwhelming for the average Web user.

For Safari, I think they've got some excellent system integration. It's really nice that they can leverage Keychain and Address Book like they do, and of course, it's a Cocoa based application which gives it a bit of UI integration that we don't yet have. I'm a little disappointed that they're so focused on making the entire experience Apple-centric, though, and would love to see more ability for users to customize their experience and the applications they can integrate with Safari.

IE7 has taken a lot of steps forward from IE6 and it's nice to see them following along with the features introduced by Opera, Safari and Firefox -- and that have made Firefox so popular; that's a huge vindication for us, and we're flattered to be imitated. They've shipped some improvements to the standard Windows printing platform which I'm a little jealous of, but hopefully those will be part of Vista so that all Windows applications can take advantage of them, too.

4) Future?
by nine-times

What does the long-term future have in store for Firefox? Is the web browser going to become more feature rich, or is the Mozilla team going to aim at keeping Firefox very minimalist and optimized? If the former, what features do you think will help advance the user experience of the web? If the latter, how will you differentiate Firefox from its competitors and maintain the brand in absence of flashy new features?

Chris: The Firefox Charter states that our goal is to provide the most useful browser to the largest possible market while maintaining a simple interface that focuses on helping users accomplish their online tasks. That means adding the features which we think are useful for accomplishing tasks, but making sure that they're not thrust into users' faces unless they want them. We think people are doing more interactive things online these days, and are visiting more places than the average web user visited 4 or 5 years ago, so we're looking at features that help people navigate their "local web" and are also looking at providing tools for helping them act on the information they find there. If we design them right, they'll "just work" like users expect, much like we feel the Search Suggestion and Spell Checking features of Firefox 2 "just work".

5) Tackling The DOM
by x3nos

With the most recent releases of FF 2.0 and IE7 almost simultaneously, from a person who does QA for a web deliverable software company, trying to debug and locate the source of inconsistencies in the way that FF 2.0 and IE7 handles DOM - what steps is the Mozilla foundation taking to help blaze the trail for some kind of standardization in DOM? I realize that IE has its own version of DOM, but is there hope that 1) Mozilla will better respond to erratic DOM programming from those that develop for IE or that 2) Mozilla will somehow influence the Microsoft camp to come over to standards?

Chris: Compatibility with IE is something we look very seriously at (in all areas, not just the DOM API) and in the obvious cases where there's no specification (de facto or "standard") that dictates what the right thing is -- we do our best to match IE's behavior. But we also realize that trying to be bug-for-bug compatible with IE is a dead end. So, we work with the W3C and groups like the WHATWG to find the common ground and a resolution that benefits everyone. We also actively promote and encourage developing to open standards, but Microsoft's decisions in this area are obviously out of our direct control.

6) Firefox Features
by Eideewt

Firefox was created partly as an alternative to the bloated Mozilla suite. Now as Firefox matures, it too is gaining features. While all of them are fairly useful, some, such as spell check, web feed previews, and session restoration, might be better implemented as extensions. Firefox is still a fairly lightweight browser, and I appreciate Firefox 2.0's improved response speed, but I still worry that Firefox is becoming the kind of software that I hate.

How committed is the team to keeping Firefox's core as small as possible, and what, if any, features might be turned into extensions in the future?

6A) Re:Firefox Features
by diamondsw

As an add on to that question, since you can distribute extensions with the installer, why not just make these "official" extensions rather than building them into the app? Then people could easily switch them off or substitute third party ones (think tab management).

You've created a great extension management system, yet aren't using it yourselves.

Chris: A lot of the answer for question 4 here applies as well. Our community is surprisingly conservative, and we ask ourselves a lot of tough questions about whether or not a feature is really needed and used by a majority of users before we add it into Firefox. Spellchecking is a perfect example. As more and more users move to Web-based e-mail and other types of online content creation, a feature like inline spellchecking just makes sense. For those who don't need it, it's mostly out of the way and costs them nothing in terms of usability. But when you do need it, it's there, and it helps.

We're also encouraging more and more feature development as extensions, and promoting that work through programs like Mozilla Labs, as a way of allowing us to test things out before accepting them into the main product itself.

I don't know if there's a need for "official" extensions, but we are planning on making it easier to understand which extensions have been extensively tested by the Mozilla community for performance and compatibility issues, as part of an upcoming upgrade to the Firefox add-ons site.

7) Add In Validation
by Jarhead1972

Chris;

Does FF worry that an unscrupulous add-on developer could produce what could be a click-fraud capable bot net hidden in an add-on that could be promoted and distributed by FF team? What steps are taken to prevent it given the add-ons are not signed or hosted by FF?

Chris: We've got a committed team of contributors who keep a close eye on recommended extensions distributed by Mozilla. And we continue to build out the community and tools available at addons.mozilla.org to keep up with the increasing activity and demand for Firefox add-ons. We're also working on a major revision to this site that we'll be launching soon.

8) Old Bugs
by SeaFox

Has the Mozilla team considered adopting timeframes to the resolution of bugs, no matter what the severity? I've seen bugs on Bugzilla that, while minor, have been open since before the browser was named Firefox, some without any comment besides the initial confirmation they exist. Why do issues stay unaddressed after multiple major releases?

Chris: We're always evaluating and prioritizing the most important bugs. Thousands of bugs are of next to no consequence for most users and those will be prioritized below the bugs that affect large numbers of users. Putting some timeframe on bugs would encourage bug fixing around age rather than severity or visibility and that prioritization doesn't best serve the needs of our users.

Of course, we do understand that there are some issues which, while they're not a high priority for most Firefox users, might be very important to one or a small group of users and that's why we leave these Bugzilla reports open and we encourage interested people to become a part of the Mozilla project by contributing fixes for even the lower priority issues.

9) Firefox and Macs
by chrisgeleven

When will Firefox get some much needed love on Mac OS X? The toolbars look hideous, the form widgets don't look aqua like, and there is no integration into OS X services (like the dictionary). Plus there is always a need for speed improvements.

Chris: It turns out that it's hard to find developers with rich experience in application development on Mac, but we'd be happy if any passionate open-source Slashdot Mac users want to help out! We're constantly improving our platform support and Gecko 1.9 will have support for Cocoa which will improve our form widget rendering as well as the ability to integrate with OSX services.

10) Future of Thunderbird
by Kelson

Thunderbird, as a companion to Firefox, seems to be getting the "also-ran" treatment. Releases tend to trail Firefox releases by weeks or months, and there seems to be very little promotion or marketing.

Do you expect the influx of Eudora developers to change this? Are there any plans for more coordination between Firefox and Thunderbird in terms of scheduling, marketing and promotion?

Chris: Thunderbird has achieved a solid position in the email client market, with several million active users worldwide. As you note, we're focused as an organization on Firefox but we're also starting to look and think about what modern communications should look like online. Especially as we see more and more people making the Web their primary communications medium. Thunderbird has a loyal following and has made inroads into the enterprise, so any future planning around Thunderbird will take those factors into account.

-----

Thanks to everyone for all the great questions and remember that the conversation doesn't have to end here. As an open source project you can reach us through the newsgroups and other forums, or join us in our global effort to make the Web better for everyone.

twofish writes "InfoWorld columnist Peter Wayner recently reviewed six of the most popular "open source" Ajax toolkits. The article sets out to see if they are enterprise ready in comparison to commercial products such Backbase, JackBe, and Tibco's General Interface. The six open source projects covered were selected because each has a high-profile in the developer community and support of one or more stable organizations. " The toolkits covered are:

1. Dojo
2. Google Web Toolkit
3. Microsoft Atlas
4. Open Rico and Prototype
5. Yahoo AJAX Library
6. Zimbra Kabuki AJAX Toolkit

Whilst the definition of open source is broad, the round-up is quite helpful.

tachijuan asks: "My job allows me too meet many technically inclined people. Invariably we get to talking about our home setups. I've run across some very sophisticated setups. Some people I've met have enough computing and storage resources to have themselves classified as large data centers. They run this at home, and usually just for the hell of it. How do the setups of Slashdot readers measure up?" How many pieces of networked digital equipment do you have at home? "Here's a description of mine:

1. 1 x RedHat 9 quad processor PIII Xeon web server+other general duties stuff
2. 1 x FC3 router/VPN server
3. 1 x Astaro secure unix firewall/external router
4. 1 x FC3 email ( http://zimbra.com/ ) server + backup server
5. 1 x Mac G3 OSX 10.3.9 print server
6. 1 x WinXP print server/general use machine
7. 1 x WinXP general purpose home machine + TIVO media center server
8. 1 x UltraSparc 10, Solaris 9, play machine + web server
9. 2 x WinXP laptops
10. 1 x Apple PowerBook 17"
11. 1 x NetApp 630 with 1.1TB of disk serving both NFS and CIFS
12. 2 x external USB 200GB drives for backups of main data in NetApp DCF
13. 3 x inkjet printers scattered around the house
14. 1 x 8 port GigE main DCF backbone switch
15. 1 x 32 port Etherport III main home network switch
16. 1 x WRT54G switch providing high speed network for interal home use
17. 1 x befw11s4 switch + range extender for slow-speed, high range, general home use
18. 1 x TIVO!
19. 4 x spare machines laying around waiting to be purposed

By the standards of some of the people I've run accross, this is not much. To my non-techie friends, this seems either extravagant, puzzling, or both."

USSJoin asks: "I am looking for a solution which I can install on my servers, that will allow me to run my email, calendars, to-do lists, and other groupware-ish functions. Specifically, I want a solution which allows equal access through the web and over an SSH session -- so that everything I do on one is accessible through the other. After extensive googling, I found Zimbra, which is nice and AJAX-ified, but doesn't include a to-do, and doesn't seem to have any way to deal with calendar access that is not made through the web front-end. I also found Citadel, but it seems like while it's a cute solution, it's quite cobbled-together and filled with hacks. This is especially true with its major Telnet interface, which seems dangerous to me. Has anyone on Slashdot had the same problem? What solutions have you found? Are Citadel or Zimbra really great and I just don't see their true possibilities? Are there other things I should be looking at, or different ways to approach this problem?"

Nochiel writes "What is open source and why should businesses care? Why is innovation important and why isn't our company innovative? Why does it seem like everyone else is innovating while we aren't? How can we leverage Open Source? How can we implement an Open Source business strategy?" Read on for Nochiel's review. Innovation Happens Elsewhere: Open Source as Business Stratgy author Ron Goldman and Richard P. Gabriel pages 377 publisher Morgan Kaufmann Publishers rating 8 reviewer Nicholas Ochiel ISBN 1558608893 summary How to introduce open source into the enterprise as a viable and valuable business strategy.

This is a book about open source in the enterprise. It seeks to answer those questions and more. Finally, the Open Source Process has been codified in a manner that gives management the business perspective they have been yearning for.

Too often, Open Source come across as a religion. Ron Goldman and Richard Gabriel, through their sober treatment of the topic, successfully detail all the pragmatic aspects that a business should consider.

This book, to paraphrase the authors: ..is for anyone interested in a better understanding of open source--its larger history, its philosophy--, and its future prospects.

It is licensed under a Creative Commons License and is available at this link.

Chapter 1 presents the problem that the modern enterprise faces, namely: how to ensure high levels of innovation and productivity.

The reader is then introduced to the "innovation happens elsewhere" problem: High productivity requires doing less in order to produce more. This, in turn, necessitates being able to leverage other individuals'/companies' efforts. A company, therefore, has to recognize that there are more innovative forces outside the company than in it. By using these forces, a company can maintain a competitive edge. Open source is then presented as a solution to the problem.

The rest of the chapter opens the readers mind to the "new" new way of doing business., illustrates why open source is a viable business strategy and introduces the most important aspect of open source: community.

Chapter 2 discusses the "innovation happens elsewhere" dilemma in even more depth. The authors have a keen understanding on the power of the Commons and how it can make a difference.

In order to illustrate how the Commons can make a difference, the authors use the history of the Web as an example. They highlight the fact that it was built as a volunteer effort with no central planning and a small set of simple protocols. The growth of the internet then came primarily from volunteer efforts.

In this chapter, the authors successfully illustrate that a modern business can succeed only by leveraging the creativity of the Commons and engaging in conversations with a broad and dynamic set of participants in the given problem space.

Chapter 3 then tackles the most important question that managers ask: What is Open Source?

This chapter details the philosophical tenets of open source, the root of the zealotism as well as the history of open source. Many readers will find it interesting that, in the past, open source was the default methodology for leading software and scientific work!

Common myths and misconceptions are also addressed. The authors also provide an interesting comparison of the open source and agile methodologies showing how open source borrows from the strengths of the latter.

The secret sauce in open source is revealed and the various sections along the open source continuum are discussed. In particular, the authors address the value of gated communities and internal open source, a valuable discussion for those managers who wish to introduce open source into their company slowly or even extract value from only a subsection of the open source value chain.

This chapter is a complete description of the open source phenomena. As such, it can easily stand on it's own if one is looking for a quick primer.

Chapter 4 concerns itself with the business reason for adopting open source, how to develop an open source business strategy and how to create a business model that supports the open source strategy. Sun's NetBeans platform is used as a case study to illustrate the various aspects of an open source business.

This section gives possible reasons why you should open source your product as well as why you should use open source. This chapter is directed at the business strategist who wishes to understand how to implement an open source strategy and measure it's success.

Chapter 5 provides a discussion of the legal aspects of open source. It details the nature of a license, the structure of copyright, patents and types of licenses. It also covers multi-licensing, contributor agreements and licenses for documentation.

Chapter 6 concerns itself with the workings of the open source development process. An open source product is not so different from a proprietary one. It has versions, minor and major releases as well as a typical product life cycle.

The differences, where they do arise, are in the new infrastructure (and management of the same) as well as the additional responsibilities that developers are expected to take as they engage the community.

The authors also discuss joining an open source project. In particular, they emphasize that it is valuable to join an existing project if that project is already targeting the niche/functionality you wish to address with your project. This is important because it generates goodwill within the community.

Finally, open source within the company is discussed with case studies from IBM, HP and Sun.

Chapter 7 makes note of the fact that open source initiatives generally begin with middle management. As a result, middle managers encounter a number of challenges: The need to convince upper level management, get approval, acquire resources and set up the infrastructure.

This chapter provides valuable advice and strategies for individuals in this situation. (I wish I had read this chapter while at my previous employment. It would have saved me a tonne of grief.)

Chapter 8 assumes that the project is up and running. The mailing lists are functional and the public repositories are bursting with bleeding edge code. How, then, do we harvest the innovation that is happening elsewhere and build momentum?

After reading this chapter, the reader understands the value of marketing and community outreach. This is particularly valuable especially because it comes from two prominent members of the Sun community. (Sun, is the king of marketing. Their marketing efforts have made Java a household name and tool.)

Chapter 9 provides a summary of the gotcha's at various stages in the open source journey. At first, this chapter seemed superfluous as it repeats much of what has been said in previous chapters.

Upon review, however, the chapter becomes useful as a reference guide for managers as they tackle the problems that arise during implementation. The section on "recovering from mistakes" is particularly useful because a proprietary closed source company is typically used to hiding it's mistakes from customers and the world at large. The authors emphasize that it is important and valuable to fail in public especially if this failure is accompanied by an effective solution.

In Summary the title of this book is deceptive. I would have been better titled: Professional Open Source: A Manger's Guide. It is a lucid and accurate treatment of the topic.

The authors' concept of the commons is very interesting. It is one composed of things whose basic value is not diminished by making a copy. This, in my mind, is amazing! Does this mean that all projects should be open sourced? After all, software increases in value proportionally to the number of people to whom it's distributed.

The book also manages to dispel the myth of first mover advantage. In fact, first mover products rarely have the required quality to dominate the market. Perhaps this explains why open source products are rapidly eroding the market share of established applications. The proprietary stuff was a first mover relative to open source. It's quality was so bad that open source now presents a mature solution that actually works! (I can't help thinking about Zimbra in that regard)

Perhaps the most important message of the book is that there are smarter people in the world and they don't work for you! To paraphrase the authors:

Regardless of how smart, creative and innovative you believe your organization is, there are more smart, creative and innovative people outside your organization than inside. In addition, the majority of elsewhere doesn't particularly care to make products in your space.

This book should be at the bedside of any manager who is either delving into the open source world, wishes to understand what open source has to offer or seeks to clarify why open source as a business strategy will erode the market share of proprietary companies."

Carl Bialik from the WSJ writes "Ajax, or 'Asynchronous JavaScript and XML,' is allowing webpages to update as quickly as desktop software, powering applications like Google Maps and attracting money from Silicon Valley investors, including for a collaboration-software company called Zimbra. The Wall Street Journal reports: 'Zimbra's chief executive, Satish Dhamaraj, says that when he started his company in December 2003, "I really thought that Ajax was just a bathroom cleaner." Now his San Mateo, Calif., business has amassed $16 million in funding from venture-capital firms including Accel Partners, Redpoint Ventures and Benchmark Capital, the firm that famously funded eBay Inc. Peter Fenton, an Accel partner, says Ajax "has the chance to change the face of how we look at Web applications" and could boost technology spending by corporations, because Ajax is also being used to develop software for big companies, not just for consumers.'"

commonchaos writes "Recently a company named Zimbra has come out of nowhere and released an open source Exchange replacement. The exciting part is a front end that uses AJAX. There is an impressive flash demo, you can download the source or try out a "live" version of the code yourself." Interestingly, this open source system seems to be very similar to the recent Yahoo announcement covered on Slashdot.

commonchaos writes "Recently a company named Zimbra has come out of nowhere and released an open source Exchange replacement. The exciting part is a front end that uses AJAX. There is an impressive flash demo, you can download the source or try out a "live" version of the code yourself." Interestingly, this open source system seems to be very similar to the recent Yahoo announcement covered on Slashdot.

commonchaos writes "Recently a company named Zimbra has come out of nowhere and released an open source Exchange replacement. The exciting part is a front end that uses AJAX. There is an impressive flash demo, you can download the source or try out a "live" version of the code yourself." Interestingly, this open source system seems to be very similar to the recent Yahoo announcement covered on Slashdot.