https://en.opensuse.org/api.php?action=feedcontributions&user=Bmwiedemann&feedformat=atomopenSUSE Wiki - User contributions [en]2024-03-29T02:09:08ZUser contributionsMediaWiki 1.37.6https://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=185407openSUSE:Slowroll2024-03-27T07:12:07Z<p>Bmwiedemann: drop Tumbleweed repos</p>
<hr />
<div>== What ==<br />
<br />
[[File:OpenSUSE Slowroll green logo.svg|160x76px|links|Logo of openSUSE Slowroll]]<br />
<br />
Slowroll is a new experimental distribution from 2023 based on Tumbleweed, but rolling slower. With big updates every one or two months, and continous bug fixes and security fixes as they come in. <br />
[[File:Slowroll-vs-tumbleweed-updates.svg|thumb]]<br />
<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
http://download.opensuse.org/slowroll/iso/ but leave online repositories disabled (so it does not pull in newer Tumbleweed packages from online repos). You can also switch directly from any actual Leap or Tumbleweed release to Slowroll by replacing the repositories.<br />
<br />
After installation from DVD you need to replace Tumbleweed with Slowroll repositories. The same applies when switching from Leap or an older Tumbleweed snapshot to Slowroll.<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper rm openSUSE-repos-Tumbleweed<br />
zypper ar --refresh http://download.opensuse.org/slowroll/repo/oss/ base-oss<br />
zypper ar --refresh http://download.opensuse.org/slowroll/repo/non-oss/ base-non-oss<br />
zypper ar --refresh -p 80 http://download.opensuse.org/update/slowroll/repo/oss/ update<br />
zypper ar --refresh --disable http://download.opensuse.org/slowroll/repo/src-oss/ base-src-oss<br />
zypper ar --refresh --disable http://download.opensuse.org/debug/slowroll/repo/oss/ base-oss-debug<br />
zypper ar --refresh http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
<br />
We do not recommend using development repos and packages on top, unless those are specifically compiled for Slowroll. Third party repositories which are not tested with Tumbleweed might break your installation.<br />
<br />
Packman might work, but might also break occasionally. There is a special packman repository for Slowroll:<br />
<br />
zypper ar --refresh -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Resources ==<br />
<br />
* [https://www.reddit.com/r/openSUSE_Slowroll/ Reddit]<br />
* [https://forums.opensuse.org/tag/slowroll Forums.o.o]<br />
* [https://lists.opensuse.org/archives/search?mlist=factory%40lists.opensuse.org&q=Slowroll Mailing-list]<br />
* Bugzilla TBD<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=184879openSUSE:Slowroll2024-03-07T10:18:41Z<p>Bmwiedemann: use download.o.o as default - it will redirect to cdn where appropriate</p>
<hr />
<div>== What ==<br />
<br />
[[File:OpenSUSE Slowroll green logo.svg|160x76px|links|Logo of openSUSE Slowroll]]<br />
<br />
Slowroll is a new experimental distribution from 2023 based on Tumbleweed, but rolling slower. With big updates every one or two months, and continous bug fixes and security fixes as they come in. <br />
[[File:Slowroll-vs-tumbleweed-updates.svg|thumb]]<br />
<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
http://download.opensuse.org/slowroll/iso/ but leave online repositories disabled (so it does not pull in newer Tumbleweed packages from online repos). You can also switch directly from any actual Leap or Tumbleweed release to Slowroll by replacing the repositories.<br />
<br />
After installation from DVD you need to replace Tumbleweed with Slowroll repositories. The same applies when switching from Leap or an older Tumbleweed snapshot to Slowroll.<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar --refresh http://download.opensuse.org/slowroll/repo/oss/ base-oss<br />
zypper ar --refresh http://download.opensuse.org/slowroll/repo/non-oss/ base-non-oss<br />
zypper ar --refresh -p 80 http://download.opensuse.org/update/slowroll/repo/oss/ update<br />
zypper ar --refresh --disable http://download.opensuse.org/slowroll/repo/src-oss/ base-src-oss<br />
zypper ar --refresh --disable http://download.opensuse.org/debug/slowroll/repo/oss/ base-oss-debug<br />
zypper ar --refresh http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
<br />
We do not recommend using development repos and packages on top, unless those are specifically compiled for Slowroll. Third party repositories which are not tested with Tumbleweed might break your installation.<br />
<br />
Packman might work, but might also break occasionally. There is a special packman repository for Slowroll:<br />
<br />
zypper ar --refresh -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Resources ==<br />
<br />
* [https://www.reddit.com/r/openSUSE_Slowroll/ Reddit]<br />
* [https://forums.opensuse.org/tag/slowroll Forums.o.o]<br />
* [https://lists.opensuse.org/archives/search?mlist=factory%40lists.opensuse.org&q=Slowroll Mailing-list]<br />
* Bugzilla TBD<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Reproducible_Builds_Status&diff=184015openSUSE:Reproducible Builds Status2024-02-25T03:55:43Z<p>Bmwiedemann: init</p>
<hr />
<div>The further down an entry, the closer it is to completion (become reproducible in Factory)<br />
<br />
<pre><br />
ToDo<br />
binutils<br />
cmake CMake.qch<br />
qt6-quick3d ?parallelism https://bugreports.qt.io/browse/QTBUG-121643<br />
openssl-1_0_0 https://bugzilla.suse.com/show_bug.cgi?id=1219879 obj_dat.h<br />
crash dminfo.so parallelism<br />
app-builder minor build-id<br />
cockpit filesys (python)<br />
javadoc toolchain filesys-readdir-order: antlr4 apache-commons-csv ...<br />
openjfx filesys + minor mtime/other?<br />
cuarzo-srm filesys<br />
python-seaborn filesys low-entropy .pyc python3.9<br />
python-debugpy filesys low-entropy .pyc python3.9<br />
parboiled?<br />
scala filesys<br />
deepin-gir-generator<br />
scummvm minor<br />
python-frozenlist https://github.com/cython/cython/issues/5949 random path, toolchain random tmp path from https://github.com/sysfce2/python-frozenlist/blob/master/packaging/pep517_backend/_backend.py#L199<br />
plasma5-workspace parallelism<br />
gri ps<br />
deluge .egg zip mtime<br />
waf minor: time-based .pyc<br />
julia CPU in openblas + ordering + other = parallelism?<br />
dbus-sharp2 mono (ignored by build-compare+monodis)<br />
calibre CPU-dependent from Qt6 QImage scaler | .png files differ from SSE-4.1<br />
ceph boost b2 project-cache.jam filesys-readdir-order<br />
contrast rust/llvm<br />
dealii doxygen parallelism?<br />
deno rust zstd-sys?<br />
difftastic rust/llvm<br />
dmd parallelism + ASLR<br />
eclipse .jar files containing .jar files vary in size<br />
elixir-ex_doc<br />
gammaray .qch order<br />
ghc sphinx doctrees + ghc-9.6.3/GHC/Runtime/Interpreter.dyn_hi<br />
groovy18 order issue in .class file<br />
gstreamer-plugins-rs date ; pkgconfig .pc generation<br />
hawk2 sprockets .cache files vary for unknown reason<br />
installation-images various issues from efi + %post<br />
java-21-openjdk FTBFS-2034 = https://bugzilla.opensuse.org/show_bug.cgi?id=1213796, date<br />
jedit javadoc .html date<br />
kdevelop5-plugin-php parallelism+ASLR in libkdevphpparser.so via phpparser.cpp<br />
kernel-vanilla .vmlinuz.hmac ; Build time autogenerated kernel key0 = https://bugzilla.suse.com/show_bug.cgi?id=1187167<br />
kernel-default "<br />
ksh year in copyright ; compile time benchmarking ; SIGQUEUE_MAX detection<br />
lapce filesys-readdir-order minor<br />
lazarus <br />
ldc order x+?ASLR<br />
libaom .png, copyright year in aom_version.h<br />
libqt5-qtdoc .qhp, .qch (sqlite3), doc order<br />
mame order issue from https://github.com/mamedev/mame/pull/11651 + mame.make filesys-readdir-order from genie + other ; |(premake4 had order issues?) ; => SR 1119553<br />
nauty CPU<br />
nodejs20 v8_snapshot_blob_data varies<br />
nodejs21<br />
pass-import ASLR order issue - toolchain pandoc?<br />
pspp /usr/share/info/pspp.info-1.gz # unreproducible testsuite.log => split with _multibuild?<br />
pympress date+time from python-Babel?<br />
python-cPyparsing cpython toolchain fix in :test?<br />
python-HyperKitty variations in /srv/www/webapps/mailman/hyperkitty/static/CACHE/css/output.*.css from Django?<br />
python-mesonpep517 cpython<br />
python-pandas OBS verification fail - ?from preinstallimage?<br />
python-scikit-learn parallelism via cython+openmp - similar to https://github.com/yt-project/yt/issues/4611<br />
python-scipy ....<br />
qgis parallelism (via ninja?)<br />
qt-creator parallelism in libTracing.so.11.0.2? gone?<br />
rage-encryption rust/llvm?<br />
sad order ?from rust/llvm?<br />
scap-security-guide order<br />
sdcc 32bit epoch timestamp<br />
smlnj order + EPOCH timestamp<br />
starship 1-byte-diff in .note.ABI-tag ?from rust/llvm?<br />
stl-thumb unknown rust/llvm<br />
swipl prolog date + FTBFS-2029 + other<br />
tiny rust/llvm<br />
virtualbox copyright year ; _BUILD_STRING date+time ; tar mtime ; g_VTGObjHeader https://www.virtualbox.org/ticket/16854 + https://sourceforge.net/p/gsoap2/patches/185/<br />
warp filesys maybe https://github.com/briansmith/ring/issues/1625<br />
wpewebkit copyright year ; varying JSCBytecodeCacheVersion<br />
xemacs order in lisp/custom-load.el ; .elc ; other<br />
xemacs-packages readdir+ASLR+CPU in .elc order ; SR 1119571 partial date<br />
<br />
<br />
Analyzed:<br />
asymptote toolchain pdflatex date<br />
ginac pdflatex<br />
glucat pdflatex<br />
unison pdf from pdfTeX - cannot reproduce after 20231122?<br />
libreoffice https://lists.reproducible-builds.org/pipermail/rb-general/2023-November/003121.html various: clucene .idxl ; order ; copyright year ; records -jN <br />
openmpi5 https://github.com/open-mpi/ompi/pull/11847 date+readdir<br />
openblas cpu type in openblas.pc<br />
coq parallelism from ocaml +maybe others - same as ocaml-camlp-streams?<br />
grass https://github.com/OSGeo/grass/pull/3415 https://github.com/OSGeo/grass/pull/3417 https://github.com/OSGeo/grass/issues/3038 date+parallelism in r3.mapcalc<br />
hevea random ocaml tmp dir from ocamlopt<br />
mathgl random example .png<br />
R-base embedded random tmp path in /usr/lib64/R/library/KernSmooth/help/paths.rds; many other<br />
rabbitmq-server timestamps in zip from elixir toolchain<br />
rakudo patch-mtime + https://github.com/rakudo/rakudo/issues/5427 + #https://github.com/rakudo/rakudo/pull/5426<br />
wine timestamp in PE .dll + #https://gitlab.winehq.org/wine/wine/-/merge_requests/4035<br />
python-pytest-httpbin FTBFS SSL + other<br />
?MozillaFirefox FTBFS-j1<br />
clisp hostname + uninitialized mem dump<br />
scheme48 unreproducible scheme dump<br />
chezscheme scheme .boot files<br />
emacs .eln ASLR + .pdmp unknown issue (5+6 random bytes) https://lists.gnu.org/archive/html/emacs-devel/2024-01/msg00464.html<br />
maxima clisp .mem dump<br />
pgloader from sbcl (lisp dump)<br />
scsh totally unreproducible scheme image dump<br />
spack parallelism https://github.com/spack/spack/pull/36064<br />
racket various issues - unknown source - scheme dump<br />
xindy xindy.mem CLISP memory image data dump<br />
<br />
python-numba toolchain:<br />
python-iminuit numba toolchain<br />
python-librosa numba toolchain<br />
python-xarray-einstats numba toolchain<br />
<br />
<br />
https://trello.com/c/lXGJn6Wf/44-ghostscript<br />
gfan<br />
LiE<br />
lout<br />
pnetcdf<br />
srecord<br />
<br />
<br />
reported in openSUSE:<br />
python-mpi4py https://bugzilla.suse.com/show_bug.cgi?id=1212698 from gcc?<br />
tycho + eclipse-jgit https://github.com/openSUSE/build-compare/issues/65 bogus<br />
mozilla-nss https://bugzilla.opensuse.org/show_bug.cgi?id=1081723 DSA sig<br />
wsl-appx https://bugzilla.opensuse.org/show_bug.cgi?id=1189698 verification failure - publisher from OBS ssl cert<br />
libguestfs https://bugzilla.opensuse.org/show_bug.cgi?id=1216986 embeds host /etc/hosts in supermin.d/base.tar.gz<br />
python-numpy https://bugzilla.opensuse.org/show_bug.cgi?id=1216458 random file names<br />
libkolabxml https://bugzilla.opensuse.org/show_bug.cgi?id=1060506 ASLR/CPU order-issue in xsdbin ; partially workarounded?<br />
grub2 https://bugzilla.opensuse.org/show_bug.cgi?id=1217967 https://bugzilla.opensuse.org/show_bug.cgi?id=1217619 grub.xen tar mtime + (parallelism?) + filesys-readdir-order(from grub_util_fd_readdir) + octal UNIX timestamp from grub-mkstandalone | grub-mkimage<br />
ovmf https://bugzilla.opensuse.org/show_bug.cgi?id=1217704 ovmf-riscv64-code.bin<br />
qt6-webengine https://bugzilla.opensuse.org/show_bug.cgi?id=1217774 qtpdf.index parallelism<br />
libcamera https://bugzilla.opensuse.org/show_bug.cgi?id=1217690 random: private key signatures of modules<br />
elixir https://bugzilla.opensuse.org/show_bug.cgi?id=1205134 FTBFS-j1 stuck<br />
llvm13 https://bugzilla.opensuse.org/show_bug.cgi?id=1195427 ASLR<br />
<br />
python310 https://bugzilla.opensuse.org/show_bug.cgi?id=1040589 - improvable<br />
python311<br />
python312<br />
python38<br />
python39<br />
gcc12<br />
bash<br />
<br />
<br />
reported upstream:<br />
llvm11-17 https://bugzilla.opensuse.org/show_bug.cgi?id=1199076<br />
llvm17/rust1.73 https://github.com/llvm/llvm-project/issues/72206 <br />
<br />
efl https://git.enlightenment.org/enlightenment/efl/issues/41 parallelism<br />
enlightenment-theme-dark<br />
enlightenment-theme-openSUSE<br />
enlightenment-theme-openSUSE-ice<br />
enlightenment-theme-openSUSE-neon<br />
enlightenment-theme-openSUSE-oliveleaf<br />
<br />
libpinyin https://github.com/libpinyin/libpinyin/issues/162<br />
fcitx5-zhuyin<br />
fcitx-libpinyin<br />
ibus-libzhuyin<br />
<br />
kubernetes1.24 https://github.com/golang/go/issues/63851 = https://github.com/kubernetes/kubernetes/issues/110928<br />
kubernetes1.25<br />
kubernetes1.26<br />
kubernetes1.27<br />
<br />
https://github.com/mono/mono/issues/20172 report unknown/time-based nondeterminism<br />
keepass<br />
mono-addins<br />
mono-core<br />
nunit<br />
flickrnet mono PE-header-timestamp, 1024-bit ?PublicKeyToken?, other ; ignored by build-compare+monodis<br />
<br />
https://github.com/sphinx-doc/sphinx/issues/2946 = https://github.com/sphinx-doc/sphinx/issues/6714 ; workaroundable<br />
kernel-docs<br />
<br />
(also guake, qemu listed elsewhere (already fixed in Factory))<br />
<br />
ocaml-camlp-streams https://github.com/ocaml/dune/issues/9152 https://github.com/ocaml/camlp-streams/issues/9<br />
ocaml-extlib<br />
<br />
release-notes-openSUSE https://github.com/apache/xmlgraphics-fop/pull/65 TODO<br />
gsequencer "<br />
bibletime "<br />
pam .pdf from fop<br />
erlang " and other issues<br />
<br />
gegl https://gitlab.gnome.org/GNOME/gegl/-/issues/337 parallelism, memory<br />
postfish/fftw3 https://github.com/FFTW/fftw3/issues/337<br />
sbcl https://sourceforge.net/p/sbcl/mailman/sbcl-devel/thread/3ebdd95c-c498-462f-9cfe-7d05a1ee0044%40suse.de/ report timestamp+other<br />
<br />
lilypond https://sourceforge.net/p/testlilyissues/issues/5328/ https://savannah.gnu.org/patch/?9370 https://codereview.appspot.com/337650043<br />
python-yt https://github.com/yt-project/yt/issues/4611 parallelism +#=> https://github.com/yt-project/yt/pull/4609 python filesys order<br />
wrk https://github.com/wg/wrk/issues/507 hash order issue<br />
python3-pyside6 ASLR order from shiboken6<br />
python3-pyside2 https://bugreports.qt.io/browse/PYSIDE-2508 order<br />
rash https://github.com/willghatch/racket-rash/issues/52 report parallelism-related non-determinism<br />
gnu-cobol https://savannah.gnu.org/bugs/index.php?54361 https://bugzilla.opensuse.org/show_bug.cgi?id=1195087<br />
bcc order in bcc-lua from toolchain luajit https://github.com/LuaJIT/LuaJIT/issues/1008<br />
boost https://github.com/boostorg/boost/issues/741 2038-date influences order in libboost_log.so.1.82.0<br />
joker https://github.com/candid82/joker/issues/491 hash random order # https://github.com/candid82/joker/pull/490 sort, partial<br />
colord https://github.com/omgovich/colord/issues/122 https://bugzilla.opensuse.org/show_bug.cgi?id=1217747 .icc only-CPU<br />
neovim https://github.com/neovim/neovim/issues/26387 order issue maybe from gen_api_dispatch.lua<br />
glfw https://github.com/geany/geany/issues/3717 toolchain geany glfw.c.tags<br />
<br />
soapy-sdr https://github.com/pothosware/SoapySDR/issues/428 parallelism<br />
qt6-virtualkeyboard qt6-declarative https://bugreports.qt.io/browse/QTBUG-121643 bug? parallelism<br />
<br />
<br />
fix submitted upstream:<br />
mage https://github.com/magefile/mage/pull/474<br />
rpm + obs-build https://bugzilla.opensuse.org/show_bug.cgi?id=1206816 https://github.com/rpm-software-management/rpm/pull/2762 https://github.com/rpm-software-management/rpm/issues/2343 + https://github.com/openSUSE/obs-build/blob/1fe25db/build-recipe#L259 toolchain ; TODO<br />
nfdump https://github.com/phaag/nfdump/pull/482 date<br />
kernel-obs-build patch per mail - initrd cpio varies in /etc/hosts from build machine hostname<br />
pommed https://salsa.debian.org/mactel-team/pommed/-/merge_requests/2 parallelism<br />
<br />
<br />
fix merged upstream:<br />
python-grpcio https://github.com/grpc/grpc/pull/35687 sort filesys<br />
kraft https://github.com/dragotin/kraft/pull/215 hostname<br />
gap https://github.com/gap-system/gap/pull/5551 https://github.com/gap-system/gap/pull/5550 date<br />
rehex https://github.com/solemnwarning/rehex/pull/221 zip mtime >0.60.1<br />
ooRexx https://sourceforge.net/p/oorexx/bugs/1712/ ASLR ; fixed in 5.0.0?<br />
OpenRGB https://gitlab.com/CalcProgrammer1/OpenRGB/-/merge_requests/2103 filesys >0.9<br />
orthanc-volview https://orthanc.uclouvain.be/hg/orthanc-ohif/rev/154cb76a042f after 2023-08<br />
qpid-proton https://github.com/apache/qpid-proton/pull/411 sort >0.39<br />
goldendict-ng https://bugreports.qt.io/browse/QTBUG-115737 qmake toolchain ; also rewritten in goldendict-ng >23.05.03<br />
librcc https://github.com/RusXMMS/librcc/pull/5 date >0.2.13<br />
maildir-utils https://github.com/djcb/mu/issues/2570 >=1.11<br />
intel-graphics-compiler https://github.com/intel/intel-graphics-compiler/issues/302 https://github.com/intel/intel-graphics-compiler/commit/4354d0bb3b8d1cd436b6601327c076abfcf9d2ff 20231025+<br />
git-interactive-rebase-tool https://github.com/MitMaro/git-interactive-rebase-tool/pull/881 >2.3.0<br />
kopete https://invent.kde.org/network/kopete/-/merge_requests/14<br />
buildah https://github.com/containers/buildah/issues/5191 timestamp 4 byte EPOCH vary in github.com/containers/buildah/internal/mkcw..gobytes.1<br />
whatsie https://github.com/keshavbhatt/whatsie/pull/146 date (needs qmake patch)<br />
osc https://github.com/openSUSE/osc/pull/1454 build-jobs captured in man-page<br />
shadowsocks-rust https://github.com/AlephAlpha/build-time/pull/5 date+time<br />
meson https://github.com/mesonbuild/meson/pull/12528 toolchain, sort >=1.3.1<br />
lagrange https://codeberg.org/skyjake/lagrange/pulls/3 zip mtime<br />
Setzer https://github.com/mesonbuild/meson/pull/12788 filesys / meson toolchain<br />
systemd https://github.com/systemd/systemd/pull/31080 sort filesys<br />
presenterm https://github.com/mfontanini/presenterm/pull/202 filesys (rust)<br />
ocaml-dune https://github.com/ocaml/dune/issues/9794 filesys ; merged: https://github.com/ocaml/dune/pull/9735 https://github.com/ocaml/dune/issues/9507 parallelism >= 3.14<br />
<br />
<br />
SR:<br />
-1119524 occt sort (not upstream)<br />
.1139511 1133453 1121011 qemu parallelism-issue from sphinx ; + https://gitlab.com/qemu-project/SLOF/-/merge_requests/1 date + #https://github.com/openSUSE/qemu/pull/44 hostname<br />
1144993 grub2 filesys in grub.efi<br />
<br />
<br />
Done:<br />
#1130635 1130399 python-efl Spinx doctrees pickle<br />
#1119096 kanku https://github.com/maros/MooseX-App/pull/71 toolchain, date from perl-MooseX-App => SR 1119096<br />
#1108744 siproxd https://build.opensuse.org/request/show/1108744<br />
#1117880 deepin-desktop-schemas<br />
#1117898 python-quantities date<br />
#1123416 openblas cpu count (orig SR 1118201)<br />
#1124071 1123507 1118130 spack https://github.com/spack/spack/pull/36064 parallelism ; solved differently upstream<br />
#1121668 ghc* https://github.com/opensuse-haskell/ghc-rpm-macros/pull/1 toolchain >2.5.3<br />
#1124263 kitty https://github.com/kovidgoyal/kitty/pull/6685 sort+mtime >0.30.1<br />
#1123597 spotifyd https://github.com/Spotifyd/spotifyd/issues/1167 fixed in 0.3.5<br />
#1120220 selinux-policy/policycoreutils https://bugzilla.opensuse.org/show_bug.cgi?id=1216452 toolchain, order issues in /usr/share/selinux/devel/html/index.html<br />
#1127255 google-noto-fonts https://github.com/notofonts/Arimo/pull/17 downstream patch fix caused mtime to creep into build results<br />
#1127661 xen date+time<br />
#1125191 amber-cli date<br />
#1127547 guake parallelism/race<br />
#1129136 ipxe https://github.com/ipxe/ipxe/pull/1082 .sdsk random from mtools init_random(time)<br />
#1129609 pcp varying HAVE_MEMORY_H<br />
? groff time in .pdf<br />
#apache-arrow https://github.com/apache/arrow/issues/37276 FTBFS-j1<br />
#1129751 fdo-client https://bugzilla.opensuse.org/show_bug.cgi?id=1216293 private key<br />
#1127368 guile-fibers parallelism https://issues.guix.gnu.org/issue/20272 https://bugzilla.opensuse.org/show_bug.cgi?id=1170378<br />
#1127367 guile-newt parallelism<br />
#1130552 procmail benchmarking<br />
#1130719 1129495 1129303 quazip missing fonts quazip .png - toolchain random from doxygen->dot<br />
#1129040 tigervnc drop RSA-signature https://bugzilla.opensuse.org/show_bug.cgi?id=1208478 tigervnc RSA key<br />
#1130500 1128769 gutenprint date+hostname https://sourceforge.net/p/gimp-print/source/merge-requests/9/ date >5.3.4<br />
#1132004 1131679 python-pyface time = https://github.com/enthought/pyface/issues/1254<br />
#1135210 1134362 xemacs toolchain gnugo+uim hostname<br />
#1132811 python-rdflib https://github.com/RDFLib/rdflib/issues/2645 random Graph identifier ?toolchain from python-Sphinx?<br />
#1132690 1132599 python-yarl https://github.com/cython/cython/issues/5949 cpython random path - regression in 1.9.3<br />
#1136570 orthanc-ohif https://orthanc.uclouvain.be/hg/orthanc-ohif/rev/154cb76a042f 1.1 after 2023-08<br />
#1137474 python-rjsmin drop gcc instrumentation<br />
#1140578 doxygen toolchain libzypp+wxWidgets-3_2:doc filesys clhep<br />
#1138193 1138082 libjcat https://bugzilla.opensuse.org/show_bug.cgi?id=1218715 random/crypto<br />
#1141433 mumble https://github.com/mumble-voip/mumble/pull/6147 filesys >1.5.517<br />
#1137333 warewulf https://bugzilla.opensuse.org/show_bug.cgi?id=1217973 cpio mtime + inode<br />
#1137377 hub https://github.com/mislav/hub/pull/3344 random<br />
<br />
<br />
obsolete:<br />
go1.13 parallelism<br />
go1.14 parallelism<br />
go1.15 parallelism<br />
java-11-openj9<br />
java-1_8_0-openjdk<br />
<br />
WONTFIX:<br />
rpm-config-SUSE<br />
update-test-trivial<br />
</pre></div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=183733openSUSE:Slowroll2024-02-15T06:51:50Z<p>Bmwiedemann: add links</p>
<hr />
<div>== What ==<br />
<br />
[[File:OpenSUSE Slowroll green logo.svg|160x76px|links|Logo of openSUSE Slowroll]]<br />
<br />
Slowroll is a new experimental distribution from 2023 based on Tumbleweed, but rolling slower. With big updates every one or two months, and continous bug fixes and security fixes as they come in. <br />
[[File:Slowroll-vs-tumbleweed-updates.svg|thumb]]<br />
<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
http://download.opensuse.org/slowroll/iso/ but leave online repositories disabled (so it does not pull in newer Tumbleweed packages from online repos).<br />
<br />
After installation from DVD you need to replace Tumbleweed with Slowroll repositories. The same applies when switching from Leap or an older Tumbleweed snapshot to Slowroll.<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar --refresh http://cdn.opensuse.org/slowroll/repo/oss/ base-oss<br />
zypper ar --refresh http://cdn.opensuse.org/slowroll/repo/non-oss/ base-non-oss<br />
zypper ar --refresh -p 80 http://cdn.opensuse.org/update/slowroll/repo/oss/ update<br />
zypper ar --refresh --disable http://cdn.opensuse.org/slowroll/repo/src-oss/ base-src-oss<br />
zypper ar --refresh --disable https://download.opensuse.org/debug/slowroll/repo/oss/ base-oss-debug<br />
zypper ar --refresh http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
zypper ar --refresh -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally. This can also apply to the third party repositories which are not tested with Tumbleweed.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Resources ==<br />
<br />
* [https://www.reddit.com/r/openSUSE_Slowroll/ Reddit]<br />
* [https://forums.opensuse.org/tag/slowroll Forums.o.o]<br />
* [https://lists.opensuse.org/archives/search?mlist=factory%40lists.opensuse.org&q=Slowroll Mailing-list]<br />
* Bugzilla TBD<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Post-mortem-20240105&diff=183196openSUSE:Post-mortem-202401052024-01-05T14:37:22Z<p>Bmwiedemann: update ipa fix</p>
<hr />
<div>* What/Problem: various openSUSE services were disfunctional (wiki, etherpad, management-VPN)<br />
* When: 2024-01-05 01:30 to 09:01 UTC<br />
* Why: We identified a number of contributing issues: <br />
** autoupdates run at night when nobody is around to fix breakages<br />
*** updateos [https://progress.opensuse.org/issues/153160 config got reverted] - [https://build.opensuse.org/request/show/1137024 fixed]<br />
** freeipa service start issue from https://en.opensuse.org/openSUSE:Post-mortem-20231122 - now fixed via an adapted ipa.service<br />
** matrix nginx failed to start when DNS was not yet available</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Post-mortem-20240105&diff=183193openSUSE:Post-mortem-202401052024-01-05T12:51:48Z<p>Bmwiedemann: +link</p>
<hr />
<div>* What/Problem: various openSUSE services were disfunctional (wiki, etherpad, management-VPN)<br />
* When: 2024-01-05 01:30 to 09:01 UTC<br />
* Why: We identified a number of contributing issues: <br />
** autoupdates run at night when nobody is around to fix breakages<br />
*** updateos [https://progress.opensuse.org/issues/153160 config got reverted] - [https://build.opensuse.org/request/show/1137024 fixed]<br />
** freeipa service start issue from https://en.opensuse.org/openSUSE:Post-mortem-20231122 - now fixed via a new freeipa.service<br />
** matrix nginx failed to start when DNS was not yet available</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Post-mortem-20240105&diff=183190openSUSE:Post-mortem-202401052024-01-05T12:49:49Z<p>Bmwiedemann: formatting</p>
<hr />
<div>* What/Problem: various openSUSE services were disfunctional (wiki, etherpad, management-VPN)<br />
* When: 2024-01-05 01:30 to 09:01 UTC<br />
* Why: We identified a number of contributing issues: <br />
** autoupdates run at night when nobody is around to fix breakages<br />
*** updateos config got reverted - [https://build.opensuse.org/request/show/1137024 fixed]<br />
** freeipa service start issue from https://en.opensuse.org/openSUSE:Post-mortem-20231122 - now fixed via a new freeipa.service<br />
** matrix nginx failed to start when DNS was not yet available</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Post-mortem-20240105&diff=183187openSUSE:Post-mortem-202401052024-01-05T12:48:53Z<p>Bmwiedemann: init</p>
<hr />
<div>What/Problem: various openSUSE services were disfunctional (wiki, etherpad, management-VPN)<br />
When: 2024-01-05 01:30 to 09:01 UTC<br />
Why: We identified a number of contributing issues: <br />
<br />
* autoupdates run at night when nobody is around to fix breakages<br />
** updateos config got reverted - [https://build.opensuse.org/request/show/1137024 fixed]<br />
* freeipa service start issue from https://en.opensuse.org/openSUSE:Post-mortem-20231122 - now fixed via a new freeipa.service<br />
* matrix nginx failed to start when DNS was not yet available</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=183101openSUSE:Slowroll2023-12-22T14:40:07Z<p>Bmwiedemann: +debug repo</p>
<hr />
<div>== What ==<br />
<br />
[[File:OpenSUSE Slowroll green logo.svg|160x76px|links|Logo of openSUSE Slowroll]]<br />
<br />
Slowroll is a new experimental distribution from 2023 based on Tumbleweed, but rolling slower. With big updates every one or two months, and continous bug fixes and security fixes as they come in. <br />
[[File:Slowroll-vs-tumbleweed-updates.svg|thumb]]<br />
<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
http://download.opensuse.org/slowroll/iso/ but leave online repositories disabled (so it does not pull in newer Tumbleweed packages from online repos).<br />
<br />
After installation from DVD you need to replace Tumbleweed with Slowroll repositories. The same applies when switching from Leap or an older Tumbleweed snapshot to Slowroll.<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar --refresh http://cdn.opensuse.org/slowroll/repo/oss/ base-oss<br />
zypper ar --refresh http://cdn.opensuse.org/slowroll/repo/non-oss/ base-non-oss<br />
zypper ar --refresh -p 80 http://cdn.opensuse.org/update/slowroll/repo/oss/ update<br />
zypper ar --refresh --disable http://cdn.opensuse.org/slowroll/repo/src-oss/ base-src-oss<br />
zypper ar --refresh --disable https://download.opensuse.org/debug/slowroll/repo/oss/ base-oss-debug<br />
zypper ar --refresh http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
zypper ar --refresh -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=File:Usecase2023-usecases.svg&diff=182935File:Usecase2023-usecases.svg2023-12-17T15:09:59Z<p>Bmwiedemann: Bmwiedemann uploaded a new version of File:Usecase2023-usecases.svg</p>
<hr />
<div>== Summary ==<br />
made with libreoffice-calc -> draw -> inkscape</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=File:Usecase2023-usecases.svg&diff=182933File:Usecase2023-usecases.svg2023-12-17T15:05:26Z<p>Bmwiedemann: Bmwiedemann uploaded a new version of File:Usecase2023-usecases.svg</p>
<hr />
<div>== Summary ==<br />
made with libreoffice-calc -> draw -> inkscape</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Post-mortem-20231122&diff=182231openSUSE:Post-mortem-202311222023-11-23T08:38:17Z<p>Bmwiedemann: init</p>
<hr />
<div>* What/Problem: various openSUSE services were disfunctional (wiki, etherpad, management-VPN)<br />
* When: 2023-11-22 00:50 to 13:00 UTC<br />
* Why: We identified a number of contributing issues:<br />
** autoupdates run at night when nobody is around to fix breakages (Georg was around, but his home internet broke, so he went to bed)<br />
** https://bugzilla.opensuse.org/show_bug.cgi?id=1217403 virtlockd stopped VMs after auto-update<br />
*** proposed solution: https://github.com/openSUSE/os-update/pull/17<br />
** galera DB disintegrated when all its 3 VMs were restarted due to the virtlockd issue<br />
*** galera had a missing sst_user, causing cluster recovery to fail<br />
*** ulimit restrictions caused recovery debugging to fail<br />
*** existing data directories on consumer nodes caused recovery to fail<br />
** freeipa had no network after reboot - fixed<br />
*** freeipa had no slapd running after reboot - '''TBD'''<br />
*** without freeipa, no openVPN-access was possible<br />
** The VM host that provides remote-access without heroes-openVPN did not have autostart enabled for important VMs - fixed<br />
** openVPN gateway had missing ip-forward config applied from salt - fixed<br />
** The network is tightly firewalled, so no ssh access from other places was possible - '''TBD''' fallback entrypoint still needs to be set up</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=181741openSUSE:Slowroll2023-11-20T15:36:17Z<p>Bmwiedemann: update more OBS locations</p>
<hr />
<div>== What ==<br />
<br />
[[File:OpenSUSE Slowroll green logo.svg|160x76px|links|Logo of openSUSE Slowroll]]<br />
<br />
Slowroll is a new experimental distribution from 2023 based on Tumbleweed, but rolling slower. With big updates every one or two months, and continous bug fixes and security fixes as they come in. <br />
[[File:Slowroll-vs-tumbleweed-updates.svg|thumb]]<br />
<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
http://download.opensuse.org/slowroll/iso/ but leave online repositories disabled (so it does not pull in newer Tumbleweed packages from online repos).<br />
<br />
After installation from DVD you need to replace Tumbleweed with Slowroll repositories. The same applies when switching from Leap or an older Tumbleweed snapshot to Slowroll.<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar --refresh http://cdn.opensuse.org/slowroll/repo/oss/ base-oss<br />
zypper ar --refresh http://cdn.opensuse.org/slowroll/repo/non-oss/ base-non-oss<br />
zypper ar --refresh -p 80 http://cdn.opensuse.org/update/slowroll/repo/oss/ update<br />
zypper ar --refresh --disable http://cdn.opensuse.org/slowroll/repo/src-oss/ base-src-oss<br />
zypper ar --refresh http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
zypper ar --refresh -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
20th November, 2023: Please note the comment from the Packman Administrator <https://lists.links2linux.de/pipermail/packman/2023-November/017648.html> about edge cases.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=181738openSUSE:Slowroll2023-11-20T15:34:29Z<p>Bmwiedemann: update repo locations</p>
<hr />
<div>== What ==<br />
<br />
[[File:OpenSUSE Slowroll green logo.svg|160x76px|links|Logo of openSUSE Slowroll]]<br />
<br />
Slowroll is a new experimental distribution from 2023 based on Tumbleweed, but rolling slower. With big updates every one or two months, and continous bug fixes and security fixes as they come in. <br />
[[File:Slowroll-vs-tumbleweed-updates.svg|thumb]]<br />
<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
http://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/ but leave online repositories disabled (so it does not pull in newer Tumbleweed packages from online repos).<br />
<br />
After installation from DVD you need to replace Tumbleweed with Slowroll repositories. The same applies when switching from Leap or an older Tumbleweed snapshot to Slowroll.<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar --refresh http://cdn.opensuse.org/slowroll/repo/oss/ base-oss<br />
zypper ar --refresh http://cdn.opensuse.org/slowroll/repo/non-oss/ base-non-oss<br />
zypper ar --refresh -p 80 http://cdn.opensuse.org/update/slowroll/repo/oss/ update<br />
zypper ar --refresh --disable http://cdn.opensuse.org/slowroll/repo/src-oss/ base-src-oss<br />
zypper ar --refresh http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
zypper ar --refresh -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
20th November, 2023: Please note the comment from the Packman Administrator <https://lists.links2linux.de/pipermail/packman/2023-November/017648.html> about edge cases.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Reproducible_openSUSE&diff=181625openSUSE:Reproducible openSUSE2023-11-17T00:34:20Z<p>Bmwiedemann: +section headings +optional goals</p>
<hr />
<div>Bernhard M. Wiedemann has been testing [[openSUSE:Reproducible Builds|reproducible builds of openSUSE distributions]] since 2016. In this process he already produced over 1000 patches and bugreports.<br />
<br />
== What ==<br />
Now it is time to create a general-purpose Linux distribution from it, that consists of 100% bit-reproducible packages (minus the rpm signature).<br />
It shall be based on [[Portal:Tumbleweed|openSUSE Tumbleweed]] or its [[openSUSE:Slowroll|Slowroll-variant]] (if available).<br />
<br />
== How ==<br />
<br />
To get there, we have to review the remaining (approx 130) packages and either drop them or fix or workaround issues. Fixing can be quite some effort as most of the easy patches have already been done.<br />
<br />
Bugfixes will be sent upstream wherever possible, to ensure long-term viability.<br />
<br />
The few remaining unreproducible leaf packages may live in an extra repo that is disabled by default.<br />
<br />
It might be possible some day to get all of the required changes into the openSUSE Tumbleweed distribution to make the extra project obsolete.<br />
<br />
== Optional Goals ==<br />
<br />
* provide bit-reproducible images (install, VM)<br />
* self-hosting = everything in Reproducible-openSUSE can be reproduced using the code that is in Reproducible-openSUSE</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Reproducible_openSUSE&diff=181601openSUSE:Reproducible openSUSE2023-11-16T14:04:48Z<p>Bmwiedemann: add links</p>
<hr />
<div>Bernhard M. Wiedemann has been testing [[openSUSE:Reproducible Builds|reproducible builds of openSUSE distributions]] since 2016. In this process he already produced over 1000 patches and bugreports.<br />
<br />
Now it is time to create a general-purpose Linux distribution from it, that consists of 100% bit-reproducible packages (minus the rpm signature).<br />
It shall be based on [[Portal:Tumbleweed|openSUSE Tumbleweed]] or its [[openSUSE:Slowroll|Slowroll-variant]] (if available).<br />
<br />
To get there, we have to review the remaining (approx 130) packages and either drop them or fix or workaround issues. Fixing can be quite some effort as most of the easy patches have already been done.<br />
<br />
Bugfixes will be sent upstream wherever possible, to ensure long-term viability.<br />
<br />
The few remaining unreproducible leaf packages may live in an extra repo that is disabled by default.<br />
<br />
It might be possible some day to get all of the required changes into the openSUSE Tumbleweed distribution to make the extra project obsolete.</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Reproducible_openSUSE&diff=181550openSUSE:Reproducible openSUSE2023-11-16T11:23:24Z<p>Bmwiedemann: init</p>
<hr />
<div>Bernhard M. Wiedemann has been testing reproducible builds of openSUSE distributions [[openSUSE:Reproducible_Builds]] since 2016. In this process he produced over 1000 patches and bugreports.<br />
<br />
Now it is time to create a distribution from it, that consists of 100% bit-reproducible packages (minus the rpm signature).<br />
It shall be based on openSUSE Tumbleweed or its Slowroll-variant (if available).<br />
<br />
To get there, we have to review the remaining 130 packages and either drop them or fix or workaround issues.<br />
<br />
Bugfixes will be sent upstream whereever possible, to ensure long-term viability.<br />
<br />
The few remaining unreproducible leaf packages may live in an extra repo that is disabled by default.<br />
<br />
It might be possible some day to get all of the required changes into the openSUSE Tumbleweed distribution to make the extra project obsolete.</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=File:Usecase2023-usecases.svg&diff=181136File:Usecase2023-usecases.svg2023-11-06T12:26:10Z<p>Bmwiedemann: Bmwiedemann uploaded a new version of File:Usecase2023-usecases.svg</p>
<hr />
<div>== Summary ==<br />
made with libreoffice-calc -> draw -> inkscape</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=Usecase2023&diff=181133Usecase20232023-11-06T12:22:37Z<p>Bmwiedemann: add usecases graphic</p>
<hr />
<div>The following is a summary of the use case survey run by openSUSE during the month of October 2023. The full results are listed in the [[File:Usecase2023.pdf|Use Case 2023 report]].<br />
<br />
= Intro Questions: Results =<br />
<br />
=== What best describes your use of IT? ===<br />
Work/business (SQ001) 146 9.24%<br />
Home/Hobby (SQ002) 450 28.48%<br />
Both (SQ003) 656 41.52%<br />
No answer 21 1.33%<br />
Not completed or Not displayed 307 19.43%<br />
<br />
== Summary ==<br />
<br />
A recent survey provides a breakdown of the use cases of Linux among respondents based on their primary use of IT:<br />
<br />
[[File:Usecase2023-use-of-IT.svg]]<br />
<br />
* Work/Business: 9.24% of respondents primarily use Linux for work or business-related purposes.<br />
* Home/Hobby: 28.48% of respondents use Linux for home or hobby activities.<br />
* Both: 41.52% of respondents use Linux for both work/business and home/hobby purposes.<br />
* No answer: 1.33% of respondents did not provide an answer regarding their IT use.<br />
* Not completed or not displayed: 19.43% of respondents' information was not completed or displayed.<br />
<br />
The survey also assessed the use of various IT technologies on a scale of 1 to 5 (1 meaning little use and 5 being primary use) across different domains:<br />
[[File:Usecase2023-usecases.svg]]<br />
<br />
* Cloud Computing: Most respondents (41.70%) rated their use of Linux for cloud computing as 1 (little use), while a significant portion (13.51%) rated it as 5 (primary use).<br />
* Containerization: 34.68% rated their use of containerization as 1 (little use), and 13.84% rated it as 5 (primary use).<br />
* Configuration Management: 30.53% rated their use of configuration management as 1 (little use), and 27.17% rated it as 5 (primary use).<br />
* Desktop Computing: 81.22% of respondents primarily use Linux for desktop computing (rated 5), while only a small portion (3.27%) rated it as 1 (little use).<br />
* Server Infrastructure: 26.53% rated their use of Linux for server infrastructure as 5 (primary use), and 29.95% rated it as 1 (little use).<br />
* Serverless Computing: 64.34% primarily use Linux for serverless computing (rated 5), while 12.49% rated it as 5 (primary use).<br />
* Virtualization: 20.20% rated their use of Linux for virtualization as 5 (primary use), and 23.04% rated it as 1 (little use).<br />
* Edge Computing: 68.36% primarily use Linux for edge computing (rated 5), while 3.76% rated it as 5 (primary use).<br />
* IoT Applications: 64.95% primarily use Linux for IoT applications (rated 5), and 4.54% rated it as 5 (primary use).<br />
* Machine Learning: 68.64% primarily use Linux for machine learning (rated 5), and 4.19% rated it as 5 (primary use).<br />
* Blockchain: A significant majority (89.00%) of respondents indicated little use of Linux for blockchain (rated 1).<br />
* Gaming: 31.04% primarily use Linux for gaming (rated 5), and 25.58% rated it as 1 (little use).<br />
* Other: For other use cases, 28.88% primarily use Linux (rated 5), and 24.67% rated it as 1 (little use).<br />
<br />
Please note that these percentages represent the distribution of responses among the survey participants.<br />
<br />
=== Cloud computing ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 460 41.70% 58.20%<br />
2 (2) 182 16.50%<br />
3 (3) 192 17.41% 17.41%<br />
4 (4) 120 10.88%<br />
5 (5) 149 13.51% 24.39%<br />
No answer 170 10.76% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Containerization ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 386 34.68% 52.83%<br />
2 (2) 202 18.15%<br />
3 (3) 193 17.34% 17.34%<br />
4 (4) 178 15.99%<br />
5 (5) 154 13.84% 29.83%<br />
No answer 160 10.13% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Configuration Management ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 327 30.53% 50.61%<br />
2 (2) 215 20.07%<br />
3 (3) 238 22.22% 22.22%<br />
4 (4) 164 15.31%<br />
5 (5) 127 11.86% 27.17%<br />
No answer 202 12.78% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Desktop Computing ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 40 3.27% 4.65%<br />
2 (2) 17 1.39%<br />
3 (3) 63 5.14% 5.14%<br />
4 (4) 110 8.98%<br />
5 (5) 995 81.22% 90.20%<br />
No answer 48 3.04% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Server Infrastructure ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 333 29.95% 43.79%<br />
2 (2) 154 13.85%<br />
3 (3) 188 16.91% 16.91%<br />
4 (4) 142 12.77%<br />
5 (5) 295 26.53% 39.30%<br />
No answer 161 10.19% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Serverless Computing ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 608 64.34% 76.61%<br />
2 (2) 116 12.28%<br />
3 (3) 103 10.90% 10.90%<br />
4 (4) 54 5.71%<br />
5 (5) 64 6.77% 12.49%<br />
No answer 328 20.76% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Virtualization ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 259 23.04% 39.95%<br />
2 (2) 190 16.90%<br />
3 (3) 238 21.17% 21.17%<br />
4 (4) 210 18.68%<br />
5 (5) 227 20.20% 38.88%<br />
No answer 149 9.43% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Edge Computing ===<br />
Rate your use of IT 1 through 5? (1 meaning litttle use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 618 68.36% 80.09%<br />
2 (2) 106 11.73%<br />
3 (3) 90 9.96% 9.96%<br />
4 (4) 56 6.19%<br />
5 (5) 34 3.76% 9.96%<br />
No answer 369 23.35% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== IoT Applications ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 630 64.95% 81.24%<br />
2 (2) 158 16.29%<br />
3 (3) 93 9.59% 9.59%<br />
4 (4) 45 4.64%<br />
5 (5) 44 4.54% 9.18%<br />
No answer 303 19.18% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Machine Learning ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 672 68.64% 81.92%<br />
2 (2) 130 13.28%<br />
3 (3) 89 9.09% 9.09%<br />
4 (4) 47 4.80%<br />
5 (5) 41 4.19% 8.99%<br />
No answer 294 18.61% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Blockchain ===<br />
Rate your use of IT 1 through 5? (1 meaning litttle use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 833 89.00% 94.98%<br />
2 (2) 56 5.98%<br />
3 (3) 28 2.99% 2.99%<br />
4 (4) 9 0.96%<br />
5 (5) 10 1.07% 2.03%<br />
No answer 337 21.33% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Gaming ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 286 25.58% 36.40%<br />
2 (2) 121 10.82%<br />
3 (3) 180 16.10% 16.10%<br />
4 (4) 184 16.46%<br />
5 (5) 347 31.04% 47.50%<br />
No answer 155 9.81% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Other ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 170 24.67% 31.93%<br />
2 (2) 50 7.26%<br />
3 (3) 184 26.71% 26.71%<br />
4 (4) 86 12.48%<br />
5 (5) 199 28.88% 41.36%<br />
No answer 584 36.96% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
= Distro Use Cases =<br />
<br />
What did people say the use cases are for the following distros.<br />
<br />
=== Tumbleweed ===<br />
The use cases for openSUSE Tumbleweed are diverse and cover a wide range of activities. Users rely on Tumbleweed for internet browsing, programming, note-taking, music listening, and even gaming. It serves as a daily driver for many, including office applications and software development. Tumbleweed is used on both servers and desktops, and some users appreciate its continuous rolling updates and cutting-edge features. It's employed for testing purposes, container environments, and experimental features. For many, Tumbleweed is their main operating system, offering a combination of stability and the latest software. It is a preferred choice for development, multimedia, and daily personal tasks, including watching videos and listening to music. In summary, openSUSE Tumbleweed caters to a broad spectrum of users, from developers to gamers, offering a rolling release experience with a focus on keeping software up to date and stable.<br />
<br />
=== Leap ===<br />
openSUSE Leap serves a variety of purposes for its users. It is utilized for tasks like club finance management, personal finance management, photography archive and management, document production, and family communication. Some users rely on it as a stable and reliable system for both desktop and server needs. It's commonly used as a home server, NAS, and for various server applications.<br />
openSUSE Leap is praised for its stability, bulletproof performance, and reliability, making it an excellent choice for server-related tasks. Some users appreciate the fact that it doesn't require constant upgrades and provides a consistent interface throughout its supported lifespan.<br />
<br />
On the desktop side, it's used for general computing, including internet usage, document handling, and multimedia activities. Some users prefer it as their primary operating system, emphasizing its stability for everyday tasks. Additionally, openSUSE Leap is chosen for its compatibility with SUSE's enterprise-grade distributions, making it an ideal choice for learning more about SUSE.<br />
In summary, openSUSE Leap caters to users who prioritize stability and a consistent experience, both on the desktop and for server-related tasks. It is a reliable choice for various computing needs, including personal, professional, and educational use cases.<br />
<br />
=== MicroOS (Aeon, Kalpa, Server) ===<br />
openSUSE MicroOS (Aeon, Kalpa, Server) caters to a diverse range of use cases. Users are interested in its potential, including for desktop and server applications, as well as IoT devices. It is seen as a solution for low-end computers and container hosting, with some users emphasizing its role as a Kubernetes (K8s) platform.<br />
<br />
While some are not interested in or do not see advantages in MicroOS, others are exploring it for development, testing, and experimentation purposes. It is used for work, college, gaming, and home server needs.<br />
<br />
Despite mixed opinions, openSUSE MicroOS is being considered for various scenarios, from providing secure, immutable desktop environments to running containers and virtualization. Some users appreciate its self-maintenance and update handling, making it an attractive option for server and IoT applications.<br />
<br />
In summary, openSUSE MicroOS serves a wide spectrum of use cases, from professional and hobby development to secure and low-maintenance server and desktop setups. It is an intriguing option for those seeking to explore the benefits of an immutable operating system.<br />
<br />
=== Leap Micro ===<br />
Users have varying opinions and use cases for openSUSE Leap Micro. While some express disinterest and see no advantage in this system, others are experimenting with it, primarily as a container host or server. Some are waiting for it to become generally available for desktop use, indicating a potential future application as a desktop OS.<br />
<br />
A common theme is its role in containerization and virtualization, with users mentioning experiments with containers and the use of Leap Micro on servers. Some users are considering it for home labing and self-hosting purposes, while others are planning to test it for specific projects.<br />
<br />
In summary, openSUSE Leap Micro has a range of potential use cases, primarily centered around containers, virtualization, and server applications, with some users exploring it for future desktop use.<br />
<br />
=== Slowroll ===<br />
openSUSE SlowRoll is a new distribution that aims to bridge the gap between the stable but aging Leap and the cutting-edge but fast-paced Tumbleweed. It is a rolling release that updates on a monthly basis, providing users with a balance of freshness and stability. Many users are interested in SlowRoll for various reasons, such as:<br />
<br />
* Server Use: Some users find SlowRoll appealing for server use, as it offers a modern but reliable OS that does not require frequent updates or major upgrades. Some users also hope for better integration with docker and other tools.<br />
* Stable Base: Some users prefer a stable base that does not change too often, but still provides access to newer software and features. Some users compare SlowRoll to FreeBSD’s RELEASE or STABLE branches, or to older versions of openSUSE that they miss.<br />
* Lower Surprise: Some users want to avoid surprises or breakages that may occur with Tumbleweed’s rapid updates. They also want to reduce the size of update downloads and the frequency of update notifications.<br />
* Faster GNOME/KDE: Some users are eager to get the latest versions of GNOME or KDE faster than Leap, without having to switch to Tumbleweed. They value the user experience and the performance of these desktop environments.<br />
* Leap Alternative: Some users are looking for an alternative to Leap that would eliminate the need for major upgrades every 18 months. They also want to avoid the obsolescence of some packages in Leap.<br />
<br />
SlowRoll may not be suitable for everyone; some users are happy with Tumbleweed or Leap, and some doubt the viability of SlowRoll. However, SlowRoll has the potential to attract a new group of users who are looking for a recent and stable distribution that updates at a moderate pace.<br />
<br />
Reasons for use include:<br />
reasons why users are interested in openSUSE SlowRoll and what makes this distribution appealing to them:<br />
<br />
* Balancing Stability and Freshness: Many users appreciate the desire for a distribution that strikes a balance between stability and up-to-date software. They find SlowRoll to be a compromise between the highly stable Leap and the rapidly updating Tumbleweed.<br />
<br />
* Server-Friendly: Some users see SlowRoll as a suitable option for server environments where stability is crucial, and frequent updates may pose challenges.<br />
<br />
* Predictable Update Cadence: The regular monthly updates of SlowRoll are seen as a convenient and predictable way to keep the system current without the need for frequent large-scale upgrades.<br />
<br />
* User-Friendly for Beginners: SlowRoll is considered a good option for beginners or family members who may not be comfortable with frequent updates or complex upgrade processes.<br />
<br />
* Addressing the Leap Transition: Some users express interest in SlowRoll due to concerns about Leap's future. They are looking for a stable alternative.<br />
<br />
* Better Software Compatibility: SlowRoll is seen as a way to achieve better software compatibility compared to Tumbleweed, particularly for those not wanting to deal with frequent updates.<br />
<br />
* Reduced Update Frequency: Users with limited internet connectivity or older hardware appreciate the less frequent updates, reducing data usage and performance strain.<br />
<br />
* Maintaining Stability: SlowRoll aims to offer stable updates while avoiding potential breakages that can occur with more frequent updates.<br />
Transition from Leap: As Leap users face a transition, SlowRoll is considered a suitable alternative, providing a rolling release with a slower update pace.<br />
<br />
* Slower Cadence for Secondary Devices: SlowRoll is seen as ideal for secondary devices that are not used as frequently and don't require the same rapid update cycle as Tumbleweed.<br />
<br />
* Improved Software Management: Users want an efficient way to manage software without redundant updates and hope SlowRoll addresses this issue.<br />
<br />
* Sustainability: Some users appreciate the slower update pace for its potential sustainability benefits and reduced load on openSUSE infrastructure.<br />
<br />
* Experimental Interest: Some express curiosity about SlowRoll but may not be convinced of its value or specific use case yet.<br />
<br />
= Home/Hobby Use: Questions & Results =<br />
<br />
== Summary ==<br />
In the survey, respondents reported their use of various technologies at home and as services. Notably, 10.82% use cloud computing at home, 36.90% use desktop computing, and 26.65% use gaming technologies. Conversely, 30.13% do not use blockchain at home, and 27.78% do not use edge computing. In terms of services, 12.34% use desktop computing, while 25.95% use machine learning. Additionally, 5.57% of respondents are not interested in the Adaptable Linux Platform. The survey provides insights into the adoption of these technologies among home and hobby users.<br />
<br />
=== Cloud computing ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 171 10.82%<br />
No (AO02) 356 22.53%<br />
No answer 100 6.33%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 198 12.53%<br />
No (AO02) 281 17.78%<br />
No answer 148 9.37%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Containerization ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 298 18.86%<br />
No (AO02) 244 15.44%<br />
No answer 85 5.38%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 108 6.84%<br />
No (AO02) 361 22.85%<br />
No answer 158 10.00%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Configuration Management ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 216 13.67%<br />
No (AO02) 295 18.67%<br />
No answer 116 7.34%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 76 4.81%<br />
No (AO02) 386 24.43%<br />
No answer 165 10.44%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Desktop Computing ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 583 36.90%<br />
No (AO02) 10 0.63%<br />
No answer 34 2.15%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 195 12.34%<br />
No (AO02) 300 18.99%<br />
No answer 132 8.35%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Server Infrastructure ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 260 16.46%<br />
No (AO02) 278 17.59%<br />
No answer 89 5.63%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 136 8.61%<br />
No (AO02) 328 20.76%<br />
No answer 163 10.32%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Serverless Computing ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 75 4.75%<br />
No (AO02) 416 26.33%<br />
No answer 136 8.61%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 37 2.34%<br />
No (AO02) 410 25.95%<br />
No answer 180 11.39%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Virtualization ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 377 23.86%<br />
No (AO02) 171 10.82%<br />
No answer 79 5.00%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 135 8.54%<br />
No (AO02) 338 21.39%<br />
No answer 154 9.75%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Edge Computing ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 47 2.97%<br />
No (AO02) 439 27.78%<br />
No answer 141 8.92%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 20 1.27%<br />
No (AO02) 417 26.39%<br />
No answer 190 12.03%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== IoT Applications ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 133 8.42%<br />
No (AO02) 376 23.80%<br />
No answer 118 7.47%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 62 3.92%<br />
No (AO02) 390 24.68%<br />
No answer 175 11.08%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Machine Learning ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 92 5.82%<br />
No (AO02) 410 25.95%<br />
No answer 125 7.91%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 47 2.97%<br />
No (AO02) 398 25.19%<br />
No answer 182 11.52%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Blockchain ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 21 1.33%<br />
No (AO02) 476 30.13%<br />
No answer 130 8.23%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 14 0.89%<br />
No (AO02) 432 27.34%<br />
No answer 181 11.46%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Gaming ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 421 26.65%<br />
No (AO02) 131 8.29%<br />
No answer 75 4.75%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 165 10.44%<br />
No (AO02) 301 19.05%<br />
No answer 161 10.19%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Other ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 245 15.51%<br />
No (AO02) 124 7.85%<br />
No answer 258 16.33%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 116 7.34%<br />
No (AO02) 223 14.11%<br />
No answer 288 18.23%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
== Are you interested in the Adaptable Linux Platform? ==<br />
Yes (Y) 286 18.10%<br />
No (N) 168 10.63%<br />
No answer 173 10.95%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
== Are you interested in the new distribution Slowroll? ==<br />
Yes (Y) 340 21.52%<br />
No (N) 154 9.75%<br />
No answer 133 8.42%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
= Work/Business Use: Questions & Results =<br />
<br />
== Summary ==<br />
In the survey, approximately 15% of respondents reported using Cloud Computing for work/business, while around 16% reported using it as a service. Similarly, around 15-18% used technologies like Containerization, Configuration Management, Desktop Computing, Server Infrastructure, Serverless Computing, and Virtualization for work/business, and 10-13% used them as services.<br />
<br />
=== Cloud computing ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 240 15.19%<br />
No (AO02) 141 8.92%<br />
No answer 44 2.78%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 257 16.27%<br />
No (AO02) 112 7.09%<br />
No answer 56 3.54%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Containerization ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 244 15.44%<br />
No (AO02) 138 8.73%<br />
No answer 43 2.72%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 168 10.63%<br />
No (AO02) 187 11.84%<br />
No answer 70 4.43%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Configuration Management ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 235 14.87%<br />
No (AO02) 133 8.42%<br />
No answer 57 3.61%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 147 9.30%<br />
No (AO02) 194 12.28%<br />
No answer 84 5.32%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Desktop Computing ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 352 22.28%<br />
No (AO02) 44 2.78%<br />
No answer 29 1.84%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 172 10.89%<br />
No (AO02) 187 11.84%<br />
No answer 66 4.18%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Server Infrastructure ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 292 18.48%<br />
No (AO02) 91 5.76%<br />
No answer 42 2.66%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 242 15.32%<br />
No (AO02) 114 7.22%<br />
No answer 69 4.37%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Serverless Computing ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 90 5.70%<br />
No (AO02) 262 16.58%<br />
No answer 73 4.62%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 102 6.46%<br />
No (AO02) 221 13.99%<br />
No answer 102 6.46%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Virtualization ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 275 17.41%<br />
No (AO02) 107 6.77%<br />
No answer 43 2.72%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 198 12.53%<br />
No (AO02) 146 9.24%<br />
No answer 81 5.13%<br />
<br />
=== Edge Computing ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 70 4.43%<br />
No (AO02) 264 16.71%<br />
No answer 91 5.76%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 61 3.86%<br />
No (AO02) 256 16.20%<br />
No answer 108 6.84%<br />
<br />
=== IoT Applications ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 61 3.86%<br />
No (AO02) 288 18.23%<br />
No answer 76 4.81%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 60 3.80%<br />
No (AO02) 260 16.46%<br />
No answer 105 6.65%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Machine Learning ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 100 6.33%<br />
No (AO02) 249 15.76%<br />
No answer 76 4.81%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 74 4.68%<br />
No (AO02) 243 15.38%<br />
No answer 108 6.84%<br />
<br />
=== Blockchain ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 17 1.08%<br />
No (AO02) 327 20.70%<br />
No answer 81 5.13%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 14 0.89%<br />
No (AO02) 305 19.30%<br />
No answer 106 6.71%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Gaming ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 43 2.72%<br />
No (AO02) 315 19.94%<br />
No answer 67 4.24%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 28 1.77%<br />
No (AO02) 298 18.86%<br />
No answer 99 6.27%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Other ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 122 7.72%<br />
No (AO02) 115 7.28%<br />
No answer 188 11.90%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 87 5.51%<br />
No (AO02) 146 9.24%<br />
No answer 192 12.15%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
== Are you interested in the Adaptable Linux Platform? ==<br />
Yes (Y) 216 13.67%<br />
No (N) 88 5.57%<br />
No answer 121 7.66%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
= Service Satisfaction =<br />
<br />
== Summary ==<br />
In the survey, respondents expressed dissatisfaction with various IT services for different reasons. For Cloud Computing, dissatisfaction stemmed from security concerns, high costs, and integration challenges. For Containerization, users desired better security and automation tools. Configuration Management users sought improved online management and flexibility. Desktop Computing users wanted better graphical upgrades and software deployment. Server Infrastructure dissatisfaction arose from cost concerns and the need for better management tools. Serverless Computing users desired innovation and improved security. Virtualization users faced challenges with installation and performance. Edge Computing users wanted better automation and security. IoT Applications users found services confusing and called for innovation. Machine Learning users preferred open-source solutions and performance improvements. Blockchain dissatisfaction was expressed without specific details. Gaming users desired better gaming support, compatibility, and performance. Other services dissatisfaction ranged from the lack of a virtual keyboard to compatibility issues with corporate applications, with some users recommending open-source solutions.<br />
<br />
=== Cloud computing ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 73 4.62%<br />
Not Satisfied (AO02) 34 2.15%<br />
Neutral (AO03) 110 6.96%<br />
Satisfied (AO04) 133 8.42%<br />
No answer 75 4.75%<br />
<br />
Many individuals expressed dissatisfaction with the cloud computing services used by their company for various reasons. Security concerns were a recurring theme, with some pointing out that they don't trust the security of cloud providers' systems. High costs and the need for significant application integration were common complaints, with a desire for more cost-effective and flexible options. Others emphasized the importance of performance, management, and visibility, as well as reliability. Some expressed frustration with the slow speeds and painful experiences when using cloud folders. There was also a dislike for monopolies and a desire to reduce dependence on Microsoft and Google products. Open source solutions and a preference for on-premises cloud like Kubernetes were mentioned. Standardization and open standards were proposed to make cloud services more user-friendly and compatible. The complexity of some cloud services for simpler tasks and the lack of specialized tech personnel were also cited as issues. A multi-cloud approach and the use of free and open-source software (FLOSS) services were advocated for. In summary, dissatisfaction with cloud computing services primarily stemmed from concerns about security, cost, integration, and the desire for more standardized and user-friendly solutions.<br />
<br />
=== Containerization ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 96 6.08%<br />
Not Satisfied (AO02) 18 1.14%<br />
Neutral (AO03) 86 5.44%<br />
Satisfied (AO04) 127 8.04%<br />
No answer 98 6.20%<br />
<br />
People who answered express dissatisfaction with their current containerization services for various reasons. Some of them highlight the need for migration to Rancher, which they see as a more suitable option for managing Docker containers. They also emphasize the importance of better security and management, with a desire for improved tools for pipeline building and automation. Additionally, there's a need for increased awareness of containerization benefits among managers and a desire for on-premises solutions, though cost is a concern. Other aspects include a lack of security updates, slow performance with an OS, a deficit of knowledge for implementation, and limited usage, making improvement challenging. Overall, the dissatisfaction stems from issues with security, performance, management, and a lack of alignment with the company's future plans.<br />
<br />
=== Configuration Management ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 92 5.82%<br />
Not Satisfied (AO02) 25 1.58%<br />
Neutral (AO03) 93 5.89%<br />
Satisfied (AO04) 105 6.65%<br />
No answer 110 6.96%<br />
<br />
People who answered express dissatisfaction with the current Configuration Management services for various reasons. They desire better online management capabilities and complain about the lack of quality examples for writing Salt statements to manage the infrastructure effectively. Additionally, they wish for more flexibility in managing flatpaks and containers through YaST. The need for making configurations less dependent on the OS and promoting innovation is emphasized. There's a call for increased automation with Uyuni and a desire for better tools for user management and security within YaST.<br />
Some express discontent with the current use of Git and GitLab, citing issues with these tools. Security concerns are raised as well, indicating a need for improvement in this area. Others seek more awareness of the benefits of Configuration Management among managers. Some feel that the existing system has too many issues and could be significantly improved. They prefer standard patterns over custom solutions and are cautious about depending on Microsoft Active Directory. However, a few individuals are content with the current setup and see no need for improvement. The dissatisfaction largely revolves around issues of tool quality, security, and the desire for more user-friendly and effective solutions.<br />
<br />
<br />
=== Desktop Computing ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 59 3.73%<br />
Not Satisfied (AO02) 38 2.41%<br />
Neutral (AO03) 69 4.37%<br />
Satisfied (AO04) 183 11.58%<br />
No answer 76 4.81%<br />
<br />
People who answered express a wide range of dissatisfaction with the current Desktop Computing services they use. They desire better graphical upgrades, full interoperability, and suggest the use of Linux for a more seamless desktop experience. Some request that desktop environments like GNOME adopt a more traditional configuration style.<br />
There are concerns about the current implementation, management, updates, and deployment of desktop systems. Users are looking for improvements in security, graphics card support, and the availability of HDR support for KDE Plasma and Firefox.<br />
<br />
Some express a preference for openSUSE over Windows but face challenges with VPN setup. Others wish for a corporate-branded openSUSE installation, longer lifecycles, and simplified user experiences, especially for new users.<br />
Linux is seen as a viable alternative to Windows, but concerns remain about software compatibility and the need for better codecs and hardware acceleration. The desire to standardize to one desktop environment is evident, and some users wish to see fewer proprietary software packages and a shift towards Linux workstations.<br />
<br />
In general, dissatisfaction is rooted in issues of software reliability, security, the use of proprietary software, and the desire for more freedom in choosing their desktop environment. Many have varied preferences and concerns regarding the use of Linux, Windows, and cloud-based solutions.<br />
<br />
=== Server Infrastructure ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 49 3.10%<br />
Not Satisfied (AO02) 22 1.39%<br />
Neutral (AO03) 76 4.81%<br />
Satisfied (AO04) 188 11.90%<br />
No answer 90 5.70%<br />
<br />
People who responded express their dissatisfaction with the current server infrastructure services for various reasons. Some suggest a shift from Windows servers to Linux for a more cost-effective and flexible solution. Concerns are raised about the cost of integrating less expensive options and a desire for more tools to provision bare metal servers.<br />
<br />
Innovation and improved functionality for Yast2cli are highlighted as areas of improvement. Some acknowledge that there has been self-inflicted mismanagement of Linux, which may have impacted the server infrastructure. Security is cited as a major concern, emphasizing the need for better protection.<br />
There's a call for hosting more services and implementing a self-service portal to streamline server requests. A stable base for long-supported applications is deemed crucial, and outside input and best practices are welcomed. Cost management is stressed, urging a more efficient use of resources and a focus on reducing expenses.<br />
<br />
The use of open-source (FLOSS) services is encouraged, and some express the need to move away from AWS, possibly in search of more predictable performance and access to bare metal machines for critical applications. In summary, dissatisfaction with server infrastructure services is rooted in concerns about cost, security, performance, and the desire for more innovation and flexibility.<br />
<br />
=== Serverless Computing ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 174 11.01%<br />
Not Satisfied (AO02) 8 0.51%<br />
Neutral (AO03) 56 3.54%<br />
Satisfied (AO04) 44 2.78%<br />
No answer 143 9.05%<br />
<br />
People who responded express their dissatisfaction with the current serverless computing services for various reasons. The need for innovation in these services is highlighted, suggesting a desire for improvements and advancements in functionality.<br />
<br />
Security is a major concern, with users expressing that the existing security measures are inadequate. Some take a skeptical view of serverless computing, asserting that it's an everyday reality that software still needs to run somewhere, potentially indicating a preference for more traditional approaches.<br />
Others mention that the services are not currently in use, making it difficult to assess and improve them. Additionally, the cost-effectiveness of serverless computing is questioned, with a sentiment that it can be more expensive by design. The advice given is to use it sparingly, primarily when IT is not the core business, and to avoid overusing it.<br />
<br />
In summary, dissatisfaction with serverless computing services is driven by concerns about innovation, security, cost, and the practicality of this approach in the context of the company's needs and objectives.<br />
<br />
=== Virtualization ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 71 4.49%<br />
Not Satisfied (AO02) 17 1.08%<br />
Neutral (AO03) 84 5.32%<br />
Satisfied (AO04) 148 9.37%<br />
No answer 105 6.65%<br />
<br />
People who responded express their dissatisfaction with the current virtualization services for various reasons. They find it difficult to install a Windows 11 machine, highlighting the need for better integration of virtualization hosts, a task that some are willing to work on when they have time.<br />
<br />
The speed of I/O and the performance of virtualization are of concern, and users want easier installation and usage with improved performance. There is a call for innovation in virtualization services.<br />
<br />
Issues with VirtualBox's speed and network firewall rules are raised, suggesting a need for better management GUI tools for multiple KVM hosts. Security is criticized, and users want the ability to use virtual machines for testing without needing to install temporary tools on the host OS.<br />
<br />
Some express a desire for an alternative to VMWare, with a mention of a lack of competitive offerings. Better infrastructure management and increased speed are sought, although there are concerns about the performance of an OS. Users want more flexibility in VM creation, including GPU passthrough.<br />
<br />
While some express contentment with the existing services, there are also requests for better virtualization management tools, the use of open-source (FLOSS) services, and better performance for database servers on Azure Virtual Desktop (AVD).<br />
<br />
In summary, dissatisfaction with virtualization services revolves around installation difficulties, performance, management, security, and the desire for more flexibility and innovation in the virtualization environment.<br />
<br />
=== Edge Computing ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 195 12.34%<br />
Not Satisfied (AO02) 7 0.44%<br />
Neutral (AO03) 52 3.29%<br />
Satisfied (AO04) 27 1.71%<br />
No answer 144 9.11%<br />
<br />
People who responded express their dissatisfaction with the current edge computing services for various reasons. They emphasize the need for innovation, signaling a desire for improved and more advanced edge computing solutions.<br />
Better automation is sought, suggesting a need for streamlining processes and reducing manual tasks. Security is a significant concern, with users pointing out that the existing security measures are inadequate.<br />
<br />
Some people mention the rarity of long-living, transactional, self-managing systems and the lack of documentation for such systems, which hampers their usability and implementation.<br />
<br />
There are references to the need for better integration with central tools for deploying software, indicating a desire for a more cohesive and efficient software deployment process. Additionally, users express the desire for increased computing capability at a lower cost within the same environmental package, highlighting the importance of cost-effectiveness and performance.<br />
<br />
In summary, dissatisfaction with edge computing services is driven by the desire for innovation, better automation, enhanced security, improved documentation, integration with central tools, and cost-efficiency.<br />
<br />
=== IoT Applications ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 206 13.04%<br />
Not Satisfied (AO02) 9 0.57%<br />
Neutral (AO03) 51 3.23%<br />
Satisfied (AO04) 20 1.27%<br />
No answer 139 8.80%<br />
<br />
Those who responded express their dissatisfaction with the current IoT application services for various reasons. They find the services confusing and feel that they require too much prior knowledge about the platform, making them challenging to use effectively.<br />
<br />
Innovation is highlighted as an area for improvement, suggesting a desire for more advanced and cutting-edge IoT solutions. Some indicate that they are not currently using these services or are not actively engaged in IoT applications.<br />
There is a reference to the rarity of long-living, transactional, and self-managing systems, and the lack of documentation for such systems, which creates usability issues. Additionally, very few individuals are utilizing these services.<br />
<br />
Some express disinterest in IoT applications, stating that they are not involved in that area. However, others mention the need for better integration with central tools for deploying software, indicating a desire for a more streamlined and cohesive deployment process.<br />
<br />
Lastly, the challenge of supporting multiple networking infrastructures concurrently, such as GSM EDGE, NB IoT, LoraWAN, Ethernet, and Wi-Fi, is noted, implying the complexity of managing diverse IoT connectivity options.<br />
In summary, dissatisfaction with IoT application services stems from issues related to usability, the desire for innovation, a lack of use or interest, the need for better documentation and integration, and the challenges of supporting multiple networking infrastructures.<br />
<br />
=== Machine Learning ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 189 11.96%<br />
Not Satisfied (AO02) 15 0.95%<br />
Neutral (AO03) 52 3.29%<br />
Satisfied (AO04) 27 1.71%<br />
No answer 142 8.99%<br />
<br />
Those who responded express their dissatisfaction with the current machine learning services for various reasons. They find machine learning services offered by external providers too proprietary and prefer in-house implementations using open-source technologies.<br />
<br />
One individual's response is simply "Ok," indicating a lack of specific complaints or needs. Innovation is not mentioned as an area for improvement.<br />
<br />
Some express the need for easier access to machines, highlighting a desire for more straightforward and efficient access to the resources required for machine learning projects. Others mention the need for more GPU power and improved scheduling, underlining the importance of performance and resource management.<br />
<br />
Using up-to-date versions of systems that implement machine learning is deemed necessary for staying current and effective in this field.<br />
<br />
There's a clear emphasis on treating machine learning as a practical tool rather than a novelty. Users are advised to structure and prepare data properly, avoid rushing into machine learning, and prevent the development of biased algorithms that merely reflect existing understanding. They stress the importance of using data to gain insights and understanding.<br />
<br />
Lastly, there is a call to run machine learning pipelines with the same level of continuous integration and reliability as is available to developers, emphasizing the need for robust and reliable machine learning processes.<br />
<br />
In summary, dissatisfaction with machine learning services is driven by concerns about proprietary offerings, the need for in-house open-source implementations, access to resources, performance, up-to-date systems, and the responsible and practical use of machine learning as a tool in the organization's workflows.<br />
<br />
=== Blockchain ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 253 16.01%<br />
Not Satisfied (AO02) 4 0.25%<br />
Neutral (AO03) 15 0.95%<br />
Satisfied (AO04) 6 0.38%<br />
No answer 147 9.30%<br />
<br />
Those who responded express a strong negative sentiment toward blockchain. There's no specific mention of innovation or any potential areas for improvement. Responses were minimal, cryptic and lacked clarity and detail regarding the specific issues or concerns with the services, making it challenging to discern the exact nature of the dissatisfaction with its use.<br />
<br />
=== Gaming ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 221 13.99%<br />
Not Satisfied (AO02) 6 0.38%<br />
Neutral (AO03) 26 1.65%<br />
Satisfied (AO04) 29 1.84%<br />
No answer 143 9.05%<br />
<br />
Those who responded express their dissatisfaction with the current gaming services for various reasons. They call for better gaming support, suggesting a need for improvements in this area.<br />
<br />
There are mentions of issues related to the use of NVIDIA graphics cards under Wayland on openSUSE, indicating a lack of convenience and compatibility in this context. Linux drivers are criticized for not rendering some games properly, ultimately requiring the use of Windows for certain gaming needs.<br />
<br />
On a more positive note, some users appreciate the good compatibility, performance, and HDR support in the existing gaming services.<br />
<br />
Innovation is highlighted as an area for improvement, suggesting a desire for more advanced and up-to-date gaming features and technologies. The pace of graphics development is seen as slower than Windows, particularly concerning HDR, ray tracing, and GPU drivers.<br />
<br />
There are requests for better support of modern graphical features, including HDR and ray tracing, as well as a desire for support for new game releases. The mention of RegataOS, which is based on openSUSE, suggests the potential for openSUSE to take inspiration from such initiatives.<br />
<br />
VR is mentioned as a specific area of interest and potential improvement. Users express a general wish for every game to work effectively, suggesting a desire for enhanced compatibility.<br />
<br />
However, some responses lack specific details, with phrases like "no idea," making it challenging to discern the exact nature of the dissatisfaction in those cases.<br />
In summary, dissatisfaction with gaming services is driven by issues related to compatibility, performance, graphics development, and support for modern gaming features, as well as a desire for better innovation and VR support.<br />
<br />
<br />
=== Other ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 103 6.52%<br />
Not Satisfied (AO02) 5 0.32%<br />
Neutral (AO03) 56 3.54%<br />
Satisfied (AO04) 42 2.66%<br />
No answer 219 13.86%<br />
<br />
Those who responded express their dissatisfaction with other services for various reasons. One of the concerns raised is the lack of a proper built-in virtual keyboard, which is seen as necessary for security and other purposes. This indicates a need for enhanced security features.<br />
<br />
Another user points out that while it may not be an openSUSE-specific problem, Linux, in general, lacks traction among end-users in the multimedia and creative suite sectors. They suggest that Linux isn't attractive enough as a platform for digital artists, emphasizing the need for more innovation and user-friendly tools in this area.<br />
Some users express dissatisfaction with the lack of Linux support for certain corporate applications, listing examples like Oracle Content Experience desktop client, Microsoft Outlook desktop, Microsoft Office, and Cisco telephony. This indicates a need for better compatibility with widely used software, particularly in corporate environments.<br />
A few responses are marked as "N/A," indicating that the users may not have specific issues or needs related to the other services. However, one response suggests that the term "other" could possibly refer to AI services, and they clarify that the company is not currently using AI technologies.<br />
<br />
There is also a recommendation to use open-source (FLOSS) services, highlighting a preference for open and community-driven solutions.<br />
<br />
In summary, dissatisfaction with other services primarily revolves around the need for improved security features, better support for creative and multimedia sectors, more innovation, and enhanced compatibility with widely used corporate applications on Linux. Additionally, users express a preference for open-source solutions.<br />
<br />
= General Questions =<br />
<br />
=== What do you believe are the primary factors driving the growth of Linux and open-source technologies in your industry? ===<br />
<br />
In summary, the primary factors driving the growth of Linux and open-source technologies in various industries include cost savings, fast deployment, the need for scientific applications and platforms beyond business-oriented Microsoft applications, and increased interest leading to more software development. Other key drivers include digital sovereignty, regulatory compliance, and cost considerations. In the telecom industry, the migration to Linux and open-source platforms is a major trend.<br />
<br />
The open development and contribution model, along with the decentralization of larger companies, is contributing to the growth of open source. Employee preferences for Linux and personal interests in traditional industries are also driving adoption. Concerns about Windows' subscription model and privacy issues have led to a shift towards open source alternatives.<br />
<br />
Linux's robustness, security, adaptability, and open APIs are key factors. The availability of vendors like SUSE with helpful technical support is driving adoption, as well as ease of use and the avoidance of intrusive paid services.<br />
Innovations such as containers and cloud technology are further promoting Linux and open-source adoption. Copy-left licensing, access to source code, and adaptability play a role in growth.<br />
<br />
The broad availability of open-source software in various industries, from astronomy to high-performance computing, offers quality solutions. Linux's security, reliability, stability, and extensive ecosystem satisfy diverse needs.<br />
Factors like virtualization, cost, reliability, transparency, and avoiding vendor lock-in are also contributing to the growth of Linux and open-source technologies. Overall, these factors reflect the adaptability and cost-effectiveness of Linux and open-source solutions across different sectors.<br />
<br />
=== Are there any specific challenges/barriers hindering wider adoption of the technologies cited above in your industry? ===<br />
In various industries, there are several challenges and barriers hindering wider adoption of Linux and open-source technologies. These include:<br />
<br />
Industry-specific software: Many industries rely on specialized software that is designed for Windows environments. In some cases, these applications have no Linux-compatible alternatives. This is a significant barrier to adoption in sectors like textile, CAD, and graphics design.<br />
<br />
Vendor lock-in: Organizations often face challenges in migrating away from existing proprietary technologies due to vendor lock-in. This is especially true when dealing with Microsoft, which dominates the end-user computing space, and Google's dominance in education.<br />
<br />
Lack of knowledge and inertia: Many managers and end-users are more familiar with proprietary technologies like Microsoft, and there is often a resistance to change. This is compounded by a lack of knowledge about Linux and open source among IT staff and management.<br />
<br />
Compatibility and software support: Some critical legacy and proprietary software do not have Linux versions or suitable alternatives. Lack of support from third-party vendors for Linux also poses a barrier to adoption.<br />
<br />
Fragmentation and choice: The wide variety of Linux distributions and desktop environments can be confusing for regular users. This fragmentation can lead to hesitation and lack of standardization.<br />
<br />
Documentation and usability: Inconsistent or inadequate documentation and the lack of an end-user-friendly experience on Linux desktops can discourage adoption.<br />
<br />
Hardware support: Lack of support for specific hardware and peripherals can be a barrier to adoption, especially when users depend on these devices for their work.<br />
<br />
Resistance to change and complacency: Many users and organizations are resistant to change and prefer to stick with familiar systems, even if they are suboptimal.<br />
<br />
Reliance on proprietary software and technologies: Industries, such as finance and banking, heavily rely on proprietary software that is considered essential for compliance with regulations.<br />
<br />
Training and knowledge: There is a need for better training and knowledge dissemination about Linux and open-source alternatives in educational institutions, workplaces, and among decision-makers.<br />
<br />
Overall, the challenges and barriers to wider adoption of Linux and open-source technologies in various industries are complex and multifaceted, ranging from technical compatibility issues to organizational and cultural resistance to change. Overcoming these barriers will require concerted efforts in education, software development, and standardization to make Linux and open source more accessible and user-friendly.<br />
<br />
=== Are there any emerging technologies/trends pertaining to the IT industry you believe will significantly contribute to business growth in the next three to five years? Please explain. ===<br />
<br />
<br />
Several emerging technologies and trends are expected to significantly contribute to business growth in the IT industry over the next three to five years. These include:<br />
<br />
Containerization: Technologies like containerization (e.g., Docker) and orchestration (e.g., Kubernetes) are becoming increasingly essential for managing and deploying applications. They offer consistent developer experiences and facilitate the transition to cloud-native architectures.<br />
<br />
* Artificial Intelligence (AI) and Machine Learning (ML): AI and ML are having a broad impact on various sectors, from automating tasks to improving business insight and customer satisfaction. AI at the edge, data storage, and communication technologies will drive growth in IT.<br />
<br />
* Cloud Computing: Cloud computing is expected to become even more widespread, with businesses leveraging cloud-based services and applications. The shift toward the cloud is driven by remote work, scalability, and accessibility from various devices.<br />
<br />
* Edge Computing: Edge computing is gaining prominence, particularly in IoT applications. It reduces latency, making real-time processing and analysis of data more accessible, which has implications for various industries.<br />
<br />
* Domain-Specific Applications: Growth in browser-based applications tailored for specific industries.<br />
<br />
* Python Integration: The integration of Python with Excel and other applications will streamline processes.<br />
<br />
* Scientific Clusters: Use of clusters for scientific applications will advance research and development.<br />
<br />
*Blockchain: While blockchain technology continues to evolve, it offers numerous use cases, including improved security, supply chain management, and transparent transactions. Blockchain is expected to drive innovation and growth in several sectors.<br />
<br />
* Immutable OS: Immutable operating systems are gaining attention, particularly for their reliability and the ability to roll back the OS easily in case of issues. This trend is particularly relevant for businesses looking to maintain system stability.<br />
<br />
* Open Source: The continued growth of open-source software and the commercialization of open-source projects will contribute to business growth. Open-source solutions can provide cost-effective alternatives and greater flexibility.<br />
<br />
AI-Assisted Software Development: AI tools that assist developers in tasks such as code optimization, text generation, and image correction will enhance productivity in software development.<br />
<br />
* Containerization Standardization (e.g., Flatpak): Efforts to standardize containerization formats like Flatpak will lead to better app availability, particularly on Linux-based systems. This will simplify the distribution and installation of third-party applications.<br />
<br />
* Internet of Things (IoT): As more devices and objects become connected to the internet, IoT applications will continue to grow. IoT offers opportunities for data collection, analysis, and automation in various industries.<br />
<br />
* Quantum Computing: Advances in quantum computing will enable complex calculations and simulations, offering new opportunities in research and problem-solving.<br />
<br />
* Big Data and Analytics: The combination of big data and AI, powered by new-generation processors, opens up opportunities for advanced data analysis and automated processing, providing insights for business growth.<br />
<br />
* Standardization of Data Access Protocols: The standardization of data access protocols, especially in environmental data management, will open new applications and enable the development of digital twins for various systems.<br />
<br />
These emerging technologies and trends are expected to shape the IT industry, drive innovation, and offer opportunities for businesses to grow and thrive.<br />
<br />
<br />
=== In the last three months, have you contributed to an open-source project? ===<br />
<br />
'''Fedora Infrastructure Project:''' One participant joined the Fedora Infrastructure project but expressed difficulty navigating it.<br />
openSUSE and es.opensuse.org: Several contributors mentioned their involvement in openSUSE, either through translation, bug reporting, or other forms of support.<br />
<br />
'''GitHub Projects:''' Many mentioned working on GitHub projects, including small open-source projects, symbol viewers for code, and various scripts.<br />
<br />
'''Linux Distribution and Software Projects:''' Some participants contributed to specific Linux distributions, like Xubuntu, Tumbleweed, or Void Linux. Others mentioned their contributions to various software projects such as Haiku, Mastodon, and OSM.<br />
<br />
'''Documentation and Translation:''' Several participants contributed through documentation, translation work, or opening bug reports.<br />
<br />
'''Testing and Bug Reports:''' Many mentioned their involvement in testing and reporting issues for open-source projects.<br />
<br />
'''Personal Open-Source Projects:''' Some contributors mentioned their own open-source projects and their ongoing work.<br />
<br />
'''Donations:''' A few participants mentioned donating to open-source projects, such as LibreOffice, KDE, and others.<br />
<br />
'''Limited Coding Skills:''' Some participants admitted they had limited coding skills but expressed a willingness to help with documentation and user support.<br />
<br />
'''Icon Design:''' One contributor mentioned creating icons for the Linux Papirus icon theme.<br />
<br />
'''Monetary Donations:''' A few mentioned contributing through monetary donations to various open-source projects.<br />
<br />
'''Survey Responses:''' Some participants contributed by responding to surveys from projects like Mozilla.<br />
<br />
'''Linux Distributions:''' Contributors reported work on various Linux distributions such as Manjaro and Q4OS.<br />
<br />
'''Translation:''' Multiple contributors mentioned translation work for projects like GNOME, OpenVPN, and Mastodon.<br />
<br />
'''Code Contributions:''' A few mentioned providing code contributions to projects like Path of Building and Flare.<br />
<br />
'''Bug Reporting:''' Several contributors mentioned their involvement through bug reporting for projects like KDE, Plasma, and openwrt.<br />
<br />
'''Small Commits and Testing:''' Several participants mentioned making small commits, testing, and bug reporting for various open-source projects.<br />
No Recent Contributions: Some participants indicated that they had not made any contributions in the past three months, often citing a lack of coding skills or limited time.<br />
<br />
In summary, the responses show a diverse range of contributions to open-source projects, including code development, documentation, translations, bug reports, and financial support. These contributions help sustain and improve the open-source ecosystem.<br />
<br />
<br />
=== In the last three months, have you contributed to openSUSE? ===<br />
<br />
'''Forum Support:''' Many contributors reported providing support via the openSUSE forum, helping users troubleshoot issues, and answering questions.<br />
<br />
'''Documentation:''' Several participants mentioned their involvement in documentation, including maintaining entries on the openSUSE Chinese Wiki, contributing to the Knowledge Base, and helping improve documentation.<br />
<br />
'''Bug Reports:''' A significant number of contributors engaged in bug reporting and interacting on mailing lists, bugfixes, and bug reports for areas like Tumbleweed, Aeon, Leap, and more.<br />
<br />
'''Packaging:''' Packaging contributions were mentioned for Tumbleweed, Leap, and Factory, with some reporting maintaining packages for the Build Service and packaging tools.<br />
<br />
'''Translations:''' Some participants contributed through translations for openSUSE official news and other areas, as well as making contributions to documentation and marketing.<br />
<br />
'''Testing and Bug Fixing:''' Contributors shared their involvement in testing Tumbleweed, bug reporting, bug fixes, and participation in openQA.<br />
<br />
'''Marketing and Advocacy:''' A few mentioned marketing and advocacy efforts to promote openSUSE in various ways.<br />
<br />
'''Community Engagement:''' Some participants reported their community involvement, including attending conferences, supporting forums, and moderating forums.<br />
<br />
'''Challenges and Concerns:''' A few contributors expressed concerns about the lack of clear onboarding documentation and difficulties navigating openSUSE resources like the Wiki, Bugtracker, and a perceived vagueness surrounding the project's future.<br />
<br />
'''Other Contributions:''' Miscellaneous contributions were mentioned, such as conducting surveys, filing bug reports, updating Wiki articles, and offering support in various forms.<br />
<br />
While many contributors shared active engagement and efforts to contribute to openSUSE in various capacities, there were concerns raised about certain aspects of the project, such as documentation and community engagement. These responses provide insights into both the positive contributions and challenges faced by individuals within the openSUSE community.<br />
<br />
=== Are you considering or actively using Linux in areas beyond your primary use case (e.g., gaming, blockchain, AI, robotics, graphic design, movie animation or sound creation, etc.)? if yes, please share your the uses case in a few small sentences. ===<br />
<br />
'''Creative Work:''' Many respondents indicated that they use Linux for their primary use case, such as general computing or software development, but they switch to Windows for creative work like photo and video editing due to the perceived lack of suitable creative apps on Linux.<br />
<br />
'''Multifunctional Use:''' Some respondents reported using Linux for a wide range of purposes, including finance, video production, graphic design, game development, IoT, and more, indicating that Linux covers their diverse needs.<br />
<br />
'''Gamers:''' Several mentioned using Linux for gaming, either natively or through compatibility layers like Proton or Wine.<br />
<br />
'''Home Automation and IoT:''' A few respondents were actively considering or using Linux for home automation, IoT, and other embedded applications.<br />
<br />
'''Hobbyists:''' Hobbyist activities such as 3D modeling, 3D printing, machine learning, and blockchain experimentation were mentioned as use cases for Linux.<br />
<br />
'''Server and Cloud:''' Some participants discussed using Linux for hosting servers and cloud-based services.<br />
<br />
'''Self-Hosted Services:''' A few users highlighted self-hosting applications, such as Nextcloud and Freshrss, as part of their Linux usage.<br />
<br />
'''Mobile and Edge Devices:''' A few were exploring Linux for mobile devices and edge computing.<br />
<br />
'''Scientific and Research:''' Linux was mentioned for scientific research, running simulations, and data analysis.<br />
'''<br />
Media Production:''' Some participants expressed interest in using Linux for audio and video editing, animation, and music production.<br />
<br />
'''Educational and Training:''' Linux was considered for educational and training purposes, including using it in kiosk mode.<br />
<br />
'''Use Everywhere:''' Some respondents stated that they use Linux for everything and aim to continue doing so wherever possible.<br />
<br />
'''Testing and Experimentation:''' Linux was preferred for testing and experimentation, including software development, learning new programming languages, and AI research.<br />
<br />
'''Graphics and Design:''' Some were using Linux for graphic design, 3D modeling, and CAD work.<br />
<br />
'''Server Administration:''' Linux was used for server administration and remote data analysis in scientific fields.<br />
<br />
'''General Hobby Use:''' Linux was used for various hobbies like photography, 3D printing, home automation, and more.<br />
<br />
'''Creative Professionals:''' A few respondents reported using Linux in creative fields like graphics, music, and video production.<br />
<br />
'''Enterprise:''' A few discussed using Linux for corporate and business applications and in professional settings.<br />
<br />
'''Home Media and NAS:''' Linux was used as a home media server and for network-attached storage (NAS) setups.<br />
<br />
'''Cloud-Based Development:''' Linux was actively used for cloud-based development, containerization, and web hosting.<br />
<br />
'''School and Training:''' Linux was considered for school and training purposes, with some respondents noting the need for open-source training resources.<br />
<br />
While some users faced limitations in certain areas due to software availability, the responses showed that Linux is being embraced for an array of use cases, both personal and professional. Additionally, there was a recurring theme of users wanting to extend their use of Linux to more scenarios, such as gaming and creative work, as the ecosystem evolves and matures.<br />
<br />
=== “What specific benefits have you experienced by using Linux in your chosen use case(s)?” ===<br />
<br />
'''Trust and Privacy:''' Users appreciate the trustworthiness of Linux, which doesn't collect and sell their data. It provides better privacy and doesn't force updates on them.<br />
<br />
'''Stability and Reliability:''' Linux is known for its stability and reliability. It doesn't crash often, and users find it dependable for their daily tasks.<br />
<br />
'''Customization:''' Linux offers extensive customization, allowing users to configure their systems to meet their exact needs. They can choose from a wide range of desktop environments and software.<br />
<br />
'''Low Resource Usage:''' Linux is efficient and runs well on older hardware, extending the life of aging devices and saving money.<br />
Open Source and Free Software: Many users appreciate the open-source nature of Linux and the availability of free software. It gives them freedom, both in terms of using the software and modifying it.<br />
<br />
'''Community and Learning:''' Linux has a strong and supportive community. Users learn a lot about IT, computing, and how their computer works. It's a platform for gaining knowledge and skills.<br />
<br />
'''Security:''' Linux is often praised for its security features, including fewer virus risks and greater control over user data.<br />
<br />
'''Flexibility:''' Users can adapt Linux to their workflows, whether it's for development, gaming, or daily use. It's a versatile operating system.<br />
<br />
'''Cost-Effective:''' Linux is generally free to use, reducing costs compared to proprietary alternatives. This is especially beneficial for individuals and small organizations.<br />
<br />
'''Containerization and Server Management:''' Linux is favored for server management, thanks to its containerization capabilities. It's often seen as an ideal platform for DevOps professionals.<br />
<br />
'''Performance:''' Many users report that Linux offers better performance, stability, and speed compared to other operating systems.<br />
Choice and Variety: Linux provides users with a wide range of choices, from distributions and desktop environments to software and tools. Users appreciate the diversity and options available.<br />
<br />
Overall, Linux users value its open nature, customization, security, and the control it provides over their computing environment. It's clear that Linux serves a wide range of needs and preferences across its user base.<br />
<br />
=== What challenges or limitations have you encountered when using our distributions for your primary or secondary use case(s)? ===<br />
<br />
'''Outdated Software:''' Difficulty accessing the latest software packages, affecting software like Docker.<br />
<br />
'''Limited Host Support:''' Some hosts do not provide images for openSUSE, limiting platform usability.<br />
<br />
'''Encryption Issues:''' Problems setting up hard drive encryption, including keyboard layout issues during boot.<br />
<br />
'''Documentation and Support:''' Inadequate documentation and challenges finding support, especially for data science.<br />
<br />
'''Graphics Card Setup:''' Configuration issues with graphics cards and difficulties getting community assistance.<br />
<br />
'''Compatibility:''' Issues running Windows programs under Wine/Proton, requiring complex troubleshooting.<br />
<br />
'''Hardware Integration:''' Problems with hardware integration, including graphics card switching and docking.<br />
<br />
'''Choice Overload:''' OpenSUSE's abundance of options can overwhelm new users.<br />
<br />
'''Multimedia Codecs:''' Issues with multimedia codecs and the absence of some software packages.<br />
<br />
'''Incomplete Documentation:''' OpenSUSE's documentation can be challenging to comprehend, especially for new tools.<br />
<br />
'''VPN Compatibility:''' Problems with corporate VPN solutions due to different naming conventions.<br />
<br />
'''Learning Curve:''' A steep learning curve for users new to Linux.<br />
<br />
'''Gaming Support:''' Support for certain games and peripherals can be problematic.<br />
<br />
'''Proprietary Software:''' Limited support for proprietary software and hardware, including graphics drivers.<br />
<br />
'''Frequent Upgrades:''' Users find the need for frequent fresh installations onerous.<br />
<br />
'''Battery Life and Performance:''' Users have reported issues with battery life, performance, and resource usage.<br />
<br />
'''Troubleshooting:''' Troubleshooting problems can be challenging, particularly for less experienced users.<br />
<br />
'''Hardware Compatibility:''' Challenges with hardware support, including printers, graphics cards, and touchpad configuration.<br />
<br />
'''Filesystem Read-Only:''' Ext4 root partitions on virtual machines can go 'read-only' unexpectedly, requiring backups.<br />
<br />
'''Network Scanner Compatibility:''' Difficulty recognizing network scanners, occasionally requiring the use of Windows machines.<br />
<br />
Despite these challenges, openSUSE users appreciate the flexibility and choices the distribution offers and find the investment in learning to be worthwhile. OpenSUSE has a strong community and user base, and many of these issues can be addressed through community support and further development.<br />
<br />
=== Have you explored Linux-based solutions for edge computing or IoT applications? If yes, please share your experiences and any notable benefits. ===<br />
<br />
Many of the comments indicate that users have explored Linux-based solutions for edge computing and IoT applications, with a mix of experiences and perceived benefits:<br />
<br />
* Some users mentioned that Linux, especially in combination with containers and WebAssembly (WASM), is excellent for edge and IoT applications.<br />
<br />
* Linux is recognized for providing full control over services and being reliable for various IoT use cases, including home automation, home servers, and multimedia control.<br />
<br />
* Several users highlighted the use of Raspberry Pi devices for IoT, surveillance, and home automation.<br />
<br />
* The ability to build custom Linux distributions for IoT applications using tools like Yocto was appreciated.<br />
<br />
* Despite the benefits, some users mentioned challenges, including the heavyweight nature of current Linux distributions and the need for more self-managing capability in IoT solutions.<br />
<br />
* Notable benefits of Linux for edge computing include faster development, the ability to run compute-intensive tasks, and the capacity to keep data and services in-house.<br />
<br />
* Users emphasized the importance of Linux's open nature, privacy, and freedom from IoT platform capture or abandonment.<br />
<br />
* Challenges mentioned include the need for stable power supplies, reliable storage, and efficient service separation.<br />
<br />
Overall, Linux-based solutions seem to offer flexibility and control for edge computing and IoT applications, with the trade-offs of managing updates and hardware considerations.<br />
<br />
=== Are there particular Linux distributions or flavors that you prefer for specific use cases? If so, which ones and why? ===<br />
<br />
It's clear that there is a wide range of Linux distributions preferred by different users based on their specific needs and preferences. Some common themes and distributions mentioned in the comments include:<br />
<br />
'''openSUSE (Leap and Tumbleweed):''' Many users prefer openSUSE for its stability, Yast configuration tool, and rolling release option (Tumbleweed).<br />
<br />
'''Debian:''' Known for its stability, Debian is a popular choice for servers and desktops, especially among those who don't want frequent updates.<br />
<br />
Ubuntu: Frequently chosen for its extensive software repositories, user-friendly nature, and long-term support (LTS) versions.<br />
<br />
'''Fedora:''' Chosen for its cutting-edge features, and Kinoite, a Fedora variant with features like Toolbox and Podman, was mentioned as providing an excellent experience.<br />
<br />
'''Arch Linux:''' Selected by users who appreciate the ability to customize their system, stay up-to-date with the latest software, and are comfortable with a DIY approach.<br />
CentOS / RHEL / Oracle Linux: Picked for their stability and reliability, especially in server environments.<br />
<br />
'''Kubuntu:''' A flavor of Ubuntu, known for its KDE desktop environment.<br />
<br />
'''Manjaro:''' Chosen for its user-friendliness and its close relationship with Arch Linux.<br />
<br />
'''Zorin OS:''' Known for its user-friendly interface, making it a good choice for beginners transitioning from other operating systems.<br />
<br />
'''Gentoo:''' Preferred by advanced users who appreciate the control and optimization it offers.<br />
<br />
'''NixOS:''' Selected for its unique approach to package management and system configuration.<br />
<br />
'''Solus:''' Used for light desktop usage and integration purposes.<br />
<br />
'''Amazon Linux:''' Employed in AWS environments due to compatibility.<br />
<br />
'''Alpine Linux:''' Known for its speedy package management.<br />
<br />
'''Garuda Linux:''' Used for home desktop use, offering unique KDE customizations.<br />
<br />
'''TrueNAS / Proxmox:''' Preferred for storage and virtualization purposes.<br />
<br />
'''Nix:''' Mentioned for its unique package management approach.<br />
<br />
'''Kali Linux:''' Chosen for testing and research.<br />
<br />
'''Raspberry Pi OS:''' Ideal for Raspberry Pi-based projects and systems.<br />
<br />
It's important to choose a distribution that aligns with your specific use case and preferences. Each distribution has its own strengths and weaknesses, so it's worthwhile to explore and experiment with different ones to find the best fit for your needs.<br />
<br />
=== In your opinion, what emerging IT trends or technologies show the most promise in the next three to five years? ===<br />
<br />
In the coming three to five years, several promising IT trends and technologies are emerging:<br />
<br />
'''Artificial Intelligence (AI):''' AI is a prominent trend, with applications in various fields such as natural language processing and machine learning. However, some are concerned about privacy issues associated with certain AI technologies.<br />
<br />
'''Advanced Connectivity (5G Networks):''' The deployment of 5G networks is expected to revolutionize connectivity and enable faster data transmission, benefiting various sectors.<br />
<br />
'''Web3:''' The transition to Web3, which is expected to enhance decentralized and blockchain-based internet services, is gaining attention.<br />
Trust Architectures: Technologies focused on trust and security, such as digital identity and secure architectures, are expected to play a crucial role in the coming years.<br />
<br />
'''Containerization:''' Container technologies and solutions, like Docker and Kubernetes, are being increasingly adopted for software deployment and management.<br />
<br />
'''Immutable Systems:''' Immutable operating systems and file systems are gaining popularity for their ability to enhance system stability and security.<br />
<br />
'''AI-Driven Game Development (e.g., Godot):''' AI is becoming integral in game development, automating various aspects of game design and rendering.<br />
<br />
'''WebAssembly:''' The use of WebAssembly for applications, system tuning, and system enhancements is on the rise.<br />
Security: Security is expected to remain a top concern, especially with the increasing use of cloud services and the need to protect sensitive data.<br />
<br />
'''Open Source and FOSS Adoption:''' There is a growing trend toward using open-source software and Linux-based solutions, focusing on transparency and control over data.<br />
<br />
'''Sustainability and Green IT:''' Sustainability and environmentally friendly technologies are becoming more significant as the IT industry explores eco-friendly solutions.<br />
<br />
'''Desktop Linux and Gaming:''' Desktop Linux is expected to gain more popularity, especially in the gaming sector, with trends like the Steam Deck driving its adoption.<br />
<br />
'''Generative AI:''' Generative AI technologies, like language models and image generation tools, are likely to have a growing impact in various domains.<br />
<br />
'''Quantum Computing:''' Quantum computing may become more accessible and find applications, particularly in cryptography and complex problem-solving.<br />
<br />
'''Edge Computing:''' Edge computing, which involves processing data closer to the source, is gaining importance, especially for IoT and autonomous systems.<br />
<br />
'''Data Analysis:''' The field of data analysis and analytics is expected to expand further, providing valuable insights for various industries.<br />
Rust Programming Language: The Rust programming language is gaining popularity for its safety and performance, contributing to software development tools.<br />
<br />
'''Digital Twins:''' The integration of multiple systems into digital twins is expected to advance, offering enhanced simulations and modeling.<br />
<br />
'''Augmented and Virtual Reality (AR/VR):''' AR and VR technologies are expected to evolve and find applications in various sectors.<br />
<br />
'''Machine Learning (LLM):''' Machine learning, particularly large language models (LLMs), is advancing rapidly and is likely to impact various aspects of computing.<br />
<br />
It's important to note that these trends may vary in significance based on the specific industry or field of interest. Additionally, privacy and security concerns, as well as environmental considerations, will continue to shape the development and adoption of emerging technologies.<br />
<br />
=== Do you believe Linux is well-positioned to meet the evolving needs of the market, including emerging technologies? Please explain. === <br />
<br />
Linux is well-positioned to meet the evolving needs of the market, especially in emerging technologies. Many comments in favor of Linux mention its stability, high performance, system administration capabilities, and open nature. It's widely used in server technologies, with a growing market share, and its versatility, openness, and flexibility make it suitable for various applications. Linux's popularity is increasing, with more support for open platforms and the adoption of emerging technologies.<br />
<br />
On the other hand, some comments express concerns about Linux's position, primarily in the desktop market. They mention issues related to the user experience and the absence of specific applications for end users, making it less competitive with commercial operating systems. However, there is hope that devices like the Steam Deck and increasing support for various technologies will improve Linux's position on the desktop.<br />
<br />
In summary, Linux's adaptability, open-source nature, and presence in the server and cloud markets make it well-suited to meet the evolving needs of the market, but there are challenges in expanding its desktop market share and improving user-friendliness.<br />
<br />
=== Are there any specific features or improvements you would like to see in Linux distributions to better support your use case(s)? ===<br />
<br />
The responses to the question about specific features or improvements desired in Linux distributions vary widely. Here's a summary of the key points:<br />
<br />
'''Professional Apps:''' Many respondents express the need for professional-grade applications on Linux. The lack of such software is seen as one of Linux's biggest challenges.<br />
<br />
'''Continuous Improvement:''' Some respondents believe that the open-source community is continually improving software packages, indicating satisfaction with the direction Linux is taking.<br />
<br />
'''User Assistance and Support:''' There's a call for better post-installation support, guidance on configuration optimization, and integration of AI-driven assistance.<br />
<br />
'''Contentment:''' Several users express their satisfaction with Linux, acknowledging its role in enabling their scientific achievements and revolutionary impact.<br />
<br />
'''Security and Encryption:''' Improved security features like systemd-homed, LUKS, TPM, and FIDO support are desired. Also, better integration of secure boot and device onboarding.<br />
<br />
'''Better Color Management:''' Enhanced color management, particularly in Wayland, is requested.<br />
<br />
'''Desktop Environment Switching:''' Users want more flexibility to switch between desktop environments without system-wide changes and advocate for declarative configuration.<br />
<br />
'''User-Friendly Permissions:''' Requests for simplified administration, like adding printers or editing files as admin via GUI editors without needing root access, are highlighted.<br />
<br />
'''Technical Compatibility:''' Improved compatibility with other Linux distributions, particularly Red Hat-based systems, in terms of package naming and structures, is desired.<br />
<br />
'''Tumbleweed and SlowRolls Relationship:''' Users appreciate the relationship between Tumbleweed and SlowRolls and hope to see similar cooperation among other distributions.<br />
<br />
'''Graphics and GPU Support:''' Enhanced support for graphics card settings and improved Intel Atom graphics drivers are mentioned.<br />
<br />
'''Virtualization:''' Better virtualization support for running OS/2 on KVM is requested.<br />
<br />
'''Remote Management Tools:''' Some users would like to see tooling for remote management and long-running, well-documented transactional distributions.<br />
<br />
'''Aesthetics:''' Aesthetically pleasing desktop environments and improved marketing are suggested for openSUSE.<br />
<br />
'''Debugging and Simplification:''' Users call for better debugging tools, enhanced organization, reduced duplicity, and increased simplicity.<br />
<br />
'''Power Management:''' Improved power management and better support for ARM64 platforms are mentioned.<br />
<br />
'''Finance and Desktop Distribution:''' Some users believe that Linux companies should take finance platforms more seriously and develop desktop distributions accordingly.<br />
<br />
'''Appealing Desktop Environments:''' Better desktop environments that are welcoming to newcomers not well-versed in the command line are desired.<br />
<br />
'''Tumbleweed Defaults:''' Users hope for better default configurations in Tumbleweed.<br />
<br />
'''Concerns about the Future:''' Some express concerns about the direction of openSUSE, particularly related to changes like the termination of Leap and a shift towards microservices and containerization.<br />
<br />
'''Package Management:''' A desire for more straightforward package management and simplicity with a focus on immutability is mentioned.<br />
<br />
'''Hardware Support:''' Better support for newer hardware, including graphics cards, graphic tablets, and touchscreens, is requested.<br />
HDR Support: Improved HDR support is desired.<br />
<br />
'''Linux on IoT Devices:''' Users emphasize the importance of free, open, stable distributions for developing IoT products.<br />
<br />
'''Linux for Artists:''' Better support for graphic tablets and artistic tools is mentioned.<br />
<br />
'''User-Friendly Updates:''' Users call for a more user-friendly approach to handling system updates.<br />
<br />
'''Version Management:''' Users want easier management of components with multiple versions.<br />
<br />
'''Ease of Use:''' Simplicity, ease of use, and an easier entry point for new users are recurring themes.<br />
<br />
'''Documentation:''' There's a call for better documentation and information about how to install the OS.<br />
<br />
'''Security Configuration:''' Simplifying the configuration of security measures like firewalls and AppArmor is requested.<br />
<br />
'''PHP Version Management:''' Some users express the need for easier management of PHP versions.<br />
<br />
'''Driver Management:''' Better driver management, particularly for video cards, is desired.<br />
<br />
'''Containerization:''' Users express concerns about the growing complexity due to container-based solutions and their impact on the average desktop user.<br />
<br />
'''Init System:''' Some users want alternatives to the systemd init system.<br />
<br />
'''Wayland and HDR Support:''' Better Wayland support and HDR capabilities are desired.<br />
<br />
'''Windows Compatibility:''' Users hope for better compatibility with Windows applications, particularly for proprietary software.<br />
<br />
'''Update Management:''' Easier management of updates, including improved management of multiple versions of software components, is requested.<br />
<br />
'''File Management:''' Users want better drag and drop functionality for files.<br />
<br />
'''Repository Management:''' Easier management of software repositories is requested.<br />
<br />
'''NAS Distribution:''' Some users would like to see an openSUSE-based NAS distribution.<br />
<br />
'''openSUSE Repositories:''' Requests for more packages in openSUSE repositories and a ports system like Arch's AUR are made.<br />
<br />
'''KDE Support:''' Users ask for continued support for KDE on openSUSE Tumbleweed.<br />
<br />
'''Server and Desktop Needs:''' Users emphasize the importance of different distributions for server and desktop needs, with specific stability requirements.<br />
<br />
'''Graphics Support:''' Better graphics support, including improved drivers for older and new hardware, is desired.<br />
Improved Desktop Experience: Users express the need for an improved desktop experience, including support for peripherals and reducing complications.<br />
<br />
'''LSB Standardization:''' Some users call for standardizing on the Linux Standard Base (LSB) for easier application development.<br />
Focusing on Support: OpenSUSE is urged to focus on offering support through books, training, and knowledge sharing.<br />
<br />
'''Geoinformatics Tools:''' Users express a need for better tools for geoinformatics on openSUSE.<br />
<br />
'''Electron App Rendering:''' Users are frustrated with how Electron-based applications render on Wayland compositors.<br />
<br />
'''Marketing and Awareness:''' Better marketing and efforts to increase Linux adoption and awareness are suggested.<br />
Please note that the variety of responses reflects the diverse needs and expectations of Linux users across different use cases.<br />
<br />
=== Would you recommend Linux to others in your industry for the use cases you've explored? Why or why not? ===<br />
<br />
The comments reflect a wide range of opinions regarding recommending Linux in various industries and use cases. Some key points that emerge from these comments are:<br />
<br />
'''Server Workloads:''' Linux is highly recommended for server workloads. It is praised for its stability, performance, and its ability to ease the management of distributed computing instances. It is seen as the best option for these scenarios, with no real alternatives.<br />
<br />
'''Development and Privacy:''' Many people recommend Linux for development purposes, highlighting its flexibility, openness, and privacy features. It's viewed as a superior platform for coding and learning new things.<br />
<br />
'''Customization and Freedom:''' Linux is praised for its customizability and the freedom it provides to users. It's seen as a system that lets you have more control and tailor it to your specific needs.<br />
<br />
'''Cost Savings:''' Some recommend Linux because it's free and open source, which can save money compared to proprietary alternatives like Windows.<br />
Security: Security-conscious users appreciate Linux for its robust security features.<br />
<br />
'''Mixed Recommendations:''' Some express hesitation about recommending Linux for certain use cases. They point out that Linux might not be suitable for everyone and that there can be limitations, especially in environments that rely heavily on proprietary software.<br />
<br />
'''Challenges with Gaming and Compatibility:''' Gaming is mentioned as a challenge, but there's optimism about Linux's future in this area due to the improvement of tools like Proton.<br />
<br />
'''Specific Use Cases:''' Recommendations vary depending on the use cases and the specific requirements of the industry. Some industries might be more receptive to Linux than others.<br />
<br />
'''Learning Curve:''' The comments highlight the need for users to be somewhat tech-savvy and willing to adapt to a different operating system.<br />
Support and Knowledge: The availability of Linux expertise and support is mentioned as a critical factor when recommending it.<br />
<br />
In summary, Linux is highly recommended for server workloads, development, and privacy-conscious users. However, the suitability of Linux for a particular industry or use case often depends on factors like software compatibility, user expertise, and the willingness to adapt to a different operating system.</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=File:Usecase2023-usecases.svg&diff=181130File:Usecase2023-usecases.svg2023-11-06T12:21:05Z<p>Bmwiedemann: Bmwiedemann uploaded a new version of File:Usecase2023-usecases.svg</p>
<hr />
<div>== Summary ==<br />
made with libreoffice-calc -> draw -> inkscape</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=File:Usecase2023-usecases.svg&diff=181127File:Usecase2023-usecases.svg2023-11-06T12:18:21Z<p>Bmwiedemann: made with libreoffice-calc -> draw -> inkscape</p>
<hr />
<div>== Summary ==<br />
made with libreoffice-calc -> draw -> inkscape</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=Usecase2023&diff=181124Usecase20232023-11-06T11:17:29Z<p>Bmwiedemann: add stacked bar chart</p>
<hr />
<div>The following is a summary of the use case survey run by openSUSE during the month of October 2023. The full results are listed in the [[File:Usecase2023.pdf|Use Case 2023 report]].<br />
<br />
= Intro Questions: Results =<br />
<br />
=== What best describes your use of IT? ===<br />
Work/business (SQ001) 146 9.24%<br />
Home/Hobby (SQ002) 450 28.48%<br />
Both (SQ003) 656 41.52%<br />
No answer 21 1.33%<br />
Not completed or Not displayed 307 19.43%<br />
<br />
== Summary ==<br />
<br />
A recent survey provides a breakdown of the use cases of Linux among respondents based on their primary use of IT:<br />
<br />
[[File:Usecase2023-use-of-IT.svg]]<br />
<br />
* Work/Business: 9.24% of respondents primarily use Linux for work or business-related purposes.<br />
* Home/Hobby: 28.48% of respondents use Linux for home or hobby activities.<br />
* Both: 41.52% of respondents use Linux for both work/business and home/hobby purposes.<br />
* No answer: 1.33% of respondents did not provide an answer regarding their IT use.<br />
* Not completed or not displayed: 19.43% of respondents' information was not completed or displayed.<br />
<br />
The survey also assessed the use of various IT technologies on a scale of 1 to 5 (1 meaning little use and 5 being primary use) across different domains:<br />
<br />
* Cloud Computing: Most respondents (41.70%) rated their use of Linux for cloud computing as 1 (little use), while a significant portion (13.51%) rated it as 5 (primary use).<br />
* Containerization: 34.68% rated their use of containerization as 1 (little use), and 13.84% rated it as 5 (primary use).<br />
* Configuration Management: 30.53% rated their use of configuration management as 1 (little use), and 27.17% rated it as 5 (primary use).<br />
* Desktop Computing: 81.22% of respondents primarily use Linux for desktop computing (rated 5), while only a small portion (3.27%) rated it as 1 (little use).<br />
* Server Infrastructure: 26.53% rated their use of Linux for server infrastructure as 5 (primary use), and 29.95% rated it as 1 (little use).<br />
* Serverless Computing: 64.34% primarily use Linux for serverless computing (rated 5), while 12.49% rated it as 5 (primary use).<br />
* Virtualization: 20.20% rated their use of Linux for virtualization as 5 (primary use), and 23.04% rated it as 1 (little use).<br />
* Edge Computing: 68.36% primarily use Linux for edge computing (rated 5), while 3.76% rated it as 5 (primary use).<br />
* IoT Applications: 64.95% primarily use Linux for IoT applications (rated 5), and 4.54% rated it as 5 (primary use).<br />
* Machine Learning: 68.64% primarily use Linux for machine learning (rated 5), and 4.19% rated it as 5 (primary use).<br />
* Blockchain: A significant majority (89.00%) of respondents indicated little use of Linux for blockchain (rated 1).<br />
* Gaming: 31.04% primarily use Linux for gaming (rated 5), and 25.58% rated it as 1 (little use).<br />
* Other: For other use cases, 28.88% primarily use Linux (rated 5), and 24.67% rated it as 1 (little use).<br />
<br />
Please note that these percentages represent the distribution of responses among the survey participants.<br />
<br />
=== Cloud computing ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 460 41.70% 58.20%<br />
2 (2) 182 16.50%<br />
3 (3) 192 17.41% 17.41%<br />
4 (4) 120 10.88%<br />
5 (5) 149 13.51% 24.39%<br />
No answer 170 10.76% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Containerization ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 386 34.68% 52.83%<br />
2 (2) 202 18.15%<br />
3 (3) 193 17.34% 17.34%<br />
4 (4) 178 15.99%<br />
5 (5) 154 13.84% 29.83%<br />
No answer 160 10.13% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Configuration Management ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 327 30.53% 50.61%<br />
2 (2) 215 20.07%<br />
3 (3) 238 22.22% 22.22%<br />
4 (4) 164 15.31%<br />
5 (5) 127 11.86% 27.17%<br />
No answer 202 12.78% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Desktop Computing ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 40 3.27% 4.65%<br />
2 (2) 17 1.39%<br />
3 (3) 63 5.14% 5.14%<br />
4 (4) 110 8.98%<br />
5 (5) 995 81.22% 90.20%<br />
No answer 48 3.04% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Server Infrastructure ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 333 29.95% 43.79%<br />
2 (2) 154 13.85%<br />
3 (3) 188 16.91% 16.91%<br />
4 (4) 142 12.77%<br />
5 (5) 295 26.53% 39.30%<br />
No answer 161 10.19% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Serverless Computing ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 608 64.34% 76.61%<br />
2 (2) 116 12.28%<br />
3 (3) 103 10.90% 10.90%<br />
4 (4) 54 5.71%<br />
5 (5) 64 6.77% 12.49%<br />
No answer 328 20.76% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Virtualization ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 259 23.04% 39.95%<br />
2 (2) 190 16.90%<br />
3 (3) 238 21.17% 21.17%<br />
4 (4) 210 18.68%<br />
5 (5) 227 20.20% 38.88%<br />
No answer 149 9.43% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Edge Computing ===<br />
Rate your use of IT 1 through 5? (1 meaning litttle use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 618 68.36% 80.09%<br />
2 (2) 106 11.73%<br />
3 (3) 90 9.96% 9.96%<br />
4 (4) 56 6.19%<br />
5 (5) 34 3.76% 9.96%<br />
No answer 369 23.35% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== IoT Applications ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 630 64.95% 81.24%<br />
2 (2) 158 16.29%<br />
3 (3) 93 9.59% 9.59%<br />
4 (4) 45 4.64%<br />
5 (5) 44 4.54% 9.18%<br />
No answer 303 19.18% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Machine Learning ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 672 68.64% 81.92%<br />
2 (2) 130 13.28%<br />
3 (3) 89 9.09% 9.09%<br />
4 (4) 47 4.80%<br />
5 (5) 41 4.19% 8.99%<br />
No answer 294 18.61% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Blockchain ===<br />
Rate your use of IT 1 through 5? (1 meaning litttle use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 833 89.00% 94.98%<br />
2 (2) 56 5.98%<br />
3 (3) 28 2.99% 2.99%<br />
4 (4) 9 0.96%<br />
5 (5) 10 1.07% 2.03%<br />
No answer 337 21.33% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Gaming ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 286 25.58% 36.40%<br />
2 (2) 121 10.82%<br />
3 (3) 180 16.10% 16.10%<br />
4 (4) 184 16.46%<br />
5 (5) 347 31.04% 47.50%<br />
No answer 155 9.81% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
=== Other ===<br />
Rate your use of IT 1 through 5? (1 meaning little use and 5 being primary use)<br />
<br />
Answer Count Percentage Sum<br />
1 (1) 170 24.67% 31.93%<br />
2 (2) 50 7.26%<br />
3 (3) 184 26.71% 26.71%<br />
4 (4) 86 12.48%<br />
5 (5) 199 28.88% 41.36%<br />
No answer 584 36.96% 0.00%<br />
Not completed or Not displayed 307 19.43% 0.00%<br />
<br />
= Distro Use Cases =<br />
<br />
What did people say the use cases are for the following distros.<br />
<br />
=== Tumbleweed ===<br />
The use cases for openSUSE Tumbleweed are diverse and cover a wide range of activities. Users rely on Tumbleweed for internet browsing, programming, note-taking, music listening, and even gaming. It serves as a daily driver for many, including office applications and software development. Tumbleweed is used on both servers and desktops, and some users appreciate its continuous rolling updates and cutting-edge features. It's employed for testing purposes, container environments, and experimental features. For many, Tumbleweed is their main operating system, offering a combination of stability and the latest software. It is a preferred choice for development, multimedia, and daily personal tasks, including watching videos and listening to music. In summary, openSUSE Tumbleweed caters to a broad spectrum of users, from developers to gamers, offering a rolling release experience with a focus on keeping software up to date and stable.<br />
<br />
=== Leap ===<br />
openSUSE Leap serves a variety of purposes for its users. It is utilized for tasks like club finance management, personal finance management, photography archive and management, document production, and family communication. Some users rely on it as a stable and reliable system for both desktop and server needs. It's commonly used as a home server, NAS, and for various server applications.<br />
openSUSE Leap is praised for its stability, bulletproof performance, and reliability, making it an excellent choice for server-related tasks. Some users appreciate the fact that it doesn't require constant upgrades and provides a consistent interface throughout its supported lifespan.<br />
<br />
On the desktop side, it's used for general computing, including internet usage, document handling, and multimedia activities. Some users prefer it as their primary operating system, emphasizing its stability for everyday tasks. Additionally, openSUSE Leap is chosen for its compatibility with SUSE's enterprise-grade distributions, making it an ideal choice for learning more about SUSE.<br />
In summary, openSUSE Leap caters to users who prioritize stability and a consistent experience, both on the desktop and for server-related tasks. It is a reliable choice for various computing needs, including personal, professional, and educational use cases.<br />
<br />
=== MicroOS (Aeon, Kalpa, Server) ===<br />
openSUSE MicroOS (Aeon, Kalpa, Server) caters to a diverse range of use cases. Users are interested in its potential, including for desktop and server applications, as well as IoT devices. It is seen as a solution for low-end computers and container hosting, with some users emphasizing its role as a Kubernetes (K8s) platform.<br />
<br />
While some are not interested in or do not see advantages in MicroOS, others are exploring it for development, testing, and experimentation purposes. It is used for work, college, gaming, and home server needs.<br />
<br />
Despite mixed opinions, openSUSE MicroOS is being considered for various scenarios, from providing secure, immutable desktop environments to running containers and virtualization. Some users appreciate its self-maintenance and update handling, making it an attractive option for server and IoT applications.<br />
<br />
In summary, openSUSE MicroOS serves a wide spectrum of use cases, from professional and hobby development to secure and low-maintenance server and desktop setups. It is an intriguing option for those seeking to explore the benefits of an immutable operating system.<br />
<br />
=== Leap Micro ===<br />
Users have varying opinions and use cases for openSUSE Leap Micro. While some express disinterest and see no advantage in this system, others are experimenting with it, primarily as a container host or server. Some are waiting for it to become generally available for desktop use, indicating a potential future application as a desktop OS.<br />
<br />
A common theme is its role in containerization and virtualization, with users mentioning experiments with containers and the use of Leap Micro on servers. Some users are considering it for home labing and self-hosting purposes, while others are planning to test it for specific projects.<br />
<br />
In summary, openSUSE Leap Micro has a range of potential use cases, primarily centered around containers, virtualization, and server applications, with some users exploring it for future desktop use.<br />
<br />
=== Slowroll ===<br />
openSUSE SlowRoll is a new distribution that aims to bridge the gap between the stable but aging Leap and the cutting-edge but fast-paced Tumbleweed. It is a rolling release that updates on a monthly basis, providing users with a balance of freshness and stability. Many users are interested in SlowRoll for various reasons, such as:<br />
<br />
* Server Use: Some users find SlowRoll appealing for server use, as it offers a modern but reliable OS that does not require frequent updates or major upgrades. Some users also hope for better integration with docker and other tools.<br />
* Stable Base: Some users prefer a stable base that does not change too often, but still provides access to newer software and features. Some users compare SlowRoll to FreeBSD’s RELEASE or STABLE branches, or to older versions of openSUSE that they miss.<br />
* Lower Surprise: Some users want to avoid surprises or breakages that may occur with Tumbleweed’s rapid updates. They also want to reduce the size of update downloads and the frequency of update notifications.<br />
* Faster GNOME/KDE: Some users are eager to get the latest versions of GNOME or KDE faster than Leap, without having to switch to Tumbleweed. They value the user experience and the performance of these desktop environments.<br />
* Leap Alternative: Some users are looking for an alternative to Leap that would eliminate the need for major upgrades every 18 months. They also want to avoid the obsolescence of some packages in Leap.<br />
<br />
SlowRoll may not be suitable for everyone; some users are happy with Tumbleweed or Leap, and some doubt the viability of SlowRoll. However, SlowRoll has the potential to attract a new group of users who are looking for a recent and stable distribution that updates at a moderate pace.<br />
<br />
Reasons for use include:<br />
reasons why users are interested in openSUSE SlowRoll and what makes this distribution appealing to them:<br />
<br />
* Balancing Stability and Freshness: Many users appreciate the desire for a distribution that strikes a balance between stability and up-to-date software. They find SlowRoll to be a compromise between the highly stable Leap and the rapidly updating Tumbleweed.<br />
<br />
* Server-Friendly: Some users see SlowRoll as a suitable option for server environments where stability is crucial, and frequent updates may pose challenges.<br />
<br />
* Predictable Update Cadence: The regular monthly updates of SlowRoll are seen as a convenient and predictable way to keep the system current without the need for frequent large-scale upgrades.<br />
<br />
* User-Friendly for Beginners: SlowRoll is considered a good option for beginners or family members who may not be comfortable with frequent updates or complex upgrade processes.<br />
<br />
* Addressing the Leap Transition: Some users express interest in SlowRoll due to concerns about Leap's future. They are looking for a stable alternative.<br />
<br />
* Better Software Compatibility: SlowRoll is seen as a way to achieve better software compatibility compared to Tumbleweed, particularly for those not wanting to deal with frequent updates.<br />
<br />
* Reduced Update Frequency: Users with limited internet connectivity or older hardware appreciate the less frequent updates, reducing data usage and performance strain.<br />
<br />
* Maintaining Stability: SlowRoll aims to offer stable updates while avoiding potential breakages that can occur with more frequent updates.<br />
Transition from Leap: As Leap users face a transition, SlowRoll is considered a suitable alternative, providing a rolling release with a slower update pace.<br />
<br />
* Slower Cadence for Secondary Devices: SlowRoll is seen as ideal for secondary devices that are not used as frequently and don't require the same rapid update cycle as Tumbleweed.<br />
<br />
* Improved Software Management: Users want an efficient way to manage software without redundant updates and hope SlowRoll addresses this issue.<br />
<br />
* Sustainability: Some users appreciate the slower update pace for its potential sustainability benefits and reduced load on openSUSE infrastructure.<br />
<br />
* Experimental Interest: Some express curiosity about SlowRoll but may not be convinced of its value or specific use case yet.<br />
<br />
= Home/Hobby Use: Questions & Results =<br />
<br />
== Summary ==<br />
In the survey, respondents reported their use of various technologies at home and as services. Notably, 10.82% use cloud computing at home, 36.90% use desktop computing, and 26.65% use gaming technologies. Conversely, 30.13% do not use blockchain at home, and 27.78% do not use edge computing. In terms of services, 12.34% use desktop computing, while 25.95% use machine learning. Additionally, 5.57% of respondents are not interested in the Adaptable Linux Platform. The survey provides insights into the adoption of these technologies among home and hobby users.<br />
<br />
=== Cloud computing ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 171 10.82%<br />
No (AO02) 356 22.53%<br />
No answer 100 6.33%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 198 12.53%<br />
No (AO02) 281 17.78%<br />
No answer 148 9.37%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Containerization ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 298 18.86%<br />
No (AO02) 244 15.44%<br />
No answer 85 5.38%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 108 6.84%<br />
No (AO02) 361 22.85%<br />
No answer 158 10.00%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Configuration Management ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 216 13.67%<br />
No (AO02) 295 18.67%<br />
No answer 116 7.34%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 76 4.81%<br />
No (AO02) 386 24.43%<br />
No answer 165 10.44%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Desktop Computing ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 583 36.90%<br />
No (AO02) 10 0.63%<br />
No answer 34 2.15%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 195 12.34%<br />
No (AO02) 300 18.99%<br />
No answer 132 8.35%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Server Infrastructure ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 260 16.46%<br />
No (AO02) 278 17.59%<br />
No answer 89 5.63%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 136 8.61%<br />
No (AO02) 328 20.76%<br />
No answer 163 10.32%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Serverless Computing ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 75 4.75%<br />
No (AO02) 416 26.33%<br />
No answer 136 8.61%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 37 2.34%<br />
No (AO02) 410 25.95%<br />
No answer 180 11.39%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Virtualization ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 377 23.86%<br />
No (AO02) 171 10.82%<br />
No answer 79 5.00%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 135 8.54%<br />
No (AO02) 338 21.39%<br />
No answer 154 9.75%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Edge Computing ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 47 2.97%<br />
No (AO02) 439 27.78%<br />
No answer 141 8.92%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 20 1.27%<br />
No (AO02) 417 26.39%<br />
No answer 190 12.03%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== IoT Applications ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 133 8.42%<br />
No (AO02) 376 23.80%<br />
No answer 118 7.47%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 62 3.92%<br />
No (AO02) 390 24.68%<br />
No answer 175 11.08%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Machine Learning ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 92 5.82%<br />
No (AO02) 410 25.95%<br />
No answer 125 7.91%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 47 2.97%<br />
No (AO02) 398 25.19%<br />
No answer 182 11.52%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Blockchain ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 21 1.33%<br />
No (AO02) 476 30.13%<br />
No answer 130 8.23%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 14 0.89%<br />
No (AO02) 432 27.34%<br />
No answer 181 11.46%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Gaming ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 421 26.65%<br />
No (AO02) 131 8.29%<br />
No answer 75 4.75%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 165 10.44%<br />
No (AO02) 301 19.05%<br />
No answer 161 10.19%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
=== Other ===<br />
What of the following do you use at home? (Select all that apply)<br />
<br />
Yes (AO01) 245 15.51%<br />
No (AO02) 124 7.85%<br />
No answer 258 16.33%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
What of the following do you use at home as a service? (Select all that apply)<br />
<br />
Yes (AO01) 116 7.34%<br />
No (AO02) 223 14.11%<br />
No answer 288 18.23%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
== Are you interested in the Adaptable Linux Platform? ==<br />
Yes (Y) 286 18.10%<br />
No (N) 168 10.63%<br />
No answer 173 10.95%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
== Are you interested in the new distribution Slowroll? ==<br />
Yes (Y) 340 21.52%<br />
No (N) 154 9.75%<br />
No answer 133 8.42%<br />
Not completed or Not displayed 953 60.32%<br />
<br />
= Work/Business Use: Questions & Results =<br />
<br />
== Summary ==<br />
In the survey, approximately 15% of respondents reported using Cloud Computing for work/business, while around 16% reported using it as a service. Similarly, around 15-18% used technologies like Containerization, Configuration Management, Desktop Computing, Server Infrastructure, Serverless Computing, and Virtualization for work/business, and 10-13% used them as services.<br />
<br />
=== Cloud computing ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 240 15.19%<br />
No (AO02) 141 8.92%<br />
No answer 44 2.78%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 257 16.27%<br />
No (AO02) 112 7.09%<br />
No answer 56 3.54%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Containerization ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 244 15.44%<br />
No (AO02) 138 8.73%<br />
No answer 43 2.72%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 168 10.63%<br />
No (AO02) 187 11.84%<br />
No answer 70 4.43%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Configuration Management ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 235 14.87%<br />
No (AO02) 133 8.42%<br />
No answer 57 3.61%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 147 9.30%<br />
No (AO02) 194 12.28%<br />
No answer 84 5.32%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Desktop Computing ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 352 22.28%<br />
No (AO02) 44 2.78%<br />
No answer 29 1.84%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 172 10.89%<br />
No (AO02) 187 11.84%<br />
No answer 66 4.18%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Server Infrastructure ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 292 18.48%<br />
No (AO02) 91 5.76%<br />
No answer 42 2.66%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 242 15.32%<br />
No (AO02) 114 7.22%<br />
No answer 69 4.37%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Serverless Computing ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 90 5.70%<br />
No (AO02) 262 16.58%<br />
No answer 73 4.62%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 102 6.46%<br />
No (AO02) 221 13.99%<br />
No answer 102 6.46%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Virtualization ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 275 17.41%<br />
No (AO02) 107 6.77%<br />
No answer 43 2.72%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 198 12.53%<br />
No (AO02) 146 9.24%<br />
No answer 81 5.13%<br />
<br />
=== Edge Computing ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 70 4.43%<br />
No (AO02) 264 16.71%<br />
No answer 91 5.76%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 61 3.86%<br />
No (AO02) 256 16.20%<br />
No answer 108 6.84%<br />
<br />
=== IoT Applications ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 61 3.86%<br />
No (AO02) 288 18.23%<br />
No answer 76 4.81%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 60 3.80%<br />
No (AO02) 260 16.46%<br />
No answer 105 6.65%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Machine Learning ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 100 6.33%<br />
No (AO02) 249 15.76%<br />
No answer 76 4.81%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 74 4.68%<br />
No (AO02) 243 15.38%<br />
No answer 108 6.84%<br />
<br />
=== Blockchain ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 17 1.08%<br />
No (AO02) 327 20.70%<br />
No answer 81 5.13%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 14 0.89%<br />
No (AO02) 305 19.30%<br />
No answer 106 6.71%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Gaming ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 43 2.72%<br />
No (AO02) 315 19.94%<br />
No answer 67 4.24%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 28 1.77%<br />
No (AO02) 298 18.86%<br />
No answer 99 6.27%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
=== Other ===<br />
What of the following do you use for work/business use? (Select all that apply)<br />
Yes (AO01) 122 7.72%<br />
No (AO02) 115 7.28%<br />
No answer 188 11.90%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
What of the following do you/your company use as a service? (Select all that apply<br />
Yes (AO01) 87 5.51%<br />
No (AO02) 146 9.24%<br />
No answer 192 12.15%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
== Are you interested in the Adaptable Linux Platform? ==<br />
Yes (Y) 216 13.67%<br />
No (N) 88 5.57%<br />
No answer 121 7.66%<br />
Not completed or Not displayed 1155 73.10%<br />
<br />
= Service Satisfaction =<br />
<br />
== Summary ==<br />
In the survey, respondents expressed dissatisfaction with various IT services for different reasons. For Cloud Computing, dissatisfaction stemmed from security concerns, high costs, and integration challenges. For Containerization, users desired better security and automation tools. Configuration Management users sought improved online management and flexibility. Desktop Computing users wanted better graphical upgrades and software deployment. Server Infrastructure dissatisfaction arose from cost concerns and the need for better management tools. Serverless Computing users desired innovation and improved security. Virtualization users faced challenges with installation and performance. Edge Computing users wanted better automation and security. IoT Applications users found services confusing and called for innovation. Machine Learning users preferred open-source solutions and performance improvements. Blockchain dissatisfaction was expressed without specific details. Gaming users desired better gaming support, compatibility, and performance. Other services dissatisfaction ranged from the lack of a virtual keyboard to compatibility issues with corporate applications, with some users recommending open-source solutions.<br />
<br />
=== Cloud computing ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 73 4.62%<br />
Not Satisfied (AO02) 34 2.15%<br />
Neutral (AO03) 110 6.96%<br />
Satisfied (AO04) 133 8.42%<br />
No answer 75 4.75%<br />
<br />
Many individuals expressed dissatisfaction with the cloud computing services used by their company for various reasons. Security concerns were a recurring theme, with some pointing out that they don't trust the security of cloud providers' systems. High costs and the need for significant application integration were common complaints, with a desire for more cost-effective and flexible options. Others emphasized the importance of performance, management, and visibility, as well as reliability. Some expressed frustration with the slow speeds and painful experiences when using cloud folders. There was also a dislike for monopolies and a desire to reduce dependence on Microsoft and Google products. Open source solutions and a preference for on-premises cloud like Kubernetes were mentioned. Standardization and open standards were proposed to make cloud services more user-friendly and compatible. The complexity of some cloud services for simpler tasks and the lack of specialized tech personnel were also cited as issues. A multi-cloud approach and the use of free and open-source software (FLOSS) services were advocated for. In summary, dissatisfaction with cloud computing services primarily stemmed from concerns about security, cost, integration, and the desire for more standardized and user-friendly solutions.<br />
<br />
=== Containerization ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 96 6.08%<br />
Not Satisfied (AO02) 18 1.14%<br />
Neutral (AO03) 86 5.44%<br />
Satisfied (AO04) 127 8.04%<br />
No answer 98 6.20%<br />
<br />
People who answered express dissatisfaction with their current containerization services for various reasons. Some of them highlight the need for migration to Rancher, which they see as a more suitable option for managing Docker containers. They also emphasize the importance of better security and management, with a desire for improved tools for pipeline building and automation. Additionally, there's a need for increased awareness of containerization benefits among managers and a desire for on-premises solutions, though cost is a concern. Other aspects include a lack of security updates, slow performance with an OS, a deficit of knowledge for implementation, and limited usage, making improvement challenging. Overall, the dissatisfaction stems from issues with security, performance, management, and a lack of alignment with the company's future plans.<br />
<br />
=== Configuration Management ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 92 5.82%<br />
Not Satisfied (AO02) 25 1.58%<br />
Neutral (AO03) 93 5.89%<br />
Satisfied (AO04) 105 6.65%<br />
No answer 110 6.96%<br />
<br />
People who answered express dissatisfaction with the current Configuration Management services for various reasons. They desire better online management capabilities and complain about the lack of quality examples for writing Salt statements to manage the infrastructure effectively. Additionally, they wish for more flexibility in managing flatpaks and containers through YaST. The need for making configurations less dependent on the OS and promoting innovation is emphasized. There's a call for increased automation with Uyuni and a desire for better tools for user management and security within YaST.<br />
Some express discontent with the current use of Git and GitLab, citing issues with these tools. Security concerns are raised as well, indicating a need for improvement in this area. Others seek more awareness of the benefits of Configuration Management among managers. Some feel that the existing system has too many issues and could be significantly improved. They prefer standard patterns over custom solutions and are cautious about depending on Microsoft Active Directory. However, a few individuals are content with the current setup and see no need for improvement. The dissatisfaction largely revolves around issues of tool quality, security, and the desire for more user-friendly and effective solutions.<br />
<br />
<br />
=== Desktop Computing ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 59 3.73%<br />
Not Satisfied (AO02) 38 2.41%<br />
Neutral (AO03) 69 4.37%<br />
Satisfied (AO04) 183 11.58%<br />
No answer 76 4.81%<br />
<br />
People who answered express a wide range of dissatisfaction with the current Desktop Computing services they use. They desire better graphical upgrades, full interoperability, and suggest the use of Linux for a more seamless desktop experience. Some request that desktop environments like GNOME adopt a more traditional configuration style.<br />
There are concerns about the current implementation, management, updates, and deployment of desktop systems. Users are looking for improvements in security, graphics card support, and the availability of HDR support for KDE Plasma and Firefox.<br />
<br />
Some express a preference for openSUSE over Windows but face challenges with VPN setup. Others wish for a corporate-branded openSUSE installation, longer lifecycles, and simplified user experiences, especially for new users.<br />
Linux is seen as a viable alternative to Windows, but concerns remain about software compatibility and the need for better codecs and hardware acceleration. The desire to standardize to one desktop environment is evident, and some users wish to see fewer proprietary software packages and a shift towards Linux workstations.<br />
<br />
In general, dissatisfaction is rooted in issues of software reliability, security, the use of proprietary software, and the desire for more freedom in choosing their desktop environment. Many have varied preferences and concerns regarding the use of Linux, Windows, and cloud-based solutions.<br />
<br />
=== Server Infrastructure ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 49 3.10%<br />
Not Satisfied (AO02) 22 1.39%<br />
Neutral (AO03) 76 4.81%<br />
Satisfied (AO04) 188 11.90%<br />
No answer 90 5.70%<br />
<br />
People who responded express their dissatisfaction with the current server infrastructure services for various reasons. Some suggest a shift from Windows servers to Linux for a more cost-effective and flexible solution. Concerns are raised about the cost of integrating less expensive options and a desire for more tools to provision bare metal servers.<br />
<br />
Innovation and improved functionality for Yast2cli are highlighted as areas of improvement. Some acknowledge that there has been self-inflicted mismanagement of Linux, which may have impacted the server infrastructure. Security is cited as a major concern, emphasizing the need for better protection.<br />
There's a call for hosting more services and implementing a self-service portal to streamline server requests. A stable base for long-supported applications is deemed crucial, and outside input and best practices are welcomed. Cost management is stressed, urging a more efficient use of resources and a focus on reducing expenses.<br />
<br />
The use of open-source (FLOSS) services is encouraged, and some express the need to move away from AWS, possibly in search of more predictable performance and access to bare metal machines for critical applications. In summary, dissatisfaction with server infrastructure services is rooted in concerns about cost, security, performance, and the desire for more innovation and flexibility.<br />
<br />
=== Serverless Computing ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 174 11.01%<br />
Not Satisfied (AO02) 8 0.51%<br />
Neutral (AO03) 56 3.54%<br />
Satisfied (AO04) 44 2.78%<br />
No answer 143 9.05%<br />
<br />
People who responded express their dissatisfaction with the current serverless computing services for various reasons. The need for innovation in these services is highlighted, suggesting a desire for improvements and advancements in functionality.<br />
<br />
Security is a major concern, with users expressing that the existing security measures are inadequate. Some take a skeptical view of serverless computing, asserting that it's an everyday reality that software still needs to run somewhere, potentially indicating a preference for more traditional approaches.<br />
Others mention that the services are not currently in use, making it difficult to assess and improve them. Additionally, the cost-effectiveness of serverless computing is questioned, with a sentiment that it can be more expensive by design. The advice given is to use it sparingly, primarily when IT is not the core business, and to avoid overusing it.<br />
<br />
In summary, dissatisfaction with serverless computing services is driven by concerns about innovation, security, cost, and the practicality of this approach in the context of the company's needs and objectives.<br />
<br />
=== Virtualization ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 71 4.49%<br />
Not Satisfied (AO02) 17 1.08%<br />
Neutral (AO03) 84 5.32%<br />
Satisfied (AO04) 148 9.37%<br />
No answer 105 6.65%<br />
<br />
People who responded express their dissatisfaction with the current virtualization services for various reasons. They find it difficult to install a Windows 11 machine, highlighting the need for better integration of virtualization hosts, a task that some are willing to work on when they have time.<br />
<br />
The speed of I/O and the performance of virtualization are of concern, and users want easier installation and usage with improved performance. There is a call for innovation in virtualization services.<br />
<br />
Issues with VirtualBox's speed and network firewall rules are raised, suggesting a need for better management GUI tools for multiple KVM hosts. Security is criticized, and users want the ability to use virtual machines for testing without needing to install temporary tools on the host OS.<br />
<br />
Some express a desire for an alternative to VMWare, with a mention of a lack of competitive offerings. Better infrastructure management and increased speed are sought, although there are concerns about the performance of an OS. Users want more flexibility in VM creation, including GPU passthrough.<br />
<br />
While some express contentment with the existing services, there are also requests for better virtualization management tools, the use of open-source (FLOSS) services, and better performance for database servers on Azure Virtual Desktop (AVD).<br />
<br />
In summary, dissatisfaction with virtualization services revolves around installation difficulties, performance, management, security, and the desire for more flexibility and innovation in the virtualization environment.<br />
<br />
=== Edge Computing ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 195 12.34%<br />
Not Satisfied (AO02) 7 0.44%<br />
Neutral (AO03) 52 3.29%<br />
Satisfied (AO04) 27 1.71%<br />
No answer 144 9.11%<br />
<br />
People who responded express their dissatisfaction with the current edge computing services for various reasons. They emphasize the need for innovation, signaling a desire for improved and more advanced edge computing solutions.<br />
Better automation is sought, suggesting a need for streamlining processes and reducing manual tasks. Security is a significant concern, with users pointing out that the existing security measures are inadequate.<br />
<br />
Some people mention the rarity of long-living, transactional, self-managing systems and the lack of documentation for such systems, which hampers their usability and implementation.<br />
<br />
There are references to the need for better integration with central tools for deploying software, indicating a desire for a more cohesive and efficient software deployment process. Additionally, users express the desire for increased computing capability at a lower cost within the same environmental package, highlighting the importance of cost-effectiveness and performance.<br />
<br />
In summary, dissatisfaction with edge computing services is driven by the desire for innovation, better automation, enhanced security, improved documentation, integration with central tools, and cost-efficiency.<br />
<br />
=== IoT Applications ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 206 13.04%<br />
Not Satisfied (AO02) 9 0.57%<br />
Neutral (AO03) 51 3.23%<br />
Satisfied (AO04) 20 1.27%<br />
No answer 139 8.80%<br />
<br />
Those who responded express their dissatisfaction with the current IoT application services for various reasons. They find the services confusing and feel that they require too much prior knowledge about the platform, making them challenging to use effectively.<br />
<br />
Innovation is highlighted as an area for improvement, suggesting a desire for more advanced and cutting-edge IoT solutions. Some indicate that they are not currently using these services or are not actively engaged in IoT applications.<br />
There is a reference to the rarity of long-living, transactional, and self-managing systems, and the lack of documentation for such systems, which creates usability issues. Additionally, very few individuals are utilizing these services.<br />
<br />
Some express disinterest in IoT applications, stating that they are not involved in that area. However, others mention the need for better integration with central tools for deploying software, indicating a desire for a more streamlined and cohesive deployment process.<br />
<br />
Lastly, the challenge of supporting multiple networking infrastructures concurrently, such as GSM EDGE, NB IoT, LoraWAN, Ethernet, and Wi-Fi, is noted, implying the complexity of managing diverse IoT connectivity options.<br />
In summary, dissatisfaction with IoT application services stems from issues related to usability, the desire for innovation, a lack of use or interest, the need for better documentation and integration, and the challenges of supporting multiple networking infrastructures.<br />
<br />
=== Machine Learning ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 189 11.96%<br />
Not Satisfied (AO02) 15 0.95%<br />
Neutral (AO03) 52 3.29%<br />
Satisfied (AO04) 27 1.71%<br />
No answer 142 8.99%<br />
<br />
Those who responded express their dissatisfaction with the current machine learning services for various reasons. They find machine learning services offered by external providers too proprietary and prefer in-house implementations using open-source technologies.<br />
<br />
One individual's response is simply "Ok," indicating a lack of specific complaints or needs. Innovation is not mentioned as an area for improvement.<br />
<br />
Some express the need for easier access to machines, highlighting a desire for more straightforward and efficient access to the resources required for machine learning projects. Others mention the need for more GPU power and improved scheduling, underlining the importance of performance and resource management.<br />
<br />
Using up-to-date versions of systems that implement machine learning is deemed necessary for staying current and effective in this field.<br />
<br />
There's a clear emphasis on treating machine learning as a practical tool rather than a novelty. Users are advised to structure and prepare data properly, avoid rushing into machine learning, and prevent the development of biased algorithms that merely reflect existing understanding. They stress the importance of using data to gain insights and understanding.<br />
<br />
Lastly, there is a call to run machine learning pipelines with the same level of continuous integration and reliability as is available to developers, emphasizing the need for robust and reliable machine learning processes.<br />
<br />
In summary, dissatisfaction with machine learning services is driven by concerns about proprietary offerings, the need for in-house open-source implementations, access to resources, performance, up-to-date systems, and the responsible and practical use of machine learning as a tool in the organization's workflows.<br />
<br />
=== Blockchain ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 253 16.01%<br />
Not Satisfied (AO02) 4 0.25%<br />
Neutral (AO03) 15 0.95%<br />
Satisfied (AO04) 6 0.38%<br />
No answer 147 9.30%<br />
<br />
Those who responded express a strong negative sentiment toward blockchain. There's no specific mention of innovation or any potential areas for improvement. Responses were minimal, cryptic and lacked clarity and detail regarding the specific issues or concerns with the services, making it challenging to discern the exact nature of the dissatisfaction with its use.<br />
<br />
=== Gaming ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 221 13.99%<br />
Not Satisfied (AO02) 6 0.38%<br />
Neutral (AO03) 26 1.65%<br />
Satisfied (AO04) 29 1.84%<br />
No answer 143 9.05%<br />
<br />
Those who responded express their dissatisfaction with the current gaming services for various reasons. They call for better gaming support, suggesting a need for improvements in this area.<br />
<br />
There are mentions of issues related to the use of NVIDIA graphics cards under Wayland on openSUSE, indicating a lack of convenience and compatibility in this context. Linux drivers are criticized for not rendering some games properly, ultimately requiring the use of Windows for certain gaming needs.<br />
<br />
On a more positive note, some users appreciate the good compatibility, performance, and HDR support in the existing gaming services.<br />
<br />
Innovation is highlighted as an area for improvement, suggesting a desire for more advanced and up-to-date gaming features and technologies. The pace of graphics development is seen as slower than Windows, particularly concerning HDR, ray tracing, and GPU drivers.<br />
<br />
There are requests for better support of modern graphical features, including HDR and ray tracing, as well as a desire for support for new game releases. The mention of RegataOS, which is based on openSUSE, suggests the potential for openSUSE to take inspiration from such initiatives.<br />
<br />
VR is mentioned as a specific area of interest and potential improvement. Users express a general wish for every game to work effectively, suggesting a desire for enhanced compatibility.<br />
<br />
However, some responses lack specific details, with phrases like "no idea," making it challenging to discern the exact nature of the dissatisfaction in those cases.<br />
In summary, dissatisfaction with gaming services is driven by issues related to compatibility, performance, graphics development, and support for modern gaming features, as well as a desire for better innovation and VR support.<br />
<br />
<br />
=== Other ===<br />
Rate how satisfied you are with the IT services you/your company use?<br />
Don't Use (AO01) 103 6.52%<br />
Not Satisfied (AO02) 5 0.32%<br />
Neutral (AO03) 56 3.54%<br />
Satisfied (AO04) 42 2.66%<br />
No answer 219 13.86%<br />
<br />
Those who responded express their dissatisfaction with other services for various reasons. One of the concerns raised is the lack of a proper built-in virtual keyboard, which is seen as necessary for security and other purposes. This indicates a need for enhanced security features.<br />
<br />
Another user points out that while it may not be an openSUSE-specific problem, Linux, in general, lacks traction among end-users in the multimedia and creative suite sectors. They suggest that Linux isn't attractive enough as a platform for digital artists, emphasizing the need for more innovation and user-friendly tools in this area.<br />
Some users express dissatisfaction with the lack of Linux support for certain corporate applications, listing examples like Oracle Content Experience desktop client, Microsoft Outlook desktop, Microsoft Office, and Cisco telephony. This indicates a need for better compatibility with widely used software, particularly in corporate environments.<br />
A few responses are marked as "N/A," indicating that the users may not have specific issues or needs related to the other services. However, one response suggests that the term "other" could possibly refer to AI services, and they clarify that the company is not currently using AI technologies.<br />
<br />
There is also a recommendation to use open-source (FLOSS) services, highlighting a preference for open and community-driven solutions.<br />
<br />
In summary, dissatisfaction with other services primarily revolves around the need for improved security features, better support for creative and multimedia sectors, more innovation, and enhanced compatibility with widely used corporate applications on Linux. Additionally, users express a preference for open-source solutions.<br />
<br />
= General Questions =<br />
<br />
=== What do you believe are the primary factors driving the growth of Linux and open-source technologies in your industry? ===<br />
<br />
In summary, the primary factors driving the growth of Linux and open-source technologies in various industries include cost savings, fast deployment, the need for scientific applications and platforms beyond business-oriented Microsoft applications, and increased interest leading to more software development. Other key drivers include digital sovereignty, regulatory compliance, and cost considerations. In the telecom industry, the migration to Linux and open-source platforms is a major trend.<br />
<br />
The open development and contribution model, along with the decentralization of larger companies, is contributing to the growth of open source. Employee preferences for Linux and personal interests in traditional industries are also driving adoption. Concerns about Windows' subscription model and privacy issues have led to a shift towards open source alternatives.<br />
<br />
Linux's robustness, security, adaptability, and open APIs are key factors. The availability of vendors like SUSE with helpful technical support is driving adoption, as well as ease of use and the avoidance of intrusive paid services.<br />
Innovations such as containers and cloud technology are further promoting Linux and open-source adoption. Copy-left licensing, access to source code, and adaptability play a role in growth.<br />
<br />
The broad availability of open-source software in various industries, from astronomy to high-performance computing, offers quality solutions. Linux's security, reliability, stability, and extensive ecosystem satisfy diverse needs.<br />
Factors like virtualization, cost, reliability, transparency, and avoiding vendor lock-in are also contributing to the growth of Linux and open-source technologies. Overall, these factors reflect the adaptability and cost-effectiveness of Linux and open-source solutions across different sectors.<br />
<br />
=== Are there any specific challenges/barriers hindering wider adoption of the technologies cited above in your industry? ===<br />
In various industries, there are several challenges and barriers hindering wider adoption of Linux and open-source technologies. These include:<br />
<br />
Industry-specific software: Many industries rely on specialized software that is designed for Windows environments. In some cases, these applications have no Linux-compatible alternatives. This is a significant barrier to adoption in sectors like textile, CAD, and graphics design.<br />
<br />
Vendor lock-in: Organizations often face challenges in migrating away from existing proprietary technologies due to vendor lock-in. This is especially true when dealing with Microsoft, which dominates the end-user computing space, and Google's dominance in education.<br />
<br />
Lack of knowledge and inertia: Many managers and end-users are more familiar with proprietary technologies like Microsoft, and there is often a resistance to change. This is compounded by a lack of knowledge about Linux and open source among IT staff and management.<br />
<br />
Compatibility and software support: Some critical legacy and proprietary software do not have Linux versions or suitable alternatives. Lack of support from third-party vendors for Linux also poses a barrier to adoption.<br />
<br />
Fragmentation and choice: The wide variety of Linux distributions and desktop environments can be confusing for regular users. This fragmentation can lead to hesitation and lack of standardization.<br />
<br />
Documentation and usability: Inconsistent or inadequate documentation and the lack of an end-user-friendly experience on Linux desktops can discourage adoption.<br />
<br />
Hardware support: Lack of support for specific hardware and peripherals can be a barrier to adoption, especially when users depend on these devices for their work.<br />
<br />
Resistance to change and complacency: Many users and organizations are resistant to change and prefer to stick with familiar systems, even if they are suboptimal.<br />
<br />
Reliance on proprietary software and technologies: Industries, such as finance and banking, heavily rely on proprietary software that is considered essential for compliance with regulations.<br />
<br />
Training and knowledge: There is a need for better training and knowledge dissemination about Linux and open-source alternatives in educational institutions, workplaces, and among decision-makers.<br />
<br />
Overall, the challenges and barriers to wider adoption of Linux and open-source technologies in various industries are complex and multifaceted, ranging from technical compatibility issues to organizational and cultural resistance to change. Overcoming these barriers will require concerted efforts in education, software development, and standardization to make Linux and open source more accessible and user-friendly.<br />
<br />
=== Are there any emerging technologies/trends pertaining to the IT industry you believe will significantly contribute to business growth in the next three to five years? Please explain. ===<br />
<br />
<br />
Several emerging technologies and trends are expected to significantly contribute to business growth in the IT industry over the next three to five years. These include:<br />
<br />
Containerization: Technologies like containerization (e.g., Docker) and orchestration (e.g., Kubernetes) are becoming increasingly essential for managing and deploying applications. They offer consistent developer experiences and facilitate the transition to cloud-native architectures.<br />
<br />
* Artificial Intelligence (AI) and Machine Learning (ML): AI and ML are having a broad impact on various sectors, from automating tasks to improving business insight and customer satisfaction. AI at the edge, data storage, and communication technologies will drive growth in IT.<br />
<br />
* Cloud Computing: Cloud computing is expected to become even more widespread, with businesses leveraging cloud-based services and applications. The shift toward the cloud is driven by remote work, scalability, and accessibility from various devices.<br />
<br />
* Edge Computing: Edge computing is gaining prominence, particularly in IoT applications. It reduces latency, making real-time processing and analysis of data more accessible, which has implications for various industries.<br />
<br />
* Domain-Specific Applications: Growth in browser-based applications tailored for specific industries.<br />
<br />
* Python Integration: The integration of Python with Excel and other applications will streamline processes.<br />
<br />
* Scientific Clusters: Use of clusters for scientific applications will advance research and development.<br />
<br />
*Blockchain: While blockchain technology continues to evolve, it offers numerous use cases, including improved security, supply chain management, and transparent transactions. Blockchain is expected to drive innovation and growth in several sectors.<br />
<br />
* Immutable OS: Immutable operating systems are gaining attention, particularly for their reliability and the ability to roll back the OS easily in case of issues. This trend is particularly relevant for businesses looking to maintain system stability.<br />
<br />
* Open Source: The continued growth of open-source software and the commercialization of open-source projects will contribute to business growth. Open-source solutions can provide cost-effective alternatives and greater flexibility.<br />
<br />
AI-Assisted Software Development: AI tools that assist developers in tasks such as code optimization, text generation, and image correction will enhance productivity in software development.<br />
<br />
* Containerization Standardization (e.g., Flatpak): Efforts to standardize containerization formats like Flatpak will lead to better app availability, particularly on Linux-based systems. This will simplify the distribution and installation of third-party applications.<br />
<br />
* Internet of Things (IoT): As more devices and objects become connected to the internet, IoT applications will continue to grow. IoT offers opportunities for data collection, analysis, and automation in various industries.<br />
<br />
* Quantum Computing: Advances in quantum computing will enable complex calculations and simulations, offering new opportunities in research and problem-solving.<br />
<br />
* Big Data and Analytics: The combination of big data and AI, powered by new-generation processors, opens up opportunities for advanced data analysis and automated processing, providing insights for business growth.<br />
<br />
* Standardization of Data Access Protocols: The standardization of data access protocols, especially in environmental data management, will open new applications and enable the development of digital twins for various systems.<br />
<br />
These emerging technologies and trends are expected to shape the IT industry, drive innovation, and offer opportunities for businesses to grow and thrive.<br />
<br />
<br />
=== In the last three months, have you contributed to an open-source project? ===<br />
<br />
'''Fedora Infrastructure Project:''' One participant joined the Fedora Infrastructure project but expressed difficulty navigating it.<br />
openSUSE and es.opensuse.org: Several contributors mentioned their involvement in openSUSE, either through translation, bug reporting, or other forms of support.<br />
<br />
'''GitHub Projects:''' Many mentioned working on GitHub projects, including small open-source projects, symbol viewers for code, and various scripts.<br />
<br />
'''Linux Distribution and Software Projects:''' Some participants contributed to specific Linux distributions, like Xubuntu, Tumbleweed, or Void Linux. Others mentioned their contributions to various software projects such as Haiku, Mastodon, and OSM.<br />
<br />
'''Documentation and Translation:''' Several participants contributed through documentation, translation work, or opening bug reports.<br />
<br />
'''Testing and Bug Reports:''' Many mentioned their involvement in testing and reporting issues for open-source projects.<br />
<br />
'''Personal Open-Source Projects:''' Some contributors mentioned their own open-source projects and their ongoing work.<br />
<br />
'''Donations:''' A few participants mentioned donating to open-source projects, such as LibreOffice, KDE, and others.<br />
<br />
'''Limited Coding Skills:''' Some participants admitted they had limited coding skills but expressed a willingness to help with documentation and user support.<br />
<br />
'''Icon Design:''' One contributor mentioned creating icons for the Linux Papirus icon theme.<br />
<br />
'''Monetary Donations:''' A few mentioned contributing through monetary donations to various open-source projects.<br />
<br />
'''Survey Responses:''' Some participants contributed by responding to surveys from projects like Mozilla.<br />
<br />
'''Linux Distributions:''' Contributors reported work on various Linux distributions such as Manjaro and Q4OS.<br />
<br />
'''Translation:''' Multiple contributors mentioned translation work for projects like GNOME, OpenVPN, and Mastodon.<br />
<br />
'''Code Contributions:''' A few mentioned providing code contributions to projects like Path of Building and Flare.<br />
<br />
'''Bug Reporting:''' Several contributors mentioned their involvement through bug reporting for projects like KDE, Plasma, and openwrt.<br />
<br />
'''Small Commits and Testing:''' Several participants mentioned making small commits, testing, and bug reporting for various open-source projects.<br />
No Recent Contributions: Some participants indicated that they had not made any contributions in the past three months, often citing a lack of coding skills or limited time.<br />
<br />
In summary, the responses show a diverse range of contributions to open-source projects, including code development, documentation, translations, bug reports, and financial support. These contributions help sustain and improve the open-source ecosystem.<br />
<br />
<br />
=== In the last three months, have you contributed to openSUSE? ===<br />
<br />
'''Forum Support:''' Many contributors reported providing support via the openSUSE forum, helping users troubleshoot issues, and answering questions.<br />
<br />
'''Documentation:''' Several participants mentioned their involvement in documentation, including maintaining entries on the openSUSE Chinese Wiki, contributing to the Knowledge Base, and helping improve documentation.<br />
<br />
'''Bug Reports:''' A significant number of contributors engaged in bug reporting and interacting on mailing lists, bugfixes, and bug reports for areas like Tumbleweed, Aeon, Leap, and more.<br />
<br />
'''Packaging:''' Packaging contributions were mentioned for Tumbleweed, Leap, and Factory, with some reporting maintaining packages for the Build Service and packaging tools.<br />
<br />
'''Translations:''' Some participants contributed through translations for openSUSE official news and other areas, as well as making contributions to documentation and marketing.<br />
<br />
'''Testing and Bug Fixing:''' Contributors shared their involvement in testing Tumbleweed, bug reporting, bug fixes, and participation in openQA.<br />
<br />
'''Marketing and Advocacy:''' A few mentioned marketing and advocacy efforts to promote openSUSE in various ways.<br />
<br />
'''Community Engagement:''' Some participants reported their community involvement, including attending conferences, supporting forums, and moderating forums.<br />
<br />
'''Challenges and Concerns:''' A few contributors expressed concerns about the lack of clear onboarding documentation and difficulties navigating openSUSE resources like the Wiki, Bugtracker, and a perceived vagueness surrounding the project's future.<br />
<br />
'''Other Contributions:''' Miscellaneous contributions were mentioned, such as conducting surveys, filing bug reports, updating Wiki articles, and offering support in various forms.<br />
<br />
While many contributors shared active engagement and efforts to contribute to openSUSE in various capacities, there were concerns raised about certain aspects of the project, such as documentation and community engagement. These responses provide insights into both the positive contributions and challenges faced by individuals within the openSUSE community.<br />
<br />
=== Are you considering or actively using Linux in areas beyond your primary use case (e.g., gaming, blockchain, AI, robotics, graphic design, movie animation or sound creation, etc.)? if yes, please share your the uses case in a few small sentences. ===<br />
<br />
'''Creative Work:''' Many respondents indicated that they use Linux for their primary use case, such as general computing or software development, but they switch to Windows for creative work like photo and video editing due to the perceived lack of suitable creative apps on Linux.<br />
<br />
'''Multifunctional Use:''' Some respondents reported using Linux for a wide range of purposes, including finance, video production, graphic design, game development, IoT, and more, indicating that Linux covers their diverse needs.<br />
<br />
'''Gamers:''' Several mentioned using Linux for gaming, either natively or through compatibility layers like Proton or Wine.<br />
<br />
'''Home Automation and IoT:''' A few respondents were actively considering or using Linux for home automation, IoT, and other embedded applications.<br />
<br />
'''Hobbyists:''' Hobbyist activities such as 3D modeling, 3D printing, machine learning, and blockchain experimentation were mentioned as use cases for Linux.<br />
<br />
'''Server and Cloud:''' Some participants discussed using Linux for hosting servers and cloud-based services.<br />
<br />
'''Self-Hosted Services:''' A few users highlighted self-hosting applications, such as Nextcloud and Freshrss, as part of their Linux usage.<br />
<br />
'''Mobile and Edge Devices:''' A few were exploring Linux for mobile devices and edge computing.<br />
<br />
'''Scientific and Research:''' Linux was mentioned for scientific research, running simulations, and data analysis.<br />
'''<br />
Media Production:''' Some participants expressed interest in using Linux for audio and video editing, animation, and music production.<br />
<br />
'''Educational and Training:''' Linux was considered for educational and training purposes, including using it in kiosk mode.<br />
<br />
'''Use Everywhere:''' Some respondents stated that they use Linux for everything and aim to continue doing so wherever possible.<br />
<br />
'''Testing and Experimentation:''' Linux was preferred for testing and experimentation, including software development, learning new programming languages, and AI research.<br />
<br />
'''Graphics and Design:''' Some were using Linux for graphic design, 3D modeling, and CAD work.<br />
<br />
'''Server Administration:''' Linux was used for server administration and remote data analysis in scientific fields.<br />
<br />
'''General Hobby Use:''' Linux was used for various hobbies like photography, 3D printing, home automation, and more.<br />
<br />
'''Creative Professionals:''' A few respondents reported using Linux in creative fields like graphics, music, and video production.<br />
<br />
'''Enterprise:''' A few discussed using Linux for corporate and business applications and in professional settings.<br />
<br />
'''Home Media and NAS:''' Linux was used as a home media server and for network-attached storage (NAS) setups.<br />
<br />
'''Cloud-Based Development:''' Linux was actively used for cloud-based development, containerization, and web hosting.<br />
<br />
'''School and Training:''' Linux was considered for school and training purposes, with some respondents noting the need for open-source training resources.<br />
<br />
While some users faced limitations in certain areas due to software availability, the responses showed that Linux is being embraced for an array of use cases, both personal and professional. Additionally, there was a recurring theme of users wanting to extend their use of Linux to more scenarios, such as gaming and creative work, as the ecosystem evolves and matures.<br />
<br />
=== “What specific benefits have you experienced by using Linux in your chosen use case(s)?” ===<br />
<br />
'''Trust and Privacy:''' Users appreciate the trustworthiness of Linux, which doesn't collect and sell their data. It provides better privacy and doesn't force updates on them.<br />
<br />
'''Stability and Reliability:''' Linux is known for its stability and reliability. It doesn't crash often, and users find it dependable for their daily tasks.<br />
<br />
'''Customization:''' Linux offers extensive customization, allowing users to configure their systems to meet their exact needs. They can choose from a wide range of desktop environments and software.<br />
<br />
'''Low Resource Usage:''' Linux is efficient and runs well on older hardware, extending the life of aging devices and saving money.<br />
Open Source and Free Software: Many users appreciate the open-source nature of Linux and the availability of free software. It gives them freedom, both in terms of using the software and modifying it.<br />
<br />
'''Community and Learning:''' Linux has a strong and supportive community. Users learn a lot about IT, computing, and how their computer works. It's a platform for gaining knowledge and skills.<br />
<br />
'''Security:''' Linux is often praised for its security features, including fewer virus risks and greater control over user data.<br />
<br />
'''Flexibility:''' Users can adapt Linux to their workflows, whether it's for development, gaming, or daily use. It's a versatile operating system.<br />
<br />
'''Cost-Effective:''' Linux is generally free to use, reducing costs compared to proprietary alternatives. This is especially beneficial for individuals and small organizations.<br />
<br />
'''Containerization and Server Management:''' Linux is favored for server management, thanks to its containerization capabilities. It's often seen as an ideal platform for DevOps professionals.<br />
<br />
'''Performance:''' Many users report that Linux offers better performance, stability, and speed compared to other operating systems.<br />
Choice and Variety: Linux provides users with a wide range of choices, from distributions and desktop environments to software and tools. Users appreciate the diversity and options available.<br />
<br />
Overall, Linux users value its open nature, customization, security, and the control it provides over their computing environment. It's clear that Linux serves a wide range of needs and preferences across its user base.<br />
<br />
=== What challenges or limitations have you encountered when using our distributions for your primary or secondary use case(s)? ===<br />
<br />
'''Outdated Software:''' Difficulty accessing the latest software packages, affecting software like Docker.<br />
<br />
'''Limited Host Support:''' Some hosts do not provide images for openSUSE, limiting platform usability.<br />
<br />
'''Encryption Issues:''' Problems setting up hard drive encryption, including keyboard layout issues during boot.<br />
<br />
'''Documentation and Support:''' Inadequate documentation and challenges finding support, especially for data science.<br />
<br />
'''Graphics Card Setup:''' Configuration issues with graphics cards and difficulties getting community assistance.<br />
<br />
'''Compatibility:''' Issues running Windows programs under Wine/Proton, requiring complex troubleshooting.<br />
<br />
'''Hardware Integration:''' Problems with hardware integration, including graphics card switching and docking.<br />
<br />
'''Choice Overload:''' OpenSUSE's abundance of options can overwhelm new users.<br />
<br />
'''Multimedia Codecs:''' Issues with multimedia codecs and the absence of some software packages.<br />
<br />
'''Incomplete Documentation:''' OpenSUSE's documentation can be challenging to comprehend, especially for new tools.<br />
<br />
'''VPN Compatibility:''' Problems with corporate VPN solutions due to different naming conventions.<br />
<br />
'''Learning Curve:''' A steep learning curve for users new to Linux.<br />
<br />
'''Gaming Support:''' Support for certain games and peripherals can be problematic.<br />
<br />
'''Proprietary Software:''' Limited support for proprietary software and hardware, including graphics drivers.<br />
<br />
'''Frequent Upgrades:''' Users find the need for frequent fresh installations onerous.<br />
<br />
'''Battery Life and Performance:''' Users have reported issues with battery life, performance, and resource usage.<br />
<br />
'''Troubleshooting:''' Troubleshooting problems can be challenging, particularly for less experienced users.<br />
<br />
'''Hardware Compatibility:''' Challenges with hardware support, including printers, graphics cards, and touchpad configuration.<br />
<br />
'''Filesystem Read-Only:''' Ext4 root partitions on virtual machines can go 'read-only' unexpectedly, requiring backups.<br />
<br />
'''Network Scanner Compatibility:''' Difficulty recognizing network scanners, occasionally requiring the use of Windows machines.<br />
<br />
Despite these challenges, openSUSE users appreciate the flexibility and choices the distribution offers and find the investment in learning to be worthwhile. OpenSUSE has a strong community and user base, and many of these issues can be addressed through community support and further development.<br />
<br />
=== Have you explored Linux-based solutions for edge computing or IoT applications? If yes, please share your experiences and any notable benefits. ===<br />
<br />
Many of the comments indicate that users have explored Linux-based solutions for edge computing and IoT applications, with a mix of experiences and perceived benefits:<br />
<br />
* Some users mentioned that Linux, especially in combination with containers and WebAssembly (WASM), is excellent for edge and IoT applications.<br />
<br />
* Linux is recognized for providing full control over services and being reliable for various IoT use cases, including home automation, home servers, and multimedia control.<br />
<br />
* Several users highlighted the use of Raspberry Pi devices for IoT, surveillance, and home automation.<br />
<br />
* The ability to build custom Linux distributions for IoT applications using tools like Yocto was appreciated.<br />
<br />
* Despite the benefits, some users mentioned challenges, including the heavyweight nature of current Linux distributions and the need for more self-managing capability in IoT solutions.<br />
<br />
* Notable benefits of Linux for edge computing include faster development, the ability to run compute-intensive tasks, and the capacity to keep data and services in-house.<br />
<br />
* Users emphasized the importance of Linux's open nature, privacy, and freedom from IoT platform capture or abandonment.<br />
<br />
* Challenges mentioned include the need for stable power supplies, reliable storage, and efficient service separation.<br />
<br />
Overall, Linux-based solutions seem to offer flexibility and control for edge computing and IoT applications, with the trade-offs of managing updates and hardware considerations.<br />
<br />
=== Are there particular Linux distributions or flavors that you prefer for specific use cases? If so, which ones and why? ===<br />
<br />
It's clear that there is a wide range of Linux distributions preferred by different users based on their specific needs and preferences. Some common themes and distributions mentioned in the comments include:<br />
<br />
'''openSUSE (Leap and Tumbleweed):''' Many users prefer openSUSE for its stability, Yast configuration tool, and rolling release option (Tumbleweed).<br />
<br />
'''Debian:''' Known for its stability, Debian is a popular choice for servers and desktops, especially among those who don't want frequent updates.<br />
<br />
Ubuntu: Frequently chosen for its extensive software repositories, user-friendly nature, and long-term support (LTS) versions.<br />
<br />
'''Fedora:''' Chosen for its cutting-edge features, and Kinoite, a Fedora variant with features like Toolbox and Podman, was mentioned as providing an excellent experience.<br />
<br />
'''Arch Linux:''' Selected by users who appreciate the ability to customize their system, stay up-to-date with the latest software, and are comfortable with a DIY approach.<br />
CentOS / RHEL / Oracle Linux: Picked for their stability and reliability, especially in server environments.<br />
<br />
'''Kubuntu:''' A flavor of Ubuntu, known for its KDE desktop environment.<br />
<br />
'''Manjaro:''' Chosen for its user-friendliness and its close relationship with Arch Linux.<br />
<br />
'''Zorin OS:''' Known for its user-friendly interface, making it a good choice for beginners transitioning from other operating systems.<br />
<br />
'''Gentoo:''' Preferred by advanced users who appreciate the control and optimization it offers.<br />
<br />
'''NixOS:''' Selected for its unique approach to package management and system configuration.<br />
<br />
'''Solus:''' Used for light desktop usage and integration purposes.<br />
<br />
'''Amazon Linux:''' Employed in AWS environments due to compatibility.<br />
<br />
'''Alpine Linux:''' Known for its speedy package management.<br />
<br />
'''Garuda Linux:''' Used for home desktop use, offering unique KDE customizations.<br />
<br />
'''TrueNAS / Proxmox:''' Preferred for storage and virtualization purposes.<br />
<br />
'''Nix:''' Mentioned for its unique package management approach.<br />
<br />
'''Kali Linux:''' Chosen for testing and research.<br />
<br />
'''Raspberry Pi OS:''' Ideal for Raspberry Pi-based projects and systems.<br />
<br />
It's important to choose a distribution that aligns with your specific use case and preferences. Each distribution has its own strengths and weaknesses, so it's worthwhile to explore and experiment with different ones to find the best fit for your needs.<br />
<br />
=== In your opinion, what emerging IT trends or technologies show the most promise in the next three to five years? ===<br />
<br />
In the coming three to five years, several promising IT trends and technologies are emerging:<br />
<br />
'''Artificial Intelligence (AI):''' AI is a prominent trend, with applications in various fields such as natural language processing and machine learning. However, some are concerned about privacy issues associated with certain AI technologies.<br />
<br />
'''Advanced Connectivity (5G Networks):''' The deployment of 5G networks is expected to revolutionize connectivity and enable faster data transmission, benefiting various sectors.<br />
<br />
'''Web3:''' The transition to Web3, which is expected to enhance decentralized and blockchain-based internet services, is gaining attention.<br />
Trust Architectures: Technologies focused on trust and security, such as digital identity and secure architectures, are expected to play a crucial role in the coming years.<br />
<br />
'''Containerization:''' Container technologies and solutions, like Docker and Kubernetes, are being increasingly adopted for software deployment and management.<br />
<br />
'''Immutable Systems:''' Immutable operating systems and file systems are gaining popularity for their ability to enhance system stability and security.<br />
<br />
'''AI-Driven Game Development (e.g., Godot):''' AI is becoming integral in game development, automating various aspects of game design and rendering.<br />
<br />
'''WebAssembly:''' The use of WebAssembly for applications, system tuning, and system enhancements is on the rise.<br />
Security: Security is expected to remain a top concern, especially with the increasing use of cloud services and the need to protect sensitive data.<br />
<br />
'''Open Source and FOSS Adoption:''' There is a growing trend toward using open-source software and Linux-based solutions, focusing on transparency and control over data.<br />
<br />
'''Sustainability and Green IT:''' Sustainability and environmentally friendly technologies are becoming more significant as the IT industry explores eco-friendly solutions.<br />
<br />
'''Desktop Linux and Gaming:''' Desktop Linux is expected to gain more popularity, especially in the gaming sector, with trends like the Steam Deck driving its adoption.<br />
<br />
'''Generative AI:''' Generative AI technologies, like language models and image generation tools, are likely to have a growing impact in various domains.<br />
<br />
'''Quantum Computing:''' Quantum computing may become more accessible and find applications, particularly in cryptography and complex problem-solving.<br />
<br />
'''Edge Computing:''' Edge computing, which involves processing data closer to the source, is gaining importance, especially for IoT and autonomous systems.<br />
<br />
'''Data Analysis:''' The field of data analysis and analytics is expected to expand further, providing valuable insights for various industries.<br />
Rust Programming Language: The Rust programming language is gaining popularity for its safety and performance, contributing to software development tools.<br />
<br />
'''Digital Twins:''' The integration of multiple systems into digital twins is expected to advance, offering enhanced simulations and modeling.<br />
<br />
'''Augmented and Virtual Reality (AR/VR):''' AR and VR technologies are expected to evolve and find applications in various sectors.<br />
<br />
'''Machine Learning (LLM):''' Machine learning, particularly large language models (LLMs), is advancing rapidly and is likely to impact various aspects of computing.<br />
<br />
It's important to note that these trends may vary in significance based on the specific industry or field of interest. Additionally, privacy and security concerns, as well as environmental considerations, will continue to shape the development and adoption of emerging technologies.<br />
<br />
=== Do you believe Linux is well-positioned to meet the evolving needs of the market, including emerging technologies? Please explain. === <br />
<br />
Linux is well-positioned to meet the evolving needs of the market, especially in emerging technologies. Many comments in favor of Linux mention its stability, high performance, system administration capabilities, and open nature. It's widely used in server technologies, with a growing market share, and its versatility, openness, and flexibility make it suitable for various applications. Linux's popularity is increasing, with more support for open platforms and the adoption of emerging technologies.<br />
<br />
On the other hand, some comments express concerns about Linux's position, primarily in the desktop market. They mention issues related to the user experience and the absence of specific applications for end users, making it less competitive with commercial operating systems. However, there is hope that devices like the Steam Deck and increasing support for various technologies will improve Linux's position on the desktop.<br />
<br />
In summary, Linux's adaptability, open-source nature, and presence in the server and cloud markets make it well-suited to meet the evolving needs of the market, but there are challenges in expanding its desktop market share and improving user-friendliness.<br />
<br />
=== Are there any specific features or improvements you would like to see in Linux distributions to better support your use case(s)? ===<br />
<br />
The responses to the question about specific features or improvements desired in Linux distributions vary widely. Here's a summary of the key points:<br />
<br />
'''Professional Apps:''' Many respondents express the need for professional-grade applications on Linux. The lack of such software is seen as one of Linux's biggest challenges.<br />
<br />
'''Continuous Improvement:''' Some respondents believe that the open-source community is continually improving software packages, indicating satisfaction with the direction Linux is taking.<br />
<br />
'''User Assistance and Support:''' There's a call for better post-installation support, guidance on configuration optimization, and integration of AI-driven assistance.<br />
<br />
'''Contentment:''' Several users express their satisfaction with Linux, acknowledging its role in enabling their scientific achievements and revolutionary impact.<br />
<br />
'''Security and Encryption:''' Improved security features like systemd-homed, LUKS, TPM, and FIDO support are desired. Also, better integration of secure boot and device onboarding.<br />
<br />
'''Better Color Management:''' Enhanced color management, particularly in Wayland, is requested.<br />
<br />
'''Desktop Environment Switching:''' Users want more flexibility to switch between desktop environments without system-wide changes and advocate for declarative configuration.<br />
<br />
'''User-Friendly Permissions:''' Requests for simplified administration, like adding printers or editing files as admin via GUI editors without needing root access, are highlighted.<br />
<br />
'''Technical Compatibility:''' Improved compatibility with other Linux distributions, particularly Red Hat-based systems, in terms of package naming and structures, is desired.<br />
<br />
'''Tumbleweed and SlowRolls Relationship:''' Users appreciate the relationship between Tumbleweed and SlowRolls and hope to see similar cooperation among other distributions.<br />
<br />
'''Graphics and GPU Support:''' Enhanced support for graphics card settings and improved Intel Atom graphics drivers are mentioned.<br />
<br />
'''Virtualization:''' Better virtualization support for running OS/2 on KVM is requested.<br />
<br />
'''Remote Management Tools:''' Some users would like to see tooling for remote management and long-running, well-documented transactional distributions.<br />
<br />
'''Aesthetics:''' Aesthetically pleasing desktop environments and improved marketing are suggested for openSUSE.<br />
<br />
'''Debugging and Simplification:''' Users call for better debugging tools, enhanced organization, reduced duplicity, and increased simplicity.<br />
<br />
'''Power Management:''' Improved power management and better support for ARM64 platforms are mentioned.<br />
<br />
'''Finance and Desktop Distribution:''' Some users believe that Linux companies should take finance platforms more seriously and develop desktop distributions accordingly.<br />
<br />
'''Appealing Desktop Environments:''' Better desktop environments that are welcoming to newcomers not well-versed in the command line are desired.<br />
<br />
'''Tumbleweed Defaults:''' Users hope for better default configurations in Tumbleweed.<br />
<br />
'''Concerns about the Future:''' Some express concerns about the direction of openSUSE, particularly related to changes like the termination of Leap and a shift towards microservices and containerization.<br />
<br />
'''Package Management:''' A desire for more straightforward package management and simplicity with a focus on immutability is mentioned.<br />
<br />
'''Hardware Support:''' Better support for newer hardware, including graphics cards, graphic tablets, and touchscreens, is requested.<br />
HDR Support: Improved HDR support is desired.<br />
<br />
'''Linux on IoT Devices:''' Users emphasize the importance of free, open, stable distributions for developing IoT products.<br />
<br />
'''Linux for Artists:''' Better support for graphic tablets and artistic tools is mentioned.<br />
<br />
'''User-Friendly Updates:''' Users call for a more user-friendly approach to handling system updates.<br />
<br />
'''Version Management:''' Users want easier management of components with multiple versions.<br />
<br />
'''Ease of Use:''' Simplicity, ease of use, and an easier entry point for new users are recurring themes.<br />
<br />
'''Documentation:''' There's a call for better documentation and information about how to install the OS.<br />
<br />
'''Security Configuration:''' Simplifying the configuration of security measures like firewalls and AppArmor is requested.<br />
<br />
'''PHP Version Management:''' Some users express the need for easier management of PHP versions.<br />
<br />
'''Driver Management:''' Better driver management, particularly for video cards, is desired.<br />
<br />
'''Containerization:''' Users express concerns about the growing complexity due to container-based solutions and their impact on the average desktop user.<br />
<br />
'''Init System:''' Some users want alternatives to the systemd init system.<br />
<br />
'''Wayland and HDR Support:''' Better Wayland support and HDR capabilities are desired.<br />
<br />
'''Windows Compatibility:''' Users hope for better compatibility with Windows applications, particularly for proprietary software.<br />
<br />
'''Update Management:''' Easier management of updates, including improved management of multiple versions of software components, is requested.<br />
<br />
'''File Management:''' Users want better drag and drop functionality for files.<br />
<br />
'''Repository Management:''' Easier management of software repositories is requested.<br />
<br />
'''NAS Distribution:''' Some users would like to see an openSUSE-based NAS distribution.<br />
<br />
'''openSUSE Repositories:''' Requests for more packages in openSUSE repositories and a ports system like Arch's AUR are made.<br />
<br />
'''KDE Support:''' Users ask for continued support for KDE on openSUSE Tumbleweed.<br />
<br />
'''Server and Desktop Needs:''' Users emphasize the importance of different distributions for server and desktop needs, with specific stability requirements.<br />
<br />
'''Graphics Support:''' Better graphics support, including improved drivers for older and new hardware, is desired.<br />
Improved Desktop Experience: Users express the need for an improved desktop experience, including support for peripherals and reducing complications.<br />
<br />
'''LSB Standardization:''' Some users call for standardizing on the Linux Standard Base (LSB) for easier application development.<br />
Focusing on Support: OpenSUSE is urged to focus on offering support through books, training, and knowledge sharing.<br />
<br />
'''Geoinformatics Tools:''' Users express a need for better tools for geoinformatics on openSUSE.<br />
<br />
'''Electron App Rendering:''' Users are frustrated with how Electron-based applications render on Wayland compositors.<br />
<br />
'''Marketing and Awareness:''' Better marketing and efforts to increase Linux adoption and awareness are suggested.<br />
Please note that the variety of responses reflects the diverse needs and expectations of Linux users across different use cases.<br />
<br />
=== Would you recommend Linux to others in your industry for the use cases you've explored? Why or why not? ===<br />
<br />
The comments reflect a wide range of opinions regarding recommending Linux in various industries and use cases. Some key points that emerge from these comments are:<br />
<br />
'''Server Workloads:''' Linux is highly recommended for server workloads. It is praised for its stability, performance, and its ability to ease the management of distributed computing instances. It is seen as the best option for these scenarios, with no real alternatives.<br />
<br />
'''Development and Privacy:''' Many people recommend Linux for development purposes, highlighting its flexibility, openness, and privacy features. It's viewed as a superior platform for coding and learning new things.<br />
<br />
'''Customization and Freedom:''' Linux is praised for its customizability and the freedom it provides to users. It's seen as a system that lets you have more control and tailor it to your specific needs.<br />
<br />
'''Cost Savings:''' Some recommend Linux because it's free and open source, which can save money compared to proprietary alternatives like Windows.<br />
Security: Security-conscious users appreciate Linux for its robust security features.<br />
<br />
'''Mixed Recommendations:''' Some express hesitation about recommending Linux for certain use cases. They point out that Linux might not be suitable for everyone and that there can be limitations, especially in environments that rely heavily on proprietary software.<br />
<br />
'''Challenges with Gaming and Compatibility:''' Gaming is mentioned as a challenge, but there's optimism about Linux's future in this area due to the improvement of tools like Proton.<br />
<br />
'''Specific Use Cases:''' Recommendations vary depending on the use cases and the specific requirements of the industry. Some industries might be more receptive to Linux than others.<br />
<br />
'''Learning Curve:''' The comments highlight the need for users to be somewhat tech-savvy and willing to adapt to a different operating system.<br />
Support and Knowledge: The availability of Linux expertise and support is mentioned as a critical factor when recommending it.<br />
<br />
In summary, Linux is highly recommended for server workloads, development, and privacy-conscious users. However, the suitability of Linux for a particular industry or use case often depends on factors like software compatibility, user expertise, and the willingness to adapt to a different operating system.</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=File:Usecase2023-use-of-IT.svg&diff=181121File:Usecase2023-use-of-IT.svg2023-11-06T11:09:47Z<p>Bmwiedemann: rendered with Libreoffice calc from data in https://en.opensuse.org/Usecase2023</p>
<hr />
<div>== Summary ==<br />
rendered with Libreoffice calc from data in https://en.opensuse.org/Usecase2023</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Reproducible_Builds&diff=180983openSUSE:Reproducible Builds2023-11-02T19:15:01Z<p>Bmwiedemann: /* With OBS */ change Y to 1 for fedora's 0%{? expansion</p>
<hr />
<div>For openSUSE Reproducible Builds we are trying to identify packages that produce different binaries when building on different hosts or times. And then we remove the sources of those diffs.<br />
<br />
== Resources ==<br />
* https://reproducible-builds.org/ collects information around reproducible builds <br />
* https://reproducible-builds.org/docs/buy-in/ lists why reproducible builds are useful.<br />
* https://github.com/bmwiedemann/reproducibleopensuse scripts to help us find issues with openSUSE OBS packages<br />
* https://rb.zq1.de/compare.factory/ diffs of unreproducible packages (is a symlink pointing to the latest results dir)<br />
* https://github.com/bmwiedemann/theunreproduciblepackage examples and explanations of sources of indeterminism<br />
* [https://bugzilla.opensuse.org/show_bug.cgi?id=1081754 master trackerbug]<br />
* https://lists.reproducible-builds.org/pipermail/rb-general/2018-December/001301.html summary of rpm/OBS/osc/obs-build/build-compare r-b work<br />
* https://events.opensuse.org/conference/oSC16/program/proposal/838 openSUSE conference talk from 2016<br />
* https://events.opensuse.org/conference/oSC17/program/proposal/1236 openSUSE conference talk from 2017<br />
* https://ossna2022.sched.com/event/11NpJ/reproducible-builds-unexpected-benefits-and-problems-bernhard-m-wiedemann-suse https://www.youtube.com/watch?v=RfN2eWn6c9o SupplyChainSecurityCon talk from 2022<br />
<br />
If you want to help, contact Bernhard M. Wiedemann <reproducibleopensuse zq1.de><br />
<br />
Besides the distribution independent chat there is https://matrix.to/#/#reproducible-builds:opensuse.org<br />
<br />
== With OBS ==<br />
<br />
If you want OBS to produce verifyable bit-identical binaries for you, <br />
you need to have in your project's [https://build.opensuse.org/project/prjconf/home:bmwiedemann:reproducible prjconf]<br />
Macros:<br />
%source_date_epoch_from_changelog 1<br />
%clamp_mtime_to_source_date_epoch 1<br />
%use_source_date_epoch_as_buildtime 1<br />
%_buildhost reproducible<br />
:Macros<br />
<br />
You can also edit it in a shell with<br />
osc meta -e prjconf $PROJECT<br />
<br />
The first macro is already default-on in Tumbleweed and Leap-15.0, Leap 15.1, and Leap 15.2.<br />
The other macros will normalize build times and hostname values. So if you want to find out when and where a package was actually built, you need to look at the signature date and use <code>osc jobhistory</code>.<br />
<br />
When you just enabled these macros, packages will remain as they are. After the next source change or<br />
osc wipebinaries --repo=openSUSE_Tumbleweed --all $PROJECT<br />
newly built binaries will be created and published. Just 'rebuild' is not enough, because build-compare will notice that it is similar to the old packages and discard the new build result.<br />
<br />
Packages from OBS will only be bit-identical to your local builds after processing them with<br />
rpm --delsign $RPMPACKAGE<br />
<br />
== Verifying ==<br />
<br />
You can do a local build and compare it to the OBS build result by calling the [https://github.com/bmwiedemann/reproducibleopensuse/blob/master/nachbau nachbau] script in a checkout dir. See the repo's README.md for setup instructions.<br />
<br />
== Debugging ==<br />
See the [https://github.com/bmwiedemann/reproducibleopensuse/blob/master/howtodebug guide on how to find, debug and fix reproducibility issues in openSUSE OBS packages]</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=179903openSUSE:Slowroll2023-10-13T12:50:53Z<p>Bmwiedemann: add autorefresh to all repos to avoid nasty surprises on major version bumps</p>
<hr />
<div>== What ==<br />
<br />
[[File:OpenSUSE Slowroll green logo.svg|160x76px|links|Logo of openSUSE Slowroll]]<br />
<br />
Slowroll is a new experimental distribution from 2023 based on Tumbleweed, but rolling slower. With big updates every one or two months, and continous bug fixes and security fixes as they come in. <br />
[[File:Slowroll-vs-tumbleweed-updates.svg|thumb]]<br />
<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
http://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/ but leave the network disabled (so it does not pull in newer Tumbleweed packages from online repos)<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar --refresh http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar --refresh http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar --refresh -p 80 http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
zypper ar --refresh --disable http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/src-oss/ base-src-oss<br />
zypper ar --refresh http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
zypper ar --refresh -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=179900openSUSE:Slowroll2023-10-13T12:15:01Z<p>Bmwiedemann: +diagram</p>
<hr />
<div>== What ==<br />
<br />
[[File:OpenSUSE Slowroll green logo.svg|160x76px|links|Logo of openSUSE Slowroll]]<br />
<br />
Slowroll is a new experimental distribution from 2023 based on Tumbleweed, but rolling slower. With big updates every one or two months, and continous bug fixes and security fixes as they come in. <br />
[[File:Slowroll-vs-tumbleweed-updates.svg|thumb]]<br />
<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
http://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/ but leave the network disabled (so it does not pull in newer Tumbleweed packages from online repos)<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar -p 80 --refresh http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
zypper ar --disable http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/src-oss/ base-src-oss<br />
zypper ar http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
zypper ar -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=File:Slowroll-vs-tumbleweed-updates.svg&diff=179897File:Slowroll-vs-tumbleweed-updates.svg2023-10-13T12:13:51Z<p>Bmwiedemann: </p>
<hr />
<div>How Slowroll updates compared to Tumbleweed</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=179816openSUSE:Slowroll2023-10-09T15:17:22Z<p>Bmwiedemann: codecs does not work with https either.</p>
<hr />
<div>== What ==<br />
<br />
[[File:OpenSUSE Slowroll green logo.svg|160x76px|links|Logo of openSUSE Slowroll]]<br />
<br />
Slowroll is a new experimental distribution from 2023 based on Tumbleweed, but rolling slower. With updates every one or two months with bug fixes and CVE fixes as they come in.<br />
<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
http://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/ but leave the network disabled (so it does not pull in newer Tumbleweed packages from online repos)<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar -p 80 --refresh http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
zypper ar --disable http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/src-oss/ base-src-oss<br />
zypper ar http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
zypper ar -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=179633openSUSE:Slowroll2023-10-01T16:30:36Z<p>Bmwiedemann: fix h264 codecs repo</p>
<hr />
<div>== What ==<br />
<br />
[[File:OpenSUSE Slowroll green logo.svg|160x76px|links|Logo of openSUSE Slowroll]]<br />
<br />
Slowroll is a new experimental distribution from 2023 based on Tumbleweed, but rolling slower. With updates every one or two months with bug fixes and CVE fixes as they come in.<br />
<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
http://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/ but leave the network disabled (so it does not pull in newer Tumbleweed packages from online repos)<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar -p 80 --refresh http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
zypper ar --disable http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/src-oss/ base-src-oss<br />
zypper ar https://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
zypper ar -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=179516openSUSE:Slowroll2023-09-26T14:03:31Z<p>Bmwiedemann: +logo</p>
<hr />
<div>== What ==<br />
<br />
[[File:OpenSUSE Slowroll green logo.svg|160x76px|links|Logo of openSUSE Slowroll]]<br />
<br />
Slowroll is a new experimental distribution from 2023 based on Tumbleweed, but rolling slower. With updates every one or two months with bug fixes and CVE fixes as they come in.<br />
<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
http://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/ but leave the network disabled (so it does not pull in newer Tumbleweed packages from online repos)<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar -p 80 --refresh http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
zypper ar --disable http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/src-oss/ base-src-oss<br />
zypper ar http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
zypper ar -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=File:OpenSUSE_Slowroll_green_logo.svg&diff=179513File:OpenSUSE Slowroll green logo.svg2023-09-26T13:47:30Z<p>Bmwiedemann: Bmwiedemann uploaded a new version of File:OpenSUSE Slowroll green logo.svg</p>
<hr />
<div>== Summary ==<br />
based on Tumbleweed svg</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=File:OpenSUSE_Slowroll_green_logo.svg&diff=179510File:OpenSUSE Slowroll green logo.svg2023-09-26T13:33:12Z<p>Bmwiedemann: Bmwiedemann uploaded a new version of File:OpenSUSE Slowroll green logo.svg</p>
<hr />
<div>== Summary ==<br />
based on Tumbleweed svg</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=File:OpenSUSE_Slowroll_green_logo.svg&diff=179507File:OpenSUSE Slowroll green logo.svg2023-09-26T13:09:01Z<p>Bmwiedemann: Bmwiedemann uploaded a new version of File:OpenSUSE Slowroll green logo.svg</p>
<hr />
<div>== Summary ==<br />
based on Tumbleweed svg</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=File:OpenSUSE_Slowroll_green_logo.svg&diff=179504File:OpenSUSE Slowroll green logo.svg2023-09-26T13:00:24Z<p>Bmwiedemann: based on Tumbleweed svg</p>
<hr />
<div>== Summary ==<br />
based on Tumbleweed svg</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=179366openSUSE:Slowroll2023-09-19T12:47:57Z<p>Bmwiedemann: clarify DVD install + drop NET-install</p>
<hr />
<div>== What ==<br />
<br />
Slowroll is a new distribution from 2023 based on Tumbleweed, but rolling slower. With updates every one or two months with bug fixes and CVE fixes as they come in.<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
http://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/ but leave the network disabled (so it does not pull in newer Tumbleweed packages from online repos)<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar -p 80 --refresh http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
zypper ar --disable http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/src-oss/ base-src-oss<br />
zypper ar http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
zypper ar -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=179345openSUSE:Slowroll2023-09-15T07:20:54Z<p>Bmwiedemann: change URLs to http as CDN has trouble with https</p>
<hr />
<div>== What ==<br />
<br />
Slowroll is a new distribution from 2023 based on Tumbleweed, but rolling slower. With updates every one or two months with bug fixes and CVE fixes as they come in.<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
http://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/<br />
or use the NET iso with a boot parameter of install=http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar -p 80 --refresh http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
zypper ar --disable http://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/src-oss/ base-src-oss<br />
zypper ar http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
zypper ar -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=179330openSUSE:Slowroll2023-09-14T03:24:42Z<p>Bmwiedemann: +staging</p>
<hr />
<div>== What ==<br />
<br />
Slowroll is a new distribution from 2023 based on Tumbleweed, but rolling slower. With updates every one or two months with bug fixes and CVE fixes as they come in.<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
https://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/<br />
or use the NET iso with a boot parameter of install=https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar -p 80 --refresh https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
zypper ar --disable https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/src-oss/ base-src-oss<br />
zypper ar http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
zypper ar -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Untested packages go into https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll:Staging first and are tested by openQA (TBD)<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)<br />
{{IW|openSUSE:Slowroll}}</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=179183openSUSE:Slowroll2023-09-11T10:14:56Z<p>Bmwiedemann: +h264</p>
<hr />
<div>== What ==<br />
<br />
Slowroll is a new distribution from 2023 based on Tumbleweed, but rolling slower. With updates every one or two months with bug fixes and CVE fixes as they come in.<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
https://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/<br />
or use the NET iso with a boot parameter of install=https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar -p 80 https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
zypper ar --disable https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/src-oss/ base-src-oss<br />
zypper ar http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264<br />
zypper ar -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=179108openSUSE:Slowroll2023-09-09T17:00:26Z<p>Bmwiedemann: </p>
<hr />
<div>== What ==<br />
<br />
Slowroll is a new distribution from 2023 based on Tumbleweed, but rolling slower. With updates every one or two months with bug fixes and CVE fixes as they come in.<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
https://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/<br />
or use the NET iso with a boot parameter of install=https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar -p 80 https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
zypper ar --disable https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/src-oss/ base-src-oss<br />
zypper ar -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=179093openSUSE:Slowroll2023-09-08T10:07:39Z<p>Bmwiedemann: </p>
<hr />
<div>== What ==<br />
<br />
Slowroll is a new distribution from 2023 based on Tumbleweed, but rolling slower. With updates every one or two months with bug fixes and CVE fixes as they come in.<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
https://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/<br />
or use the NET iso with a boot parameter of install=https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar -p 80 https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
zypper ar --disable https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/src-oss/ base-src-oss<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
Like Tumbleweed, use '''zypper dup''' to upgrade.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=178961openSUSE:Slowroll2023-08-30T12:07:31Z<p>Bmwiedemann: </p>
<hr />
<div>== What ==<br />
<br />
Slowroll is a new distribution from 2023 based on Tumbleweed, but rolling slower. With updates every one or two months with bug fixes and CVE fixes as they come in.<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
https://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/<br />
or use the NET iso with a boot parameter of install=https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar -p 80 https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
zypper ar --disable https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/src-oss/ base-src-oss<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=178949openSUSE:Slowroll2023-08-29T13:01:09Z<p>Bmwiedemann: add source repo</p>
<hr />
<div>== What ==<br />
<br />
Slowroll is a new distribution from 2023 based on Tumbleweed, but rolling slower.<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
https://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/<br />
or use the NET iso with a boot parameter of install=https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
zypper ar --disable https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/src-oss/ base-src-oss<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:ALP/ArchitectureTeam&diff=178940openSUSE:ALP/ArchitectureTeam2023-08-29T12:17:31Z<p>Bmwiedemann: </p>
<hr />
<div>[[File:Alp-architecture-team.png|thumb|right]]<br />
<br />
__TOC__<br />
<br />
<div class="greybar"><br />
=== Introduction ===<br />
</div><br />
The openSUSE ALP Architecture Team is the group of openSUSE volunteers investigating building new openSUSE distributions based on SUSE Adaptable Linux Platform (ALP).<br />
<br />
The inaugural project the ALP Architecture Team is tackling is investigating a future replacement for Leap based on the SUSE ALP codebase and [[openSUSE:ALP/BuildDesign|build design]].<br />
<br />
<div class="greybar"><br />
<br />
=== Communicate ===<br />
</div><br />
The Team primarily discusses on a Matrix chat channel<br />
* https://matrix.to/#/#alp:opensuse.org<br />
<br />
This channel is also bridged to Discord and IRC<br />
* https://discord.gg/opensuse<br />
* ircs://libera.chat/#opensuse-alp<br />
<br />
<div class="greybar"><br />
=== Members ===<br />
</div><br />
The team currently consists of the following members<br />
<br />
* Richard Brown<br />
* Lubos Kocman<br />
* Max Lin<br />
* Marcus Meissner<br />
* Simon Lees<br />
* Bernhard Wiedemann<br />
* Kris Scott<br />
* Felix Niederwanger<br />
* Alexandre Vicenzi<br />
* Maurizio Galli<br />
* Antonio Teixeira<br />
* Valentin Lefebvre<br />
* Emiliano Langella<br />
* David Dyess<br />
* Robin Shepheard<br />
* Dirk Müller<br />
* Morgan Green<br />
<br />
<div class="greybar"><br />
<br />
=== How to join ===<br />
</div><br />
The team is open to all. Please just add your name to the list above and join the Matrix/IRC/Discord channel and get involved.<br />
<br />
=== Kick Off Meeting ===<br />
The ALP Architecture Team kick-off meeting happened on Tuesday 27th June at 1430 UTC for 1 hour.<br />
<br />
A recording of the presentation is here: https://youtu.be/hLWvC1c7Fms<br />
<br />
The Agenda for this meeting was primarily a presentation from Richard Brown (Distribution Architect @ SUSE), covering the following:<br />
<br />
* What is SUSE ALP?<br />
* What SUSE be building, and when.<br />
* How Richard sees the 'gap' between what SUSE ALP will be and what our current Leap user base expects.<br />
* Richard's initial thoughts on how this group might want to address that 'gap'<br />
<br />
<div class="greybar"><br />
<br />
=== Meeting Minutes===<br />
</div><br />
Kickoff Minutes- https://etherpad.opensuse.org/p/weeklymeeting20230627<br />
<br />
=== Experimental/Research Projects ===<br />
<br />
As a consequence of the Kick Off, contributors have been encouraged to consider different possible approaches to address the needs of Leap users who otherwise might not be satisfied by the planned ALP offerings. These approaches should then be experimented/prototyped for others to be able to understand them and better evaluate their feasibility.<br />
<br />
These different Experimental Projects are likely to be hosted in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental<br />
<br />
==== Experiment 1: Slowroll ====<br />
main page: [[openSUSE:Slowroll]]<br />
<br />
"Slowroll" - a derivative codestream of openSUSE:Factory/ALP:Source:Rolling that uses automated rules to limit the rate of change to the codebase<br />
<br />
{|class="wikitable"<br />
|-<br />
| Experiment Owner || bmwiedemann<br />
|-<br />
| OBS Project || https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
|}<br />
<br />
==== Experiment 2: Linarite ====<br />
<br />
"Linarite" - a successor to the [[openSUSE:ALP/Workgroups/GrassyKnoll|GrassyKnoll]] concept, building a community distribution atop SUSE ALP "Granite"<br />
<br />
{|class="wikitable"<br />
|-<br />
|Aims <br />
|To be a Granite++ Ie Take the concepts of SUSE's Traditional ALP based distro and expand them with community packages and support to ideally become a successor to Leap<br />
|-<br />
|Experiment Owner<br />
|simotek<br />
|-<br />
|OBS Project<br />
|https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Linarite<br />
|}<br />
<br />
[[Category:Team pages]]<br />
<br />
__NOTOC__</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=178937openSUSE:Slowroll2023-08-29T12:14:24Z<p>Bmwiedemann: +install</p>
<hr />
<div>== What ==<br />
<br />
Slowroll is a new distribution from 2023 based on Tumbleweed, but rolling slower.<br />
<br />
== Use ==<br />
<br />
For initial install, you can use the DVD iso from<br />
https://download.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/iso/<br />
or use the NET iso with a boot parameter of install=https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/<br />
<br />
To use in Leap or an older Tumbleweed, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=178934openSUSE:Slowroll2023-08-29T11:46:28Z<p>Bmwiedemann: add update path</p>
<hr />
<div>== What ==<br />
<br />
Slowroll is a new distribution from 2023 based on Tumbleweed, but rolling slower.<br />
<br />
== Use ==<br />
<br />
To use, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools<br />
<br />
Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. <br />
Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly)</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Slowroll&diff=178931openSUSE:Slowroll2023-08-29T11:38:02Z<p>Bmwiedemann: init</p>
<hr />
<div>== What ==<br />
<br />
Slowroll is a new distribution from 2023 based on Tumbleweed, but rolling slower.<br />
<br />
== Use ==<br />
<br />
To use, replace repositories<br />
<br />
rm /etc/zypp/repos.d/*<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/oss/ base-oss<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/base/repo/non-oss/ base-non-oss<br />
zypper ar https://cdn.opensuse.org/repositories/openSUSE:/ALP:/Experimental:/Slowroll/standard/ update<br />
<br />
We do not recommend using devel repos on top, unless those are specifically compiled for Slowroll. Tumbleweed might work, but might also break occasionally.<br />
<br />
== Development ==<br />
<br />
bmwiedemann did the design and scripting.<br />
<br />
Development happens in https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll<br />
with the use of https://github.com/bmwiedemann/slowroll-tools</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Heroes&diff=176138openSUSE:Heroes2023-06-16T08:15:26Z<p>Bmwiedemann: add me</p>
<hr />
<div><!-- Template:Navbar is used to connect similar articles in one easy to navigate group --><br />
{{Services_navbar}}<br />
<br />
<br />
[[Image:Heroes logo.png|500px|center|Infrastructure]]<br />
<br />
{| style="width:100%"<br />
|}<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#000000"><br />
=== Introduction ===<br />
</div><br />
Heroes Team members are volunteers helping the project with all system administration related tasks. It consists of people with skills ranging from generic Administrators over to Storage and Network experts. The team also welcomes new volunteers who want to start learning new skills.<br />
<br />
In short: the team helps the openSUSE community make their ideas and dreams come true.<br />
<br />
Check out videos of past openSUSE Conferences where we give more details about the Team and the openSUSE infrastructure and services: [https://www.youtube.com/watch?v=91xKCInVSKM&index=32&list=PL_AMhvchzBafyMDGuvBmtb45mhmukdLOP oSC13] [https://www.youtube.com/watch?v=Cp5vAaTI3wQ&index=35&list=PL_AMhvchzBaeV36wYqnKb7xWAN0zfDfjz oSC15] [https://www.youtube.com/watch?v=-CYHkNym124&index=43&list=PL_AMhvchzBaeIQntCDiVNUUgmRaAzam1V oSC16] [https://www.youtube.com/watch?v=QSXniKW_q9Q oSC17]<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#000000"><br />
<br />
=== Communication ===<br />
</div><br />
As team we communicate over a lot of channels. Mostly mailing list and IRC.<br />
<br />
* join our monthly [[openSUSE:Heroes/Meetings|meeting]] - usually at the first Thursday of a month at 20:00 CET / 18:00 UTC at https://meet.opensuse.org/heroes.<br />
* [mailto:admin@opensuse.org admin@opensuse.org] is where you create issues in our ticket system (https://progress.opensuse.org).<br />
{{Mailinglist|heroes|Is our mailing list and communication channel}} <br />
* [irc://irc.opensuse.org/opensuse-admin #opensuse-admin] is the generic channel where you can reach us. We have a bot there that logs the discussions. You can have a look at former discussions [https://monitor.opensuse.org/heroes/ here].<br />
* [irc://irc.opensuse.org/opensuse-buildservice #opensuse-buildservice] is the channel to reach build service administrators.<br />
* We post information about maintenance of the infrastructure to [https://status.opensuse.org/ status.opensuse.org].<br />
* For ways to communicate with us individually check our list of [[openSUSE:Services_team#Members|members]].<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#0b5147"><br />
<br />
=== System Administration ===<br />
</div><br />
One of the main areas of work for the Heroes Team is the system administration of the infrastructure for openSUSE. Here is a short list of areas that need our/your help:<br />
* The [[openSUSE:Mirror_infrastructure|mirror infrastructure]] used for deploying images and packages over the world.<br />
* The [[Portal:Build_Service|Build Service]] - working on the [https://github.com/openSUSE/open-build-service source code], helping [[openSUSE:Build_Service_installations|Build Service Users]] in [ircs://irc.libera.chat/opensuse-buildservice #opensuse-buildservice].<br />
* Providing the infrastructure behind projects like the [[Portal:Conference|openSUSE Conference]], the [[Portal:Documentation|Documentation]] or the [[openSUSE:Maintenance_team|Maintenance]].<br />
* Maintaining infrastructure as code [https://code.opensuse.org/heroes/salt in Git using SaltStack].<br />
* Operating various public services -> check the mega-menu by clicking on the icon on the top right!<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#0b5147"><br />
<br />
=== Duties ===<br />
</div><br />
Many team members have special areas of interest (others call it "hobbies") and take care of maintaining specific services, others help out generally with day to day tasks.<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#0b5147"><br />
<br />
=== Members ===<br />
</div><br />
<br />
{| class="wikitable sortable"<br />
! Image<br />
! Name <br />
! IRC (Libera) nick <br />
! Blog <br />
! Email <br />
<span style="font-weight:100;">(add opensuse.org behind the @)</span><br />
! Area of expertise<br />
|-<br />
| align="left" | <br />
| [[User:cboltz|Christian Boltz]] <br />
| cboltz<br />
| -<br />
| cboltz@<br />
| wiki server admin, admin for English wiki, salting servers and services<br />
|-<br />
| align="left" | <br />
| [[User:AdaLovelace|Sarah Kriesch]] <br />
| AdaLovelace<br />
| -<br />
| sarah.kriesch@<br />
| Admin for German Wiki<br />
|-<br />
| align="left" | <br />
| [[User:TBro|Thorsten B.]]<br />
| thomic<br />
| <br />
| TBro@<br />
| openSUSE Infrastructure, SaltStack, Hardware wishlist <br />
|-<br />
| align="left" | <br />
| [[User:mcaj|Martin Caj]]<br />
| mcaj<br />
| <br />
| mcaj@<br />
| openSUSE Infrastructure, SaltStack<br />
|-<br />
<br />
| align="left" | [[Image:DSC00964a.jpeg|50px|thumbnail|left]]<br />
| [[User:pjessen|Per Jessen]]<br />
| pjessen<br />
| http://rambling.jessen.ch/<br />
| per@<br />
| A grumpy old greybeard. Mailing list manager, mail servers, DNS, mirror infrastructure, general dogsbody &amp; overall nuisance. <br />
|-<br />
| align="left" |<br />
| [[User:IonutVan|Ioan Vancea]]<br />
| IonutVan<br />
| https://www.vioan.eu/<br />
| IonutVan@<br />
| ~ to be assigned ~<br />
|-<br />
| align="left" |<br />
| [[User:okurz|Oliver Kurz]]<br />
| okurz<br />
|<br />
| okurz@<br />
| openQA (openqa.opensuse.org)<br />
|-<br />
| align="left" |<br />
| [[User:mstrigl|Marco Strigl]]<br />
| lethliel<br />
|<br />
| mstrigl@<br />
| openSUSE Infrastructure, Videoteam<br />
|-<br />
| align="left" | [[Image:LCP.png|50px|thumbnail|left]]<br />
| [[User:hellcp|Jacob Michalskie]]<br />
| lcp<br />
| https://lcp.world<br />
| hellcp@<br />
| Whatever's needed<br />
|-<br />
| align="left" |<br />
| [[User:bmwiedemann|Bernhard]]<br />
| bmwiedemann<br />
| -<br />
| bmwiedemann@<br />
| download.o.o and co, Miscellaneous<br />
|-<br />
| align="left" |<br />
| [[User:crameleon|Georg]]<br />
| acidsys<br />
| -<br />
| crameleon@<br />
| Infrastructure, SaltStack, Miscellaneous<br />
|-<br />
|}<br />
<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#0b5147"><br />
<br />
=== Contributions ===<br />
</div><br />
You want to contribute to our openSUSE infrastructure? Contact us via [irc://irc.libera.chat/#opensuse-admin IRC] or at the [https://lists.opensuse.org/archives/list/heroes@lists.opensuse.org/ mailing list].<br />
<br />
Check the list of [[Portal:Teams|teams]] to learn more about which teams exist in the project.<br />
<br />
[[Category:Team pages]]<br />
[[Category:Infrastructure]]<br />
__NOTOC__</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Roadmap&diff=175833openSUSE:Roadmap2023-06-07T15:05:10Z<p>Bmwiedemann: update to 15.6</p>
<hr />
<div>== openSUSE Release Cycle ==<br />
<br />
[[Portal:Tumbleweed|openSUSE Tumbleweed]] is openSUSE's rolling release, which is constantly updated and always at the 'latest release'.<br />
<br />
[[Portal:Leap|openSUSE Leap]] is openSUSE's regular release, which is has the following estimated release cycle:<br />
<br />
* One minor release is expected approximately every 12 months, aligned with SUSE Linux Enterprise Service Packs<br />
* One major release is expected after approximately 36–48 months, aligned with SUSE Linux Enterprise Releases.<br />
* openSUSE Leap 15.6 is confirmed<br />
<br />
'''openSUSE Leap is always based on the newest SUSE Linux Enterprise Server available to the date, which means Leap would have a major version update if a successor to SUSE Linux Enterprise 15 becomes available.'''<br />
<br />
SUSE Linux Enterprise 15 has already confirmed that there will be Service Pack 7.<br />
As of today we plan to have openSUSE Leap 15.6 and would like to come with a Leap 15.X successor in year 2024. This would result in a length of community support for Leap 15 of 84 (7*12 SP0..SP6) months.'''<br />
<br />
The life cycle of openSUSE Tumbleweed and Leap are documented in [[Lifetime|The Lifetime Wiki Page]].<br />
<br />
== Active openSUSE Leap releases ==<br />
<br />
=== Schedule for openSUSE Leap 15.6 ===<br />
<br />
TBD<br />
Release around 2024-06<br />
<br />
=== Schedule for openSUSE Leap 15.4 ===<br />
<br />
[https://raw.githubusercontent.com/openSUSE/openSUSE-release-process/master/schedule/Leap-15.4-Schedule.txt Schedule in .txt] | [https://raw.githubusercontent.com/openSUSE/openSUSE-release-process/master/schedule/Leap-15.4-Schedule.ics Schedule in .ics]<br />
<br />
------------------------------------------------------------------------------<br />
Wed, Jun 8, 2022 Public Availability of the Release<br />
<br />
o openSUSE Leap 15.4 was released to the public at 12:00 UTC<br />
<br />
------------------------------------------------------------------------------<br />
<br />
Wed, Oct 5th, 2022 Quarterly Update 1<br />
<br />
o Respin of installation images, if we identify a reason to respin (can be skipped)<br />
<br />
------------------------------------------------------------------------------<br />
Wed, Jan 18th, 2023 Quarterly Update 2<br />
<br />
o Respin of installation images, if we identify a reason to respin (can be skipped)<br />
<br />
------------------------------------------------------------------------------<br />
Wed, May 3rd, 2023 Quarterly Update 3<br />
<br />
o Respin of installation images, if we identify a reason to respin (can be skipped)<br />
<br />
------------------------------------------------------------------------------<br />
<br />
=== Schedule for openSUSE Leap 15.5 ===<br />
<br />
[https://raw.githubusercontent.com/openSUSE/openSUSE-release-process/master/schedule/Leap-15.5-Schedule.txt Schedule in .txt] | [https://raw.githubusercontent.com/openSUSE/openSUSE-release-process/master/schedule/Leap-15.5-Schedule.ics Schedule in .ics]<br />
<br />
------------------------------------------------------------------------------<br />
Fri, July 15, 2022 Start of Development phase<br />
<br />
o openSUSE Leap and Backports OBS projects are set up.<br />
o openSUSE Leap 15.5 is Alpha.<br />
o SUSE:SLE-15-SP5:GA is being synced to OBS<br />
o Release checklist for Leap 15.5 is in progress-o-o<br />
<br />
------------------------------------------------------------------------------<br />
Fri, July 29, 2022 SLES Features are Submitted to E&I<br />
o Features must be in JIRA and submitted to E&I<br />
<br />
------------------------------------------------------------------------------<br />
Fri, September 9, 2022 SLES Final Decision and Feedback Deadline for features<br />
o Starts late feature process<br />
<br />
------------------------------------------------------------------------------<br />
Wed, September 21, 2022 Engineering Interlock<br />
o Week after Interlock for SUSE Linux Enteprise<br />
<br />
------------------------------------------------------------------------------<br />
Fri, September 30, 2022 SLES Code Drop Deadline for partners<br />
o Informative! SLES code drop deadline for SUSE's partners<br />
<br />
------------------------------------------------------------------------------<br />
Wed, Jan 25, 2023 Checkin Deadline for Beta<br />
<br />
o Deadline is at 15:00 UTC<br />
o Deadline for any package removals from Leap.<br />
o Deadline corresponds with SLE 15 SP5 late feature cutoff deadline and Snap 3 prior Public Beta<br />
<br />
------------------------------------------------------------------------------<br />
Wed, Jan 25, 2023 Late Feature Request Cutoff for SLE<br />
<br />
o Every feature with a code delivery for SUSE Linux Enterprise after this date requires an ECO and may be targeted post FCS date. Does not apply for Leap code-drops.<br />
o After this date only P1 bugfixes, important security fixes and pre-agreed important P2 fixes are accepted in SUSE Linux Enterprise. This does not apply for Leap code-drops.<br />
<br />
------------------------------------------------------------------------------<br />
Wed, Feb 16, 2023 Beta build is done<br />
<br />
o Week after SLES 15 SP5 Public Beta<br />
o openSUSE Leap 15.5 is Beta<br />
o Maintenance team starts working on maintenance setup <br />
<br />
<br />
------------------------------------------------------------------------------<br />
Thu, April 12th, 2023 Checkin Deadline for RC<br />
<br />
o Deadline is at 15:00 UTC<br />
o Corresponds with a deadline for two weekly snapshots prior to SLE's Public RC<br />
o Only important bugfixes should be accepted after this point<br />
<br />
------------------------------------------------------------------------------<br />
Wed, April 27, 2023 RC build is done<br />
<br />
o RC build is done<br />
o Maintenance setup is done<br />
o Leap Code freeze.<br />
o Backports project freeze ahead of Leap<br />
o Stop using snapshot of SLES 15 SP5 changes<br />
<br />
------------------------------------------------------------------------------<br />
Wed, May 11, 2023 Gold Master code submission deadline<br />
<br />
o In sync with SLES GMC candidate code submission deadline<br />
<br />
------------------------------------------------------------------------------<br />
Fri, May 14, 2023 Deadline for Documentation and Translations<br />
<br />
o All translations were pulled this has to happen prior GM<br />
<br />
------------------------------------------------------------------------------<br />
Wed, May 31, 2023 Gold Master build is done<br />
<br />
o Leap is GOLD<br />
<br />
------------------------------------------------------------------------------<br />
Wed, Jun 7, 2023 Public Availability of the Release<br />
<br />
o openSUSE Leap 15.5 will be released to the public at 12:00 UTC<br />
<br />
------------------------------------------------------------------------------<br />
Thu, Jun 8, 2024 Release retrospective survey is open<br />
<br />
o Release retro on survey.opensuse.org is open right after GA<br />
<br />
------------------------------------------------------------------------------<br />
Thu, Jun 22, 2024 Collect feedback from the retrospective<br />
<br />
o Share feedback of the retrospective with community.<br />
<br />
------------------------------------------------------------------------------<br />
Wed, Oct 4th, 2024 Quarterly Update 1<br />
<br />
o Respin of installation images, if we identify a reason to respin (can be skipped)<br />
<br />
------------------------------------------------------------------------------<br />
Wed, Jan 17th, 2024 Quarterly Update 2<br />
<br />
o Respin of installation images, if we identify a reason to respin (can be skipped)<br />
<br />
------------------------------------------------------------------------------<br />
Wed, May 8th, 2024 Quarterly Update 3<br />
<br />
o Respin of installation images, if we identify a reason to respin (can be skipped)<br />
<br />
------------------------------------------------------------------------------<br />
Tue, Dec 31st, 2024 EOL<br />
<br />
o Leap 15.5 is End of life. See [[SDB:How_to_migrate_to_SLE]] for a longer support.<br />
<br />
------------------------------------------------------------------------------<br />
<br />
== Active openSUSE Leap Micro releases ==<br />
<br />
Leap Micro is simply a re-brand of SLE Micro rpms with some product building configuration tweaks.<br />
<br />
Our goal is to be tailing SLE Micro typically with roughly a one month delay, <br />
hat usually translates into the previous milestone.<br />
<br />
We expect SLE Micro 5.4 to be the last 5.X release of Micro as according to [SLE Micro lifecycle infromation](https://documentation.suse.com/sle-micro/5.2/html/SLE-Micro-all/cha-upgrade-introduction.html#sec-upgrade-slemicro-lifecycle)<br />
SLE Micro is released twice a year.<br />
<br />
<br />
------------------------------------------------------------------------------<br />
=== Schedule for openSUSE Leap Micro 5.2 ===<br />
<br />
<br />
------------------------------------------------------------------------------<br />
Thu, Mar 31, 2022 Beta build is done<br />
<br />
o Typically around first SLE Micro 5.2 RC<br />
o openSUSE Leap Micro 5.2 is Beta<br />
o Maintenance team starts working on maintenance setup <br />
o get.opensuse.org availability<br />
<br />
------------------------------------------------------------------------------<br />
Tue, May 3, 2022 RC build is done<br />
<br />
o RC build is done<br />
o Maintenance setup is done<br />
o Code freeze<br />
o get.opensuse.org availability<br />
o IPRQ submitted<br />
o Security audit requested<br />
<br />
------------------------------------------------------------------------------<br />
Wed, May 18, 2022 Public Availability of the Release<br />
<br />
o openSUSE Leap Micro 5.2 will be released to the public at 12:00 UTC<br />
<br />
------------------------------------------------------------------------------<br />
Thu, April 27, 2023 Planned End of Live<br />
<br />
o openSUSE Leap Micro 5.2 will reach end of life soon after the next-next release is out<br />
<br />
------------------------------------------------------------------------------<br />
<br />
<br />
=== Schedule for openSUSE Leap Micro 5.3 ===<br />
<br />
Leap Micro is simply a re-brand of SLE Micro rpms withs ome product building configuration tweaks.<br />
Our goal is to be tailing SLE Micro typically with roughly a one month delay, <br />
hat usually translates into the previous milestone.<br />
<br />
<br />
------------------------------------------------------------------------------<br />
Thu, Sep 8, 2022 Beta build is done<br />
<br />
o Typically around first SLE Micro 5.3 RC<br />
o openSUSE Leap Micro 5.3 is Beta<br />
o Maintenance team starts working on maintenance setup <br />
o get.opensuse.org availability<br />
<br />
------------------------------------------------------------------------------<br />
Wed, Nov 9, 2022 RC build is done<br />
<br />
o RC build is done<br />
o Maintenance setup is done<br />
o Code freeze<br />
o get.opensuse.org availability<br />
o IPRQ submitted<br />
o Security audit requested<br />
<br />
------------------------------------------------------------------------------<br />
Thu, Nov 17, 2022 Public Availability of the Release<br />
<br />
o openSUSE Leap Micro 5.3 will be released to the public at 12:00 UTC<br />
<br />
------------------------------------------------------------------------------<br />
Thu, Nov 30, 2023 Planned End of Live<br />
<br />
o openSUSE Leap Micro 5.3 will reach end of life soon after the next-next release is out<br />
<br />
------------------------------------------------------------------------------<br />
<br />
=== Schedule for openSUSE Leap Micro 5.4 ===<br />
<br />
Leap Micro is simply a re-brand of SLE Micro rpms withs ome product building configuration tweaks.<br />
Our goal is to be tailing SLE Micro typically with roughly a one month delay, <br />
hat usually translates into the previous milestone.<br />
<br />
------------------------------------------------------------------------------<br />
Wed, March 1, 2023 Alpha build is done<br />
<br />
o Leap Micro 5.4 is Alpha<br />
<br />
------------------------------------------------------------------------------<br />
Tue, March 28, 2023 Beta build is done<br />
<br />
o Typically around first SLE Micro 5.4 Public RC<br />
o openSUSE Leap Micro 5.4 is Beta<br />
o Maintenance team starts working on maintenance setup <br />
o get.opensuse.org availability<br />
<br />
------------------------------------------------------------------------------<br />
Thu, April 20, 2023 RC build is done<br />
<br />
o RC build is done<br />
o Maintenance setup is done<br />
o Code freeze<br />
o get.opensuse.org availability<br />
o IPRQ submitted<br />
o Security audit requested<br />
<br />
------------------------------------------------------------------------------<br />
Thu April 27, 2023 Public Availability of the Release<br />
<br />
o openSUSE Leap Micro 5.4 will be released to the public at 12:00 UTC<br />
<br />
------------------------------------------------------------------------------<br />
Thu, May 31, 2024 Planned End of Live<br />
<br />
o openSUSE Leap Micro 5.4 will reach end of life soon after the next-next release is out<br />
<br />
------------------------------------------------------------------------------<br />
<br />
== Next-gen ==<br />
=== Draft schedule for ALP based product ===<br />
<br />
Project name TBD, for now we use "openSUSE ALP" for reference to openSUSE's take on [https://build.opensuse.org/project/show/SUSE:ALP Adaptable Linux Platform].<br />
<br />
== See also ==<br />
* [https://en.wikipedia.org/wiki/OpenSUSE Wikipedia entry] (sometimes more up to date)<br />
* [[openSUSE:Build Service Roadmap|Build Service roadmap]] page about planning details<br />
* [[openSUSE:Release_process|openSUSE Release process]]<br />
** [https://progress.opensuse.org/projects/opensuse-release-process Release process page on the openSUSE project management tool]<br />
* [[Lifetime|Lifetime of openSUSE releases]]<br />
<br />
{{IW|openSUSE:Roadmap}}<br />
[[Category:Factory|Roadmap]]</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=openSUSE:Mirror_howto&diff=170275openSUSE:Mirror howto2022-10-20T11:25:58Z<p>Bmwiedemann: recommend --ignore-existing</p>
<hr />
<div>{{Mirror navbar}}<br />
{{Intro|This document walks you through how to set up a mirror for openSUSE.}}<br />
<br />
== Walk-through ==<br />
Below, I'll list steps to set up a mirror for openSUSE content. Feel free to improve this page, or simply mail feedback to ftpadmin at suse.de.<br />
<br />
There is one big assumption made: The mirror is running openSUSE itself. This allows me to give specific directions.<br />
<br />
If you run a different operating system, the details will differ, but hopefully this howto can serve as an example nevertheless!<br />
<br />
* At first, be sure that you can afford the '''expected traffic''', and your Internet Service Provider doesn't terminate your contract!<br />
<br />
* '''packages''' to install:<br />
** rsync<br />
** chronyd or ntp (or systemd-timesyncd)<br />
** apache2-prefork or apache2-worker or nginx (or any other webserver you want to use)<br />
<br />
* take provision to '''regularly update''' the machine with security fixes<br />
<br />
* '''firewall''':<br />
** if you use one, open port 80 (HTTP) and 873 (rsync).<br />
<br />
* '''general things''': <br />
** add the hostname or IP address of a time server into /etc/chrony.d/local.conf or /etc/ntp.conf, and configure it to start (systemctl start chronyd|ntpd; systemctl enable chronyd|ntpd)<br />
** if unsure how to configure a NTP client, follow instructions from https://doc.opensuse.org/documentation/leap/reference/single-html/book-reference/index.html#cha-ntp<br />
** make sure that hostname and DNS resolution makes sense:<br />
*** check /etc/hosts, /etc/HOSTNAME, /etc/resolv.conf<br />
*** check that the commands 'hostname' and 'hostname -f' return something useful. A functioning hostname and name resolution are really helpful.<br />
<br />
* '''web server''':<br />
** assuming your mirror hostname is: mirror.example.com<br />
** create /etc/apache2/vhosts.d/mirror.example.com.conf <br />
<br />
<VirtualHost *:80><br />
ServerAdmin admin@example.com<br />
ServerName mirror.example.com<br />
<br />
DocumentRoot "/srv/pub/opensuse"<br />
<br />
<Directory "/srv/pub/opensuse"><br />
Options FollowSymLinks Indexes<br />
IndexOptions FancyIndexing VersionSort NameWidth=* Charset=UTF-8 TrackModified FoldersFirst XHTML<br />
AllowOverride None<br />
Require all granted<br />
# Order allow,deny # prior Leap 15.3 <br />
# Allow from all # prior Leap 15.3<br />
</Directory><br />
<br />
Alias /robots.txt /srv/www/mirror.example.com/robots.txt<br />
<Directory "/srv/www/mirror.example.com"><br />
Options None<br />
Require all granted<br />
# Order allow,deny # prior Leap 15.3 <br />
# Allow from all # prior Leap 15.3<br />
</Directory><br />
<br />
Include /etc/apache2/conf.d/apachestats.conf<br />
<br />
</VirtualHost><br />
<br />
** for nginx, create /etc/nginx/nginx.conf<br />
worker_processes 1;<br />
events {<br />
worker_connections 1024;<br />
use epoll;<br />
}<br />
http {<br />
include mime.types;<br />
default_type application/octet-stream;<br />
gzip on;<br />
sendfile on;<br />
tcp_nopush on;<br />
tcp_nodelay on;<br />
keepalive_timeout 65;<br />
server {<br />
listen 80;<br />
server_name mirror.example.com;<br />
access_log /var/log/nginx/access.log;<br />
location / {<br />
root /srv/pub/opensuse/;<br />
index index.html index.htm;<br />
autoindex on;<br />
}<br />
error_page 500 502 503 504 /50x.html;<br />
location = /50x.html {<br />
root /srv/www/htdocs/;<br />
}<br />
location /robots.txt { <br />
add_header Content-Type text/plain;<br />
return 200 "User-agent: *\nDisallow: /\n"; <br />
}<br />
}<br />
}<br />
<br />
** create a robots.txt to avoid web crawlers:<br />
*** mkdir /srv/www/mirror.example.com<br />
*** put this into /srv/www/mirror.example.com/robots.txt:<br />
User-agent: *<br />
Disallow: *<br />
** tuning apache for high performance:<br />
*** adjust the MPM characteristics in /etc/apache2/server-tuning.conf so that they fit the memory size of your machine. The worst thing which can happen is that it starts swapping, so Apache's maximal size needs to fit in the memory you have. The worker MPM can make better use of the available memory, however the prefork MPM is easier to configure. Watch the RSS column in ps (you can substract SHARED), and multiply it with the maximum number of processes...<br />
*** set a low KeepAliveTimeout (decrease it to 3) in /etc/apache2/server-tuning.conf<br />
** rcapache2 restart; chkconfig -a apache2<br />
<br />
* '''content''':<br />
** create a special user, and a directory to mirror to:<br />
*** groupadd mirror<br />
*** useradd -m -g mirror -c "Mirror User" -s /bin/bash mirror<br />
*** mkdir /srv/pub/opensuse<br />
*** mkdir /srv/pub/opensuse/update<br />
*** chown -R mirror:mirror /srv/pub/opensuse<br />
** pick an rsync module that you want to sync up from. They are described in [[openSUSE:Mirror infrastructure#rsync_modules|rsync modules]]. This example will use the "opensuse-hotstuff-160gb" module below.<br />
** add a cronjob to sync content. Here's an example for the most requested files, which we'll pull frequently (every 6 hours, after a small random offset):<br />
1 */6 * * * mirror sleep $(($RANDOM/16)); rsync -rlpt rsync.opensuse.org::opensuse-hotstuff-160gb /srv/pub/opensuse/ --delete-after --delete-excluded --max-delete=4000 --timeout=1800 -hi<br />
<br />
** you can try the command out, and pull the initial sync (and watch it), like this:<br />
*** su - mirror<br />
*** rsync -rlpt rsync.opensuse.org::opensuse-hotstuff-160gb /srv/pub/opensuse/ --delete-after --delete-excluded --max-delete=4000 --timeout=1800 -hi<br />
<br />
** beware that this `rsync` invocation won't result in atomic repo tree update and your consumers may see hit transitional errors (FIXME create improvement with [https://github.com/WayneD/rsync/blob/master/support/atomic-rsync atomic-rsync])<br />
<br />
** use locking for the cron job, because it could potentially be long-running, and new jobs could eventually stack up. The easiest way to run the cron job under a lock is to use the withlock wrapper script. Available via a package:<br />
*** zypper in withlock<br />
** now, change the cron job to run rsync under the wrapper script that takes care of locking:<br />
1 */6 * * * mirror sleep $(($RANDOM/16)); /usr/bin/withlock /home/mirror/LOCK-opensuse-hotstuff rsync -rlpt rsync.opensuse.org::opensuse-hotstuff-160gb /srv/pub/opensuse/ --delete-after --delete-excluded --max-delete=4000 --timeout=1800 -hi<br />
<br />
<br />
* give the '''openSUSE scanner''' access, by setting up an rsync server:<br />
** (rcrsyncd start; chkconfig -a rsyncd)<br />
** add the following to /etc/rsyncd.conf:<br />
[opensuse]<br />
path = /srv/pub/opensuse<br />
comment = rsync access for openSUSE scanner<br />
uid = nobody<br />
# if you want to limit access to the openSUSE mirror scanner:<br />
#hosts allow = 195.135.220.0/22<br />
<br />
<br />
* tell the '''redirector''' about it<br />
** write mail to admin at opensuse org, providing your details, as explained here: [[openSUSE:Mirror infrastructure#Register_Your_Mirror|register your mirror]]<br />
** take appropriate care that your webserver is up! The redirector will check it every few minutes... but until the next probe happens, it will continue to redirect clients to your hosts.<br />
<br />
<br />
* for extra points, you can considerably increase the service quality for users by configuring '''cache control headers''' for certain content. The idea is to mark the metadata files with cache control headers that indicate that they are not served from an intermediary (proxy) cache without checking for freshness before. This greatly reduces the risk that users see inconsistencies (one file being served stale from the cache, another one served fresh from the origin server). Add this to your Apache config (outside of a directory context):<br />
<br />
<LocationMatch "\.(xml|xml\.gz|xml\.asc)"><br />
Header set Cache-Control "must-revalidate"<br />
ExpiresActive On<br />
ExpiresDefault "now"<br />
</LocationMatch><br />
<br />
** mod_headers and mod_expires are required for this configuration. Enable them with the following commands:<br />
<br />
a2enmod headers<br />
a2enmod expires<br />
rcapache2 restart<br />
<br />
<br />
* '''monitoring''' and mail<br />
** there are many ways to configure and use a mail system. What I do, is:<br />
*** add myself to the root alias in /etc/aliases: "root: poeml@example.com"<br />
*** make sure that sending out mail works (you might need to configure a relay). Make sure YOUR mirror isn't accepting mail from externally, which would turn it into a spam hub<br />
*** make the sender more explicit: usermod -c "root at $(hostname)" root<br />
*** a highly useful package is sysstat. After installation, start it (rcsysstat start; chkconfig -a sysstat). The command "sar -A | less" will show various performance data for analysis.<br />
<br />
* '''apachestats''' - create visual server load graphs<br />
** a2enmod status<br />
** add 127.0.0.1 to /etc/apache2/mod_status.conf<br />
** set APACHE_EXTENDED_STATUS="on" in /etc/sysconfig/apache2<br />
** install the apachestats package http://software.opensuse.org/search?q=apachestats<br />
** graphs will be at http://your_mirror/apachestats/<br />
<br />
== Things to watch out for ==<br />
<br />
If the mirror syncs from our stage rsync server (stage.opensuse.org), a few points need to be observed:<br />
<br />
* use rsync --delay-updates --delete-delay to ensure consistent repositories<br />
* for large repos, --delay-updates is problematic, as it does not resume cleanly and our download-redirector does not see the files until rsync is done. Do one or more runs with --ignore-existing and without --delay-updates --delete-delay before to get most new files while keeping the repository consistent.<br />
* rsync needs to be run in a way that directory permissions are respected, and reproduced on the target machine. The above example takes care of that. If the permissions are not correctly reproduced, it interferes with the bitflip release process.<br />
* always run your mirror scripts under a user id different from the one your web server runs as. An identical user id would make all files readable for the web server, which interferes with the bitflip release process.<br />
* the user id running the mirror scripts also needs to be different from the user id that runs an rsync daemon<br />
* never run your web server as root. It also interferes with the bitflip release process.<br />
* if you happen to also run a public rsync server, make sure that your rsync daemon runs under a different user id than the script which pulls content from openSUSE. Otherwise you might be publicly serving content which is still "staged", i.e. not meant to be public.<br />
<br />
See also: [[openSUSE:Mirror infrastructure#Conditions_for_access_to_stage.opensuse.org|Conditions to access stage.opensuse.org]]<br />
<br />
== Protection of resources ==<br />
<br />
If your mirror is very popular, it may happen that it gets substantial traffic by download clients that open too many connections. There are download clients that open simultaneous connections to grab more of your bandwidth. That's not necessarily a wrong thing in itself, but if they open too many connections (20, or even more than 100), you will have to do something against it, in order to protect your server and also to protect the resources you provide, so they stay accessible for other legitimate users.<br />
<br />
You can see the number of simultaneous connections e.g. with this command:<br />
<br />
rcapache2 full-server-status | grep ' W ' | sort -k 11<br />
<br />
This command basically takes the output of the Apache server status and sorts it by IP address, making it easy to see how many connections originate from where.<br />
<br />
There is a number of Apache modules that can be used to achieve that. Don't be confused: what you *don't* want in this scenario is connection throttling, because it would make the clients stay even longer, and occupying server slots longer. There are two modules that I can recommend:<br />
<br />
=== mod_limitipconn===<br />
<br />
from http://dominia.org/djao/limitipconn.html. Packages here: http://software.opensuse.org/search?q=apache2-mod_limitipconn<br />
<br />
This module limits connections that are handled at the same time, per IP. Example configuration:<br />
<br />
<IfModule mod_limitipconn.c><br />
<Directory /srv/pub/opensuse><br />
MaxConnPerIP 20<br />
# exempting images from the connection limit is often a good<br />
# idea if your web page has lots of inline images, since these<br />
# pages often generate a flurry of concurrent image requests<br />
NoIPLimit image/*<br />
</Directory><br />
</IfModule><br />
<br />
The limit should not be too small, because simultaneous connections can also mean that corporate users access your site via a common proxy.<br />
<br />
=== mod_ip_count ===<br />
Packages are here: http://software.opensuse.org/search?q=apache2-mod_ip_count_modmemcache. Needs mod_memcache from http://software.opensuse.org/search?q=apache2-mod_memcache and a memcache daemon (http://software.opensuse.org/search?q=memcached).<br />
<br />
This module limits the rate at which new connections are accepted, per IP.<br />
<br />
<IfModule mod_memcache.c><br />
MemcacheServer 127.0.0.1:11211 min=0 smax=16 max=32 ttl=600<br />
</IfModule><br />
<IfModule mod_ip_count.c><br />
# Max number of requests before failing<br />
MemCacheMaxRequests 800<br />
# Time period in which the requests have to come (seconds)<br />
MemCacheMaxTime 120<br />
</IfModule><br />
<br />
The window we look at must be large enough so we don't block clients that download a large directory, like the openSUSE install client which downloads packages to install from 11.0/repo/i586/...<br />
<br />
The required memcache daemon is started with 'rcmemcached start' and configured to start permanently with 'chkconfig -a memcached'. <br />
<br />
==Registering your public mirror==<br />
<br />
If your mirror is public available, your can add it to our [http://www.mirrorbrain.org redirector database] and get it listed on the [http://mirrors.opensuse.org mirrors page] by following the [[openSUSE:Mirror_infrastructure#Registering_your_mirror|instructions on this wiki page]].<br />
<br />
==See also==<br />
* Transferred from old wiki [http://old-en.opensuse.org/Mirror_Setup_Howto Mirror Setup Howto]<br />
<br />
[[Category:Mirrors]]<br />
<br />
[[de:Einrichtung eines Spiegelservers]]<br />
[[zh:openSUSE:镜像指南]]</div>Bmwiedemannhttps://en.opensuse.org/index.php?title=Sponsors&diff=169639Sponsors2022-09-16T18:08:25Z<p>Bmwiedemann: Re-add IP Exchange</p>
<hr />
<div>With more than 50,000 registered users, the openSUSE project is a [http://www.suse.com/ SUSE]-sponsored community initiative that promotes the use and development of Linux everywhere. The [[Portal:Build Service|openSUSE Build Service]] has changed the way packages have been built. Thanks to the to the generous contribution of our sponsors. openSUSE and the openSUSE Build Service will continue to be the collaboration and package building platform for developers of all distributions.<br />
<br />
===Platinum sponsors of openSUSE===<br />
<br />
==== AMD ====<br />
<br />
[[File:53863A_AMD_E_Blk_RGB.png|thumb]]<br />
<br />
The combined forces of you, [http://www.amd.com/ AMD] and openSUSE are helping lead the Linux operating system community in 64-bit innovation.<br />
<br />
Consistent with AMD's theme of customer-centric innovation, openSUSE provides developers with a tool to compile, release, and publish their software for the broad user audience. AMD is a proud Platinum Sponsor of openSUSE.<br />
<br />
SUSE has consistently been among the first Linux distributions to support advanced features in AMD microprocessors such as AMD Direct Connect Architecture with NUMA memory architecture and HyperTransport technology, AMD Virtualization&trade; technology (AMD-V&trade;), and AMD PowerNow!&trade; technology.<br />
<br />
----<br />
<br />
===Gold Sponsors of openSUSE===<br />
<br />
==== IP Exchange ====<br />
<br />
[[ File:IP-Exchange-Logo.jpg |thumb]]<br />
<br />
[https://www.ip-exchange.de/ IP Exchange] : <br />
offers multi-certified data centers in Nuremberg and Munich, and ensures maximum availability of your IT through optimal physical and operational security, modern air conditioning and geo-redundancy.<br />
<br />
----<br />
<br />
===Silver Sponsors of openSUSE===<br />
<br />
==== B1 Systems GmbH ====<br />
<br />
[[File:B1-systems-1.jpg|thumb]]<br />
<br />
[http://www.b1-systems.de/ B1 Systems GmbH] is specialized in consulting and project work around Linux/Open Source and employs about 100 consultants, software developers, trainers and technical writers in this field. We act internationally in the topics of virtualization, clustering and performance optimization. <br />
<br />
We hand the knowledge we gain in those projects and feasibility studies on in trainings, workshops, books and presentations. We are active contributors to various Open Source projects and provide long-term support and maintenance for selected projects. <br />
<br />
B1 Systems GmbH is a proud sponsor of the openSUSE project. We are closely following the latest openSUSE development driven by the openSUSE community (e.g. the openSUSE Build Service etc.).<br />
<br />
----<br />
<br />
==== Core Backbone ====<br />
<br />
[[File:Logo_300dpi.png|thumb]] <br />
<br />
[http://www.core-backbone.com/ Core Backbone] is an established international carrier. Besides having a presence in different European countries, its network also reaches Singapore and different locations in the United States. With state-of-the-art data centres in Nuremberg, Germany, Core-Backbone guarantees secure, high-availability and high-performance connections to the Internet. Furthermore, Core-Backbone provides services, such as IP-Transit, Layer2 Circuits and premium DDoS protection, as well as CDN and dedicated servers in Nuremberg.<br />
<br />
----<br />
<br />
==== Heinlein Support ====<br />
<br />
[[File:Heinlein-support.png|thumb]]<br />
<br />
[http://www.heinlein-support.de Heinlein Support], based in Berlin, offers <br />
over 20 years of knowledge and experience in Linux servers and e-mail <br />
services. Our customers can benefit from the knowledge we impart during our <br />
Linux training courses at the Heinlein Academy or during in-house training <br />
sessions. They can also take advantage of our experience in personal <br />
consultation, our attention to detail when hosting customer data on our Linux <br />
servers, and our understanding of the Linux operating system when using our <br />
appliance and software products.<br />
<br />
In addition, Heinlein hosts the Mailserver Conference and the Secure Linux <br />
Administration Conference. We have worked with thousands of customers from <br />
reputable consumer goods companies, service and industry branches, as well as <br />
the public sector place for years and they continue to place their trust in <br />
us.<br />
---<br />
<br />
==== MARVELL ====<br />
[[File:Marvell.png|thumb]]<br />
Marvell first revolutionized the digital storage industry by moving information at speeds never thought possible. Today, that same breakthrough innovation remains at the heart of the company's storage, processing, networking, security and connectivity solutions. With leading intellectual property and deep system-level knowledge, Marvell's semiconductor solutions continue to transform the enterprise, cloud, automotive, industrial, and consumer markets. To learn more, visit: [https://www.marvell.com www.marvell.com].<br />
----<br />
[[File:Tuxedocomputerssmall.png|thumb]]<br />
==== TUXEDO Computers ====<br />
<br />
[https://www.tuxedocomputers.com TUXEDO Computers] is the provider of customized hardware solutions based<br />
on Linux: We offer our customers individual PCs and notebooks that are<br />
completely Linux-compatible. With our own development of drivers, addons<br />
and installation systems, we deliver the all-round carefree package for<br />
beginners as well as for professionals. All TUXEDO devices are available<br />
pre-installed with openSUSE Leap 15!<br />
Additionally there is the possibility of a fully automatic installation<br />
service, of course free of charge! Your own notebook or PC will be set<br />
up in the same way as TUXEDO does it in the factory.<br />
<br />
As a proud sponsor of the openSUSE community, TUXEDO Computers makes<br />
selected devices available for events. Interested people worldwide have<br />
the opportunity to experience openSUSE Linux on the latest hardware<br />
<br />
===Want to Become a Sponsor of openSUSE?===<br />
<br />
Sponsoring openSUSE.org is sponsoring a community project and emphasizing the sponsors commitment and support of open source and the open source community. [[Media:Sponsoring_for_opensuse.pdf|More information on how to become a sponsor.]] Sponsors will be asked to sign an [[Media:Equipment-Donation-Agreement.pdf|Equipment Donation Agreement]]. Email ddemaio (@) opensuse.org for more information.<br />
<br />
<br />
[[de:Sponsoren]]<br />
[[ru:Спонсоры]]</div>Bmwiedemann