About a year or so ago I move almost all existing DNN core modules from CodePlex to GitHub so that it would be easier to for people to contribute bug fixes and enhancements, in line with the true nature of Open Source.
In the past months there has been some activity on the repo's. People forked the repo's, issues were mentioned and in
some cases, pull requests were submitted to improve the modules. To be honest, the amount of activity was small, but
nevertheless, the contribution was welcome.
DNN 8 creates a breaking change
Most modules will not run on DNN 8 without some intervention A minimal change incorporates at least a check for the correct DLL references,
the addition of a reference in the .ascx to DNN controls that are based on Telerik which have been moved to a separate DLL
and setting the target .NET framework to 4.5.1.
So, unless you are will to stay with DNN 7 or earlier, things have to be
done to move the core modules to a DNN8 level compatibility. And for some core modules, that is what I have been doing in the past month. Some completely by myself, some with the
help (pull requests) of others, which is great!
New releases created
In the past weeks I have created new releases for several modules:
a new release for DNN 7.4.2 and a release for DNN 8
DNN_Feedback: a new release for DNN 8
a new release for DNN 7, which is Azure compliant
DNN_Newsletter: an installable module release of the previous Admin integrated module, for DNN 8
new release for DNN 7.4.2
Apart from me, other DNN 8 compliant releases of community modules have been created as well:
DNNCE_Sitelog: an installable module release of the previous Admin integrated module, for DNN 8
DNNCE_Vendors: an installable module release of the previous Admin integrated module, for DNN 8
Nice isn't it?
There is more to come. I have one volunteer (Michael Tobisch) who is working on a complete new
DNN 8 compliant version of iFrame, including a conversion to C#, so stay tuned for more
A fair warning: since DNN8 is really a radical and breaking change I assume that the new
modules versions can have features in which we are not interested a.k.a. bugs. If you find one, please
describe the steps to reproduce these in a clean DNN8 install and create an issue in the corresponding GitHub repo.
Interested in a way to contribute?
There is a general group on GitHub for all the community modules:
Go to the repo on GitHub, fork, clone, correct, improve and enhance the module, publish the result
and, if possible, create pull requests for the original copy. And if you are interested to do a bit
more, become a project member and handle the enhancements directly on the GitHub module projects.
If you have no experience with GitHub and you are interested, come to the DNN-Connect event in June 2016 in Spain. I am working (with others) on an extensive workshop "Getting started with GitHub for DNN module development".