For those of us in the ham radio community, staying connected and informed about the latest updates, news, and technologies is crucial. Whether it's updates on frequency changes, new technologies, or news from the wider radio community, having a reliable and efficient way to aggregate and consume content is essential. This is where FreshRSS comes in-a self-hosted RSS feed aggregator that is powerful, customizable, and lightweight. You can easily check out the demo at freshrss.hamradio.my to get a feel for how this platform works and see if it suits your needs.

What is FreshRSS?

FreshRSS is an open-source RSS feed aggregator that allows you to collect and read all your favorite content in one place. Unlike many other RSS platforms, FreshRSS is designed to be easy to set up, use, and customize to meet your specific needs. You can host FreshRSS on your own server, keeping control over your personal data and feeds.

What makes FreshRSS particularly appealing is its light footprint-designed to run on modest server hardware-and its extensive customizability, making it a fantastic tool for both hobbyists and professionals. Whether you're following ham radio blogs, technical discussions, or personal news feeds, FreshRSS consolidates all your content into a single, organized interface.

Key Features of FreshRSS

1. Multi-User Support and Anonymous Reading Mode

FreshRSS isn't just for solo users; it's built to handle multiple accounts. Whether you're a team of developers, ham radio enthusiasts, or just want to share access with friends or colleagues, FreshRSS makes it easy to manage multiple user profiles. Additionally, it includes an anonymous reading mode, allowing users to browse content without signing in. This is particularly useful for those who prefer a more private or casual browsing experience.

2. Real-Time Updates with WebSub

One of FreshRSS's standout features is its support for the WebSub standard, which allows for real-time push notifications from compatible sources. Unlike traditional RSS, where you need to manually refresh or rely on polling intervals, WebSub enables instant updates as soon as new content is published on supported sites. This is particularly useful for staying updated with real-time information such as live ham radio broadcasts, news, or blog posts.

With WebSub, services like WordPress, Blogger, Medium, Friendica, and other compatible platforms can push updates to your FreshRSS feed instantly, saving you time and ensuring you're always in the loop.

3. Mobile-Friendly with Native App Support

FreshRSS supports integration with mobile clients via two distinct APIs-Google Reader API and Fever API. These APIs ensure that you can use a wide range of mobile RSS apps like Readrops, Capy Reader, FeedMe, and FocusReader on Android or Fluent Reader, RSS Guard, and Newsboat on Linux and Windows.

These apps are capable of syncing quickly, fetching content even while offline, and managing your feeds in an intuitive, user-friendly way. For example, the Readrops Android app allows you to access FreshRSS with offline functionality and fast syncing, ensuring you have access to all your feeds regardless of connectivity.

4. Customizable Tagging and Web Scraping

FreshRSS allows you to create custom tags to better organize your feeds, whether you want to group them by topic, priority, or type of content. For instance, you can tag all your ham radio-related feeds with a specific label, making it easy to filter and find the content you're most interested in.

Additionally, FreshRSS supports Web scraping via XPath, allowing you to scrape websites that don't offer an RSS or Atom feed. You can also scrape JSON documents, further enhancing the flexibility of your feed aggregation. This is especially useful for sites that may have niche content but don't provide a standard feed format. It means you can pull in content from any site, regardless of whether it offers RSS or not.

5. Feed Sharing and Export

FreshRSS isn't just about reading your own feeds. It also allows you to reshare selections of articles via HTML, RSS, and OPML. This is particularly useful for ham radio groups or communities where you may want to share your curated list of articles, news, or resources with others. Whether it's a blog post or a technical document, you can easily export or share it with others in a variety of formats.

Additionally, FreshRSS supports integration with external apps, providing a seamless experience across different platforms and use cases.

6. Advanced Configuration and Extensions

For those who want to fine-tune FreshRSS to meet their specific needs, the platform supports a variety of advanced configuration settings. These are located in the config.default.php file, which can be modified in data/config.php for customized behavior.

For users who want even more functionality, FreshRSS supports a wide range of extensions. These extensions allow you to add custom features, tweak the interface, or improve the integration with other tools. The repository dedicated to FreshRSS extensions provides numerous ways to further enhance the platform. From advanced filters to custom display themes, the possibilities are vast.

Why Choose FreshRSS on freshrss.hamradio.my?

By using freshrss.hamradio.my, you're accessing a tailored experience for ham radio enthusiasts and hobbyists. The platform allows you to consolidate all your feeds, whether they're related to amateur radio, tech blogs, or anything else you find interesting, into one organized interface. The security and customization that FreshRSS offers ensure that you have control over your data, all while providing a simple and intuitive user interface.

Additionally, with the inclusion of WebSub, mobile client compatibility, and web scraping features, you can stay updated instantly without worrying about manually refreshing or missing out on content.

How to Get Started with FreshRSS

To explore the demo, visit freshrss.hamradio.my. Here, you can try out the platform's features, check how it works in a live environment, and decide whether FreshRSS fits your needs.

Once you're ready to install FreshRSS on your own server, you can follow the instructions provided on the official FreshRSS GitHub repository. The GitHub page offers detailed installation instructions for manual installs, as well as automated deployment options using Docker, YunoHost, Cloudron, and other methods.

Contributing to FreshRSS

As an open-source project, FreshRSS thrives on contributions from the community. Whether you're reporting bugs, suggesting new features, or developing new extensions, FreshRSS offers various ways for users to get involved. You can open issues, submit pull requests, or even develop new features to help improve the platform.

Visit the GitHub repository to learn more about contributing and to check out the documentation for setting up and maintaining FreshRSS.

Conclusion

FreshRSS is an excellent solution for anyone looking to aggregate and manage their RSS feeds in a clean, organized, and customizable way. By using freshrss.hamradio.my, you can experience the power and flexibility of FreshRSS while staying connected to the ham radio community and other interests. Whether you're following live updates, scraping custom web content, or managing your feeds on the go, FreshRSS offers a full-featured, self-hosted solution that is perfect for power users and beginners alike.

Start your journey today with FreshRSS!

The post Explore FreshRSS on freshrss.hamradio.my: A Powerful Self-Hosted RSS Aggregator for Ham Radio Enthusiasts appeared first on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

11 Mar 2025 5:53pm GMT

In the world of music players, finding a feature-rich, high-performance application that respects user privacy can be a challenge. Many modern music players are either bloated with unnecessary features, locked behind paywalls, or designed with intrusive data collection practices. But what if there was a player that offered the best of all worlds-high-quality playback, extensive format support, powerful music library management, and complete privacy? Enter Strawberry Music Player-a robust, open-source audio player that is tailored for audiophiles and music lovers alike.

What is Strawberry Music Player?

Strawberry is an advanced music player and music collection organizer built on Qt. It's a continuation of the Clementine Music Player, developed to provide a modern, feature-packed alternative while staying true to its open-source roots. Designed with audiophiles in mind, Strawberry brings an intuitive interface, lossless audio support, and seamless music management.

Whether you're a casual listener or someone who meticulously curates a massive library of high-fidelity audio, Strawberry provides an exceptional listening experience without unnecessary distractions.

Why Choose Strawberry Over Other Music Players?

Strawberry is not just another music player; it is a carefully designed piece of software that provides everything you need in a sleek and efficient package. Here are some reasons why it stands out:

1. Comprehensive Audio Format Support

Unlike many commercial music players that require additional plugins or paid upgrades, Strawberry supports a vast range of audio formats right out of the box. This includes:

• MP3
• FLAC (Free Lossless Audio Codec)
• WAV
• APE (Monkey's Audio)
• M4A (AAC/ALAC)
• Opus, WavPack, and more

This ensures that whether you're playing standard compressed files or high-resolution lossless tracks, Strawberry delivers pristine audio quality without compromises.

2. Audiophile-Grade Sound with Advanced Playback Features

Strawberry is engineered to provide high-quality audio playback, supporting a range of advanced features such as:

• ReplayGain: Normalize volume levels across tracks.
• Equalizer & DSP Effects: Fine-tune your music to match your preferences.
• Gapless Playback: Enjoy uninterrupted playback between songs.
• Crossfade Support: Smooth transitions between tracks.
• Streaming Support: Play online radio and integrate with services like Tidal.

3. Powerful Music Library Management

Strawberry goes beyond simple music playback by offering a comprehensive music library management system. Features include:

• Tag Editing: Easily edit metadata and organize your collection.
• Album Art Downloader: Fetch high-quality artwork automatically.
• Smart & Dynamic Playlists: Create playlists that update dynamically based on your listening habits.
• Fast Library Scanning: Quickly import and manage large music collections.

4. Seamless Device Integration

Strawberry allows you to transfer and sync music between different devices effortlessly. It supports:

• USB Storage & External Devices
• Android Device Synchronization
• MTP & iPod Support
• Last.fm & Libre.fm Integration for scrobbling and tracking your listening habits.

5. Built for Privacy-Conscious Users

One of Strawberry's core principles is privacy. Unlike many commercial music players, Strawberry does not collect or share user data. There are no telemetry trackers, no analytics reporting, and no invasive advertisements. Your music library remains entirely private, ensuring a safe and secure listening experience.

6. Cross-Platform Availability

Strawberry is available for multiple operating systems, making it a great choice regardless of the platform you use. You can install Strawberry on:

• Linux (Debian, Ubuntu, Fedora, Arch, etc.)
• Windows (7, 8, 10, 11)
• macOS

How to Install Strawberry Music Player

Getting started with Strawberry is quick and easy. Follow the steps below to install it on your preferred operating system:

For Linux Users:

Most Linux distributions have Strawberry available in their official repositories. You can install it using:

• Debian/Ubuntu: sudo apt install strawberry
• Fedora: sudo dnf install strawberry
• Arch Linux: sudo pacman -S strawberry

For Windows Users:

1. Download the latest version from the official Strawberry website.
2. Run the installer and follow the on-screen instructions.
3. Launch Strawberry and start enjoying your music collection.

For macOS Users:

1. Download the latest macOS package from the official site.
2. Install the application by dragging it into the Applications folder.
3. Open Strawberry and set up your music library.

Final Thoughts: The Music Player You've Been Looking For

Strawberry Music Player is a breath of fresh air in the world of digital music. It is lightweight, powerful, privacy-focused, and completely free. Whether you're an audiophile looking for the best lossless playback or a casual listener who just wants a clean and efficient music player, Strawberry delivers in every way.

Its commitment to open-source principles ensures that the software remains user-driven, free of bloatware, and continuously improved by a passionate community of developers. With extensive format support, advanced music library management, and a smooth, polished interface, Strawberry Music Player is the ultimate solution for music lovers who demand the best.

So why settle for less? Download Strawberry Music Player today and elevate your music experience to new heights!

Visit https://www.strawberrymusicplayer.org/

If you've already tried Strawberry, let us know in the comments what you think about it!

The post Experience the Ultimate Audio Player: Strawberry Music Player appeared first on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

10 Mar 2025 6:42pm GMT

10 Mar 2025 3:48pm GMT

10 Mar 2025 3:48pm GMT

Photo by William White on Unsplash.

Please join us at the next regular Open NeuroFedora team meeting on Monday 10 March 2025 at 1300 UTC. The meeting is a public meeting, and open for everyone to attend. You can join us in the Fedora meeting channel on chat.fedoraproject.org (our Matrix instance). Note that you can also access this channel from other Matrix home severs, so you do not have to create a Fedora account just to attend the meeting.

You can use this link to convert the meeting time to your local time. Or, you can also use this command in the terminal:

$ date -d 'Monday, March 10, 2025 13:00 UTC'

The meeting will be chaired by @ankursinha. The agenda for the meeting is:

• New introductions and roll call.
• Tasks from last meeting.
• Open Pagure tickets.
• Package health check.
• Open package reviews check.
• CompNeuro lab compose status check for Fedora 41/rawhide.
• Neuroscience query of the week
• Next meeting day, and chair.
• Open floor.

We hope to see you there!

10 Mar 2025 9:24am GMT

The Fedora Community Operations (CommOps) Initiative, formally titled "Community Ops 2024 Reboot," ran from late 2023 to December 2024, aiming to bolster community support within the Fedora Project. This initiative demonstrated a strong interest within the Fedora contributor community to engage not only in operational tasks but also in exploring Fedora's data and understanding community trends. While the "Community Ops 2024 Reboot" didn't generate a massive amount of immediate change, it successfully re-established community operations as a key area of focus within the Fedora Project. This post summarizes the key achievements and areas for growth.

Leveraging Fedora Infrastructure: Paving the Way for Data Exploration

The "Community Ops 2024 Reboot" initiative effectively utilized Fedora Infrastructure, gaining access to crucial resources like the PostgreSQL database for Datanommer and deploying a Business Intelligence (BI) platform on AWS Cloud. Critically, the initiative also focused on refining the process for community members to work with public Fedora data. Currently, this process is often opaque, difficult, and time-consuming. While the modernization work is ongoing, the initiative laid the groundwork for creating common, accessible pathways that any contributor can follow in the future. This effort aims to democratize access to Fedora data, fostering more data experiments and deeper insights into our contributor community.

Process Improvement: A Mixed Bag

Process improvement efforts under the "Community Ops 2024 Reboot" saw both successes and challenges. A new Standard Operating Procedure (SOP) for virtual Fedora events was developed, aiming to streamline event organization. However, implementation revealed unforeseen complexities, including significant manual effort and reliance on the Fedora Community Architect. This was reflected in the contrasting outcomes of the Fedora Linux Release Parties for versions 40 and 41. While the former was successfully executed, the latter faced last-minute challenges that impacted smooth execution. Although documentation for the Join SIG process and contributor recognition efforts through Community Blog series and Fedora Badges were planned, they were not completed within the initiative's timeframe. This was not due to a lack of importance, but rather because the team prioritized establishing an onboarding pipeline for CommOps members and defining the team's scope and purpose, given the available community contributors.

Community Social Analysis: Laying the Foundation

Despite limited resources, the "Community Ops 2024 Reboot" team made progress in Community Social Analysis. Initial governance needs were defined, and key metrics were documented to facilitate discussions and establish common terminology. This work lays the groundwork for standardized data governance within Fedora. A Pandas-based analysis solution for the Fedora Message Bus was deployed, providing some initial insights. However, this solution lacked repeatability and equitable access, highlighting the need for more robust and scalable data tools in the future.

Key Outcomes and Deliverables

The "Community Ops 2024 Reboot" initiative achieved several significant milestones, while also identifying areas for future development:

Process Improvement

• Developed and partially implemented a new SOP for virtual Fedora events.
• Improved documentation for newcomer onboarding and updated CommOps processes in repositories.
• Successfully executed the Fedora Linux 40 Release Party; experienced challenges with the Fedora Linux 41 Release Party.

Community Social Analysis

• Defined initial governance needs and documented basic metrics.
• Deployed a Pandas-based analysis solution for Message Bus data.
• Created a preliminary data dictionary and established a foundation for future data infrastructure.

Engagement and Recognition

• Fostered community engagement by creating dedicated spaces and facilitating regular meetings.

Reporting and Communication

• Provided periodic updates to the Fedora Council (though less frequently than initially planned).
• Prepared a final initiative report outlining successes, challenges, and recommendations.

Looking Ahead

The "Community Ops 2024 Reboot" initiative has provided valuable insights into how to better support the Fedora community.

The work done on process improvement, while facing some obstacles, has led to more defined release party structures, including issue templates and some established processes. However, it's clear that reducing reliance on key individuals is crucial for scalability.

In Community Social Analysis, the initiative identified critical data points for measuring user engagement by topic, aligning with the Fedora 2028 Strategy's goal of doubling contributors. The team also successfully launched community engagement efforts by creating dedicated spaces and facilitating regular meetings. The critical groundwork laid for easier access to Fedora data will empower more community members to explore and understand our project.

The next steps involve building on these achievements, addressing the identified challenges, and continuing to empower the Fedora community. Thank you to all the CommOps members for their contributions to this important initiative!

10 Mar 2025 8:00am GMT

10 Mar 2025 12:00am GMT

As amateur radio enthusiasts, we're always on the lookout for software that can enhance our operating experience. Today, I want to introduce you to QLog, a powerful open-source logging application that's been gaining popularity in the ham radio community.

What is QLog?

QLog is a feature-rich amateur radio logging application available for Linux and Windows platforms (with experimental MacOS support for developers). Built on the Qt framework with an SQLite database backend, QLog strikes an impressive balance between simplicity and functionality.

The philosophy behind QLog is straightforward: be as simple as possible while providing all the essential features operators need. While it's not primarily focused on contests, it does offer basic contest support among its many capabilities.

Key Features That Stand Out

QLog comes packed with features that make it a compelling choice for radio operators:

Station Integration

• Rig Control: Supports multiple interfaces including Hamlib, Omnirig v1 & v2 (Windows only), and TCI
• Rotator Control: Works with Hamlib and PSTRotator
• CW Keyer Support: Compatible with CWDaemon, FLDigi (all modes), Morse Over CAT, and WinKey V2 hardware

Online Services

• Callbook Integration: Connects with HamQTH and QRZ.com
• DX Cluster Integration: Stay updated on DX stations
• QSL Services: Integrates with LoTW, eQSL (including QSL pictures download), QRZ.com, Clublog, HRDLog.net, and ON4KST Chat
• Secure Password Storage: For all services with password or security token protection

Operating Features

• Customizable GUI: Adapt the interface to your preferences
• Online and Offline Maps: Visualize your contacts
• Club Member Lookup: Quickly identify fellow club members
• Bandmap and CW Console: Enhanced operating tools
• WSJT-X Integration: Seamless operation with digital modes
• Station Location Profiles: Support for multiple operating locations
• Various Statistics: Track your operating achievements
• Basic Awards Support: Keep tabs on your award progress

One of the most refreshing aspects of QLog is its commitment to user privacy and freedom. There are NO ads, NO user tracking, and NO hidden telemetry-it's simply free and open-source.

Platform Support

QLog runs well on:

• Linux (with packages available for Ubuntu, Fedora, and as a Flatpak)
• Windows 10 (64-bit)
• MacOS (experimental support for developers)

The application supports a wide range of radio equipment through its compatibility with Hamlib, Omnirig, and TCI interfaces, making it versatile enough for most ham shacks.

Getting Started with QLog

For Linux Users

Ubuntu users can install QLog through the dedicated PPA:

sudo add-apt-repository ppa:foldyna/qlog
sudo apt update
sudo apt install qlog

Fedora users can download RPM packages from GitHub Releases, and a Flatpak package (which includes built-in TrustedQSL) is available via Flathub.

For Windows Users

Windows users need to install:

• Trusted QSL (optional)
• Omnirig v1 (optional)
• Omnirig v2 (optional)

The installation package is available through GitHub Releases.

My Experience with QLog

What I particularly appreciate about QLog is its clean, uncluttered interface combined with powerful features. The SQLite backend ensures your logging data is stored efficiently and can be backed up easily.

The integration with online services like LoTW and eQSL has streamlined my QSLing process, while the rig control features mean I spend less time manually entering frequency and mode information.

Final Thoughts

Whether you're new to amateur radio logging or looking to switch from another application, QLog deserves your consideration. Its combination of simplicity, features, and open-source philosophy makes it a valuable tool for any ham radio operator.

QLog is actively maintained, with regular updates and a responsive community. If you encounter issues or have suggestions, you can report them through QLog Issues or join the QLog mailing list.

Give QLog a try-I think you'll be impressed by what this free, open-source logging application has to offer to the amateur radio community.

Visit https://github.com/foldynl/QLog

QLog is licensed under the GNU General Public License v3.0. The project was started by Thomas Gatzweiler in 2020 and is currently maintained by Ladislav Foldyna (2021-2025).

The post QLog: A Comprehensive Amateur Radio Logging Application for the Modern Ham appeared first on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

08 Mar 2025 8:00pm GMT

Here we are saturday morning again. This week was shorter than normal for me work wise, as I took thursday and friday off, but there was still a lot going on.

08 Mar 2025 5:33pm GMT

07 Mar 2025 3:10pm GMT

This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.

Week: 3rd Mar - 7th Mar 2025

Infrastructure & Release Engineering

The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It's responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues

Fedora Infra

• In progress:
  • re-add datagrepper nagios checks (and add to zabbix?)
  • Fix logrotate on kojipkgs01/02
  • 2025 datacenter move (IAD2->RDU3)
  • [CommOps] Open Data Hub on Communishift
  • retire easyfix
  • Add StartInstanceRefresh permission for fedora-ci-testing-farm user in AWS
  • Deploy Element Server Suite operator in staging
  • Pagure returns error 500 trying to open a PR on https://src.fedoraproject.org/rpms/python-setuptools-gettext
  • a real domain name for konflux
  • Create a POC integration in Konflux for fedora-infra/webhook-to-fedora-messaging
  • maubot-meetings bot multi line paste is cut
  • setup ipa02.stg and ipa03.stg again as replicas
  • Manage our new testing.farm domain via AWS Route53
  • Add support for creating RDS instances under `testing-farm-` prefix
  • Move OpenShift apps from deploymentconfig to deployment
  • The process to update the OpenH264 repos is broken
  • httpd 2.4.61 causing issue in fedora infrastructure
  • Support allocation dedicated hosts for Testing Farm
  • EPEL minor version archive repos in MirrorManager
  • vmhost-x86-copr01.rdu-cc.fedoraproject.org DOWN
  • Add yselkowitz to list to notify when ELN builds fail
  • Cleaning script for communishift
  • Setup RISC-V builder(s) VM in Fedora Infrastructure
  • Move from iptables to firewalld
  • Help me move my discourse bots to production?
  • rhel9 adoption
  • Replace Nagios with Zabbix in Fedora Infrastructure
  • Migration of registry.fedoraproject.org to quay.io
• Done:
  • Automatically invited ChanServ channel is unjoinable.
  • "Fatal Error" when uploading image.
  • FAS account: Accept the user agreement with registration
  • [koji, s390x] GenericError: Downloaded file … doesn't match expected size (… vs …)
  • s390x Koji builders: Librepo error: Cannot download toplink/packages/librsvg2/2.59.2/1.fc41/s390x/librsvg2-2.59.2-1.fc41.s390x.rpm: All mirrors were tried
  • ca.mirrors.cicku.me seems to be outdated, should be taken out of the mirror list
  • Request for Asahi calendar owned by asahi-sig
  • Redeploy WCIDFF to production after the changes in source
  • Please provide commit acces for nikromen to fedora-infra/ansible
  • Create a token for anaconda team for the purpose of automated test result reporting to Wiki
  • RISC-V Koji Administration
  • Create CentOS calendar

CentOS Infra including CentOS CI

• In progress:
  • Increase Storage capacity for koji built artifacts
  • Testing Jenkins - c10s x86_64 metal doesn't provision
  • Release Improvements
  • [spike] : investigating needed deps (poetry) for duffy on el9
  • Onboarding new infra SIG member
  • Migrate main backup storage pool to different hardware
  • [spike] : investigating options/alternatives for the upcoming DC move
• Done:
  • grant sf-service-account namespace-scoped access to monitoring.coreos.com API on cloud-softwarefactory
  • Adding Theory7.net Centos-stream mirror
  • http 503 when accessing https://cloud.centos.org/centos/9-stream/x86_64/images
  • Scope operator installations in cloud-softwarefactory namespace
  • Move cloud.centos.org to its new CDN setup
  • Redesign mirror network due to Equinix stopping OSS sponsorship
  • New NL/Amsterdam Mirror - low latency!

Release Engineering

• In progress:
  • Stalled epel package request: python-hamcrest
  • Please send openh264-2.6.0 to Cisco
  • Unretire datanommer-commands and python-datanommer-models packages
  • Create `image-builder-build` koji build group
  • Please untag tinysparql-3.8~rc-3.fc42
  • 300+ F42FTBFS bugzillas block the F41FTBFS tracker
  • Packages that have not been rebuilt in a while or ever
  • Fedora 42 Mass Rebuild Tracker
  • Send compose reports to a to-be-created separate ML
  • .sqlite metadata missing in f41-updates and f41-updates-testing repositories
  • Could we have fedoraproject-updates-archive.fedoraproject.org for Rawhide?
  • Investigate and untag packages that failed gating but were merged in via mass rebuild
  • a few mass rebuild bumps failed to git push - script should retry or error
  • Package retirements are broken in rawhide
  • Implement checks on package retirements
  • Untag containers-common-0.57.1-6.fc40
  • orphan-all-packages.py should remove bugzilla_contact entries from fedora-scm-requests as well
  • Packages that fail to build SRPM are not reported during the mass rebuild bugzillas
  • When orphaning packages, keep the original owner as co-maintainer
  • Create an ansible playbook to do the mass-branching
  • RFE: Integration of Anitya to Packager Workflow
  • Fix tokens for ftbfs_weekly_reminder. script
  • Update bootloader components assignee to "Bootloader Engineering Team"for Improved collaboration
• Done:
  • Stalled EPEL package: xclip
  • New repo stuck in inconsistent state: rpms/rust-tree-sitter-julia
  • kiwi-10.2.11-1.fc43 isn't used in Rawhide/f43 image builds
  • Allow macro _with_bootstrap for f43 sidetags
  • Deletion of accidently created branch
  • Stalled EPEL package: python-qt5
  • Stalled EPEL package: python-msgpack
  • Migrate to lastlog2
  • Branch cleanup: please remove the 'rawhi' branch of rust-tree-sitter-bash
  • F42 stable push requests
  • Please update openh264 to 2.6.0 in rawhide and F42
  • Please update `openh264`to 2.5.0 in F41
  • please create epel10 based el10-openjdk tag
  • Please send openh264-2.4.1-1.el10_0 to Cisco
  • RFE: data store and/or messages and/or server for release cycle information

If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.

The post Infra and RelEng Update - Week 10 appeared first on Fedora Community Blog.

07 Mar 2025 10:00am GMT

Introduction

Ready to run your own Wikipedia-style knowledge repository on Fedora, Centos or RHEL?

Hold on tight! We are about to walk you through the steps for installing MediaWiki on the most innovative Linux distro out there.

Whether you are a Linux geek or a Linux noob looking to get started with MediaWiki, this step-by-step guide will take you from start to finish, pronto!

MediaWiki ?

MediaWiki facilitates collaboration and documentation in many reputable organizations around the world. Some worthy of mention are:

• Moodle
• Blender,
• BogleHeads
• National Gallery of Arts
• OpenStreetMaps
• OpenOffice
• University of Buffalo
• The Nielsen Company.

MediaWiki is used in place of Microsoft's SharePoint, as well. It is preferred for its less complicated RBAC (Role-Based Access Control) system, and $0.00 licensing cost. Sharepoint licensing costs between $25,000 - $150,000 .

Prerequisites

• Fedora, Centos or RHEL server. This guide uses Centos Stream 10. Fedora, Centos, and RHEL servers are interchangeable.
• A user account with sudo privileges on the server.
• Command line competency.
• Docker experience is useful but not required.

Step 1: Update the server.

$ sudo dnf update; sudo dnf upgrade -y

Step 2: Install Podman

$ sudo dnf install podman

This tutorial uses podman > 5.3. Ensure a compatible version is installed with

$ podman -v
podman version 5.4

Step 3: Pull MediaWiki container from Docker hub.

$ podman pull docker.io/mediawiki:lts
Trying to pull docker.io/library/mediawiki:latest...
Getting image source signatures
Copying blob 46506c43b76b done   |  
Copying blob 7cf63256a31a done   |  
Copying blob f7e553522295 done   |  
Copying blob ccca7c183c0b done   |  
Copying blob 41bfba87aa2a done   |  
Copying blob 904933496485 done   |  
Copying blob 7906c5c5b56e done   |  
Copying blob 5f93253b2de6 done   |  
Copying blob 0230624a769b done   |  
Copying blob 6beeb76481f6 done   |  
Copying blob 012fd53ee67a done   |  
Copying blob a3339e6f62b1 done   |  
Copying blob b1eb0357bfab done   |  
Copying blob 4f4fb700ef54 done   |  
Copying blob 675bda9db3e3 done   |  
Copying blob c0a6d25b98b0 done   |  
Copying blob 417fd4c91734 done   |  
Copying blob 3c7453788306 done   |  
Copying blob ce01c7644913 done   |  
Copying blob ebe12d15cfb9 done   |  
Copying blob 35fe3b70b606 done   |  
Copying config 346df66094 done   |  
Writing manifest to image destination
346df660949efc448741705767a5db05a290e9d870c354ae93edc0e0291f7f03

Step 4: Pull Mariadb container from Docker hub.

$ podman pull docker.io/mariadb:lts
Trying to pull docker.io/library/mariadb:latest...
Getting image source signatures
Copying blob 597f7afe50fe done   |  
Copying blob 5a7813e071bf done   |  
Copying blob 5db80086e4da done   |  
Copying blob 901fe9394c00 done   |  
Copying blob 43eb19e1b102 done   |  
Copying blob bdecd990c29c done   |  
Copying blob e1dede558384 done   |  
Copying blob 5c3a22df929b done   |  
Copying config a914eff5d2 done   |  
Writing manifest to image destination
a914eff5d2eb4c650a4e787e453d52a4ffba977632bd624cc6e63d0c9c4c2d65

Step 5: Run Mariadb and Mediawiki containers in a pod.

5.1. Create a pod

A pod is a group of containers which share the same network, and/or resources.

Create a pod named wikipod:

$  podman pod create -n wikipod -p 8080:80

5.2. Run mariadb in wikipod

$  podman run --detach --name mariadb --env MARIADB_ROOT_PASSWORD=mediawiki --pod wikipod mariadb:lts

5.3. Run mediawiki in wikipod

$  podman run --detach --name mediawiki --pod wikipod mediawiki:lts

5.4 Check mariadb, mediawiki containers are running.

$  podman ps
CONTAINER ID  IMAGE                                    COMMAND               CREATED         STATUS         PORTS                           NAMES
936f315a87be  localhost/podman-pause:5.4.0-1739318400                        52 seconds ago  Up 31 seconds  0.0.0.0:8080->80/tcp            752fc149d017-infra
2a4ada8a898d  docker.io/library/mediawiki:lts          apache2-foregroun...  30 seconds ago  Up 31 seconds  0.0.0.0:8080->80/tcp            mediawiki
7d1c7a41ea83  docker.io/library/mariadb:lts            mariadbd              14 seconds ago  Up 15 seconds  0.0.0.0:8080->80/tcp, 3306/tcp  mariadb

Voila! Mariadb and mediawiki containers are up and running.

Step 6: Complete Mediawiki installation.

6.1 Go to http://<Your-Server-IP>:8080.

Server IP for this installation is 127.0.0.1.

Click complete the installation, and follow the prompt to configure mariadb.

6.2 Follow the prompt to configure the database.

6.3. Fill in database credentials.

The credentials used for this demonstration installation are as follows (adjust this to suit your needs):

6.4 Database setup complete.

Once database setup is complete, click continue to complete mediawiki installation

6.5 Mediawiki setup complete.

At this point we have accomplished the following:

1. Mariadb, successful configuration for mediawiki
2. Mediawiki, successful installation.

Now the LocalSettings.php file must be copied to the directory where mediawiki is installed.

7. Copy LocalSettings.php to mediawiki installation directory.

7.1. Get mediawiki container id.

The mediawiki container id for this installation is 2a4ada8a898d. For your reference, go to section 5.4, above.

7.2 Copy LocalSettings.php into mediawiki container using podman.

$  podman cp ~/Downloads/LocalSettings.php 2a4ada8a898d:/var/www/html

8. Log in to mediawiki.

07 Mar 2025 8:00am GMT

07 Mar 2025 12:00am GMT

Hello readers of community blog!

Recently on community blog round table meeting we had an interesting conversation about the future of community blog and we would like to hear your feedback on that discussion.

What is this change about? We would like to move from your wordpress instance to discussions.fedoraproject.org as new category with new team of curators. Why this change you ask? Here is the list of improvements that this would bring us:

• Simpler editor workflow - this could potentially help us to get more editors for community blog and the actual reviews should be faster
• One place to read the blog posts - we are currently forwarding all the blog posts to discussions anyway and this is also used to enable comments for blog posts
• One less service to maintain - we are already maintaining and using discussions as Fedora and maintaining wordpress instance on top of that for community blog is more work that is not adding much

Here is the space for your feedback. Do you think this is a good idea? What would you miss on discussions.fedoraproject.org compared to wordpress instance. Please let us know in comments.

If you want to be a potential curator for new community blog let us know in the comments as well.

The post Proposal to move Community Blog to Fedora Discussion appeared first on Fedora Community Blog.

06 Mar 2025 10:00am GMT

06 Mar 2025 7:48am GMT

05 Mar 2025 3:42pm GMT