├── .vscode └── settings.json ├── CODE_OF_CONDUCT.md ├── LICENSE ├── README.md └── contributing.md /.vscode/settings.json: -------------------------------------------------------------------------------- 1 | { 2 | "workbench.colorCustomizations": { 3 | "activityBar.activeBackground": "#ef86d4", 4 | "activityBar.background": "#ef86d4", 5 | "activityBar.foreground": "#15202b", 6 | "activityBar.inactiveForeground": "#15202b99", 7 | "activityBarBadge.background": "#ebf8c7", 8 | "activityBarBadge.foreground": "#15202b", 9 | "commandCenter.border": "#15202b99", 10 | "sash.hoverBorder": "#ef86d4", 11 | "statusBar.background": "#e959c4", 12 | "statusBar.foreground": "#15202b", 13 | "statusBarItem.hoverBackground": "#e32cb4", 14 | "statusBarItem.remoteBackground": "#e959c4", 15 | "statusBarItem.remoteForeground": "#15202b", 16 | "titleBar.activeBackground": "#e959c4", 17 | "titleBar.activeForeground": "#15202b", 18 | "titleBar.inactiveBackground": "#e959c499", 19 | "titleBar.inactiveForeground": "#15202b99" 20 | }, 21 | "peacock.color": "#e959c4" 22 | } -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | Gmail. 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series 86 | of actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or 93 | permanent ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within 113 | the community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.0, available at 119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 120 | 121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 122 | enforcement ladder](https://github.com/mozilla/diversity). 123 | 124 | [homepage]: https://www.contributor-covenant.org 125 | 126 | For answers to common questions about this code of conduct, see the FAQ at 127 | https://www.contributor-covenant.org/faq. Translations are available at 128 | https://www.contributor-covenant.org/translations. 129 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2024 Aatmaj 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 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ### KJSCE - computer Engineering 2 | Links to material, lab writeups, notes, code for KJSCE - Computer Engineering. 3 | 4 | Please dont forget to star 🌟 the repositories! 5 | 6 | 7 | #### List of repositories 8 | | Year | Link to repo | Comments | 9 | |-------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------| 10 | | First Year | [Sem I notes](https://github.com/Aatmaj-Zephyr/First-year) | Sem I notes, important questions, viva questions | 11 | | | [Python full course](https://github.com/Aatmaj-Zephyr/Learning-Python) | Learning python full blog course | 12 | | | [C and Python](https://github.com/Aatmaj-Zephyr/Solutions-to-first-year-practicals) | Programming in C and Python code and writeups | 13 | | Second Year | [ITVC and COA](https://github.com/Aatmaj-Zephyr/3rd-sem-svu) | Maths ITVC handwritten notes | 14 | | | [Data Structures](https://github.com/Aatmaj-Zephyr/Data-Structures/tree/main) | DS Lab code and writeups | 15 | | | [Second Year Experiments](https://github.com/Aatmaj-Zephyr/SecondYearExperiments) | DS, OOPM, RDMBS, Py writeups | 16 | | | [OOPM-Java](https://github.com/Aatmaj-Zephyr/Java-OOP/tree/main) | Java codes and lab writeups | 17 | | | [COA](https://github.com/Aatmaj-Zephyr/COA) | Computer Organization and Architecture writeups | 18 | | | [Scilab](https://github.com/Aatmaj-Zephyr/Scilab) | Scilab tutorials | 19 | | | [PSOT](https://github.com/Aatmaj-Zephyr/4th-sem-svu) | Probability, optimization handwritten notes | 20 | | | [AOA](https://github.com/Aatmaj-Zephyr/AOA) | Analysis of Algorithms notes and practical codes | 21 | | | [RDBMS](https://github.com/Aatmaj-Zephyr/RDBMS) | Database code and writeups | 22 | | | [WPL](https://github.com/Aatmaj-Zephyr/WPL) | Web programming code and writeups | 23 | | | [Django](https://github.com/sushantnair/Django-Tutorial) | Django code and drive notes | 24 | | | [SY Notes](https://github.com/MinavKaria/SY-Notes) | Other bunch of helpful SY Notes | 25 | | | [SY](https://github.com/Soumilgit/SY-resources) | ADS,AOA,DDL,DS,DV,ITVC,PSOT,WPL notes and writeups | 26 | | Third Year | [Operating Systems](https://github.com/Aatmaj-Zephyr/OS) | OS experiments | 27 | | | [Computer Networks](https://github.com/Aatmaj-Zephyr/Computer-networks) | CN experiments | 28 | | | [Computer Graphics](https://github.com/Aatmaj-Zephyr/ComputerGraphics) | Experiments | 29 | | | [Information security](https://github.com/Aatmaj-Zephyr/information-security) | IS handwritten notes, important questions, Lab code and writeups | 30 | | | [Artificial Intelligence](https://github.com/Aatmaj-Zephyr/AI-Notes) | AI important questions, Lab code and writeups | 31 | | | [Image processing](https://github.com/Aatmaj-Zephyr/DSIP) | DSIP handwritten notes, lab code and writeups | 32 | | | [Machine Learning](https://github.com/Aatmaj-Zephyr/Machine-Learning-Lab) | ML lab code and writeups | 33 | | Final Year | | | 34 | | | | | 35 | 36 | #### Drive Links 37 | 38 | Please access them from Somaiya Mail ID from desktop. 39 | 40 | 1) Links to past year papers - https://drive.google.com/drive/folders/1RNFaYqhC2TZiy3xr0IBFxQ6YlD5DJD_7?usp=sharing 41 | 2) Link to extra past year papers and solutions - https://drive.google.com/drive/folders/18fNsY9SdEaULGZBf8fGARAhjG7nKP8rs?usp=sharing 42 | 3) Link to AOA lab writeups and C++ code. 43 | https://drive.google.com/drive/folders/1aZdEPVMzT7xFUQlF3hUJbR86C7Yo0Sta 44 | 45 | ______ 46 | 47 | ### Special thanks to: 48 | 49 | 50 | 51 | 52 | 53 | ______ 54 | 55 | 56 | ## 🤝 Help to Grow the Community. 57 | 58 | Have something useful to share? Please make a pull request. Also please read the [contributing guidelines](https://github.com/Aatmaj-Zephyr/KJSCE-CE/blob/main/contributing.md). 59 | 60 | 61 | ______ 62 | 63 | 64 | > Disclaimer: This repository is made by students for students. You can use the material only for your own education. This material is not intended for copy-pasting code or writeups. 65 | 66 | > Please remember that this repository is for helping students and not encouraging in any malpractises. Anti-plagarism measures taken by the college will detect this code and strict action will be taken against you, hence refrain from copying any part of this material. Please do not use this repository to just copy paste the code or the solutions. Try to understand this on your own and then try it out. For any doubts, please raise an issue on the respective repository for seeking help. 67 | 68 | -------------------------------------------------------------------------------- /contributing.md: -------------------------------------------------------------------------------- 1 | ### How to contribute? 2 | 3 | #### Github Repository 4 | 1) Make a Github repository with relevant code 5 | 2) Add License to the repository 6 | 3) Add contributing guidelines 7 | 4) Make a pull request to this repository 8 | 5) Add the link to your repo, and comments in the table 9 | 6) Wait for the reviewers to review and merge your PR 10 | 11 | #### Drive link 12 | 1) Make sure that your drive link is accessible by everyone via Somaiya Mail ID 13 | 2) Add the link to drive link section of this repository and make a pull request 14 | 3) Wait for the reviewers to review and merge your PR --------------------------------------------------------------------------------