Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create 2022-07-20-community-wg-discusses-next-edition.md
- Loading branch information
Showing
1 changed file
with
43 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
--- | ||
|
||
author: Douglas DeMaio | ||
date: 2022-07-20 10:00:00+10:00 | ||
layout: post | ||
image: /wp-content/uploads/2022/06/opensuse-alp-concept-unofficial.png | ||
license: CC-BY-SA-3.0 | ||
title: Community Work Group Discusses Next Edition | ||
categories: | ||
- Announcements | ||
- openSUSE | ||
tags: | ||
- openSUSE | ||
- Developers | ||
- Open Source | ||
- distrowatch | ||
- Linux | ||
- Adaptable Linux Platform | ||
- ALP | ||
- MicroOS | ||
- Feedback | ||
|
||
--- | ||
|
||
Members of openSUSE had a visitor for a [recent Work Group (WG) session](https://etherpad.opensuse.org/p/weeklymeeting20220621) that provided the community an update from one of the leaders focusing on the development of the next generation distribution. | ||
|
||
[SUSE](https://www.suse.com/) and the [openSUSE](https://get.opensuse.org/) community have a steering committee and several Work Groups (WG) collectively innovating what is being referred to as the Adaptable Linux Platform (ALP). | ||
|
||
[SUSE](https://www.suse.com/)'s Frederic Crozat, who is one of ALP Architects and part of the ALP steering committee, joined in the exchange of ideas and opinions as well as provided some insight to the group about moving technical decisions forward. | ||
|
||
The vision is to take step beyond of what SUSE does with modules like in SUSE LInux Enterprise (SLE) 15. This is not really seen on the openSUSE side. On the SLE side it's bit different, but the point is to be more flexible and agile with development. The way to get there is not yet fully decided, but one thing that is certain is containerization is one of the easiest ways to ensure adaptability. | ||
|
||
"If people have their own workloads in containers or VMs, the chance of breaking their system is way lower," openSUSE Leap release manager Lubos Kocman pointed out in the session. "We'll need to make sure that users can easily search and install "workloads" from trusted parties." | ||
|
||
In some cases, people break their systems by consuming software outside of the distribution repository. Some characterizations of ALP have been referred to as strict use of containers such as flatpaks, but it's better to reference the items as workload. There were some efforts planned for [Hack Week](https://hackweek.opensuse.org/) to provide documentation regarding the workload builds. | ||
|
||
There was confirmation that there will be no migration path from SLES to ALP, which most think would means the same for Leap to ALP, but this does not necessarily apply for openSUSE as people are not being stopped from writing upgradeable scripts. | ||
|
||
Working on the community edition is planned after the proof of concept, but the community is actively involved with developing the proof of concept. Some points brought up were that the intial build will aim at a build on Intel and then expand later with other architectures. | ||
|
||
The community platform is being referred to as openSUSE ALP during its development cycle with SUSE to be concise with planning the next community edition. | ||
|
||
<meta name="openSUSE, Tumbleweed, Developers, sysadmin, user, Open Source, rolling release, gamers, superuser, distrowatch, hacker, Linux, Kernel, ALP, openSUSE, support" content="HTML,CSS,XML,JavaScript"> |
aaed68b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same issue with this article publishing @cboltz & @hellcp. I provided feedback on https://progress.opensuse.org/issues/113803. By my calculations, it took about 48 hours for the server to pick it up.
aaed68b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, I remember from the manual jekyll run yesterday that the article was intentionally skipped because of
date: 2022-07-20 10:00:00+10:00
which (as of yesterday) was a date in the future.So if you schedule an article to be published on a specific future date, you shouldn't be too surprised if jekyll honors this ;-)
BTW: The
+10:00
doesn't look like an european timezone, not sure if that was intentional.aaed68b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. Thank you @cboltz. I see what you're saying now. I understand now.