Bryan Ãstergaard wrote: > On Sun, Sep 03, 2006 at 08:38:19PM -0400, Alec Warner wrote: >> Stefan Schweizer wrote: >>> Hi, >>> >>> as requested by multiple devrel members I have written a GLEP to standardize >>> bugzilla access for contributors. It has already been discussed on the >>> devrel mailing list before but I am looking for a wider opinion now. >>> >>> This is also a submission for the new council when it meets. >>> >>> Best regards, >>> Stefan >> Errr. on -devrel you noted you would just make people take the ebuild >> quiz and now devrel wants a GLEP again? >> >> I'll state the same thing I stated on that list. >> >> A. This already happens. I had bugs access for MONTHS before becoming >> a dev; I got assigned to the portage buggroup and I could edit portage >> bugs. Anyone already on the portage team could add me, so no nastiness >> for recruiters (or anyone else). > If people are randomly given bugzie privs (or any other privs) this is > something we need to fix. And just to make this clear to all - handing > out privs is only half the equation and it's already hard enough for > recruiters to keep track of devs even though we have well defined > procedures etc. for that.
Then you better get to patching bugs, since I can hand out gentoo-dev and portage-dev privs on bugs without any problem (I tried it on ferringb to check even; and i took them away right after). >> B. Double bonus is that I don't even see why a GLEP is required? This >> is a small subset of users using one resource (bugzilla) so perhaps >> Infra and devrel and you can work out the requisite groups? Why is >> there all this red tape? > Because it's going to affect all devs if people don't need to pass > quizzes (or we lower the threshhold substantially) before they can > reassign, close, reopen etc. the maintainers bugs. And in this case I'm saying a subset. I'll use Java as an example. Caster is like an awesome Java dude. Lets say I want to give him access to bugs assigned to [EMAIL PROTECTED] Either I (as a member of that herd/project) already have bugs perms to java bugs, or the group doesn't exist and I need to ask JForman to make a java-bugs group and make it so they can do stuff to bugs assigned to [EMAIL PROTECTED] If I'm already in the group I can just delegate the java perms to Caster and be done. Aside from the java bugs, no one else is affected. No other permissions on bugs are granted. The user can only mess with java bugs. >> Create a group; come up with a subset of bugs that they can access, add >> user to group -> done. As long as they can't access my bugs; I really >> shouldn't (and trust me I don't) care. > Who's going to admin that? We already have the Arch Tester / Herd Tester > projects that defines a proper way of achieving the goal as I see it. > > Only problem with Herd Testers / Arch Testers compared to genstefs goal > is that HTs/ATs deal with packages in the tree while sunrise > contributors deal with packages outside the tree. > > And personally I'd very much like to draw the line somewhere. Genstef > made the GLEP extremely vague regarding contributors (on purpose) but > guess what? Everybody who files a new bug, submits a fixed ebuild etc. > are contributors. So should we just remove all the restrictions now? > This is definitely something we need to define before moving on, no > matter if the GLEP is eventually denied or accepted. I liked my definition in my earlier mail ;) Generally contributing requires you know someone rather well, such that they proxy your changes into the tree. >> C. No real standard on any other fora. I don't need a GLEP to add >> someone to my project overlay, or grant them voice or ops in my >> project's IRC channel. I don't need a GLEP to get them subscribed to my >> mailing list and I don't need a GLEP to add them to (most) project >> aliases. Why does this require one? > Because this is about the entire Gentoo project and affects us all in a > very direct way as opposed to random projects. I tried to make it clear above that it doesn't. I hope I succeeded. > > Regards, > Bryan Østergaard -- gentoo-dev@gentoo.org mailing list
