JWOC provides a fully immersive learning experience for students and first-time contributors by promoting the wonders of open-source software and crafting a community of new and experienced technical developers. The best projects are selected for this program. Students get acquainted with the projects from the mentors during the Community Bonding Period. Students work on these projects during the coding phase. At the end of the coding period, the winners of the programs are announced on the basis of their contribution in terms of quantity as well as quality.
Report Bug · Request Extension
(Bottom)
In our day-to-day lives, we use Chrome Extensions frequently, such as Grammarly. Similarly, I will add some extensions and along with them give some ideas of extensions that can be implemented. What if we built an extension to make life easier? It would be much more exciting. so,It doesn't matter what level of learning you have, you can always contribute to this project and build your own extensions!
Here's an example of what a Chrome Extension usually looks like:
(Image taken from Chrome's extension library as an example.)
Read this documentation it has all the steps.
We would ❤️ for you to contribute to Chrome-Extension and help make it better by adding your ideas or by making current one better! We want contributing to be fun, enjoyable, and educational for everyone. All contributions are welcome, including issues as well as updates.
If you have a idea of any Chrome-Extension you want to build just open an appropriate issue regarding this, we will discuss and assign you that issue. In case you are confused and have queries, just ping me, will help you get along and build!
Branch naming convention is as following
TYPE-ISSUE_ID-DESCRIPTION
When TYPE can be:
- feat - is a new chrome-extension
- doc - documentation only changes
- fix - a bug fix/improving current extension or UI enhancement
All PRs must include a commit message with the changes description!
For the initial start, fork the project and use git clone command to download the repository to your computer
git pull, before creating a new branch, pull the changes from upstream. Your master needs to be up to date.
$ git pull
- Create new branch from
master
$ git checkout -b [name_of_your_new_branch]
- Work - commit - repeat ( be sure to be in your branch )
- Push changes to GitHub
$ git push origin [name_of_your_new_branch]
-
Submit your changes for review If you go to your repository on GitHub, you'll see a
Compare & pull requestbutton. Click on that button. -
Start a Pull Request Now submit the pull request and click on
Create pull request. -
Get a code review approval/reject
-
After approval, merge your PR
-
GitHub will automatically delete the branch after the merge is done. (they can still be restored).
-
Yey! you made it! 🎊
Thanks to all the people who have contributed 💜
To maintain a safe and inclusive space for everyone to learn and grow, contributors are advised to follow the Code of Conduct.
If you have any feedback or suggestions please reach out to Project - Maintainer.
Or you can create a issue and mention there , which new features or extension can make this Project more good.