Description of problem: Nigel/Misc, Prasanna, Vijay and I are using the following github repo as the place for developing gluster-block: https://github.com/pkalever/gluster-block. We want the project to be hosted on our gerrit going forward. Could you please add Prasanna, Vijay and I as people with commit permissions for the project? We want the github mirror as well under github.com/gluster. Let me know if you need any more information if necessary?
For adding the project under the Gluster organization in GitHub, we have previously followed the following steps: - transfer ownership of the persona repository to one of the Gluster admins - admin accepts the transfer and moves it under github.com/gluster/... - original owner forks the moved project to keep existing links working This makes it obvious in GitHub where users can find the project (as long as they follow the "forked from ..." links). Once moved, pushing changes would then only be allowed through Gerrit, which maintains the official repository and mirrors changes to the GitHub repo.
Thanks for info Niels! I have these two question in my mind: 1. I have a master branch and working branch(rpc) in the repository, so will both branches be mirrored ? 2. Is the new owner github user name is 'gluster' (Gluster admins)?
1. How different is your working branch from master? Is it possible to make that a review request? 2. The new owner's github organization name is "gluster", yes. 3. Feel free to add me "nigelbabu" as admin on the repo and I'm happy to make the changes.
Cool Nigel! The the rpc branch was just 3-4 commits ahead by master, I can merge them onto master in a while and transfer the account. Then mirroring just master would be enough. Thanks.
Nigel, 1. Merged the working and and master branches. 2. I have added you to collaborators in on the github repo (Waiting for your respose) 3. Transfer to gluster errors out "You don’t have the permission to create repositories on gluster"
The repo is setup on Gerrit and replicating to Github. I've tested everything works by making a tiny review and comitting it myself. Please let me know if there are any further issues.
Nigel, I have noticed that Reviewed-by and Review-on are absent after merge in the git history ? can we so something about it ?
So the merge type that I usually select for projects lets you build have dependent reviews. However, in that case you can't have the Reviewed-by and Review-on flags. I default to this submit type because of the advantages it providers. If you'd like the flags more than anything else, I can change the submit type.
Haven't heard anything back. Closing.