|
5 | 5 | 
|
6 | 6 | [](https://github.com/PrabhaniN/Codebadge/blob/master/LICENSE)
|
7 | 7 |
|
8 |
| -Well we all have been working in Open Source and committing various Pull requests and issues. Many a times it may happen that a mentor is unanle to manage all these activities. So This project is about tracking the contributor as well as its contribution by respective mentors. |
| 8 | +CodeBadge is a project which takes official GitHub API into consideration and makes a fading badges graph for each organization. This project would be organization-oriented project i.e. each organization will need to serve it on a reserved route, say /codebadge. For eg: If coala wants to integrate CodeBadge, they’ll serve this project on coala.io/codebadge. Our aim is to make CodeBadge as a standard such that people start using it as a measure in order to test their skill level/track their progress in a specific community. For eg, Competitive Coding guys test their skills by asking each other what’s their rank on HackerRank / HackerEarth! Likewise, open-source contributors should start asking, **Hey! What badge did you recently earned on CodeBadge!** |
| 9 | + |
| 10 | +### Why do we need CodeBadge? |
| 11 | +- To track and incorporate contributors’ progress in the community or community’s progress as a whole. Making a one-stop platform to find each contributor’s progress rather than finding it separately for each contributor. |
| 12 | +- To show the progress by awarding some really cool badges to top contributors in order to keep them connected towards the community. |
| 13 | +- Auto-assign related issues to most active contributors using tagging to keep contributors connected. |
9 | 14 |
|
10 |
| -### Features |
11 | 15 |
|
12 |
| -- Easy to monitor the activities of various contributors. |
13 |
| -- Visibility of top contributors in various projects. |
14 |
| -- Real time tracking of commits, PR's and other contributions. |
15 |
| -- Contributors list based on number of PR's, merged pulls and other activities. |
16 |
| -- Contribution history of each contributor. |
| 16 | +### Features |
17 | 17 |
|
18 |
| -The other part of this project includes the “notifying moderator” since we see sometimes that there are many PRs being sent, or issues being opened by various people across the globe but there are limited numbers of maintainers merging the PRs. This way organisations usually lose their potential contributors due to following things: |
| 18 | +- GitHub Heatmaps are for each person’s profile and can be observed from visiting each contributor’s profile specifically. Whereas, our aim is to show a complete fading graph for an organization, which would hence be capable of showing each contributor’s progress as well. |
| 19 | +- There would be some pre-built badges by us as well as we offer the organization to design their own badges. This can be done by the illustrator which we are developing for this project. |
| 20 | +- Pre-defined badges could be based on some achievement levels like Baby-Steps, Not-a-Newbie, Almost-Pro, Legendary-Committer, etc which could be awarded by setting some convention like a number of merged PRs or difficulty of issues resolved by the person. |
| 21 | +- Creating/Integrating a bot with our platform which would auto-assign/auto-suggest related issues to the top-most active contributors of the community on the basis of tagging, like what their recent PRs were based upon. |
| 22 | +- Admin Dashboard creation which would show notifications/cards for whosoever earned any new badge. Community Admins should have some extra privileges to award any extra badge to an extraordinary contributor say Committer-of-the-Month, Top-Contributor, GOAT(Greatest-of-all-Times), etc manually. |
| 23 | +- The illustrator will provide the user with an interface which will help the organization to design their own badges. It has a special feature of making a sketch outline of any image which is uploaded. Once a template is uploaded by any user it will also be available to be used by other organizations. It will also provide a feature to make a shareable interface so that more than one person of an organization can work on the same badge at the same time. |
19 | 24 |
|
20 |
| -- Their PRs are not being merged |
21 |
| -- They finds difficulty in understanding the issue |
22 |
| -- They could not reach to expectation |
23 |
| - So this will help the maintainers get notified when they see these people inactive. |
24 | 25 |
|
25 | 26 | ## How does it work
|
26 | 27 |
|
27 | 28 | For instance, suppose a contributor “X” has been quite active within the community by working on various PRs, opening and resolving various issues, active on chat channels but after a month “X” gets disappeared. So by using this dashboard they will have a badge interface. There will be a badge attached in front of the name of the contributor. Let the name of the badge be “Y” so this badge will have a unique color. So as the time passes like “ a day went, 1 week went, 2 weeks went, a month, etc) this badges will get keep on fading. And Every fade color will have a unique reason. For example, when a contributor made a PR, the badge appeared “Red” in color. This badge will remain in the same color as long as he/she is contributing. Assume that contributor stops contributing and has not contributed for a week so his badge will become green in color. And this will keep on notifying mainaters, Admins about their disappearing. This way the organisations will have greater eye on the contributors and can help them sustain with the community.
|
28 | 29 |
|
29 | 30 | ## Setting up the project
|
30 | 31 | To set up the project, carry out the following steps:
|
31 |
| -- Clone/download the project locally |
| 32 | + |
| 33 | +**Step 1:-** clone the repository |
| 34 | + |
| 35 | +``` git clone https://github.com/username/Codebadge.git ``` |
| 36 | + |
32 | 37 | - Create an [oAuth](https://github.com/settings/developers) application if you haven't already
|
| 38 | + |
33 | 39 | - Make sure that the callback-url is set to `http://localhost:8080/#/auth`
|
| 40 | + |
34 | 41 | - Make an `.env` file in the root folder of the project (where package.json is)
|
| 42 | + |
35 | 43 | - Add the code given below and replace it with values from your oAuth application:
|
36 |
| -`VUE_APP_CLIENT_ID=<client id>` |
37 |
| -`VUE_APP_CLIENT_SECRET=<client secret>` |
38 |
| -- Run the app using `npm start serve` |
| 44 | +``` |
| 45 | +VUE_APP_CLIENT_ID=<client id> |
| 46 | +VUE_APP_CLIENT_SECRET=<client secret> |
| 47 | +``` |
| 48 | +**Step 2:-** install frontend dependencies and run frontend server |
| 49 | +``` npm install && npm run serve``` |
| 50 | + |
| 51 | +**Step 3:-** install flask api dependencies and run api |
| 52 | +``` |
| 53 | +cd backend |
| 54 | +virtualenv -p python3 venv |
| 55 | +source venv/bin/activate |
| 56 | +pip install -r requirements.txt |
| 57 | +FLASK_APP=run.py flask run |
| 58 | +``` |
39 | 59 |
|
40 | 60 | ## Stack used
|
41 | 61 |
|
42 |
| -This will have a dashboard, where these things can be placed. The stack used can be any but since the organisation have fixed stack so its better to stick to Nodejs, Vue, React. |
| 62 | +This will have a dashboard, where these things can be placed. The stack used can be any but since the organisation have fixed stack so its better to stick to Nodejs, Vue, Flask. |
43 | 63 |
|
44 | 64 | ## Benefits to the community
|
45 | 65 |
|
|
0 commit comments