Slashdot Mirror
Campaign to Open Source IBM's Notes/Domino
Ian Tree, an IT consultant from the Netherlands, has started a campaign to convince IBM to open source the code for Notes/Domino. Hoping for results similar to the push for Sun to open source Solaris, which finally saw success in 2005, Tree makes the simple point that it won't happen until someone asks. "By being an open source product, Tree is also hoping that Domino becomes something schools use to teach groupware and application development concepts, which is the holy grail for future market adoption. This is how various Unixes, relational databases, Linux, and a raft of other products eventually became commercialized. While the idea of open sourcing any proprietary program is appealing, in as much as it sets a program free to live beyond the commitment (or lack thereof) of its originator, it is hard to see why open Notes/Domino would have any more impact than OpenSolaris."
Hi, can I talk to the product manager of Outlook? Thanks, I'll hold.
Hello? Hi, I think it would be spiffy if you would consider open-sourcing Outlook. No, the whole shebang, not just the client. Yeah, server side components and everything.
I think it would prolong the life of the product since it would allow it to exist beyond your commitment to it. And you know, as the saying goes, more eyes lead to shallower bugs.
So what I'm proposing is that you open up the source and give it away for free. Then you could...
Hello? Hello?
Dumb idea. Whether you love Notes or hate it, open sourcing it would just be dumb when there's already 800 engineers working on it inside IBM. The number of developers that would contribute to it would drop dramatically.
If you want to develop open source applications ON TOP of Notes/Domino -- you can just look to http://www.openntf.org/
The patents linked to the products, makes it a no-go. Besides, IBM still makes a lot of money from Notes/Domino.
That's a fair reason in general, but the only reason I know of to interoperate with Notes is to export the data to something else.
Ah yes, Netscape. I was never a fan of Netscape. I thought MSIE was better and faster for the longest while. Netscape was, at one time, very closed. But once things got going, Firefox came out of it. Perhaps the same might happen with this? People WANT an open source groupware server and the ones that exist now seem to lack in one way or another. But perhaps a project that starts with working code, just as Firefox started out, could turn into something a lot better... something that could kick Exchange and MS Office to the curb.
Gimp is open source and it's UI sucks too.
The last I used something like that I thought you had the option of refusing it? I couldn't refuse them because it was my boss that sent the "request" and I actually liked being included on the meetings as it was better than hearing about the decisions made later on. Not that it really mattered, but every once in a while the upper management would listen (usually by accident).
Let's see, you can either have everyone keep up their calendar, or you can waste 3-5 minutes * n people in an average meeting * number of meetings in a year. There's a reason companies will pay the bucks they do for groupware licenses. Add in the workflow stuff they enable (though much of that is moving to web based apps) and they just make sense for many organizations.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
And your own appeal to authority would work better if you had a little more respect for the most popular LISP dialect in the world. Seriously.
But consider two things: First, the storage is JSON (not JavaScript), and I don't actually know that it's the on-disk format (I doubt it), only that it's the format exposed to developers. What would you use in place of it, for a schema-free database? XML? ASN.1? Serialized objects in $my_favorite_language?
And for what it's worth, JSON is not just Javascript -- it's also valid notation (as in, you can pipe it through eval, if you really want to) for Python, Ruby 1.9, and probably others I don't know about.
The only better candidate I can think of is YAML, which is more complex to parse, and a superset of JSON anyway.
Second, the views (sort of a query language) aren't necessarily Javascript. It's true, Javascript is the default view format, but it can actually be any language that can operate on text sent via a Unix pipe. I hear Python developers are using it with some success.
But given the choice, would you rather write SQL than JavaScript? Really?
Of course, it also has the nice side effect that you can write an entire application in JavaScript, using AJAX, talking directly to the CouchDB server. But I'm guessing that's a side effect, not the real reason Javascript was chosen.
Don't thank God, thank a doctor!
"who only seen the Web as a medium a few ages ago"
Only if you consider 1996 to be a few years ago. Domino's biggest problem is that it has been too far ahead of it's competitors, so it is common for people not to understand the benefits that it offers, and by the time the rest of the industry catches up, the features have been rebuild a little different, and the people who now start to understand it complain because the feature that Domino had a decade earlier doesn't look just like the program that was developed this year.
Precisely because Gimp is open source that someone was able to tweak its GUI and make GimpShop. That's qbzzt's point.
the bloated Web Mail Java Applets that refuse to download/upload, and a total mess of the Email/database system.
The Domino Web Access client was one of the very first commercial AJAX implementations and didn't use any Java whatsoever. It came out in 2001 with release 5.0.8, and could be implemented by applying a new template to your mail -- a process that could be performed by a competent administrator in about 15 seconds across an entire server.
I still cringe when hearing references to programing in Lotus Notes. The native language to Lotus Notes is the Lotus Formula language, where no looping allowed and certain functions could not be put before others for no good reason (or unpredictable side effects will occur).
False. The native language to Lotus Notes is C, and there is a comprehensive C API that has been made available since version 1. The original end-user programming language was @formulas, and was styled after the 1-2-3 formula language back in 1989. In 2002, IBM released Notes/Domino version 6, which included a comprehensive rewrite of the @formula engine to dramatically improve performance and flexibility. It also added looping constructs.
However, it's not like you couldn't do loops before. Notes 4 came out in 1994, and included Lotusscript -- a VB-like scripting language, which provided a sophisticated class model and extensive OOP capabilities. Lotusscript remains the dominant language in Notes/Domino development worldwide (though many devs on the platform are moving to Java & Javascript with the latest versions.)
Then the dreaded DbLookup function. That one function alone caused so many intradatabase dependencies that I could not remove out-of-date documents in fear of causing problems in other seemly unrelated documents in bloated Databases.
Wow. Sounds like you kept top-notch entity relationship diagrams.
If you were running a MySQL database on the backend, would you know every single application in your environment that queried every table? Would that be MySQL's fault?
Please, somebody kill Lotus Notes with FIRE!
Yeah, let's kill a platform because zildgulf doesn't know how to write and document a computer program. So it must be bad!