Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogCodeplex issues - Why are they Forsaken?Codeplex issues - Why are they Forsaken?
Previous
 
Next
New Post
9/16/2012 8:48 PM
 

G'day,

Blogs are a very important part of the social communication push that DNN is involved with and I would like to personally thank Chris Paterra for his involvement in the forums and with the codebase.

There are a lot of issues outstanding (63 open as at 17th Sept 2012) on http://dnnblog.codeplex.com with no sign of any review of those issues or any indication about if and when those are going to be scheduled for work.  I don't want to sound rude, but what exactly is the process at DNN corp for addressing, scheduling and prioritising issues raised by the community on this module (or any module for that matter)? 

The 5.0 edition of blogs is a big code and UI experience change, I would have expected that further minor updates would be required as the community finds issues and reports back the difficulties they have with the 5.0 blog module. Is this an unrealistic expectation from DNNCorp?

 
New Post
9/16/2012 9:21 PM
 

Hi Jamie, 

I appreciate the thanks and I understand that initial glance it may seem the project has been 'ignored'. However, if you were to look over the source code changes in the project you would see that myself and Peter Donker have spent a significant amount of time on 5.0 not only updating for the social features but also fixing the biggest bugs and deficiencies defined by the community (via voting on CodePlex). While the release notes only specify 14 or so issues as being addressed in 5.0, the real number is closer to 50 (I cleaned out the bug tracker to get it down to the count you see today). No modules available on CodePlex today have ever been run by DNN Corporation. Even my time on the Forum (almost all before I joined the company) and the blog module (done on my own free time) were not 'corporate' sponsored. The same goes for others on this very project (Peter Donker and Matthias Schlomann; who are not employees) as well as any other members of any projects on CodePlex (Wiki, Media, etc.) which have various combinations of employees and volunteers who only work on these in their free time (not all projects have a DNN Corp employee either). 

So, the current process today (management of the modules) is how it always has been since even before the company existed. Peter and I have agreed that we will continue to address issues for this specific project and eventually we will release a 5.0.1 (we have even been doing some intermediate builds exposing the changes immediately and making those available for download). 

To close this off, while I am a DNN Corp employee I am by no means making any official statement but the corporation does not schedule, prioritize and address community raised issues via CodePlex projects., I have passed information (bugs) received via support tickets (professional customers) to the various project leads who have fixed them when they were available to do so but even those bugs, prioritization of items and scheduling were all done by the volunteer leads of each project as they deemed fit.


Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
9/16/2012 11:47 PM
 
Chris,
Thanks for the update on the processes and the relationships between DNN Corp and the codeplex community.
Is it possible to upgrade the http://dnnblog.codeplex.com/SourceCon... to include support for Mecurial (HG) support? I believe project organisers at the codeplex project need to request this. I have a preference for HG over tfs/svn source control.
This would allow "me" to branch the code and tweek the area's that concern me and submit patches as required.
http://blogs.msdn.com/b/codeplex/arch...
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogCodeplex issues - Why are they Forsaken?Codeplex issues - Why are they Forsaken?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out