/rss20.xml">

Fedora People

Announcing Webhook To Fedora Messaging

Posted by Fedora Community Blog on 2024-10-22 08:00:00 UTC

With the transition of the applications from Fedmsg to Fedora Messaging inching towards completion, today we want to introduce a new service, Webhook To Fedora Messaging. Webhook To Fedora Messaging has been researched and developed by the Fedora Infrastructure team members with the company of an Outreachy mentee over the last quarter to communicate with services using webhooks.

Webhook To Fedora Messaging takes webhook events from services and translates them into semantic messages to be sent over on the Fedora Messaging bus, to which every Fedora Project application can listen and act for automation. Currently, the project supports services like GitHub but going forward we plan on implementing support for services like Discourse, GitLab, Forgejo etc.

As this service was designed to be the successor to the existing Github2Fedmsg service, we are also announcing that the service is now deprecated and users are encouraged to migrate to the newer service. If you are an existing user of the Github2Fedmsg service, please open a private ticket in the fedora-infra/w2fm-registration repository using the template named “Github2Fedmsg Migration Request”.

Additionally, as GitHub allows for managing webhooks at an organizational level, users migrating from the GitHub2Fedmsg service can explore the functionality by visiting the page https://github.com/organizations//settings/hooks. Once the changes have been made by the owner of the GitHub organization, the activities from all repositories can be conveniently relayed on the Fedora Messaging bus.

The post Announcing Webhook To Fedora Messaging appeared first on Fedora Community Blog.

4 cool new projects to try in Copr for October 2024

Posted by Fedora Magazine on 2024-10-21 17:07:06 UTC

Copr is a build-system for anyone in the Fedora community. It hosts thousands of projects for various purposes and audiences. Some of them should never be installed by anyone, some are already being transitioned to the official Fedora Linux repositories, and the rest are somewhere in between. Copr gives you the opportunity to install 3rd party software that is not available in Fedora Linux repositories, try nightly versions of your dependencies, use patched builds of your favourite tools to support some non-standard use-cases, and just experiment freely.

This article takes a closer look at interesting projects that recently landed in Copr.

If you don’t know how to enable a repository or if you are concerned about whether is it safe to use Copr, please consult the project documentation.

Hyprland

Hyprland is a beautiful Wayland compositor for Linux, offering advanced window management, eye-candy animations, and high customizability. It gives users fine control over their desktop environment, making it perfect for those who value both aesthetics and functionality.

Installation instructions

The repo currently provides Hyprland and many more packages needed for your setup like ags or swww for Fedora 39, 40, 41, and Fedora Rawhide. To install it, use these commands:

sudo dnf copr enable solopasha/hyprland
sudo dnf install hyprland

hblock

Improve your security and privacy by blocking ads, tracking, and malware domains with hBlock. This POSIX-compliant shell script compiles lists of such domains from multiple sources and creates a hosts file to block connections to them. You just need to use the following command:

hblock

This will generate an /etc/hosts file with the blocked domains. Keep in mind that hBlock replaces your system’s existing hosts file by default, so it’s a good idea to back it up before running the script.

Installation instructions

The repo currently provides hblock for Fedora 39, 40, 41, and Fedora Rawhide. To install it, use these commands:

sudo dnf copr enable pesader/hblock
sudo dnf install hblock

Ungoogled Chromium

Ungoogled Chromium is a privacy-enhanced version of the Chromium browser, designed to remove all Google services dependencies and tracking. It offers the same speed and functionality as regular Chromium but without the built-in connections to Google. This makes it ideal for users who want more control over their data and a more private browsing experience, while still enjoying the benefits of an open-source, lightweight browser.

Installation instructions

The repo currently provides ungoogled-chromium for Fedora 39, 40, 41, and Fedora Rawhide. To install it, use these commands:

sudo dnf copr enable wojnilowicz/ungoogled-chromium
sudo dnf install ungoogled-chromium

Floorp

Floorp is a privacy-focused web browser based on Firefox, designed to enhance user security and reduce tracking. It removes telemetry and includes built-in tools for blocking ads and trackers, providing a cleaner browsing experience. With its user-friendly interface, Floorp is an excellent choice for those looking to protect their online privacy.

Installation instructions

The repo currently provides floorp for Fedora 39, 40, 41, and Fedora Rawhide. To install it, use these commands:

sudo dnf copr enable sneexy/floorp
sudo dnf install floorp

Posted by Mohammadreza Hendiani on 2024-10-21 13:43:31 UTC

Just learned that 🤖 can now run models directly from Hugging Face via:
`ollama hf.co/{username}/{repository}`

If you're interested in getting a natively ollama for up and running, consider helping me out at:
gitlab.com/fedora/sigs/ai-ml/g

Fedora Operations Report

Posted by Fedora Community Blog on 2024-10-21 11:05:13 UTC

Its spooky season, and also release season! Here’s a roundup of some stuff’n’things happeing in the project.

Fedora Linux 41

The F41 Go/No-Go meeting will happen on Thursday 24th October @ 1700 UTC. To join, you can find the information on the fedocal calendar entry. This meeting will determine if we can meet the early release date of Tuesday 29th October at this time or not.

There are still some proposed blockers for F41 too, so if you can help resolve some of these bus, please check out our blocker bugs app, or for a more condensed summary, please read out blocker bug report email.

Fedora Linux 42

Fedora Linux 42 is currently in development, and for the most recent set of changes planned in this rel;ease, please refer to our change set page. Our release schedule is also live, and a reminder of some key dates are below:

  • December 18th – Changes requiring infrastructure changes
  • December 24th – Changes requiring mass rebuild
  • December 24th – System Wide changes
  • January 14th – Self Contained changes
  • February 4th – Changes need to be Testable
  • February 4th – Branching
  • February 18th – Changes need to be Complete

The changes that are currently in our community feedback period are :

Changes that are awaiting FESCo voting are:

Hot Topics

For all the latest on boot-c, check out the bootc post on discourse!

Our Git Forge evaluation is continuing, with an instance of both Forgejo and GitLab CE available to try out in the Communshift app. Details of how to get access can be found on this discussion thread, and we are encouraging folks to try out each instance and report their feedback, preferably against the user stories collected, on this discussion thread.

The proposal to amend the Editions Promotion policy has now been submitted to Fedora Council, and a decision is expected this week on both this change, and on the request to grant KDE Desktop Spin edition status also.

FOSDEM 2025 returns on Saturday 1st and Sunday 2nd February! The call for devrooms has passed, but the call for stands is still open until November 7th.

Do you have an idea for an episode of the Fedora Podcast, or want to see what some of the upcoming episodes will be? Bookmark The IT Guy’s discussion post on planning for the podcast!

Did you know there are EPEL Office Hours? If not, check out the details on how to join and when they happen on the announcement post!

The post Fedora Operations Report appeared first on Fedora Community Blog.

Infra and RelEng Update – Week 42 2024

Posted by Fedora Community Blog on 2024-10-18 10:00:00 UTC

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: 14th October – 18th October 2024

I&R Infographic

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

CentOS Infra including CentOS CI

Release Engineering

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 42 2024 appeared first on Fedora Community Blog.

Power t-shirts

Posted by Peter Czanik on 2024-10-15 07:12:21 UTC

I love t-shirts, especially those that you’d call logowear. But it’s not the kind of big name fashion logos that I’m referring to. Rather, it’s logowear from my favorite IT companies. I have well over a hundred of these t-shirts, and except when I’m preparing for a special event, I pull a random t-shirt from my collection. Yesterday I happened to wear a power.org t-shirt, while today I’m wearing an OpenPOWER t-shirt, two POWER t-shirts in two days :-) Both of these brought back some nice memories.

power.org t-shirt

The first t-shirt is really old, I got it probably around 2008, while working for Genesi. One of my tasks was moderating the forums on the power.org website. It was a website focusing on IBM POWER server products, but it also included some generic POWER information. Besides sharing information, it also provided a meeting point for like-minded engineers, where they could discuss anything related to POWER. You can read my history with POWER-based computers in one of my opensource.com articles at https://opensource.com/article/20/10/power-architecture.

OpenPOWER t-shirt

The t-shirt I had on today is a lot more recent, but still cannot be called new. It is a t-shirt by the OpenPOWER Foundation from the golden era of open source on POWER: the POWER9 years. Those years have seen the most active open source development on POWER ever since the Pegasos / PowerMac years. Many applications were ported to POWER, both for the server and the desktop. Hopefully there will be another wave of open source activity on POWER soon, fingers crossed :-)

Do you have any interesting POWER t-shirts? Share with me on your preferred social network! My accounts are listed in the top right corner of this page.

Fedora Operations Report

Posted by Fedora Community Blog on 2024-10-13 22:53:58 UTC

Happy October folks! In this post you’ll find some information on our F41 and F42 releases, plus a few lines on a couple of topics happening around the project lately. Read on to find out more!

Fedora Linux 41

We are nearing the end of the Fedora Linux 41 release cycle! Our Go/No-Go meeting will happen next Thursday 17th October @ 1700 UTC. To join, you can find the information on the fedocal calendar entry.

There are still some proposed blockers for F41 too, so if you can help resolve some of these bus, please check out our blocker bugs app, or for a more condensed summary, please read out blocker bug report email.

Fedora Linux 42

Fedora Linux 42 is currently in development, and for the most recent set of changes planned in this rel;ease, please refer to our change set page. Our release schedule is also live, and a reminder of some key dates are below:

  • December 18th – Changes requiring infrastructure changes
  • December 24th – Changes requiring mass rebuild
  • December 24th – System Wide changes
  • January 14th – Self Contained changes
  • February 4th – Changes need to be Testable
  • February 4th – Branching
  • February 18th – Changes need to be Complete

The changes that are currently in our community feedback period are :

Hot Topics

For all the latest on boot-c, check out the bootc post on discourse!

Our Git Forge evaluation is taking shape. We have an instance of both Forgejo and GitLab CE available to try out in the Communshift app. Details of how to get access can be found on this discussion thread, and we are encouraging folks to try out each instance and report their feedback, preferably against the user stories collected, on this discussion thread. Directly linked to the git forge evaluation, following Wednesdays council meeting, we have decided to extend the report comparing both Forgejo and GitLab CE to be due by December 5th to allow our QA team, and other teams impacted by the F41 release, time to properly validate their use cases against each forge option. This means the council decision may not happen until early January, but we do hope to proceed with a decision as early as possible so the CPE team can help create a migration plan for affected workflows that can be shared and agreed to in good time to allow minimal disruption to the project as a whole as possible.

There is still time to share feedback on the proposal to amend the Editions Promotion policy. You can read the current policy, and what the council would like to change, in this discussion thread.

FOSDEM 2025 returns on Saturday 1st and Sunday 2nd February! The call for devrooms has passed, but the call for stands is still open until November 7th.

A new episode of The Fedora Podcast is now available! Details of episode 38 and how to listen can be found on the discussion post and by visiting the audio post for the latest, and all episodes.

The post Fedora Operations Report appeared first on Fedora Community Blog.

Redis: The Powerhouse Behind Modern Databases

Posted by Piju 9M2PJU on 2024-10-13 11:33:41 UTC

In today’s rapidly evolving tech world, the need for fast and efficient data management is more critical than ever. One name that frequently stands out in the NoSQL database world is Redis. Since its introduction in 2009, Redis has become a go-to choice for real-time applications that require exceptional speed and flexibility in handling data.

In this article, we’ll explore the history of Redis, how it’s used, and the benefits it offers to various modern applications.

The History of Redis: Origins and Evolution

Redis, which stands for Remote Dictionary Server, was developed by Salvatore Sanfilippo in 2009. Initially launched as an open-source project to address scalability issues faced by large-scale systems, Redis quickly gained popularity among developers for its ability to process data at lightning speeds.

Redis operates as an in-memory database, meaning it stores all data in RAM rather than on disk. This design enables Redis to deliver significantly faster performance compared to traditional databases, making it ideal for applications that demand real-time speed.

How is Redis Used?

One of the primary reasons Redis is so popular is its flexibility, allowing it to be used in various scenarios. Here are some real-world examples of how Redis is utilized:

  1. Caching
    Redis is well-known for its use in caching due to its speed. By storing data in memory, Redis drastically reduces the time it takes to retrieve data. This is especially useful in web applications where users need instant access to information such as previously loaded pages, images, or API data.
  2. Session Management
    Many large platforms use Redis to store user session information. When users log into a system, Redis can store their session data in memory, ensuring quick access. This is crucial for maintaining a smooth user experience without delays.
  3. Real-Time Analytics
    In a data-driven world, companies need instant analytics to make informed decisions. Redis enables companies to process and analyze data in real time, such as tracking user behavior on websites, monitoring IoT devices, or analyzing financial transactions as they occur.
  4. Message Queuing
    Redis is also widely used for message queuing via its Pub/Sub (Publisher/Subscriber) feature. This is particularly helpful in systems where real-time communication between services or applications is required, such as notification systems or instant messaging services.

The Benefits of Redis: What Makes It Great?

Incredible Speed
Redis stands out because of its speed. As an in-memory database, Redis delivers sub-millisecond response times, making it one of the fastest technologies available for data management. This is why it is often the preferred choice for real-time applications.

Versatile Data Structures
Another feature that sets Redis apart is its support for various data structures like strings, lists, sets, and hashes. This versatility allows developers to use Redis in a wide range of scenarios, from storing user information to managing complex data in e-commerce systems.

Persistence Options
Even though Redis stores data in memory, it also offers persistence options, allowing users to periodically save data to disk. This provides an added layer of security in case of system failures, ensuring that data is backed up and recoverable.

Easy Scalability
Redis is easily scalable, whether vertically (by adding more RAM) or horizontally (by adding more Redis servers). This is essential for growing applications where the need to process more data increases over time.

Conclusion

Redis has proven itself to be one of the most powerful tools in modern data management. Its incredible speed, support for multiple data types, and scalability make it the top choice for real-time applications. Whether you’re a developer building web apps or a company looking to process real-time analytics, Redis is a technology worth exploring.


There you have it—a brief guide to Redis and the benefits it brings. This technology not only accelerates application performance but also provides a flexible and reliable solution for managing data at scale.

The post Redis: The Powerhouse Behind Modern Databases appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

Infra and RelEng Update – Week 41 2024

Posted by Fedora Community Blog on 2024-10-11 10:00:00 UTC

This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contains updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.

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: 7th October – 10th October 2024

I&R infographic

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

CentOS Infra including CentOS CI

Release Engineering

List of new releases of apps maintained by CPE

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

NOTE: There are currently internal changes happening in CPE Team (we will see if the name even remains), which caused that the last week update didn’t came out (it was also caused by the login issue in community blog, but that was just a coincidence) and caused change in the content (some sections are currently missing). We apologize for that and we see how the format will look in the future.

The post Infra and RelEng Update – Week 41 2024 appeared first on Fedora Community Blog.

PHP version 8.2.25RC1 and 8.3.13RC1

Posted by Remi Collet on 2024-10-11 07:11:00 UTC

Release Candidate versions are available in the testing repository for Fedora and Enterprise Linux (RHEL / CentOS / Alma / Rocky and other clones) to allow more people to test them. They are available as Software Collections, for a parallel installation, the perfect solution for such tests, and also as base packages.

RPMs of PHP version 8.3.13RC1 are available

  • as base packages in the remi-modular-test for Fedora 39-41 and Enterprise Linux ≥ 8
  • as SCL in remi-test repository

RPMs of PHP version 8.2.25RC1 are available

  • as base packages in the remi-modular-test for Fedora 39-41 and Enterprise Linux ≥ 8
  • as SCL in remi-test repository

emblem-notice-24.png The packages are available for x86_64 and aarch64.

emblem-notice-24.pngPHP version 8.1 is now in security mode only, so no more RC will be released.

emblem-notice-24.pngInstallation: follow the wizard instructions.

emblem-notice-24.png Announcements:

Parallel installation of version 8.3 as Software Collection:

yum --enablerepo=remi-test install php83

Parallel installation of version 8.2 as Software Collection:

yum --enablerepo=remi-test install php82

Update of system version 8.3:

dnf module switch-to php:remi-8.3
dnf --enablerepo=remi-modular-test update php\*

Update of system version 8.2:

dnf module switch-to php:remi-8.2
dnf --enablerepo=remi-modular-test update php\*

emblem-notice-24.png Notice:

  • version 8.4.0RC2 is also available in the repository
  • EL-9 packages are built using RHEL-9.4
  • EL-8 packages are built using RHEL-8.10
  • oci8 extension uses the RPM of the Oracle Instant Client version 23.5 on x86_64 or 19.24 on aarch64
  • intl extension uses libicu 74.2
  • RC version is usually the same as the final version (no change accepted after RC, exception for security fix).
  • versions 8.2.25 and 8.3.13 are planed for October 24th, in 2 weeks.

Software Collections (php82, php83)

Base packages (php)

🚀 PM2 Process Manager 🚀

Posted by Piju 9M2PJU on 2024-10-11 00:09:06 UTC

In the past, users with Linux/Unix accounts often relied on various tools such as at, setsid, nohup, screen, and tmux to manage their processes. However, with technological advancements, there is now a more sophisticated and effective process manager available: PM2.

What Is PM2?

PM2 is a modern solution that simplifies application management. It offers a range of features that make it a top choice for developers looking to ensure their applications run smoothly and continuously. PM2 is also compatible with various frameworks and environments, making it versatile for different application types.

Advantages of Using PM2

  1. Start and Stop Processes: With PM2, you can easily manage your applications using simple commands. It supports various types of applications, whether they are Node.js, Python, Go, Java, or others. No more hassle of managing applications manually!
  2. Keep Applications Alive: One of the best features of PM2 is its ability to automatically restart your applications if they crash. This means your applications will always be active and available for users.
  3. Performance Monitoring: PM2 provides real-time metrics on CPU and memory usage, allowing you to optimize your applications more effectively. With this information, you can make better decisions to enhance your application’s performance.
  4. Manage Clusters: PM2 makes it easy to scale your applications with built-in cluster support. You can run multiple instances of your application on a single server to maximize capacity and performance.
  5. Compatibility: PM2 is compatible with various frameworks, such as Express, Koa, NestJS, and more, making it a flexible choice for developers across different environments.
  6. Operating Systems Supported: PM2 runs seamlessly on multiple operating systems, including Linux, macOS, and Windows. This cross-platform support ensures that you can use PM2 in your preferred development environment without any issues.

Conclusion

Given these numerous advantages, it’s no surprise that PM2 has become the go-to choice for many developers to manage their applications. If you’re still using outdated tools like at or nohup, it might be time to consider switching to PM2. With PM2, you’ll experience a significant difference in how you manage your processes and applications.

So, if you’re looking for a modern and efficient process manager that supports various frameworks and operating systems, PM2 is the answer! 🌟

The post 🚀 PM2 Process Manager 🚀 appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

Debugging Jekyll posts locally

Posted by Pavel Raiskup on 2024-10-11 00:00:00 UTC

Just a quick post about a small side-project. For a few years now, I’ve been maintaining a Jekyll Container image. Mostly for my own convenience—whether I’m working on posts for this blog or writing documentation for Mock (or other). I thought I’d share a few words about it now.

Keep My Box Clean! (and DRY)

The motivation was simple: to be able to debug Jekyll/GitHub Pages posts locally before pushing them to GitHub. I wanted to do this consistently across multiple pages, and I didn’t want to repeat myself in the future (following the DRY principle).

Back then, I realized that running Jekyll locally wasn’t a trivial task—at least not on Fedora, if, like me, you prefer staying on a “pure” Fedora system (meaning you only install software distributed through Fedora repositories). Notably, installing the GitHub Pages additions from gems wasn’t easy either, and it still isn’t (as of autumn 2024). Building your own container can also cause some headaches.

Jekyll made easy

So here we are—assuming you have a blog post or any documentation root directory, you can run the Jekyll server in a container, and available on http://localhost:4000/, using just:

$ jekyll-host ./your-jekyll-root
Installing deps, may take several minutes
=========================================
 Server listens on http://127.0.0.1:4000
 Jekyll Log: /tmp/jekyll-server.log (in container)
 Install logs: /tmp/bundler-install.log (in container)
=========================================

The jekyll-host script (which must be in your $PATH) is just a one-line wrapper around a podman run command that uses a pre-built container image hosted and built by https://quay.io/.

I prefer to stay 100% focused on writing, not on the infrastructure. After a quick chat with my colleagues, it seems this setup could be helpful to others as well. If that’s the case, enjoy!

Switch Upgrade

Posted by Fedora Infrastructure Status on 2024-10-10 15:00:00 UTC

A 10G switch in our main datacenter needs upgrades. Many machines may drop off the network and come back during the outage window.

Gaming on Fedora Asahi Remix

Posted by Fedora Magazine on 2024-10-10 14:30:00 UTC

Better support for gaming on Fedora Asahi Remix has been a long standing user request. Today at XDC 2024, we announced the preliminary availability of our game playing toolkit, integrating x86 emulation with MS Windows compatibility. This toolkit, with the conformant Vulkan 1.3 and OpenGL 4.6 drivers, enables playing commercial AAA games on Apple Silicon Macs running Fedora Asahi Remix 40. For more details, see Alyssa’s talk and blog post , or head over to our documentation.

Fedora Asahi Remix is developed in close collaboration with the Fedora Asahi SIG and the Asahi Linux project. As part of our work on the Remix, we’ve also been working on a Change to integrate the FEX emulator into Fedora Linux 42. The goal is to provide a delightful out-of-box experience for users that want to run x86_32 and x86_64 binaries on their AArch64 systems. Today’s release provides a preview of this work. It allows us to perfect the integration and improve the experience on Apple Silicon systems. The aim is for Fedora KDE systems, on AArch64, to offer this functionality out of the box for all supported Fedora ARM desktop systems.

Please report any Remix-specific issues in our tracker. You may also reach out in our Discourse forum or our Matrix room for user support.

The syslog-ng Insider 2024-10: 4.8.0 release; version number; Debian Stable

Posted by Peter Czanik on 2024-10-10 11:48:31 UTC

The September syslog-ng newsletter is now available:

  • Improved FreeBSD and MacOS support in 4.8.0

  • Setting the version number in the syslog-ng configuration

  • Switching containers from Debian Testing to Stable

You can read it at: https://www.syslog-ng.com/community/b/blog/posts/the-syslog-ng-insider-2024-10-4-8-0-release-version-number-debian-stable

syslog-ng logo

Switching Fedora Copr RHSM account to SCA

Posted by Fedora Infrastructure Status on 2024-10-10 10:00:00 UTC

We plan to switch the community RHSM account to Simple Content Access. Systems should stay available during this period.

This outage could impact the copr-frontend and the copr-backend servers.

Syslog-ng needs some karma on Fedora

Posted by Peter Czanik on 2024-10-10 07:27:54 UTC

Version 4.8.1 of syslog-ng was released last week. It is a bugfix release, and it contains fixes for problems also reported by members of the Fedora community. The Fedora 41 release is near, so package updates now need some additional testing, and “karma” in Bodhi. You can find information on how to install syslog-ng 4.8.1 from a testing repo on Fedora 41 beta at https://bodhi.fedoraproject.org/updates/FEDORA-2024-4e812b8a23. This is also the place where you can provide feedback and karma. Thanks for your help!

syslog-ng logo

koji upgrades

Posted by Fedora Infrastructure Status on 2024-10-09 21:00:00 UTC

We will be upgrading koji to the latest upstream version, 1.35.0 with various bugfixes and enhancements.

During the outage the koji hubs will be down as the database schema is updated, and various builders may restart as their koji version is updated.

Additionally, we will be reinstalling some …

Open source is not consent for experiments

Posted by Ben Cotton on 2024-10-09 12:00:00 UTC

“Your scientists were so preoccupied with whether or not they could, they didn’t stop to think if they should.”

Ian Malcolm, “Jurassic Park”

ScanOSS gave an accidental lesson about this recently when, apparently, an “experiment” resulted in filing issues about profanity in open source project code. According to a comment from ScanOSS’s CTO, this was a “brief experiment involving contributions to a small set of repositories” with the intention “to gather insights.” It’s not clear what insights the experiment wanted to produce. What is clear is that they didn’t work with project maintainers before conducting this experiment.

CTO Julian Coccia made it worse with this comment:

The terms of service of Github (and the Open Source license of your choice under which your contribution was released), openly allow contributions from other users. Therefore, people looking at contributing to your project don’t really need your consent before issuing a PR. You always have the right to accept or reject contributions at your discretion.

[…]

If you are not willing to receive contributions from the community, if you are not interested in your Open Source contribution gaining adoption, or if you prefer people to sign special agreements to make contributions, perhaps you are better off closing down your repository, making it private.

If you’ll pardon my language, I think the fuck not! Maintainers are overworked. They don’t need to deal with spam. If you are making a contribution, whether individually or on behalf of a company, it is your responsibility to make sure it’s meaningful. Yes, you’ll get it wrong sometime, but you have to make a good faith effort.

Typically, making a non-trivial contribution involves spending some time learning about the community. At a minimum, reading the contribution guide (if it exists). It does not mean you’re allowed to lob automated issues at projects and then get indignant when the maintainers are mad about it.

With open source licenses, you can do whatever you want with the code you download. Run any experiments your heart desires on it. But once you’re writing instead of reading, you need to be a good participant. No amount of good intention changes that.

This post’s featured photo by Vedrana Filipović on Unsplash

The post Open source is not consent for experiments appeared first on Duck Alignment Academy.

Contribute to Fedora 41 Upgrade and Virtualization Test Days

Posted by Fedora Magazine on 2024-10-09 08:00:00 UTC

Fedora test days are events where anyone can help make certain that changes in Fedora Linux work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed to Fedora before, this is a perfect way to get started.

There are two test periods occurring in the coming days:

  • Friday October 11 through October 15 , is to test the Fedora Upgrade
  • Friday October 11 through October 13 , is to test Virtualization

Come and test with us to make Fedora 41 even better. Read more below on how to do it.

Upgrade test day

As we approach the Fedora Linux 41 release date, it’s time to test upgrades. This release has many changes, and it becomes essential that we test the graphical upgrade methods as well as the command-line methods.

This test period will start on Friday, October 11. It will test upgrading from a fully updated F39 or F40 to F41 for all architectures (x86_64, ARM, aarch64) and variants (WS, cloud, server, silverblue, IoT). See this wiki page for information and details. For this test period, we also want to test DNF5 Plugins before and after upgrade. Recently noted regressions resulted in a Blocker Bug. The DNF5 Plugin details are available here.

Virtualization test day

This test period will start on Friday, October 11 and will test all forms of virtualization possible in Fedora 41. The test period will focus on testing Fedora Linux, or your favorite distro, inside a bare metal implementation of Fedora Linux running Boxes, KVM, VirtualBox and whatever you have. The test cases outline the general features of installing the OS and working with it. These cases are available on the results page.

How do test days work?

A test period is an event where anyone can help make certain that changes in Fedora work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. Test days are the perfect way to start contributing if you not in the past.

The only requirement to get started is the ability to download test materials (which include some large files) and then read and follow directions step by step.

Detailed information about all the test days are on the wiki page links provided above. If you are available on or around the days of the events, please do some testing and report your results

A Comparison of Text Editors – vi, vim, nano, edit, and pico

Posted by Piju 9M2PJU on 2024-10-09 01:12:08 UTC

In the world of Linux and Unix-based systems, text editors play a vital role in editing system configurations, writing scripts, and handling various programming tasks. Whether you are a system administrator, developer, or simply working on a server, choosing the right text editor can impact your productivity and workflow. Today, we will take a look at some of the most popular text editors: vi, vim, nano, edit, and pico. Each of these editors has its own strengths, weaknesses, and use cases.


1. vi: The Classic Workhorse

vi is one of the oldest and most basic text editors available on Unix systems. Released in 1976, it has remained a cornerstone for many Linux users. One of the key reasons for its popularity is that vi comes pre-installed in almost every Unix-based operating system, making it an editor that you can always rely on to be available.

  • Ease of Use: Intermediate
  • Key Features: Minimalist, with basic functionality like modal editing (command and insert modes).
  • Pros:
  • Lightweight and consumes very few resources.
  • Always available by default on Unix systems.
  • Cons:
  • Steep learning curve, as vi relies heavily on keyboard shortcuts, and its modal nature can be confusing for beginners.

vi is perfect for users who prefer something lightweight and don’t need advanced features. It’s especially handy in situations where only a command-line interface is available, and graphical editors are not an option.


2. vim: Vi Improved

vim, released in 1991, stands for “Vi IMproved.” As its name suggests, vim is an enhanced version of vi that offers a wealth of additional features. It retains the same modal nature as vi but includes many conveniences for modern programmers and power users, such as syntax highlighting, multi-level undo, and plugin support.

  • Ease of Use: Intermediate to Advanced
  • Key Features: Extensive customization, syntax highlighting, and support for plugins and scripting.
  • Pros:
  • Highly configurable and ideal for coding and scripting.
  • Large community support with a variety of plugins for specific programming languages.
  • Cons:
  • The learning curve is steep for new users due to its complexity.

vim is a go-to editor for developers and system administrators who need the power and flexibility to work efficiently. Once you master its commands and keybindings, it becomes a highly efficient tool.


3. nano: Simplicity at Its Best

For users looking for an easy-to-learn and intuitive text editor, nano is a great choice. It was released in 1999 as a free replacement for pico and has become widely popular due to its simplicity. Unlike vi or vim, nano does not have modes, and all the available commands are clearly listed at the bottom of the screen, making it very approachable for beginners.

  • Ease of Use: Beginner-friendly
  • Key Features: No modes, simple interface, and basic commands visible on-screen.
  • Pros:
  • Easy to use and available on most Linux distributions.
  • Perfect for beginners or users who just want to make quick edits.
  • Cons:
  • Lacks advanced features like syntax highlighting, plugins, or scripting capabilities.

If you’re new to the Linux environment and need a no-frills editor to get things done, nano is likely your best bet.


4. edit: A DOS Throwback

edit was originally released in 1981 for the MS-DOS environment and became the default editor for many DOS and early Windows users. While it was simple and effective for its time, edit is largely outdated and rarely seen in modern Unix or Linux systems.

  • Ease of Use: Beginner-friendly (for DOS/Windows users)
  • Key Features: Classic DOS-style interface, simple for basic text editing.
  • Pros:
  • Lightweight and familiar to users who have worked in DOS environments.
  • Cons:
  • Very outdated, with limited functionality compared to modern text editors.
  • Irrelevant in most modern Unix/Linux systems.

edit might evoke nostalgia for users who spent time on early DOS-based systems, but it’s not a practical choice in today’s Linux environment.


5. pico: The Original Simplicity

pico, released in 1989, was originally bundled with the Pine email client. Like nano, it is designed for simplicity, with a focus on ease of use. In fact, nano was created as a free clone of pico. While pico was once popular, it has largely been replaced by nano in most Linux systems.

  • Ease of Use: Beginner-friendly
  • Key Features: Simple navigation, basic functionality, no modes.
  • Pros:
  • Straightforward and easy to use.
  • Best for quick text editing without the need for advanced features.
  • Cons:
  • Lacks many features, including plugins, syntax highlighting, and scripting.

While pico has fallen out of favor compared to nano, it still serves its purpose as a simple, lightweight editor for users who value ease of use over advanced features.


Choosing the Right Text Editor

So which one should you use? The answer depends on your needs and experience level:

  • For Beginners: If you’re new to Linux or Unix, start with nano or pico. They are simple, intuitive, and get the job done without much hassle.
  • For Intermediate Users: vim is a powerful tool with a large feature set. If you’re willing to invest time in learning it, vim will reward you with faster editing and more customization.
  • For Minimalists: Stick with vi if you want a light, quick-to-open editor that’s always available.
  • For DOS Fans: If you’re feeling nostalgic, you can still give edit a try, but it’s mostly a relic of the past.

Each text editor has its place in the Linux/Unix world, and the right one for you depends on how comfortable you are with the system and what features you need.


Final Thoughts

While text editors like vi, vim, and nano have different strengths, it’s important to remember that there is no “best” text editor. The best one is the one that fits your workflow and comfort level. Whether you’re just getting started or are a seasoned sysadmin, knowing the right tool for the job will make your life easier.

Which text editor do you use? Share your thoughts in the comments!

The post A Comparison of Text Editors – vi, vim, nano, edit, and pico appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

Reinstalling openqa virthost and database hosts

Posted by Fedora Infrastructure Status on 2024-10-08 21:00:00 UTC

We will be reinstalling some openqa virthost and database hosts as well as reinstalling workers to use a common partitioning and networking setup.

This outage impacts openqa and openqa-labs. During the outage, updates may not go stable; waiting for testing. After the outage is over, openqa will test all pending …

Budapest Audio Expo 2024

Posted by Peter Czanik on 2024-10-08 10:35:05 UTC

This weekend I visited the first Audio Expo in Budapest. It was the first music event I truly enjoyed in years. Even if corridors and rooms were packed, there was enough fresh air. What sets this event apart from other events is the focus on listening to music on the vendors’ products rather than just the speeds and feeds on why you should buy their products. While, of course, the expected outcome is the same, with the emphasis on listening to live systems, I found the event much more comfortable to walk around.

Key takeaway

Do not judge quickly! Go back to a place multiple times! If you are lucky, there will be less people in the room, and you can sit at a better spot. You can also listen to a different music, or listen to the same speakers with a different amplifier. Actually, both of these happened to me this weekend, and brought drastic changes to the experience.

Best of Audio Expo

Everyone is asking me what I liked the most. I am not an engineer when it comes to listening to music. I just listen to my ears and do not care much about the technical details. At home I listen to a pair of Heed Enigma 5 speakers, which are omnidirectional. At the expo the best listening experience was another omnidirectional speaker: the MBL speakers at Core Audio. This was also probably the most expensive setup at the expo.

According to my ears the best value award should go to NCS Audio Reference One PREMIUM. I visited all rooms on all floors and listened to many different speakers along the way. Some were close to or matching the sound quality of the NCS Audio speakers, however for a lot higher price. I only felt with the MBL speakers that they sounded better, however from the price difference you can buy a luxury car :-)

Exhibitors

I had various programs in the neighborhood, so instead of a long block at the Audio Expo, I spent three times a few hours there. Some places I visited multiple times, just to ensure that my first judgment was not too quick. Let me share here my experiences with some of the exhibitors, in alphabetical order.

Allegro Audio

As usual, the system exhibited at Audio Expo sounded really nice. Allegro Audio not only distributes some quality components, but also has its own amplifier: Flow. I really love listening to their Franco Serblin Accordo monitor speakers, but Ktema was not bad either :-)

Core Audio

Probably the most expensive setup of the expo was exhibited by Core Audio. However, the first time I visited them, they played some terrible (at least to me) music. With that music, the whole setup sounded like a pair of $100 computer speakers. So, I started to wonder what is all the hype about MBL speakers… Fortunately, I returned to the show the next day and with a different selection of music, the system really shined, and became the best sounding system of the whole Expo. However, price is prohibitively expensive for most people…

Heed

I listen to various Heed components at home: DAC, amp and speakers. So, I was very happy to see the founder talking about the latest Heed products, and also having the opportunity to listen to them. I love Heed speakers, especially the omnidirectional variants, however for the demo they used GoldenEar speakers with the Heed amplifiers at the Expo. Not bad at all, but different.

Heed

NCS Audio

I already listened to Reference One a few times, and I was amazed. Rock, classical, jazz and others, all sounded perfectly on these speakers, no matter the room size. This time Reference One Premium was on stage, using cables from Bonsai Audio. This pair sounded even better than speakers costing many times more.

NCS Audio

Popori Acoustics

I have been reading about Popori Acoustics for years. Finally I had a chance to listen to these electrostatic speakers made in Hungary for the first time. And I must admit that my first listening experience was not that good. Hearing a woman singing was fantastic. However, even if the sound of bass guitar was very detailed, it still sounded a kind of meh. Luckily I went back on the second day of the expo again. The amplifier was replaced, and suddenly not just human voice, but everything sounded perfectly.

Popori Acoustics

Closing words

Of course there were many more exhibitors. In some cases I loved the sound I heard, but did not have enough time to go back, ask questions, take photos. Some examples are 72audio and Sabo Audio. And there were many more, where the sound was not bad, but did not impress me too much either.

I really hope that next year we will have a similarly good Audio Expo in Budapest!

pagure.io network upgrades

Posted by Fedora Infrastructure Status on 2024-10-08 06:00:00 UTC

Networking gear at the datacenter that hosts pagure.io will be upgraded. Network may be up or down during the outage window as routers and switches are rebooted.

This outage impacts pagure.io.