Peter Tribble wrote: > On Sat, Jan 3, 2009 at 4:35 PM, Darren Reed <Darren.Reed at sun.com> wrote: >> Peter Tribble wrote: >>> Commit rights are per-project, so if the project ceases to exist then >>> there's >>> nothing left to commit to. Rights to other projects are unaffected. >> Hmmm, by extension, doesn't that also mean that bugs found in code >> that isn't associated with a project, can then be closed because no >> further commits to that code are possible, allowing the bug to be >> closed? > > No. All code is part of a project somewhere. Essentially by definition. > >> For example, if a bug was reported in /bin/ls, that is never going >> to be a part of a project (it has already been committed), so any >> bugs relating to it will never be fixed because nobody can ever >> commit a change to it. > > Rubbish. /bin/ls is part of the ONNV project.
So let me put this another way. At present OpenSolaris benefits from Sun's HR for its control of who comes and goes and gets access to make change. When OpenSolaris breaks out and is capable of allowing direct commits from people outside of Sun, how will projects such as ONNV manage their access rights? Does the OGB just punt on that and say "that's up to the project to figure out" or does the OGB get inolved and decide that all projects need to manage themselves in accordance with a minimal set of rules/guidelines that are picked up by all communities? Or to put a pratical spin on this, if in the future (when direct commits from non-Sun pplis possible) John Doe from some isolated place proposes to take on a cool project by himself and that gets approved, who does the due diligence every 6 months/year/whatever to verify that access for John Doe is still required? How do we ever know if he gets hit by a bus? Darren
