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.

A Brave New World

Community puzzleIf you could add one feature to DNN what would it be? What bug is at the top of your wish list that you would like to get fixed in the next release? Is there some documentation you would like to see improved? Do you ever wonder why certain decisions are made for the platform or the community? What if I said that you can add that feature, or get that bug fixed, or help improve the documentation?

Over the last 2 weeks I have had a chance to speak to a lot of community members. I heard over and over again that people want to have more visibility into what is happening with the project.  People want to help in developing the platform. People want to get involved to help solve many of the community and platform problems, both big and little. In short people want to participate in the development and management of the platform and community.

I have long believed that the strength of an OS project is measured not by its technology or codebase, but rather by the vibrancy of its community. Many products which might be technically superior have been supplanted in the market by Open Source products due to the fanatical following they develop as part of the Open Source development model. A thriving community also has a way of much more quickly narrowing the technical gaps than might otherwise occur with a purely closed development approach.

While DNN has some big technical issues we need to tackle this next year, I think our biggest issue is addressing how we re-invigorate our community. A critical part of most successful Open Source projects is the culture of collaboration and participation that is fostered within the community. This is an area where we can make some substantial improvements that can infuse new energy and vibrancy back into the DNN community.

Community Structure

StructureAs part of re-invigorating community we have begun the task of making the DNN Community true partners in developing and maintaining the DNN Platform. The first step in this process was to create a community structure which better reflects this partnership and which gives the community a greater role in managing the platform and the community.

At the top level we have created a Steering Committee which provides oversight for the product roadmap and community changes. This Committee is comprised of both DNN Corp and Community leaders and will help guide the future direction of the DNN Platform. The steering committee initially includes Peter Donker, Ernst Peter Tamminga,  Bob Kruger, Will Morgenweck and myself.

While the steering committee will be responsible for high level strategic decisions for the platform and community, much of the week to week work will be handled by various Standing Working Groups. The standing working groups are where issues are discussed and evaluated and where plans are initially formulated. These groups may perform the needed work related to their function or may create ad-hoc working groups to perform work as they deem necessary.

Initially we have formed four standing working groups but may create others at the direction of the steering committee. These groups will have both DNN Corp and community members and will have a single member appointed to chair the group and help oversee operation of the group. This initial group leader will work with community members to define how the group will be organized. Some groups will have open membership, while other groups will be merit based where membership is by invitation only.

  1. Architecture Group - The architecture group is responsible for deciding the architectural and coding standards that are enforced for all code contributed to the project and distributed as part of the platform. This group includes community committers who have commit privileges to the platform repository on GitHub. I am happy to say that Peter Donker, Brian Dukes and Vicenç Masanas have agreed to be part of the initial group of community committers. This working group is currently led by Charles Nurse.
  2. Website Group - The website group is responsible to manage the content of the community sections of the website that have been turned over for community management. Initially this will include the platform roadmap, the community events page and a new page with curated blog posts and articles from community members. Over time we will work with the steering committee to identify other areas of the website that makes sense for the community to manage. The website group is currently led by Ernst Peter Tamminga and includes Oliver Hine who is currently managing the DNN Platform Roadmap page.
  3. Localization/Internationalization Group - The localization/i18n group is responsible for ensuring that all aspects of the platform are supported across all languages and cultures. In addition, this group will work to create the necessary tools to support the management of localization resources. The Localization/Internationalization Group will be led by Peter Donker.
  4. Training Group - The training group is responsible for developing and coordinating educational events and content for the community including community webinars, virtual conferences and platform documentation. This group will also work where possible with various community organizations like DNN-Connect and DNNCon to ensure we are providing valuable educational events and content throughout the year and to help avoid scheduling conflicts between the various events. Will Strohl is currently leading the Training group.

Both the Steering Committee and the standing working groups will have the ability to create ad-hoc working groups. The ad-hoc groups will manage work for specific projects or tasks of a limited duration and scope. They might be created to handle community contests, to focus on specific types of documentation we need created or updated or even to help organize a specific community event. Community members may also choose to create a small ad-hoc group to work on a specific feature listed in Community Voice.

For the past few years, the community has been a passive observer in the development of the DNN Platform. These changes will help ensure that the community has a more meaningful role in moving the community and the platform forward.

The changes to the community structure is just one step forward on our journey. Over the coming weeks we will make additional changes to create a more open and transparent community that works closely with DNN Corp to deliver a DNN Platform that we can all be proud of. I look forward to working with the community as we continue our amazing DNN journey.


Daniel Mettler
Thanks Joe
Who / what group will make decisions like "not to enforce any css-library" or "which best practices do we promote" or even large software-architecture issues like removing widgets or reworking the default menu-system (DDR has been troublesome for a while). Is this the architecture group?
Daniel Mettler Tuesday, August 26, 2014 2:37 AM (link)
Daniel Mettler
...or even more to my heart ATM: who architects the new CSHTML / MVP / Razor system? I believe we have loads of experience in this and could probably contribute a lot...
Daniel Mettler Tuesday, August 26, 2014 2:41 AM (link)
Tony Henrich
- I would like to see more transparency about major design decisions to the platform, either from within DNN corp or from the community. We want to ask questions or give input like "I don't think this is a good idea because..".

- Add descriptions to the APIs at a faster pace. If the DNN developers spend just 10 minutes/day adding the descriptions, we will notice big improvements to the API document with every new DNN release. It will make life easier for module developers and for submitting bug fixes from the community if we understand the inner workings of the platform. It would be very productive when the bug list is tackled at a faster rate. This will give more time for DNN developers on working on new features instead of fixing bugs.
Tony Henrich Tuesday, August 26, 2014 2:30 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