From: hasufell <hasufell@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds
Date: Tue, 04 Dec 2012 19:17:15 +0100 [thread overview]
Message-ID: <50BE3E2B.4030001@gentoo.org> (raw)
In-Reply-To: <50BE36D8.1090909@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
the patch has been modified to reflect Zero_Chaos suggestions:
- tell where to look for herd or maintainer notes (such as "touch at
will"): metadata.xml
- explicitly say to contact other devs if unsure how to handle a
situation, especially if it's a critical one
[-- Attachment #2: ebuild-committing-guide.patch --]
[-- Type: text/x-patch, Size: 3700 bytes --]
commit e6ebf193852f92aa1dfec162f1bcdc34e933eda1
Author: hasufell <julian.ospald@googlemail.com>
Date: Sat Dec 1 00:04:51 2012 +0100
add ebuild comitting guide section
diff --git a/ebuild-committing-guide/cvs-tutorial/text.xml b/ebuild-committing-guide/cvs-tutorial/text.xml
new file mode 100644
index 0000000..a2bd612
--- /dev/null
+++ b/ebuild-committing-guide/cvs-tutorial/text.xml
@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<guide self="ebuild-committing-guide/cvs-tutorial/">
+<chapter>
+<title>CVS Tutorial</title>
+
+<body>
+<p>
+TODO: write something here.
+</p>
+</body>
+
+</chapter>
+
+</guide>
diff --git a/ebuild-committing-guide/ebuild-policy/text.xml b/ebuild-committing-guide/ebuild-policy/text.xml
new file mode 100644
index 0000000..44ce9aa
--- /dev/null
+++ b/ebuild-committing-guide/ebuild-policy/text.xml
@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<guide self="ebuild-committing-guide/ebuild-policy/">
+<chapter>
+<title>Ebuild policy</title>
+
+<body>
+<p>
+TODO: write something here.
+</p>
+</body>
+
+</chapter>
+
+</guide>
diff --git a/ebuild-committing-guide/text.xml b/ebuild-committing-guide/text.xml
new file mode 100644
index 0000000..db8e982
--- /dev/null
+++ b/ebuild-committing-guide/text.xml
@@ -0,0 +1,23 @@
+<?xml version="1.0"?>
+<guide self="ebuild-committing-guide/">
+<chapter>
+<title>Ebuild Committing Guide</title>
+
+<body>
+<p>
+This section describes how to commit an ebuild. It covers the basics of handling CVS commits and desribes some ebuild and tree policies.
+</p>
+</body>
+
+<section>
+<title>Contents</title>
+<body>
+<contentsTree maxdepth="1"/>
+</body>
+</section>
+</chapter>
+
+<include href="ebuild-policy/"/>
+<include href="tree-policy/"/>
+<include href="cvs-tutorial/"/>
+</guide>
diff --git a/ebuild-committing-guide/tree-policy/text.xml b/ebuild-committing-guide/tree-policy/text.xml
new file mode 100644
index 0000000..1c56a00
--- /dev/null
+++ b/ebuild-committing-guide/tree-policy/text.xml
@@ -0,0 +1,23 @@
+<?xml version="1.0"?>
+<guide self="ebuild-committing-guide/tree-policy/">
+<chapter>
+<title>Tree and Etiquette policy</title>
+
+<body>
+<p>
+This section outlines the etiquette policy for Gentoo developers and describes common sense when dealing with problems in the tree.
+</p>
+<section>
+<title>Changing/Fixing other developers ebuilds</title>
+<body>
+<p>Usually you don't just change other developers ebuilds without a word unless you know he does not mind or if you are part of the herd involved in maintenance (those information can be found in metadata.xml). Start with filing a bug or try 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 one and needs to be handled ASAP. Otherwise a soft limit of 2 to 4 weeks depending on the severity of the bug is an acceptable timeframe 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>
+</body>
+</section>
+
+
+</body>
+
+</chapter>
+
+</guide>
diff --git a/text.xml b/text.xml
index 88016b0..137a99f 100644
--- a/text.xml
+++ b/text.xml
@@ -50,6 +50,7 @@ section lists specific contributions to this manual.
<include href="quickstart/"/>
<include href="general-concepts/"/>
<include href="ebuild-writing/"/>
+<include href="ebuild-committing-guide/"/>
<include href="eclass-writing/"/>
<include href="profiles/"/>
<include href="keywording/"/>
prev parent reply other threads:[~2012-12-04 18:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 15:21 [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds hasufell
2012-12-02 15:38 ` Rich Freeman
2012-12-02 19:30 ` Markos Chandras
2012-12-04 1:18 ` Ben de Groot
2012-12-04 7:43 ` Ian Whyman
2012-12-04 9:19 ` Markos Chandras
2012-12-04 15:42 ` Alec Warner
2012-12-04 18:54 ` Markos Chandras
2012-12-06 10:53 ` Ben de Groot
2012-12-04 8:10 ` Rick "Zero_Chaos" Farina
2012-12-04 9:23 ` Markos Chandras
2012-12-04 16:01 ` Rick "Zero_Chaos" Farina
2012-12-04 17:06 ` Proxy maintainers in metadata.xml (was Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds) Diego Elio Pettenò
2012-12-04 17:28 ` Rick "Zero_Chaos" Farina
2012-12-04 18:35 ` Sergey Popov
2012-12-04 18:48 ` Diego Elio Pettenò
2012-12-04 18:51 ` Markos Chandras
2012-12-06 11:02 ` Ben de Groot
2012-12-06 13:28 ` Markos Chandras
2012-12-06 15:27 ` Peter Stuge
2012-12-06 15:54 ` Ian Stakenvicius
2012-12-06 16:04 ` Peter Stuge
2012-12-06 19:07 ` Markos Chandras
2012-12-08 17:48 ` Jeroen Roovers
2012-12-04 17:01 ` [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds hasufell
2012-12-04 17:17 ` Rick "Zero_Chaos" Farina
2012-12-04 17:32 ` hasufell
2012-12-04 17:46 ` Rick "Zero_Chaos" Farina
2012-12-04 18:17 ` hasufell [this message]
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=50BE3E2B.4030001@gentoo.org \
--to=hasufell@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