[request-sponsor] defect 3093 pam security issue in very specific environment
On Tue, 26 Aug 2008, Nils Goroll wrote: Do I need to request a sponsor for bugzilla bugs or is anyone monitoring all bugzilla bugs? Sorry, have posted a legacy bug with identical content. webrev with fix is ready for review - who is going to ask for review for this one? http://defect.opensolaris.org/bz/show_bug.cgi?id=3093 Hi Nils - That's not the right place for the bug to be, as defect.opensolaris.org is currently only supposed to be used for things in development - things that aren't integrated into the source base. I don't know of general monitoring of bugzilla bugs happening. I'm working with some internal people to figure out where this bug does belong in bugster/bugs.opensolaris.org, and I'll let you know. Are you looking for a sponsor to help you integrate your changes? Valerie -- Valerie Fenwick, http://blogs.sun.com/bubbva Solaris Security Technologies, Developer, Sun Microsystems, Inc. 17 Network Circle, Menlo Park, CA, 94025.
[request-sponsor] defect 3093 pam security issue in very specific environment
Nils Goroll wrote: Do I need to request a sponsor for bugzilla bugs or is anyone monitoring all bugzilla bugs? Sorry, have posted a legacy bug with identical content. webrev with fix is ready for review - who is going to ask for review for this one? Which bug tracking system is used doesn't really matter in the question of whether or not you need a sponsor. You need a sponsor for any change you want to proactively request be integrated into a OpenSolaris gate that you don't have commit access to. If you just want to wait and see if someone has time to pick up the bug someday, then you don't need a sponsor, but you may not see your change integrated for years, if ever. (This is a big difference between OpenSolaris process and many other open source projects - our process assumes everyone wants to become a committer and to do the work of testing/reviewing/integrating, and doesn't have a good fit for those who want to just toss a patch at the existing committers for them to test/review/integrate.) -- -Alan Coopersmith- alan.coopersmith at sun.com Sun Microsystems, Inc. - X Window System Engineering
[request-sponsor] Remove sponsorship of Bug 6431132
6431132: legacy yacc code cannot be maintained or understood Update from the sponsor of this bug indicates that this request is dead. The contributor has no access to a Solaris system the code, what he contributed does not match the bug and the whole thing was massively unclean. Please remove this bug from the sponsorship list. Thanks, Ebru
