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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Are developers contributing code and bug fixes?Are developers contributing code and bug fixes?
Previous
 
Next
New Post
1/28/2009 1:56 AM
 

Salama wrote
 

Plus the story for the modules is also sad. For example the store module. It seems the speed of progress is like molasses. I can't get timely replies and when I do after several days, it's still nothing satisfactory. Developers ask for help and when you offer it, they are not response. I am finding the whole situation frustrating.

The store module is not a very good example of a sad story. The module is thriving, and saw 9 beta releases over the past year, and the team is ready to release the next major version (2.2). Also, recently, the team has been beefed up with Benoit Sarton as co team lead, and Robert Collins as team member.

 


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
1/28/2009 11:14 AM
 

 

So why are these releases obscured from the public? Committed changes of DNN are not visible to the public. We can't test the bug fixes. CodePlex has no change sets.

 

The last recent beta version of the store is 02.01.09 on a French site. I specifically asked the team lead about the recent changes a month ago and I am still waiting for an answer and now you're saying 2.2 (never heard of it) is going to be released soon.

I don't know about the other modules but my guess they have similar issues.

It seems to me that the public is not able to get involved more in a more proactive way. You guys keep asking for public contributions and involvement but you're not making it easy and friction free for us.

 
New Post
1/28/2009 2:15 PM
 

Salama wrote

So why are these releases obscured from the public? Committed changes of DNN are not visible to the public. We can't test the bug fixes. CodePlex has no change sets.

This has been discussed before many times.  DNN doesn't provide beta releases or nightly builds you might find in a Linux OS project (And not all of them either).  Every release is a true release.  Great for 95% of the user community, frustrating for the developer community.  DNN Corp has suggested that this may change, with definite support issues recognized, but right now they're tied up with DNN 5 updates/releases/fixes.

As for modules. there are some modules that have beta code available to those who aree interested.  Not all module development goes through the DNN teams, plenty of module projects are on CodePlex.  And you're always welcome to start your own at any time, with any team of developers and schedule that you wish.

Jeff

 
New Post
1/28/2009 2:17 PM
 

as i mentioned already, the team leads run their projects as they want. The majority of projects do not release betas (in fact we used to explicitly ban it), but a few such as forums, events and store do. We are investigating offering access to items such as changesets/nightly builds, but historically we have only released builds through the project tracker, which allows for them to be tested independantly for localisation, quality, xhtml, security etc., so I imagine this will be trialled with one or two projects rather than make a switch.

Regarding your issue about forum involvement, I'd love it if each project team had people who followed up on all posts in their forums as this minimises frustration(i know some of them such as blogs have people like Dario who have an impressive post rate).

As for making it easy, why not just log any enhancement requests, bug issues, suggested code at the public forum @ support.dotnetnuke.com, this is open to all (simply create a login so you can track the status of your issue)

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/28/2009 3:11 PM
 

In fact we have a special status in support.dotnetnuke.com called "code for review"... for those who submit actual code (not just an example)... and this is very much appreciated... more of it please :)....



Alex Shirley


 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Are developers contributing code and bug fixes?Are developers contributing code and bug fixes?


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