forked from Stat585-at-ISU/blog-2019
-
Notifications
You must be signed in to change notification settings - Fork 0
/
KueonJessica.Rmd
40 lines (25 loc) · 2.36 KB
/
KueonJessica.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
---
title: "All that legal stuff..."
author: "Firstname Lastname"
topic: "07"
layout: post
root: ../../../
---
## Background:
The `DESCRIPTION` file of a package contains the package's meta information. Most of the fields in this file are quite straight forward: author, version number, and a short package description. When you call `library(help="<package name>")` for package `<package name>` you can see the contents of the `DESCRIPTION` file for that package (and some parts of the `NAMESPACE` file).
Read through the chapter on [metadata](http://r-pkgs.had.co.nz/description.html) from Wickham's book on R packages.
Here, we want to focus on the use of licenses in R packages.
There are several important aspects to consider when choosing a license for your work.
Three of the main questions to answer are:
1. Are you and your collaborators fine with other people modifying your work and then sharing the modified work?
2. Are you and your collaborators fine with other people making a profit from those derivations?
3. Who is responsible if your software does not do what it promises to do?
Write a blog post addressing the following questions:
1. **Under what license does R operate?**
2. **Answer the three questions listed above for the licenses: MIT, GPL-3, LGPL-3, and CC-0. Note that some of the questions might not be answered with a simple yes/no. In that case, go into more detail, but do not just copy the terms of the license.**
3. **Assume that you are in the process of making a package for your own graduate work. Describe considerations that come into play in deciding on a license. In case you are not quite at that stage in your graduate studies yet, come up with a likely scenario. Describe it and discuss.**
## Instructions:
Update your forked version of the 'blog-2019' repository (or re-fork it after deleting your previous repo).
Save a **copy** of this file, replacing "Lastname" and "Firstname" with your own and *leave the original unedited*. (Note: Lastname = your family name, Firstname = your given name)
In **your copy**, replace the `title:` and `author:` fields in the YAML above, while leaving the remaining fields intact. Remove the background and the instructions sections and write your blog post!
Once you are done, **create a pull request** to upload your changes to the original repository. Do not commit the compiled HTML file to the repository.