From Gentoo Wiki
Jump to:navigation Jump to:search
Description Ebuild repository entirely maintained by Gentoo users
Project email
IRC channel #gentoo-guru (webchat)
No lead election date set
(and inherited member(s))
Parent Project Gentoo
Project listing

The goal of the GURU project is to create an official repository of new Gentoo packages that are maintained collaboratively by Gentoo users. It follows the tradition of Sunrise project but aims to improve its maintainability by reducing the involvement of Gentoo developers and letting experienced contributors take care of reviewing work of others.

GURU project logo


Please note that the GURU project is maintained and reviewed entirely by Gentoo users. It is only subject to minimal supervision from individual Gentoo developers, and is not supported by projects such as Gentoo Security. While our Trusted Contributors do their best to keep GURU safe, it is possible for it to contain vulnerable, badly broken or even malicious software. You are using it on your own responsibility.

The regulations

Every user willing to contribute to the GURU project needs to explicitly agree with the following regulations.

  1. The purpose of GURU project is to maintain a repository that can be reasonably used by Gentoo users. All contributors are responsible for ensuring that the repository is safe to use and free of malicious or severely buggy software.
  2. GURU is an official Gentoo project, and is therefore bound by the official Gentoo policies. In particular, the Copyright Policy (GLEP 76) is binding to all committers.
  3. While following Gentoo ebuild policies and quality standards is recommended, it will not be strictly enforced. More experienced users are encouraged to improve the quality of ebuilds in GURU, and less experienced users are encouraged to learn from those corrections.
  4. Packages in GURU are to have ~arch keywords. Stable keywords must not be used.
  5. Packages in GURU are community maintained. While users are encouraged to list themselves as maintainers and take explicit responsibility for their packages, it is acceptable for others to commit improvements to those packages and to commit packages without an explicit maintainer.
  6. At the same time, users are asked to maintain respectful and professional behavior, and to attempt to maintain a good quality of GURU overall.
  7. Users that list themselves as maintainers must use an e-mail address known to in metadata.xml and keep it up to date in case it changes.
  8. Contributors should refrain from adding packages that they cannot reasonably maintain, due to, for example, the complexity, scope, or quantity of the added work. Adding rough drafts of ebuilds with the hope that someone else will fix them up and no intent of doing so yourself is not acceptable. Adding packages in bulk should be avoided.
  9. Packages in GURU must solve a problem that cannot be reasonably achieved using simpler methods. In other words, there should be some rationale for an ebuild to be an ebuild instead of, for example, a wget script or config snippet.
  10. With very few exceptions, such as virtuals or meta-packages, new packages in GURU should have an upstream (meaning SRC_URI should usually be populated). Exceptions must be justified.
  11. The primary purpose of GURU is to maintain packages not present in the Gentoo repository. Forking (overriding) actively maintained Gentoo packages into GURU is prohibited. If the package is moved to Gentoo, it should be removed from GURU.

User roles and responsibilities

GURU notes three classes of users:

  • Regular contributors that are permitted to commit to the development (dev) branch.
  • Trusted contributors that gain additional privilege of merging commits into the reviewed (master) branch.
  • Gentoo developers who are responsible for handling new user acceptance, enforcement of regulations and taking care of emergencies.

New contributors request access via filing a bug in GURU product and stating their agreement to the regulations. A Gentoo developer grants access to the repository.

Regular contributors perform their work on the development branch. This work is afterwards reviewed by trusted contributors and/or Gentoo developers. They either inform the authors of necessary changes or fix the ebuilds themselves. Whenever the final status is good enough, they merge the changes to the reviewed (master) branch.

The trusted contributor status is granted by Gentoo developers based on previous good work done in GURU. Trusted contributors are generally expected to be responsible for ensuring that the repository is free of malicious or otherwise dangerous code, and for preventing it from reaching the end users via the reviewed branch.

Gentoo developers can join the project at their leisure. Their main role is taking care of technical requests from users, granting trusted contributor privileges and preventing abuse.


While project is maintained and reviewed entirely by Gentoo users, Tinderbox project builds GURU packages on a regular basis to find common mistakes.

Conflict resolution

If an unresolvable disagreement arises between (trusted) contributors or between contributors and users, follow the steps below:

  1. Involve (the other) Trusted Contributors via e-mail to the mailing list or If this does not lead to an acceptable resolution then,
  2. Hold a formal vote on among the Trusted Contributors on how the conflict should be resolved. The issue may be escalated to the Gentoo Developers involved in GURU if this is the conclusion of the vote, or if the involved parties wish to appeal the conclusion of the vote.
  3. If the issue still cannot be resolved via discussion with the Gentoo Developers involved in GURU, then they too will hold a vote to decide how the matter should be resolved,

In this process, the following conditions apply:

  1. A decision to revoke access to the dev or master branch, whether temporarily or permanent, must involve the Gentoo Developers that are a member of the GURU project.
  2. A decision to permanently revoke access to the dev or master branch should be preceded by a formal warning, a preceding temporary suspension of access counts as a warning. Only in extreme cases, such as malevolent behaviour, may this warning be skipped.
  3. To keep track of them, formal warnings and suspensions are noted in the contributor's access request bug.
  4. A Trusted Contributor who is the subject of a vote, may not participate in this vote.
  5. Policies and guidelines of the Community Relations project with regards to developer-user conflict apply here as well.


Technical resources:

Commit feeds:

GURU guides:

Useful development documentation: