From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4D1BA3858D38; Fri, 10 Mar 2023 17:29:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4D1BA3858D38 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1678469379; bh=SpXJ7O1dyydMP0Vht95V2uQvi3Gq2e2DVXHe2QUpgoA=; h=From:To:Subject:Date:From; b=CpcTMwjzhCnhIr2cAVtQCa5iQpwaQ1kTHAesNNkbSYdoYotSR6Gac2/0SQyeWcBbh 199gUUkcwbP/1IQWoplz7PnyPGRZq9ny61oliXcDoUWVLLzJ939UNzvIV2JTVgzA4l +t243CjKHMveyN/34ENI9h0QndMNyswz6k/0Qypg= From: "fche at redhat dot com" To: overseers@sourceware.org Subject: [Bug Infrastructure/30218] New: retire pdw/ for new account process Date: Fri, 10 Mar 2023 17:29:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: sourceware X-Bugzilla-Component: Infrastructure X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fche at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: overseers at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30218 Bug ID: 30218 Summary: retire pdw/ for new account process Product: sourceware Version: unspecified Status: NEW Severity: normal Priority: P2 Component: Infrastructure Assignee: overseers at sourceware dot org Reporter: fche at redhat dot com Target Milestone: --- We can use bugzilla instead for new account requests, complete with audit t= rail and deprecating tricky perl stuff that appears to have problems with non-as= cii names. Suggested process would be that the *sponsor* would file an infrastructure = bug right here, with a new component. We may be able to have an appropriate template, but not a huge deal. That way, no formal approval is needed notification/flagging, just a check that the submitter is acceptable for the project in question. Some automation to do the qcreate-user equivalent might be nice, but then again, new account requests are rare. --=20 You are receiving this mail because: You are the assignee for the bug.=