this was the an issue I have brought up in the past.
using the bugtracker is fine, but the biggest problem is you have to be:
A) a user on the system
B) have to have certain rights to use extended project management (like roadmap)
I believe it to be ok for the bugtracker to contain a general outline
for the roadmap.
But I also believe that the roadmap should be Wiki style, ie you dont
need to be a developer with admin privilages to add or edit it
As for Jo's comment about "attracting more coders"& "get to know the
code base", these need to be tied in with source documentation
If the roadmap were to be wiki style, other people who are not
currently developers (because of time or commitments), can add details
at the technical level.
This would also allow for a "loose knit" project group to be formed,
maintained and managed, without the need to place commitment on any
one person (or key people)
Overall though, it seems to me that all current developers need to
update there current documentation, websites, and web apps etc..
That would be the first step is clearly seeing an over direction that
the community is taking, and allow others (especially by current
developers) to see specific direction of key items or ideas currently
being worked on
what ever what future development is organised, it should be as
totally open as possible, without the need for access rights, etc,
that people can come and go as they need to.
Should the unthinkable happen (which it has all ready), there will be
no hold-ups it continuing momentum, whether those are dev work, or
documentation, or project detailing, or testing, or non-coding dev
work