[aur-general] Enforcing TU Bylaws

[Aaron Griffin]

On Dec 20, 2007 12:42 PM, Vinay Shastry <vinayshastry at gmail.com> wrote:
> I consider administrative activities to be "extra" activities of a TU.
> And I feel asking a TU to step down because of refusal to participate
> in voting is not a good idea. I urge other TUs to kindly reconsider
> and not oust useful members for this reason alone.

You know. Everyone has this attitude when they're young. I see it in a
lot of people entering the work force. "I'm a programmer, I don't have
to deal with people!"

Surprise! Administrava is part of life. To get things done as a
"collective" there needs to be collaboration. There needs to be
agreement, and people need to be involved.

Here's a solution for you. The TU bylaws show that everything can be
done by voting. If people refuse to vote, then they cannot vote
ANYWHERE for ANY topic.

This way you get two classes of TUs: those who make the decisions (and
of course do all the other duties too), and those who make packages.
That means that it is no longer a collective, but a bureaucracy.