From: "Paul Varner" <fuzzyray@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoolkit:gentoolkit commit in: /
Date: Sat, 2 Nov 2013 17:50:23 +0000 (UTC) [thread overview]
Message-ID: <1383414569.11eb5742928c8b2fcb9e8c74b84a46e8f66f0343.fuzzyray@gentoo> (raw)
commit: 11eb5742928c8b2fcb9e8c74b84a46e8f66f0343
Author: Paul Varner <fuzzyray <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 2 17:49:29 2013 +0000
Commit: Paul Varner <fuzzyray <AT> gentoo <DOT> org>
CommitDate: Sat Nov 2 17:49:29 2013 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=11eb5742
Add contributing section to README.dev
---
README.dev | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/README.dev b/README.dev
index 951b707..62a35fe 100644
--- a/README.dev
+++ b/README.dev
@@ -1,3 +1,20 @@
+Contributing:
+=============
+Gentoo Developers have full priviledges to the gentoolkit repository and
+any Gentoo developer can do work on the gentoolkit source.
+
+We only have several requirements. If you want to do a major change (i.e
+rewrite/refactor something), please talk to us before pushing any
+commits. If you break something, please fix it.
+
+If you want a new release of gentoolkit or gentoolkit-dev, please coordinate
+it with fuzzyray (gentoolkit) or idl0r (gentoolkit-dev).
+
+Any non Gentoo developers who wish to contribute, the best way to get
+started is by pulling a copy of the repository and submitting patches to
+bugzilla. Additionally, we can be found in the #gentoo-portage IRC
+channel.
+
Adding or modifying code:
=========================
- If you add new code, best practice is to write a test for it.
next reply other threads:[~2013-11-02 17:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 17:50 Paul Varner [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-12 7:16 [gentoo-commits] proj/gentoolkit:gentoolkit commit in: / Slawek Lis
2014-08-29 4:04 Brian Dolbec
2014-01-21 11:25 slis
2013-09-05 14:47 Paul Varner
2013-01-04 2:31 Paul Varner
2013-01-02 23:12 Paul Varner
2012-12-23 1:53 Brian Dolbec
2012-12-22 17:12 Brian Dolbec
2012-12-18 10:42 Paul Varner
2012-06-29 2:24 Brian Dolbec
2012-02-06 16:23 Paul Varner
2011-12-19 19:40 Paul Varner
2011-07-14 1:44 Brian Dolbec
2011-05-29 10:59 Christian Ruppert
2011-05-12 2:55 Paul Varner
2011-05-12 2:55 Paul Varner
2011-02-23 9:10 Brian Dolbec
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=1383414569.11eb5742928c8b2fcb9e8c74b84a46e8f66f0343.fuzzyray@gentoo \
--to=fuzzyray@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