@Matt
What I’m looking for is someone to clearly define the product roadmap. This is something we have NEVER had.
Even reading the blog, irc and this forum – it’s still unclear to me what should be worked on for the next release. What will make it in, what won’t.
The problem with just looking at Trac is that anyone can just add a ticket to a release. Which then makes it appear the next release will never get completed because tickets just pile up.
https://trac.bbpress.org/roadmap
We need you to:
* Clearly establish what the next major features/work/purpose will be for the next release.
* Define exactly which tickets in Trac should be worked on for each release and those tickets to not work no, move those tickets to a future release.
* Set hard dates to have it completed by so that we have a target to work towards.
The bullets above does the following: It keeps those of us that can code focused to only work on what’s important (and also informs us what to work on if we’re not aware). It gives us a target to hit, right now we’re very blind.
This is what I’m looking for in a Benevolent Dictator. Don’t get me wrong, I love your involved but we need someone to provide some organization.
To give an example of a project that excutes the bullets above well is Edgewall, the makers of Trac. Just look at the following link on how well organized their releases are. Includes release date, pre-req tickets to fix, etc. http://trac.edgewall.org/roadmap
People like to be told what to do. Just tell us what to do … you’d be surprised at how many people will perform once asked and they know the target. (Just saying “please contribute code” is not enough, we need to be told specifically what needs to be contributed)
