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.

Core modules development team first meeting

I would like to start regular meetings for everyone interested in discussing the development and modernization of the old Dnn core modules.

If you are interested in joining this first meeting, please select all available time slots you have at you can click and drag to select a time frame or even click on the date to select all day. I will then select the date and time where we can get the most people available for our first meeting. Important: Enter your email in the comments field on that selector so I can get back to you when a date and time is decided. A date and time has been decided, it will be 3PM EDT (19:00 GMT) on july 5th. Everyone is welcom, just click this link a bit before the meeting to make sure your audio settings are correct:

The current agenda for that meeting is as follows, I think these are the subjects we need to start before anything else, then we can add discussions on next meetings, but if you feel there are other subjects we need to resolve in this first meeting, feel free to comment and I will add that to this agenda.:

Core Modules Developers Group

Meeting Agenda

Date: July 5th 2018

Time: 3PM EDT (19:00 GMT)

Meeting Facilitator: Daniel Valadas

Participants: Daniel Valadas, Joe Craig, David Poindexter, Michael Onizuka, Peter Donker, Ernst Peter Tamminga, others welcome

1.      Call to order

2.      Roll call

3.      Review and adoption of agenda

4.      Approval of minutes from last meeting

5.      Open Forum

6.      Unfinished business

7.      New business

7.1.   Legal

7.1.1.     Naming
How should we name the modules that where formerly provided with Dnn: core, community, forge, something else? We need a way to differentiate them from the other free modules that never where bundled with Dnn installation.

7.1.2.     Copyright on the modules
Some modules have copyrights from the maintainer instead of Dnn, should something be done with this situation?

7.1.3.     Do we have a license template we should use?

7.1.4.     Contributor license agreement
We may not need to have one, but can we confirm this with legal.

7.2.   Maintainers
Are there specific active maintainers on some modules, do we just move on and work all together on all modules at once?

7.3.   Merge/Release process
We should agree on an approval process for merging pull request and publishing releases.

7.4.   Help needed

7.4.1.     Active Directory Authentication provider
Can someone take charge of this or help out in testing or setting up a testing environment

7.4.2.     Forums / ActiveForums           Is someone aware of the current location of the old migration script from Forums to Active Forums?           Is ActiveForums considered a community module, how was this acquisition done, do we want to bring that under the dnncommunity organization?

8.      Addendum

9.      Adjournment

And here is the meeting recording:



Daniel Valadas
Just edited the post, please enter your email in the comments field when entering your availabilities so I can get back to you when a date and time is selected. Thanks.
Daniel Valadas Tuesday, June 26, 2018 8:56 PM (link)
Daniel Valadas
A date and time has been decided:

If you are interested in joining this first meeting, please note this url and click it a few minutes before the meeting to make sure your audio settings are correct.

The meeting will be at 3PM EDT (19:00 GMT) on July 5th 2018
Daniel Valadas Wednesday, June 27, 2018 12:19 AM (link)
Craig Mitchell
Hi Daniel,
I would just like to say i am happy this is being looked into. I do feel that the quality of the community modules are something that is harder to find with the lack of the forge. Git is a fantastic platform for developers, but can be a drawn out process to none technical users when first seeing the platform. Compared to other platforms DNN is still second to none under the hood but to the none technical i feel the none technical user experiences has been lost. For a user who wants to put together a quality site without the technical knowledge it's getting harder to find skins and extensions without a substantial payout. I understand the Eco system needs to make money, just reading the blogs which I've been following on and off since DNN 2 it's getting harder to follow without feeling i'm reading msdn posts. I suppose what i'm trying to say it would be nice to have a central place for people maybe to submit open source offerings without needing to search for 2 hrs for the resource. If this could be fed back to the meeting that would be great. The Store i feel is crowded with modules that are no longer supported under current version and with maybe some monitoring to add an end of life to code that is no longer monitored as it is again making it harder to rely on for resources. Again affordable or opensource as some things like forms as 1 example modules can be up to $300+ so far out of price range for normal users unless i was an enterprise i could not even look at the store. Something i feel is needed to help bring back the opensource community to the platform.
Craig Mitchell Monday, July 2, 2018 12:19 PM (link)
Daniel Valadas
@Craig Mitchell
I totally agree that those core modules should be easier to find for a newcomer to the Dnn Platform. Many of those modules have not been maintained for a long time and need a lot of love.

So the first priority in my opinion is to bring them all under the same roof and make them all work with the latest Dnn version.

Then for a phase 2, we need to check on all issues and pull requests and iron out all bugs on each of them and have a least one responsive template or view on each module for them to be a viable production option.

For a phase 3 I think we could look at promoting them to the Dnn newcomers as great options to extend the platform, for that we need nice documentation, examples, etc. Cost is obviously a consideration for low budget customers but there is also a demand for having the source code available (no matter the cost) to not get stuck if the module developer suddenly disappears. I get asked that a lot.

This first meeting, I think is to iron out what we need to accomplish phase 1 of this project, but if we have people on board (anyone is welcome), I am willing to have those meetings on a regular basis, and for sure when we have something nice to show, awareness of the existence of these modules will be a subject to discuss.
Daniel Valadas Monday, July 2, 2018 9:37 PM (link)
Benoit Sarton
Daniel this is a great initiative. The abrupt spin off of the core modules has been a mistake and was not done very elegantly towards module developers who were left orphans without much recognition and help to continue their commitment.

I would expand point 7.1.1 to the specifics of the core modules vs 'regular modules', not only their naming or licence but also their objectives. There could be something like a 'charter for the core modules'

As a former co-lead of the 'store module' (the real developper is Gilles Le Pigocher), here are my suggestions for the 'core module charter' (or any other name):

1. is easy to find/install for a newcomer
2. share as much as possible their look and feel, so the set of core modules can be perceived as a family of modules
3. Keeps simple and easy to use.
4. leaves room for, and helps 'competitors' in the ecosystem that are better suited for more complex tasks (i.e. make it clear in their communication that there are other free or for pay alternatives that can be better alternatives)
5. Exposes as much as possible best practices and new technologies, and serves as programming example for the developpers
6. Respect and implement DNN standards and interfaces (localisation, etc)
7. Core modules leads are commited to regular meetings to keep the charter alive

See you on Thurdsay

Benoit Sarton Tuesday, July 3, 2018 6:28 AM (link)
Daniel Valadas
Thanks for your comment @Benoit Sarton and happy to know you will join the meeting. I would like to add to your point 5 (when we actually have done some more work): Maintainers will coordinate to keep modules current and compatible with the latest Dnn version.
Daniel Valadas Wednesday, July 4, 2018 7:30 AM (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