MvcContrib’s version control is now managed on GitHub.com.  Thanks to Jeremy Skinner for doing the work necessary to move the Subversion repository.  Thanks to Eric Hexter for reconfiguring the TeamCity build to work with GitHub and publish artifacts to teamcity.codebetter.com.  Jeremy also has a tutorial for how to work with GitHub.

http://MvcContrib.org continues to be the main URL for the project.  It currently directs to CodePlex for all SCM except for version control.

What are we trying to do with MvcContrib?

We are trying to make it as easy as possible to contribute to the project.  Continue to contribute feedback through CodePlex and on the mailing list at http://groups.google.com/group/mvccontrib-discuss.  The source has always been in Subversion at GoogleCode, but we (Jeremy) have recently move the source onto Git so that enthusiastic contributors don’t find themselves waiting for a committer to review a patch.  Because of GitHub’s setup, forking is normal and expected.  In fact, if we are slow to review and publish a new release with your contribution, other users who want your feature can pull it straight from your public fork.  This is a way of working that is less friction than the centralized patching workflow that Subversion requires. 

I, Eric, and Jeremy are all new to Git.  Jeremy knows it much better than Eric or I at this point, but we are giving it a shot because of the great reviews we’ve heard.  We are serious about it, too.  MvcContrib has become large and wildly popular with ASP.NET MVC developers, and it is linked directly off of ASP.NET MVC’s downloads page at http://www.asp.net/mvc/download/.  MvcContrib has racked up over 50,000 downloads since the project started, and many people have contributed to it.

We want MvcContrib to continue to grow in value.  If/When Microsoft implements some features that are directly in MvcContrib, we will refactor so that we depend on the latest feature releases.  MvcContrib will also soon have a branch preparing for the ASP.NET MVC 2 release.