Don't want to sound negative, but the truth is I've been getting a fair amount of email asking about a project I used to lead, the News (Newsfeeds RSS).  The basic questions:

• when is someone going to update the status of this project
• release a new version
• start keeping the project blog current

I know that things take time, and work queues get full, that's why I had to drop out of the Core Team.  However, it would seem that this is an issue with other projects as well.  I know that DNN is moving forward, but those unfamiliar with the history of the project, and newer members really need to hear from folks regularly regarding a project status.  I continue to offer what help I can on the project, helping with questions on the current release version, but am not able to provide anyone with updates regarding the above questions.

So, please take this in the spirit of trying to give some positive feedback.  I did see evidence of the new release, but don't have any specifics.  So, with a view to keep our fellow DNNers updated, I would urge all Project Leads to blog reqularly with updates.  A brief blog about what's going on goes a long way towards helping folks in the know.  It doesn't take that long to blog a short piece, and if you are committed to the team or the lead, someone could take the time to give updates weekly, even if just to say nothing but testing is being done, or we continue to wait for members to step forward to positively impact the project.  I've had a few folks ask to join the project, and I refer them to the project lead, but if they don't get a response, there is a negative association with the whole DNN project not just the individual project.

That's all I want to say, except for I appreciate the effort, and the work of the Core Team, Project Teams, and other contributing members, and just want to see the project continue to blossom.

Thanks for your ears...

Phil,

please be assured, that your post has not be ignored - you should remember from your own time on the CT, that there os always some action behind th stage, due to different time zones, business and personal constraints, not all reactions will happen within a few hours.

Your observations of the blogs are helpful - though not accurately reflecting a communication problem IMO: nearly all have a latest entry within the past 3 month, Chat does not yet exist, Contacts has been discontinued, Users Online No activity at all yet and UDT - my own project, well, I prefer the forums and my team and I try to answer each post within 24 h, and some of them contain project status update.

I agree, that project work shall be continuous - but from my own experience, I got to realize, that this is not always possible. Take UDT as an example, since it was separated from the core mid 2005, we released: 

2005-11-18 - UDT 3.2.0
2006-06-20 - UDT 3.3.1
2006-07-15 - UDT 3.3.2
2006-07-20 - UDT 3.3.3
2006-10-17 - UDT 3.3.6

UDT 3.3.7 was intended for end 2006, but we decided to add some more features before the release - and due to other business, there was some delay. And, of courde, the new release tracking process slows down the release cycle frequency - as more efforts are needed to prepare and to test each version - on the other hand, the community benefits from additonal testing to get more mature outcome (e.g. I asked today a project lead to correct an issue I encountered during localizability tests, which will require him to correct, rebuild and resubmit the module). As a conclusion: the formal release process slows down release cycles - but lead into, better tested, i.e. more stable and secure modules - and, from my observations on the forums, this benefit outperforms the disadvantages.

Nice to hear from both Scott and Sebastian, too!  Really don't mean to appear unappreciative of the efforts and the behnid the scenes work - I do understand the difficulty in managing so much.  All I'm saying is that the effort to give a short blog update goes a long way to help inform the community.  Responding to forum issues is everyone's responsibility, and I do try to help as much as I can, I think you both know that I am in earnest in my effort despite not being fully engaged in any project or CT.  The problem with just focusing on a particular forum to respond to project status is they get lost so easily in the routine posting.   Certainly, in many cases Project Leads are responsive to posts, not only in their forum but in other forums, as well.  Obviously, Sebastian is a very committed community leader in that regard ( I don't know how he keeps up with so much!). 

My point in posting the project and blog last update was to illustrate the differences in the ways communcitations for DNN projects in a central area are handled.  Like it or not the focus for many on info about projects is the project page.  It seems reasonable to expect some type of update in a timed manner, regardless of the level of work engaged.  Now, I do know that coordinating efforts project-wise on a global scale has it's difficulty, so that's why it's import for folks who join a project to understand it's a big undertaking, not to be taken lightly or for the sake of just getting a kewl avatar to display with your name.

Specifically, I was directing my comments to the attention of the News project, although after looking at the other projects noticed that some were better than others at keeping project updates available.  I put the post in the 'Let's Chat About It' forum because, well, I want to chat about it to improve the situation, and nothing more than that.  I'll go a bit further, and say, in my own support activities for the work I am paid - supporting clinical systems support and consulting - I have a rule that we do not oppose without proposing.  I find the rule a good way for folks to engage in dialogue and move projects forward without focusing on negatives that offer no positives.

In that regard, I will further offer to assist in the effort to enhance communication of projects updates for any project team so inclined to take advantage of my services.   Another area that seems to be needing attention is the DNN web page itself.  What good is listing projects and team members for anything but active and engaged projects?  Need help with that - again, I offer to help. 

So, hopefully, project leads, teams, and the CT understand that I'm not about focusing on negatives, but rather pinpointing areas of improvement and even offering assistance to move things in a positive direction.

Cheers