By time I get through responding to the comments I'm sure that almost no one will be reading anymore, but for those that stick around you get to witness this little mental exercise.
MS and Patents
A lot of people have plenty of feedback on Microsoft patents as a reason for distrust. Here are just a couple:
- Dwayne: "Well, for starters, Microsoft needs to quit hindering technology development through the use of its patent portfolio. "
- AC: "Tobacco company execs got punished for destroying lungs MS should be **punished** for stealing and attempting to PATENT a concept so general and self-evident that it is an affront to human decency. " (In reference to the SUDO example.)
I started to try and tackle this one, but then I remembered that Chris Pratley pretty much covered everything I would care to on the subject. I would deffer to what he has written for most comments about Microsoft (or any larger company) and their use of the patent system.
Patents and Participation in Microsoft Shared Source
A hold up to participation in our efforts would be the fear of patent litigation and our desire to keep the rights to whatever the community developers.
- Tux: "...trying to dilute the ideas behind free software and open source into this mish-mash of ideas, seems more intentional then serious. Talking about WIX and WTL, relased under CPL, is a good enough example. Thought open, Microsoft business-minded approach lets it keep patent rights. Unlike IBM, it does have full intention to use is at will. "
- Pete Nelson: "The reason I'm leary of your open source projects is because I'm not a lawyer. If there are patents or IP involved, I don't want it tainting my ability to work on a similar project without MS's stamp of approval. Unless the IP these projects are based on are unilaterally released into the public domain, its viewed with suspicion by many. If there is no IP of concern, that should be clearly expressed. I haven't looked, but a NDS, of course, would be the nail in the coffin. "
- James: " How do I (Microsoft) convince others that if I give access to API/program "blah" that I will not come back later with some sort of patent, copyright and/or trade secret issues and take the work of others? "
I am not a lawyer, but when I've talked to lawyers about this, most of the choices made are made in an attempt to reduce our risk in these endeavors. Believe it or not, the members of the legal team I have been working with would not like to start random David VS Goliath wars. We are mostly worried about legal action against us because of our developer taint or a community contributor unknowingly inserting code that they don't have the rights to that they may have gotten from their employer. I won't pretend to know all the answers, but there were some interesting looks on peoples faces when we went in with the following:
Using the VB Powerpack as an example... we would like to be in a world where these controls are freely available for anyone to use for whatever purpose. If a contributor would like to help with the project, then re-package a commercial offering with these controls in addition to their own specific improvements... I want to be cool with that. Hey, these controls are pretty cool so we'd also like people who download the VB Express Sku to get them for their use as well as part of the download. Ours would be the basic shared version, but the person who repackages them might also make changes and support additional features using the shared project as a base.
There were a lot of specific comments about the CPL license and what exact rights MS would want to keep. The WIX projects may choose a CPL license, but we could go with a BSD model for some of our projects. Honestly, we are still working out the details and will be starting small to test the waters with what we come up with.
PS: Oh, and my cardkey worked again today... SWEET!!!