Search
89 results for “asmaloney”
-
Dun & Bradstreet is a company whose entire reason for existence is maintaining a database of company info.
I just called to update a phone number.
How long will that take?
"Up to 15 business days."
Wow. What kind of database are they using?
#database #business #DNB #DUNS #bureacracy #WhoUsesPhoneNumbersAnyways #venting
-
Great cartoon from The Marketoonist:
-
NodeJS (19.4) won't build on my laptop using homebrew anymore because it's running out of disk space.
I have 13.6 GB free space. 🤦
#NodeJS #ModernSoftware #bloatware #SoftwareBloat #BloatyMcBloatface
-
For anyone considering donating to the Red Cross note that they will continually waste your donation by sending you trinkets in the mail (at least here in Canada).
I've tried repeatedly to get them to stop, but they won't. I think this is the 5th snail mail full of junk now?
YMMV
-
I love that someone put a bread recipe on GitHub. 🍞
(No license though. 😆)
Looks tasty!
https://github.com/LanaSina/feeling_bread
Oh! Found the "someone" - @lana
-
I love that someone put a bread recipe on GitHub. 🍞
(No license though. 😆)
Looks tasty!
https://github.com/LanaSina/feeling_bread
Oh! Found the "someone" - @lana
-
I love that someone put a bread recipe on GitHub. 🍞
(No license though. 😆)
Looks tasty!
https://github.com/LanaSina/feeling_bread
Oh! Found the "someone" - @lana
-
I love that someone put a bread recipe on GitHub. 🍞
(No license though. 😆)
Looks tasty!
https://github.com/LanaSina/feeling_bread
Oh! Found the "someone" - @lana
-
-
Top ten posts in October 2025
https://library.hrmtc.com/2025/11/01/top-ten-posts-in-october-2025/
#account #achieve #AdamHassan #AdamHulse #AdeptusExemptus #AdeptusMajor #AdeptusMinor #adopted #alchemicalInquiry #aleisterCrowley #AlexanderSaxton #AliMaloney #allBeings #AmandaBlake #amongMany #amusement #AmyBoucher #Anat #ancientGods #ancientIsrael #AngelikaMay #Anglican #anthology #archivalMaterials #artists #Asherah #astarte #astralDeities #AtlanticOcean #AtlantisBookshop #Baal #BarneyMuldoon #bbc #BBCRadio #belief #BernhardBeyer #bestPosts #bestRemembered #bestTen #biblicalMagi #Blondie #BobbyCampbell #BookOfTheLaw #buddhism #CJSubko #California #Canaan #CanaanitePolytheism #CanaaniteReligionAndMythology #CatholicSuperstition #celebrated #charlatan #CharlesMocenigo #ChristianIdiom #ChristianKabbalah #ChristianNonDuality #churchRitual #churches #ChymicalWedding #cleansing #commonMetaphysicalTemplate #comparativeFramework #ConfessioFraternitatis #conspiracies #conspiracy #contemplativePractice #cosmic #counterculturalBookshops #counterculturalIcon #cultOfYahweh #curiosity #dangerousManipulator #DanteBonutto #darkArts #DavidMitchell #deliverance #deliveranceMinistry #demanding #demonology #dismissed #distinctlySeparate #divineFeminine #DivineUnity #DoWhatThouWiltShallBeTheWholeOfTheLaw #Doctrinal #doctrineOfRéintégration #Doinel #drugTaking #dues #DutchSchulz #earlyHistory #EdgarBroughton #EdwardianEccentric #ÉgliseGnostique #El #EleanorGraydon #eliphasLevi #ElizabethRMcClellan #ÉlusCoëns #emanation #encounters #esotericChristianity #esotericCurrent #esotericKnowledge #esotericMysteries #EucharisticVision #evangelicalExcess #evilSpirits #evolved #exile #exorcism #expulsion #FUCKUP_ #faith #FamaFraternitatis #fascination #fear #feast #feminineEros #feminineWisdom #figure #finDeSiècle #fire #FissionChips #flamboyantShowman #FlorenceSusanneReppert #folk #Foreign #France #FrancisYoung #fraudster #freemasonry #FrenchEsotericism #FrenchTradition #fullyDefined #GaryLachman #genius #GeorgeDorn #GeraldineBeskin #GérardEncausse #gnosis #GnosticLiturgy #Gnosticism #god #goddeses #gods #greatGoddesses #greaterFeast #greaterMysteries #HagbardCeline #hardRock #HarryCoin #heavyMetal #HebrewBible #HermeticSymbolism #hermeticism #historicallyGrounded #history #historyOfIdeas #horrors #HowardTheDolphin #IanHGladwin #identity #illuminatedTreeOfLife #Illuminatus #ineffableOne #initiated #initiaticOrders #initiatoryCodification #institutionalDiversity #integralSpirituality #integrate #interiorPath #invoked #JDMYoder #JamesFoster #JannHaworth #JazColemanmKillingJoke #jimmyPage #JohnDay #JohnDillinger #JonathanHart #journals #JulesDoinel #Juniorus #keySource #LauraCathcart #leadingGods #LeeIrwin #lesserMysteries #Levi #LindaBromilow #lineage #lodgeRooms #lodges #Logos #louisClaudeDeSaintMartin #lucidDreamers #lucifer #LydiaWaites #madMan #magickalOrder #Magister #magus #MarkSSmith #MartinèsDePasqually #MaryLouServix #masculinePrinciple #masonic #master #metalMusicians #modernEurope #MoggMorgan #Molech #monotheism #monotheisticFaith #moon #Mot #mountaineer #MrCrowley #Musicians #mysteries #mysteriesOfNature #mysticalInsight #nativeChristianNonDuality #NeoplatonicMetaphysics #neoplatonism #newGeneration #nineGrades #occultChurches #occultReligion #occultist #October2025 #OldTestament #OllyPearson #openInvitation #OrderOfTheGoldenAndRosyCross #otherDeities #outrightRejection #OzzyOsbourne #paganGods #pansentience #Papus #PatrickDMiller #PaulMorley #pedagogiesOfUnity #pervert #Philosophus #pioneeringThinker #plymouthBrethren #poet #popularCulture #Power #practicalWisdom #Practicus #primaryDeity #progressiveEstablishment #prophet #provocation #psychedelia #public #publicForm #RLoftiss #realities #rediscover #Reincarnation #reintegration #religion #religiousHorror #religiousTrauma #remarkableTransformation #remarkablyCoherent #Rephaim #Resheph #return #rigorous #riteOfExorcism #ritual #ritualForms #robertAntonWilson #RobertPearson #RobertShea #rockStars #rosicrucian #RosicrucianManifestos #rosicrucianSociety #rosicrucianism #RyanDay #sacredMarriage #SaintMartin #SaintYvesDAlveydre #SashaRavitch #SaulGoodman #scandal #scandalous #selfMythology #seven #SgtPepper #SimonMoon #soleGod #sophia #spiritualEntities #spiritualOutlook #spiritualSignificance #StephenHoward #summary #summaryOfTheMonth #sun #symbol #symbolicSynthesis #syncreticCuriosity #taoism #thaumaturgicalHeritage #TheAMA #TheBeatles #TheGreatBeast #TheOneirocriticalSociety #theWickedestManInTheWorld #theWorldSOldest #theoreticalFoundations #Theoreticus #theurgy #ToddPurse #topPosts #topTen #underworldDeities #unity #unwaveringDevotion #VanessaSantos #Vedanta #vision #westernEsotericism #wholeness #WieboGrobler #worlds #wreckedLives #yahweh
-
Hello folks! I’m coming to you live from a very wet and windy Ireland. April showers is certainly a thing, but this kind of rain is even giving the typical Irish weather a run for its money! 😀 I hope you all have had a good (and drier) week so far and enjoy your weekend, and if you would like some weekend reading, weekend bug fixing, or even a weekend proposal writing session, read on for the links and information you need to do just that 🙂
Flock to Fedora
The call for papers for our annual contributor conference, Flock to Fedora, is now open until April 21st. Check out the cfp page for details on the tracks and themes of this years conference, plus information on travel subsidies and how to contact event staff if you need help.
Fedora Linux 40
Important Dates
- Currently in Final Freeze
- Thursday, April 11th @ 1700 UTC – Fedora Linux 40 Go/No-Go Meeting
- Tuesday, April 16th – Current Release Target Date (this will depend on the outcome of the Go/No-Go meeting)
Help Wanted
There are a number of blocker bugs open against F40 at the moment, both proposed and accepted. If you could spare some time to visit the blocker bugs app and reproduce some of the bugs to validate if they are blocking bugs or not, and/or even propose a fix for a bug listed, that would be hugely appreciated. A summary of the current F40 bugs can be found on this email with links to each too.
Fedora Linux 41
Change proposals are welcome for F41, and even F42 (and F43 if you’re that prepared!). The first deadline is 19th June if your change requires any infrastructure changes, and 26th June if it is a system-wide change. Self-contained changes may be submitted until 16th July. Those dates might seem far off, but please do have your changes in Rawhide as early as possible as this impacts a lot of the build and release folks (QA, rel-eng, etc) so getting the work proposed, approved and into development as early as possible is strongly recommended. Below is a list of changes proposed, awaiting FESCo decision and already accepted for F41.
Proposed
Awaiting FESCo Decision
- Changes/EnableConsistentDeviceNamingCloud
- Changes/GNUToolchainF41
- Changes/php no 32 bit
- Changes/RPM-4.20
- Changes/SwitchToDnf5
Accepted F41
- Changes/AnacondaWebUIforFedoraWorkstation
- Changes/DefaultBpfman
- Changes/Haskell GHC 9.6 and Stackage 22
- Changes/KDEKinoiteAutoUpdateByDefault
- Changes/KTLSSupportForGnuTLS
- Changes/mkosi-initrd
- Changes/ModernizeLiveMedia
- Changes/OstreeNativeContainerStable
- Changes/Python3.13
- Changes/RemovePythonMockUsage
- Changes/ReplaceDnfWithDnf5
- Changes/RPMCoW
- Changes/SPDX Licenses Phase 4
- Changes/SystemdSecurityHardening
- Changes/Unify bin and sbin
Hot Topics
An update on the Git Forge Evaluation has been published by the Fedora Council. Please have a read on discussion.fpo or on the community blog.
The CommOps Team is rebooting! Read about the newly (re)formed team on their blog post and find out how to get involved and join the team.
Help Wanted
Lots of Test Days! Check them out on the QA calendar in fedocal for component-specific days. Help is always greatly appreciated.We also have some packages needing some new maintainers and others needing reviews. See below links to adopt and review packages!
https://communityblog.fedoraproject.org/fedora-ops-architect-weekly-5/
-
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
-
Hi folks, welcome to the weekly from your Fedora operations architect. This is an exciting week in the project as our Fedora Linux 40 Beta goes live tomorrow! Have a read on for more information.
Fedora Linux 40
Beta is GO!
Tomorrow, March 26th, our Fedora Linux 40 Beta will release, and I cannot thank our wonderful community enough for all the hard work they have been putting in the last few months to create it. When it lands, testing how the release behaves and filing bugs and posting fixes would be hugely appreciated as our Beta is what we will polish and refine for our official final release in a few weeks. You can learn how to and where to file a bug on our docs page.
Reminder: Final Freeze is due to start in one week – 2nd April 2024. Please try to prioritize F40 Beta testing and fixes this week in order to get any fixes submitted and applied before we enter the freeze period. This really helps our QA and release engineering teams on the far side of the freeze build and test our final release candidate compose(s) in good time to find any pesky bugs.
Save the Dates!
Flock to Fedora is returning this year from August 7th – 10th in Rochester, New York, USA and the call for proposals has officially opened! The deadline is April 21st and check out the blog post for more details on tracks, themes and venue details.Open Source Summit Europe has a call for proposals currently open – deadline is April 30th and the conference is set for September 14th – 18th in Vienna, Austria.The deadline for devconf.cz has now closed. Their schedule will be live towards the end of April, and the conference itself will take place from Thursday 13th – Saturday 15th June. The event is free to attend once you register for tickets, so keep an eye on their website for when registration becomes live.
Fedora Linux 41 Release
Fedora Linux 41 Changes
Announced Changes
- Changes/ChangeComposeSettings
- Changes/EnableConsistentDeviceNamingCloud
- Changes/RPM-4.20
- Changes/SwitchToDnf5
- Changes/VersionedKubernetesPackages
Accepted Changes
- Changes/AnacondaWebUIforFedoraWorkstation
- Changes/Haskell GHC 9.6 and Stackage 22
- Changes/KDEKinoiteAutoUpdateByDefault
- Changes/KTLSSupportForGnuTLS
- Changes/mkosi-initrd
- Changes/ModernizeLiveMedia
- Changes/OstreeNativeContainerStable
- Changes/Python3.13
- Changes/RemovePythonMockUsage
- Changes/ReplaceDnfWithDnf5
- Changes/RPMCoW
- Changes/SPDX Licenses Phase 4
- Changes/SystemdSecurityHardening
- Changes/Unify bin and sbin
Help Wanted
Lots of Test Days! Check them out on the QA calendar in fedocal for component-specific days. Help is always greatly appreciated.We also have some packages needing some new maintainers and others needing reviews. See below links to adopt and review packages!
https://communityblog.fedoraproject.org/fedora-ops-architect-weekly-4/
-
Lá Fhéile Pádraig sona duit! I hope you all had a great weekend and if you celebrate with us Irish, you enjoyed some St Patricks Day celebrations ☘️ This weeks report is a little late coming to you, I promise its not because of a pub-related hangover…entirely…but you will now get to enjoy two reports this week instead, so you must have the luck of the Irish 😉 Read on for important information about our release and upcoming events.
Save the Dates!
Flock to Fedora is returning this year from August 7th – 10th in Rochester, New York, USA and the call for proposals has officially opened! The deadline is April 21st and check out the blog post for more details on tracks, themes and venue details.
Open Source Summit Europe has a call for proposals currently open – deadline is April 30th and the conference is set for September 14th – 18th in Vienna, Austria.
The deadline for devconf.cz has now closed. Their schedule will be live towards the end of April, and the conference itself will take place from Thursday 13th – Saturday 15th June. The event is free to attend once you register for tickets, so keep an eye on their website for when registration becomes live.
Fedora Linux 40 Release
Beta Go/No-Go Meeting
The Fedora Linux 40 Beta release is targeting Tuesday 26th March. There is a Go/No-Go meeting scheduled for Thursday 21st March to determine if we have a suitable release candidate or not.
For more information on the Go/No-Go meetings you can visit the wiki page, and for current release targets and other key milestone dates for F40, please refer to the release schedule.
Beta Blockers
There are a few beta blocker bugs active right now. If you can spare some time to try to reproduce the bug to verify it is a bug, and/or even try to find a fix, it would be greatly appreciated. A summary report has gone out to the devel-list this week, and you can also find all blocker bugs, both proposed and accepted, in the blockerbugs app.
Fedora Linux 41 Release
Fedora Linux 41 Changes
Announced Changes
Changes Awaiting FESCo Votes
Help Wanted
Lots of Test Days! Check them out on the QA calendar in fedocal for component-specific days. Help is always greatly appreciated.
We also have some packages needing some new maintainers and others needing reviews. See below links to adopt and review packages!
https://communityblog.fedoraproject.org/fedora-ops-architect-weekly-19th-march/
-
Happy new year everyone! The Fedora Ops Architect weekly has resumed after a little downtime post the holiday period. I hope you all have had a pleasant January and the year is off to a good start. Below are a few items that you might find interesting happening around the project space right now, and I look forward to being able to bring a more diverse spread of information on various activities in Fedora in weeks to come!
Upcoming Travel & Events
Some of you maybe travelling to CentOS Connect (Feb 1st & 2nd) & FOSDEM (Feb 3rd & 4th) this year – lucky you! I will be too and I am looking forward to seeing folks there so come say hi 🙂 However, this comes with the possibility that replies to messages and service requests might be a little slower with people being away from their computer, so please do be patient and as always, for anything in crisis, (ie a service is causing an outage that is infrastructure related), please check the status page, open a ticket in the infra repo and check in on the #fedora matrix channel.
The deadline for devconf.cz call for proposals is also fast approaching, March 3rd 2024, so make sure you get your talks in by this date for consideration!
Fedora Linux 40 Release
Mass Rebuild Finish Delayed
The mass rebuild finish date has been extended by one week to allow for side-tags to be merged and bugs that have emerged during the mass rebuild to be resolved, amongst other tasks, to ensure the build is done well. Right now, the targeted finish date is February 20th. All tasks from the mass rebuild start date up until and including the Beta Freeze have been extended by one week. Please check the release schedule for up to date milestone dates, and report any issues in the schedule repository.
Spins/Labs Keepalive Request
As per a requirement made by FESCo, if you are a maintainer or work in a spin or lab, you must confirm that this is to continue to be built for Fedora Linux 40. A number of tickets have been created in the schedule repo and labeled as spins/keepalive request, please confirm your keepalive request for your respective spin or lab. If you maintain a spin or lab, and did not receive a ticket to confirm, please feel free to create an issue in the repo and tag me for awareness.
Fedora Linux 40 Changes
All deadlines have now passed for changes to be proposed for Fedora Linux 40. If you are an owner of an approved chnage, please be aware that your change must be in a ‘Testable‘ state by 6th Feb 2024. All approved changes to date can be found on the Change Set page. Below are a list of changes that are currently awaiting a decision from FESCo:
- PyTorchRelese
- Replace iotop with iotop-c
- ROCm6Release
- Optimized Binaries for the AMD64 Architecture
- Java21
- ibus-anthy 1.5.16
- IBus 1.5.30
- Fedora IoT Unified Core
- DefaultBpfman
- ArmMinimalImageOSBuild
- Anaconda dir and image installations in automated text mode
- Deprecate ntlm in cyrus sasl
- Fedora IoT Bootable Container
Hot Topics
Join the conversation about planning for src.fedoraproject.org on discourse. I would love to see this topic getting his topic needs more opinions and ideas on how we can move forward with our git forge evaluation efforts this year.
There’s a thread on discourse where Fedorans visiting FOSDEM this year are sharing their plans in order to meet and connect with others attending the event too!
Another thread has been started to talk about creating and introducing a Flock location policy for DEI too, which is such an important conversation to have.
You can also weigh in on the Can We Have a Fedora OEM Installer discussion, and there’s a good conversation happening in the Criteria for making Fedora Atomic the default desktop experience thread too if you want to get involved in that conversation as well.
Help Wanted
That’s all from me this week folks, its good to be back! I look forward to experiencing my first FOSDEM this year next week, and more importantly, meeting more of the fedora community members in person too. Have a great week everyone, and as always – don’t hesitate to reach out 🙂
https://communityblog.fedoraproject.org/fedora-ops-architect-weekly-3/
-
Voting in the Fedora Linux 39 elections is now open. Go to the Elections app to cast your vote. Voting closes at 23:59 UTC on Thursday 21 December, and don’t forget to claim your “I Voted” badge when you cast your ballot. Links to candidate interviews are below.
Fedora Council
There is one seat open on the Fedora Council.
Mindshare Committee
There is one seat open on the Mindshare Committee.
Fedora Engineering Steering Committee (FESCo)
There are five seats open for the Fedora Engineering Steering Committee (FESCo).
https://communityblog.fedoraproject.org/f39-elections-voting-is-now-open/
-
Voting in the Fedora Linux 39 elections is now open. Go to the Elections app to cast your vote. Voting closes at 23:59 UTC on Thursday 21 December, and don’t forget to claim your “I Voted” badge when you cast your ballot. Links to candidate interviews are below.
Fedora Council
There is one seat open on the Fedora Council.
Mindshare Committee
There is one seat open on the Mindshare Committee.
Fedora Engineering Steering Committee (FESCo)
There are five seats open for the Fedora Engineering Steering Committee (FESCo).
https://communityblog.fedoraproject.org/f39-elections-voting-is-now-open/
-
Voting in the Fedora Linux 39 elections is now open. Go to the Elections app to cast your vote. Voting closes at 23:59 UTC on Thursday 21 December, and don’t forget to claim your “I Voted” badge when you cast your ballot. Links to candidate interviews are below.
Fedora Council
There is one seat open on the Fedora Council.
Mindshare Committee
There is one seat open on the Mindshare Committee.
Fedora Engineering Steering Committee (FESCo)
There are five seats open for the Fedora Engineering Steering Committee (FESCo).
https://communityblog.fedoraproject.org/f39-elections-voting-is-now-open/
-
Voting in the Fedora Linux 39 elections is now open. Go to the Elections app to cast your vote. Voting closes at 23:59 UTC on Thursday 21 December, and don’t forget to claim your “I Voted” badge when you cast your ballot. Links to candidate interviews are below.
Fedora Council
There is one seat open on the Fedora Council.
Mindshare Committee
There is one seat open on the Mindshare Committee.
Fedora Engineering Steering Committee (FESCo)
There are five seats open for the Fedora Engineering Steering Committee (FESCo).
https://communityblog.fedoraproject.org/f39-elections-voting-is-now-open/
-
Voting in the Fedora Linux 39 elections is now open. Go to the Elections app to cast your vote. Voting closes at 23:59 UTC on Thursday 21 December, and don’t forget to claim your “I Voted” badge when you cast your ballot. Links to candidate interviews are below.
Fedora Council
There is one seat open on the Fedora Council.
Mindshare Committee
There is one seat open on the Mindshare Committee.
Fedora Engineering Steering Committee (FESCo)
There are five seats open for the Fedora Engineering Steering Committee (FESCo).
https://communityblog.fedoraproject.org/f39-elections-voting-is-now-open/
-
This is a part of the Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Friday, 8 December and closes promptly at 23:59:59 UTC on Thursday, 21 December.
Interview with Kevin Fenzi
- Fedora Account: Kevin
- IRC/Nick: nirik
- Matrix Channels typically found in: #fedora-admin/admin, #fedora-noc/noc, #fedora-releng/releng, #fedora-devel/devel
- Fedora User Wiki Page
Why do you want to be a member of FESCo and how do you expect to help steer the direction of Fedora?
I wish to continue to serve the fedora community on FESCo to provide history and help make today’s decisions based on yesterdays learning.
How do you currently contribute to Fedora? How does that contribution benefit the community?
I currently am lucky to be employed by Red Hat working full time on Fedora Infrastructure. But outside of that ‘day job’ I try and do as many things as I can to help the fedora community: Maintaining packages, providing feedback on plans or ideas, doing release engineering tasks (often in non ‘work’ times).
How do you handle disagreements when working as part of a team?
I try and reach consensus until it becomes clear thats not possible. However, it almost always is possible, you just need to look at things from other perspectives and consider what solution would work for everyone. This is not foolproof, but helps to handle disagreements when they happen.
What else should community members know about you or your positions?
I’m happy to talk to anyone from the community anytime about fedora items. Feel free to contact me on matrix or irc or email. I’m human and make mistakes, but I like to think I learn from them and do better over time. 🙂
elections, Fedora, Fedora Engineering Steering Committee (FESCo)https://communityblog.fedoraproject.org/fesco-election-interview-with-kevin-fenzi-2/
#elections #Fedora #FedoraEngineeringSteeringCommitteeFESCo_
-
This is a part of the Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Friday, 8 December and closes promptly at 23:59:59 UTC on Thursday, 21 December.
Interview with Tomas Hckra
- Fedora Account: Tomas Hckra
- IRC/Nick: jednorozec/humaton
- Matrix Channels typically found in: fedora-releng, #fedora-devel, #fedora-devel, #fedora-noc
- Fedora User Wiki Page
Why do you want to be a member of FESCo and how do you expect to help steer the direction of Fedora?
I believe that my perspective as a fedora release engineer can bring some new opinions into the steering process. My focus is mostly on user/contributor self-service where possible so we can remove obstacles for new people coming into the Fedora project.
How do you currently contribute to Fedora? How does that contribution benefit the community?
Over the last decade, I went through package maintenance and app development. Currently, I am part of the release engineering team, helping out with releases and related infrastructure work. Right now I am working on dropping the Product Definition Center from our workflows so we can reduce the complexity in our package-related processes and tooling.
How do you handle disagreements when working as part of a team?
Most of the team disagreements I was part of were caused by communication issues and misunderstanding of one or the other side. So I strongly believe that most problems are resolvable by listening, considering the other side, and communicating about the disagreement clearly. The next step is building consensus keeping in mind all the viewpoints that caused the conflict in the first place.
What else should community members know about you or your positions?
I am a full-on open-source nerd, everything in my house is running open-source SW. I am not shy of public speaking you can find some of my talks on YouTube like this one about opensource home automation: https://www.youtube.com/watch?v=HUhHaHnzhYA
Two main ideas that define my approach to technology:
“I want all things open and all sources shown”
“Where is a serial console there is a way”https://communityblog.fedoraproject.org/fesco-election-interview-with-tomas-hckra/
#elections #Fedora #FedoraEngineeringSteeringCommitteeFESCo_
-
Today we are starting the nomination & campaign period during which we accept nominations to the “steering bodies” of the following teams:
- FESCo (Engineering) (5 seats)
- Fedora Council (1 seat)
- Mindshare (1 seat)
This period is open until 2023-11-27 at 23:59:59 UTC.
Candidates may self-nominate. If you nominate someone else, please check with them to ensure that they are willing to be nominated before submitting their name.
The steering bodies are currently selecting interview questions for the candidates.
Nominees submit their questionnaire answers via a private Pagure issue. The Election Wrangler or their backup will publish the interviews to the Community Blog before the start of the voting period.
Please note that the interview is mandatory for all nominees. Nominees not having their interview ready by end of the Interview period (2023-05-17) will be disqualified and removed from the election.
As part of the campaign people may also ask questions to specific candidates on the appropriate mailing list.
The full schedule of the elections is available on the Elections schedule. For more information about the elections, process see the Elections docs.
https://communityblog.fedoraproject.org/f39-elections-now-open/
#electionCampaigns #elections #FedoraCouncil #FedoraEngineeringSteeringCommitteeFESCo_ #FedoraMindshareCommittee
-
Today we are starting the nomination & campaign period during which we accept nominations to the “steering bodies” of the following teams:
- FESCo (Engineering) (5 seats)
- Fedora Council (1 seat)
- Mindshare (1 seat)
This period is open until 2023-11-27 at 23:59:59 UTC.
Candidates may self-nominate. If you nominate someone else, please check with them to ensure that they are willing to be nominated before submitting their name.
The steering bodies are currently selecting interview questions for the candidates.
Nominees submit their questionnaire answers via a private Pagure issue. The Election Wrangler or their backup will publish the interviews to the Community Blog before the start of the voting period.
Please note that the interview is mandatory for all nominees. Nominees not having their interview ready by end of the Interview period (2023-11-29) will be disqualified and removed from the election.
As part of the campaign people may also ask questions to specific candidates on the appropriate mailing list.
The full schedule of the elections is available on the Elections schedule. For more information about the elections, process see the Elections docs.
https://communityblog.fedoraproject.org/f39-elections-now-open/
#electionCampaigns #elections #FedoraCouncil #FedoraEngineeringSteeringCommitteeFESCo_ #FedoraMindshareCommittee
-
Today we are starting the nomination & campaign period during which we accept nominations to the “steering bodies” of the following teams:
- FESCo (Engineering) (5 seats)
- Fedora Council (1 seat)
- Mindshare (1 seat)
This period is open until 2023-11-27 at 23:59:59 UTC.
Candidates may self-nominate. If you nominate someone else, please check with them to ensure that they are willing to be nominated before submitting their name.
The steering bodies are currently selecting interview questions for the candidates.
Nominees submit their questionnaire answers via a private Pagure issue. The Election Wrangler or their backup will publish the interviews to the Community Blog before the start of the voting period.
Please note that the interview is mandatory for all nominees. Nominees not having their interview ready by end of the Interview period (2023-11-29) will be disqualified and removed from the election.
As part of the campaign people may also ask questions to specific candidates on the appropriate mailing list.
The full schedule of the elections is available on the Elections schedule. For more information about the elections, process see the Elections docs.
https://communityblog.fedoraproject.org/f39-elections-now-open/
#electionCampaigns #elections #FedoraCouncil #FedoraEngineeringSteeringCommitteeFESCo_ #FedoraMindshareCommittee