PageRenderTime 50ms CodeModel.GetById 20ms RepoModel.GetById 1ms app.codeStats 0ms

/_posts/archived/2009-04-01-aspnetmvc-open-source.aspx.markdown

https://gitlab.com/Blueprint-Marketing/haacked.com
Markdown | 75 lines | 66 code | 9 blank | 0 comment | 0 complexity | 4390320f6025c927e05b8ae32bc41fe1 MD5 | raw file
  1. ---
  2. layout: post
  3. title: "Open Source License For System.Web.Mvc"
  4. date: 2009-04-01 -0800
  5. comments: true
  6. disqus_identifier: 18604
  7. categories: [asp.net mvc,asp.net]
  8. ---
  9. First let me begin by assuring you, **this is not an April Fools
  10. joke**.
  11. ![2871423645\_2f690a0c61](http://haacked.com/images/haacked_com/WindowsLiveWriter/OpenSourceLicenseForASP.NETMVC_AE1E/2871423645_2f690a0c61_3.jpg "2871423645_2f690a0c61")Exciting
  12. news! [Scott Guthrie announced
  13. today](http://weblogs.asp.net/scottgu/archive/2009/04/01/asp-net-mvc-1-0.aspx "ASP.NET MVC 1.0")
  14. that we have released the source code for [ASP.NET
  15. MVC](http://asp.net/mvc "ASP.NET Website") 1.0 under the [Ms-PL
  16. license](http://www.opensource.org/licenses/ms-pl.html "Ms-PL at OSI"),
  17. an OSI approved Open Source license with all the rights that license
  18. entails.
  19. You can download the Ms-PL licensed source package from the [**download
  20. details page
  21. here**](http://go.microsoft.com/fwlink/?LinkId=144444 "ASP.NET MVC 1.0 Download Page").
  22. Just scroll down and look for the file named
  23. *AspNetMvc1.Ms-PL.source.zip*. My baby is growing up!
  24. A big thanks must go out to everyone involved in making this happen and
  25. to those who approved it. Its truly a team effort. When I joined
  26. Microsoft, I remember walking into ScottGus office to try and plant the
  27. seed for releasing ASP.NET MVC under the Ms-PL license. I came in armed
  28. with reasons why we should, but found him to be immediately receptive,
  29. if not already thinking along those lines. In fact, a lot of people such
  30. as [Brian Goldfarb](http://blogs.msdn.com/bgold/ "Brian Goldfarb"), my
  31. management chain, our LCA contact, etc were completely on board, which
  32. was unexpected (though maybe it should not have been) and encouraging to
  33. me.
  34. However, theres agreement to do something and the actual doing. It
  35. still a lot of people to do the leg-work to make it happen. I personally
  36. was kept me *very busy* in the days leading up to the official RTM
  37. release. Lets just say I feel like Im one course away from getting a
  38. law degree.
  39. I know one of the first questions some of you will ask is will we accept
  40. source code contributions (Ive already seen the question on Twitter :).
  41. Unfortunately, at this time the answer is no, we do not accept patches.
  42. Please dont let that stop you from [contributing in other
  43. ways](http://forums.asp.net/1146.aspx "ASP.NET MVC Forums"). The terms
  44. of the license do mean we need to stay on our toes to keep putting out
  45. compelling releases and we will work hard not to disappoint.
  46. Personally (and this is totally my own opinion), Id like to reach the
  47. point where we could accept patches. There are many hurdles in the way,
  48. but if you went back in time several years and told people that
  49. Microsoft would release several open source projects ([Ajax Control
  50. Toolkit](http://www.codeplex.com/AjaxControlToolkit "Ajax Control Toolkit"),
  51. MEF, DLR,
  52. [IronPython](http://www.codeplex.com/Wiki/View.aspx?ProjectName=IronPython "IronPython")
  53. and [IronRuby](http://www.ironruby.net/ "IronRuby"), etc….) you’d have
  54. been laughed back to the present. Perhaps if we could travel to the
  55. future a few years, well see a completely different landscape from
  56. today.
  57. However, it is a complex issue and I dont want to downplay that, but
  58. there are many of us who are looking for novel solutions and trying to
  59. push things forward. I really think in the long run, it is good for us
  60. and four our customers, otherwise we wouldnt care.
  61. But coming back to the present, Im extremely pleased with where we are
  62. now and look forward to what will happen in the future. Someone once
  63. expressed disappointment that my involvement in open source projects
  64. seriously declined after joining Microsoft. It was my hope at the time
  65. that by the time it released, it would be clear that technically, I had
  66. been working on OSS. :)