#pagure — Public Fediverse posts

If you host anything at Pagure.io, please read

https://communityblog.fedoraproject.org/the-forge-is-our-new-home/

and migrate.

Pagure.io will become read-only in June

#Fedora #Pagure

If you host anything at Pagure.io, please read

https://communityblog.fedoraproject.org/the-forge-is-our-new-home/

and migrate.

Pagure.io will become read-only in June

#Fedora #Pagure

If you host anything at Pagure.io, please read

https://communityblog.fedoraproject.org/the-forge-is-our-new-home/

and migrate.

Pagure.io will become read-only in June

#Fedora #Pagure

If you host anything at Pagure.io, please read

https://communityblog.fedoraproject.org/the-forge-is-our-new-home/

and migrate.

Pagure.io will become read-only in June

#Fedora #Pagure

If you host anything at Pagure.io, please read

https://communityblog.fedoraproject.org/the-forge-is-our-new-home/

and migrate.

Pagure.io will become read-only in June

#Fedora #Pagure

It's almost certain by now that tomorrow, 2024-12-23, the #Fedora council will announce the "decision to migrate Fedoras git forge to #forgejo and sunset #pagure." That's a HUGE win for @forgejo and the Fedora project IMHO. I am so looking forward to what new code this might deliver :)

It's almost certain by now that tomorrow, 2024-12-23, the #Fedora council will announce the "decision to migrate Fedoras git forge to #forgejo and sunset #pagure." That's a HUGE win for @forgejo and the Fedora project IMHO. I am so looking forward to what new code this might deliver :)

It's almost certain by now that tomorrow, 2024-12-23, the #Fedora council will announce the "decision to migrate Fedoras git forge to #forgejo and sunset #pagure." That's a HUGE win for @forgejo and the Fedora project IMHO. I am so looking forward to what new code this might deliver :)

It's almost certain by now that tomorrow, 2024-12-23, the #Fedora council will announce the "decision to migrate Fedoras git forge to #forgejo and sunset #pagure." That's a HUGE win for @forgejo and the Fedora project IMHO. I am so looking forward to what new code this might deliver :)

SUSE Hack Week is over :( But it was a great time, can't wait for 2025! Day 5 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-5.html
Lot of coding today, actually only coding the whole day :D I solved the annoying problem from yesterday and finished around 2/3 of what was planned. I hope to get the rest done in the next week or two. My Goals were probably too ambitious, as always ;)

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

SUSE Hack Week is over :( But it was a great time, can't wait for 2025! Day 5 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-5.html
Lot of coding today, actually only coding the whole day :D I solved the annoying problem from yesterday and finished around 2/3 of what was planned. I hope to get the rest done in the next week or two. My Goals were probably too ambitious, as always ;)

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

SUSE Hack Week is over :( But it was a great time, can't wait for 2025! Day 5 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-5.html
Lot of coding today, actually only coding the whole day :D I solved the annoying problem from yesterday and finished around 2/3 of what was planned. I hope to get the rest done in the next week or two. My Goals were probably too ambitious, as always ;)

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

SUSE Hack Week is over :( But it was a great time, can't wait for 2025! Day 5 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-5.html
Lot of coding today, actually only coding the whole day :D I solved the annoying problem from yesterday and finished around 2/3 of what was planned. I hope to get the rest done in the next week or two. My Goals were probably too ambitious, as always ;)

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

SUSE Hack Week day 4 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-4.html
Nothing fancy today. I had to fix a couple of things in my pagure dev instance. Writing the plugin code went fine till I hit a weird issue with one of the tests that I couldn't solve yet. Overall progress was ok but I lost a lot of time with unexpected problems. Let's see what will be finished on the last day tomorrow.

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

SUSE Hack Week day 4 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-4.html
Nothing fancy today. I had to fix a couple of things in my pagure dev instance. Writing the plugin code went fine till I hit a weird issue with one of the tests that I couldn't solve yet. Overall progress was ok but I lost a lot of time with unexpected problems. Let's see what will be finished on the last day tomorrow.

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

SUSE Hack Week day 4 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-4.html
Nothing fancy today. I had to fix a couple of things in my pagure dev instance. Writing the plugin code went fine till I hit a weird issue with one of the tests that I couldn't solve yet. Overall progress was ok but I lost a lot of time with unexpected problems. Let's see what will be finished on the last day tomorrow.

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

SUSE Hack Week day 4 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-4.html
Nothing fancy today. I had to fix a couple of things in my pagure dev instance. Writing the plugin code went fine till I hit a weird issue with one of the tests that I couldn't solve yet. Overall progress was ok but I lost a lot of time with unexpected problems. Let's see what will be finished on the last day tomorrow.

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

Another day SUSE Hack Week, another recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-3.html
The time I could invest today was pretty limited. I focused on further Architecture improvements. And started with the pagure ci plugin implementation. It's in an early stage but I'm confident that there is more to demonstrate tomorrow.

My Project: AWS CodePipeline CI plugin for pagure on code.opensuse.org (https://hackweek.opensuse.org/projects/aws-codepipeline-ci-plugin-for-pagure-on-code-dot-opensuse-dot-org)

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

Another day SUSE Hack Week, another recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-3.html
The time I could invest today was pretty limited. I focused on further Architecture improvements. And started with the pagure ci plugin implementation. It's in an early stage but I'm confident that there is more to demonstrate tomorrow.

My Project: AWS CodePipeline CI plugin for pagure on code.opensuse.org (https://hackweek.opensuse.org/projects/aws-codepipeline-ci-plugin-for-pagure-on-code-dot-opensuse-dot-org)

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

Another day SUSE Hack Week, another recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-3.html
The time I could invest today was pretty limited. I focused on further Architecture improvements. And started with the pagure ci plugin implementation. It's in an early stage but I'm confident that there is more to demonstrate tomorrow.

My Project: AWS CodePipeline CI plugin for pagure on code.opensuse.org (https://hackweek.opensuse.org/projects/aws-codepipeline-ci-plugin-for-pagure-on-code-dot-opensuse-dot-org)

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

Another day SUSE Hack Week, another recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-3.html
The time I could invest today was pretty limited. I focused on further Architecture improvements. And started with the pagure ci plugin implementation. It's in an early stage but I'm confident that there is more to demonstrate tomorrow.

My Project: AWS CodePipeline CI plugin for pagure on code.opensuse.org (https://hackweek.opensuse.org/projects/aws-codepipeline-ci-plugin-for-pagure-on-code-dot-opensuse-dot-org)

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

A couple bug fixes and improvements. Followed by research, tests and design decisions. SUSE Hack Week Day 2 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-2.html

I was hoping for a bit more progress today, bug hunting and planning took quite a while. Three days left, I'm still on track and confident that I have something usable at the end of the week.

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

A couple bug fixes and improvements. Followed by research, tests and design decisions. SUSE Hack Week Day 2 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-2.html

I was hoping for a bit more progress today, bug hunting and planning took quite a while. Three days left, I'm still on track and confident that I have something usable at the end of the week.

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

A couple bug fixes and improvements. Followed by research, tests and design decisions. SUSE Hack Week Day 2 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-2.html

I was hoping for a bit more progress today, bug hunting and planning took quite a while. Three days left, I'm still on track and confident that I have something usable at the end of the week.

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

A couple bug fixes and improvements. Followed by research, tests and design decisions. SUSE Hack Week Day 2 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-2.html

I was hoping for a bit more progress today, bug hunting and planning took quite a while. Three days left, I'm still on track and confident that I have something usable at the end of the week.

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

I finally fixed a long annoying issue and completed two out of four goals, great first day :) SUSE Hack Week Day 1 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-1.html
My Project: AWS CodePipeline CI plugin for pagure on code.opensuse.org (https://hackweek.opensuse.org/projects/aws-codepipeline-ci-plugin-for-pagure-on-code-dot-opensuse-dot-org)

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

I finally fixed a long annoying issue and completed two out of four goals, great first day :) SUSE Hack Week Day 1 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-1.html
My Project: AWS CodePipeline CI plugin for pagure on code.opensuse.org (https://hackweek.opensuse.org/projects/aws-codepipeline-ci-plugin-for-pagure-on-code-dot-opensuse-dot-org)

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

I finally fixed a long annoying issue and completed two out of four goals, great first day :) SUSE Hack Week Day 1 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-1.html
My Project: AWS CodePipeline CI plugin for pagure on code.opensuse.org (https://hackweek.opensuse.org/projects/aws-codepipeline-ci-plugin-for-pagure-on-code-dot-opensuse-dot-org)

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

I finally fixed a long annoying issue and completed two out of four goals, great first day :) SUSE Hack Week Day 1 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-1.html
My Project: AWS CodePipeline CI plugin for pagure on code.opensuse.org (https://hackweek.opensuse.org/projects/aws-codepipeline-ci-plugin-for-pagure-on-code-dot-opensuse-dot-org)

#SUSE #openSUSE #HackWeek #pagure #AWS #CodePipeline #AWSCodePipeline #OpenSource #Python

I did not realize that the #fedora git-forge-future discussion has been going on since last year. Learnt some pretty interesting tidbits regarding #forgejo and #pagure.

My personal opinion as a random bystander is a +1 for Forgejo, mainly due possible issues with "Open-Core" GitLab CE.

That said, I believe Fedora infra is pretty scattered so I wonder what can and what can't be integrated into Forgejo atm as its feature set is relatively limited afaik.

I've updated my Hare COPR to have the latest QBE commits and 0.24.2-rc1 builds of hare and harec. Available for Fedora 39+ and EPEL 9:

$ dnf copr enable mroche/hare
$ dnf install hare

If you have previous iterations of the packages you may need to run some dnf swaps, but there should not be any glaring issues. Let me know if you run into anything pesky!

#hare #harelang #fedora #epel #copr #centos #centosstream #pagure

I've updated my Hare COPR to have the latest QBE commits and 0.24.2-rc1 builds of hare and harec. Available for Fedora 39+ and EPEL 9:

$ dnf copr enable mroche/hare
$ dnf install hare

If you have previous iterations of the packages you may need to run some dnf swaps, but there should not be any glaring issues. Let me know if you run into anything pesky!

#hare #harelang #fedora #epel #copr #centos #centosstream #pagure

I've updated my Hare COPR to have the latest QBE commits and 0.24.2-rc1 builds of hare and harec. Available for Fedora 39+ and EPEL 9:

$ dnf copr enable mroche/hare
$ dnf install hare

If you have previous iterations of the packages you may need to run some dnf swaps, but there should not be any glaring issues. Let me know if you run into anything pesky!

#hare #harelang #fedora #epel #copr #centos #centosstream #pagure

I've updated my Hare COPR to have the latest QBE commits and 0.24.2-rc1 builds of hare and harec. Available for Fedora 39+ and EPEL 9:

$ dnf copr enable mroche/hare
$ dnf install hare

If you have previous iterations of the packages you may need to run some dnf swaps, but there should not be any glaring issues. Let me know if you run into anything pesky!

#hare #harelang #fedora #epel #copr #centos #centosstream #pagure

Désolé à toutes les personnes qui ont participé au sondage, j'ai finalement opté pour https://pagu.re/ :blobsmilehappyeyes:
#pagure

Désolé à toutes les personnes qui ont participé au sondage, j'ai finalement opté pour https://pagu.re/ :blobsmilehappyeyes:
#pagure

Désolé à toutes les personnes qui ont participé au sondage, j'ai finalement opté pour https://pagu.re/ :blobsmilehappyeyes:
#pagure

Désolé à toutes les personnes qui ont participé au sondage, j'ai finalement opté pour https://pagu.re/ :blobsmilehappyeyes:
#pagure

Vol. I – Fedora Council 2024 Hackfest

During the Council’s February 2024 hackfest, we discussed the future of Fedora’s git forge – that is, the platform Fedora uses for version control and tracking for packages, source code, documentation, and more. This topic has been around for quite some time. If you are just coming into this conversation, or would like a refresher, #git-forge-future is a good place to start.

Instead of one huge post, the Fedora Council divided the follow-ups from our hack-fest into a mini-series of posts throughout April that will cover all the topics we discussed and made decisions on. In each post, we will walk through one core topic, and share our discussion and thought process on how we reached our outcomes. The first in this series, because why not start strong 🙂 , is an update on our git forge evaluation. Read on for important information.

The Council arrived at two main decisions during this discussion. 

Pagure

First, the Council does not see Pagure as a viable git forge solution for Fedora’s future. Instead, we will investigate other git forge options which meet our core community values: Freedom, Features, Friends, First. When a suitable solution is found, the work needed to migrate to the new git forge will be shared. 

At a later date, the Council will announce a sunsetting date for Pagure, with ample time for projects to migrate to the replacement.

Options for an alternate git forge

Second, the Council examined a long list of possibilities, and eliminated those that do not fit. We narrowed down the list to these options we think might meet the needs and spirit of Fedora: 

1. GitLab Community Edition
2. Forgejo (a fork of Gitea)

In both cases, the Council determined that the project will need to run the software in Fedora Infrastructure. Fedora Infrastructure previously investigated hosting possibilities from GitLab at length, and could not find something workable without compromising on our community values for software freedom.

The Council is grateful to everything the Pagure developers have done for us, and acknowledge Pagure’s immense positive impact on Fedora. In the end, these other two options were what the Council felt we could honestly ask our community to use. 

The Community Platform Engineering (CPE) Team is a Red Hat-sponsored team that supports Fedora Infrastructure and Release Engineering with staffing, efforts, and resources. The Council will ask the Red Hat CPE to lead the maintenance efforts alongside the community. Therefore, the Council encourages the community to collaborate and support the Red Hat CPE in an in-depth technical evaluation for both options.

When these investigations are complete, the project will have at least two weeks of community discussion on the reports. Then, the Council will select an option and will launch a Community Initiative implementing the migration plan.

Share your feedback on git forge future

To keep track of feedback and conversations in one place, direct all feedback and comments to the #git-forge-future tag on Fedora Discussion. You can reply to an existing topic or start a new one.

This will be a long journey for us to take together as a community. Thank you for your patience and feedback as we go down this road together. Please remember to keep your feedback courteous, respectful, and aligned with the Fedora Code of Conduct.

https://communityblog.fedoraproject.org/2024-git-forge-evaluation/

#CommunityPlatformEngineering #CouncilHackfest2024 #CPE #distGit #gitForge #GitLab #hackfests #Pagure

Vol. I – Fedora Council 2024 Hackfest

During the Council’s February 2024 hackfest, we discussed the future of Fedora’s git forge – that is, the platform Fedora uses for version control and tracking for packages, source code, documentation, and more. This topic has been around for quite some time. If you are just coming into this conversation, or would like a refresher, #git-forge-future is a good place to start.

Instead of one huge post, the Fedora Council divided the follow-ups from our hack-fest into a mini-series of posts throughout April that will cover all the topics we discussed and made decisions on. In each post, we will walk through one core topic, and share our discussion and thought process on how we reached our outcomes. The first in this series, because why not start strong 🙂 , is an update on our git forge evaluation. Read on for important information.

The Council arrived at two main decisions during this discussion. 

Pagure

First, the Council does not see Pagure as a viable git forge solution for Fedora’s future. Instead, we will investigate other git forge options which meet our core community values: Freedom, Features, Friends, First. When a suitable solution is found, the work needed to migrate to the new git forge will be shared. 

At a later date, the Council will announce a sunsetting date for Pagure, with ample time for projects to migrate to the replacement.

Options for an alternate git forge

Second, the Council examined a long list of possibilities, and eliminated those that do not fit. We narrowed down the list to these options we think might meet the needs and spirit of Fedora: 

1. GitLab Community Edition
2. Forgejo (a fork of Gitea)

In both cases, the Council determined that the project will need to run the software in Fedora Infrastructure. Fedora Infrastructure previously investigated hosting possibilities from GitLab at length, and could not find something workable without compromising on our community values for software freedom.

The Council is grateful to everything the Pagure developers have done for us, and acknowledge Pagure’s immense positive impact on Fedora. In the end, these other two options were what the Council felt we could honestly ask our community to use. 

The Community Platform Engineering (CPE) Team is a Red Hat-sponsored team that supports Fedora Infrastructure and Release Engineering with staffing, efforts, and resources. The Council will ask the Red Hat CPE to lead the maintenance efforts alongside the community. Therefore, the Council encourages the community to collaborate and support the Red Hat CPE in an in-depth technical evaluation for both options.

When these investigations are complete, the project will have at least two weeks of community discussion on the reports. Then, the Council will select an option and will launch a Community Initiative implementing the migration plan.

Share your feedback on git forge future

To keep track of feedback and conversations in one place, direct all feedback and comments to the #git-forge-future tag on Fedora Discussion. You can reply to an existing topic or start a new one.

This will be a long journey for us to take together as a community. Thank you for your patience and feedback as we go down this road together. Please remember to keep your feedback courteous, respectful, and aligned with the Fedora Code of Conduct.

https://communityblog.fedoraproject.org/2024-git-forge-evaluation/

#CommunityPlatformEngineering #CouncilHackfest2024 #CPE #distGit #gitForge #GitLab #hackfests #Pagure

Vol. I – Fedora Council 2024 Hackfest

During the Council’s February 2024 hackfest, we discussed the future of Fedora’s git forge – that is, the platform Fedora uses for version control and tracking for packages, source code, documentation, and more. This topic has been around for quite some time. If you are just coming into this conversation, or would like a refresher, #git-forge-future is a good place to start.

Instead of one huge post, the Fedora Council divided the follow-ups from our hack-fest into a mini-series of posts throughout April that will cover all the topics we discussed and made decisions on. In each post, we will walk through one core topic, and share our discussion and thought process on how we reached our outcomes. The first in this series, because why not start strong 🙂 , is an update on our git forge evaluation. Read on for important information.

The Council arrived at two main decisions during this discussion. 

Pagure

First, the Council does not see Pagure as a viable git forge solution for Fedora’s future. Instead, we will investigate other git forge options which meet our core community values: Freedom, Features, Friends, First. When a suitable solution is found, the work needed to migrate to the new git forge will be shared. 

At a later date, the Council will announce a sunsetting date for Pagure, with ample time for projects to migrate to the replacement.

Options for an alternate git forge

Second, the Council examined a long list of possibilities, and eliminated those that do not fit. We narrowed down the list to these options we think might meet the needs and spirit of Fedora: 

1. GitLab Community Edition
2. Forgejo (a fork of Gitea)

In both cases, the Council determined that the project will need to run the software in Fedora Infrastructure. Fedora Infrastructure previously investigated hosting possibilities from GitLab at length, and could not find something workable without compromising on our community values for software freedom.

The Council is grateful to everything the Pagure developers have done for us, and acknowledge Pagure’s immense positive impact on Fedora. In the end, these other two options were what the Council felt we could honestly ask our community to use. 

The Community Platform Engineering (CPE) Team is a Red Hat-sponsored team that supports Fedora Infrastructure and Release Engineering with staffing, efforts, and resources. The Council will ask the Red Hat CPE to lead the maintenance efforts alongside the community. Therefore, the Council encourages the community to collaborate and support the Red Hat CPE in an in-depth technical evaluation for both options.

When these investigations are complete, the project will have at least two weeks of community discussion on the reports. Then, the Council will select an option and will launch a Community Initiative implementing the migration plan.

Share your feedback on git forge future

To keep track of feedback and conversations in one place, direct all feedback and comments to the #git-forge-future tag on Fedora Discussion. You can reply to an existing topic or start a new one.

This will be a long journey for us to take together as a community. Thank you for your patience and feedback as we go down this road together. Please remember to keep your feedback courteous, respectful, and aligned with the Fedora Code of Conduct.

https://communityblog.fedoraproject.org/2024-git-forge-evaluation/

#CommunityPlatformEngineering #CouncilHackfest2024 #CPE #distGit #gitForge #GitLab #hackfests #Pagure

Vol. I – Fedora Council 2024 Hackfest

During the Council’s February 2024 hackfest, we discussed the future of Fedora’s git forge – that is, the platform Fedora uses for version control and tracking for packages, source code, documentation, and more. This topic has been around for quite some time. If you are just coming into this conversation, or would like a refresher, #git-forge-future is a good place to start.

Instead of one huge post, the Fedora Council divided the follow-ups from our hack-fest into a mini-series of posts throughout April that will cover all the topics we discussed and made decisions on. In each post, we will walk through one core topic, and share our discussion and thought process on how we reached our outcomes. The first in this series, because why not start strong 🙂 , is an update on our git forge evaluation. Read on for important information.

The Council arrived at two main decisions during this discussion. 

Pagure

First, the Council does not see Pagure as a viable git forge solution for Fedora’s future. Instead, we will investigate other git forge options which meet our core community values: Freedom, Features, Friends, First. When a suitable solution is found, the work needed to migrate to the new git forge will be shared. 

At a later date, the Council will announce a sunsetting date for Pagure, with ample time for projects to migrate to the replacement.

Options for an alternate git forge

Second, the Council examined a long list of possibilities, and eliminated those that do not fit. We narrowed down the list to these options we think might meet the needs and spirit of Fedora: 

1. GitLab Community Edition
2. Forgejo (a fork of Gitea)

In both cases, the Council determined that the project will need to run the software in Fedora Infrastructure. Fedora Infrastructure previously investigated hosting possibilities from GitLab at length, and could not find something workable without compromising on our community values for software freedom.

The Council is grateful to everything the Pagure developers have done for us, and acknowledge Pagure’s immense positive impact on Fedora. In the end, these other two options were what the Council felt we could honestly ask our community to use. 

The Community Platform Engineering (CPE) Team is a Red Hat-sponsored team that supports Fedora Infrastructure and Release Engineering with staffing, efforts, and resources. The Council will ask the Red Hat CPE to lead the maintenance efforts alongside the community. Therefore, the Council encourages the community to collaborate and support the Red Hat CPE in an in-depth technical evaluation for both options.

When these investigations are complete, the project will have at least two weeks of community discussion on the reports. Then, the Council will select an option and will launch a Community Initiative implementing the migration plan.

Share your feedback on git forge future

To keep track of feedback and conversations in one place, direct all feedback and comments to the #git-forge-future tag on Fedora Discussion. You can reply to an existing topic or start a new one.

This will be a long journey for us to take together as a community. Thank you for your patience and feedback as we go down this road together. Please remember to keep your feedback courteous, respectful, and aligned with the Fedora Code of Conduct.

https://communityblog.fedoraproject.org/2024-git-forge-evaluation/

#CommunityPlatformEngineering #CouncilHackfest2024 #CPE #distGit #gitForge #GitLab #hackfests #Pagure

Not to rain on a parade of #GitLab and some #Fedora projects embracing #GitLabEE, but the official web UI and mobile apps (by enthusiasts) for surfacing it are in a sorry state.

- Web: very JavaScript-heavy, not optimized for mobile.
- Web (mobile): can't view comments without logging in.
- Web: too many fields are immediately thrown into the mix, despite the lack of usage. Mobile apps: the complete absence thereof.
- Web: issue tasks open either in a popup and as a separate page, but not easy to predict.
- Web: you wanna click on the task - too bad, it's confused with drag-and-drop.

This all made me reminisce about #GitNex, #Codeberg, #Forgejo and plain ol' issues, without all that fluff. And then, there is #Pagure: it lets you work with issues and pull requests as #Git repos of their own. I have to wonder why fedorians resort to GitLab, when in-house solution (such as Pagure) exists. I assume, it's just that - a fluff. I simpathize it is hard to say no to these minute conveniences.

Not to rain on a parade of #GitLab and some #Fedora projects embracing #GitLabEE, but the official web UI and mobile apps (by enthusiasts) for surfacing it are in a sorry state.

- Web: very JavaScript-heavy, not optimized for mobile.
- Web (mobile): can't view comments without logging in.
- Web: too many fields are immediately thrown into the mix, despite the lack of usage. Mobile apps: the complete absence thereof.
- Web: issue tasks open either in a popup and as a separate page, but not easy to predict.
- Web: you wanna click on the task - too bad, it's confused with drag-and-drop.

This all made me reminisce about #GitNex, #Codeberg, #Forgejo and plain ol' issues, without all that fluff. And then, there is #Pagure: it lets you work with issues and pull requests as #Git repos of their own. I have to wonder why fedorians resort to GitLab, when in-house solution (such as Pagure) exists. I assume, it's just that - a fluff. I simpathize it is hard to say no to these minute conveniences.

Not to rain on a parade of #GitLab and some #Fedora projects embracing #GitLabEE, but the official web UI and mobile apps (by enthusiasts) for surfacing it are in a sorry state.

- Web: very JavaScript-heavy, not optimized for mobile.
- Web (mobile): can't view comments without logging in.
- Web: too many fields are immediately thrown into the mix, despite the lack of usage. Mobile apps: the complete absence thereof.
- Web: issue tasks open either in a popup and as a separate page, but not easy to predict.
- Web: you wanna click on the task - too bad, it's confused with drag-and-drop.

This all made me reminisce about #GitNex, #Codeberg, #Forgejo and plain ol' issues, without all that fluff. And then, there is #Pagure: it lets you work with issues and pull requests as #Git repos of their own. I have to wonder why fedorians resort to GitLab, when in-house solution (such as Pagure) exists. I assume, it's just that - a fluff. I simpathize it is hard to say no to these minute conveniences.

Not to rain on a parade of #GitLab and some #Fedora projects embracing #GitLabEE, but the official web UI and mobile apps (by enthusiasts) for surfacing it are in a sorry state.

- Web: very JavaScript-heavy, not optimized for mobile.
- Web (mobile): can't view comments without logging in.
- Web: too many fields are immediately thrown into the mix, despite the lack of usage. Mobile apps: the complete absence thereof.
- Web: issue tasks open either in a popup and as a separate page, but not easy to predict.
- Web: you wanna click on the task - too bad, it's confused with drag-and-drop.

This all made me reminisce about #GitNex, #Codeberg, #Forgejo and plain ol' issues, without all that fluff. And then, there is #Pagure: it lets you work with issues and pull requests as #Git repos of their own. I have to wonder why fedorians resort to GitLab, when in-house solution (such as Pagure) exists. I assume, it's just that - a fluff. I simpathize it is hard to say no to these minute conveniences.

Not to rain on a parade of #GitLab and some #Fedora projects embracing #GitLabEE, but the official web UI and mobile apps (by enthusiasts) for surfacing it are in a sorry state.

- Web: very JavaScript-heavy, not optimized for mobile.
- Web (mobile): can't view comments without logging in.
- Web: too many fields are immediately thrown into the mix, despite the lack of usage. Mobile apps: the complete absence thereof.
- Web: issue tasks open either in a popup and as a separate page, but not easy to predict.
- Web: you wanna click on the task - too bad, it's confused with drag-and-drop.

This all made me reminisce about #GitNex, #Codeberg, #Forgejo and plain ol' issues, without all that fluff. And then, there is #Pagure: it lets you work with issues and pull requests as #Git repos of their own. I have to wonder why fedorians resort to GitLab, when in-house solution (such as Pagure) exists. I assume, it's just that - a fluff. I simpathize it is hard to say no to these minute conveniences.

Today I learned the usefulness of #git #subtree. It wasn't completely necessary, "git filter-branch" could achieve the same results by other means, but subtree just made it so much easier.

I've broken up my #COPR's cloud-native-utilities repo into their own distinct repos on #Pagure. The process was actually pretty straightfoward!

General overview since I'll run out of characters here:

https://paste.sr.ht/~omenos/46140c3432919c8dc74cb3fb255c67c5ed2b1a73

So this:

https://pagure.io/mroche/cloud-utilities

Has become:

https://pagure.io/group/mroche-cloud

Today I learned the usefulness of #git #subtree. It wasn't completely necessary, "git filter-branch" could achieve the same results by other means, but subtree just made it so much easier.

I've broken up my #COPR's cloud-native-utilities repo into their own distinct repos on #Pagure. The process was actually pretty straightfoward!

General overview since I'll run out of characters here:

https://paste.sr.ht/~omenos/46140c3432919c8dc74cb3fb255c67c5ed2b1a73

So this:

https://pagure.io/mroche/cloud-utilities

Has become:

https://pagure.io/group/mroche-cloud

Today I learned the usefulness of #git #subtree. It wasn't completely necessary, "git filter-branch" could achieve the same results by other means, but subtree just made it so much easier.

I've broken up my #COPR's cloud-native-utilities repo into their own distinct repos on #Pagure. The process was actually pretty straightfoward!

General overview since I'll run out of characters here:

https://paste.sr.ht/~omenos/46140c3432919c8dc74cb3fb255c67c5ed2b1a73

So this:

https://pagure.io/mroche/cloud-utilities

Has become:

https://pagure.io/group/mroche-cloud

Today I learned the usefulness of #git #subtree. It wasn't completely necessary, "git filter-branch" could achieve the same results by other means, but subtree just made it so much easier.

I've broken up my #COPR's cloud-native-utilities repo into their own distinct repos on #Pagure. The process was actually pretty straightfoward!

General overview since I'll run out of characters here:

https://paste.sr.ht/~omenos/46140c3432919c8dc74cb3fb255c67c5ed2b1a73

So this:

https://pagure.io/mroche/cloud-utilities

Has become:

https://pagure.io/group/mroche-cloud

@mcepl This works on #Pagure and #GitLab too. 😉

@mcepl This works on #Pagure and #GitLab too. 😉

@mcepl This works on #Pagure and #GitLab too. 😉

@mcepl This works on #Pagure and #GitLab too. 😉

@mcepl This works on #Pagure and #GitLab too. 😉

Really, what I would love to see is an activity aggregator across #git platforms - #GitHub, #Gitlab, #Forgejo, #Gitea, #Bitbucket, #Pagure, etc.

Really, what I would love to see is an activity aggregator across #git platforms - #GitHub, #Gitlab, #Forgejo, #Gitea, #Bitbucket, #Pagure, etc.

Really, what I would love to see is an activity aggregator across #git platforms - #GitHub, #Gitlab, #Forgejo, #Gitea, #Bitbucket, #Pagure, etc.

Really, what I would love to see is an activity aggregator across #git platforms - #GitHub, #Gitlab, #Forgejo, #Gitea, #Bitbucket, #Pagure, etc.