Quote: "As we are capable of recompiling the Original DarkGDK along with the current version of DBPro for ourselves through Lee's Dark Basic SDK google source code."
From what I understand, yes. However, DarkGDK 2.0 is completely different. Many of the new features are build "on top" of the engine not within the engine itself and will not propagate backwards if you were to recompile the engine. Additionally, features such as the 250 new commands and plugin support also will not propagate back as there are most likely no exports for these functions when compiling static libraries of the engine.
Quote: "Are you going to update the google source code with your personal additional features or keeping that code to yourself?"
Coinciding with this announcement, I now have commit access to the DBP/DarkGDK source code. This means that I can now fix bugs which PureGDK has had to previously work around. I'll also be able to add new features directly to the core engine and push those updates to you faster.
Previously, as PureGDK relied upon updates getting pushed into the source tree by Lee for me, those updates would not actually appear until a new release of DBP (as PureGDK/DarkGDK 2 uses the same code base). Now the situation has reversed. When I commit a change I can release updated files immediately with a new version of DarkGDK and those changes will then make their way into DBP (albeit unsupported).
The most important part of this announcement is that DarkGDK will have a developer dedicated working on this product exclusively whereas Lee has his resources spread across many different projects. This is a very good thing for the health of DarkGDK as a whole.