[gentoo-commits] proj/printer-drivers:master commit in: Documentation/

[gentoo-commits] proj/printer-drivers:master commit in: Documentation/

[Andreas Hüttel]

commit:     a88d53ffb4ddeccd82d99e97706a2abfa09a025c
Author:     Andreas K. Huettel (dilfridge) <mail <AT> akhuettel <DOT> de>
AuthorDate: Sat Apr  7 16:55:41 2012 +0000
Commit:     Andreas Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Sat Apr  7 16:55:41 2012 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/printer-drivers.git;a=commit;h=a88d53ff

[Documentation] added bug text snippet

---
 Documentation/bug-snippet.txt |   35 +++++++++++++++++++++++++++++++++++
 1 files changed, 35 insertions(+), 0 deletions(-)

diff --git a/Documentation/bug-snippet.txt b/Documentation/bug-snippet.txt
new file mode 100644
index 0000000..74f6d72
--- /dev/null
+++ b/Documentation/bug-snippet.txt
@@ -0,0 +1,35 @@
+Are you interested in maintaning this driver directly yourself in the new 
+printer-drivers overlay [1]?
+
+If yes, just send me via personal e-mail at dilfridge@gentoo.org
+a public ssh key [2], so we can give you git push access to the overlay.
+If you have a gnupg key, you should sign that e-mail [3].
+
+Just a few rules:
+* Initially, the ebuilds should work for you, and not break
+  anything else.
+* You enter yourself as maintainer in metadata.xml (together with
+  the printing herd), and are then automatically cc'ed in bug reports 
+  on bugzilla.
+* We will guide you towards improving the ebuilds over the next 
+  months so they follow the rules and qa guidelines of the Gentoo 
+  main portage tree. In particular this means also using a recent
+  EAPI (3 or perferably 4), and fixing repoman warnings [4].
+  Don't worry, we'll help you with that.
+* I hope this is never going to happen, but... ebuilds that "work but 
+  go against the guidelines" and do not see any improvement will be 
+  removed again one year after initial addition.
+
+There are many ways to get help.
+* You can directly ask me by personal e-mail (my time is limited, 
+  but I'll try), 
+* you can ask on freenode, channel #gentoo-dev-help,
+* you can read the documentation (ebuild howto [5], devmanual [6]), 
+* ...
+
+[1] http://git.overlays.gentoo.org/gitweb/?p=proj/printer-drivers.git;a=summary
+[2] http://www.gentoo.org/doc/en/articles/openssh-key-management-p1.xml
+[3] http://www.gentoo.org/doc/en/gnupg-user.xml
+[4] http://dev.gentoo.org/~zmedico/portage/doc/man/repoman.1.html
+[5] http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2
+[6] http://devmanual.gentoo.org/

[gentoo-commits] proj/printer-drivers:master commit in: Documentation/

[Andreas Hüttel]

commit:     cf7ba3613e1499d69832b4e12b9cd9f08519b598
Author:     Andreas K. Huettel (dilfridge) <mail <AT> akhuettel <DOT> de>
AuthorDate: Sat Apr  7 18:37:56 2012 +0000
Commit:     Andreas Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Sat Apr  7 18:37:56 2012 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/printer-drivers.git;a=commit;h=cf7ba361

[Documentation] more explicit bug text instructions

---
 Documentation/bug-snippet.txt |    8 ++++++--
 1 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/Documentation/bug-snippet.txt b/Documentation/bug-snippet.txt
index 74f6d72..d0fed49 100644
--- a/Documentation/bug-snippet.txt
+++ b/Documentation/bug-snippet.txt
@@ -1,8 +1,12 @@
 Are you interested in maintaning this driver directly yourself in the new 
 printer-drivers overlay [1]?
 
-If yes, just send me via personal e-mail at dilfridge@gentoo.org
-a public ssh key [2], so we can give you git push access to the overlay.
+If yes, just send me via personal e-mail at dilfridge@gentoo.org the
+following data, so we can give you git push access to the overlay:
+* the user name that you'd like to have
+* your public ssh key [2], so we can give you git push access to the overlay
+* your e-mail address
+* and your full name
 If you have a gnupg key, you should sign that e-mail [3].
 
 Just a few rules: