deadlock - GitLit

[vchrombie]

DEADLOCK - GITLIT

ℹ️ Project information

• Project Name: GitLit
• Short Project Description: Platform to connect developers with organizations and create new Open Source Communities.
• Team Name: deadlock
• Team Members:
  • Venu Vardhan
  • Aswin Shenoy
  • Akhil K Gangadharan
• Demo Link: https://goo.gl/qpWz2g
• Repository Link: https://github.com/amfoss/gitlit
• Labels: Open Innovation, Open Innovation No Track Followed

🔥 Your Pitch

Open Source is, by large, hard to adjust into. Whenever one enters the world of Open Source, he/she is, in most of the cases, greeted by large organizations where new contributors may find difficult to contribute something worthy, it can be their lack of patience or simply the lack of enough skills or it might be what we think it is - simply the lack of finding the correct projects.

GitLit is a web app which matches projects available on GitHub by rating the user by analyzing the skills and interests and then recommend projects for them, after analyzing the projects by activity, complexity, etc to get you the perfect project to contribute to which is available for your skills.

Furthermore, even for the contributors, discovering interesting and contributable communities, and then to find workable issues and cool features to take up, is, in fact, a complicated and time-taking task, often leading many beginners to drop out of Open Source as they don't know where and how to get started.

GitLit is a web app that rates repositories and contributors through a logical algorithm which takes into consideration not only a few standard metrics like Stars, Forks, and PRs, but also accounting for factors like Activity in the Community (eg: Issue Resolution, Feature Addition), backgrounds of the contributors etc.

Target Customers

• Students & Beginners: GitLit can be used by students and beginners to get started into the world of
  Open Source. It helps them to break-the-ice, and kick-start their FOSS journey without essentially going into the deeper level they can.
• Developers GitLit can also be used by amateur as well as professional developers to discover innovate, interesting and relevant projects to contribute to, based on their skill level.
• Developer Advocates: GitLit can be used by developer advocates to identify enthusiastic and talented contributors, who are interested in their organization, and connect with them. It can be also used by them to analyze their projects, and monitor community members.
• College Clubs: College-based computer clubs like amFOSS, can use GitLit to identify enthusiastic and talented students out of a large pool, effectively monitor them and check their progress.
• Corporate Recruiters: Corporate companies can discover developers, with the required talent and passion using credible metrics of GitLit

General Metrics

User Analysis:

• Base Score: General cliche metrics
• Creation: How good the developer’s own project is?
• Contribution: How active is the developer in contributing to other repositories?
• Community: How large is the network of the repository?
• Activity: How frequently does the user contribute?
• Topic-wise Metrics :
  • Skill Score: represents the skill a user has for a topic?
  • Interest Score: how interested the user is in the topic?

Repo Analysis:

• Merit: How valuable is the community to FOSS?
• Activity: How engaging and active the community is?
• Popularity: How popular is the community?
• Inclusivity : How likely is the community open to new contributors?

🔦 Any other specific thing you want to highlight?

We plan to scale up by adding more advanced metrics by using dedicated processing by Google Big Query since we are largely dependent on the API's of GitHub, there are large limitations for now.

We also have started working on an ML algorithm which will efficiently match the developers with the most relevant projects, backing on our metrics.

Further, we would like to integrate NLP for identifying the quality of code, and community engagement.

✅ Checklist

Before you post the issue:

• You have followed the issue title format.
• You have mentioned the correct labels.
• You have provided all the information correctly.