This past weekend some discussion sprung up around a new blog engine called Oxite.  This blog engine is put out by the MIX Online team and it's used to power their blog.

Now, I'm not going to rehash some of the statements made by other members of the community since there is no point in beating a dead horse.  However, if you want check them out I suggest that first see Rob Conery's thoughts on Oxite as well as Scott Koon with TLC for Oxite post.

The thing I do want to point out is that the team is listening to what the community is saying.  Erik Porter twitted me and Derik Whittaker a reply stating,

@lozanotek @DerikWhittaker Write code and send it in. Maybe upload a patch? We're definitely looking for the right community help!

Unfortunately, the way things are setup with the Microsoft Public License (Ms-PL) and some internal processes, they can't fully accept contributions to the code.  Again, I give the team HUGE kudos for asking for guidance.

As I stated on my comment in Rob's post,

I think one important thing to note is that Oxite serves as a good example of viewing an MVC implementation from a "WebForms state of mind".

So, for those of you coming from the WebForms world, as it currently stands, Oxite shows you some of the basic applications of the MVC framework but with some of the bad habits of WebForms.  By no means, I would call it a real-world example since there is no base for the statement to either prove it or disprove it.  I would say that Oxite is a step on the direction of fully understanding what ASP.NET MVC can provide to your applications.

I will commit to this though, as soon as the project starts accepting contributions, I will be more than happy to lend a hand in their efforts.