Hi. I'm Brian Madden, the creator (along with Gabe Knuth) of the Mission Pinball Framework. It's exciting to see everything we've been working on getting some attention!
I can tell you 100% that not a single line of the FAST platform interface code was taken from pyprocgame. I wrote our P-ROC interface first (in June), and then when I got a FAST hardware controller about two weeks ago, I used our P-ROC platform interface as a template for the FAST interface. That's why those references to P-ROC are in there. That code was stolen by me from me, not from pyprocgame. If anyone who's familiar with the inner workings of pyprocgame looks at MPF, you'll see that they are two unique things.
I'll also let you know that no money changed hands between FAST and us in either direction. They did mail me a FAST controller a few weeks ago for free. But that's it. I met the FAST guys in Seattle earlier this year and talked to them at the NW show and explained what we were doing, and they have been very supportive.
As for their effort to not make their own Python-based framework, that was their decision. Basically I showed them what we were doing with MPF and told them that we wanted to make it work with FAST, and they essentially said, "great, so now we don't have to make our own Python framework, and the industry will be better off with a platform-independent framework." So they've absolutely been supportive in that regard. I don't know what their plans are around other frameworks, but we're excited to add FAST support to ours.
That said, I've been using a P-ROC for a few years, and Gerry Stellenberg as *also* been very supportive of what we're doing in the framework. In fact we have a Mission Pinball Framework subforum on Gerry's pinballcontrollers.com website, and we'll have our Big Shot EM-to-SS conversion running the Mission Pinball Framework on P-ROC hardware in Gerry's booth at the Expo.
So big error on my part not to clean up the comments for our FAST interface, but to be clear when you run our framework with FAST hardware, there is not one single line of code from pyprocgame there. (We do use libpinproc and pypinproc of course since those are the drivers for P-ROC.)
Also if you look at our P-ROC platform interface module (https://github.com/missionpinball/mpf/blob/dev/mpf/platform/p_roc.py), you'll see that we pulled some code for the hardware configuration of the P-ROC from pyprocgame, but that's fully credited in the comments, and pyprocgame is available via the MIT license, and since it's in our module for the P-ROC we're fine with it since it's needed to talk to a P-ROC.
Finally, as for FAST's plans for WPC2.0 and all that, at this point I don't know what their plans are, but I can tell you I would love it if some of these games were written with our framework! I know that they have some things to work out around licensing and DRM, and I hope that we can make MPF work with whatever they do so people can use MPF to write and sell officially-licensed games. (MPF itself is released under the MIT license, so anyone can do whatever they want with it.)
Oh, also I hope that P-ROC and FAST are just the tip of the iceberg for us. I talked to Ben Heck and the NW show too, and if he ever sells the PinHeck boards then I would assume we could support that too. (Even though it has its own PIC32 microprocessor, if we could get a firmware rev for it that talked USB then we should be able to add it to MPF. Same for Visual Pinball and hopefully whatever JJP has in WOZ.