Josh Ledgard On MS's Future Open Source Efforts

prostoalex writes "Josh Ledgard from Microsoft, the developer responsible for open-sourcing WiX and WTL, is looking for opinions on what Microsoft should do next in regards to the open source movement that he himself established within the company. "Would you have interest in working on these types of projects with Microsoft? If not, what could entice you? If so, what would be your motivation?", asks Josh." Update: 08/24 19:04 GMT by T : As Ledgard writes on his site, "I am NOT the person responsible for the WIX/WTL projects. I cite them as examples and am working with people who where responsible for those projects to enable more of the same for the groups I work in." Sorry for the misattribution!

Comments

OpenSource IE

[drater]

Open Source IE. That's what they should do.

Office File Formats

[Anonymous Coward]

Open up the file formats for Word documents so that other programs (e.g. Open Office) can correctly decode the formatting.

What would get me interested?

[59Bassman]

Hmm...

1) Microsoft quit funding "independent" bogus TCO research to discredit OS operating systems. Oh yeah, and call off SCO.

2) Microsoft quit attempting to make all of their file formats dependent upon the OS/software that they write. The data is MINE, and I should be able to use other software to read the data. Commit to open file formats and I'd look a lot more favorably on MS.

3) Microsoft quit using draconian EULAs that make me fear that any contribution I made to a MS effort would be locked away for good once MS got a hold of it.

4) Money. Truckloads of it.

Well, maybe not so much 4, but the first 3 would be a good start.

My problem is that I've got such a bad image of Microsoft after working with their stuff for the past 12 years or so that at the end of the day I'd rather contribute effort to a "real" open source effort than anything funded by Microsoft. I just don't trust them to "do the right thing" with anything that came out of an OSS initiative.

Opensource whatever, I'm not interested

[Pingo]

I don't see any point in opensourcing any
Microsoft software except for Windows Media Player series 9 with codecs, perhaps also
Windows Media Encoder could be of some interest. //Pingo

Why ask first?

[houghi]

What I think is distuurbing that they want to askt this question. Just start the project and see who is interested. If it is interesting, people will jump aboard. If not, people will not.

It almost looks as if they know that the OSS comunity will spit them out and then the can play the underdog.

If people are interested, they can first play the nice guy who allowed the OSS comunity what they wanted and then let it blow up to proove that OSS does not work.

This is a win-win situation for them. So my question to them is, if you think that Open Source is so good, when can we help you with other parts that ARE interesting (and who need to be open by European court desision anyway). If you truly believe the project is interesting, it will create followers. If not, it will die a silent dead, as many projects that were started.

I would

[Apreche]

If Microsoft started open source projects, with "real" open source licenses I would be glad to work on them under two conditions. First, the project has to interest me. That's rather obvious that since open source work is volunteer that nobody is going to work on something that doesn't interest them. The second thing is it has to be software I can use. Since I don't run windows there are probably going to be very few MS OSS projects I would work on.

What MS SHOULD do is appeal to all the Windows developers out there. Yes, there are people out there who live in Visual Studio and love windows. They should get these people to fix all the bugs in windows and IE and such. There are people out there, willing and able to do work which the internal MS developers have failed to do multiple times over. Give someone else a try.

Re:I would

[Tarwn]

Apreche raises a good point, mod him up (I'm mod point-les right now).

The best source of Open Source developers your going to find that will work on developiung MS products in their freetime are going to be found in the Windows user groups. These are the people that run into the little problems here and there, consistently, over and over, for weeks and weeks on end. Some of them would probably bribe you to let them get in there and fix the problems. I say some because it doesn't matter wat community your part of, there is always someone who would prefer to whine to doing real work.

So start with a small windows groups of developers. Maybe give them IE as a starting place since it is not an essential product, but rather a bundled one (ie, it doesn't directly have a price). See if you can get them interested in implementing some of the newer standards, or re-implementing CSS or the JScript DOM to match the standards. Don't ask them to help, offer limited access to a SourceShare archive and a tasklist, let them work on it as they please. I'm willing to bet you'll find a lot of work getting done, especially after one of them comes back from an especially painful application install or intranet development.

I have been in the grey area, ie not a fanatic about either Linux or Windows, for years. I develop (for work) primarily with VS.Net, with occasional Web Devel mostly aimed at IE. I prefer Linux these days simply because everything happens for a reason. With Windows it's all black magic even when I kind of know what is going on under the hood based on how the system acts. It's the difference between training Gorillas based on watchng them for several years or training chimps after being given Gods notes on how and why he built them.

-T

No need to open more.

[taj]

Though I would pay attention if they open sourced .net.

What they should try doing is participating with the community rather than trying to harvest/divide it. Ship perl, python, apache... Work with some of these open source projects. Show this isnt headed the direction of mosaic, embraced and extinguished mit licensed works.

Show this isnt just some game. Otherwise, have fun.

MSFT's culture is bankrupt. They have little to bring to the table. Show they are changing their culture, come out and play.

DirectX

[GuyFawkes]

Because it is the one area where MS completely and utterly destroys Linux and the one are where Linux really needs to grow up.

Course, it won't happen, ever.

Code contribution tracking

[afreniere]

I'm being a weenie and posting this to an early reply because I think it's one of the few thoughtful replies. :P

One of the major potential benefits of contributing to open-source projects is that, when searching for a future programming job, one can point to one's open-source contributions and say "Here's some of my code, and people are using it." This works especially if one has contributed to a project with prestige - something that a Microsoft-sanctioned project would certainly have in the closed-source corporate world.

However, it can be difficult to pick out the code that one has contributed from a large project and say, "yeah, download this tgz and look at kluge.cpp lines 377-421, that's my code!" So I would propose, as a carrot to your future open-source contributors, that you design a system that keeps a database of who contributed code, how old it is, and maybe some other statistics about it. You could post a summary page for each contributor with browseable links to the code and statistics.

-Ansel.

Some light on your two items

[hummassa]

1. Id like to see a more rigid Linux Kernel API (so a module doesnt have to be recompiled between kernel maintenace versions),

This is not going to happen. Linus himself already told innumerous times that he thinks this would make unnecessarily hard to change the kernel APIs, and that, notwithstanding the point "2", below, he is not interested in binary compatibility for kernel-space things between versions of the kernel. This is right, and if you did not get it yet, I'll explain it to you: it leads to Big Bad Difficult Bugs, trying to get kernel modules to work in various kernel versions. Many things evolve from one version of the kernel to the next, many assumptions change.

2. and the 'grey' area of binary modules sorted out as well. I dont think it will happen.

This one has already happened, (*) but many people still want to pretend it didn't. Some binary modules are derived works of the kernel, and such, to be distributed at all, they must be distributed under the GPL. Some binary modules are not derived work of the kernel, and as such, they can be distributed under any license that the author seems fit. What determines if a work (in the case, a binary module) is a derived work of another (the kernel) is copyright law.

In the USofA and in Brasil, the copyright law states that a derived work is the result of some non-automated transformation of the original work. USofAn case law established the method of "abstraction, filtration, and comparison" [AFC] to determine derivation of works.

There is a myth, spread by the last paragraph of the "postamble" of the GPL, "How to Apply These Terms to Your New Programs":

This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.

I will repeat here the position I have after carefully studying the GPL, copyright law, and case law: the GPL regulates the licensing to derived works of the GPL'd work, but it cannot regulate the licensing of encompassing "anthology" works. Linking does not make a work derived on other work: to see if some work is a derived work, apply the [AFC] method. Some (not all) linking, non-derived, non-GPL'd, works can be even distributed along with a GPL'd work, because they would be covered by the "mere aggregation" clause in the 3rd paragraph of section 2 of the GPL.

And one more funny stuff: the section 6 of the GPL states:

"You may not impose any further restrictions on the recipients' exercise of the rights granted herein."

This basically means that you can't even clarify the license further than copyright law would restrict the rights of the recipient of your work (**), without rendering it undistributable by others (and even by yourself, if your work is derived from another GPL'd work).

But, OTOH, IANAL and TINLA. But I am a paralegal. IMMV and the others TFFLAs :-)

(*) Google for: "linus torvalds" abstraction filtration comparison binary
(**) Google: "hans reiser" derivative plagiarism