[PATCH 3/6] Updated Developer Guide - Accounts

Shawn Wells shawn at redhat.com
Mon May 12 06:22:56 UTC 2014

Updated "accounts" section of Developer guide, highlighting where to signup for core accounts needed when commiting to SSG

Signed-off-by: Shawn Wells <shawn at redhat.com>
 docs/Developer_Guide/en-US/ch001-Accounts.xml |   37 +++++++++++++++++++++++++
 1 files changed, 37 insertions(+), 0 deletions(-)
 create mode 100644 docs/Developer_Guide/en-US/ch001-Accounts.xml

diff --git a/docs/Developer_Guide/en-US/ch001-Accounts.xml b/docs/Developer_Guide/en-US/ch001-Accounts.xml
new file mode 100644
index 0000000..f34220c
--- /dev/null
+++ b/docs/Developer_Guide/en-US/ch001-Accounts.xml
@@ -0,0 +1,37 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent">
+<chapter id="chap-Developer_Guide-Accounts">
+	<title>Establishing Accounts</title>
+	<para> </para>
+	<section id="sect-Developer_Guide-Accounts-maillist">
+		<title>Mailing List</title>
+		<para>Join the mailing list at <ulink
+				url="https://fedorahosted.org/mailman/listinfo/scap-security-guide"
+				>https://fedorahosted.org/mailman/listinfo/scap-security-guide</ulink>. </para>
+	</section>
+	<section id="sect-Developer_Guide-Accounts-fedorahosted">
+		<title>GitHub</title>
+		<para>In May 2014 the SCAP Security Guide project moved the underlying source repository from
+			FedoraHosted to GitHub.</para>
+		<para>To register for a free GitHub account, visit <ulink url="https://github.com/join"
+				>https://github.com/join</ulink>. Registering for a GitHub account should not be
+			troublesome.</para>
+	</section>
+	<section id="sect-Developer_Guide-Accounts-ssgproject">
+		<title>OpenSCAP "Content Developers"</title>
+		<para>If you envision committing code, and needing direct push access to the repository (vs
+			GitHub's pull request system), send a quick hello to the mailing list introducing
+			yourself. The community may already know you, but this is an opportunity to reintroduce
+			yourself and update the community on areas you'd like to contribute to. This need not be
+			formal; though don't forget to include your GitHub account name! Pending approval from
+			an existing maintainer, you will be added to the OpenSCAP Content Developers group on
+			GitHub: <ulink url="https://github.com/orgs/OpenSCAP/teams/content-authors"
+				>https://github.com/orgs/OpenSCAP/teams/content-authors</ulink>.</para>
+	</section>

More information about the scap-security-guide mailing list