#gitforge — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #gitforge, aggregated by home.social.
-
-
-
-
-
-
Read this blog by @sourav666 on @itsfoss about the use of #Forgejo by the Dutch central #government:
https://itsfoss.com/news/netherlands-forgejo-migration/
"The platform is a self-hosted Forgejo instance, running on Dutch government infrastructure... It's free for all government organizations..."
"... this initiative is still in the pilot phase, with the rollout being kept deliberately gradual."
#overheid #DigitalSovereignty #DigitalAutonomy #GitForge #Netherlands #FOSS #OpenSource #Git
-
Look at this:
The beginning of a #GitForge by the Dutch government (overheid) based on #Forgejo.
Very good that the Dutch #government takes the first steps to become independent regarding their Git repositories.
Read why this important in a blog with a recommendation for a Git forge that I wrote a while ago (in Dutch):
https://developer.overheid.nl/blog/2025/11/11/git-forge-overheid
#Git #DigitalSovereignty #DigitalAutonomy #FOSS #opensource #Netherlands #overheid
-
My blog #BurgeonLab relies on #SourceHut Git and Builds. They’ve been down and at first I couldn’t deploy my site to my static host, #Bunnynet.
This triggered me to create a local script that runs all the fetch/build steps as an alternative pathway to upload...
View full note: https://burgeonlab.com/notes/2026/0408-3421
Syndicated via https://getindiekit.com
This is post 27 of #100DaysToOffload
#CICD #CI #Githubctions #srht #ddos #gitforge #git #continuousintegration #bash #script #statichost #statichosting
-
My blog #BurgeonLab relies on #SourceHut Git and Builds. They’ve been down and at first I couldn’t deploy my site to my static host, #Bunnynet.
This triggered me to create a local script that runs all the fetch/build steps as an alternative pathway to upload...
View full note: https://burgeonlab.com/notes/2026/0408-3421
Syndicated via https://getindiekit.com
This is post 27 of #100DaysToOffload
#CICD #CI #Githubctions #srht #ddos #gitforge #git #continuousintegration #bash #script #statichost #statichosting
-
My blog #BurgeonLab relies on #SourceHut Git and Builds. They’ve been down and at first I couldn’t deploy my site to my static host, #Bunnynet.
This triggered me to create a local script that runs all the fetch/build steps as an alternative pathway to upload...
View full note: https://burgeonlab.com/notes/2026/0408-3421
Syndicated via https://getindiekit.com
This is post 27 of #100DaysToOffload
#CICD #CI #Githubctions #srht #ddos #gitforge #git #continuousintegration #bash #script #statichost #statichosting
-
My blog #BurgeonLab relies on #SourceHut Git and Builds. They’ve been down and at first I couldn’t deploy my site to my static host, #Bunnynet.
This triggered me to create a local script that runs all the fetch/build steps as an alternative pathway to upload...
View full note: https://burgeonlab.com/notes/2026/0408-3421
Syndicated via https://getindiekit.com
This is post 27 of #100DaysToOffload
#CICD #CI #Githubctions #srht #ddos #gitforge #git #continuousintegration #bash #script #statichost #statichosting
-
My blog #BurgeonLab relies on #SourceHut Git and Builds. They’ve been down and at first I couldn’t deploy my site to my static host, #Bunnynet.
This triggered me to create a local script that runs all the fetch/build steps as an alternative pathway to upload...
View full note: https://burgeonlab.com/notes/2026/0408-3421
Syndicated via https://getindiekit.com
This is post 27 of #100DaysToOffload
#CICD #CI #Githubctions #srht #ddos #gitforge #git #continuousintegration #bash #script #statichost #statichosting
-
@rtyler I deployed my own instance of #OneDev and I haven't really used GitHub since. @forgejo is also a good option. Don't want to host your own? Then use code.onedev.io or codeberg.org public instances! #openSource #Git #GitForge #Collaboration
-
Forgejo: Die leichte Git-Forge für Sysadmins und DevOps
Warum du Forgejo kennen solltest Forgejo ist eine selbst gehostete, leichte Software-Forge, die auf Git basiert und dir als Sysadmin oder DevOps-Engineer eine vollständige Plattform für Code-Hosting, Issue-Tracking und CI/CD bietet. Du solltest sie kennen, weil sie ressourcenschonend läuft, 100% Free Software ist und Projekte wie Fedora sie für moderne, community-getriebene Workflows einsetzen. In der Sysadministration hilft sie dir, zentrale Repositories zu managen, ohne auf […]https://andreas-moor.de/forgejo-die-leichte-git-forge-fuer-sysadmins-und-devops/
-
@lexinova @nlnetlabs @nextcloud @terts
I wrote once a blog about #GitLab, #GitHub, and #Forgejo (#codeberg). What to choose?
It is in Dutch, but I'm pretty sure your browser can translate it for you:
https://developer.overheid.nl/blog/2025/11/11/git-forge-overheid
It is a recommendation for a #GitForge for the Dutch #government.
Part of the conclusion:
In summary, from the point of view of digital sovereignty and digital autonomy is a self-hosted Forgejo the best choice for the government. -
Have you heard any recent updates on the federation? Last time I checked (a few months back) it seemed to be in the "nice to have" category but not particularly actively being worked on.
-
🤖🔒 A fox-led #crusade to bamboozle #AI #scrapers from a "Git forge" that sounds as mythical as it does unnecessary. 29 minutes of your life wasted on a convoluted game of hide-and-seek with bots, because apparently, that's the hill we're choosing to die on. 🦊💻
https://vulpinecitrus.info/blog/guarding-git-forge-ai-scrapers/ #Fox #GitForge #HideAndSeek #TechHumor #HackerNews #ngated -
I feel like more projects should just self-host their core services again. Like self-hosting a #Git server (even if it is a fully fledged #Gitforge) isn't that complicated. And then you're in control of when it goes down and when it gets DDOSed you can just be like "LOL, *click disable internet uplink*" and continue working using e.g. a VPN towards it.
You can literally put it into your basement and serve millions of people whit almost no resources...
-
@number6 See for an elaborate discussion on the topic of using a free and #opensource git forge also this thread:
https://fosstodon.org/@organicmaps/115202657995358203
#gitforge #government #git #opensource #FOSS #digitalsovereignty
-
Ik heb een blog met een aanbeveling voor de Git-werkplaats van de #overheid geschreven:
https://developer.overheid.nl/blog/2025/11/11/git-forge-overheid
Conclusie: vanuit het oogpunt van digitale soevereiniteit en digitale autonomie is een self-hosted #Forgejo de beste keuze voor de overheid.
#Git #DigitaleSoevereiniteit #DigitaleAutonomie #GitLab #GitHub #FOSS #OpenSource #GitForge #SelfHosting
-
Anyone using https://git.sr.ht notice `git push` acting really slowly for the past few days? It was never like this before... Increased server load? #sourcehut #srht #git #gitforge #gitrepo
Example: Writing 11 objects, 1.2KB only. `time git push` took 1m3s total, 0.05s user, 0.04s system, 0% CPU.
Update: I think the error is local to me; I had some errors on `git fsck` and I streamlined `.build.yml`. It seems to be fixed now.
-
Anyone using https://git.sr.ht notice `git push` acting really slowly for the past few days? It was never like this before... Increased server load? #sourcehut #srht #git #gitforge #gitrepo
Example: Writing 11 objects, 1.2KB only. `time git push` took 1m3s total, 0.05s user, 0.04s system, 0% CPU.
Update: I think the error is local to me; I had some errors on `git fsck` and I streamlined `.build.yml`. It seems to be fixed now.
-
Anyone using https://git.sr.ht notice `git push` acting really slowly for the past few days? It was never like this before... Increased server load? #sourcehut #srht #git #gitforge #gitrepo
Example: Writing 11 objects, 1.2KB only. `time git push` took 1m3s total, 0.05s user, 0.04s system, 0% CPU.
Update: I think the error is local to me; I had some errors on `git fsck` and I streamlined `.build.yml`. It seems to be fixed now.
-
Anyone using https://git.sr.ht notice `git push` acting really slowly for the past few days? It was never like this before... Increased server load? #sourcehut #srht #git #gitforge #gitrepo
Example: Writing 11 objects, 1.2KB only. `time git push` took 1m3s total, 0.05s user, 0.04s system, 0% CPU.
Update: I think the error is local to me; I had some errors on `git fsck` and I streamlined `.build.yml`. It seems to be fixed now.
-
Anyone using https://git.sr.ht notice `git push` acting really slowly for the past few days? It was never like this before... Increased server load? #sourcehut #srht #git #gitforge #gitrepo
Example: Writing 11 objects, 1.2KB only. `time git push` took 1m3s total, 0.05s user, 0.04s system, 0% CPU.
Update: I think the error is local to me; I had some errors on `git fsck` and I streamlined `.build.yml`. It seems to be fixed now.
-
Finally migrated my personal website (powered by #HugoSSG) from #GitLab to #Codeberg. Including #CI via #ForgejoActions and hosting via #CodebergPages. Jobs are running on the local #homelab server.
There are jobs for building and deploying the website and for updating the contribution data through #contripy.
So far this has been very smooth and straightforward. Though I still need to learn the new CI workflow syntax as I'm used to GitLab from the daytime job.
-
Hey FOSS-community, I'm trying to compare #GitLab and @forgejo.
Some important aspects are:
- #DigitalSovereignty (most important)
- #SelfHosting
- #Collaboration between instances (#federation)
- #PublicValues
- Prevention of #VendorLockIn
- #Scalability
- #Robustness
- Guaranteed #support by professionals
- Software #freedom
- #Longevity
- Suitability for the #governmentDo you have any thoughts on this? Or any useful links?
cc: @Codeberg
-
okies, decided, today's the day... gonna start moving my repositories to codeberg... notabug.org's too consistently inconsistently available. n_n a little sad. mmmmmmuch fondness for notabug.org. ... i wonder, if i leave the repository off the end of the url in codeberg's migration tool... does it allow migrating everything in one go? :3
or should i skip codeberg, and go full forgejo? :)
#git #githosting #gitforge #notabug #codeberg #forgejo #forgefed
-
TIL Forgejo can map issue links to an external issue tracker! i knew it could put an Issues tab that links out, but now those pesky
#123links in commit messages can be useful and go somewhere!brb gonna go update all my code mirrors to link to the parent repo's issue board :3c
-
@radicle looks like an interesting Free Software to check out: it’s a peer-to-peer, local-first git forge for the decentralized Web! 👀
#Radicle #p2p #DWeb #decentralization #decentralized #git #gitForge #software #FreeSoftware #openSource #localFirst
-
#Fedora Moves Towards #Forgejo – A Unified Decision
https://fedoramagazine.org/fedora-moves-towards-forgejo-a-unified-decision/
'"[…] The decision to move to #Forgejo as the new #gitforge [for @fedora] has been made. There are numerous factors involved in this decision and this article will discuss them, present some background on the process, and invite one more chance for feedback before the formal Fedora Council vote. […]"'
-
On m'a linker ça : radicle.xyz/ 👀
#Git #GitForge -
"Forgejo changes license to GPLv3+"
https://forgejo.org/2024-08-gpl/
YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES
#Forgejo #FOSS #GPL #OpenSource #Git #GitForge -
@mxivi It makes no sense to be fatalistic about hosting open source repo somewhere outside the #GitHub. In fact, there are numbers of successful projects that reside on #Codeberg and people pick up quickly.
Anyone can sign up on Codeberg or fellow #Forgejo, #Gitea instances without fuss and silly animations (meant as a patronizing gesture, big no-no), while also disregarding the futile race for some "pretty" centralized activity chart. GitHub isn't the git forge we all deserved anyway: they just made it clearer recently by excluding non-GitHub git commits from the chart. And you still can make a portfolio that points to, surprise-surprise, profiles outside GitHub! Who might have thought that once making account on GH to contribute to your project of choice is no different from making just another on the side?
-
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:
- GitLab Community Edition
- 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:
- GitLab Community Edition
- 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:
- GitLab Community Edition
- 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:
- GitLab Community Edition
- 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:
- GitLab Community Edition
- 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
-
The next big thing in Fediverse would be the full launch of git forge federation.
I already can imagine hundreds of "Hi, gitea, creating this PR from Lemmy"...
