Bug 1686754 - Requesting merge rights for Cloudsync
Summary: Requesting merge rights for Cloudsync
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Deepshikha khandelwal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-08 09:18 UTC by Susant Kumar Palai
Modified: 2019-03-11 12:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-11 12:51:32 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Susant Kumar Palai 2019-03-08 09:18:07 UTC
Requesting to provide merge rights being a maintainer for Cloudsync Xlator.

Comment 2 M. Scherer 2019-03-08 11:23:16 UTC
Hi, can you explain a bit more what is missing ? As i am not familliar with the ACL system of gerrit, I would like to understand the kind of access you want, and for example who have it already so I can see where this would be defined, or something like this.

Comment 3 Susant Kumar Palai 2019-03-08 11:40:42 UTC
(In reply to M. Scherer from comment #2)
> Hi, can you explain a bit more what is missing ? As i am not familliar with

Maintainer right is missing. This gives the ability to add +2 on a patch and merge it as well. 

> the ACL system of gerrit, I would like to understand the kind of access you
> want, and for example who have it already so I can see where this would be

You can look at Amar's profile.

> defined, or something like this.

Comment 4 M. Scherer 2019-03-08 13:19:55 UTC
So Amar has a bit more access that most people, but I suspect that we want you either in github group glusterfs-maintainers or gluster-committers, based on the project.config file that can be access using the meta/config branch, according to  
https://gerrit-review.googlesource.com/Documentation/access-control.html

I will add you to the group once I verify your github id (I see https://github.com/spalai but since there is no information at all on the profile, I can't be sure). I would also like to make sure folks with more access to approve have 2FA turned on, so please take a look at https://help.github.com/en/articles/about-two-factor-authentication

Comment 5 Susant Kumar Palai 2019-03-08 14:31:46 UTC
Michael, Is there something pending on me?

Susant

Comment 6 M. Scherer 2019-03-08 14:36:24 UTC
Well, your github account, you need to confirm if that's https://github.com/spalai (who do not show much information such as name, company, and our internal directory do not list that as your github account so before granting privilege, I prefer to have a confirmation)

Also, plaase enable 2FA.

Comment 7 Susant Kumar Palai 2019-03-08 14:48:49 UTC
I doubt any Maintainers using two-factor authentication. Plus I don't see India listed for SMS based 2FA. 

Updated the bio as you asked.

Comment 8 M. Scherer 2019-03-08 14:52:23 UTC
You can use a yubikey with u2f, or any u2f compliant device. You can use google auth, or freeotp.

Comment 9 M. Scherer 2019-03-08 15:41:52 UTC
Also, I didn't ask to change the bio, I just asked to confirm that is your account. Just telling me "yes, that's my account" would have been sufficient :/

Comment 10 M. Scherer 2019-03-11 12:51:32 UTC
So, that was unrelated to github in the end, I did the change (in gerrit UI), but I would still push folks to use 2FA as much as possible.


Note You need to log in before you can comment on or make changes to this bug.