10/19 basic

Author: brownsarahm

_practice/2022-10-19.md

@@ -0,0 +1,7 @@
+1. Make your script form class a nested loop to check for all 3 types of files
+1. Make a script that gets the updates to the course site and creates a single `todo-YYYY-MM-DD.md` file that has the review, prepare, and practice tasks in it  for each date that does not already exist in a `todo/` folder outside of your KWL repo. Save the script as `gathertasks.sh`
+
+```{index} checker.sh
+```
+```{index} gathertasks.sh
+```

_prepare/2022-10-19.md

@@ -0,0 +1,11 @@
+1. On Windows, install Putty ( we will use this Monday) 
+2. Get ready for class by creating `networking.md` in your KWL repo with notes about what you know about networking
+3. Add an issue on your KWL repo titled "Self Reflection 10/24" (there will be time on Monday for this, but giving you warning so you have time to think about it). Tag @brownsarahm on this issue. 
+```{index} networking.md
+```
+```
+1. Are you where you want to be in this course?
+1. Have you been getting feedback on your work?
+1. If not, what could help you get back on track?
+1. What if any concepts are you most struggling with?
+```

_review/2022-10-19.md

@@ -0,0 +1,10 @@
+1. Update your KWL Chart learned column with what you've learned
+2. Make a [contribution](groupcontrib) to your group repo and do a peer review of a team member's PR.
+3. Use the gh cli, grep, and bash to create `group_contributions.md` to your KWL repo with a list of all of your PRs. Append your history from creating this to the bottom of the file after `## Commands`
+4. Move your checker script into your kwl repo and update the paths so that it still works
+
+```{index}  group_contributions.md
+```
+
+```{index}  checker.sh
+```

activities/practice.md

@@ -122,3 +122,11 @@ Activities:
 Activities:
 ```{include} ../_practice/2022-10-17.md
 ```
+
+## 2022-10-19
+
+[related notes](../notes/2022-10-19)
+
+Activities:
+```{include} ../_practice/2022-10-19.md
+```

activities/prepare.md

@@ -144,3 +144,11 @@ Activities:
 Activities:
 ```{include} ../_prepare/2022-10-17.md
 ```
+
+## 2022-10-19
+
+[related notes](../notes/2022-10-19)
+
+Activities:
+```{include} ../_prepare/2022-10-19.md
+```

activities/review.md

@@ -146,3 +146,11 @@ Activities:
 Activities:
 ```{include} ../_review/2022-10-17.md
 ```
+
+## 2022-10-19
+
+[related notes](../notes/2022-10-19)
+
+Activities:
+```{include} ../_review/2022-10-19.md
+```

activities/team.md

@@ -1,6 +1,29 @@
 # Team Repo
 
+(groupcontrib)=
+## Contributions
 
+Your team repo is a place to build up a glossary of key terms and a "cookbook" of "recipes" of common things you might want to do on the shell, bash commands, git commands and others.  
+
+For the glossary, follow the [jupyterbook]() syntax.  
+
+For the cookbook, use standard markdown.
+
+to denote code inline `use single backticks`
+```
+to denote code inline `use single backticks`
+```
+
+to make a code block use 3 back ticks
+````
+```
+to make a code block use 3 back ticks
+```
+````
+
+To nest blocks use increasing numbers of back ticks.
+
+To make a link, `[show the text in squarebrackets](url/in/parenthesis)`
 
 ## Collaboration