I would love to get not just additional feedback on this, but tangible help as well. If you look at the history of Qcodo since it was open sourced back in 2005, the community saw a very promising slow but steady growth in membership and community activity, contribution, blogging, etc. throughout its lifetime up until early 2009.
At around that time, a lot of things started stagnating in the community, with myself to blame for a lot of it. There were a lot of limitations with the way the framework was structured and distributed, making releases more difficult. Moreover, it was very difficult to implement changes and code contributions back into the code. Members of the community were getting increasingly (and understandably) upset at the lack of cohesion and progress with the community, and thus, forks started happening. Initially with ZCodo, and now with QCubed. With some of these forks, the confusion around the community, and the lack of regular releases during the re-structuring, it's no surprise that the community overall began to stagnate. Some folks left, and many I feel are just sitting on the sidelines.
Fast forward to October 2009, and I am excited to say that a lot of the structural issues with Qcodo and the ability for users to more-easily contribute to Qcodo have been resolved. With QPM and GitHub, it's very straightforward and easy for anyone to post code and to contribute code back into the core. It's rediculously easy for code to get code reviewed and put into the core repository. It's exciting to see community members like Marcos and Klucznik beginning starting to contribute code patches via github back into the core... and as momentum hopefully continues in this area, I can only see this increasing more and more.
Comet does bring up a good issue that QPM is still a bit slow to pick up and I think he does a good job in pointing out specific areas where this can be addressed, and I definitely solicit any additional feedback as well as outright help when it comes to the suggestions that he has.
And along the same lines, I do continue to encourage everyone to help out as well.
I think as with most FOSS projects, documentation is the key to help bringing more users into the fold. With Qcodo specifically, as Comet pointed out Qcodo does have a steeper learning curve than most of the other PHP and other scripting language frameworks. What that means is that documentation is even more important for Qcodo.
With all documentation now being put into the wiki so that anyone can edit, I definitely want to encourage folks to make fixes, changes, enhancements, etc. If there is something that doesn't read right or is unclear, post comments on that wiki page or better yet, go ahead and rewrite it.
If there are wiki pages missing, go ahead and start a wiki page for it and post on the forums or on that page encouraging others to submit content.
If some content isn't well organized, go ahead and do some wiki gardening, moving links around, etc. so that things can be easier to find.
Even if individuals can only contribute 15 minutes per week, I think these things collectively can go a long way in pushing the community-level of development further for Qcodo.
And finally, in terms of branching out beyond the community, I definitely encourage everyone to continuing posting, talking about and blogging about Qcodo. It's what helped bring about the slow but steady growth throughout the past 5 years, and I think it'll be another key area that will help the Qcodo community not just communicate well with each other but to also grow at the same time.
I look forward to hearing additional thoughts about this.