public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/
Date: Sat,  9 May 2015 15:22:15 +0000 (UTC)	[thread overview]
Message-ID: <1430950009.960ae7a0f9ef60d3afb7e47ed27e4707ed284756.ulm@gentoo> (raw)

commit:     960ae7a0f9ef60d3afb7e47ed27e4707ed284756
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Sun May  3 18:07:39 2015 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed May  6 22:06:49 2015 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=960ae7a0

Merge ebuild etiquette policy from Developer Handbook.

This is taken from proj/en/devrel/handbook/hb-policy-etiquette.xml,
section "Tips", subsection "Ebuilds".

Permission to reuse the CC-BY-SA-1.0 work under CC-BY-SA-2.0
(or any later version) obtained from author plasmaroo per e-mail
on 2015-04-16.

 ebuild-maintenance/text.xml | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml
index 7325b66..ac68dcd 100644
--- a/ebuild-maintenance/text.xml
+++ b/ebuild-maintenance/text.xml
@@ -180,6 +180,15 @@ which is often more convenient.
 <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> 
 <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>
 


             reply	other threads:[~2015-05-09 15:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09 15:22 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-02-05 12:59 [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/ Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-04-19 10:40 Ulrich Müller
2016-04-23 19:26 Göktürk Yüksek
2016-04-24  0:47 Göktürk Yüksek
2016-05-01  3:49 Göktürk Yüksek
2016-05-22  8:35 Ulrich Müller
2016-08-18  9:01 Ulrich Müller
2016-11-20 20:46 Göktürk Yüksek
2017-01-22 20:45 Göktürk Yüksek
2017-07-29 20:48 Göktürk Yüksek
2017-09-25  4:40 Göktürk Yüksek
2017-09-25  4:40 Göktürk Yüksek
2020-01-23  8:40 Ulrich Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1430950009.960ae7a0f9ef60d3afb7e47ed27e4707ed284756.ulm@gentoo \
    --to=ulm@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox