Basic Contributor Flow Chart, With Relative Control Over Development Based On Contribution
I think this is adding bureaucracy where it is not needed- lead positions (balance, for example) exist only by necessity. Equally, any authority is meaningless when a contributor isnt around to (quant) or choses not to (trepan) exercise it (though quant gets all credit due him as soon as he decides to excercise it again, naturally). If this doesnt accurately reflect our power structure i dont think its useful, and our power structure is organic and hard to reflect. We could do with slightly better organisation but i dont think our team is big enough to need too strict a hierarchy. We can elect official representatives if we need them etc, as well, but that doesnt need this kinda hierarchy. -Saktoth
Attachments
- Project ChartCA.emf (22.0 KB) - added by neddiedrow 4 years ago.
- Project ChartCA.png (31.9 KB) - added by neddiedrow 4 years ago.
