20 lines
1.1 KiB
Markdown
20 lines
1.1 KiB
Markdown
|
---
|
||
|
|
title: "Why Git?"
|
||
|
|
weight: 10
|
||
|
|
---
|
||
|
|
|
||
|
|
# Why Git?
|
||
|
|
|
||
|
|
## Decentralization
|
||
|
|
|
||
|
|
While Gabriel controls the **cyberfreedom.ca** domain name, anyone is able to fork the project for their own needs and/or publish their own changes. Licensed under [Creative Commons Attribution-ShareAlike 4.0 International](http://creativecommons.org/licenses/by-sa/4.0), only attribution is needed.
|
||
|
|
|
||
|
|
With copies of the site being distributed among contributors there really isn't a single-point of failure. Ideally, this means that the project can live on even if this particular attempt fails. In addition to this, changes can be submitted anonymously with as much or as little about the author recorded as desired.
|
||
|
|
|
||
|
|
If this model proves successful, it's not difficult for a foreign project leader to fork the project for a different country's needs, reducing repetitive work.
|
||
|
|
|
||
|
|
## Source Control
|
||
|
|
|
||
|
|
It's nice to be able to track changes or even reverse mistakes. Git is built for managing changes which makes it the perfect tool for collaboration. Contributions also allow for attribution on a
|
||
|
|
|
||
|
|
## Division of Labor
|