- From: <bugzilla@jessica.w3.org>
- Date: Wed, 01 Sep 2010 23:27:21 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10524 --- Comment #2 from Laura Carlson <laura.lee.carlson@gmail.com> 2010-09-01 23:27:20 --- (In reply to comment #1) > (In reply to comment #0) > > > > So a non-working group member can ask that their bug be escalated. However, if > > a working group member does not write a change proposal and champion said > > issue, the issue is closed. > > There is a saying in the legal profession that hard cases make for bad laws. > > I think this is one of the cases. > > I believe that the scenario that is being described here is that somebody > outside of the working group reports a bug, and (a) nobody within the working > group takes enough interest in the bug to propose a resolution in the form of a > change proposal, (b) the original person who reported the bug is willing to > write a change proposal, (c) said individual is not willing to agree to the W3C > Patent Policy or otherwise is not willing to follow the process that has been > put into place ensuring that the W3C has sufficient rights to incorporate said > proposal, and (d) said individual is willing to accept the decision of the very > same group on the disposition of the proposal. > > Yes, in such a case the outcome would be that the only outcome of raising the > issue would be to confirm that nobody in the working group has an active > interest in addressing the problem reported, but even then, the issue would be > closed without prejudice. > > Relaxing any of (a), (b), (c), or (d) results in a different outcome. Thanks Sam. In the policy or boiler plate bug message it might be good to let non-working group members know that they MUST join the group to affect change if they can't get someone who is a member to write a change proposal on their behalf. Many people outside of the group won't be aware of the fact that they have to join. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 1 September 2010 23:27:23 UTC