In the network, nodes represent repositories and the weighted arcs the number of accounts that follow a pair of nodes. I then generated the network of repositories. For each account I collected a list of all the account’s repositories. Through the Github API I collected the list of accounts that have made a fork to the repository. “a line-oriented search tool that recursively searches your current directory for a regex pattern while respecting your gitignore rules” Some notable projects in other communities: The result is an interesting collection of small bipartite networks that, as I had hoped, collect several projects that I like and that are fun to analyse. In short, I have used various hidden techniques with an arbitrary choice of some parameters :) Simplifying the process: I created the network formed by users and projects (so users are bound by projects they share as forks), I took the subnetwork of the nodes with the highest pagerank and broke it into communities. I started from all the accounts that made a fork of the awesome-rust project and collected the list of projects associated with each user. An interesting language, related to the Redox operating system. The various Awesome xyz repositories are structured lists of projects: they are often well made and are excellent starting points for tackling a theme.Īwesome Rust is dedicated to the programming language Rust. I decided to use one of the repositories that best helps you navigate other projects: Awesome Rust. So why use the fork? Because this action indicates interest in the content of a project. The forks can lead to an enrichment of the initial project, through the merge operation, or they can lead to a fork even within the active community. The fork action allows a Github user to create a copy of a repository to begin independent code development. Github generates different types of networks thanks to different methods of user interaction and different actions that can be performed with respect to repositories (star, fork, watch, etc.).įor this experiment I decided to use the fork, perhaps the most basic action that a git user can perform. In short: I tried to see which informal networks form around a repository. The idea is simple (more or less): if a project interests me, it is also likely to interest a subset of people with similar tastes to mine. I have therefore created a small tool that allows me to fish not completely blindly in the sea of repositories. Reflecting on the techniques I know and use in my work at Elif Lab, I wanted to try to help the probability. Very often, the discovery of these projects is accidental and, on several occasions, it is virtually impossible to find some of them by simply navigating in a linear way. One of my recurring activities is the search for interesting projects on GitHub: I am often pleasantly surprised to find big and small projects of great utility (or fascinating, but sometimes useless).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |