In our meeting x3mboy raised the question if we should start to migrate our repo to GitLab as many projects do. We decided to open a discussion on the mailing list.
So, the floor is open.
My opinion: IMHO, pagure does for us what we need at the moment. Therefore, there is no need for us to migrate now. And we have so many task to (see https://pagure.io/fedora-server/boards/Works%20in%20progress) we are well advised to concentrate on those. Not only, that one has to do the work, all others have to adapt there working routine and maybe spend some time to learn the new / different functionality. We should better spend the time into our working projects.
On Thu, May 5, 2022 at 4:57 PM Peter Boy pboy@uni-bremen.de wrote:
In our meeting x3mboy raised the question if we should start to migrate our repo to GitLab as many projects do. We decided to open a discussion on the mailing list.
So, the floor is open.
My opinion: IMHO, pagure does for us what we need at the moment. Therefore, there is no need for us to migrate now. And we have so many task to (see https://pagure.io/fedora-server/boards/Works%20in%20progress) we are well advised to concentrate on those. Not only, that one has to do the work, all others have to adapt there working routine and maybe spend some time to learn the new / different functionality. We should better spend the time into our working projects.
I agree. We've done plenty of process shuffling already, and our main trouble isn't where the tasks are, but getting them done. Let's just focus on that problem rather than doing more shuffling.
* Neal Gompa [05/05/2022 16:59] :
I agree. We've done plenty of process shuffling already, and our main trouble isn't where the tasks are, but getting them done. Let's just focus on that problem rather than doing more shuffling.
I agreee. Let's focus on getting stuff done during the F37 dev cycle. We can revisit process after that.
Emmanuel
If this is simply a matter of moving our infrastructure from Pagure to Gitlab but both are still hosted on private Fedora Servers, than I agree that I don't see the need to move to Gitlab. It doesn't appear that any of the Fedora projects have moved to the gitlab.com site, so that is why I'm assuming that we are talking about what we are self hosting on our Fedora infrastructure. There may be a slight advantage of having a browser based editor for our docs pages, but I also agree that there seems to be enough on the plate of our WG without adding an infrastructure change. Perhaps after the next cycle if we get some of our big rocks taken care of during the F37 cycle. 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.
* mowest [06/05/2022 04:02] :
If this is simply a matter of moving our infrastructure from Pagure to Gitlab but both are still hosted on private Fedora Servers, than I agree that I don't see the need to move to Gitlab.
FTR, I don't think we have ever had the option of Gitlab running on Red Hat servers, only the one of using Gitlab running on Gitlab server, through their program for open source.
Emmanuel
Am 06.05.2022 um 06:02 schrieb mowest mowest@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.
but both are still hosted on private Fedora Servers,
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.
Pagure will remain available, at least for some time, but obviously more or less unmaintained. The details are a bit unclear to me.
See https://discussion.fedoraproject.org/t/gitlab-available-for-fedora/33672 for example
I think it is decidedly unfortunate to practically force Fedora contributors to entrust their data to yet another commercial Internet shark. It may be OK for now, but if gitlab is reasonably successful, it's only a matter of time before some tech giant, possibly even some Russian or Chinese state-owned corporation or even worse Oracle, takes it over. But the discussion and the decision is done and closed. The technical features of gitlab are too tempting and our Fedora techies obviously behave no much differently than any other artless Internet user who still thinks Facebook and Co are "social media". All ideas of freedom, self-determination, privacy, locked in etc then turn into "social chatter" and nice decoration for the front page. As far as I can tell after the first impression, Debian has, unfortunately once again, found a cleverer solution - or just better hidden. </rant off>
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.
Peter
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@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.
- 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.
--------- mowest --------- discoverfoss.com
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@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.
Hello team,
I agree there is no need to migrate, if pagure do what we need, then no need to migrate. I put it in discussion because pagure will be left behind at some point, but that doesn't mean it will be immediately nor will it stop working. Maybe even we could take pagure and maintain it ourselves, dunno.
I've been using the Fedora Namespace in GitLab without any issues until now, and TBCH I love GitLab, both the software and the company, so IF at some point we want to migrate, count on me to help.
Best Regards,
On Fri, 2022-05-06 at 14:52 +0000, 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@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.
I agree the process is confusing, but you went wrong here. What you should do at this point is ignore the login screen and go back to the SSO login link. Now your account is confirmed, it will work and fully log you in, after you accept Gitlab's T&Cs.
I just went through the same thing, and yeah I agree it's messy.
server@lists.fedoraproject.org
-
Adam Williamson -
Alexander Bokovoy -
Eduard Lucena -
Emmanuel Seyman -
mowest -
Neal Gompa -
Peter Boy