BIND 10 trac3109, updated. 016bfae00460b4f88adbfd07ed26759eb294ef10 [3109] ChangeLog updated

[BIND 10 source code commits]

The branch, trac3109 has been updated
       via  016bfae00460b4f88adbfd07ed26759eb294ef10 (commit)
       via  ae4ce59aabd5281822630668956425fa6167eca8 (commit)
      from  342c56224c215ca1cb245df0875878e4f8fad0e6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 016bfae00460b4f88adbfd07ed26759eb294ef10
Author: Tomek Mrugalski <tomasz at isc.org>
Date:   Thu Dec 5 19:10:43 2013 +0100

    [3109] ChangeLog updated

commit ae4ce59aabd5281822630668956425fa6167eca8
Author: Tomek Mrugalski <tomasz at isc.org>
Date:   Thu Dec 5 19:10:20 2013 +0100

    [3109] Added proposed chages in review:
    - eased language
    - added link to system specific notes
    - fixed coding guidelines link to look better
    - added link to our build farm

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                |    4 ++++
 doc/devel/contribute.dox |   11 +++++++----
 2 files changed, 11 insertions(+), 4 deletions(-)

-----------------------------------------------------------------------
diff --git a/ChangeLog b/ChangeLog
index ed17181..268e0aa 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+6XX.	[doc]		tomek
+	BIND10 Contributor's Guide added.
+	(Trac #3109, git ABCD)
+
 663.	[func]		marcin
 	b10-dhcp6: Server processes the DHCPv6 Client FQDN Option
 	sent by a client and generates the response. The DHCPv6 Client
diff --git a/doc/devel/contribute.dox b/doc/devel/contribute.dox
index af5142a..9103bed 100644
--- a/doc/devel/contribute.dox
+++ b/doc/devel/contribute.dox
@@ -18,7 +18,7 @@
 
 So you found a bug in BIND10 or plan to develop an extension and want to
 send a patch? Great! This page will explain how to contribute your
-changes and not get disappointed in the process.
+changes smoothly.
 
 @section contributorGuideWritePatch Writing a patch
 
@@ -51,10 +51,13 @@ is portable software. Besides Linux, it is compiled and used on
 relatively uncommon systems like OpenBSD and Solaris 11. Will your code
 compile and work there? What about endianess? It is likely that you used
 a regular x86 architecture machine to write your patch, but the software
-is expected to run on many other architectures.
+is expected to run on many other architectures. You may take a look at
+system specific build notes (http://bind10.isc.org/wiki/SystemSpecificNotes).
+For a complete list of systems we build on, you may take a look at the
+following build farm report: http://git.bind10.isc.org/~tester/builder/builder-new.html .
 
-Does your patch conform to BIND10
-<http://bind10.isc.org/wiki/CodingGuidelines>? You still can submit a
+Does your patch conform to BIND10 coding guidelines
+(http://bind10.isc.org/wiki/CodingGuidelines)? You still can submit a
 patch that does not adhere to it, but that will decrease its chances of
 being accepted. If the deviations are minor, the BIND10 engineer who
 does the review will likely fix the issues. However, if there are lots