On 7 August 2013 06:06, Lukas Fleischer <archlinux@cryptocrack.de> wrote:
The total number of TUs isn't fixed. It changes from time to time and it might change during a SVP. I agree that it is a rare case but why not find a proper way to handle that while we're talking about it...
OK, I was just pointing out what looked most obvious to me, in a simple way (take the static number, purposely prevent it from changing by ignoring additions/removals during the vote).
[...] * Record active at start, add newly active, ignore newly inactive, ignore newly added, ignore newly removed
So we're ignoring the fact that adding/removing a TU during the SVP distorts the results? Because it is a corner case?
In that option additions/removals are not counted at all (towards quorum) -- they are exempt. You can, of course, include newly added but ignore newly removed, following the active/inactive policy. This was just a suggestion. All we need is a reasonable (read: pragmatic) system to bring new people on board to do things in their spare time, so it's fine to not take it _too_ seriously. Do whatever it takes to automate the process; the bylaws just prevent us from f*ing up at certain times. -- GPG/PGP ID: C0711BF1