101010.pl

PhilSo currently I'm hosting <code>gptel-org-tools</code> on my own forge... <a href="https://git.bajsicki.com/phil/gptel-org-tools" rel="nofollow noopener" target="_blank">https://git.bajsicki.com/phil/gptel-org-tools</a> I can't seem to find a good way for people to create issues. I thought that creating issues via email was a thing with Forgejo, but it appears not. So here's a poll. Despite my hatred of Microsoft, is it for the best to move the repo to GitHub? Or is there some way to federate with GitHub users so I don't need to open public sign-ups on my git? I'm not exactly clear on what the move is here. <a href="https://fed.bajsicki.com/tags/Emacs" rel="nofollow noopener" target="_blank">#Emacs</a> <a href="https://fed.bajsicki.com/tags/gptel" rel="nofollow noopener" target="_blank">#gptel</a> <a href="https://fed.bajsicki.com/tags/gitforge" rel="nofollow noopener" target="_blank">#gitforge</a> <a href="https://fed.bajsicki.com/tags/forgejo" rel="nofollow noopener" target="_blank">#forgejo</a> <a href="https://fed.bajsicki.com/tags/github" rel="nofollow noopener" target="_blank">#github</a> <a href="https://fed.bajsicki.com/tags/microsoft" rel="nofollow noopener" target="_blank">#microsoft</a> <a href="https://fed.bajsicki.com/tags/foss" rel="nofollow noopener" target="_blank">#foss</a>

jablkoziemne<a href="https://defcon.social/@ngn" class="u-url mention">@ngn</a> Thanks for elaborating on this topic.Im still not sure about <a href="https://101010.pl/tags/fedora" class="mention hashtag" rel="tag">#fedora</a> being testing ground for <a href="https://101010.pl/tags/rhel" class="mention hashtag" rel="tag">#rhel</a>, they surely have really formal way of introducing and documenting changes with their change proposals <a href="https://docs.fedoraproject.org/en-US/program_management/changes_guide/" target="_blank" rel="nofollow noopener" translate="no">https://docs.fedoraproject.org/en-US/program_management/changes_guide/</a> which to my knowledge from one of episodes of <a href="https://101010.pl/tags/techovertea" class="mention hashtag" rel="tag">#techovertea</a> by <a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention">@BrodieOnLinux</a> are later reviewed by <a href="https://101010.pl/tags/rhel" class="mention hashtag" rel="tag">#rhel</a> and merged/notmerged into it. Some people asked about <a href="https://101010.pl/tags/fedora" class="mention hashtag" rel="tag">#fedora</a> and <a href="https://101010.pl/tags/rhel" class="mention hashtag" rel="tag">#rhel</a> relationship in the past <a href="https://discussion.fedoraproject.org/t/request-for-a-detailed-breakdown-of-the-relationship-between-fedora-and-red-hat/86775" target="_blank" rel="nofollow noopener" translate="no">https://discussion.fedoraproject.org/t/request-for-a-detailed-breakdown-of-the-relationship-between-fedora-and-red-hat/86775</a>For the source code availability, even with <a href="https://101010.pl/tags/gpl" class="mention hashtag" rel="tag">#gpl</a> <a href="https://101010.pl/tags/license" class="mention hashtag" rel="tag">#license</a> you are only required to share the source code to the recipients of the application/whatever you are distributing/selling, just because most <a href="https://101010.pl/tags/gitforge" class="mention hashtag" rel="tag">#gitforge</a> services allow everyone to view the projects stored on their servers, it doesn't mean it has to be like that - though, for open development process, maybe it should be? But that doesn't change that if <a href="https://101010.pl/tags/redhat" class="mention hashtag" rel="tag">#redhat</a> called their <a href="https://101010.pl/tags/downstream" class="mention hashtag" rel="tag">#downstream</a> <a href="https://101010.pl/tags/distro" class="mention hashtag" rel="tag">#distro</a> "freeloaders", its really rude.They are doing it for profit, I guess. Not caring about their potential customers will get them eventually. But besides that, everyone has to earn money somehow, and having <a href="https://101010.pl/tags/foss" class="mention hashtag" rel="tag">#foss</a> product doesn't make it easy. > best you can do is to put new tech and software into your repos, and encourage users to test and use it, which is what most rolling distros doI disagree, although its good to have unstable features as opt-in, it introduces bias where the new features are only used by people that know about them, and know how to enable/switch to them. This way, you are severely reducing amount of useful bug reports that are crucial to know what are your users even doing.Ideally you would perform AB tests, with ever increasing number of real users, and in case of issues you would simply <a href="https://101010.pl/tags/rollback" class="mention hashtag" rel="tag">#rollback</a> the update to the latest stable version. Sadly, it would require that rollback feature, and prefill all system information in the bug report.

DWeb<a href="https://toot.radicle.xyz/@radicle" class="u-url mention" rel="nofollow noopener" target="_blank">@radicle</a> looks like an interesting Free Software to check out: it’s a peer-to-peer, local-first git forge for the decentralized Web! 👀<a href="https://social.coop/tags/Radicle" class="mention hashtag" rel="nofollow noopener" target="_blank">#Radicle</a> <a href="https://social.coop/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#p2p</a> <a href="https://social.coop/tags/DWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#DWeb</a> <a href="https://social.coop/tags/decentralization" class="mention hashtag" rel="nofollow noopener" target="_blank">#decentralization</a> <a href="https://social.coop/tags/decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#decentralized</a> <a href="https://social.coop/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#git</a> <a href="https://social.coop/tags/gitForge" class="mention hashtag" rel="nofollow noopener" target="_blank">#gitForge</a> <a href="https://social.coop/tags/software" class="mention hashtag" rel="nofollow noopener" target="_blank">#software</a> <a href="https://social.coop/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeSoftware</a> <a href="https://social.coop/tags/openSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSource</a> <a href="https://social.coop/tags/localFirst" class="mention hashtag" rel="nofollow noopener" target="_blank">#localFirst</a><a href="https://radicle.xyz/" rel="nofollow noopener" translate="no" target="_blank">https://radicle.xyz/</a>

Acid Bong[kinda solved: I already applied for Codeberg's Woodpecker access]Ight, Fedi, i know there's a bunch of nerds, so here's a wee request.What public <a href="https://cupoftea.social/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#git</a> forges with open registration and a CI would you recommend?My requirements:<ul><li>not Github</li><li>not Gitlab — too slow interface + incorrect table of contents behaviour (at least in Org files)</li><li>the CI should be free of charge (sorry, sr.ht)</li><li>no Drone CI — it lacks some functionality i'm interested in (sorry, tildegit and envs)</li></ul>I guess, that only leaves me with <a href="https://cupoftea.social/tags/Forgejo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Forgejo</a> / <a href="https://cupoftea.social/tags/Gitea" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gitea</a> and <a href="https://cupoftea.social/tags/Sourcehut" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sourcehut</a> instances. I'm already aware of Codeberg (might consider its <a href="https://cupoftea.social/tags/Woodpecker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Woodpecker</a>, if I can't find anything else), Tildegit and envs' gitea (these two use Drone, which I don't quite like), Disroot's forgejo (doesn't have a CI). What else?<a href="https://cupoftea.social/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#Development</a> <a href="https://cupoftea.social/tags/gitforge" class="mention hashtag" rel="nofollow noopener" target="_blank">#gitforge</a> <a href="https://cupoftea.social/tags/cicd" class="mention hashtag" rel="nofollow noopener" target="_blank">#cicd</a>

AmgineWhy am I not hearing more discussion about this?<a href="https://mamot.fr/tags/Fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fedora</a> moves toward <a href="https://mamot.fr/tags/Forgejo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Forgejo</a> <a href="https://fedoramagazine.org/fedora-moves-towards-forgejo-a-unified-decision/" rel="nofollow noopener" translate="no" target="_blank">https://fedoramagazine.org/fedora-moves-towards-forgejo-a-unified-decision/</a>This could be massive, <a href="https://mamot.fr/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#git</a> <a href="https://mamot.fr/tags/gitforge" class="mention hashtag" rel="nofollow noopener" target="_blank">#gitforge</a> <a href="https://mamot.fr/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a>

Alexandre Dulaunoy<a href="https://retro.social/@patrick" class="u-url mention" rel="nofollow noopener" target="_blank">@patrick</a> I don't get why they Apache Software Foundation <a href="https://fosstodon.org/@TheASF" class="u-url mention" rel="nofollow noopener" target="_blank">@TheASF</a> are not doing a self-hosting of git repositories with <a href="https://floss.social/@forgejo" class="u-url mention" rel="nofollow noopener" target="_blank">@forgejo</a> and sync with <a href="https://hachyderm.io/@github" class="u-url mention" rel="nofollow noopener" target="_blank">@github</a> or any other proprietary git hosting services. I know the only issue is the sync of issues but having a copy on a self-hosted forge won't hurt and for resilience is also better. <a href="https://paperbay.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://paperbay.org/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#git</a> <a href="https://paperbay.org/tags/gitforge" class="mention hashtag" rel="nofollow noopener" target="_blank">#gitforge</a> <a href="https://paperbay.org/tags/forge" class="mention hashtag" rel="nofollow noopener" target="_blank">#forge</a>

amoloneyVol. I – Fedora Council 2024 HackfestDuring the Council’s <a href="https://fedoraproject.org/wiki/Council/2024_Hackfest" rel="nofollow noopener" target="_blank">February 2024 hackfest</a>, 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, <a href="https://discussion.fedoraproject.org/tags/c/project/7/git-forge-future" rel="nofollow noopener" target="_blank">#git-forge-future</a> is a good place to start.Instead of one huge post, the <a href="https://communityblog.fedoraproject.org/category/council/" rel="nofollow noopener" target="_blank">Fedora Council</a> 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. PagureFirst, 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 forgeSecond, 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: <ol><li>GitLab Community Edition</li><li>Forgejo (a fork of Gitea)</li></ol>In both cases, the Council determined that the project will need to run the software in Fedora Infrastructure. <a href="https://communityblog.fedoraproject.org/category/infrastructure/" rel="nofollow noopener" target="_blank">Fedora Infrastructure</a> 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 <a href="https://docs.fedoraproject.org/en-US/cpe/" rel="nofollow noopener" target="_blank">Community Platform Engineering (CPE)</a> 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 futureTo keep track of feedback and conversations in one place, direct all feedback and comments to the <a href="https://discussion.fedoraproject.org/tags/c/project/7/git-forge-future" rel="nofollow noopener" target="_blank">#git-forge-future</a> 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 <a href="https://docs.fedoraproject.org/en-US/project/code-of-conduct/" rel="nofollow noopener" target="_blank">Fedora Code of Conduct</a>.<a href="https://communityblog.fedoraproject.org/2024-git-forge-evaluation/" rel="nofollow noopener" target="_blank">https://communityblog.fedoraproject.org/2024-git-forge-evaluation/</a><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/community-platform-engineering/" target="_blank">#CommunityPlatformEngineering</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/council-hackfest-2024/" target="_blank">#CouncilHackfest2024</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/cpe/" target="_blank">#CPE</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/dist-git/" target="_blank">#distGit</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/git-forge/" target="_blank">#gitForge</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/gitlab/" target="_blank">#GitLab</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/hackfests/" target="_blank">#hackfests</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/pagure/" target="_blank">#Pagure</a>

Recent searches

Search options

Administered by:

Server stats:

#gitForge