Publishing and maintaining the current focus would already make a lot to avoid irrelevant distractions like the bingo in client stuff.
Thinking out loudly, here's what I think could on the "focus" page (development oriented):
- Strategic goals we want to reach until may 2015, september 2015, december 2015. Eg: popularise bitUSD, develiver light client, ....
- List what feature/software is currently developed with an roughly expected delivery date
- List of features/software to develop afterwards.
- Possibly list what we postpone for now
- Possibly list the things we do not want and clearly reject.
This page could be reviewed monthly, but between those revisions, new proposals
would be assessed based on this list. This would prevent loosing time and
energy in discussions of items not aligning with our current objectives.
In may 2015, we evaluate what was done, try to learn and optimise the process, and publish objectives for may 2016.
This page could be simply an ASCII text document kept in a git repo, so that the history is kept, and published on github.
I'm a developed myself, and of course the goal should not be to make it a heavy
procedure or cumbersome project management methodology. But this kind of light
structuration approach has already worked for me and my teams.
Take this as a constructive post, written in the hope the developers can get something out of it to help them deliver
all the potential of Bitshares. The goal is certainly not to impose anything!