This project contains the application containers for openSUSE MicroOS

Ignition is an utility to manipulate disks and configuration files during the initramfs.
This includes partitioning disks, formatting partitions, writing files (regular files,
systemd units, etc.), and creating users. On first boot, Ignition reads its configuration
from a source of truth (remote URL, network metadata service, hypervisor
bridge, etc.) and applies the configuration.

This project contains all built packages for Yuga Linux. They can be downloaded from the repositories. There are three branches:
Stable
Testing
Unstable

If you don't know what each of those mean, please download the images from the Stable repository

okurz: I am not yet sure which repo(s) would be good for this project. openSUSE_Factory corresponds to where we want to submit to, openSUSE_Tumbleweed is what we test against in https://openqa.opensuse.org/tests/latest?distri=openqa&test=openqa_install%2Bpublish

Quite some packages in openSUSE:Factory are not easy split into topic parts, so
we have this "the rest" project, that contains packages that do not really fit
anywhere else.

This project is different to many other devel projects in that the maintainers
are defined by package and not by project.

devel:openSUSE:Apps is the development space for leaf applications of openSUSE:Factory (Tumbleweed) and potential backport projects openSUSE:Apps

This project is STRICTLY for Application packages targeted at openSUSE:Tumbleweed and potentially at openSUSE:Apps - a collection project to provide up-to-date application versions to released products.

Devel project for rpmlint to avoid rpmlint breaking other packages

Devel project for rpmlint to avoid rpmlint breaking other packages

This projects contains the different HA cluster resource and fence agents, mostly oriented for SAP workloads

All kind of developments tools. Esp. profiling and debugging tools.

Tools for building software

Jenkins monitors executions of repeated jobs, such as building a software
project or jobs run by cron. Among those things, current Jenkins focuses
on the following two jobs:

1. Building/testing software projects continuously, just like
CruiseControl or DamageControl. In a nutshell, Jenkins provides an
easy-to-use so-called continuous integration system, making it
easier for developers to integrate changes to the project, and
making it easier for users to obtain a fresh build. The automated,
continuous build increases the productivity.
2. Monitoring executions of externally-run jobs, such as cron jobs and
procmail jobs, even those that are run on a remote machine. For
example, with cron, all you receive is regular e-mails that capture
the output, and it is up to you to look at them diligently and notice
when it broke. Jenkins keeps those outputs and makes it easy for you
to notice when something is wrong.

Site configuration for autoconf based configure scripts provides smart defaults for paths that are not specified.

Various compilers

LTTng (Linux Trace Toolkit Next Generation) is a tracer for Linux.
It is a kernel module accompanied by a toolchain (ltt-control) to control the tracing, as well as a trace viewing and analysis application (LTTV).
LTTng includes a set of kernel instrumentation points useful for debugging a wide range of bugs, that are otherwise extremely challenging.
These include, for example, performance problems on parallel systems and on real-time systems.
LTTng is designed for minimal performance impact and has a near zero impact when not tracing. LTTng has at least basic support for all Linux architectures.

to quote wikipedia:
Software Configuration Management (SCM) is part of configuration management (CM). Roger Pressman (in his book) Software Engineering: A Practitioner's Approach, says that software configuration management (SCM) is a "set of activities designed to control change by identifying the work products that are likely to change, establishing relationships among them, defining mechanisms for managing different versions of these work products, controlling the changes imposed, and auditing and reporting on the changes made." In other words, SCM is a methodology to control and manage a software development project.

SCM concerns itself with answering the question: somebody did something, how can one reproduce it? Often the problem involves not reproducing "it" identically, but with controlled, incremental changes. Answering the question will thus become a matter of comparing different results and of analysing their differences. Traditional CM typically focused on controlled creation of relatively simple products. Nowadays, implementers of SCM face the challenge of dealing with relatively minor increments under their own control, in the context of the complex system being developed.

Subversion and related tools

Collection of tools for static source code analysis.

fop for 12.3 needs xml-commons-jaxp-1.3-apis from e.g. Documentation:Tools

Tools of the SUSE Documentation Team and documentation-related tools, used for building the contents in project Documentation.