├── .gitbook └── assets │ ├── image.png │ ├── never-give-up.jpeg │ └── openhack-banner.png ├── README.md ├── SUMMARY.md ├── code-of-conduct.md ├── cohort-1 ├── achievements.md ├── communication.md ├── getting-help.md ├── program-overview.md └── projects.md ├── cohort-2 ├── communication.md ├── getting-help.md ├── program-overview.md └── projects.md ├── communication.md ├── faq.md ├── openhack-banner.png ├── openhack-logo.png ├── post-openhack-todo-list.md ├── resources.md ├── responsibilities ├── junior-mentors.md ├── mentors.md └── students.md └── wall-of-love.md /.gitbook/assets/image.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FOSS-Cell-GECPKD/OpenHack-20/9b6a8953aec6a58bf7c08c903a9ca121ff693563/.gitbook/assets/image.png -------------------------------------------------------------------------------- /.gitbook/assets/never-give-up.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FOSS-Cell-GECPKD/OpenHack-20/9b6a8953aec6a58bf7c08c903a9ca121ff693563/.gitbook/assets/never-give-up.jpeg -------------------------------------------------------------------------------- /.gitbook/assets/openhack-banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FOSS-Cell-GECPKD/OpenHack-20/9b6a8953aec6a58bf7c08c903a9ca121ff693563/.gitbook/assets/openhack-banner.png -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Welcome! 2 | 3 | ![](.gitbook/assets/openhack-banner.png) 4 | 5 | FOSS OpenHack '20 is a program which offers students an opportunity to build open source projects at the FOSS Cell, GEC Palakkad and contribute to major open source projects under the guidance of mentors. Students get to learn the git workflow, explore new languages, frameworks & tools, improve leadership and collaboration skills while following best coding and open-source practices. This would help them build a strong foundation for their early career and they would walk away with an amazing experience to put on their resume. 6 | 7 | -------------------------------------------------------------------------------- /SUMMARY.md: -------------------------------------------------------------------------------- 1 | # Table of contents 2 | 3 | * [Welcome!](README.md) 4 | * [Wall of Love](wall-of-love.md) 5 | 6 | ## Cohort 2 7 | 8 | * [Program Overview](cohort-2/program-overview.md) 9 | * [Projects](cohort-2/projects.md) 10 | * [Communication](cohort-2/communication.md) 11 | * [Getting Help](cohort-2/getting-help.md) 12 | 13 | ## Cohort 1 14 | 15 | * [Program Overview](cohort-1/program-overview.md) 16 | * [Projects](cohort-1/projects.md) 17 | * [Achievements](cohort-1/achievements.md) 18 | * [Communication](cohort-1/communication.md) 19 | * [Getting Help](cohort-1/getting-help.md) 20 | 21 | ## Responsibilities 22 | 23 | * [Students](responsibilities/students.md) 24 | * [Mentors](responsibilities/mentors.md) 25 | * [Junior Mentors](responsibilities/junior-mentors.md) 26 | 27 | *** 28 | 29 | * [FAQ](faq.md) 30 | * [Resources](resources.md) 31 | * [Post OpenHack TODO List](post-openhack-todo-list.md) 32 | * [Code of Conduct](code-of-conduct.md) 33 | * [Contact Us](communication.md) 34 | -------------------------------------------------------------------------------- /code-of-conduct.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | ### Our Pledge 4 | 5 | We as contributors, mentors and managers pledge to make participation in this program a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. 6 | 7 | We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy program. 8 | 9 | ### Our Standards 10 | 11 | Examples of behavior that contributes to a positive environment for our program include: 12 | 13 | * Demonstrating empathy and kindness toward other people 14 | * Being respectful of differing opinions, viewpoints, and experiences 15 | * Giving and gracefully accepting constructive feedback 16 | * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience 17 | * Focusing on what is best not just for us as individuals, but for the overall program 18 | 19 | Examples of unacceptable behavior include: 20 | 21 | * The use of sexualized language or imagery, and sexual attention or advances of any kind 22 | * Trolling, insulting or derogatory comments, and personal or political attacks 23 | * Public or private harassment 24 | * Publishing others’ private information, such as a physical or email address, without their explicit permission 25 | * Other conduct which could reasonably be considered inappropriate in a professional setting 26 | 27 | ### Enforcement Responsibilities 28 | 29 | Program managers and mentors are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. 30 | 31 | Program managers and mentors have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. 32 | 33 | ### Scope 34 | 35 | This Code of Conduct applies within all program spaces, and also applies when an individual is officially representing the program in public spaces. Examples of representing our program include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. 36 | 37 | ### Enforcement 38 | 39 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the program managers responsible for enforcement at [anandbaburajan@gmail.com](mailto:anandbaburajan@gmail.com). All complaints will be reviewed and investigated promptly and fairly. 40 | 41 | All program managers and mentors are obligated to respect the privacy and security of the reporter of any incident. 42 | 43 | ### Enforcement Guidelines 44 | 45 | Program managers and mentors will follow these Program Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: 46 | 47 | #### 1. Correction 48 | 49 | **Program Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the program. 50 | 51 | **Consequence**: A private, written warning from program managers and mentors, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. 52 | 53 | #### 2. Warning 54 | 55 | **Program Impact**: A violation through a single incident or series of actions. 56 | 57 | **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in program spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. 58 | 59 | #### 3. Temporary Ban 60 | 61 | **Program Impact**: A serious violation of program standards, including sustained inappropriate behavior. 62 | 63 | **Consequence**: A temporary ban from any sort of interaction or public communication with the program for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. 64 | 65 | #### 4. Permanent Ban 66 | 67 | **Program Impact**: Demonstrating a pattern of violation of program standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. 68 | 69 | **Consequence**: A permanent ban from any sort of public interaction within the program. 70 | 71 | ### Attribution 72 | 73 | This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.0, available at [https://www.contributor-covenant.org/version/2/0/code\_of\_conduct.html](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html). 74 | 75 | Program Impact Guidelines were inspired by [Mozilla’s code of conduct enforcement ladder](https://github.com/mozilla/diversity). 76 | 77 | -------------------------------------------------------------------------------- /cohort-1/achievements.md: -------------------------------------------------------------------------------- 1 | # Achievements 2 | 3 | {% tabs %} 4 | {% tab title="Anaswara T Rajan" %} 5 | Google Summer of Code '21 at oCIS \(ownCloud\) under CERN 6 | 7 | **Project:** [https://summerofcode.withgoogle.com/projects/\#5918066472386560](https://summerofcode.withgoogle.com/projects/#5918066472386560) 8 | **GitHub:** [https://github.com/anaswaratrajan](https://github.com/anaswaratrajan) 9 | {% endtab %} 10 | {% endtabs %} 11 | 12 | {% tabs %} 13 | {% tab title="Muhammed Suhail" %} 14 | Google Summer of Code '21 at CVE Binary Tool \(Intel\) under Python Software Foundation 15 | 16 | **Project:** [https://summerofcode.withgoogle.com/projects/\#4546535053852672](https://summerofcode.withgoogle.com/projects/#4546535053852672) 17 | **GitHub:** [https://github.com/BreadGenie](https://github.com/BreadGenie) 18 | {% endtab %} 19 | {% endtabs %} 20 | 21 | {% tabs %} 22 | {% tab title="Athul Joshi" %} 23 | Open source contributions at Oppia/Oppia 24 | 25 | **Link**: [https://github.com/oppia/oppia/pulls?q=is%3Apr+is%3Aclosed+author%3Aathuljoshi](https://github.com/oppia/oppia/pulls?q=is%3Apr+is%3Aclosed+author%3Aathuljoshi) 26 | {% endtab %} 27 | {% endtabs %} 28 | 29 | {% tabs %} 30 | {% tab title="Alwin Joseph" %} 31 | Open source contributions at Oppia/Oppia-android 32 | 33 | **Link**: [https://github.com/oppia/oppia-android/pulls?q=is%3Apr+is%3Aclosed+alwin48](https://github.com/oppia/oppia-android/pulls?q=is%3Apr+is%3Aclosed+alwin48) 34 | {% endtab %} 35 | {% endtabs %} 36 | 37 | -------------------------------------------------------------------------------- /cohort-1/communication.md: -------------------------------------------------------------------------------- 1 | # Communication 2 | 3 | We will be using WhatsApp for both general and off-topic chat and all the participants would be added to OpenHack's WhatsApp group. Technical doubts and discussions are welcome at FOSS Cell's [Gitter chatroom](https://gitter.im/FOSS-Cell-GECPKD/community). 4 | 5 | Your project would also have an associated Gitter chatroom integrated with the GitHub repo. For the weekly stand-ups and show-and-tells, we will be using Jitsi Meet and all the sessions would be uploaded to OpenHack's [YouTube channel](https://www.youtube.com/channel/UCWFTHKmCRTlBx-XWhHuGSKg). 6 | 7 | Please check our code of conduct [here](https://openhack.gitbook.io/openhack-20/code-of-conduct). 8 | 9 | -------------------------------------------------------------------------------- /cohort-1/getting-help.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: >- 3 | Keep in mind that an important part of open source is self-reliance. We expect 4 | you to look for answers before approaching us for help. Try to ask your doubts 5 | in the open, unless it's specific to you. 6 | --- 7 | 8 | # Getting Help 9 | 10 | **Mentors** 11 | 12 | | **Name** | **Email** | Gitter | 13 | | :--- | :--- | :--- | 14 | | Anand Baburajan | [anandbaburajan@gmail.com](mailto:anandbaburajan@gmail.com) | [Link](https://gitter.im/anandbaburajan) | 15 | | Abijith Bahuleyan | [abijithbahuleyan@gmail.com](mailto:%20abijithbahuleyan@gmail.com) | [Link](https://gitter.im/twentyse7en) | 16 | | Muhammed Suhail | [msuhailbh07@gmail.com](mailto:%20msuhailbh07@gmail.com) | [Link](https://gitter.im/BreadGenie) | 17 | 18 | **Program Managers** 19 | 20 | | **Name** | **Email** | Gitter | 21 | | :--- | :--- | :--- | 22 | | Anand Baburajan | [anandbaburajan@gmail.com](mailto:anandbaburajan@gmail.com) | [Link](https://gitter.im/anandbaburajan) | 23 | | Abijith Bahuleyan | [abijithbahuleyan@gmail.com](mailto:%20abijithbahuleyan@gmail.com) | [Link](https://gitter.im/twentyse7en) | 24 | 25 | -------------------------------------------------------------------------------- /cohort-1/program-overview.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: 5th September, 2020 - 21st November, 2020 3 | --- 4 | 5 | # Program Overview 6 | 7 | To kickoff the program, a workshop would be hosted by Anand Baburajan and Abijith Bahuleyan on 5th September which would give you an understanding on FOSS, git, GitHub, open source contributions and OpenHack. 8 | 9 | How to participate? 10 | 11 | 1. **Make sure you have a GitHub account or create one**\ 12 | ****We will be using GitHub for hosting the code, collaboration, reviews, etc.\ 13 | 14 | 2. **Join** [**FOSS Cell's Gitter chatroom**](https://gitter.im/FOSS-Cell-GECPKD/community) **using your GitHub account**\ 15 | ****Apart from the Whatsapp group where you've been already added, technical doubts, suggestions, etc are welcome at the Gitter chatroom.\ 16 | 17 | 3. **Accept the mail invitation to join FOSS Cell, GEC PKD org on GitHub**\ 18 | ****That's where your projects would be hosted.\ 19 | 20 | 4. **Choose your project**\ 21 | Select one or more projects you'd like to work on from the [projects page](https://openhack.gitbook.io/openhack-20/cohort-1/projects). You are also welcome to suggest new ideas.\ 22 | 23 | 5. **Join your project's Gitter chatroom**\ 24 | ****Once we create a repo (repository) for your project, you need to join its Gitter chatroom using the button in your project's readme since project related communication would take place in the project chatrooms.\ 25 | 26 | 6. **Discuss roles**\ 27 | ****You can divide your project into smaller meaningful parts after dicussing with your mentors then divide the roles among your team. Your project should also have a maintainer who would look after the project, goals, contributions, etc.\ 28 | 29 | 7. **Sign up for GitHub's** [**student education pack**](https://education.github.com/pack)****\ 30 | ****The education pack provides free access to a lot of really helpful resources while you're a student. Make sure you use your college email ID while signing up.\ 31 | 32 | 8. **Start building**\ 33 | ****Have discussions in your chatrooms or video calls and start building!\ 34 | 35 | 9. **Follow best practices**\ 36 | One of the goals of OpenHack is to inclulcate best coding and open source practices among student developers. The mentors will review your pull requests (your code contributions) and provide you with suggestions on best practices. They will also open an issue titled "Best practices TODO" at your project's repo which is a list of things you need to take care of before submitting your project for the final review.\ 37 | 38 | 10. **Attend weekly stand-ups**\ 39 | ****We'll have meetings at 4PM every Saturday where all the OpenHackers would introduce themselves, what they've been upto the previous week, how their projects are going, any interesting challenge they faced, etc. So be sure to attend the stand-ups! We will also have show-and-tells where teams would explain their projects in detail along with what they learnt and the challenges they faced. All the meets will be uploaded to our [YouTube channel](https://www.youtube.com/channel/UCWFTHKmCRTlBx-XWhHuGSKg). 40 | -------------------------------------------------------------------------------- /cohort-1/projects.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: >- 3 | Choose a project which you are passionate about. Don't go with one just 4 | because it can be built with a language/framework you already know. New ideas 5 | are welcome! 6 | --- 7 | 8 | # Projects 9 | 10 | {% tabs %} 11 | {% tab title="Brick Breaker" %} 12 | A game in which the player must smash a wall of bricks by deflecting a bouncing ball with a paddle. When the player destroys all the bricks, they will win the game. 13 | 14 | **Link:** [https://github.com/FOSS-Cell-GECPKD/brick-breaker](https://github.com/FOSS-Cell-GECPKD/brick-breaker)\ 15 | **Tech used:** Java, JFrame, Jpanel, etc\ 16 | **Contributors:** [Aiswarya Anand](https://github.com/Aiswarya-anand) and [Samvrutha Shaji](https://github.com/SamvruthaShaji) 17 | {% endtab %} 18 | {% endtabs %} 19 | 20 | {% tabs %} 21 | {% tab title="Chat App" %} 22 | A realtime chat app which uses websockets for communication between two or more users. 23 | 24 | **Link:** [https://github.com/FOSS-Cell-GECPKD/chat-app](https://github.com/FOSS-Cell-GECPKD/chat-app)\ 25 | **Tech used:** JavaScript, React.Js, socket.io, etc\ 26 | **Contributors:** [Vipin K P](https://github.com/VipinVIP) and [Sankar Vinayak](https://github.com/sankarvinayak) 27 | {% endtab %} 28 | {% endtabs %} 29 | 30 | {% tabs %} 31 | {% tab title="DevPad" %} 32 | A blog app, based on HTML based content. 33 | 34 | **Link:** [https://github.com/FOSS-Cell-GECPKD/DevPad](https://github.com/FOSS-Cell-GECPKD/DevPad)\ 35 | **Tech used:** JavaScript, React.js, Express.js, MongoDB, etc\ 36 | **Contributors:** [Anas Vakyathodi](https://github.com/anasvakyathodi) and many other Hacktoberfest participants 37 | {% endtab %} 38 | {% endtabs %} 39 | 40 | {% tabs %} 41 | {% tab title="FOSS Cell blog" %} 42 | A blog for the FOSS Cell to share stories, achievements and for freshers at our college to make them aware of good CSE opportunities, things they could do/shouldn't do to become better at CSE, communities and all sorts of things which a student would find helpful. 43 | 44 | **Link:** [https://github.com/FOSS-Cell-GECPKD/foss-blog](https://github.com/FOSS-Cell-GECPKD/foss-blog)\ 45 | **Tech used:** JavaScript, Gatsby.js, etc.\ 46 | **Contributors:** [Saleekah](https://github.com/saleekah1234) and [Anaswara T Rajan](https://github.com/anaswaratrajan) 47 | {% endtab %} 48 | {% endtabs %} 49 | 50 | {% tabs %} 51 | {% tab title="Hide-it" %} 52 | A progresive web app (PWA) which utilizes whitespaces to make text invisible 53 | 54 | **Link:** [https://github.com/FOSS-Cell-GECPKD/Hide-it](https://github.com/FOSS-Cell-GECPKD/Hide-it)\ 55 | **Tech used:** JavaScript, React.js, PWA. etc\ 56 | **Contributors:** [Vipin K P](https://github.com/VipinVIP) and [Alwin Joseph](https://github.com/alwin48) 57 | {% endtab %} 58 | {% endtabs %} 59 | 60 | {% tabs %} 61 | {% tab title="Image-stego" %} 62 | An app which lets you hide text in images. 63 | 64 | **Link:** [https://github.com/FOSS-Cell-GECPKD/image-stego](https://github.com/FOSS-Cell-GECPKD/image-stego)\ 65 | **Tech used:** JavaScript, React.js, etc.\ 66 | **Contributors:** [Muhammed Suhail](https://github.com/BreadGenie), [Balasubramanian T K](https://github.com/btkcodedev) and [Aysha C M](https://github.com/Ayshhh) 67 | {% endtab %} 68 | {% endtabs %} 69 | 70 | {% tabs %} 71 | {% tab title="Interpreter" %} 72 | An attempt to port and improve Jlox, an interpreter for Lox language. 73 | 74 | **Link:** [https://github.com/FOSS-Cell-GECPKD/interpreter](https://github.com/FOSS-Cell-GECPKD/interpreter)\ 75 | **Tech used:** Python, etc.\ 76 | **Contributors:** [Abijith Bahuleyan](https://github.com/twentyse7en) and **** [Athul Joshi](https://github.com/AthulJoshi) 77 | {% endtab %} 78 | {% endtabs %} 79 | 80 | {% tabs %} 81 | {% tab title="Lifetree" %} 82 | Wrapper for GitGraph.js 83 | 84 | **Link:** [https://github.com/FOSS-Cell-GECPKD/Lifetree](https://github.com/FOSS-Cell-GECPKD/Lifetree)\ 85 | **Tech used:** JavaScript, gitgraph.js, React.js, etc\ 86 | **Contributors:** [Alwin Joseph](https://github.com/alwin48) and [Aryan Baburajan](https://github.com/aryanbaburajan) 87 | {% endtab %} 88 | {% endtabs %} 89 | 90 | {% tabs %} 91 | {% tab title="P2P File Transfer" %} 92 | A tool which lets you share files over a network (currently local area only) 93 | 94 | **Link:** [https://github.com/FOSS-Cell-GECPKD/P2P-file-transfer](https://github.com/FOSS-Cell-GECPKD/P2P-file-transfer)\ 95 | **Tech used:** Python, sockets, etc.\ 96 | **Contributors:** [Sankar Vinayak](https://github.com/sankarvinayak) and [Muhammed Rizal](https://github.com/MUHAMMEDRIZALKE) 97 | {% endtab %} 98 | {% endtabs %} 99 | 100 | {% tabs %} 101 | {% tab title="Price Tracker" %} 102 | An app which monitors, predicts and compares the prices of products every day and alerts you when prices drop, helping you decide when to buy. 103 | 104 | **Link:** [https://github.com/FOSS-Cell-GECPKD/Price-Tracker](https://github.com/FOSS-Cell-GECPKD/Price-Tracker)\ 105 | **Tech used:** Python, BeautifulSoup, JavaScript, React.js, etc\ 106 | **Contributors:** [Aravind K S](https://github.com/iamAravindks), [Balasubramanian T K](https://github.com/btkcodedev) and [Jithika Sagar](https://github.com/JITHIKASAGAR123) 107 | {% endtab %} 108 | {% endtabs %} 109 | 110 | {% tabs %} 111 | {% tab title="Today" %} 112 | A simple personal daily journal and social platform. 113 | 114 | **Link:** [https://github.com/FOSS-Cell-GECPKD/Today](https://github.com/FOSS-Cell-GECPKD/Today)\ 115 | **Tech used:** JavaScript, React.js, etc.\ 116 | **Contributors:** [Abhishek Mullacka](https://github.com/abhishek-mullackal)l**,** [Rajeev R](https://github.com/Rajeev-RJ), [Aravind K S](https://github.com/iamAravindks) and [Jaison Joshi](https://github.com/jaisonjoshi) 117 | {% endtab %} 118 | {% endtabs %} 119 | -------------------------------------------------------------------------------- /cohort-2/communication.md: -------------------------------------------------------------------------------- 1 | # Communication 2 | 3 | We will be using Discord for all general, off-topic chat, technical doubts and feedback-requests. The invite link will be shared to all the participants. 4 | 5 | **Channels:** 6 | 7 | * **announcements** - all the important updates on events, workshops, meets, etc 8 | * **general** - anything related to the program, coding, doubts, projects, etc. 9 | * **introduce-yourself** - share your name, GitHub username, facts about you, etc. 10 | * **alpha-track** - anything related to the Alpha Track 11 | * **beta-track** - anything related to the Beta Track 12 | * **feedback-requests** - if you need feedback on choices, resume, applications, etc 13 | * **git-and-github** - doubts related to Git & GitHub 14 | * **html-and-css** - doubts related to HTML & CSS 15 | * **javascript** - doubts related to JavaScript 16 | * **python** - doubts related to Python 17 | * **android** - doubts related to Android 18 | * **flutter** - doubts related to Flutter 19 | * **cpp** - doubts related to C++ 20 | * **off-topic** - anything unrelated to the program! :D 21 | 22 | Your project would also have an associated Gitter chatroom integrated with the GitHub repo. For the weekly stand-ups and show-and-tells, we will be using Jitsi Meet and all the sessions would be uploaded to OpenHack's [YouTube channel](https://www.youtube.com/channel/UCWFTHKmCRTlBx-XWhHuGSKg). 23 | 24 | Please check our code of conduct [here](https://openhack.gitbook.io/openhack-20/code-of-conduct). 25 | 26 | -------------------------------------------------------------------------------- /cohort-2/getting-help.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: >- 3 | Keep in mind that an important part of open source is self-reliance. We expect 4 | you to look for answers before approaching us for help. Try to ask your doubts 5 | in the open, unless it's specific to you. 6 | --- 7 | 8 | # Getting Help 9 | 10 | You can contact the junior mentors, mentors and program managers at our Discord. Please check the [communication](https://openhack.gitbook.io/openhack-20/cohort-2/communication) section for details on which channels to use. 11 | 12 | | **Name** | Role | Focus areas | 13 | | :--- | :--- | :--- | 14 | | Alwin Joseph | Mentor | C++ | 15 | | Anand Baburajan | Mentor | NumPy & TypeScript | 16 | | Anaswara T Rajan | Mentor | Python, Django & Databases | 17 | | Aravind K S | Mentor | JavaScript, React.js & CSS | 18 | | Aswin C G | Junior Mentor | Getting started with coding, editors, git, GitHub, etc | 19 | | Athul Joshi | Mentor | Python, Angular & git | 20 | | Dipanwita Guhathakurta | Mentor | Python, Javascript, Backend Development | 21 | | Hargun Kaur | Mentor | MERN stack & C++ | 22 | | Harshit Singh | Mentor | Flutter, Django, C++ | 23 | | Harshita Verma | Mentor | C++, HTML, CSS with Bootstrap | 24 | | Kajol Kumari | Mentor | Full stack web dev \(MEAN mostly\) & AWS | 25 | | Muhammed Suhail | Mentor | JavaScript, Node.js & git | 26 | | Rashin P | Junior Mentor | Getting started with coding, editors, git, GitHub, etc | 27 | | Vipin K P | Mentor | JavaScript, React.js & CSS | 28 | | Vishnu Sanal | Mentor | Android \(Java\) | 29 | | Yash Kumar Verma | Mentor | Node.js, TypeScript, React, React Native, Nest.js | 30 | | Yukty Khandelia | Junior Mentor | Getting started with coding, editors, git, GitHub, etc | 31 | 32 | **Program Managers** 33 | 34 | | **Name** | **Email** | 35 | | :--- | :--- | 36 | | Anand Baburajan | [anandbaburajan@gmail.com](mailto:anandbaburajan@gmail.com) | 37 | | Muhammed Suhail | [msuhailbh07@gmail.com](mailto:%20msuhailbh07@gmail.com) | 38 | 39 | -------------------------------------------------------------------------------- /cohort-2/program-overview.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: 14th December, 2020 - 1st February, 2020 3 | --- 4 | 5 | # Program Overview 6 | 7 | To kickoff the program, a workshop would be hosted on 14th December which would give you an understanding on FOSS, git, GitHub, open source contributions, OpenHack and other amazing open source programs. The program managers, mentors, junior mentors and students would also introduce themselves. 8 | 9 | After the workshop, you need to: 10 | 11 | 1. **Make sure you have a GitHub account**\ 12 | ****We will be using GitHub for hosting the code, collaboration, reviews, etc.\ 13 | 14 | 2. **Check out this site thoroughly**\ 15 | ****Especially the [student responsibilities](https://openhack.gitbook.io/openhack-20/responsibilities/students) section and the [communication](https://openhack.gitbook.io/openhack-20/cohort-2/communication) section.\ 16 | 17 | 3. **Introduce yourself at Discord**\ 18 | ****Let everyone know your name, which semester and department you are in, your GitHub username, your place, facts about you and anything you wish to share at the #introduce-yourself channel at our Discord!\ 19 | 20 | 4. **Accept the email invitation to join** [**FOSS Cell, GEC PKD org**](https://github.com/FOSS-Cell-GECPKD) **on GitHub**\ 21 | ****That's where your projects would be hosted.\ 22 | 23 | 5. **Sign up for GitHub's** [**student education pack**](https://education.github.com/pack)****\ 24 | ****The education pack provides free access to a lot of really helpful resources while you're a student. Make sure you use your college email ID while signing up. 25 | 26 | Once you're done with the aforementioned things, you can choose your track. The program is divided into two tracks: **Alpha** and **Beta**. 27 | 28 | ## Alpha Track 29 | 30 | In this track, you'll build 1-2 open source projects at the FOSS Cell in a team of 2-3 students. The mentors will review your code, suggest best practices and they would be available throughout the program if you require any assistance! Going with this track would help you learn the git workflow, explore new languages, frameworks & tools, project management, improve leadership and collaboration skills while following best coding and open-source practices. You'll walk away with 1-2 interesting projects in your portfolio and you would get to put an amazing experience on your resume! If you wish to apply for the [MLH Fellowship](https://fellowship.mlh.io) and similar programs in the future, this track would be a good choice! 31 | 32 | How to get started? 33 | 34 | 1. **Team up with 2-3 students and choose a project idea** 35 | 36 | ****\ 37 | ****Your project team would have 2-3 students who would use GitHub and Gitter to collaboratively build the project. The mentors would provide you some ideas but it's better if you come up with your own ideas to solve real-world problems then discuss with us! You can put forward your ideas in the #alpha-track along with the language/stack and other students would show interest. Don't go with an idea just because it can be built with a language/framework you already know. If you are new to coding, you still have enough time to get familiar with the basics of a programming language like Python or Javascript and build a mini project! After you come up with ideas, you need to discuss with the mentors its scope, features, tech used, time required, etc. after which a final idea would be decided and the mentors would suggest good resources to learn and follow.\ 38 | 39 | 2. **Join your project's Gitter chatroom**\ 40 | ****Once we create a GitHub repository for your project, you need to join your project's Gitter chatroom using the button in your project's readme (at the repository) since students would have project related discussions in their project's Gitter chatrooms.\ 41 | 42 | 3. **Discuss roles**\ 43 | ****You can divide your project into smaller meaningful parts after dicussing with your mentors and then divide the roles among your team. Your project should also have a maintainer who would look after the project, goals, contributions, etc.\ 44 | 45 | 4. **Start learning and building**\ 46 | ****Have discussions in your chatrooms or video calls and start building! The mentors will open an issue titled "Best practices TODO" at your project's repo which is a list of things you need to take care of before submitting your project for the final review. 47 | 48 | ## Beta Track 49 | 50 | In this track, you'll be contributing to major open source projects under the guidance of mentors at both OpenHack and at the organisation you wish to contribute to. Contributing to major open source projects is a great way to get a practical understanding of real-world software development. You would get to learn the git workflow, explore new things, solve challenging bugs and issues while following best coding and open-source practices. Also, your code is potentially used by lots of people! If you wish to apply for [Google Summer of Code](https://summerofcode.withgoogle.com) or similar open source programs in the future, this track would be a good choice! 51 | 52 | How to get started? 53 | 54 | 1. **Find open source projects**\ 55 | ****You can find interesting open source projects at GitHub, Google Summer of Code's organisations list, etc and try contributing to them. You can also contribute to open source projects you use in your daily life! 56 | 57 | 58 | 2. **Some ways of contributing** 59 | * Check out good-first-issues/beginner-friendly-issues 60 | * Find bugs and fix them 61 | * Improve the documentation which will help a lot of other people using the library/software/framework. 62 | * If you're using the project and need a feature, you can get in touch with the community, request for the feature and even code it up. 63 | * Add tests\ 64 | 65 | 3. **Read experiences of open source developers, GSoC & MLH Fellowship alumni**\ 66 | ****That's a good way of understanding how their journey was like, how they overcame challenges, etc. [Here](https://www.cncf.io/spotlights/cncf-maintainer-spotlight-goutham-veeramachaneni/)'s an interesting blog you might like and [here](https://medium.com/@viveknigam3003/getting-into-gsoc-20-with-cern-hsf-by-vivek-nigam-d7ec866c0533)'s another one.\ 67 | 68 | 4. **Approach OpenHack '20 mentors at #beta-track if you're stuck**\ 69 | ****We would be happy to help you get on track to getting your first few PRs merged!\ 70 | 71 | 5. **Stay positive** 72 | 73 | ![](../.gitbook/assets/never-give-up.jpeg) 74 | 75 | {% hint style="info" %} 76 | You can choose either of the tracks or even both of them if you wish! 77 | {% endhint %} 78 | 79 | Decided your track? 80 | 81 | 1. **Follow best practices**\ 82 | One of the goals of OpenHack is to inclulcate best coding, communication and open source practices among student developers. The mentors will review your pull requests (your code contributions) and provide you with suggestions on best practices. You're required to listen to the feedback and respond accordingly. Asking good questions is another good-to-have skill. Please check the section on student responsibilities for more good practices and feel free to explore online too!\ 83 | 84 | 2. **Attend weekly stand-ups**\ 85 | ****We'll have meetings at 4PM every Saturday where all the OpenHackers would share what they've been upto the previous week, how their projects are going, any challenges they faced, etc. So be sure to attend the stand-ups! We will also have show-and-tells where teams would explain their projects in detail along with what they learnt and the challenges they faced. All the meets will be uploaded to our [YouTube channel](https://www.youtube.com/channel/UCWFTHKmCRTlBx-XWhHuGSKg). 86 | -------------------------------------------------------------------------------- /cohort-2/projects.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: Project ideas chosen and built by students in the Alpha track 3 | --- 4 | 5 | # Projects 6 | 7 | {% tabs %} 8 | {% tab title="stone-paper-scissors" %} 9 | [https://github.com/FOSS-Cell-GECPKD/stone-paper-scissors](https://github.com/FOSS-Cell-GECPKD/stone-paper-scissors) 10 | {% endtab %} 11 | {% endtabs %} 12 | 13 | {% tabs %} 14 | {% tab title="pixelvibe" %} 15 | [https://github.com/FOSS-Cell-GECPKD/pixelvibe](https://github.com/FOSS-Cell-GECPKD/pixelvibe) 16 | {% endtab %} 17 | {% endtabs %} 18 | 19 | {% tabs %} 20 | {% tab title="Todo-List" %} 21 | [https://github.com/FOSS-Cell-GECPKD/Todo-List](https://github.com/FOSS-Cell-GECPKD/Todo-List) 22 | {% endtab %} 23 | {% endtabs %} 24 | 25 | {% tabs %} 26 | {% tab title="roots-and-squares" %} 27 | [https://github.com/FOSS-Cell-GECPKD/roots-and-squares](https://github.com/FOSS-Cell-GECPKD/roots-and-squares) 28 | {% endtab %} 29 | {% endtabs %} 30 | 31 | {% tabs %} 32 | {% tab title="tetris" %} 33 | [https://github.com/FOSS-Cell-GECPKD/tetris](https://github.com/FOSS-Cell-GECPKD/tetris) 34 | {% endtab %} 35 | {% endtabs %} 36 | 37 | {% tabs %} 38 | {% tab title="PlayTune" %} 39 | [https://github.com/FOSS-Cell-GECPKD/PlayTune](https://github.com/FOSS-Cell-GECPKD/PlayTune) 40 | {% endtab %} 41 | {% endtabs %} 42 | 43 | {% tabs %} 44 | {% tab title="daVinci-bot" %} 45 | [https://github.com/FOSS-Cell-GECPKD/daVinci-bot](https://github.com/FOSS-Cell-GECPKD/daVinci-bot) 46 | {% endtab %} 47 | {% endtabs %} 48 | 49 | {% tabs %} 50 | {% tab title="BudgetAssist" %} 51 | [https://github.com/FOSS-Cell-GECPKD/BudgetAssist](https://github.com/FOSS-Cell-GECPKD/BudgetAssist) 52 | {% endtab %} 53 | {% endtabs %} 54 | 55 | -------------------------------------------------------------------------------- /communication.md: -------------------------------------------------------------------------------- 1 | # Contact Us 2 | 3 | Before contacting us, please check the Program Overview and Communication sections corresponding to your cohort which will answer most of the questions. 4 | 5 | If you have questions about the website or specific to you alone, please email: 6 | [Anand Baburajan, FOSS Cell, GEC Palakkad](mailto:anandbaburajan@gmail.com) 7 | 8 | -------------------------------------------------------------------------------- /faq.md: -------------------------------------------------------------------------------- 1 | # FAQ 2 | 3 | * **Can a student or mentor from any college participate?**\ 4 | ****Yes, anyone who likes open source software is welcome!\ 5 | 6 | * **Can a student without any programming experience participate?**\ 7 | ****Yes, the program spans 2-3 months which we think is enough time for a beginner with basic familiarity with computers to learn the basics of a language like Python or JavaScript and build a mini project!\ 8 | 9 | * **Is there an entry fee or selection criteria?**\ 10 | ****No.\ 11 | 12 | * **Is programming background necessary to start learning Git?**\ 13 | ****No, Git is a version control system that can be used to record changes to even a .txt file\ 14 | 15 | * **What’s the difference between Git & GitHub?**\ 16 | ****Git is a version control system that lets you manage and keep track of your source code history whereas GitHub is a cloud-based hosting service that lets you manage Git repositories (and much more).\ 17 | 18 | * **Do you have any more resources to get familiar with Git & GitHub?**\ 19 | ****Yes we do! Here's our [resources](https://openhack.gitbook.io/openhack-20/resources) section.\ 20 | 21 | * **Would you teach programming to beginners?**\ 22 | ****Unforunately no. We won't be able to teach you programming but we’ll guide and help you with coding the right way, suggest resources and inculcate best practices!\ 23 | 24 | * **What should I do if I need help?**\ 25 | ****Please check out the [getting help](https://openhack.gitbook.io/openhack-20/cohort-2/getting-help) section and the [communication](https://openhack.gitbook.io/openhack-20/cohort-2/communication) section. 26 | -------------------------------------------------------------------------------- /openhack-banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FOSS-Cell-GECPKD/OpenHack-20/9b6a8953aec6a58bf7c08c903a9ca121ff693563/openhack-banner.png -------------------------------------------------------------------------------- /openhack-logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FOSS-Cell-GECPKD/OpenHack-20/9b6a8953aec6a58bf7c08c903a9ca121ff693563/openhack-logo.png -------------------------------------------------------------------------------- /post-openhack-todo-list.md: -------------------------------------------------------------------------------- 1 | # Post OpenHack TODO List 2 | 3 | Congratulations on completing OpenHack '20! We hope you learned a lot, worked on interesting projects, made good friends and built a strong foundation for your early career! You'll be receiving a completion certificate via mail soon. 4 | 5 | What next? 6 | 7 | * **Update your resume and social media accounts**\ 8 | ****The work you did over the last few months is a great way to showcase your skills to future employers. Remember to mention "**OpenHack '20 developer**" as the title and "**FOSS Cell, GEC PKD**" as the organisation name ("FOSS, GEC Palakkad" on LinkedIn). You should also put a few points in the description about the work you did. You can include the links to your project's repo and demo too. If you've also been a mentor at OpenHack '20, be sure to mention "**OpenHack '20 mentor**".\ 9 | 10 | * **Improve your project and help out contributors**\ 11 | ****Make sure to keep your project alive by maintaining it, adding new features etc. You can also try to help out future contributors by clearing their doubts, reviewing PRs, etc.\ 12 | 13 | * **Become a mentor and help others**\ 14 | ****You can give back to the community by helping others, getting them excited with open source, etc! You're also welcome to join next time as a mentor!\ 15 | 16 | * **Find open source projects**\ 17 | ****You can find interesting open source projects at GitHub, Google Summer of Code's organisations list, etc and try contributing to them. You can also contribute to open source projects you use in your daily life!\ 18 | \ 19 | Here are a few ways of contributing: 20 | * Check out good-first-issues/beginner-friendly-issues 21 | * Find bugs and fix them 22 | * Improve the documentation which will help a lot of other people using the library/software/framework. 23 | * If you're using the project and need a feature, you can get in touch with the community, request for the feature and even code it up. 24 | * Add tests\ 25 | 26 | * **Check out other programs** 27 | 1. [Google Summer of Code](https://summerofcode.withgoogle.com) 28 | 2. [MLH Fellowship](https://fellowship.mlh.io) 29 | 3. [Outreachy](https://www.outreachy.org) 30 | -------------------------------------------------------------------------------- /resources.md: -------------------------------------------------------------------------------- 1 | # Resources 2 | 3 | ## Git and GitHub 4 | 5 | Below are a few suggested resources which would help you to get familiar with Git and GitHub. You don't need to complete all of them, but familiarity and some practice with common commands would be helpful. 6 | 7 | * [Git tutorial for beginners](https://www.youtube.com/watch?v=PWqS4NBhEY8) 8 | * [GitHub flow](https://guides.github.com/introduction/flow/) 9 | * [GitHub Learning Lab](https://lab.github.com/) 10 | * [GitHub workflow live demo](https://www.youtube.com/watch?v=Z1G_pR3TooQ) 11 | * [Hello-opensource \(practice commands](https://github.com/FOSS-Cell-GECPKD/Hello-opensource)\) 12 | * [Udacity course on Git](https://www.udacity.com/course/version-control-with-git--ud123) 13 | * [Dangit, Git!?!](https://dangitgit.com/en) 14 | 15 | ## ./missing-semester 16 | 17 | We recommend to check out [The Missing Semester of Your CS Education](https://missing.csail.mit.edu/), a class taken at MIT with around nine topics which would help you "master the command-line, use a powerful text editor, use fancy features of version control systems, and much more!". It's available both as lecture notes and video recordings, so be sure to check it out! 18 | 19 | -------------------------------------------------------------------------------- /responsibilities/junior-mentors.md: -------------------------------------------------------------------------------- 1 | # Junior Mentors 2 | 3 | **To students** 4 | 5 | * Help beginners with doubts while getting started with coding, IDEs, git, GitHub, etc 6 | * Make sure students aren't stuck, if they're get in touch with them 7 | * Give them constructive feedback, be patient and respectful 8 | * Keep in touch \(check your notifications on GitHub, Discord, etc at least once a day\) 9 | 10 | **To program managers** 11 | 12 | * Inform when availability will be reduced 13 | * Inform if there are issues with a student \(communication, progress, etc\) 14 | * Lead weekly stand-ups 15 | 16 | -------------------------------------------------------------------------------- /responsibilities/mentors.md: -------------------------------------------------------------------------------- 1 | # Mentors 2 | 3 | **To students** 4 | 5 | * Help them communicate freely and in the open 6 | * Give them constructive feedback, be patient and respectful 7 | * Teach them how to ask good questions and get answers 8 | * Help them out with doubts 9 | * Follow best practices while reviewing their code 10 | * Don't merge a pull request until at least **two** mentors have approved the code 11 | * Suggest them good resources 12 | * Keep in touch (check your notifications on GitHub, Discord, etc at least once a day) 13 | 14 | **To program managers** 15 | 16 | * Inform when availability will be reduced 17 | * Inform if there are issues with a student (communication, progress, etc) 18 | * Provide us feedback regarding the program 19 | * Lead weekly stand-ups 20 | 21 | **** 22 | -------------------------------------------------------------------------------- /responsibilities/students.md: -------------------------------------------------------------------------------- 1 | # Students 2 | 3 | * Actively participate in the program 4 | * Ask for help when something is preventing you from achieving a goal 5 | * Ask your question in the open if it could be beneficial to someone else too 6 | * Look for answers yourself before going to the mentors for help 7 | * Don't say just ["hello"](https://www.nohello.com/) in the chat 8 | * Help other fellow students with their doubts 9 | * Listen and respond to feedback, especially during reviews 10 | * Submit quality code and follow best practices \(your mentors would help\) 11 | * Don't merge a pull request until at least **two** mentors have approved the code 12 | * Keep in touch \(check your notifications on GitHub, Discord, etc at least once a day\) 13 | * Regularly participate in the weekly stand-ups 14 | * Provide us feedback in the forms we will be sharing 15 | 16 | -------------------------------------------------------------------------------- /wall-of-love.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: >- 3 | Here's what OpenHack members liked about the program, how OpenHack helped them 4 | and why they would recommend OpenHack to their juniors. 5 | --- 6 | 7 | # Wall of Love 8 | 9 | {% tabs %} 10 | {% tab title="Sreelakshmi Jayarajan" %} 11 | I have to mention the amount of efforts Anand put into mentoring me as a beginner by having daily calls, helping me with starting up, listening patiently and helping me out every time I got really stuck. I'm grateful for the time and effort he put into making me realize my mistakes and for encouraging me to keep pushing myself to do challenging things. The constant sharing of resources, blogs, videos, his long TED talks etc., gave me a lot of exposure and I learnt a lot. I'm happy that I was able to open my first ever PR at Serenity OS without any prior experience. I wrote my first ever blog post to inspire students to contribute to open source. I built a few projects, contributed to Open-MSS⁠ and applied for GSoC there. I'm happy that I met Anand in my first year of college! 12 | {% endtab %} 13 | {% endtabs %} 14 | 15 | {% tabs %} 16 | {% tab title="Vishnu Sanal T" %} 17 | OpenHack - whoo, reminds me of my vulnerable, naive & indeed foolish days of S1! ... reminds me of feeling excited, that I haven't felt in a while, back then. 18 | 19 | If I talk about the ways OpenHack has helped me, it gave me much-needed guidance during my early days of college, being a newly-college-joined student, you can imagine all the overwhelms a student would face. 20 | 21 | OpenHack did offer a platform for me to help a handful of students to get started on programming, to familiarize them with different tech stacks, version control systems like Git, etc. This eventually led to the penning of [this](https://dev.to/vishnusanal/getting-started-with-software-engineering-as-a-freshman-1007) blog post, my first ever. OpenHack inspired me to focus more on my personal projects & to be further involved in OSS contributions, which led me to join [@TeamAmaze](https://github.com/TeamAmaze/) as a maintainer & later to become a contributor at [Robotutor](https://www.cmu.edu/scs/robotutor/index.html), Carnegie Mellon University. 22 | 23 | But the most noteworthy element I gained from OpenHack would be the inspiration to keep on coding, to keep on writing code, no matter what! 24 | 25 | It was a privilege working (& just being!) with fellow OpenHack-ers. I still consider the contact with fellow OpenHack-ers, be it, mentors or students, to be divine & priceless. 26 | 27 | If an OpenHack happens ever again, I'd be ~the first one~ one of the first members to join it! 28 | 29 | You're Awesome :) 30 | {% endtab %} 31 | {% endtabs %} 32 | 33 | {% tabs %} 34 | {% tab title="Aswin CG" %} 35 | Open Hack has been a game changer for me and I am lucky enough to to be a part of it in my freshman year. The program was intensive with practical sessions and standups helping beginners to get started in the world of open source. Open hack inspired me to work harder on my projects and gave me the idea of giving back to the community by involving in open source projects. Lucky that I got exposure to all this from S1 which gave me a perspective about the real industry standards and collaborating professionally. 36 | {% endtab %} 37 | {% endtabs %} 38 | 39 | {% tabs %} 40 | {% tab title="Your name" %} 41 | Your message 42 | {% endtab %} 43 | {% endtabs %} 44 | --------------------------------------------------------------------------------