| 1 |
Christina Fullam wrote: |
| 2 |
> I think everyone is overlooking the part included previously: |
| 3 |
> "An additional method discussed was to have all non-dev emails on a |
| 4 |
> timeout, pick a number of hours, and then the email if not moderated |
| 5 |
> would be released. (non-dev sends his email, time period expires and no |
| 6 |
> one booted it, so the email rolls through)" |
| 7 |
> |
| 8 |
> This means that non-dev emails will still be sent to the list, just at a |
| 9 |
> delay. This same delay can and will be exercised against developers |
| 10 |
> if the developer demonstrates a justification for it. |
| 11 |
> This also means that non-dev input will be accepted and viewed as it |
| 12 |
> always has, the only change is that there is a delay. |
| 13 |
|
| 14 |
Then what, exactly, is the damned point? The problem this is supposedly |
| 15 |
intended to solve is that -dev is too high-volume. This solution |
| 16 |
requires people to actually put MORE effort into reading -dev than they |
| 17 |
previously did. No one is going to actually do any monitoring, so all |
| 18 |
you've done is made posts from non-dev accounts time delayed. Why? |
| 19 |
|
| 20 |
|
| 21 |
-- |
| 22 |
dirtyepic salesman said this vacuum's guaranteed |
| 23 |
gentoo org it could suck an ancient virus from the sea |
| 24 |
9B81 6C9F E791 83BB 3AB3 5B2D E625 A073 8379 37E8 (0x837937E8) |
| 25 |
|
| 26 |
-- |
| 27 |
gentoo-dev@g.o mailing list |
Archives