The DNN Technology Ecosystem Advisory Group has been meeting weekly for some time. After lengthy discussions and planning sessions there are some updates I would like to convey to the greater DNN community so that you are aware of what we are doing, progress being made, and plans for the future.
DNNTAG Leadership Transition
The first thing you may be wondering is, why is Mitchel Sellers providing this update...well, that’s the first update. Shaun Walker recently informed the group that while he is eager to see progress, his current schedule makes it difficult for him to lead the group. Shaun passed the leadership of the group to me and I am happy to help do my part in moving the community forward. Please know that Shaun is still involved in an advisory role within the group. His in-depth knowledge and experience is invaluable to the group.
Shutting Down DNN Tracker (Jira) in Favor of GitHub Issues
If you have tried to keep up with pull requests and Jira items recently you’ve probably noticed how difficult it is. The difficulty stems from DNNCorp using a paid-for Jira account to triage and manage issues submitted for both the platform and Evoq versions. This created a problem in that the community could not see what was going on within DNNCorp’s Jira. Pull requests were made with no issues referenced or with Jira items referenced that community members could not see.
This will not be a problem moving forward as DNNCorp is no longer going to maintain DNN Platform and associate DNN Platform items with their Jira account. Any DNN Platform issues referenced moving forward will be located on the DNN Platform GitHub page as an “issue”. This move will bring 100% transparency to the platform and our community.
I speak for the DNNTAG when I say that this change is viewed as a big win for the greater DNN Community and we hope you agree!
In order to be actionable and open up the platform so that the community can actively contribute again the DNN TAG has set 3 immediate goals:
- Community Roadmap: With the DNN Community driving DNN again it’s imperative that we share a public roadmap for where we’re heading with the platform. We are working to post an updated roadmap for everyone to see.
- Contribution Process (Pull Requests): With all DNN Platform issues going to GitHub issues it is critical that we outline the process by which a DNN Community member makes contributions to the platform. This starts with the signing of a CLA all the way to how to submit a pull request.
- Community Lead DNN Releases: Driving the platform is great, but we must reach our destination. That is, the community needs to be able to create our own releases of the platform without any assistance from DNN Corp. Ultimately we want to have continuous integration and continuous delivery integrated into the platform.
The Community Drives Again
With these recent changes it is more clear now than ever that the community is indeed driving the platform again. If you are looking to get involved, please connect with us on GitHub as we will collectively shape the future moving forward. The tasks ahead will require a lot of time, energy, effort, and communication among the DNN TAG and greater DNN Community and we are looking forward to moving the platform forward.
The DNN TAG will continue to work together to move DNN into the future. We invite you to join us by getting active and contributing to the platform and ecosystem in any way you choose. We are in for an exciting ride ahead!