Skip to content
Permalink
master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

scr-docs/scr-bylaws.md

Go to file
 
 
Cannot retrieve contributors at this time
Summary Bylaws Mission Duties
22 lines (16 sloc) 1.5 KB
Raw Blame
Open in GitHub Desktop

Summary

This document describes the bylaws of the Sabayon Community Repositories Developers group, its mission, and duties.

Bylaws

The bylaws define the mission of the SCR, and SCRDs are required to follow these rules. They are intended to help the SCR thrive and keep the SCR reliable and useful to the community.

Mission

The SCR aims to provide additional packages to the community that cannot be supported by the main Sabayon developers. There are two classes of repository in the SCR:

  • The general “community” repository. This should contain low-risk packages; those that are available in Portage Overlays, and are beneficial to the majority of the Sabayon user community.
  • Special-purpose repositories, containing packages incompatible with the community repository, or other high-risk packages which might only be used by a small subset of the user community.

Duties

The Sabayon Community Repositories Developers (SCRDs) are expected to do the following:

  • Maintain, manage, and watch over the operation of the SCR.
  • Maintain popular packages (communicating with upstream and sending patches as needed).
  • Ensure that packages in SCR comply with the SCR guidelines.
  • Ensure that existing packages in the “for-gentoo” and “sabayon-distro” overlays that are more suited to the SCR (as described by the guidelines) are moved appropriately.
  • Prevent and respond to abuse of SCR infrastructure and services.
  • Vote in administrative matters relating to the SCR.