Rod,

the blood in Open Source Software (OSS) is pumped by volunteers - even if there is some founding for The Corp and they will be able to suit the programs better than now, we will need contribution from the community to suit all needs and to get progress in all areas. The Corp will continue to provide the tools and organizational backpane for the module and provider projects, and I expect significant improvement in their service to all programs, but those projects will continue to be driven by volunteers and need support from community members: Anybody, who wants to contribute, please step up and get involved. your benefit will be: integration in the circle of contributors, direct contact to the core team and better reputation from the community.

Hector, if you want to contribute to one of the projects, please contact the team lead or contact me directly: seastian.leupold (at) dotnetnuke.com. Thank you in advance! 

We're all pressed for time to contribute. :) It's how it rolls. 

I don't like committing myself to something when I'm not sure I'll have time to take care of it in a reasonible timeframe. I want to help with the modules or core, but I can't commit because I can't be sure I'm going to be able to take care of things.

For me, this is how I feel, if the projects and DNN had their nightly builds / commited code available for anyone to download and work with, I would be much more prone to work on issues/bugs/enhancements that I encounter/see/want.

If I had access to the nightlies, I would be much more tempted and willing to work on an issue in gemini on my free time and submit it, without feeling obligated to take care of 10 of them.

I believe I saw somewhere that DNN is looking into opening up their unreleased code so people can have access to it. I really hope they do this.

I don't want to start working on a issue for the documents module and post my code to an unassigned bug only to have them say it was fixed 3 months ago but gemini was never updated. Or have some unknown changes to some function/database I used that breaks my 'patch'... It's a little demotivational to try to help from 'outside' the group without knowing if what you are doing is already done or broken from other changes made. I can't get my motivation up to work on changes when the 'actual' code is behind closed doors. (I used examples, I've had no bad experiences with either the documents team or gemini being properly updated)

Having access to the most uptodate code would make me feel 'safer' about working with it and that my contribution is going to be worth something.

I do understand the double edged sword which will result in more volunteers, but will also result in code of questionable quality. Are the coding guidelines being followed? Does it pass security inspection?...

So don't throw the doors open, just make it so we can see in and make sure we're not duplicating or facing breaking (to the 'patch' we are doing) changes.

I hope all that makes sense, and was relevant, I tend to ramble.

Short form - Open read access to the nightlies, I think it will get more people to volunteer.