Table of Contents:
This project won the MLH Fellowship Orientation Hackathon - Batch 4 along with other great projects by MLH Fellows. We highly suggest you check them out.
Analyzes your GitHub Profile and presents you with a report on how likely you are to become the next MLH Fellow!
Provides you with an extensive analysis on the following features of your profile:
| Feature | Description |
|---|---|
| Commits | Number of total commits the user made |
| Contributions | Number of repositories where the user made contributions |
| Followers | Number of followers the user has |
| Forks | Number of forks the user has in their repositories |
| Issues | Number of issues the user has raised |
| Organizations | Number of organizations the user is a part of |
| Repos | Number of repositories the user has |
| Stars | Number of stars the user has on their repositories |
And gives you a comprehensive score of how similar your GitHub Profile is to an average MLH Fellow's GitHub.
It also shows your statistics in a user-friendly data visualization format for you to gauge the range of your skills and become the next MLH Fellow!
Dear user, building this application, we were trying our best to provide with data insights into things you can improve through your GitHub Profile. This is a hackakthon project that is built by Open Source Fellows and is not directly affiliated with MLH in any capacity. The positive score in your application does not guarantee your chances of becoming a fellow because there are external things apart from GitHub that affect the decision process.
We also hope that you understand that your GitHub Stats do not affect your value to the community as a developer. We all have different paths to success in our lives, and they do not necessarily involve high scores. Regardless of your numbers, you are going to succeed in your journey.
We used the following technologies:
- BentoML along with Heroku to build an API endpoint that calculates the comprehensive score for the user based on a simple query.
- Flask deployed to Heroku to setup a bridge between the frameworks and collect the input data.
- React.js served on Firebase to provide user-friendly UI for future MLH fellows to use.
To contribute to this open-source project, follow these steps:
- Fork the repository.
- Create a branch:
git checkout -b <branch_name>. - Make your changes and commit them:
git commit -m '<commit_message>'. - Push to your branch:
git push origin <project_name>/<location>. - Create a pull request.
To work on BentoML:
- Go to model/bento_deploy to find necessary files.
- Read BentoML Start Guide to learn more about the files.
- Improve the BentoML Interface to provide our users with a more accurate score.
- Create the BentoML prediction service with
python bento_packer.pyand commit the saved class frombentoml get IrisClassifier:latest --print-location --quiet.
To work on the Back-End:
- Consult scr/server and its README.
- Make contributions.
Alternatively: Reach out to one of the Project Contributors for questions.
We built this project because we wanted to help prospective MLH Fellows with their progress toward a better GitHub profile with solid projects and a record of active work. We also wanted to give them some insights into what an average fellow at MLH looks like.
When we were just aspiring to become MLH Fellows, we would look for different sources of information to know what MLH is looking for in their fellows and better ways to prepare. So we tried to address this issue and hopefully support future fellows on their way to success.
However, we make an important notion that your GitHub Profile does not define you as a developer. Our tool is simply to let you see into the data for areas of potential improvement and keep working toward your goals. We do not consider things like:
- Personal communication levels
- Spot availability
- Match in project interests
The mentioned points affect your chances on becoming a fellow. Unfortunately, there is no way to take them into consideration.
Working on the project, I learned the basics of BentoML and deploying the server model to the cloud like Heroku. I also gained some experience in Data Mining and Processing, which is an invaluable skill toward my journey to Machine Learning Engineering.
The contributions I made are:
- Wrote Jupyter Notebooks where we showcase our work with the GitHub API.
- Set up a Git repository with active GitHub Projects and proper infrastructure.
- Mined data on more than 650 fellows in the MLH Fellowship organization.
- Created a BentoML API node deployed to Heroku for querying.
During the hackathon I majorly worked on the Front-End part of the project. I created a friendly UI/UX to collect data and visualize the results. Also, I helped a little bit with the Back-End by creating a facade API to make working with GitHub easier. The new interface adds a level of abstraction that mainly focuses on quantitative data that we needed to do the statistical analysis.
I really enjoyed the Orientation Hackathon. I now feel more confident working with Git/GitHub. I also started learning about functional programming base API (OCamal/dream).
Utilizing BentoML gave us a flexible, high-performance framework to serve, manage, and deploy our model to predict MLH fellowship status using user's GitHub profiles. In particular, I enjoyed working with ML frameworks like Matplotlib, Seaborn, and Pandas, as well as Cloud native deployment services, and API serving that were all packaged into a single service.
Some of my contributions were:
- Implemented the ANNOVA model as an alternative improved statiscal comparison to the one we are using now. Our current one works fine, but we can use this in the case we want a more rigorous and detailed comparison (multiple pairwise comparison (post hoc comparison) analysis for all unplanned comparison using Tukey’s honestly significantly differenced (HSD) test).
- Built a CI (continuous integration) pipeline for build, run, and testing of our node app as well as python app using github actions.
- Implemented method to compute average statistics for aggregated mlh fellow data.
Shout out to everyone in our team!
I worked on the Back-End Server for the project and the deployment pipeline on Heroku. I was able to use the Flask Rest Framework for the Back-End which was a new experience for me.
This project is served under the MIT License.
MIT License
Copyright (c) 2021 Damir Temir
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.