You guys want better accountability and I agree with you. I want you to tell us how it should be done.
Some sort of voting software? Daily updates via Twitter? Video cameras on everyone?
The Invictus team is spread among multiple continents, so development is happening in real time 24 hours a day. This is why I think we have had some problems.
tldr; Ideas to make community input real time to keep pace with all the cool things we are working on.
Also I'll try to be on #protoshares on freenode for my waking hours(super3). If you have immediate concerns just ping me there. I have access to the whole team so use me a resource till Brian takes over.
Back to work on the new website for me.
My opinion is each success should result in receiving reward credits. This would allow for the automated tracking of task completion. Basically upon each completed task the reward credits get released to the Keyhotee ID of the developer who completed the assigned task.
I don't think this is too difficult. You set up a board where the to-do list is displayed. Then you have the community vote up certain tasks to the top of the to-do list and those tasks should pay more in credits than the tasks which are not voted to the top. Also the tasks which a lot of people are doing should result in the difficulty level rising for those tasks which means the amount of credits should decrease as more people do the same task.
So if its bug testing for example if everyone is trying to be a bug tester then bug testing shouldn't pay as much. If it's a task no one wants to do but which is very important then it would be voted to the top and would pay the most.
In my opinion this functionality should be built into Keyhotee itself or should be one of the primary and most fundamental functions of Keyhotee. If we cannot use Keyhotee for something like this and have to resort to using blogs then why develop Keyhotee?
Since Keyhotee has Reputation, Wallets, and pseudo-anonymous communication it is perfect in my opinion to use for something like communication among developers. As far as accountability beyond that then of course you have change logs, blogs, or something similar to the planetKDE.org site. http://planetkde.org/
is a good model for how to do a development blog.