devel:ALP ALP via a git repository This is a convert from SUSE:ALP project to a git repository. Package sources are currently in a single git repository here: https://gitea.opensuse.org/adrianSuSE/Alp The git repository can also be build using "pbuild" tool. If you are looking for installation media, check in https://build.opensuse.org/project/show/SUSE:ALP All development should be done in openSUSE Factory. https://download.opensuse.org/repositories/devel:/ALP/cross/ openSUSE:Factory:ARM openSUSE Factory ARM This is a project clone to build entire openSUSE:Factory for the ARM architecture. https://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/standard/ openSUSE:Factory:RISCV openSUSE Factory Port for RISC-V This is a project clone to build openSUSE:Factory for the RISC-V architecture. https://download.opensuse.org/repositories/openSUSE:/Factory:/RISCV/standard/ openSUSE:Factory The next openSUSE distribution Any user who wishes to have the newest packages that include, but are not limited to, the Linux kernel, SAMBA, git, desktops, office applications and many other packages, will want Tumbleweed. Tumbleweed appeals to Power Users, Software Developers and openSUSE Contributors. If you require the latest software stacks and Integrated Development Environment or need a stable platform closest to bleeding edge Linux, Tumbleweed is the best choice for you. Staging dashboard is located at: https://build.opensuse.org/staging_workflows/openSUSE:Factory List of known devel projects: https://build.opensuse.org/package/view_file/openSUSE:Factory:Staging/dashboard/devel_projects Have a look at http://en.opensuse.org/Portal:Factory for more details. https://download.opensuse.org/repositories/openSUSE:/Factory/ports/ httpcomponents-core Set of low level Java HTTP transport components for HTTP services HttpCore is a set of low level HTTP transport components that can be used to build custom client and server side HTTP services with a minimal footprint. HttpCore supports two I/O models: blocking I/O model based on the classic Java I/O and non-blocking, event driven I/O model based on Java NIO. The blocking I/O model may be more appropriate for data intensive, low latency scenarios, whereas the non-blocking model may be more appropriate for high latency scenarios where raw data throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner.