HFOSS is not a lawyer, and this does not constitute legal advice.
1\) Please expand each of the following acronyms (1 pt each):
- 1.1) IRC
- 1.2) FOSS
- 1.3) OLPC
- 1.4) FSF
- 1.5) PR
2\) What is the name of the version control system we use in this course? (1 pt)
*Bonus:* Give the name for another version control system. (1pt)
3\) Please give the one-word name for the interface used in the OLPC computers & our VMs? (1 pt)
4\) *Bonus:* What is the short, two-letter name for the OLPC computers used in the final project for this class? (1 pt)
5\) We refer to sites that host source code as "forges". What is the name of the primary forge used in this course? (1 pt)
6\) *Bonus:* Name the other forge we have used? (1pt)
7\) *Bonus:* Name another forge, one we have not used for this course. (1pt)
```
```
Multiple choice
8\) The GitHub-specific term to describe the process in which, starting from one repository hosted at GitHub, one creates another repository, also hosted at GitHub, but under the control of a different user account.
a\) repository b) branch c) remote d) fork e) clone
```
```
9\) A collection of related commit objects
a\) repository b) branch c) remote d) fork e) clone
```
```
10\) A separate, but related, repository from which one may fetch or pull changes into one's own working copy, and to which in some instances one might have permission to push changes from one's own working copy.
a\) repository b) branch c) remote d) fork e) clone
```
```
11\) The general term in git for making an exact, working copy of another repository in which changes can be tracked separately between the two versions.
a\) repository b) branch c) remote d) fork e) clone
```
```
12\) A namespace in which one can track changes to a set of files within a given repository.
This term applies both to the action and to the result of the action.
Comparisons ('diffs' or patches) can be made between different such namespaces.
a\) repository b) branch c) remote d) fork e) clone
```
```
13) We've discussed "the four R's" as a shorthand for the freedoms attached to software for it to be considered "free" or "open source". List or describe each. (eg, if you can remember the "r" word you can just give that. If you cannot remember the term, but can describe the freedom involved, that also counts). Various "r" words are roughly synonymous for some of the freedoms, but we're counting freedoms here, not synonyms so if you give two (or more) terms for the same freedom, it only counts once. For the purposes of this quiz, "remix" does not count as describing any of them. (1pt each)
-
10.1)
-
10.2)
-
10.3)
-
10.4)