Include, "add a license" to activity #25
Comments
StoneyJackson
added a commit
that referenced
this issue
Jun 8, 2018
# Version 2.0.0 ## Goals - Avoid unsafe operations (e.g., `git rebase`). - Introduce some additional best practices (e.g., `git commit -v`; checking what files will be committed before committing, and modifying .gitignore if it's wrong.). - Reduce the number of different commands required to learn, but possibly require more commands to be issued (e.g., `git branch feature; git checkout feature` instead of `git checkout -b feature`; it might seem like the latter is easier, but then you must know the purpose of -b, and when to leave it off). - Rely on more external resources for instructions and provide more links to other resources. ## To-do - [x] Create contributor guide - [x] Create maintainer guide - [x] Delete old reference - [x] Rewrite activity - [x] Link activity to steps in contributor guide. - [x] Link activity to steps in maintainer guide. - [x] Rewrite presentation.pptx - [x] Update README - [x] Add license to each file - [x] Address feedback - [x] Tag master as v1.0.0 ## Issues - Closes #25 because they are now asked to add a license - Closes #22 because reflection subsections are added to each section - Closes #21 because there are now different guides for different roles - Closes #24 because <MY_URL> and <THEIR_URL> are gone; although folks could still get confused by all caps placeholders even though they are explained at the beginning of the guide. - Closes #18 because no paths are given - Closes #20 because I gave a new guess to the time requirements. - Closes #23 because there are now each section ends with reflection questions which are times for group discussions. - Closes #31 - Closes #30 - Closes #29 - Closes #32 - Closes #33 - Closes #34
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In "Part 2: Create official upstream repository in organization" (https://github.com/StoneyJackson/github-workflow-activity/blob/master/activity.md#part-2-create-official-upstream-repository-in-organization) students should be sure to include a license when creating a new repository. Nice point to discuss Creative Commons versus OSI approved open source software license.
The text was updated successfully, but these errors were encountered: