Bug 1362465
| Summary: | Bugzilla bot account required | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Kaushal <kaushal> |
| Component: | project-infrastructure | Assignee: | Nigel Babu <nigelb> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | mainline | CC: | bugs, gluster-infra, mselvaga |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-22 03:31:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Kaushal
2016-08-02 09:24:04 UTC
Please use the bugs address (public mailinglist) for this. (In reply to Niels de Vos from comment #1) > Please use the bugs address (public mailinglist) for this. This doesn't seem a good idea to me. We can't be using a public mailing list for creating the bot account. For the bot account my preference is to create a bugbot email (or an alias forwarding to the infra admins) and use it. I'm guessing we need two things here: 1) A bot account to change status and has bugzilla privileges to make changes. 2) An account that will forward bugs to a mailing list? I'm going to exclusively focus on 1). That account will not send email publicly. It will make changes. Remember we need to grant this bug editbugs privileges, so I'll have to talk to bugzilla ops folks and take their suggestions on what works best. 2 already works. You just need to set a default CC, which is already done. We now have bugzilla-bot which only has editbugs privileges which will do this from today. |