My suggestion... before you all rush out to create, modify, code, re-program, arrange, calculate, compile, compute, design, draft, edit, process, or whatever you normally want to do to vBorg...
Elect, through registered members' vote, a Board of Advisors. Create Advisory Committee(s) within the Board.
Set up ad hoc committees (for example hack DB deployment) as needed, then disband once the project is completed.
Allocate space on the Board for non-coders, coders, designers and whatever the flavor of names call today. Get a reasonable cross-section of the community.
Allow the Board and the advisory committees to provide a concise and specific feedback to vBorg direction. vBorg should respond why or why not implementing the feedbacks/direction to the whole community.
There is no reason vBorg cannot run herself as thousands of non-profits do.
Add some structure to how things happen at vBorg, and the majority of displeasures will fade.
|