Hi Mitch-

Thanks for your response on this (and for your contributions; to the projects, and your site). I'm sure that the communications process, with so many people with changing availability, demands, and priorities, must be a challenge to juggle. Everyone has day jobs - I'm sure those take precendence and for good reason. Without a bunch of people volunteering, I realize that none of this work gets done (and arriving at discussions like this never happens ;-). Something about a "good problem"...

Overall, the DNN community is awesome. And, hopefully this project gets back on track because it sounds as though the improvements to the Blog mod will be significant. I'm anxious to get my hands on it and put it to use!

Best regards,
- Jeff

Sebastian,

I appreciate your honesty here.  What is being done to move this process forward so we can get a release on the blog module?  The fact that the team is locked out of submitting should not have held up the repairs.  They have the source on their own computers, etc.  I assume this has only held up the submission of the now completed and pre-tested blog module. What is the timeline to getting the module submitted back into release tracker?  Can this be done by the end of this week?

Just a piece of advice to everyone involved on the Dev side of this project, openness is key on an "open" source project.  Every step of the way should be blogged so the community sees that there is a problem and that the process is not being held up by apathy. Look at Linux as a great model for this.  Everything is done out in the open.  You can not take the worst parts of open source and the worst parts of closed source and combine them to make something great.  Either make it closed source and start hitting hard targets or be fired, or do it open, free, and in front of the world.  Perhaps this situation could have been resolved faster and with less disdain had it been communicated out in the open.