openSUSE Project March 2021

project@lists.opensuse.org

30 participants
19 discussions

by ddemaio

Hi all, There was a recent post on reddit (https://old.reddit.com/r/linux/comments/m1xl56/is_opensuse_leap_ready_to_be…) that made us take a look at how to present our lifecycle page (https://en.opensuse.org/Lifetime) and info to be added to the marketing of Leap 15.3. There were several comments on reddit that can be summarized as there is a lack of clear information on how long the lifecycle of Leap 15.x will be going forward. When the info on https://en.opensuse.org/Lifetime was originally written, there was some clarity on major versions lasting a minimum of 36 months. We know Leap 42 and 15 exceeded that lifecycle. It looks like we're at a point where we evolved and need to provide a bit more clarity for people based on the reddit comments I propose we change the lifecycle page to include the following sentences and include the info in the marketing of Leap 15.3 and beyond (for the foreseeable future): Leap *Major Release* (15.x) extends maintenance and support until a successor. At present, a successor has not been declared; Leap 15's lifecycle fully aligns with SUSE Linux Enterprise. There is a projection as of March 2021 that Leap 15 will extend to Leap 15.5. Both major versions of Leap 42 and 15 were supported more than 36 months. Any thoughts, changes, removals or additions to the above sentences. v/r Doug

9 months

[opensuse-project] Can one manually become a "Member Emeritus"

by Stefan Seyfried

Hi all, after reading https://en.opensuse.org/openSUSE:Members, I understand that I can cancel my membership status with immediate effect and forever. To become a "Member Emeritus", with a "way back" into the community in case things might turn good again, I have to wait for the status request and just not respond to it. But the last such request was almost 3 years ago. IIUC I need to stop all actions on the mailing lists (might be a good idea ;-)) and packaging (not so good) for the bot to pick me up. So is there a manual procedure to follow to become "Member Emeritus"? Best regards, Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

9 months, 1 week

Re: [opensuse-project] huge amount of SPAM on opensuse-connect

by christian.imhorst＠posteo.de

Hi, Am Do., 21. Feb. 2019 um 15:32 Uhr schrieb Lars Vogdt <Lars.Vogdt(a)suse.com>: As such, maintaining 447 [1] openSUSE members should not depend on a single tool. Especially not if the used tool has open, well known security issues since years[2]. On Thu, 21 Feb 2019 11:41:19 +0100 Richard Brown wrote: > This isn't the first time I've asked this question on a public stage, > but in the hope that this time I get an answer; > Who volunteers to tackle the problem with connect.o.o and drive > forward a solution? I made my proposal already and I stand the point: shut down an insecure system! what does "drive forward a solution" mean? Can we integrate the functions of connect.o.o into other services at openSUSE which are allready maintained like the openSUSE wiki? A form for travel support for example? An application for membership could be done by e-mail to an e-mail address of the membership officials. Elections could be done with an eVote software like https://github.com/mdipierro/evote for example, but probably there are better tools. What did I miss? I think Lars is right an we should shutdown this insecure system as soon as possible. Regards Christian Imhorst -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

11 months, 3 weeks

openSUSE Conference Meetings

by ddemaio

Hi all, I plan to have meetings for the planning of the openSUSE Conference starting next week every Tuesday at 18:00 UTC on the opensuse-project IRC channel. I'll plan to continue this until the conference in June. We might switch the meeting over to discord and use the bot on IRC to record the minutes. We will be using venueless (https://github.com/venueless/venueless) for the conference. I'm trying to get some documentation to better understand the features. I have access to our instance at https://opensuse.venueless.events/ If you want to know more about it, there was video done last year here https://youtu.be/u95cNlC25Ic Some of the features have changed. If you want to help with this, please let me know. Otherwise, I'll see you on Tuesday. If you haven't registered or submitted a talk for the conference, you can do so at https://events.opensuse.org/. The Call for Papers is open until May 4. v/r Doug

1 year, 1 month

MirrorBrain?

by Steven Hess

It was suggested I repost this here. I originally posted it in Project on the openSUSE Discord Server. "I don't know if this is the proper place for this to get attention but I'll post this here anyway. Firstly I want to praise all the people who contribute to the required work to keep Tumbleweed rolling on. The latest snapshot was a huge undertaking and much work was required to make it a success. So thanks to all those people. That said however many people had a painful experience obtaining this snapshot. For whatever reason there was much timing out and many had to manually ride herd on the dup. I don't think it is an issue of sufficiency of mirrors. I think it has more to do with MirrorBrain. It's just not routing people to the closest and most robust mirror. Here on Discord there was much discussion of the multi day difficulty in getting the multi gigabyte snapshot downloaded. Is there something that can be done about this?" This is a reoccurring issue. Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS K6KGE DM05gd22 Owner Flex-1500, Flex-6300, Flex-6400, FT-857D, and FT-817ND 927.0875Mhz and 441.125 analog 441.575 DMR, and 441.600 Fusion Repeaters Taft Ca. openSUSE Tumbleweed KDE Plasma with Packman

1 year, 1 month

Minutes of openSUSE Board meeting 2020-02-01

by Gerald Pfeifer

[ I wanted to wait a few days after this meeting so that the proper ] [ announcement of Syds goes out before these minutes, and then ... ] [ missed. Apologies. Note that the 2020-02-15 meeting was really short, ] [ just an informal chat, and we did not have one on 2020-03-01, so with ] [ this there's only one set of minutes outstanding. ] ==== Minutes of openSUSE Board meeting 2020-02-01 ==== Present: Axel, Gerald, Gertjan, Neal, Vinz Excused: Simon Minutes: Gerald Next: Neal == Treasurer == * Introduction Syds * Financial controller/accountant for 15 years, variety of businesses & freelance * "everything with computers and numbers" * openSUSE member since last year * General discussion on the role of treasurer * SUSE is willing to share opex budget spent on openSUSE with board AI Simon: reach out to Andrew (outgoing treasurer) before any announcement == Follow-up on Year End Survey == * Not everyone on the board could join, but all very positive about the initiative * Good conversations * No specific actions for the board as a body * Individually we do/will support == Communications == * A bit of confusion around upgrade of the forums software, which turned out to be a misunderstanding * Idea: It would be great if various team share somewhat regular updates (monthly to quartlery maybe) about all the goodness they do, WIP, and challenges AI Neal: approach other Heroes on the idea of some regular update == Leap 15.3 == * One of us mentioned some specific technical issues they saw * Suggestion to raise with openSUSE release engineering team

1 year, 1 month

[project] software.opensuse.org and download.opensuse.org are miserable re: MC and pegging CPU waiting to connect and waiting to load

by Felix Miata

https://software.opensuse.org/download/package?package=mc&project=openSUSE%… clearly lists mc 4.8.26 availability @ https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_6… which apparently doesn't exist, as also not https://download.opensuse.org/repositories/openSUSE:/Factory/standard/ If I try to fetch it, it redirects to https://download.opensuse.org/tumbleweed/repo/oss/x86_64/mc-4.8.25-1.4.x86_… which is very much not what I'm interested in. All download.opensuse.org, as previously reported, take forever to load when trying to check in a web browser: https://progress.opensuse.org/issues/69736 https://progress.opensuse.org/issues/62255 mc 4.8.26 was officially released more than 3 months ago. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

1 year, 1 month

GSoC mentor for rpmlint

by ddemaio

Hi all, Is anyone in the project willing to mentor someone interested in being mentored on rpmlint? They have previous experience. If so, please let me know. v/r Doug

1 year, 1 month

Re: openSUSE Leap 15.3 Reaches Beta Build Phase

by Sarah Kriesch

Am 22.03.21 um 08:46 schrieb Gerald Pfeifer: > On Mon 2021-03-08, ddemaio wrote: > > Does one really need to find bugs to qualify for the T-shirt? If so, > maybe you running with Hungarian language setting will unveal some, > translation or otherwise? > How many years did we receive only a low number of Translation bugs? But that is a good idea, if you can speak multiple languages. Try another language setup and test other languages. That qualifies for Bete test bug reports, too. > Gerald > Best regards, Sarah

1 year, 1 month

openSUSE Leap 15.3 Reaches Beta Build Phase

by ddemaio

Hi all, I wanted to bring your attention to the recent release of the openSUSE Leap 15.3 beta on https://get.opensuse.org/testing/ <https://get.opensuse.org/testing/> We are not in the beta build phase. Thank you to all who helped with getting things into shape thus far and please don't forget to test the beta. The below is published at https://news.opensuse.org/2021/03/03/opensuse-leap-153-reaches-beta-build-p… v/r Doug openSUSE <https://www.opensuse.org/> Leap has entered into the beta release <https://get.opensuse.org/testing/> phase today for its 15.3 <https://get.opensuse.org/testing/> minor version. This openSUSE Leap 15.3 <https://en.opensuse.org/Portal:15.3> version is a solidified release that focuses more on the building of the distribution rather than refreshing the distribution’s packages, but there are some significant changes to the distribution. Many of the packages will remain the same as those in openSUSE Leap 15.2 <https://en.opensuse.org/Portal:15.2> with a bit of hardware enablement and security backports. An updated version of glibc <https://www.gnu.org/software/libc/> brings some Power10 <https://en.wikipedia.org/wiki/POWER10> support and the Xfce <https://www.xfce.org> desktop users will have the new 4.16 <https://www.xfce.org/about/news/?post=1608595200> version. The distribution also gains adds s390x <https://en.wikipedia.org/wiki/Linux_on_IBM_Z> architecture. The biggest change for this release is how Leap is built and its relationship with SUSE Linux Enterprise <https://www.suse.com/products/server/>. Leap transitioned to a new way of building openSUSE Leap <https://en.opensuse.org/Portal:Leap> releases in the fall of 2020 through a prototype project called Jump <https://en.opensuse.org/Portal:Jump>. The Jump prototype was used as a proof of concept, but no longer exists; it did prove to work at building a distribution and bringing the code streams of both openSUSE Leap and SLE closer together. The proof of concept was implemented for building the release of openSUSE Leap 15.3 as seen in the beta release today. Building Leap on top of binary packages from SLE, which was part of the rationale for the Jump prototype, allows for easy development on a community release to be put into production on an enterprise release should the need arise. The changes make the migration from openSUSE Leap 15.3 to SLE 15 Service Pack 3 practically instantaneous and there are no socket or virtual machine limitations. A little more than 50 packages are not identical with SLE <https://en.opensuse.org/Portal:15.3/Features:Identicality>, but these are mostly branding, patterns and openSUSE branding packages. Entering this beta phase, testers are encouraged to test the migration from Leap to SLE. People testing the beta are encouraged to record their Leap Beta testing efforts on the following spreadsheet: https://docs.google.com/spreadsheets/d/1AGKijKpKiJCB616-bHVoNQuhWHpQLHPWCb3… <https://docs.google.com/spreadsheets/d/1AGKijKpKiJCB616-bHVoNQuhWHpQLHPWCb3…> Leap beta testers have an option to receive a T-shirt, so make sure to fill in all the proper information and bug reports to get one. Then send an email to ddemaio (at) opensuse.org with your address, size and name corresponding to the spreadsheet. Please make the subject title “beta test t-shirt”. Bugs should be reported on openSUSE’s bugzilla <http://bugzilla.opensuse.org> and if any are found on SLE should be reported to SUSE’s bugzilla products for desktop <https://bugzilla.suse.com/enter_bug.cgi?classification=SUSE%20Linux%20Enter…>, server <https://bugzilla.suse.com/enter_bug.cgi?classification=SUSE%20Linux%20Enter…> and High Availability <https://bugzilla.suse.com/enter_bug.cgi?classification=SUSE%20Linux%20Enter…>. Leap has a rolling development model during both its Alpha and Beta phases. After the gold master and Public Availability of Leap is released, the rolling development model stops; the release then shifts into a supported release model with maintenance and security updates until its End of Life (EOL) <https://en.wikipedia.org/wiki/End-of-life_product>. Leap has an extended life cycle greater than 12 months per release. Leap ideal for desktop and server environments. There are no concrete milestones in the Leap rolling development model. As bugs are fixed and new packages introduced or excluded, snapshots of the latest beta phase builds will be released once they pass openQA testing; this will take place over the next few months as the road map <https://en.opensuse.org/openSUSE:Roadmap> shows openSUSE Leap 15.3 will be have a Release Candidate in late April and the Gold Master on May 21, which will be follow by a public release on June 2. The documentation and translations deadline is May 14. Architectures available for testing <https://get.opensuse.org/testing/> include x86_64 <https://en.wikipedia.org/wiki/X86-64>, aarch64 <https://en.wikipedia.org/wiki/AArch64>, PowerPC <https://en.wikipedia.org/wiki/PowerPC> and s390x <https://en.wikipedia.org/wiki/Linux_on_IBM_Z>. People interested in armv7 and other architectures should read the announcement about openSUSE Step <https://news.opensuse.org/2021/02/11/opensuse-new-project-looks-to-build-sl…>. Those interested in beta testing images for openSUSE Leap 15.3 Windows Subsystem for Linux <https://en.opensuse.org/openSUSE:WSL.> can contact the Leap release manager Luboš Kocman <https://github.com/lkocman> or the factory mailing list <https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/>.

1 year, 1 month

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Project March 2021