├── assets ├── Champion Badge.png ├── Conqurer Badge.png ├── Explorer Badge.png ├── Legend Badge.png ├── Adventurer Badge.png ├── Innovator Badge.png ├── Summit Seeker Badge.png ├── Trailblazer Badge.png └── readme.md ├── LICENSE ├── gssoc-guidelines ├── Repos & Restrictions.md ├── Guidelines Summary.md └── readme.md └── README.md /assets/Champion Badge.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FarhaKousar1601/Contributor/main/assets/Champion Badge.png -------------------------------------------------------------------------------- /assets/Conqurer Badge.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FarhaKousar1601/Contributor/main/assets/Conqurer Badge.png -------------------------------------------------------------------------------- /assets/Explorer Badge.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FarhaKousar1601/Contributor/main/assets/Explorer Badge.png -------------------------------------------------------------------------------- /assets/Legend Badge.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FarhaKousar1601/Contributor/main/assets/Legend Badge.png -------------------------------------------------------------------------------- /assets/Adventurer Badge.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FarhaKousar1601/Contributor/main/assets/Adventurer Badge.png -------------------------------------------------------------------------------- /assets/Innovator Badge.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FarhaKousar1601/Contributor/main/assets/Innovator Badge.png -------------------------------------------------------------------------------- /assets/Summit Seeker Badge.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FarhaKousar1601/Contributor/main/assets/Summit Seeker Badge.png -------------------------------------------------------------------------------- /assets/Trailblazer Badge.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FarhaKousar1601/Contributor/main/assets/Trailblazer Badge.png -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2024 GSSoC24 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 | -------------------------------------------------------------------------------- /gssoc-guidelines/Repos & Restrictions.md: -------------------------------------------------------------------------------- 1 | # Contribution Guidelines 2 | 3 | We value the quality of contributions to our open source projects and want to maintain a fair and productive environment for all contributors. To ensure this, we have established some guidelines to prevent spamming and misuse of our scoring system. 4 | 5 | ## Important Notice 6 | 7 | **Contributors should not be awarded more than 150 points for contributions to the following repositories:** 8 | 9 | [`machine-learning-repos`](https://github.com/Recode-Hive/machine-learning-repos) 10 | [`GGExtensions`](https://github.com/Sulagna-Dutta-Roy/GGExtensions) 11 | [`GameZone`](https://github.com/kunjgit/GameZone) 12 | [`codeharborhub.github.io`](https://github.com/CodeHarborHub/codeharborhub.github.io) 13 | [`ResourceHub`](https://github.com/jfmartinz/ResourceHub) 14 | [`HelpOps-Hub`](https://github.com/mdazfar2/HelpOps-Hub) 15 | [`BloxAI`](https://github.com/subhadeeproy3902/BloxAI)
16 | 17 | (More repositories will be added as identified) 18 | 19 | ## Detailed Guidelines 20 | 21 | ### Point Limit 22 | 23 | - A single contributor can earn a maximum of 150 points for contributions to the repositories listed above. 24 | - Contributions exceeding 150 points in these repositories will result in a reduction of the contributor's level. 25 | 26 | ### Contribution Quality 27 | 28 | - Contributions should be meaningful and add value to the project. 29 | - Simple additions, such as downloading a Python file from ChatGPT and uploading it, do not qualify as valuable contributions. 30 | 31 | ### Repository Structure 32 | 33 | - Avoid creating a folder structure where different programs are added to sub-folders unless it significantly improves the project. 34 | - Contributions should not be purely structural or organizational without substantial code changes or enhancements. 35 | 36 | ### Misuse Prevention 37 | 38 | - We have noticed some contributors misusing the system to climb the leaderboard. Such activities are discouraged and will be monitored. 39 | - Contributors found spamming or adding low-quality contributions will have their points reviewed and potentially reduced. 40 | 41 | ### Reporting Issues 42 | 43 | - If you observe any contributor misusing the system, please report it via comments or other provided reporting mechanisms. 44 | - All feedback on potential misuse is appreciated and will be investigated thoroughly. 45 | 46 | ### Legitimate Contributions 47 | 48 | - Contributions involving significant code changes, deployment, technical issue resolution, or feature additions will be considered for higher levels. 49 | - Ensure that your contributions are in line with the project's goals and add real value to the open source community. 50 | 51 | ## Examples of Quality Contributions 52 | 53 | - Creating a deployment script that automates the project setup. 54 | - Adding a search feature that enhances the functionality of the repository. 55 | - Resolving technical issues that improve the overall stability and performance of the project. 56 | 57 | ## Conclusion 58 | 59 | These guidelines aim to maintain the integrity and quality of our open source projects. We encourage everyone to contribute meaningfully and help us create a productive and fair environment for all contributors. 60 | 61 | Thank you for your cooperation and understanding. 62 | 63 | For more information, please refer to our detailed video explanation [here](https://www.loom.com/share/8f2c5e1f15694c88b3b15f48da600e80?sid=fa8f79a3-21ff-4776-84a0-48952a7601f5) 64 | -------------------------------------------------------------------------------- /gssoc-guidelines/Guidelines Summary.md: -------------------------------------------------------------------------------- 1 | # Contribution Guidelines 2 | 3 | If you reach the top of the leaderboard with small code snippets, repeated copy-paste PRs, or spam PRs, you will only be at the top temporarily as we do manual checks on suspicious contributions. We do manual checks on the leaderboard for most of the leaderboard contributions. This is because we promised to give Job Fair and other perks to genuine contributors which include web3 conf tickets as well. Additionally, we assured our partner companies that we would recommend good and skilled contributors. 4 | 5 | Therefore, we remove all spam and unnecessary PRs. During this process, our team will verify all your PRs. Do not repeatedly address similar issues. You need to build your GitHub profile with meaningful badges and PRs. In the future, if you apply to any company, they will primarily check your GitHub profile. If they see your badges, they will get a good impression of you and ideally they will check your merged PRs. They will only consider you if they are meaningful. If you have spam PRs, they won't consider you. 6 | 7 | If all of your contributions are meaningful to the projects, we have the potential to increase perks and opportunities including from the existing project admins. We are adding a few rules to reduce spam PRs. We have defined meaningful PRs below. Please follow them. 8 | 9 | ## Table of Contents 10 | 11 | - [Instructions for Everyone (Mentors, Project Admins, Contributors)](#instructions-for-everyone-mentors-project-admins-contributors) 12 | - [Note: Meaningful contribution means](#note-meaningful-contribution-means) 13 | 1. [Beginners and Documentation Contributions](#beginners-and-documentation-contributions) 14 | 2. [PR Responsibilities](#pr-responsibilities) 15 | 3. [Document Change Issues](#document-change-issues) 16 | 4. [Issue Assignment](#issue-assignment) 17 | 5. [Role Participation](#role-participation) 18 | 6. [Inactive Repos](#inactive-repos) 19 | 7. [Meaningful Coding Contributions](#meaningful-coding-contributions) 20 | 8. [Issue Duplication](#issue-duplication) 21 | 9. [GitHub Repo-related PRs](#github-repo-related-prs) 22 | 10. [README Updates](#readme-updates) 23 | 11. [Migration Code](#migration-code) 24 | 25 | ## Instructions for Everyone (Mentors, Project Admins, Contributors) 26 | 27 | ### Note: Meaningful contribution means 28 | 29 | 1. **Beginners and Documentation Contributions:** 30 | - If you are a beginner or lack experience with README files, workflows, or documentation, you can contribute to those types of issues. 31 | 32 | 2. **PR Responsibilities:** 33 | - If you create a PR for a README, workflow, or document-related issue, it is your responsibility to make future PRs on the README or workflow for free, with no level or GSSoC label. Currently, we assign level 1 to these types of issues. If you contribute without a label, we will evaluate the changes and potentially upgrade your PR to level 2 or level 3 based on the completeness of the README, workflow, or document changes. 34 | 35 | 3. **Document Change Issues:** 36 | - PAs or Mentors, please don't create multiple document change issues. Instead, inform the contributor who worked on the documentation if possible. 37 | 38 | 4. **Issue Assignment:** 39 | - PAs or Mentors, please follow a first-come, first-served approach. We found that some repos assign issues with partiality. If an issue is created by someone, ask the creator, "Do you want to work on it or is it open to all?" If they want to work on it, assign it to them; if not, make it an open issue and assign it on a first-come, first-served basis. 40 | 41 | 5. **Role Participation:** 42 | - Everyone, please ensure you can participate in only one role as a PA, Mentor, or Contributor. Not multiple roles. If we find someone with multiple roles, severe action will be taken because we have mentioned this point from the beginning of the program. 43 | 44 | 6. **Inactive Repos:** 45 | - PAs or Mentors, if any repo is inactive for more than 2 weeks, we will remove that project. 46 | 47 | 7. **Meaningful Coding Contributions:** 48 | - Contributors, make sure that if you are a coder, you contribute to meaningful coding issues, spamming won't help in any way, and we have a strict team this time to check it this year. 49 | 50 | 8. **Issue Duplication:** 51 | - Contributors, before raising an issue, please check if it has already been raised. If it has not been raised, then create the issue. 52 | 53 | 9. **GitHub Repo-related PRs:** 54 | - All GitHub repo-related PRs won't be recreated. GitHub repo-related PRs include documentation, bots, workflows, templates, etc. If you are assigned one issue related to this point, then you have complete responsibility for that issue in the future. You need to create unlabelled PRs for those future updates. Opensource is not just about the leaderboard and points. 55 | 56 | 10. **README Updates:** 57 | - Contributors, if your code change may affect the repo's functionality but the code is important, then update the README in your PR. 58 | 59 | 11. **Migration Code:** 60 | - If you are working on migration code, create PRs and issues based on the difficulty of the complete migration work. Discuss with mentors or PAs and create the issue accordingly. 61 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ### 2 | [Pallabi](https://github.com/pallabisneha) 3 | ## For Contributors 4 | 5 | GSSoC is a 3-month long #OpenSource program by GirlScript Foundation, India.
6 | This is Contributor Space where all the relevant link regarding your doubts. 7 | #### Make sure you star the repository before forking this is the way to show 💖 to the owner of the repository. 8 | 9 | - If you have questions ask here -> :https://github.com/GSSoC24/Contributor/discussions 10 | - Mentor Assigned to the Project List: https://bit.ly/3UVRkgM 11 | - Regarding Certificate after participation: https://github.com/GSSoC24/Contributor/discussions/33 12 | - If you haven't received the Confirmation Mail: https://github.com/GSSoC24/Contributor/discussions/96 13 | - How to contribute: https://github.com/GSSoC24/Contributor/discussions/34. 14 | - How to start with GitHub https://recodehive.com/github-tutorials/ 15 | - blog to read https://gssoc.girlscript.tech/blog 16 | - Removed Projects: https://docs.google.com/spreadsheets/d/1lcbwU8sfrc-tUOe3spcLMb2uW2W8joGI6BM-ZetDehY/edit?usp=sharing 17 | - Selected Active Projects: https://docs.google.com/spreadsheets/d/1owUjczBew3FgLWqW73ND96raatUCkJZtytjjZBlK7cI/edit?usp=sharing 18 | 19 | Issue will be assigned to Only 1 person ...FCFS basis. Others get a chance if the issue gets stale & the assignee is inactive for 5+ days 20 | 21 | ## How to Start Contributing: 22 | 23 | 🌟 How to Contribute to GSSoC Projects: A Step-by-Step Guide 🌟 24 | 25 | Must watch the youtube link on Guidelines: https://youtu.be/Y9PYaPZgikg
26 | ![Sanjay Viswanathan Event](https://github.com/GSSoC24/Contributor/assets/30715153/77414867-2ffa-4a82-ba9a-d5a11a8334ea) 27 | 28 | A: Choosing Projects 29 | 30 | 1️⃣ 🌐Visit the GSSoC Website: Head to the official GSSoC website and navigate to the projects section. [Here](https://gssoc.girlscript.tech/project) 31 | 32 | 2️⃣ 📂Find Your Match 33 | 34 | 3️⃣ 🔎Get Project Details: Click on the project to view its details, including a video overview and the GitHub repository link. 35 | 36 | 37 | 38 | ## Getting Started with Contribution 39 | 40 | 🛠️B1: Setting Up The Project 41 | 42 | 1️⃣ 🍴Fork It: Fork the project to create your own copy. 43 | 44 | 2️⃣ 💻Clone Locally: Open Git Bash in your desired folder and clone your forked copy. 45 | 46 | ```bash 47 | $ git clone https://github.com//.git 48 | ``` 49 | 3️⃣ 📂Navigate: Move into the project folder. 50 | 51 | ```bash 52 | $ cd 53 | 54 | ``` 55 | 56 | 4️⃣ 🔗Add Upstream: Link to the original repository. 57 | 58 | ```bash 59 | $ git remote add upstream https://github.com//.git 60 | ``` 61 | 62 | 5️⃣ 👀Check Remotes: Verify the remote connections. 63 | 64 | ```bash 65 | $ git remote -v 66 | ``` 67 | 6️⃣ ⬇️Stay Updated: Keep your main branch in sync with the original repository. 68 | 69 | ```bash 70 | $ git pull upstream main 71 | ``` 72 | 73 | ## Contributing To The Project 74 | 75 | 1️⃣ 🌿Branch Out: Create a new branch with a meaningful name. 76 | 77 | ```bash 78 | $ git checkout -b 79 | ``` 80 | 2️⃣ ✍️Make Changes: Work your magic on the codebase. 81 | 82 | 3️⃣ 📁Track Changes: Add your modifications. 83 | 84 | ```bash 85 | $ git add . 86 | ``` 87 | 4️⃣ 🚚Commit: Commit your changes with a descriptive message. 88 | 89 | ```bash 90 | $ git commit -m "" 91 | ``` 92 | 5️⃣ 🚀Push Changes: Push your changes to your forked repository. 93 | 94 | ```bash 95 | $ git push -u origin 96 | ``` 97 | 6️⃣ 🌐Create Pull Request: Head to GitHub, navigate to your forked repo, and initiate a pull request by clicking "Compare and pull request". 98 | 99 | 🚀 Contribute, and let's make a difference together in the open-source community! Happy coding! 🎉 100 | 101 | For more details, check out the guide [here](https://sukritim.hashnode.dev/a-beginners-guide-to-gssoc#heading-what-is-open-source-contribution). 102 | 103 | Hope it helps you please mark it as answer if it solves your query. 104 | 105 | ## Common FAQ 106 | - What all label we should check? 107 |
Ans: Make sure you check the labels gssoc, level1,level2,level3 on issues. 108 | 109 | This is how it should look like, 110 | 111 | ![WhatsApp Image 2024-05-11 at 15 56 22_92229ded](https://github.com/GSSoC24/Contributor/assets/30715153/ffe6208f-21f9-4262-808e-31f3b2bc0a07) 112 | 113 | - what are the points distribution this time for PR's ? 114 |
Ans: 115 | - Level1: 10 points 116 | - Level2: 25 points 117 | - Level3: 45 points 118 | - Levels are classified by difficulty level which is calculated by core team. Also labels will be mentioned on each review 119 | And Leaderboard will update twice a day automatically 120 | 121 | Note: Leaderboard will take 1 or 2 days after May 10 to update , afterwards you can see updates daily. 122 | 123 | - how many PRs should be merged in to maintain positions on the leaderboard? 124 | - Ans: its not above PR, the best way to maintain position on leaderboard is contribute to high difficult issue raised by maintainer. 125 | As mentioned above Level 1, level 2, level 3 helps them to maintain their position rather pushing many PR as the score is high for levels 126 | -------------------------------------------------------------------------------- /gssoc-guidelines/readme.md: -------------------------------------------------------------------------------- 1 | # GSSoC Contribution Guidelines :octocat: 2 | 3 | Hello contributors, we hope all are doing great! :octocat: 4 | 5 | This year is very special compared to previous years because we have more than 27k contributors from various countries and the highest PR requests compared to all other GSSoC events and ofcourse we rank top on spamming contributions as well. 😅
6 | [`How to do first contribution`](https://github.com/GSSoC24/Contributor/discussions/175) 7 | [`How to get GitHub Achievement badge`](https://github.com/GSSoC24/Contributor/discussions/11) 8 | [`Leaderboard updates`](https://github.com/GSSoC24/Contributor/discussions/288)
9 | [`GSSOC Certification for contributors`](https://github.com/GSSoC24/Contributor/discussions/33) 10 | 11 | ![image](https://github.com/GSSoC24/Contributor/assets/30715153/9f7c800e-f28c-4916-919c-cf082d4552fc) 12 | 13 | --- 14 | 15 | ## Table of Contents 16 | - [Introduction](#introduction) 17 | - [Important Points for Contributors](#important-points-for-contributors) 18 | - [Meaningful Contribution Guidelines](#meaningful-contribution-guidelines) 19 | - [Instructions for Mentors and Project Admins (PAs)](#instructions-for-mentors-and-project-admins-pas) 20 | - [Report Issues to Us](#report-issues-to-us) 21 | - [How to Detect Spam Contributions](#how-to-detect-spams-and-fake-contributions) 22 | - [Why We Enforce These Rules](#why-we-enforce-these-rules) 23 | - [Flagged Projects and PRs](#flagged-projects-and-prs) 24 | - [Final Notes](#final-notes) 25 | 26 | --- 27 | 28 | ## Introduction 29 | 30 | We've noticed a rise in the number of cases where contributors gain high points for submissions that are not actual contributions. 31 | 32 | Every contributor should remember one thing: Labels on PRs are a must have `gssoc`, `level1` or `level2` or `level3`. 33 | - `level1`: 10 points 34 | - `level2`: 25 points 35 | - `level3`: 45 points 36 | 37 | If you reach the top of the leaderboard with small code snippets, repeated copy-paste PRs, or spam PRs, you will be temporarily banned until we perform manual checks on suspicious contributions and reduce score on leaderboard. 38 | 39 | --- 40 | 41 | ## Important Points for Contributors 42 | 43 | - **Meaningful Contributions**: Build your GitHub profile with meaningful badges and PRs. 44 | - **Manual Verification**: Our team will verify most of your PR, espescially people on the top of leaderboard. 45 | - **Avoid Spam**: Do not submit spam PRs or address similar issues repeatedly. 46 | - **GitHub Profile**: If all of your contributions are meaningful to the projects, we have the potential to increase perks and opportunities including from the existing project admins. 47 | 48 | --- 49 | 50 | ## Meaningful Contribution Guidelines 51 | 52 | - Beginners can contribute to README files, workflows, or documentation. 53 | - PRs for README, workflow, or documentation will be evaluated and potentially upgraded based on completeness. 54 | - Do not create multiple document change issues. Inform the contributor who worked on the documentation for future updates. 55 | - Follow a first-come, first-served approach for issues. 56 | - Participate in only one role: PA, Mentor, or Contributor. 57 | - Inactive projects for more than 2 weeks will be removed. 58 | 59 | --- 60 | 61 | ## Instructions for Mentors and Project Admins (PAs) 62 | 63 | - **Fair Issue Assignment**: Follow a first-come, first-served approach. 64 | - **Avoid Partiality**: Ensure fair assignment of issues, dont let PR without raising issues. 65 | - **Single Role Participation**: PAs and Mentors should not contribute to the same projects to avoid conflict of interest. 66 | - **Inactive Projects**: Projects inactive for more than 2 weeks will be removed. 67 | 68 | --- 69 | 70 | ## Report issues to us 71 | 72 | - **Minimal Changes**: PRs with minimal changes that are not impactful and getting level 2 and level 3. 73 | - **Multiple Roles**: Contributors acting as PAs or Mentors. 74 | - **Instant PR Acceptance**: PRs accepted instantly without proper review. 75 | 76 | ### Report Suspicious Activity 77 | 78 | - **Raise Discussion for it with PR links**: https://github.com/GSSoC24/Contributor/discussions/categories/q-a 79 | 80 | ### Non-Considerable PRs 81 | 82 | - Multiple documentation or workflow issues. 83 | - Exploiting personal connections with PAs or Mentors. 84 | - Repeated documentation or workflow contributions beyond 200 points. 85 | - Code snippets or template-related PRs. 86 | 87 | --- 88 | 89 | 90 | ## HOW TO DETECT SPAMS AND FAKE CONTRIBUTIONS 91 | 92 | ## An example of this can be - 🔢 93 | 94 | 1. Gaining high rep points for submission such as changing -> README.MD to README.md and getting levels for it. 95 | ![image](https://github.com/GSSoC24/Contributor/assets/30715153/0e8d778d-aae4-412f-be8c-85ef5ad78cc2) 96 | 97 | 2. Contributing to the same project but each PR is having very minimal changes. This could either be changing a line of code (without actually being Impactful) or changes that are not necessary in the first place. This doesn't have to be strictly in any one project or code, line except for a typo. 98 | ![image](https://github.com/GSSoC24/Contributor/assets/30715153/1b11fdcd-6119-4f73-8faa-256883359bea) 99 | 100 | 3. Contributors are being PA as well for some projects. This is where contributors ask PA to give high levels for very basic changes which is not actually right. 101 | 102 | 4. PA favoring one contributor - This includes assigning level3 for most of the PR, merging PR without review, and no respective issue. 103 | ![image](https://github.com/GSSoC24/Contributor/assets/30715153/72203ff1-517e-46fc-b068-ba0dcd647e75)[Link to PR code](https://github.com/SyedImtiyaz-1/GetTechProjects/pull/345/files) 104 | 105 | 5. We mentioned PAs not to give more than 150 points for below mentioned projects as they are spamming if more than 150 points found in such repo by single contributor level comes down. 106 | Click here for more information: [Watch the video Explanation](https://www.loom.com/share/8f2c5e1f15694c88b3b15f48da600e80?sid=fa8f79a3-21ff-4776-84a0-48952a7601f5) 107 | 108 | [`machine-learning-repos`](https://github.com/Recode-Hive/machine-learning-repos) 109 | [`GGExtensions`](https://github.com/Sulagna-Dutta-Roy/GGExtensions) 110 | [`GameZone`](https://github.com/kunjgit/GameZone) 111 | [`codeharborhub.github.io`](https://github.com/CodeHarborHub/codeharborhub.github.io) 112 | [`ResourceHub`](https://github.com/jfmartinz/ResourceHub) 113 | [`HelpOps-Hub`](https://github.com/mdazfar2/HelpOps-Hub) 114 | [`BloxAI`](https://github.com/subhadeeproy3902/BloxAI) 115 | [`ML-CaPsule`](https://github.com/Niketkumardheeryan/ML-CaPsule) 116 | [`APIVerse`](https://github.com/dishamodi0910/APIVerse) 117 | [`ChromeGaming`](https://github.com/ChromeGaming) 118 | [`DL-Simplified`](https://github.com/abhisheks008/DL-Simplified) 119 | [`GetTechProjects`](https://github.com/SyedImtiyaz-1/GetTechProjects) 120 | [`CalcDiverse`](https://github.com/Rakesh9100/CalcDiverse) 121 | [`GetTechProjects`](https://github.com/SyedImtiyaz-1/GetTechProjects) 122 | [`SwapReads`](https://github.com/anuragverma108/SwapReads) 123 | [`learn-python`](https://github.com/animator/learn-python) 124 | [`awesome-open-source-flutter-apps`](https://github.com/fluttergems/awesome-open-source-flutter-apps?tab=readme-ov-file) 125 | [`ThereForYou`](https://github.com/TAHIR0110/ThereForYou)
126 | more list will be added when we find it out. 127 | 128 | --- 129 | 130 | ### Why are we doing this? - 👍 131 | 132 | This is being done keeping everyone in mind for being hardworking enough to contribute something meaningful even if it's something small. We are doing this to make this event fair and memorable for all. 133 | - Right now we noticed spamming could have happened due to a lack of written guidelines, so for those who people did it, we will be allowing 200 points to gain from merging PR with official Emails and remove other scores. 134 | - Those who do spam after publishing the guidelines, if we notice we will further level down without any notice. 135 | ### How to detect them - 💯 136 | 137 | 1. If you find anyone pushing PR with changing a single change which are not necessary in a same project and gaining high reps for it. Kindly let us know. [report here](https://github.com/GSSoC24/Contributor/discussions/categories/q-a) 138 | 2. If any PA is also accepting PR from any contributor which shouldn't be accepted in the first place or giving high reps or assigning labels that should not be given, [kindly let us know](https://github.com/GSSoC24/Contributor/discussions/categories/q-a) 139 | 4. Anyone who suspects someone who is contributing at a particular time and his/her PR instantly is getting accepted regardless of being an actual contribution, kindly let us know [report here](https://github.com/GSSoC24/Contributor/discussions/categories/q-a) 140 | 5. If anyone suspects that PA is the contributor itself or vice versa, kindly let us know @sanjay-kv 141 | 6. Even if you find anyone suspicious kindly let us know . Mail us gssoc@girlscript.tech 142 | 143 | --- 144 | 145 | ### Spam PRs or PRs Won't consider: 146 | 1. If you create multiple Issues on documentation or workflow. Your PRs won't be considered. 147 | 2. If you know the PA or mentor. If you take advantage of it to make more PRs. Your PRs won't be considered. 148 | 3. If you completely depend on documentation or workflow or GitHub bots, Only the first 150 points will be considered. Focus on a variety of contributions. 149 | 4. If you create a code snippet PR for example a PR for issue template, a PR for PR temple, etc. Your PRs won't be considered. 150 | 5. Contributors, you are free to create any number of PRs in any repos excluding few repo listed below. Sticking to a particular repo will give you a strong command of the project and the tech stack. However, if we see you spamming PRs or issues, severe action will be taken against you. 151 | samples: 152 | 153 | #### Note: We request everyone to follow the above guidelines. We aim to make open source accessible to everyone, including beginners. If you all follow the instructions, it will help us bring more perks to you. Otherwise, it will push us to verify your PRs 154 | --- 155 | 156 | ## Flagged Projects and PRs 157 | 158 | - **Unresponsive Repos**: 159 | - urstrulynishkarsh/ReactChat#125 160 | - ML-CaPsule 161 | - ALL_INDIA_HACKATHON 162 | - mystory 163 | - FoodiesWeb 164 | - [ChromeGaming/GameSphere](https://github.com/ChromeGaming/GameSphere) 165 | - FitBody 166 | - [Sahil1786/Petari](https://github.com/Sahil1786/Petari) 167 | - Eduford-University 168 | - shrawani21/gamer_21#43 169 | - Kavin56/learn-python#1 170 | - Rajan-Barnwal/jobproject#248 171 | - JiyaGupta-cs/ShopNex#307 172 | - bishalde/Shrinkk#65 173 | - bishalde/TaskMate#14 174 | - juhinagpure/Eduford-university#65 175 | - [Mayank2808sharma/IRCTC-backend](https://github.com/Mayank2808sharma/IRCTC-backend) 176 | - piug-07/blogzen-OpenSource#167 177 | - shrawani21/gamer_21#97 178 | - shrawani21/gamer_21#79 179 | - Its-Aman-Yadav/Community-Site#289 180 | 181 | --- 182 | 183 | ## Final Notes 184 | 185 | We request everyone to follow the above guidelines. Our aim is to make open source accessible to everyone, including beginners. Genuine contributions will help you build healthy relationships and secure good jobs. Let's make this year’s GSSoC one with a high number of contributors, meaningful contributions, and exciting perks. 186 | 187 | If you find someone violating these rules, please inform us. 188 | 189 | Wishing you all a happy contribution!! 👍 190 | 191 | Thanks & Regards, 192 | GSSoC Team 193 | -------------------------------------------------------------------------------- /assets/readme.md: -------------------------------------------------------------------------------- 1 | # GSSoC Contribution Guidelines :octocat: 2 | 3 | Hello contributors, we hope all are doing great! :octocat: 4 | 5 | This year is very special compared to previous years because we have more than 27k contributors from various countries and the highest PR requests compared to all other GSSoC events and ofcourse we rank top on spamming contributions as well. 😅 6 | ![image](https://github.com/GSSoC24/Contributor/assets/30715153/9f7c800e-f28c-4916-919c-cf082d4552fc) 7 | 8 | --- 9 | 10 | ## Table of Contents 11 | - [Introduction](#introduction) 12 | - [Important Points for Contributors](#important-points-for-contributors) 13 | - [Meaningful Contribution Guidelines](#meaningful-contribution-guidelines) 14 | - [Instructions for Mentors and Project Admins (PAs)](#instructions-for-mentors-and-project-admins-pas) 15 | - [Report Issues to Us](#report-issues-to-us) 16 | - [How to Detect Spam Contributions](#how-to-detect-spams-and-fake-contributions) 17 | - [Why We Enforce These Rules](#why-we-enforce-these-rules) 18 | - [Flagged Projects and PRs](#flagged-projects-and-prs) 19 | - [Final Notes](#final-notes) 20 | 21 | --- 22 | 23 | ## Introduction 24 | 25 | We've noticed a rise in the number of cases where contributors gain high points for submissions that are not actual contributions. 26 | 27 | Every contributor should remember one thing: Labels on PRs are a must have `gssoc`, `level1` or `level2` or `level3`. 28 | - `level1`: 10 points 29 | - `level2`: 25 points 30 | - `level3`: 45 points 31 | 32 | If you reach the top of the leaderboard with small code snippets, repeated copy-paste PRs, or spam PRs, you will be temporarily banned until we perform manual checks on suspicious contributions and reduce score on leaderboard. 33 | 34 | --- 35 | 36 | ## Important Points for Contributors 37 | 38 | - **Meaningful Contributions**: Build your GitHub profile with meaningful badges and PRs. 39 | - **Manual Verification**: Our team will verify most of your PR, espescially people on the top of leaderboard. 40 | - **Avoid Spam**: Do not submit spam PRs or address similar issues repeatedly. 41 | - **GitHub Profile**: If all of your contributions are meaningful to the projects, we have the potential to increase perks and opportunities including from the existing project admins. 42 | 43 | --- 44 | 45 | ## Meaningful Contribution Guidelines 46 | 47 | - Beginners can contribute to README files, workflows, or documentation. 48 | - PRs for README, workflow, or documentation will be evaluated and potentially upgraded based on completeness. 49 | - Do not create multiple document change issues. Inform the contributor who worked on the documentation for future updates. 50 | - Follow a first-come, first-served approach for issues. 51 | - Participate in only one role: PA, Mentor, or Contributor. 52 | - Inactive projects for more than 2 weeks will be removed. 53 | 54 | --- 55 | 56 | ## Instructions for Mentors and Project Admins (PAs) 57 | 58 | - **Fair Issue Assignment**: Follow a first-come, first-served approach. 59 | - **Avoid Partiality**: Ensure fair assignment of issues, dont let PR without raising issues. 60 | - **Single Role Participation**: PAs and Mentors should not contribute to the same projects to avoid conflict of interest. 61 | - **Inactive Projects**: Projects inactive for more than 2 weeks will be removed. 62 | 63 | --- 64 | 65 | ## Report issues to us 66 | 67 | - **Minimal Changes**: PRs with minimal changes that are not impactful and getting level 2 and level 3. 68 | - **Multiple Roles**: Contributors acting as PAs or Mentors. 69 | - **Instant PR Acceptance**: PRs accepted instantly without proper review. 70 | 71 | ### Report Suspicious Activity 72 | 73 | - **Raise Discussion for it with PR links**: https://github.com/GSSoC24/Contributor/discussions/categories/q-a 74 | 75 | ### Non-Considerable PRs 76 | 77 | - Multiple documentation or workflow issues. 78 | - Exploiting personal connections with PAs or Mentors. 79 | - Repeated documentation or workflow contributions beyond 200 points. 80 | - Code snippets or template-related PRs. 81 | 82 | --- 83 | 84 | 85 | ## HOW TO DETECT SPAMS AND FAKE CONTRIBUTIONS 86 | 87 | ## An example of this can be - 🔢 88 | 89 | 1. Gaining high rep points for submission such as changing -> README.MD to README.md and getting levels for it. 90 | ![image](https://github.com/GSSoC24/Contributor/assets/30715153/0e8d778d-aae4-412f-be8c-85ef5ad78cc2) 91 | 92 | 2. Contributing to the same project but each PR is having very minimal changes. This could either be changing a line of code (without actually being Impactful) or changes that are not necessary in the first place. This doesn't have to be strictly in any one project or code, line except for a typo. 93 | ![image](https://github.com/GSSoC24/Contributor/assets/30715153/1b11fdcd-6119-4f73-8faa-256883359bea) 94 | 95 | 3. Contributors are being PA as well for some projects. This is where contributors ask PA to give high levels for very basic changes which is not actually right. 96 | 97 | 4. PA favoring one contributor - This includes assigning level3 for most of the PR, merging PR without review, and no respective issue. 98 | ![image](https://github.com/GSSoC24/Contributor/assets/30715153/72203ff1-517e-46fc-b068-ba0dcd647e75)[Link to PR code](https://github.com/SyedImtiyaz-1/GetTechProjects/pull/345/files) 99 | 100 | 5. We mentioned PAs not to give more than 150 points for below mentioned projects as they are spamming if more than 150 points found in such repo by single contributor level comes down. 101 | Click here for more information: https://www.loom.com/share/8f2c5e1f15694c88b3b15f48da600e80?sid=fa8f79a3-21ff-4776-84a0-48952a7601f5 102 | 103 | [`machine-learning-repos`](https://github.com/Recode-Hive/machine-learning-repos) 104 | [`machine-learning-repos`](https://github.com/Recode-Hive/machine-learning-repos) 105 | [`machine-learning-repos`](https://github.com/Recode-Hive/machine-learning-repos) 106 | [`machine-learning-repos`](https://github.com/Recode-Hive/machine-learning-repos) 107 | [`machine-learning-repos`](https://github.com/Recode-Hive/machine-learning-repos) 108 | [`machine-learning-repos`](https://github.com/Recode-Hive/machine-learning-repos) 109 | [`machine-learning-repos`](https://github.com/Recode-Hive/machine-learning-repos) 110 | 111 | more list will be added when we find it out. 112 | 113 | --- 114 | 115 | ### Why are we doing this? - 👍 116 | 117 | This is being done keeping everyone in mind for being hardworking enough to contribute something meaningful even if it's something small. We are doing this to make this event fair and memorable for all. 118 | 119 | ### How to detect them - 💯 120 | 121 | 1. If you find anyone pushing PR with changing a single change which are not necessary in a same project and gaining high reps for it. Kindly let us know @sanjay-kv 122 | 2. If any PA is also accepting PR from any contributor which shouldn't be accepted in the first place or giving high reps or assigning labels that should not be given, kindly let us know @sanjay-kv 123 | 3. Anyone who suspects someone who is contributing at a particular time and his/her PR instantly is getting accepted regardless of being an actual contribution, kindly let us know @sanjay-kv 124 | 4. If anyone who suspects that PA is the contributor itself or vice versa, kindly let us know @sanjay-kv 125 | 5. Even if you find anyone suspicious kindly let us know @sanjay-kv 126 | 127 | --- 128 | 129 | ### Spam PRs or PRs Won't consider: 130 | 1. If you create multiple Issues on documentation or workflow. Your PRs won't be considered. 131 | 2. If you know the PA or mentor. If you take advantage of it to make more PRs. Your PRs won't be considered. 132 | 3. If you completely depend on documentation or workflow or GitHub bots, Only the first 200 points will be considered. Focus on a variety of contributions. 133 | 4. If you create a code snippet PR for example a PR for issue template, a PR for PR temple, etc. Your PRs won't be considered. 134 | 5. Contributors, you are free to create any number of PRs in any repos excluding few repo listed below. Sticking to a particular repo will give you a strong command of the project and the tech stack. However, if we see you spamming PRs or issues, severe action will be taken against you. 135 | samples: 136 | 137 | #### Note: We request everyone to follow the above guidelines. We aim to make open source accessible to everyone, including beginners. If you all follow the instructions, it will help us bring more perks to you. Otherwise, it will push us to verify your PRs 138 | --- 139 | 140 | ## Flagged Projects and PRs 141 | 142 | - **Unresponsive Repos**: 143 | - urstrulynishkarsh/ReactChat#125 144 | - ML-CaPsule 145 | - ALL_INDIA_HACKATHON 146 | - mystory 147 | - FoodiesWeb 148 | - [ChromeGaming/GameSphere](https://github.com/ChromeGaming/GameSphere) 149 | - FitBody 150 | - [Sahil1786/Petari](https://github.com/Sahil1786/Petari) 151 | - Eduford-University 152 | - shrawani21/gamer_21#43 153 | - Kavin56/learn-python#1 154 | - Rajan-Barnwal/jobproject#248 155 | - JiyaGupta-cs/ShopNex#307 156 | - bishalde/Shrinkk#65 157 | - bishalde/TaskMate#14 158 | - juhinagpure/Eduford-university#65 159 | - [Mayank2808sharma/IRCTC-backend](https://github.com/Mayank2808sharma/IRCTC-backend) 160 | - piug-07/blogzen-OpenSource#167 161 | - shrawani21/gamer_21#97 162 | - shrawani21/gamer_21#79 163 | - Its-Aman-Yadav/Community-Site#289 164 | 165 | --- 166 | 167 | ## Final Notes 168 | 169 | We request everyone to follow the above guidelines. Our aim is to make open source accessible to everyone, including beginners. Genuine contributions will help you build healthy relationships and secure good jobs. Let's make this year’s GSSoC one with a high number of contributors, meaningful contributions, and exciting perks. 170 | 171 | If you find someone violating these rules, please inform us. 172 | 173 | Wishing you all a happy contribution!! 👍 174 | 175 | Thanks & Regards, 176 | GSSoC Team 177 | 178 | ---------------------------- Detailed description below. 👇🏻 179 | 180 | 181 | --- 182 | 183 | If you reach the top of the leaderboard with small code snippets, repeated copy paste PR or spam PRs, you will only be at the top temporarily as we do manual check on suspeciosu contributions. We do manual check on the leaderboard for most of the leaderboard contributions. This is because we promised to give Job Fair and other perks to genuine contributors which include web3 conf tickets as well. Additionally, we assured our partner companies that we would recommend good and skilled contributors.
184 | 185 | Therefore, we remove all spam and unnecessary PRs. During this process, our team will verify all your PRs. Do not repeatedly address similar issues. You need to build your GitHub profile with meaningful badges and PRs. In the future, if you apply to any company, they will primarily check your GitHub profile. If they see your badges, they will get a good impression of you and ideally they will check your merged PRs. They will only consider you if they are meaningful. If you have spam PRs, they won't consider you. 186 | 187 | If all of your contributions are meaningful to the projects, we have the potential to increase perks and opportunities including from the existing project admins. We are adding a few rules to reduce spam PRs. We have defined meaningful PRs below. Please follow them. 188 | 189 | Below Instructions are for everyone(mentors, project admins, contributors) 190 | 191 | Note: Meaningful contribution means 192 | 193 | 1. If you are a beginner or if don't have any experience with README files, workflows, or documentation, you can contribute to those types of issues. 194 | 2. If you create a PR for a README, workflow, or document-related issue, it is your responsibility to make future PRs on the README or workflow for free, with no level or GSSoC label. Currently, we assign level 1 to these types of issues. If you contribute without a label, we will evaluate the changes and potentially upgrade your PR to level 2 or level 3 based on the completeness of the README, workflow, or document changes. 195 | 3. PAs or Mentors, please don't create multiple document change issues. Instead, inform the contributor who worked on the documentation if possible. 196 | 4. PAs or Mentors, please follow a first-come, first-served approach. We found that some repos assign issues with partiality. If an issue is created by someone, ask the creator, "Do you want to work on it or is it open to all?" If they want to work on it, assign it to them; if not, make it an open issue and assign it on a first-come, first-served basis. 197 | 5. Everyone, please ensure you can participate in only one role as a PA, Mentor, or Contributor. Not multiple roles. If we find someone with multiple roles, severe action will be taken because we have mentioned this point from the beginning of the program. 198 | 199 | 6. PAs or Mentors, if any repo is inactive for more than 2 weeks, we will remove that project. 200 | 7. Contributors, make sure that if you are a coder, you contribute to meaningful coding issues, spamming won't help in any way, and we have a strict team this time to check it this year. 201 | 8. Contributors, before raising an issue, please check if it has already been raised. If it has not been raised, then create the issue. 202 | 9. All GitHub repo-related PRs won't be recreated. GitHub repo-related PRs include documentation, bots, workflows, templates, etc. If you are assigned one issue related to this point, then you have complete responsibility for that issue in the future. You need to create unlabelled PRs for those future updates. Opensource is not just about the leaderboard and points. 203 | 10. Contributors, if your code change may affect the repo's functionality but the code is important, then update the README in your PR. 204 | 11. If you are working on migration code, create PRs and issues based on the difficulty of the complete migration work. Discuss with mentors or PAs and create the issue accordingly. 205 | 206 | 207 | --------------------------------------------------------------------------------