Added new post on kickstarting the dev on Moq vNext

Author: kzu

_posts/2013-07-09-rebirth.md

@@ -32,7 +32,7 @@ Hence the Moq Rebirth, now in two parts: Moq SDK and Moq itself.
 
 ## Beyond Open Source
 
-Now, being open source is a great thing. But not many devs can grab a project's entire source tree and magically figure our how it works and why. Understanding how the various classes fit together, why certain implementations turned out the way they did, is tough on any non-trivial project. 
+Now, being open source is a great thing. But not many devs can grab a project's entire source tree and magically figure our how it works and why. Understanding why certain implementations turned out the way they did, and how the various classes fit together is tough on any non-trivial project. 
 
 And deep understanding of the code is precisely what's needed sometimes to carry forward a project when its owner is no longer around to do it. Or when core features need to be added to keep it alive and fresh with changing requirements.
 

_posts/2013-08-12-beyond-oss.md

@@ -0,0 +1,16 @@
+---
+layout: post
+---
+
+# Beyond Open Source
+
+At the end of my [previous post](rebirth.html) I talked about how we could go beyond "just" open source for Moq Rebirth. The basic idea was to document the creation process by having a Google+ Live Hangout, so that any number of attendees can join, but also to automatically keep a public recording of it automatically on YouTube. 
+
+[Mark Seemann](https://twitter.com/ploeh) got me thinking, however, that we could even go beyond you watching me type :). Why not just let anyone [drive too](http://en.wikipedia.org/wiki/Pair_programming)? I had seen in the past a couple products that started to offer this remote pairing capability for Visual Studio, so after googling a bit, I found one that looks very promising: [VS Anywhere](https://vsanywhere.com). And it's free for open source projects. Great!
+
+The idea is that during the hangout, the main screen getting recorded will be mine, but it will not be just me driving the keyboard all the time. In fact, I'd love to make it so that anyone that contributes, gets proper credit by having the chance to push to GitHub on their own (maybe we can even flesh out the contribution process by leveraging forks and pull requests in the sessions?). VS Anywhere would allow whoever wants to drive (and commit) to share the solution from his VS his fork of the tree with the rest of the participants (i.e. me :)), and I will get to write the tests while he writes the implementation. When we're done and agree on the implementation (it's OK to refactor!), you will commit, push to GitHub, send pull request, and I'll accept it right-away, ready to move on to the next driver. Should be a fun experiment at least, if nothing productive comes out of it in the end, hehe.
+
+
+So this is a call to action for everyone wishing to participate in Moq vNext. Please let me know at the [event scheduling page](http://www.doodle.com/az9scdziubdreagg) a day/time preference and we can start right away. I'm willing to do it very late (my time, GMT-03:00) to accomodate post-dinner time for US fellow devs, or some other time that gets the most votes. I don't expect many will be able to do it during normal working hours, so that may be best.
+
+Let's build together the most awesome mocking library ever!