Search results for

Re: Is slowroll broken?

by Stefan Seyfried

On 13.09.23 06:06, Larry Len Rainey wrote: > Timeout exceeded when accessing > 'https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll…'. - Can't provide ./repodata/876557493f31abad37825b61e24c91ddc5859b8a65315e16258318341df1dcc2-appdata.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'base-non-oss' because of the above error. "Timeout exceeded when accessing". Something network, infrastructure, whatever. Not something specific to "Slowroll" I'd guess. Reading the messages printed on the screen helps. Sometimes. :-) Have fun! -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

1 year, 1 month

Re: Devel projects not building against Slowroll, yet

by Jiri Slaby

On 27. 06. 24, 18:01, Christophe Marin via openSUSE Factory wrote: > Hello, > > On behalf of KDE maintainers: > > On jeudi 27 juin 2024 14:35:14 UTC+2 Dominik Heidler wrote: > >> KDE:Applications >> KDE:Extra >> KDE:Frameworks > >> KDE:Qt:5.15 >> KDE:Qt6 > > This was asked some time ago and the reply didn't change. > We won't add slowroll builds to the KDE repos. > Slowroll users want older versions of packages, not the ones from the devel > projects. Devel projects are useful to check if the latest version fixed a bug. So the above does not make sense at all. -- js suse labs

4 months, 1 week

Just figured out that the slowroll I installed pointed to tumbleweed repos and not slowroll repo. It still is broken.

by Larry Len Rainey

1 year, 1 month

Re: Leap Replacement - Results from recent contributor survey

by Lubos Kocman

Thank you for sharing the results Richard! As said before the survey was live. The results preferring a rolling model are to be expected for a contributor community. That was never the strong side of Leap 15.X For me, the important part is the preferred lifecycle which shows that corespondents want 12-18 months lifecycle on the server etc. Desktop bit shorter. In an ALP-like universe (thinking of Leap Micro now) we do it exactly the opposite where we do 12 months (over two releases) for LeapMicro, while desktop users using Leap get 18 (next release + 6 months overlap). I also stay positive and optimistic when it comes to help from other teams. So far I had good experience with any timely issue. Lubos On Sat, 2023-09-02 at 10:19 +0200, Richard Brown wrote: > Hi all, > > I've been looking at the results from the recent contributor survey > to > gauge the interest and feasibility of replacing openSUSE Leap with a > new community-built offering. > > For those who may not have been keeping up with the efforts, their > are > proposals to build two very different distributions to replace Leap: > > "Linarite" - a regular old fashioned release desktop distribution, > likely with a narrower package selection than we're used to with Leap > unless we find significantly more contributors to be able to support > everything > > "Slowroll" - a derivative of Tumbleweed, built automatically as much > as > possible, using automation and metrics to copy packages from > Tumbleweed > only after certain conditions (max age, X weeks without change, etc). > Basically an attempt to provide something less scary than full speed > Tumbleweed. > > Rather than bombard everyone with all the data, I've decided to take > the approach of asking specific questions and seeing what data from > the > survey best helps answer that question. > > --- > Q1: Did the survey reach a representative sample of our contributor > base? > > A: The survey received 251 responses in total, 101 from people who > self > identified as a 'Contributor', either to the distributions or the > Project more broadly. 72 identified as a distribution contributor, > which is larger than the 61 people who submitted packages to Leap or > Backports for the last release. Therefore I think it's clear the > survey > reached a broad enough audience to draw some meaningful conclusions > from. > > --- > Q2: Between "Linarite", "Slowroll" and not replacing Leap, which is > the > most popular with our contributors? > > A: Not replacing Leap was the most popular option when distribution > contributors were asked which options would they contribute towards > (39%) > > Not replacing Leap/using Tumbleweed was the most popular option when > distribution contributors were asked which would they use on their > desktop/laptops (54%) > > Those same contributors did collectively suggest that Linarite should > be the direction of openSUSE (37%) and what they'd use on their > servers > (43%) > > Q3. Between "Linarite", "Slowroll" and not replacing Leap, which is > the > most popular with our users? > > Slowroll was the most popular option when users were asked which > options they'd contribute towards (28%). Linarite was 3rd (19%) after > not replacing Leap (25%) > > Slowroll was also the #1 option when users were asked which option > was > the best direction for openSUSE (39%) and which would they use on a > server (48%). > > Just using Tumbleweed was also the most popular option with our users > for their desktop/laptops (41%), followed by Slowroll (36%) > > Linarite was not the #1 choice for our users in any of the questions > asked. > > Q4. Do we have enough contributors/Can we get enough contributors to > make any option work? > > 24 distribution contributors said they would contribute to Linarite > 13 said they would contribute to Slowroll > 49% said they wouldn't contribute to any Leap replacement > > 26 users said they would contribute to Linarite > 38 said they would contribute to Slowroll > 53% said they wouldn't contribute to any Leap replacement > > --- > Some thoughts/analysis > > Our users seem to overwhelmingly favour rolling releases, with > 51%-64% expressing a preference for either Tumbleweed or Slowroll > regardless of whether they're being asked if they'll use it for > Server, > Desktop, or whether they'll contribute or think it's the best > direction > for the project. > > This preference increases when contributors are asked, with the > preference ranging between 55%-71% depending on the question. > > In the light of these results, it is my suggestion to the community > that if we are to build something to replace Leap, then the option we > should focus on is Slowroll. > > It is the most popular with our users, and the option more closely > aligned to what our contributors use themselves. > > I also think its more important for the Leap replacement to focus on > Desktop use cases, as openSUSE will also be hosting 1:1 copies of > SUSE's ALP products. Those products should be awesome for folk who > want > Enterprise-like server distros. > > Given that it seems silly to spread ourselves too thin trying to make > a > Leap replacement that is both a Server and Desktop OS. > > That said though, I am still concerned that we do not have enough > contributors to make any Leap replacement viable. > > Leap has struggled even with 61 folk contributing directly to the > codebase and backports/PackageHub. And this is when we've had the SLE > codebase to borrow from, which dramatically reduced the work > required. > > Either Slowroll or Linarite would require considerably more packaging > and maintenance work than Leap. > > And yet, based on these survey results, we look like we're going to > be > replacing Leap with significantly _fewer_ contributors than we have > even for Leap. > > Outside of the survey, only 17 people have expressed an interest in > working on a Leap replacement, and so far Slowroll and Linarite have > both been one-man-shows. > > Being hopeful, Slowroll does seem to be the concept that promises to > convert more users into contributors. > > And if we focus on Desktop-only (relying on the 1:1 ALP copies for > Server) we might not need as much effort. > > But I worry that we'd do more harm than good for our community to > push > forward towards any effort that doesn't really have much enthusiasm > behind it. > > The survey clearly shows a tendency for folk to believe openSUSE > should > do things which they themselves are not willing to contribute to. > > For a Leap replacement to be viable, both to be made and then > supported > for years, I'm convinced we need a significant increase in folk > rolling > up their sleeves and working towards it. > > So, I want to challenge the community with a few questions > > Shall we go on with these efforts? > If so, are you willing to help? > > Thoughts, comments, flames all welcome

1 year, 2 months

New Slowroll update 20241011T1805 released!

by bernhardout＠lsmod.de

Please note that this mail was generated by a script. A collection of maintenance updates was released for Slowroll. Released 1 packages: * MozillaFirefox

3 weeks, 6 days

New Slowroll update 20240928T1906 released!

by bernhardout＠lsmod.de

Please note that this mail was generated by a script. A collection of maintenance updates was released for Slowroll. Released 1 packages: * libostree

1 month, 1 week

New Slowroll update 20241107T1526 released!

by bernhardout＠lsmod.de

Please note that this mail was generated by a script. A collection of maintenance updates was released for Slowroll. Released 1 packages: * gimp

1 day

New Slowroll update 20241105T0445 released!

by bernhardout＠lsmod.de

Please note that this mail was generated by a script. A collection of maintenance updates was released for Slowroll. Released 1 packages: * govulncheck-vulndb

3 days, 11 hours

New Slowroll update 20241107T1206 released!

by bernhardout＠lsmod.de

Please note that this mail was generated by a script. A collection of maintenance updates was released for Slowroll. Released 1 packages: * NetworkManager-branding

1 day, 4 hours

Re: VOTE ON SLOWROLL NAME

by Roger Oberholtzer

On Mon, Sep 25, 2023 at 6:28 PM Joe Salmeri <jmscdba(a)gmail.com> wrote: > On 9/24/23 22:47, Felix Miata wrote: > > Lew Wolfgang composed on 2023-09-24 19:17 (UTC-0700): > > > >> Robust and stable. Sequoia? But I think that name has been taken. > >> Maybe another strong tree? Hickory? > > Teak, very nice. But, good trees grow slowly. Slow is already in > Slowroll, and I > > like the nick I use locally, sslo, for filesystem LABELs and mountpoints. > > One the things that drive me nuts is when companies come up with names > which they think are meaningful but that require users to do research to > figure out what it really is. > > Look at the mess Intel has with their CPU names, Reaptor Lake, Alder Lake, > Rocket Lake, Tiger Lake, etc. > > Makes it hard to know which is the latest and greatest. I don't even pay > attention to the names and instead just look at the Model # which tells me > which generation it is. > > Somone said that "SlowRoll" was less desirable because of the negativeness > of "slow", how about StableRoll ? > Or SteadyRoll. And then Eric Clapton has a theme song (sort of) all ready. I agree that SlowRoll does not sound promising as a name. Pulsar is the other one that I like. -- Roger Oberholtzer

1 year, 1 month

openSUSE Factory search results for query "Slowroll"