Interesting and timely comments Shaun. Sorry I missed you in Switzerland
Great blog post, to the point.
Your face shows some doubt, but I know, seeing it by my own eyes, that you made it to the top. Let's hope that the route that DNN Corp takes, reaches the same goal.
I think Peter's face more closely reflects how I feel about our current and future progress. Rest assured... We have a plan, and we're executing it as fast as we can. Thanks for your insight, as always, Shaun. 🙂
Given the right access to both locations, it should be a straight-forward matter to import the same users into the community site and migrate/tie their forum and community related posts over to the new site and connect everything up.
it could also be a time to archive the old, show it as closed/static and redirect/advertise/promote the new location going forward.
To be more specific... I am not criticizing the initiative to create dnncommunity.org - quite the contrary, I applaud the efforts to make this happen. However I am saying that in order for this to be successful, the Community area on dnnsoftware.com needs to be completely shut down or redirected to dnncommunity.org. If this does not happen, it does not matter how much time and energy is invested in dnncommunity.org - there will not be a single "home" for the community and it will be fragmented and confusing for members. If the task is too large to migrate all of the community content from dnnsoftware.com to dnnommunity.org, or if DNN Corp is unwilling to transfer the content, I think it is better to just leave it behind and start fresh on dnncommunity.org ( this would be a significant loss however it would still be better than leaving it on dnnsoftware.com where it will cause bigger problems ). And the argument that some of the content in the community area on dnnsoftware.com is related to Evoq and needs to stay is not valid - Evoq customers are paying for support benefits which are delivered via a commercial support system - not through community channels. So the main point of my blog post is that DNN Corp needs to agree to shut down the Community area on dnnsoftware.com. If this is not part of the current community website plan it absolutely needs to be, as I am not sure if its even worth bothering with dnncommunity.org at all if this is not done, as we will be accepting a major disadvantage from the start.
Just to keep there from being any conspiracy theories generated... DNN Corp was 100% willing to help us migrate the data. They even provided some of it for some of the development that's currently underway. We weren't going to ask for users though. There would have been too many privacy and legal concerns. That would have made migration challenging to say the least. So, after some collaboration, we've decided to not migrate the content from the .com website and it will eventually be shut down. We can only do one thing at a time. :)
DNN Corp earlier took the action of making the issue-tracking Jira read-only with instructions left on the jira site, advising users to go to DNN's GitHub page to log future issues. It was per mutual agreement with the DNN Community.
I personally believe DNN Corp can have a similar arrangement to have instructions on Forum and Q&A pages advising users to post future questions in the new site. Those pages can be left in read-only mode as well on the corp site. Removing existing content will have SEO implications as it will result in lots of broken links unless someone in the community can figure out a way to set redirect rules for each of the links.
Mitchel Sellers has worked with me and Andy to come to an agreement on about 20 issues so far including giving owner permission on GitHub repository, providing anonymized update service data, full permission on nuget, etc. I do believe this is doable, all that's needed is sending an email to Andy to get his confirmation.
This is good news. As long as the community engagement features are disabled on dnnsoftware.com and there are clear links and instructions which allow people to navigate to dnncommunity.org then it will allow for a successful transition. I look forward to helping the Awareness team integrate the community modules into the new site.
Big Shame I could not make it this year, Great blog BTW and the photograph, shows when one is not a brave climber, can still pretend to be one! No one can tell the difference! :)
Your observations are spot on, Shaun, and as Will pointed out I think we'll be doing wha you suggest. And I love the picture. Not out of vanity but because it shows the differing feelings going through our community. Some will identify with you, others with me (the guy behind you on the picture, for those that don't know me). And I wish I could guide all those that feel like you to feel like me.
I see the "it has taken longer than necessary" also in light of our own capabilities. We are a group of volunteers with an ad hoc organizational structure. As we try to bootstrap ourselves to a new future it is obvious that there are (and will be) pain and delays. I agree it would have been nicer to be where we are today a lot earlier, but having been part of it I cannot see how *we* could have done better, either. DNN Corp have on the whole been cooperative and expedient when pressed (obviously our relationship has had its hiccups as well). Personally I am more in favor of keeping our eyes on a 5 year window than a 1 year window. Hopefully by that time we'll be completely severed from Evoq and on a much leaner and more manageable API. Maybe even .net core. With a thriving website and lots of Github participation.
There are no guarantees that we'll pull this off, but I remain optimistic given recent developments.
It was great seeing you in Champéry and hopefully you'll be able to fit us in on your busy schedule next year (11-14 June in Austria).
Sorry, I couldn't make it this time, I am hoping to be there next year, but certainly after that, as the schools are still not out by that week here in Canada, and I wanted to go with family. Guess what, come 2021, both the boys will be off to college, and I and my wife will have all the time to travel regardless of school schedule :).
Cheers to the next 5 years!!!
Shaun Walker has 25+ years professional experience in architecting and implementing enterprise software solutions for private and public organizations. Shaun is the original creator of Oqtane and DotNetNuke, web application frameworks which have cultivated the largest and most successful Open Source community projects native to the Microsoft platform. He was one of the original founders of DNN Corp, a commercial software company providing products, services, and technical support for DotNetNuke, which raised 3 rounds of venture capital from top tier Silicon Valley investors. Based on his significant community contributions he has been recognized as a Microsoft Most Valuable Professional (MVP) as well as an ASPInsider for over 10 consecutive years. He was recognized by Business In Vancouver as a leading entrepreneur in their Forty Under 40 business awards, was a founding member of the Board of Directors of the Outercurve Foundation, and is currently the Chair of the Project Committee for Microsoft's .NET Foundation. Shaun is currently a Technical Director and Enterprise Guildmaster at Cognizant Softvision.