On pe, 06 touko 2022, mowest wrote:
Comments below...
On Friday, May 6, 2022 2:59:30 AM (-04:00), Peter Boy wrote:
> > Am 06.05.2022 um 06:02 schrieb mowest <mowest(a)vivaldi.net>:
> >
> > If this is simply a matter of moving our infrastructure from Pagure to Gitlab
>
> Well, it is a matter of moving, but simply? You have to adjust a lot of details.
My apologies, I did not mean to infer that this would be an easy
process. I still agree with other comments that there are more
important tasks to focus on at this time.
> Fedora has decided to give up to host it’s repository and had
> outsourced it to a commercial service provider, gitlab in this case.
> You will continue zu use your FAS account to login to the gitlab
> hosted Fedora repos. The Fedora Account is kind of „shadowed“ in
> gitlab.
I have never had a Gitlab account, so I decided to attempt to get
connected to the Fedora namespace / "instance" in Gitlab to see what
has been moved over. I found the sign-in / sign-up process as little
cumbersome. By hitting the Gitlab Fedora Namespace, it triggered an
authentication asking for my Fedora Account by taking me to the FAS
login page. After doing so, it then kicked me back to Gitlab where it
said that it sent an email to verify my email address. I clicked on the
link to authenticate my email address, and then that link took me to a
page claiming that my email had been verified, and asked me to login
with either my username which was in the Gitlab email verification
email, or my email address that I use for my Fedora Account. However,
when I tried to login using either of those and then use my Fedora
Account Password, that failed. No where did it say that I needed to
create a password for the account, so I had to use the "Forgot my
password" password recovery function of Gitlab to create a password for
the account.
It is even harder in my case. I have already
gitlab.com account with the
same username as in Fedora. I simply cannot login to
gitlab.com/fedora
because after successfully authenticating me at
id.fedoraproject.org,
gitlab.com shows me
SAML authentication failed: Extern uid has already been taken
error message.
I am using
gitlab.com for contributions to CentOS 9 Stream and have to
login periodically through Red Hat's single sign-on system for that and
that works just fine with my account on
gitlab.com. The account
pre-dates my work for Red Hat, so clearly there is some issue in how
Fedora and
gitlab.com authentication was set up.
- If they have tied our Fedora Accounts to the Gitlab Fedora Namespace,
I would have expected that every time I hit that Gitlab namespace, I
would have to do the Fedora Account Login.
- But it seems that they actually just use your Fedora Account to
verify that you should be able to see the Fedora Namespace, but you
still have to create a Gitlab account for logging into the Gitlab
Fedora namespace, so they should have prompted me somewhere along the
line to create a separate password for the username they created for me
after they verified my Fedora Account.
That process was a bit confusing.
> > Has the Fedora Docs team moved over to Gitlab? I believe that is
> > where I first saw the suggestion, to have a browser editor to make
> > it easier for new documentation contributors.
>
> Yes, docs started to migrate.
Looked around, but I didn't see any of the actual documentation pages
in Gitlab just Antora toolset. I'm not sure how the Gitlab Fedora
Namespace works, it is possible that my user doesn't have permission to
see the actual documentation pages that populate
https://docs.fedoraproject.org.
Thanks, Peter, for your comments on Gitlab and how the Fedora
infrastructure works. I learned a lot of new things this morning.
If anything, I do not see any reason to migrate from Pagure to Gitlab
right now for Fedora Server.
--
/ Alexander Bokovoy