commit: 7ecc327a201853f40f04dbb2227a3f34a84ea7ea Author: Göktürk Yüksek <gokturk <AT> binghamton <DOT> edu> AuthorDate: Mon Apr 4 04:34:28 2016 +0000 Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org> CommitDate: Tue Apr 19 10:39:53 2016 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=7ecc327a
ebuild-maintenance: s/herd/project/ per GLEP 67 #572144 Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=572144 Signed-off-by: Göktürk Yüksek <gokturk <AT> binghamton.edu> ebuild-maintenance/text.xml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml index 5b2abee..a299bf2 100644 --- a/ebuild-maintenance/text.xml +++ b/ebuild-maintenance/text.xml @@ -281,7 +281,18 @@ which is often more convenient. <section> <title>Touching other developers ebuilds</title> <body> -<p>Usually you don't just change other developers ebuilds without permission unless you know that developer does not mind or if you are part of the herd involved in maintenance (this information can typically be found in metadata.xml). Start with filing a bug or trying to catch them on IRC or via email. Sometimes you cannot reach them, or there is no response to your bug. It's a good idea to consult other developers on how to handle the situation, especially if it's a critical issue that needs to be handled ASAP. Otherwise a soft limit of 2 to 4 weeks depending on the severity of the bug is an acceptable time frame before you go ahead and fix it yourself.</p> +<p> +Usually you don't just change other developers ebuilds without +permission unless you know that developer does not mind or if you are +part of the project involved in maintenance (this information can +typically be found in metadata.xml). Start with filing a bug or trying +to catch them on IRC or via email. Sometimes you cannot reach them, or +there is no response to your bug. It's a good idea to consult other +developers on how to handle the situation, especially if it's a +critical issue that needs to be handled ASAP. Otherwise a soft limit +of 2 to 4 weeks depending on the severity of the bug is an acceptable +time frame before you go ahead and fix it yourself. +</p> <important> Common sense dictates to us that toolchain/base-system/core packages and eclasses or anything else which is delicate (e.g. glibc) or widely used (e.g. gtk+) should usually be left to those maintainers. If in doubt, don't touch it.</important> <p>
