I'm a 'professional' / serious DNN user and have a suggestion to improve the core modules.  I know open source is based on the generosity of kind programmers that volunteer their expertise.  However, they all have bills to pay and I wonder if a little compensation may help the core modules move along faster?

Here's the idea:  Allow serious DNN users interested in specific modules to sponsor those modules with an annual fee. 

The module sponsors would receive the following benefits:

(1) Priority support via a private forum/email
(2) Bug fix patches released to benefactors before official releases.  For example, the last document module (v4.0?) was released with a sorting problem that has not been fixed in a LONG time.  Maybe the patch could be released to benefactors right away as a 4.0.0a unofficial release or patch file.  
(3) Future feature input.  Allow the benefactors to have priority input into future releases and to vote on new features.  Have them drive product development to some degree.

Here's the most controversial part:  Give the annual fee to the module core team as compensation.  Each team can decide how to dole out the cash, but allow them to get paid something for the work.  For example, if you got 100 benefactors for the Documents module at $50 each, the core team could split $5,000.  Not going to make anyone rich, but it gives some increased incentive.

Each module could set it's own price with the less popular ones like AD provider charging more since they have a more limited user base but the value is high to those users.

The quick fix patches are the biggest deal to me personally.  I worry about getting stuck with an error and waiting for months to get  a fix.

Thanks for reading.

JK wrote Who is going to organize and run such a scheme? :) Btw, DNN is Open Source, so if there is a bug holding you back, you are free to jump in and fix it - and then submit your fix back to the community. If it really is a small fix like sorting order, you probably can do it yourself for less than $50 in time and effort. If its a big bug, and not something you can fix yourself, then there already are paid support options - you can get the official DNN support, or ask any of the frequent contributers, you will probably find someone who will do it for a fee JK

Your post and many others saying DNN is 'Open Source' assume we are all .NET programmers.  I would venture to guess the vast majority of DNN users are not programmers.  I myself am not, thus I'd be willing to sponsor a module or two to support those that are programmers. 

Also, getting a 'fix' from outside the core team is not desirable because it makes you even more unsupported in general.

For the people using DNN for business sites, they need reliable long-term support and stable software.  You mention the paid DNN support but I don't think they offer support/fixes for the core modules, do they?  Do they offer interim patches or quick fixes to problems or do their customers have to wait for the next dot release like everyone else?  If they offer quick fix patches for core module problems, then maybe that is the way to go.

Anyone know?

Thanks.

dnner . wrote For the people using DNN for business sites, they need reliable long-term support and stable software.  You mention the paid DNN support but I don't think they offer support/fixes for the core modules, do they?  Do they offer interim patches or quick fixes to problems or do their customers have to wait for the next dot release like everyone else?  If they offer quick fix patches for core module problems, then maybe that is the way to go.

If you have alook at the Support offerings http://www.dotnetnukecorp.com/Solutions/SubscriptionProgram/FAQ/tabid/93/Default.aspx you will see that this is precisly why this system was setup the issue of core modules not but updated has plagued dnn for some time so this "sponsorship" and support system was put inplace to help rectify exactly that by prioritising work where the users require it. 
Allowing another user to modify a Coremodule is not a major issue so long as that adjust ment is done as a branch rather than simply a patch. This would mean that you couldn't directly upgrad but if the system after being fixed does what you want and need do you need to upgrade? Also if you hire someone to solve and issue with a core module, if the fix they have found is posted back to these forums within the appropriate section then it is likely that the fix will be incorportated in some manner.

As to the documents module I see from the blogs that there has been a recent change of leadership there so expect a new release soon.

To participate in the community and to help on a team you don't have to be a programmer simnply by posting up the bug s and helping test you can be just as important as a programmer.

In Regard to quick patches, this concepts goes against the quailty control that DNN has in place to benifit you the user. Each module has to go through and attain certain standards before it can be released. This doesn't mean they are bug free but it does ensure that important items such as security and reliability are generally maintained.

Hope that Helps

John