├── .gitignore
├── README.md
├── app
├── (dashboard)
│ ├── issues
│ │ └── page.tsx
│ ├── layout.tsx
│ ├── organizations
│ │ ├── [org]
│ │ │ └── page.tsx
│ │ └── page.tsx
│ ├── roadmap
│ │ └── page.tsx
│ └── starred
│ │ └── page.tsx
├── (root)
│ ├── layout.tsx
│ └── page.tsx
├── api
│ ├── all-years
│ │ └── route.ts
│ ├── one-org-data
│ │ └── route.ts
│ └── orgs-data
│ │ └── route.ts
└── favicon.ico
├── components.json
├── components
├── Loader.tsx
├── auth
│ └── LoginWithGithub.tsx
├── main
│ ├── Footer.tsx
│ ├── GsocGuide.tsx
│ ├── Navbar.tsx
│ ├── OrganizationCard.tsx
│ └── Pagination.tsx
└── ui
│ ├── Gallery
│ ├── Gallery.tsx
│ └── index.ts
│ ├── aurora-text.tsx
│ ├── blur-fade.tsx
│ ├── line-shadow-text.tsx
│ ├── select.tsx
│ └── shine-border.tsx
├── db
├── Connect.ts
└── db.ts
├── eslint.config.mjs
├── fonts
└── font.ts
├── hooks
└── use-mobile.tsx
├── lib
└── utils.ts
├── models
├── starred.model.ts
└── user.model.ts
├── next.config.ts
├── package.json
├── pnpm-lock.yaml
├── postcss.config.mjs
├── public
├── combined_projects.json
├── gsoc-orgs-with-years-git - Copy.csv
├── gsoc-orgs-with-years-git01.csv
├── gsoc-orgs-with-years.csv
├── gsoc-orgs.csv
├── gsoc-projects-with-years.csv
├── gsoc_orgs_json
│ ├── 2016.json
│ ├── 2017.json
│ ├── 2018.json
│ ├── 2019.json
│ ├── 2020.json
│ ├── 2021.json
│ ├── 2022.json
│ ├── 2023.json
│ └── 2024.json
├── image.png
└── updated_gsoc.csv
├── styles
└── globals.css
├── tailwind.config.ts
├── tsconfig.json
└── utils
├── cn.ts
└── technologies.ts
/.gitignore:
--------------------------------------------------------------------------------
1 | # See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
2 |
3 | # dependencies
4 | /node_modules
5 | /.pnp
6 | .pnp.*
7 | .yarn/*
8 | !.yarn/patches
9 | !.yarn/plugins
10 | !.yarn/releases
11 | !.yarn/versions
12 |
13 | # testing
14 | /coverage
15 |
16 | # next.js
17 | /.next/
18 | /out/
19 |
20 | # production
21 | /build
22 |
23 | # misc
24 | .DS_Store
25 | *.pem
26 |
27 | # debug
28 | npm-debug.log*
29 | yarn-debug.log*
30 | yarn-error.log*
31 | .pnpm-debug.log*
32 |
33 | # env files (can opt-in for committing if needed)
34 | .env*
35 |
36 | # vercel
37 | .vercel
38 |
39 | # typescript
40 | *.tsbuildinfo
41 | next-env.d.ts
42 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # HackToGSoC Organizations Dashboard
2 |
3 | Welcome to the HackToGSoC Organizations Dashboard! This platform showcases organizations participating in HackToGSoC.
4 |
5 | ## Features
6 | - **List of Organizations**: Browse through various organizations involved in the event.
7 | - **Contribution Guidelines**: Get the organization's guidelines for contributing to their open-source projects.
8 | - **Repositories**: Access a list of repositories available for contributions.
9 |
10 | ## How to Contribute
11 | 1. Browse the list of organizations.
12 | 2. Check their repositories and guidelines.
13 | 3. Fork, contribute, and make a pull request to participate in HackToGSoC!
14 |
15 | For more details, visit the [HackToGSoC website](https://hacktogsoc.vercel.app/organizations).
16 |
--------------------------------------------------------------------------------
/app/(dashboard)/issues/page.tsx:
--------------------------------------------------------------------------------
1 | import React from 'react'
2 |
3 |
4 |
5 | const page = () => {
6 | return (
7 |
9 | Under Development....
10 |
11 |
Loading...
53 | ) : ( 54 |{description}
55 | )} 56 |~ {project.student_name}
75 |{project.short_description}
76 |
164 | Find the best{" "}
165 |
53 | No organizations starred yet. 54 |
55 | )} 56 |Login with github
8 |83 | The source code of the software is freely accessible. This allows anyone to inspect how the software works, modify it to suit their needs, and share those modifications with others. 84 |
85 |87 | Open source software is typically distributed under licenses that comply with the Open Source Definition. These licenses grant users the rights to use, modify, and distribute the software. 88 |
89 | 94 |100 | The main philosophy of open-source products is the freedom to think, create, learn, and share. It is a collaborative effort of many developers who are working together to create something amazing. In the early phases of technology, open source helps the technology to not become handicapped by some big entities and is developed by people who really have the passion to make that piece of technology better. 101 |
102 |111 | Proficiency in at least one programming language. The language will depend on the project you want to contribute to (e.g., Python for Python projects, JavaScript for web projects). 112 |
113 |115 | Familiarity with Git and GitHub (or GitLab, Bitbucket) for version control and collaboration. 116 |
117 |clone
, commit
, push
, pull
, branch
, merge
. Understand how to fork a repository and create pull requests.
121 | 135 | Ability to set up a development environment on your local machine. This includes installing necessary software, libraries, and tools. 136 |
158 | Communicating through Emails, Slack and other methods is a huge part in getting yourself recognised and being efficient in contributing to the project. 159 | It is also a huge learning oppurtunity if you are able to work in someone with way more experience with professional programming and universal code ethics. 160 |
161 |feature/add-user-authentication
feature/update-dashboard-ui
bugfix/fix-login-issue
bugfix/correct-calculation-error
improvement/refactor-user-service
improvement/optimize-db-queries
hotfix/patch-security-vulnerability
hotfix/update-dependencies
262 | Proper code formatting and linting practices help maintain code quality, readability, and consistency across projects. 263 |
264 |265 | Some points to remember for good code consistency and quality: 266 |
267 | 268 |pylint
for Python, eslint
for JavaScript.black
for Python, prettier
for JavaScript.344 | By following these guidelines, you can maintain clean, readable code that enhances collaboration and reduces maintenance overhead in your projects. 345 |
346 |350 | Understanding the documentation of Google Summer of Code (GSoC) projects and effectively navigating large codebases are essential skills for successful contributions. 351 |
352 |400 | By following these guidelines, you can effectively read and navigate the documentation of GSoC projects and handle large codebases to make meaningful contributions during your GSoC journey. 401 |
402 |406 | Identifying a project to contribute to is a crucial step in your open source journey. Here are some effective methods to find a project that aligns with your interests: 407 |
408 | 409 |#project-ideas
channel of the server.
583 | #project-ideas
to promote contribution on your own project or to propose a project idea to server members.
594 | And Thats it for this Roadmap, Routine improvements will be made to this notebook and contributions to this roadmap are also welcome.
684 |{item["Description"]}
86 |Years: {item["years"]}
87 |Topics: {item["Topics"]}
101 |