diff --git a/index.md b/index.md index 847d7cf..45fb268 100644 --- a/index.md +++ b/index.md @@ -8,7 +8,7 @@ description: CYBR 8420 Software Assurance Modules Content will be linked as we progress through the semester. This allows to me to update/create/re-design content throughout the semester. 1. **The Demand for Software Assurance** - * [Competencies](http://resources.sei.cmu.edu/library/asset-view.cfm?assetid=47953) and Sample [Job](https://robinagandhi.github.io/swa/resources/swa-positions-1.pdf) [Description](https://robinagandhi.github.io/swa/resources/swa-positions-2.pdf) + * [Competencies](http://resources.sei.cmu.edu/library/asset-view.cfm?assetid=47953) and Sample Job Descriptions: [1](https://www.cisa.gov/careers/work-rolessecure-software-assessor), [2](https://robinagandhi.github.io/swa/resources/swa-positions-1.pdf), [3](https://robinagandhi.github.io/swa/resources/swa-positions-2.pdf) 1. What is Software Assurance? * Reading: [Why hackers know more about our systems?](https://learning.oreilly.com/library/view/system-assurance/9780123814142/B9780123814142000014.xhtml) 1. **Collaborating when working on Software** diff --git a/pages/github.md b/pages/github.md index 1063878..6e2da52 100644 --- a/pages/github.md +++ b/pages/github.md @@ -107,12 +107,12 @@ Let's start by looking at option #1. First, check if Git is installed. > ![version](./img/gitVersionCheck.png) To `clone` a remote repository (what we set out to do), we first need a ```reference URL``` to find it. -* On `GitHub.com`, navigate to your hello-world repository and click on the button that says ```Clone or download```. -* Copy that URL. +* On `GitHub.com`, navigate to your hello-world repository and click on the green button that says ```<> Code```. +* Copy the URL under Clone that starts with HTTPS. * Now we are ready to clone this remote repository, and create a local repository. ```bash - git clone + git clone <> ``` Once you issue this command, you will start to see some download messages, and upon success, your local repository will be ready for use. You may be asked to authenticate with GitHub credentials if your repository is not public. @@ -379,9 +379,7 @@ In the figure below, When in the preview mode, notice the formatting effect of ` I suggest practicing using Markdown in this interactive tutorial: [http://www.markdowntutorial.com](http://www.markdowntutorial.com) -Explore functional uses of Markdown on GitHub here: [https://help.github.com/categories/writing-on-github/](https://help.github.com/categories/writing-on-github/) - -You are now ready to explore the wonderful world of open source on GitHub. Enjoy and make your contributions! +More advanced markdown formatting like [organizing data](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables) with tables and creating [code blocks](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks) is also possible. [Top](#table-of-contents) @@ -392,10 +390,13 @@ GitHub integrates several project management features with code management. Two Project planning requires creating shared expectations about tasks and their assignments. Issues are a way to create and assign tasks with GitHub. Follow this tutorial to make understand how to use Issues: [https://guides.github.com/features/issues/](https://guides.github.com/features/issues/) ## Project Boards -Project boards are useful planning tools. Work assignments are captured as cards and organized into lists. A basic Kanban-style board works best to sort cards into columns by status like "To Do," "In Progress," and "Done." Please follow this tutorial to create a project board in your hello-world repository: [https://docs.github.com/en/github/managing-your-work-on-github/creating-a-project-board#creating-a-repository-project-board](https://docs.github.com/en/github/managing-your-work-on-github/creating-a-project-board#creating-a-repository-project-board) +Project boards are useful planning tools. Work assignments are captured as cards and organized into lists. A table view or a Kanban-style board works best to sort cards into columns by status like "To Do," "In Progress," and "Done." Please follow this tutorial to create a project [https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects](https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects) + +A project also has automated workflows to add items automatically from issues in a repository. +[https://docs.github.com/en/issues/planning-and-tracking-with-projects/automating-your-project/adding-items-automatically](https://docs.github.com/en/issues/planning-and-tracking-with-projects/automating-your-project/adding-items-automatically) -## Linking Issues with Cards -Issues can be linked to cards in Project boards. An easy way is to reference the Issue number in the card description. For example, to reference Issue number 1 you would simple add `#1` to the card. Try this in your hello-world repository: [https://docs.github.com/en/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board](https://docs.github.com/en/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board) +## Building Tasklists +For your projects, planning task and subtasks can be usefule. Try adding tasklists in your hello-world repository: [https://docs.github.com/en/issues/managing-your-tasks-with-tasklists/quickstart-for-tasklists](https://docs.github.com/en/issues/managing-your-tasks-with-tasklists/quickstart-for-tasklists) [Top](#table-of-contents) @@ -404,6 +405,8 @@ We practice what we preach at UNO. Our whole course has been developed on GitHub Navigate to the [course repository on GitHub](https://github.com/robinagandhi/swa) and click fork. Boom, you have your own copy of the whole course, use responsibly 🤓 +You are now ready to explore the wonderful world of open source on GitHub. Enjoy and make your contributions! + [Top](#table-of-contents) # Cybersecurity First Principle Reflections diff --git a/slides/teams-2023/include/teams.md b/slides/teams-2023/include/teams.md new file mode 100644 index 0000000..0a94a73 --- /dev/null +++ b/slides/teams-2023/include/teams.md @@ -0,0 +1,82 @@ +class: center, middle +# Teams Fall 2023 + +--- + +# Team 1 + +## Members +- + +## Project Focus +- + +## Deliverables +- + +--- + +# Team 2 + +## Members +- + +## Project Focus +- + +## Deliverables +- + +--- + +# Team 3 + +## Members +- + +## Project Focus +- + +## Deliverables +- + +--- + +# Team 4 + +## Members +- + +## Project Focus +- + +## Deliverables +- + +--- + +# Team 5 + +## Members +- + +## Project Focus +- + +## Deliverables +- + +--- + +# Team 6 + +## Members +- + +## Project Focus +- + +## Deliverables +- + +--- \ No newline at end of file diff --git a/slides/teams-2023/teams.html b/slides/teams-2023/teams.html new file mode 100644 index 0000000..e281b75 --- /dev/null +++ b/slides/teams-2023/teams.html @@ -0,0 +1,114 @@ + + + + Teams Fall 2023 + + + + + + + +