| Comments

at oscon this morning, microsoft unveiled a new web site outlining positions on open source strategy.  the goal is to provide transparency into microsoft's perspective on OSS and a place where evidence and information can be shared.

you can visit the new site here: Open Source at Microsoft.

you might ask, 'what about , isn't that what it was supposed to be?' and you'd have a valid question.  port25 is the site for the open source software lab at microsoft.  it will continue to be a source for technical information with the oss technical community versus anything outlining an oss strategy.

so what else is microsoft doing in oss land?

microsoft partnered with SpikeSource in an agreement to certify all the SpikeIgnited solutions on the Windows platform.

what else?  how about microsoft's intention to submit the microsoft shared source licenses to the OSI for approval?  more details will come as the licenses are submitted to the process.  personally i think this is great.  the OSI process is a very open and public process where the licenses are vetted/commented on in open forum with the OSI.  you can read about the shared source licenses here.  this is a good thing for microsoft and the open source community.  i love the microsoft permissive license (Ms-PL) and what it provides for developers as well as certain protection it provides...it's been described as BSD-like, and is pretty good and simple, easy to understand.

so that's what is going on in microsoft open source land...we're looking forward for more to come!  today john lam will be demonstrating and talking about ironruby and the dynamic language runtime at oscon...looking forward to that one!

| Comments

well the next session block had some to choose from.  i decided one of these was going to be my choice:

i saw the .net/mono one was in the product/services track, which isn't necessarily a bad thing, but usually means that it has a product twist on it.  frank w/novell is presenting on it, and maybe i'll try to poke in.

ultimately i chose to go with the 'who gets to decide...' one as i look at the panel.  i've met brian behlendorf before and wanted to see what the panel had to say about this topic.

in 1998 when open source was coined as a term, free software already existed.  the term 'free software' caused confusion (free as in no $ or free as in no liberty).  this movement helped coined the open source term.

"now sun is pretty much a free and open source licensing company" -- hmm...pretty sweeping statement.

who is the OSI?  an open process and community discussing licensing issues.   when a new license is proposed, they start a conversation about it.  the board/committee meets and decides -- open process with the submitter on ensuring OSD compliance, etc.

current discussion on gplv3 (SugarCRM supporting this license).  chris dibona has some issue with gplv3, not because of some details, but ensuring that something called open source complies with the open source definition.

ross mayfield has a company (social text) who used a mozilla license with some modified clauses...caused some issues with some in the community, a result of a passionate community.  "users are becoming developers" in certain ways...interesting thought.  ross refers to the blog post about 'will the real open source crm please stand up' and how socialtext stopped calling themselves open source until their process was vetted through the community.  social text has the common public attribution license == mozilla+.  michael just announced that this attribution license submitted by social text (CPAL) is approved and the ink is drying as we speak.

micheal suggests we look at the history page of the definition of open source on wikipedia.  he says "terrifying."

in the definition of open source is it about the OSI maintaining its reputation? 

this is some interesting discussion but perhaps way too philisophical for this time of day or my technical dweeb mind ;-).  end of panel -- do we have an idea of who gets to decide?  i'm still confused.

i'm looking forward to bill hilf's discussion during tomorrow morning's general session...stay tuned.