Merge pull request #11 from bcgov/TW20150506

Tw20150506

Author: Todd Wilson

BC-Gov-Org-HowTo/README.md

@@ -0,0 +1,21 @@
+**BCGov GitHub Organization "How To"**
+
+<a rel="Delivery" href="https://github.com/BCDevExchange/docs/blob/master/discussion/projectstates.md"><img alt="In production, but maybe in Alpha or Beta. Intended to persist and be supported." style="border-width:0" src="http://bcdevexchange.org/badge/3.svg" title="In production, but maybe in Alpha or Beta. Intended to persist and be supported." /></a> 
+
+**May, 2015**
+
+This document is "Beta" – however, all artifacts are available for use in their current state. Feedback and suggestions for improvement are welcome using the GitHub issues functionality.
+
+**Guidance, Templates and Check Lists**
+# Contents: #
+
+- Guidance
+	- [Joining the BCGov on GitHub](Joining-the-BCGov-on-GitHub.md )
+	- [Creating and Deleting Repos](Creating-And-Deleting-Repos.md)
+	- [Using Licenses](using-licenses.md)
+- Templates
+	- [Sample Contributing File](SAMPLE-CONTRIBUTING.md)
+	- [Sample ReadMe File](SAMPLE-README.md)
+- Check Lists
+	- Content Approval Check List
+

BC-Open-Source-Development-Employee-Guide/COI-Priv-IP.md

@@ -15,9 +15,13 @@ For example:
 
 Activity on GitHub is primarily concerned with sharing or generating source code and related documentation (such as specifications or descriptions related to the objectives of a project), which typically will not directly involve any information linked to individuals. However, you still need to ensure that any code or documentation you post does not contain:
 
-- Information or Records that are not accessible pursuant to the [_Freedom of Information and Protection of Privacy Act_](http://www.bclaws.ca/civix/document/id/complete/statreg/96165_00);
-- Sample data that includes personally identifying information;
-- Third-party rights the government is not authorized to license
-- - information subject to other intellectual property rights, including patents, trade-marks and official marks, and design rights
+- information or Records that are not accessible pursuant to the [_Freedom of Information and Protection of Privacy Act_](http://www.bclaws.ca/civix/document/id/complete/statreg/96165_00);
+- sample data that includes personally identifying information; 
+- third-party rights the government is not authorized to license;
+- information subject to other intellectual property rights, including patents, trade-marks and official marks, and design rights
 
-The [_Copyright Act _](http://laws-lois.justice.gc.ca/eng/acts/C-42/Index.html) [(Canada)](http://laws-lois.justice.gc.ca/eng/acts/C-42/Index.html) applies to government employees in the same manner that it applies to private citizens.  Unauthorized use of copyrighted material – including any unauthorized licensing of copyrighted materials owned by third parties – is an infringement of the intellectual property rights of the rights holder.
+The [Copyright Act (Canada)](http://laws-lois.justice.gc.ca/eng/acts/C-42/Index.html) applies to government employees in the same manner that it applies to private citizens.  Unauthorized use of copyrighted material – including any unauthorized licensing of copyrighted materials owned by third parties – is an infringement of the intellectual property rights of the rights holder.
+
+----------
+
+[Go back to the Contents List](README.md) or continue reading [Licenses](Licenses.md)

BC-Open-Source-Development-Employee-Guide/Collaborating-Contributing.md

@@ -48,3 +48,7 @@ There may be circumstances in which it is useful and appropriate for employees t
 
 Employees may also make contributions of non-BC government owned intellectual property rights outside their professional roles by using their personal email linked to their GitHub account.
 
+
+----------
+
+[Go back to the Contents List](README.md) or continue reading [Appropriate Use](appropriate-use.md)

BC-Open-Source-Development-Employee-Guide/Content-Approval-Checklist.md

@@ -70,3 +70,7 @@ The Open Content Assessment must be completed by ministries to ensure that there
 
 Deputy Minister (or delegate)                                        Date
 
+
+----------
+
+[Go back to the Contents List](README.md) or continue reading [Approaches to Collaborating/Contributing](Collaborating-Contributing.md)

BC-Open-Source-Development-Employee-Guide/Licenses.md

@@ -75,5 +75,7 @@ and the code for the cc 4.0 footer looks like this:
     Creative Commons Attribution 4.0 International License</a>.
 
 
+----------
 
+[Go back to the Contents List](README.md) or continue reading [Security](Security.md)
 

BC-Open-Source-Development-Employee-Guide/Principles.md

@@ -7,3 +7,8 @@ Participating in a collaborative environment to share and develop digital resour
 **Being Responsible** – includes acting with integrity and using your time and resources effectively and efficiently, and considering the impacts of your actions on others.
 
 **Being Compliant** – includes acting in accordance with the OCIO Information Systems Development Standard (section 2.1) or under an approved exception to the standard.
+
+
+----------
+
+[Go back to the Contents List](README.md) or continue reading [Browsing and Consuming Material in GitHub](browsing-consuming.md)

BC-Open-Source-Development-Employee-Guide/README.md

@@ -14,10 +14,9 @@ This document is "Beta" – however, all steps indicated as "required" are to be
 - [Approval Requirements](Content-Approval-Checklist.md)
 - [Approaches to Collaborating/Contributing](Collaborating-Contributing.md)
 - [Appropriate Use](appropriate-use.md)
-- Conflict of Interest
-- Privacy and Intellectual Property
+- [Conflict of Interest, Privacy and Intellectual Property](COI-Priv-IP.md)
 - [Licenses](Licenses.md)
-- Security
+- [Security](Security.md)
 
 
 # Why do we need this guide?

BC-Open-Source-Development-Employee-Guide/Security.md

@@ -0,0 +1,15 @@
+
+## Security
+
+**Under construction** – ensure any relevant material has been labelled as "Public" using the Information Security Classification Framework and that your ministry information security officer has been contacted to ensure all necessary security controls are in place.
+
+Please help, raise an issue or Fork and issue a Pull Request:-)
+
+
+
+----------
+
+[Go back to the Contents List](README.md)
+
+
+

BC-Open-Source-Development-Employee-Guide/appropriate-use.md

@@ -8,3 +8,7 @@
 - If your professional work includes use of non-BC Government repositories, you must read the licensing guidelines (in development) to ensure government does not take on undue risk.
 - Prior to publishing any content to GitHub, a suitable licence must be chosen from the list of approved licences and you must confirm your authority to license (see [Licenses](Licenses.md)).
 - Completing the [Open Content publishing checklist](Content-Approval-Checklist.md) is required for each new project prior to making any contributions. The checklist addresses privacy, intellectual property rights and information security. This helps ensure that the content posted to GitHub can be published under the associated licence.
+
+----------
+
+[Go back to the Contents List](README.md) or continue reading [Conflict of Interest, Privacy and Intellectual Property](COI-Priv-IP.md)

BC-Open-Source-Development-Employee-Guide/browsing-consuming.md

@@ -1,3 +1,7 @@
 # Browsing and Consuming Material in GitHub
 
 Once you've got an account set up, go ahead and start discovering the site. The [OCIO has established guidelines on the use of open source software](../ref-docs/96184_Open_Source_Guideline.pdf) that you should refer to, particularly if you're considering testing or adopting any OSS. Make sure you're familiar with existing [OCIO policy on information security](http://www.cio.gov.bc.ca/cio/informationsecurity/policy/informationsecuritypolicy.page?) before downloading or testing any code.
+
+----------
+
+[Go back to the Contents List](README.md) or continue reading [Approval Requirements](Content-Approval-Checklist.md)