Bug 1358456
Summary: | please create a new email alias | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Vijay Bellur <vbellur> |
Component: | project-infrastructure | Assignee: | M. Scherer <mscherer> |
Status: | CLOSED CANTFIX | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | amye, atumball, bugs, gluster-infra, mscherer |
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: | 2018-04-12 14:44:45 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
Vijay Bellur
2016-07-20 18:10:20 UTC
So I will create it for this time, but I would like us to have a bit more process to decide when we give alias to people. If in the future, if we want to start adding a bit more order (like having shell account linked to mail account, etc), we will need a proper process. So I will not create anymore aliases for users after this one before we have a documented (eg, written down somewhere) on what are the condition to get a alias. In fact, there is already a alias by the name "kp" going to kparthas at redhat. I will contact RH Infosec departement, because I know that this kind of request may be problematic for others communities, and would like to get their approval first. Hey there, This should be assigned to m.scherer@ He's currently working this. I don't seem to have perms to be able to reassign. Treating the bug as timedout. Please reopen if this is still required. |