| 1 |
i still dont see what is wrong with the amendment process that has been used |
| 2 |
multiple times in the past and ive pointed out a few times (but apparently no |
| 3 |
one has noticed). treat it like any other item of business. |
| 4 |
- it is announced on the gentoo-dev mailing list as an item (so it has to be |
| 5 |
posted weeks ahead of time) |
| 6 |
- if the developer community really has a problem, issues will be aired |
| 7 |
- once issues are aired out, vote on it like any other item |
| 8 |
- post exact changes to the mailing list as part of the meeting summary |
| 9 |
again, if there are real issues with the changes, people will complain. |
| 10 |
council members are *voted in* because the community *trusts them to make the |
| 11 |
important decisions*. if the decision made really pisses off the community, |
| 12 |
again you will hear about it and you can take the response into consideration. |
| 13 |
plus, if you do something really stupid, it isnt like your ass will remain in |
| 14 |
power. wringing your hands over nonexistent issues is simply wasting |
| 15 |
everybody's time. |
| 16 |
-mike |
Archives