Here's some info to get you started:

Google Developer Student Club is a university-based, community group for students who are interested in technology, especially technology from Google.

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

• If you have suggestions for adding or removing projects, feel free to open an issue to discuss it, or directly create a pull request after you edit the README.md file with necessary changes.
• Please make sure you check your spelling and grammar.
• Create individual PR for each suggestion. Please also read through the Code Of Conduct before posting your first idea as well.

There are many great reasons to contribute to open source projects:

• It builds your resume by demonstrating that you can collaborate with others on code.
• It gives you practice with Git and GitHub, which is a valuable computer science skill.
• It helps you to build relationships in the open source community.
• It feels good to give back to a project that you use!

• You can contribute to a library you currently use, because you will already understand the purpose of the library and you will be invested in making it better. You can contribute to python libraries like scikit-learn or scipy or pytorch etc or javascript libraries like react or nodejs or polymer etc.
• You can contribute by creating your own packages, libraries and projects for the world to use.
• You can choose from a variety of ongoing projects in our organisation to contribute to according to your choise of feild. We have ongoing projects in feilds like Web Development, Artificial Intelligence, Machine Learning, Game Development, Android Developemnt, Competitive Programming and many other to come.

If you are new to this, start by contributing to the project documentation, since it doesn't require writing any code. Start by finding a typo or a broken link to fix. Since this should be a simple fix, you will be able to focus on learning the contribution workflow.

If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow. A fork is a new repository that shares code and visibility settings with the original “upstream” repository. Forks are often used to iterate on ideas or changes before they are proposed back to the upstream repository, such as in open source projects or when a user does not have write access to the upstream repository.

This is a simple workflow of how contributing to a repo works:

• Create your Project Branch (git checkout -b Project/AmazingProject)
• Commit your Changes (git commit -m 'Add some AmazingProject')
• Push to the Branch (git push origin Project/AmazingProject)
• Open a Pull Request

Please read through How to fork a repo documentation for proper step by step guides on how to fork a repository.

At last, if you like the organisation, connect with us by following us, our members and the contributors.

Star the repositories you like, become a watcher or even better, go and contribute!