Minimum content requirements, roles and responsibilities and the basic mechanics of working in GitHub are set out in the Open Development Standard. The "Open Content Assessment Checklist" has been designed to help employees ensure there are no barriers to posting existing material on GitHub. If you are considering sharing existing code developed by or for the BC Government, you will need to complete this checklist and receive approval from your Deputy Minister (or delegate).
Please complete the checklist to determine if the existing content can be posted to GitHub
If all answers are "Yes" then posting to GitHub is possible.
Any "No" answers require additional investigation.
| Open Content Assessment Checklist | Yes | No |
|---|---|---|
| Privacy: Ministries may contact Knowledge and Information Services to assist in this assessment. | ||
| Is the content free of Personal Information that may directly identify an individual (e.g., name, phone number, photo, address, driver's license number or any similar identification number)? | Yes | |
| Copyright: Ministries must contact the Intellectual Property Program to assist in this assessment. Any legal review or legal advice will provided by Legal Services Branch. | ||
| Is the content created solely by B.C. government employees? | Yes | |
| Is the content fully owned by the B.C. government (i.e., have you ensured that it does not contain any third party content)?Note: collect copies of any contracts related to the content for review with IPP | Yes | |
| Can you confirm that there are no terms of use or any exclusive licenses that would prohibit the Province from licensing the content on GitHub?Note: collect information concerning any terms of use or licenses related to the content for review with IPP | Yes | |
| Do you have authority to licence the content?If "yes", indicate the source of the authority: [] Intellectual Property Program (attach approval email received from IPP) [] Treasury Board [] ministry legislative authority (identity Act and applicable section below): ________________________________________________________________ | Yes | |
| Legal, Contractual or Policy Constraints: | ||
| Is the public release and use of the Content permitted under law, contract or policy (e.g., have you ensured that there are no relevant legal, contractual or policy restrictions or limitations)? | Yes | |
| If there are legal, contractual or policy restrictions or limitations to the public release or use of theContent, have they been addressed? | ||
| Security Controls | ||
| Have you contacted your ministry information security officer (MISO) to ensure that all necessary security controls have been implemented? | Yes | |
| Has the material been labelled as 'Public' using the Information Security Classification Framework? | Yes |
The Open Content Assessment must be completed by ministries to ensure that there are no legal, policy, or contract restrictions to making the material publicly available. The attached form and checklist must be completed and approved by the deputy minister or delegate before posting the material on a social repository such as GitHub.
Contact Information
| Ministry, Division, Branch: | Ministry Energy and Mines, Electricity and Alternative Energy Division, Low Carbon Fuels Branch |
|---|---|
| Contact Name: | Michael Rensing |
| Contact Information: | [email protected] |
Description of the Material
| Name: | Transportation Fuels Reporting System |
|---|---|
| URL (if appropriate): | https://github.com/bcgov/tfrs |
| Description: | software enabling credit transfers and compliance reporting for transportation fuel suppliers |
| Format: | source code |
Open Content Assessment
| Is the checklist complete? | Yes / No |
|---|---|
| Has approval from IPP been received? (attach) | Yes / No |
| Are there any impediments to posting the content on a social repository? | Yes / No |
Approval
| Has the Deputy Minister (or delegate) approved the material for posting on a social repository? | Yes / No |
|---|
_______________________________ __________________________
Deputy Minister (or delegate) Date
Go back to the Contents List or continue reading Approaches to Collaborating/Contributing