On Mon, Jun 25, 2007 at 07:06:48PM +0200, Joerg Schilling wrote: > I have been told that you cannot introduce new things into OpenSolaris > in case that there is an unasked expert inside Sun. Now we have OpenSolaris > and this needs to be extended to the OpenSolaris community.
You are absolutely correct that the entire community, not just Sun employees, need to be involved. But as James and others have pointed out, the process of becoming involved requires that you speak up, not so much that others are required to consult you and prohibited from making progress until you've replied. The latter would rapidly degenerate into a web of dependencies blocked on people who are too busy, too disinterested, on vacation, or otherwise unable or unwilling to participate. I agree with you that closed ARC cases are harmful, and if you've been following the ARC process discussions elsewhere you would know that I am a committed and active opponent of that strategy. As you correctly point out, closed ARC cases deny you the right to participate in making decisions that will later affect you. That is wrong. But neither is a project team obligated to approach you when beginning work; they may do so if they believe you can help them understand the issues, but it is not a requirement. If the C-team or RTI advocate feels that a change is not complete until you have reviewed it, they may instruct the project team to seek your counsel. Given these constraints, what do you believe should have been done differently here (besides the technical changes you've suggested)? -- Keith M Wesolowski "Sir, we're surrounded!" FishWorks "Excellent; we can attack in any direction!" _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
