James Carlson wrote: > Jim Walker writes: >> - If we just authorize all contributors, and have a >> free-for-all approach, I would think the active >> contributors would get blocked, and we could give >> people a reason to sign the SCA for the sole >> purpose of getting access to nice test machines, >> with no intention of ever contributing to OpenSolaris >> in anyway. > > I don't see why anyone would bother doing that, but if it's really a > significant threat, then how about having use limited to users who > have corresponding open CRs?
How about if we try the honor system, where contributors just enter the CR or project they are working on? (ie. just like we do internally). I think this will be useful information to track in terms of where the community resources are being spent, and contributors can self police each other when they get blocked from accessing a resource that is being used by someone who obviously entered invalid CR or project information or is clearly not associated with the CR or project they entered. Peer pressure can be very powerful. In addition, many of the test machines will have short reservation limits of 3-5 days, so resource turnover will be automatic, and we can implement active run limits in Self-Service Testing, so the execution queues are not filled with jobs from just one person. At some point, I may be able to validate CR numbers and list project names, so the entries are more uniform. We could start with this approach and see how it goes. If people start getting blocked all the time, we can decide, as a community, what to do next with these shared resources. Cheers, Jim -- Jim Walker, http://blogs.sun.com/jwalker Sun Microsystems, Software, Solaris QE x77744, 500 Eldorado Blvd, Broomfield CO 80021
