Jim Walker writes: > > If access is limited to people who have signed > > and submitted the SCA, surely that should be > > more than sufficient for gaining access? > > Here's some more food for thought... > > - I personally don't like limiting anything, but > sometimes tough decisions have to be made.
Can you provide details here? What are the limits that bring us to making tough decisions? Given that we haven't tried making it open yet, it's hard to say what the demand might be, isn't it? Just as a general rule, and given our OpenSolaris experience to date, I would think that starting with "simple" and gradually moving to "complex" as needed would produce better results than starting with "complex" and expecting people to ramp up. Otherwise, we'll need to budget resources and time to answer the likely frequent questions about test system access, sponsorship, time limits, project requirements, and such. We already do that with our somewhat baroque development processes, and I'm not sure that more will be better. > want to do. So, I'm not as concerned about > getting overloaded here, short term, but, I > would rather start with access controls instead > of having to add them later after people are use > to no controls. Can you expand on that? What's the risk you see in adding access controls later only if demand becomes excessive? I'd very much like to encourage people to test their bits before delivery, so I think any stumbling block erected along the way deserves some extra scrutiny. In this case, we're discouraging contributors who have a small but valuable fix and who'd like to test it, but don't have the boundless amount of time necessary to read all the OpenSolaris documentation. > - 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? > - is simple, fair and consistent > - gives test resources to active OpenSolaris contributors > - filters out people who don't contribute to OpenSolaris > - spreads the load, so one person isn't an approval bottleneck > - is easy to implement and automate > - scales across multiple sites All of that, at least, looks reasonable to me. It's the "simple" part that has me a little concerned. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
