How about the 2FA setting? Have you got it configured on github? Best Regards, Yu
On Mon, 14 Jan 2019 at 18:03, Reid Chan <[email protected]> wrote: > >> To make sure, could you find your github username here?: > https://github.com/orgs/apache/people > > Yes, i'm in. > > > >>If so, what's the error message appeared at the MFA status part on: > https://gitbox.apache.org/setup/? > > Msg: > MFA DISABLED > Write access suspended. Please make sure you are a part of the ASF > Organisation on GitHub and have 2FA enabled. Visit id.apache.org and set > your GitHub ID to be invited to the org. Please allow 15 minutes for your > MFA status to propagate. > > > > > > -------------------------- > > Best regards, > R.C > > > > ________________________________________ > From: Yu Li <[email protected]> > Sent: 14 January 2019 17:34 > To: dev > Cc: Sean Busbey > Subject: Re: [NOTICE] project repository URLs have changed > > To make sure, could you find your github username here?: > https://github.com/orgs/apache/people > > If so, what's the error message appeared at the MFA status part on > https://gitbox.apache.org/setup/? > > On Mon, 14 Jan 2019 at 15:29, Reid Chan <[email protected]> wrote: > > > I'm already a member in Apache GitHub organization, and have been waiting > > for more than 3 days. > > > > emm... > > > > > > > > > > > > > > -------------------------- > > > > Best regards, > > R.C > > > > > > > > ________________________________________ > > From: Yu Li <[email protected]> > > Sent: 14 January 2019 14:20 > > To: dev > > Cc: Sean Busbey > > Subject: Re: [NOTICE] project repository URLs have changed > > > > We need to add our github id to our apache profile, as mentioned in below > > description on https://gitbox.apache.org/setup/ > > *NOTE: You MUST be a part of the Apache GitHub organisation before you > can > > complete this setup. If you have not done so already, visit > id.apache.org > > <https://id.apache.org/> and add your GitHub ID to your profile. An > > organisational invite will be sent to you via email shortly thereafter > > (within 2 hours).* > > > > Be patient after you update your profile until receiving the invitation > > email (may really need 2 hours or so), and after joining the Apache > Github > > organization we will need to further wait ~30min before the MFA could be > > enabled. > > > > Good luck and have fun. > > > > > > On Mon, 14 Jan 2019 at 12:35, Reid Chan <[email protected]> wrote: > > > > > >> it is possible for committers to enable write access to the GitHub > > > repository[3] > > > > > > > > > Both Apache account and Github account are authed, but MFA status is > > > disabled. > > > Is it normal, or anything i missed? > > > > > > Thanks. > > > > > > > > > -------------------------- > > > > > > Best regards, > > > R.C > > > > > > > > > > > > ________________________________________ > > > From: Sean Busbey <[email protected]> > > > Sent: 10 January 2019 02:30 > > > To: dev > > > Subject: [NOTICE] project repository URLs have changed > > > > > > Hi folks! > > > > > > Our project has now transitioned from the old "git-wip" process to the > > > current ASF infra preferred "gitbox" repository hosting[1]. > > > > > > The main practical impact for most folks day-to-day is that you will > > > need to update your git remote url[2]; this is true both for > > > contributors who want to see up to date changes as well as committers > > > who wish to push changes. > > > > > > tl;dr: > > > > > > git remote set-url origin > https://gitbox.apache.org/repos/asf/hbase.git > > > > > > This presumes that you are in the working directory of your git > > > checkout and that you refer to the main repo as the default remote > > > name "origin". > > > > > > Out of the box, this repository URL should be set to work with the > > > same credentials, if any, you previously used to interact with the old > > > git-wip repository. You should be able to both fetch and push as you > > > have previously done. > > > > > > Note that under the gitbox service it is possible for committers to > > > enable write access to the GitHub repository[3]. By doing so a > > > committer could work directly with the GitHub PR interface instead of > > > doing so indirectly as we have historically done. We have an ongoing > > > discussion and documentation effort for how we as a community want to > > > handle that work[4]. I'd ask that interested folks participate in said > > > discussion and everyone hold off using our new write access to GitHub > > > until we've documented the consensus position. > > > > > > The changes also impact our "hbase-site" and "hbase-thirdparty" > > > repositories. The gitbox URLs for those repositories are analogous to > > > the one I gave above for the main repo. There is no change to the > > > "hbase-operator-tools" repository, as it has always been on the gitbox > > > service. > > > > > > If you notice an automated process break and it looks related to git, > > > please ping myself and/or Peter Somogyi and we'll help fix any fallout > > > from this transition. > > > > > > -busbey > > > > > > [1]: ASF Infra is decommissioning the "git-wip" project and has > > > required all projects move to the gitbox service. There's more > > > explanation in the thread "[DISCUSS] move to gitbox" > > > https://s.apache.org/lUHS > > > > > > [2]: This isn't true if you already use a remote that points at > > > github. That repository should continue to see updates. > > > > > > [3]: After enabling a sync between your ASF identity and your GitHub > > > identity, the GitHub repo is writable. Committers have "maintainer" > > > access and can both configure the repository settings and push commits > > > directly to GitHub. > > > https://gitbox.apache.org/setup/ > > > > > > [4]: HBASE-21701 'Accept pull requests from contributors' > > > > > >
