Skip to content

Latest commit

 

History

History
56 lines (40 loc) · 4.78 KB

resources.md

File metadata and controls

56 lines (40 loc) · 4.78 KB

Resources

United Kingdom Government

(EN)Making source code open and reusable : UK Government Service Manual explaining that creation of new source code must be open and what are the requirements related to this practice.

(EN)Government Digital Services (GDS) Operations open source - Guidelines : This document describes a set of rules and principles for publishing Open Source code that GDS explicitly intends to support.

(EN)11 barriers to coding in the open and how to overcome them : This is a blog post from Khidr Suleman, GDS team member, that goes over barriers to coding in the open and how to overcome them.

(EN)Security considerations when coding in the open : Great Britain Government guidance document on security considerations for Open Source development.

(EN)Working with open standards : UK Government Service Manual explaining what Open Standards are and how to use them.

(EN)Why we use a ‘docs as code’ approach for technical documentation : Blog post from Jen Lambourne, GDS,explaining why they are documenting like their developers are coding. This could be interesting for policy making.

GitHub

InnerSource : Is the concept of Open Source but within a particular department, agency, or a group of similar agencies.  Denis Skinner mentioned there is difficulties in sharing and collaborating on internal projects.  Just last week at GitHub Constellation in London, we had Lloyd's bank talk about their InnerSource journey that has led to building a community of collaboration internally within the bank.

CapitalOne's Dev Exchange: CapitalOne is a great example of a company who has successfully utilized GitHub for both internal development and external (open) development.

How Github uses GitHub: I believe you were interested in this.  Late last year, we did a full series of webcasts on this topic. On our resources page, you find additional white papers, and videos.

Finally, Marc asked about secure development.  From the question section "Concerning Github, what security measures are in place to prevent mistakes? Two controls: no one can delete and there is a backup in cloud. Many controls like fork and branch to review the code before publishing it."

Additional Links

Upcoming events