New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

Open, open, PULL OPEN!

More openness and ease for access

About a year or so ago I learned about GitHub: DNN moved its source to this platform so that it would be easier for people to contribute bug fixes and enhancements, in line with the true nature of Open Source. 

The move of DNN was not very successful in the first period, but slowly people got used to the possibility to contribute and working with GitHub. As a result, the # of contributions is growing and growing! See the community blog post of Joe Brinkman with an excellent illustration of growth in participation of the community in new releases of the platform.

I have been struggling with GitHub in the beginning: it is so much different from TFS, the source control system that I am used to, both in my professional environment as well as with CodePlex for several DNN modules: Events, FAQ and Reports.

I am jealous

During the last year I have become a bit jealous with regards to code fixes that were submitted for DNNPlatform. Together with several people, most notably Roger Selwyn, I have been maintaining the DNN Events module for more than 7 years, with success. But if I look back, the number of code donations by others than Roger and me can be counted on the fingers of one hand. In short: all changes have been done by the people in the module team, processing dozens of requests of DNNEvents users. 

I will not try to analyze why there were so few code donations, I just conclude that that was the way it was over the last years. And yes, WAS the way it was, because I have changed things!

TRANSFERRING core modules sources to GitHub

With some help of of Joe Brinkman, I have created GitHub repositories for the source of several (former core) DNN modules: Events, Faq, Reports.

Moving the source project of these modules to GitHub was not a simple step. My initial idea was to move the complete source history of the modules from the CodePlex source control to GitHub. So I requested CodePlex support to change the source control for the modules from TFS to Git, I created a clone of the CodePlex/Git locally, created a new remote repository on GitHub and pushed my local clone of the TFS repository to the GitHub repository. 

That did not work out the way I wanted. The repos on GitHub contained a lot of old material, the module project structures were not clear, there were folders with files that were irrelevant for the current state of the modules. So I decided to start all over again and create repos on GitHub with (only) the source of the most recent version of the modules and forget all old material. That turned out to provide a better result: clean, straight forward.

DNN Community page on GitHubCore modules on GitHub

Where can you find the repos? There is a general group on GitHub for all the community modules:

And you will find the core module repos there:

In the upcoming period, I will (motivate to) move the source of other core modules to GitHub as well, if the current projects owner agree on that. For the first three I could decide myself.  Limiting the first round to those three is a nice way to get some real life experience in working in a new way.

Distribution on CodePlex

Distribution of the install packages, documentation and issue handling will remain on CodePlex, so you will find the end results in the familiar location. But I (we) will maintain and improve the source code via GitHub. Getting your version of the source is now a standard Git process: Fork & Clone! And if you start improving the module, don't forget to produce pull requests, DNN is Open Source!


Phil Speth
I would love to see the feedback module improve.
It is a good module with great potential.
Phil Speth Sunday, February 8, 2015 9:46 AM (link)
Ernst Peter Tamminga
@Phil; Roger Selwyn is currently handling the lead on the Feedback module. You could contact him to see if you can assist him?
Ernst Peter Tamminga Monday, February 9, 2015 5:52 AM (link)
Joe Brinkman
I'll be talking with the other module leads to see about getting them all moved over to GitHub. I think once people get used to contributing on one project, the barrier to entry for contributing to multiple projects becomes much lower.
Joe Brinkman Monday, February 9, 2015 5:28 PM (link)

Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Daniels (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out