Right, but do you really need to suppress drive by reviews from people who have already gone through these hurdles once?
Suppose I sign the form and get marked as a dev for website, and I send reviews for it. That makes me rare already. If I decide to try to review in another project, what harm is there in allowing that? If necessary for process, treat me as a developer for any project where I haven't otherwise been designated, or create a new class for such people. On 6/29/11, Jim Grisanzio <[email protected]> wrote: > On 06/29/11 02:49, timeless wrote: >> Is it necessary to be assigned a role? > > Yes. To upload a code review you have to be a Leader or a Developer in > the project to which you are uploading. > >> Surely once you've signed the >> agreement once (you only need to do it once in a year, right?), > > You sign a contributor agreement only once. You don't have to sign it > once a year. > >> then >> for any team in which you are not a lead, if you try to contribute, >> you can automatically classified as a developer. No? >> > > The initial process is not automatic. It takes place in 3 manual steps. > First, you submit your contributor agreement. Second, the website team > updates your account to enable your account to be granted a role. Third, > a Leader of your project grants you the role of Leader or Developer in > the project. Once your account is updated with your Oracle Contributor > Agreement, you are eligible to be granted a role in any project. > > Jim > > > -- Sent from my mobile device _______________________________________________ website-discuss mailing list [email protected]
