banazir

The openSUSE Board is calling for the formation of a working group to explore topics focused on project governance, operational models and rebranding for the project.

This follows a call on the openSUSE Project mailing list to formalize efforts, ideas and suggestions by community members in a centralized location.

cross-posted from: https://fedia.io/m/pine64@lemmy.ml/t/1266175

A new community update! New hardware to announced and previous hardware to return!

In recent testing scenarios involving a build and NetworkManager, a significant issue has surfaced: the network stack becomes non-operational.

Users are advised to postpone system updates for now, but if users have already updated, use Snapper to rollback; it’s important to note that while the issue primarily affects GNOME setups with Wicked, it can also impact servers without these components.

This problem has been consistently reproducible since at least the 20240825 Tumbleweed build. Bind 9.20.1 received an update has changes to DNS query handling and system controls, which may have inadvertently contributed to the network stack issue.

cross-posted from: https://lemm.ee/post/37281970

Believe it or not, an unexpected conflict has arisen in the openSUSE community with its long-time supporter and namesake, the SUSE company.

At the heart of this tension lies a quiet request that has stirred not-so-quiet ripples across the open source landscape: SUSE has formally asked openSUSE to discontinue using its brand name.

Richard Brown, a key figure within the openSUSE project, shared insights into the discussions that have unfolded behind closed doors.

Despite SUSE’s request’s calm and respectful tone, the implications of not meeting it could be far-reaching, threatening the symbiotic relationship that has benefited both entities over the years.

cross-posted from: https://lemmy.ml/post/17607748

Slowroll, which has a more modest update cadence than Tumbleweed, is gaining acceptance as a balance between the rapid updates of Tumbleweed’s rolling releases and the traditional Leap release.

Slowroll is nearly ready for full deployment and the development team has been working diligently to prepare the next version bump, with planned updates scheduled for July 9, August 9 and Sept. 9. These updates are expected to maintain a consistent monthly cadence to ensure users have timely and stable updates.

One of the critical updates pulled in will include the latest OpenSSH CVE fixes, which have already been made available in Tumbleweed. This fix enhances the security of Slowroll & ensure that it remains a robust and reliable distribution for users.

Highlighted Features of Slowroll

Balanced Update Cadence: Slowroll offers a monthly rolling update cycle that provides users with the latest features and security updates while ensuring stability through extensive testing and validation.

Beta Phase: Slowroll is now in the Beta phase, indicating its near readiness for full deployment. Users can expect a reliable experience with continuous improvements.

Continuous Improvement: The distribution integrates big updates approximately every month, alongside continuous bug fixes and security patches, ensuring a secure and up-to-date system.

Statistics and Status

According to the latest statistics available on the Slowroll Stats page:

Tumbleweed had 2813 updated packages since the last version bump

Slowroll received 1316 updates from 871 different packages and only 339 updated rpms are Slowroll-specific builds

Origins and Purpose

Slowroll, introduced in 2023, was designed as an experimental distribution. Its primary goal is to offer a slower rolling release compared to Tumbleweed, thus enhancing stability without compromising on access to new features. The distribution continuously evolves with big updates integrated approximately every month, supported by regular bug fixes and security updates.

It’s crucial to understand that Slowroll is not intended to replace Leap. Instead, it provides an alternative for users who desire more up-to-date software at a slower pace than Tumbleweed but faster than Leap.

If you try Slowroll, have a lot of fun - rolling… slowly!

Slowroll, which has a more modest update cadence than Tumbleweed, is gaining acceptance as a balance between the rapid updates of Tumbleweed’s rolling releases and the traditional Leap release.

Slowroll is nearly ready for full deployment and the development team has been working diligently to prepare the next version bump, with planned updates scheduled for July 9, August 9 and Sept. 9. These updates are expected to maintain a consistent monthly cadence to ensure users have timely and stable updates.

One of the critical updates pulled in will include the latest OpenSSH CVE fixes, which have already been made available in Tumbleweed. This fix enhances the security of Slowroll & ensure that it remains a robust and reliable distribution for users.

Highlighted Features of Slowroll

Balanced Update Cadence: Slowroll offers a monthly rolling update cycle that provides users with the latest features and security updates while ensuring stability through extensive testing and validation.

Beta Phase: Slowroll is now in the Beta phase, indicating its near readiness for full deployment. Users can expect a reliable experience with continuous improvements.

Continuous Improvement: The distribution integrates big updates approximately every month, alongside continuous bug fixes and security patches, ensuring a secure and up-to-date system.

Statistics and Status

According to the latest statistics available on the Slowroll Stats page:

Tumbleweed had 2813 updated packages since the last version bump

Slowroll received 1316 updates from 871 different packages and only 339 updated rpms are Slowroll-specific builds

Origins and Purpose

Slowroll, introduced in 2023, was designed as an experimental distribution. Its primary goal is to offer a slower rolling release compared to Tumbleweed, thus enhancing stability without compromising on access to new features. The distribution continuously evolves with big updates integrated approximately every month, supported by regular bug fixes and security updates.

It’s crucial to understand that Slowroll is not intended to replace Leap. Instead, it provides an alternative for users who desire more up-to-date software at a slower pace than Tumbleweed but faster than Leap.

If you try Slowroll, have a lot of fun - rolling… slowly!

cross-posted from: https://lemmy.ml/post/11932658

The openSUSE community is pleased to announce that it will have short sessions aimed at encouraging people on how to contribute to the project.

A group of volunteers will present short 15-minute sessions that are streamed and/or recorded on openSUSE’s YouTube channel that are aimed at teaching people about packaging, using the Open Build Service, creating tests for openQA and other development areas.

The first session about “Basic use of OBS/osc using a version bump as an example” is set to begin tomorrow, on Feb. 15 at 21:00 UTC.

Another talk, “Packaging Guidelines (Patch Policies) and Submission of New Packages”, is scheduled for Feb. 27 at 16:00 UTC.

More sessions are expected to be scheduled for future dates.

The sessions are listed on the openSUSE Calendar; look for the Contribution Workshop sessions marked in orange.

Those who are interested in presenting should fill in the blank area for future sessions listed in the email about the events.

Giving a session is a great way to give back to the community and provides opportunities to teach others skills and knowledge about open-source development.

The openSUSE community is pleased to announce that it will have short sessions aimed at encouraging people on how to contribute to the project.

A group of volunteers will present short 15-minute sessions that are streamed and/or recorded on openSUSE’s YouTube channel that are aimed at teaching people about packaging, using the Open Build Service, creating tests for openQA and other development areas.

The first session about “Basic use of OBS/osc using a version bump as an example” is set to begin tomorrow, on Feb. 15 at 21:00 UTC.

Another talk, “Packaging Guidelines (Patch Policies) and Submission of New Packages”, is scheduled for Feb. 27 at 16:00 UTC.

More sessions are expected to be scheduled for future dates.

The sessions are listed on the openSUSE Calendar; look for the Contribution Workshop sessions marked in orange.

Those who are interested in presenting should fill in the blank area for future sessions listed in the email about the events.

Giving a session is a great way to give back to the community and provides opportunities to teach others skills and knowledge about open-source development.

cross-posted from: https://lemmy.ml/post/10523858

We currently have a generic port for Nvidia Tegra 2/3/4 devices using U-Boot as bootloader, supporting 9 different devices at the time of writing. This wouldn't have been possible without the work of Svyatoslav Ryhel (also known as Clamor), who has been working on Tegra devices for the last few years and is also a maintainer of Nvidia Tegra SoCs in U-Boot.

The wiki page has a list of supported devices.

Svyatoslav ported most of these devices without owning one, just relying on testing from people. This means anyone having such a device can reach him and eventually will be able to replace the old proprietary vendor bootloader with U-Boot.

cross-posted from: https://lemmy.ml/post/10523858

We currently have a generic port for Nvidia Tegra 2/3/4 devices using U-Boot as bootloader, supporting 9 different devices at the time of writing. This wouldn't have been possible without the work of Svyatoslav Ryhel (also known as Clamor), who has been working on Tegra devices for the last few years and is also a maintainer of Nvidia Tegra SoCs in U-Boot.

The wiki page has a list of supported devices.

Svyatoslav ported most of these devices without owning one, just relying on testing from people. This means anyone having such a device can reach him and eventually will be able to replace the old proprietary vendor bootloader with U-Boot.

We currently have a generic port for Nvidia Tegra 2/3/4 devices using U-Boot as bootloader, supporting 9 different devices at the time of writing. This wouldn't have been possible without the work of Svyatoslav Ryhel (also known as Clamor), who has been working on Tegra devices for the last few years and is also a maintainer of Nvidia Tegra SoCs in U-Boot.

The wiki page has a list of supported devices.

Svyatoslav ported most of these devices without owning one, just relying on testing from people. This means anyone having such a device can reach him and eventually will be able to replace the old proprietary vendor bootloader with U-Boot.