>> Bite the bullet and at least make all CC'd people able to see all >> patches, always. It's needed. > >Yeah, that's the direction I think we should take.
Good, thanks. >For now, we will implement exact syncing of the CC list + reporter as the >revision's subscriber list. This means that anyone being added as a >subscriber who isn't CCed will unfortunately be quickly removed (we may >even prevent manual additions to the subscriber list). The reasoning here >is that I believe it's important that anyone looking at the bug knows >exactly who can see the patch. If the two lists are kept in sync, it will >be obvious. However, if we let people add subscribers directly, then it >may turn out that a bug with only, say, 10 CCed people might have a patch >that 100 people can view, and that's probably something you don't want to >hide. > >We'll also investigate what bidirectional syncing would take. Due to race >conditions and circular references, though, it won't be straightforward, >and I suspect our time would be best spent elsewhere. Don't bother with bidirectional syncing - your point about being able to look at the bug and know who can see it is important, but I don't see any advantage in subscribe mirroring into cc. I would (as you suggest) block subscribe on sec issues, to avoid confusion (if you can, tell people to use cc, but that's just gravy). -- Randell Jesup, Mozilla Corp remove "news" for personal email _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
