# GitHub for Government

Plain-language guidance for using GitHub in government and regulated environments.

This repository explains **what GitHub is, how it is commonly used, and how government teams can engage with it safely and confidently** — without requiring software development experience.

## Related Resources

- **Public Sector Security & FedRAMP Guidance**  
  https://github.com/turtini/public-sector-security

  Plain-language explanations of FedRAMP, authorization boundaries, and shared responsibility models commonly encountered in federal environments.

---

## Who this is for

This repository is for:

- Government employees and contractors
- Program managers, policy staff, and analysts
- Security, compliance, and audit stakeholders
- Technical leaders explaining GitHub to non-technical teams
- Anyone encountering GitHub as part of modern government work

You do **not** need to be a developer to use or understand this material.

---

## Who this is *not* for

This repository is **not**:

- A software development tutorial
- A guide to programming or coding
- A replacement for formal security or compliance policy
- A tool that requires installing software or using the command line

If you are looking to learn how to write code, there are many excellent resources elsewhere.  
This repository focuses on **understanding and participation**, not implementation.

---

## What GitHub is (in plain language)

GitHub is a platform for **sharing, reviewing, and tracking changes to documents and technical artifacts over time**.

At its core, GitHub provides:

- A shared place to store documents and files
- A complete history of who changed what, and when
- Structured ways to review and discuss changes
- Transparency that supports accountability and auditability

While GitHub is often associated with software development, many government teams use it primarily as **documentation and collaboration infrastructure**.

---

## What GitHub is *not*

GitHub is **not**:

- A production system
- A live operational environment
- A place where you can accidentally “break” running systems
- A platform where reading content causes changes

Reading files on GitHub is safe.  
Commenting and discussion are controlled and reversible.  
Changes require deliberate action and review.

---

## How government teams typically use GitHub

In government and regulated environments, GitHub is commonly used for:

- Public documentation and guidance
- Policy drafts and reference materials
- Technical standards and implementation guides
- Governance frameworks and decision records
- Collaboration across agencies or vendors
- Transparency into how decisions evolve over time

When used intentionally, GitHub supports **traceability, oversight, and shared understanding**.

---

## How to use this repository

You can safely:

- Read any file in this repository
- Follow links
- Share links with colleagues
- Reference or reuse content internally (this repository is CC0 licensed)

You do **not** need to:
- Create an account
- Install any tools
- Make changes to participate as a reader

Future sections will explain how to comment or suggest changes, if and when that is appropriate.

---

## Why Turtini publishes this

Turtini works in environments where **governance, accountability, and operational clarity matter**.

We believe modern government systems benefit from:
- Transparency over opacity
- Documented decision-making
- Shared understanding across technical and non-technical roles

This repository exists to make GitHub more approachable — not to promote tools, products, or services.

---

## License

This repository is released under **Creative Commons Zero (CC0 1.0 Universal)**.

You are free to copy, reuse, adapt, or incorporate this material into internal documentation or training without restriction.

---

## Status

This repository is intentionally evolving.

Content will be added incrementally as common questions arise and usage patterns become clearer.

## Documentation

```{toctree}
:maxdepth: 2

common-questions
common-terms
compliance-terms
internal-controls
participating-safely
command-line-optional
```