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...The Need for Module Standards and PracticesThe Need for Module Standards and Practices
Previous
 
Next
New Post
7/9/2010 9:49 AM
 
The module certification program, while a good idea, proved to be too time consuming and costly.

I think a lot of the issues John brought up could be helped, if not completely solved, by changing the module rating system on snowcovered.  Some issues would include:
  • The rating system sometimes seems to be a developer rating system rather than a product rating system.  You click on the ratings for a product and you get ratings for a different product by the same developer.
  • I think it would be very handy to have both - an overall developer rating/comments section and an individual product rating/comments section.
  • There are product ratings for versions that are three or four years old mixed with ratings for the current version with no way of telling which is which. Need to add a version field to the new rating form.
  • I have seen bad ratings on some modules and when you check back six months later they are gone.
  • Clients need to be able to add additional comments down the road.  Maybe an initial thoughts/installation/set-up rating/comments area followed by a long term rating/comments area - all on the same form - clients can edit their own rating/comment.
The other issue John brings up that I have also run into is developers abandoning their modules.  Snowcovered is littered with these modules and while a DNN community member that has been around for awhile knows this newcomers may not.  Why not have a snowcovered area where developers can sell module rights to each other combined with a policy that abandoned modules get uploaded to the DNN Forge (as a last resort).
 
New Post
7/9/2010 11:10 AM
 
Bruce Chapman wrote:

For the record I would never orphan a product if I decided to no longer pursue it.

My company has a similar policy about buying source.  Even if a developer never intends to orphan code, they could always get hit by a bus.  Especially in the DNN world where there are so many individual developers with nobody to carry on if they leave this earth.  We do buy software where the source is put in escrow, that might be an option for developers who don't want to release code.  Except it's not an insignificant price to do that as I understand.

Jeff 

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...The Need for Module Standards and PracticesThe Need for Module Standards and Practices


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