Gentoo Archives: gentoo-commits

From: Paul Varner <fuzzyray@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] proj/gentoolkit:gentoolkit commit in: /
Date: Sat, 02 Nov 2013 17:50:35
Message-Id: 1383414569.11eb5742928c8b2fcb9e8c74b84a46e8f66f0343.fuzzyray@gentoo
1 commit: 11eb5742928c8b2fcb9e8c74b84a46e8f66f0343
2 Author: Paul Varner <fuzzyray <AT> gentoo <DOT> org>
3 AuthorDate: Sat Nov 2 17:49:29 2013 +0000
4 Commit: Paul Varner <fuzzyray <AT> gentoo <DOT> org>
5 CommitDate: Sat Nov 2 17:49:29 2013 +0000
6 URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=11eb5742
7
8 Add contributing section to README.dev
9
10 ---
11 README.dev | 17 +++++++++++++++++
12 1 file changed, 17 insertions(+)
13
14 diff --git a/README.dev b/README.dev
15 index 951b707..62a35fe 100644
16 --- a/README.dev
17 +++ b/README.dev
18 @@ -1,3 +1,20 @@
19 +Contributing:
20 +=============
21 +Gentoo Developers have full priviledges to the gentoolkit repository and
22 +any Gentoo developer can do work on the gentoolkit source.
23 +
24 +We only have several requirements. If you want to do a major change (i.e
25 +rewrite/refactor something), please talk to us before pushing any
26 +commits. If you break something, please fix it.
27 +
28 +If you want a new release of gentoolkit or gentoolkit-dev, please coordinate
29 +it with fuzzyray (gentoolkit) or idl0r (gentoolkit-dev).
30 +
31 +Any non Gentoo developers who wish to contribute, the best way to get
32 +started is by pulling a copy of the repository and submitting patches to
33 +bugzilla. Additionally, we can be found in the #gentoo-portage IRC
34 +channel.
35 +
36 Adding or modifying code:
37 =========================
38 - If you add new code, best practice is to write a test for it.