├── logo └── awesome.sketch ├── .circleci └── config.yml ├── utils └── auto-toc.js ├── package.json ├── LICENSE.md ├── .gitignore ├── CONTRIBUTING.md ├── CODE-OF-CONDUCT.md └── README.md /logo/awesome.sketch: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kathgironpe/awesome-omscs/HEAD/logo/awesome.sketch -------------------------------------------------------------------------------- /.circleci/config.yml: -------------------------------------------------------------------------------- 1 | version: 2 2 | jobs: 3 | build: 4 | docker: 5 | - image: circleci/node:7.10 6 | 7 | working_directory: ~/repo 8 | 9 | steps: 10 | - checkout 11 | - restore_cache: 12 | keys: 13 | - v1-dependencies-{{ checksum "package.json" }} 14 | - v1-dependencies- 15 | 16 | - run: npm install 17 | 18 | - save_cache: 19 | paths: 20 | - node_modules 21 | key: v1-dependencies-{{ checksum "package.json" }} 22 | 23 | # run tests! 24 | - run: npm test 25 | -------------------------------------------------------------------------------- /utils/auto-toc.js: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env node 2 | const chalk = require('chalk'); 3 | const toc = require('markdown-toc'); 4 | const fs = require('fs'); 5 | 6 | const strip = (text)=> (text.trim()); 7 | const read = (file)=> (strip(fs.readFileSync(file, 'utf8'))); 8 | const replaceContents = (file, replacement)=> { 9 | fs.writeFile(file, replacement, err => { 10 | console.log(chalk.green('Successfully updated the table of contents')); 11 | }); 12 | }; 13 | const doc = read('./README.md'); 14 | // We have to follow the official awesome list linter's standard 15 | const newDoc = toc.insert(doc, {bullets: '-'}); 16 | 17 | replaceContents('./README.md', newDoc); 18 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "awesome-omscs", 3 | "version": "0.0.1", 4 | "description": "Awesome OMSCS Resources", 5 | "main": "index.js", 6 | "scripts": { 7 | "toc": "./utils/auto-toc.js" 8 | }, 9 | "repository": { 10 | "type": "git", 11 | "url": "git+https://github.com/kathgironpe/awesome-omscs.git" 12 | }, 13 | "keywords": [ 14 | "OMSCS", 15 | "GA Tech" 16 | ], 17 | "author": "Katherine G. Pe", 18 | "license": "MIT", 19 | "bugs": { 20 | "url": "https://github.com/kathgironpe/awesome-omscs/issues" 21 | }, 22 | "homepage": "https://github.com/kathgironpe/awesome-omscs#readme", 23 | "devDependencies": { 24 | "awesome-lint": "^0.10.0" 25 | }, 26 | "bin": { 27 | "auto-toc": "./utils/auto-toc.js" 28 | }, 29 | "dependencies": { 30 | "markdown-toc": "^1.2.0" 31 | } 32 | } 33 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | # MIT License 2 | 3 | Copyright (c) 2018 Katherine G. Pe 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Logs 2 | logs 3 | *.log 4 | npm-debug.log* 5 | yarn-debug.log* 6 | yarn-error.log* 7 | 8 | # Runtime data 9 | pids 10 | *.pid 11 | *.seed 12 | *.pid.lock 13 | 14 | # Directory for instrumented libs generated by jscoverage/JSCover 15 | lib-cov 16 | 17 | # Coverage directory used by tools like istanbul 18 | coverage 19 | 20 | # nyc test coverage 21 | .nyc_output 22 | 23 | # Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files) 24 | .grunt 25 | 26 | # Bower dependency directory (https://bower.io/) 27 | bower_components 28 | 29 | # node-waf configuration 30 | .lock-wscript 31 | 32 | # Compiled binary addons (https://nodejs.org/api/addons.html) 33 | build/Release 34 | 35 | # Dependency directories 36 | node_modules/ 37 | jspm_packages/ 38 | 39 | # TypeScript v1 declaration files 40 | typings/ 41 | 42 | # Optional npm cache directory 43 | .npm 44 | 45 | # Optional eslint cache 46 | .eslintcache 47 | 48 | # Optional REPL history 49 | .node_repl_history 50 | 51 | # Output of 'npm pack' 52 | *.tgz 53 | 54 | # Yarn Integrity file 55 | .yarn-integrity 56 | 57 | # dotenv environment variables file 58 | .env 59 | 60 | # next.js build output 61 | .next 62 | 63 | # vuepress build output 64 | .vuepress/dist 65 | 66 | # Serverless directories 67 | .serverless 68 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contribution Guidelines 2 | 3 | Please note that this project is released with a [Contributor Code of Conduct](CODE-OF-CONDUCT.md). By participating in this project you agree to abide by its terms. 4 | 5 | --- 6 | 7 | Ensure your pull request adheres to the following guidelines: 8 | 9 | - Make an individual pull request for each suggestion. 10 | - Use the following format: `- [package](link).` 11 | - A description is not required, but encouraged when necessary. 12 | - Additions should be added to the bottom of the relevant category. Maintainers will sort this based on relevance. We do not sort alphabetically to give emphasis that some resources are more important. 13 | - Link to the GitHub repo if the project is on GitHub. 14 | - Keep descriptions short and simple, but descriptive. 15 | - Start the description with a capital and end with a full stop/period. 16 | - Don't start the description with `A` or `An`. 17 | - Check your spelling and grammar. 18 | - Make sure your text editor is set to remove trailing whitespace. 19 | - The pull request should have a useful title and include a link to the package and why it should be included. 20 | - New categories or improvements to the existing categorization are welcome, but should be done in a separate pull request. 21 | - To generate new table of contents, run the command `npm run toc`. Please refer to Installation section if the command does not work. You need to do this if you added a new subcategory. 22 | 23 | ### Installing Dependencies 24 | 25 | You need the latest version of `node.js` and `npm`. 26 | 27 | Install the dependencies locally: 28 | 29 | ``` 30 | npm i 31 | ``` 32 | 33 | You can run the command for creating Table of Contents without globally installing anything: 34 | 35 | ``` 36 | ./utils/auto-toc.js 37 | ``` 38 | 39 | ### Updating your PR 40 | 41 | A lot of times, making a PR adhere to the standards above can be difficult. If the maintainers notice anything that we'd like changed, we'll ask you to edit your PR before we merge it. If you're not sure how to do that, [here is a guide](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) on the different ways you can update your PR so that we can merge it. 42 | -------------------------------------------------------------------------------- /CODE-OF-CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, gender identity and expression, level of experience, 9 | nationality, personal appearance, race, religion, or sexual identity and 10 | orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | * Trolling, insulting/derogatory comments, and personal or political attacks 28 | * Public or private harassment 29 | * Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | * Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or 41 | reject comments, commits, code, wiki edits, issues, and other contributions 42 | that are not aligned to this Code of Conduct, or to ban temporarily or 43 | permanently any contributor for other behaviors that they deem inappropriate, 44 | threatening, offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | ## Enforcement 56 | 57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 58 | reported by contacting the project team at kp@kat.pe. All 59 | complaints will be reviewed and investigated and will result in a response that 60 | is deemed necessary and appropriate to the circumstances. The project team is 61 | obligated to maintain confidentiality with regard to the reporter of an incident. 62 | Further details of specific enforcement policies may be posted separately. 63 | 64 | Project maintainers who do not follow or enforce the Code of Conduct in good 65 | faith may face temporary or permanent repercussions as determined by other 66 | members of the project's leadership. 67 | 68 | ## Attribution 69 | 70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, 71 | available at [http://contributor-covenant.org/version/1/4][version] 72 | 73 | [homepage]: http://contributor-covenant.org 74 | [version]: http://contributor-covenant.org/version/1/4/ 75 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Awesome OMSCS 2 | 3 | > Resources on admission, and how to succeed for the Online Master of Science in Computer Science program of the Georgia Institute of Technology. 4 | 5 | 6 | We encourage [contributions](./CONTRIBUTING.md). Please read the guidelines including the [code of conduct](./CODE-OF-CONDUCT.md). If you are enrolled at Georgia Tech, please follow the University's rules. 7 | 8 | 9 | **Disclaimer: we do not guarantee that all of the information on this page are reliable. You have to read through the official website's FAQ first.** 10 | 11 | 12 | ## Contents 13 | 14 | 15 | 16 | - [Admission Resources](#admission-resources) 17 | - [Official Resources for Admission](#official-resources-for-admission) 18 | - [Unofficial Resources for Admission](#unofficial-resources-for-admission) 19 | - [Computer Science Courses & Resources](#computer-science-courses--resources) 20 | - [Introduction to Computer Science](#introduction-to-computer-science) 21 | - [Mathematics for Computer Science](#mathematics-for-computer-science) 22 | - [Open Source Computer Science Education](#open-source-computer-science-education) 23 | - [Post-admission Resources](#post-admission-resources) 24 | - [Official guides and resources](#official-guides-and-resources) 25 | - [Unofficial guides and resources](#unofficial-guides-and-resources) 26 | - [Resources for International Applicants](#resources-for-international-applicants) 27 | - [TOEFL](#toefl) 28 | - [Georgia Institute of Technology General Info](#georgia-institute-of-technology-general-info) 29 | - [History](#history) 30 | - [Rank](#rank) 31 | - [Social Media](#social-media) 32 | - [Reddit](#reddit) 33 | - [Facebook](#facebook) 34 | - [Twitter](#twitter) 35 | - [Slack](#slack) 36 | 37 | 38 | 39 | ## Admission Resources 40 | 41 | ### Official Resources for Admission 42 | 43 | - [Official OMS CS FAQ](http://www.omscs.gatech.edu/prospective-students/faq) 44 | - [Academic Calendar](https://registrar.gatech.edu/calendar) 45 | - [Costs and Payment Schedule](http://www.omscs.gatech.edu/program-info/cost-payment-schedule) 46 | - [Application Deadlines, Process and Requirements](https://www.omscs.gatech.edu/program-info/application-deadlines-process-requirements) 47 | - [Minimum TOEFL score: 100](http://www.omscs.gatech.edu/prospective-students/faq) 48 | 49 | ### Unofficial Resources for Admission 50 | 51 | - [GPA Calculator](https://applications.wes.org/igpa-calculator/) 52 | - [Minimum number of recommendation letters: 2](https://www.reddit.com/r/OMSCS/comments/2emm9g/how_many_letters_of_recommendation/) 53 | 54 | 55 | 56 | ## Computer Science Courses & Resources 57 | 58 | 59 | ### Introduction to Computer Science 60 | 61 | - [Harvard's CS 50](https://www.edx.org/course/cs50s-introduction-computer-science-harvardx-cs50x) 62 | - [Introduction to Computing in Python](https://www.edx.org/professional-certificate/introduction-to-computing-in-python) 63 | 64 | ### Mathematics for Computer Science 65 | 66 | - [Shanghai Jiao Tong University's Discrete Mathematics](https://www.coursera.org/learn/discrete-mathematics) 67 | 68 | ### Open Source Computer Science Education 69 | 70 | - [Open Source Society University](https://github.com/ossu/computer-science) 71 | - [MIT Challenge](https://www.scotthyoung.com/blog/myprojects/mit-challenge-2) 72 | - [How to get an equivalent of a CS major using MOOCs](https://backdoorgraduteschooladmissions.quora.com/How-to-get-an-equivalent-of-a-CS-major-using-MOOCs) 73 | 74 | ## Post-admission Resources 75 | 76 | ### Official guides and resources 77 | 78 | - [OMS CS Onboarding](http://www.omscs.gatech.edu/online-ms-cs/omscsportal/onboarding) 79 | - [Specializations](https://www.omscs.gatech.edu/program-info/specializations) 80 | - [OMS CS Newsletter](https://www.omscs.gatech.edu/current-students/newsletter) 81 | - [Buzzport](https://buzzport.gatech.edu) 82 | - [Student Handbook](http://grad.gatech.edu/student-handbook) 83 | - [Academic Calendar](https://registrar.gatech.edu/calendar) 84 | 85 | 86 | ### Unofficial guides and resources 87 | 88 | - [How to Succeed in OMSCS](http://omscs.wikidot.com) 89 | - [OMSCental](https://omscentral.com) 90 | - [OMSCS Survival Guide](https://github.com/pyjarrett/OMSCS_Survival_Guide) 91 | - [Software and Discounts for GT OMSCS Students](https://docs.google.com/spreadsheets/d/1Gk3IPDd7_WyKeSfyuxXWrh4Hkk80As82CnaOO2m750M/edit#gid=0) 92 | - [OMSCS Notes](https://www.omscs-notes.com/) 93 | - [OMS Notes](http://omsnotes.com/) 94 | 95 | ## Resources for International Applicants 96 | 97 | ### TOEFL 98 | 99 | - [TOEFL iBT](https://www.ets.org/toefl/ibt/about) 100 | - [Official TOEFL Practice Test](http://toeflpractice.ets.org) 101 | - [TOEFL Free Practice Test](https://www.ets.org/s/toefl/free-practice/start.html) 102 | 103 | 104 | ## Georgia Institute of Technology General Info 105 | 106 | ### History 107 | 108 | - [History and Traditions](http://www.gatech.edu/about/history-traditions) 109 | 110 | ### Rank 111 | 112 | - [Top 6 in Computer Science - United States](https://www.usnews.com/best-colleges/georgia-tech-1569/overall-rankings) 113 | - [QS World University Rankings 2018: Statistics - Top 7 Worldwide](https://www.theguardian.com/higher-education-network/2018/feb/28/qs-world-university-rankings-2018-statistics) 114 | - [THE World University Rankings 2019: Top 7 Worldwide](https://www.timeshighereducation.com/world-university-rankings/georgia-institute-technology?ranking-dataset=589595) 115 | 116 | 117 | ## Social Media 118 | 119 | ### Reddit 120 | 121 | - [Reddit OMSCS](https://www.reddit.com/r/OMSCS/) 122 | 123 | ### Facebook 124 | 125 | - [OMSCS Students](https://www.facebook.com/groups/gtomscsstudents) 126 | 127 | ### Twitter 128 | 129 | - [GA Tech OMS CS](https://twitter.com/gtomscs) 130 | 131 | ### Slack 132 | 133 | - [OMS CS Study Group](https://omscs-study.slack.com) 134 | 135 | 136 | ## License 137 | 138 | [![CC0](http://mirrors.creativecommons.org/presskit/buttons/88x31/svg/cc-zero.svg)](https://creativecommons.org/publicdomain/zero/1.0/) 139 | 140 | To the extent possible under law, [Katherine Giron Pe](https://kat.pe) has waived all copyright and related or neighboring rights to this work. 141 | --------------------------------------------------------------------------------