commit: ddeb8e005a8216011b00b7cd4dcc47bb33150015 Author: Michał Górny <mgorny <AT> gentoo <DOT> org> AuthorDate: Mon Sep 9 07:17:46 2019 +0000 Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org> CommitDate: Wed Oct 16 18:49:09 2019 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=ddeb8e00
ebuild-maintenance/maintenance-tasks: "Touching other..." moved The "Touching other developers ebuilds" section has been effectively moved to "Package Maintainers". Remove the duplicate. Closes: https://github.com/gentoo/devmanual.gentoo.org/pull/104 Acked-by: Michael Orlitzky <mjo <AT> gentoo.org> Signed-off-by: Michał Górny <mgorny <AT> gentoo.org> Signed-off-by: Göktürk Yüksek <gokturk <AT> gentoo.org> ebuild-maintenance/maintenance-tasks/text.xml | 33 --------------------------- 1 file changed, 33 deletions(-) diff --git a/ebuild-maintenance/maintenance-tasks/text.xml b/ebuild-maintenance/maintenance-tasks/text.xml index 06634b8..7e73937 100644 --- a/ebuild-maintenance/maintenance-tasks/text.xml +++ b/ebuild-maintenance/maintenance-tasks/text.xml @@ -136,39 +136,6 @@ which is often more convenient. </body> </section> -<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 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> -Respect developers' coding preferences. Unnecessarily changing the -syntax of an ebuild can cause complications for others. Syntax changes -should only be done if there is a real benefit, such as faster -compilation, improved information for the end user, or compliance with -Gentoo policies. -</p> - -</body> -</section> - <section> <title>Stabilizing ebuilds</title> <body>
