An Open Letter to the OpenDS Community and to Sun Microsystems

Neil Wilson one of the founders of the OpenDS project quits and, after about two month of silence, send to the Community a letter that explain his dealing. I would like to quote this letter to give the maximum spread what happened and what are behind the people that support the open source philosophy.

"My name is Neil Wilson, and until recently I held the Owner and Committer roles in the open source OpenDS project. I helped found OpenDS, served as the project architect, and have contributed more code than anyone else. However, I must now regrettably inform you that I have been compelled to end all involvement with OpenDS. I have resigned all roles that I held in the project and have rescinded my Sun Contributor
Agreement. I will no longer contribute code, documentation, bug reports, suggestions for improvement, or advice of any kind.

I joined Sun Microsystems in October of 2001, where I was directly involved with its proprietary directory products in addition to my later work with OpenDS. I wrote and analyzed code to provide new features, fix
bugs, and improve performance, and I developed a number of tools to help improve the Directory Server experience. I had excellent working relationships with a number of customers, and I was instrumental in
closing several deals worth many millions of dollars. I consistently received the top rating in annual performance reviews, and I worked with a number of other groups within Sun, as well as with Sun partners, to
help ensure that the Directory Server products worked as well as possible with other Sun technologies, including Solaris, Java, and a number of other software products, as well as many different kinds of
hardware.

On September 27, 2007, I was notified that Directory Server engineering, including OpenDS, was being consolidated in Grenoble, France, and that US-based positions were being eliminated. Some individuals were
reassigned to work on other software products, but among those laid off were the four OpenDS project owners (myself, Stephen Shoaff, Don Bowen, and David Ely), as well as the OpenDS community manager (Trey Drake). We would technically remain Sun employees for the next two months, but were
not able to access any Sun-internal resources and were not required to work in any way and were encouraged to use that time to seek employment elsewhere.

This was certainly a very surprising move, but the shock wore off and within a few days the OpenDS owners and community manager got together and decided that even if we were no longer working for Sun that we would like to continue our involvement with OpenDS and wished to ensure that the project was in the best possible position moving forward. To that end, we had face-to-face meetings, conference calls, and e-mail
discussions with Sun employees still involved in the project to provide advice and knowledge transfers. I also continued participation on the project mailing lists, committed code changes, and updated the project
issue tracker and documentation wiki.

The project owners also decided that as an act of good faith (and without any prompting from Sun) that we should elect a fifth owner who was a Sun employee, since Sun had certainly made a significant contribution to the project. We appointed Ludovic Poitou to this position, as he had served as the architect for Sun's proprietary Directory Server product for several years, and further suggested that we should amend the project governance to ensure that Sun Microsystems was granted a permanent seat in the project ownership. On November 13, 2007, the OpenDS project owners (including Ludovic) met via conference call with the intention of discussing this governance change. However, during that meeting Ludovic informed us that Sun's intention was to change the OpenDS governance policy so that the project was controlled entirely by a Sun-selected committee. This was a surprise to us, and we indicated that while we were willing to discuss this further to better understand what was involved, we were concerned that this was not necessarily in the best interests of the OpenDS project or its associated open source community. We noted that the current OpenDS
governance policy stated that governance changes could only be made by a consensus of the project owners, and therefore we would be required to approve any potential change.

On November 14, 2007, a member of executive management within Sun's software division contacted one of the recently-laid-off OpenDS project owners and demanded that the owners approve a governance change that would grant Sun full control of the OpenDS project. During this call, we were threatened that if we did not make this change we could face immediate termination and loss of all severance benefits. The four
former-Sun owners discussed this and decided that we could not in good conscience approve the requested change as we did not believe that it would be in the best interests of the project, but we were also not
willing to risk the considerable financial loss that could result if Sun decided to make good on that threat. After first trying to resolve the issue through more amicable avenues, we were ultimately compelled to
resign our ownership and end our association with the project on November 19, 2007.

This was a very disappointing and hurtful turn of events. I believe that we acted only in good faith and in the best interests of the community, and we had clearly taken action to protect Sun's position in the project
even after our own jobs had been eliminated. OpenDS was founded as a community-focused "doacracy", and no one has done more than I have to help ensure its success, or to ensure Sun's success through OpenDS.
However, Sun management has shown that at least in this case they are willing to resort to rather hostile tactics to preserve absolute control. This is most certainly not in the spirit of open source and
open development that we tried to foster or that Sun claims to embody.

Please note that I don't feel that this action was representative of Sun's true open source strategy, but was a relatively isolated incident brought on by middle management acting of their own accord. I believe
and certainly hope that the public statements made by individuals like CEO Jonathan Schwartz and Chief Open Source Officer Simon Phipps are honest and that Sun truly does want to be a genuine community-focused open source company, and I have no reason to believe that they were
aware of or involved with any of what happened with OpenDS. Similarly, I sympathize with the remaining Sun-employed OpenDS engineers who may have been unwittingly drawn into this turmoil, and am disappointed that we will no longer be able to work together, but it was not my choice.
Unfortunately, if Sun is unable to ensure that their middle management is on the same page as the senior management setting the open source strategy and the engineers making it happen, then it won't take too many more incidents like this (or the Project Indiana / OpenSolaris Developer Preview naming fiasco) for people to start to question Sun's true intentions.

In order to avoid potential retaliation from Sun, I have remained silent on this matter through the duration of the two-month period following the layoff notification during which I was still technically a Sun
employee. Now that this time has elapsed, I am no longer at risk of losing severance benefits and I believe that it is important to clear the air. I have no desire to pursue this matter any further through
legal or other channels, but simply wish to explain why I am no longer able to be involved with the OpenDS project.

I am passionate about the technology and hope to continue working in this area in the future, but I am not yet prepared to discuss where I'm going from here. You may watch my new blog at http://directorymanager.wordpress.com/ for more information in the future.

Neil Wilson
neil.a.wilson [at]directorymanager.org"

Support Java Plug-in on 64-bit AMD and Intel

I was tring to see, surfing with firefox, if there was snow on the mountain, I like the snow and love snowboarding!!
Well I discovered that I couldn't see anything because the java plugin wasn't installed into firefox.
Oh, so easy? Well... When I upgraded my Linux to Gutsy I though to update everything to the correct configuration, I have a wonderful (?) AMD64. In other words, I change the binary from i386 to AMD64.

So everything need to be compiled to work on a 64 bit processor. Until now I had some problem, but nothing too difficult. It seems every program was compiled for AMD64 too. Until now.

I discovered with big surprise that there is no support for the java plugin on a AMD64 platform. It is really incredible. In the forllowing lines I collect some of the most interesting link about this problem and, sometime, the probably solution.

• Bug ID: 4802695 Support Java Plug-in on 64-bit AMD and Intel
• Howto Install 32 bit Firefox with Flash w/sound and Java for AMD64 - Ubuntu Forums
• HOWTO AMD64 - Gentoo Linux Wiki

OpenOffice as Windows Service AKA How to install SRVANY and live happy

Install OpenOffice as Windows Service is not so easy as it seems. You could spent an afternoon or more to understand why it wont start! So I hope this could help somebody.

To install OpenOffice as Windows Service you need two application, SRVANY.EXE and INSTSRV.EXE. You can download it from the Windows Server 2003 Resource Kit Tools at Microsoft Download Center .

I suppose you have already installed OpenOffice and you have also have started it as Administrator. It is important after the first start that you agree the license. If you first don't agree the license after the service won't start as Service.

The easiest way after you have installed OpenOffice (at this moment I have installed the version 2.3) is:

copy c:\Program Files\Windows Resource Kits\Tools\SRVANY.EXE C:\Windows\system32\

instsrv.exe "OpenOffice" c:\WINDOWS\system32\SRVANY.EXE

and add the following key into the registry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OpenOffice]
"DisplayName"="Resin - OpenOffice"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OpenOffice\Parameters]
"AppParameters"="-headless -accept=socket,host=0.0.0.0,port=8100;urp;"
"Application"="C:\\OpenOffice.org.2.3\\program\\soffice.exe"
"AppDirectory"="C:\\OpenOffice.org.2.3"

to load these lines automatically you could copy into a OpenOffice.reg file and double click on the new file.