Talk:Donation:Software

This document is supposed to cover the process of software ownership transfer to openSUSE.

Software needs to use licenses acceptable by the openSUSE project. Clarification on the reasons behind the transfer of ownership and commitment of maintenance effort.

All contributors shall agree to adhere to the openSUSE Code of Conduct https://en.opensuse.org/Code_of_Conduct

There will be an understanding that the openSUSE Board will act as the final point of call for any disputes that occur between people working on software that is a part of the openSUSE Project.

Software needs to be transferred to the openSUSE organization in GitHub, as openSUSE keeps track of its projects there. An acceptable alternative would be code-o-o.

Transfer of project to github.com/openSUSE requires approval of the openSUSE organization admin.

Readme.md or equivalent should mention the transfer of ownership and effective date.

One of Release managers should request a Bugzilla component creation under the openSUSE project(s), if necessary. The ultimate fallback would be component "Other".

To add software to our openSUSE distributions, the software needs to follow Factory first and openSUSE Factory development model. This also implies software should belong to one of the Development projects and needs to have a maintainer assigned, so Bugzilla triage is possible. This does not prohibit software that doesn't make sense to be included part of a Linux distribution from being a part of the openSUSE Project.