![]() ![]() We conclude that the conceived framework can be used to help developers increase their projects’ visibility. An empirical evaluation demonstrates that HybridRec outperforms three state-of-the-art baselines, obtaining a better performance with respect to various metrics. Furthermore, we apply a preprocessing phase to clean and refine the input data before feeding the recommendation engine. To deal with unbalanced datasets, we employ a Complement Naïve Bayesian Network (CNBN). In this paper, we extend our work by building HybridRec, a recommender system based on stochastic and collaborative-filtering techniques to generate more relevant topics. MNBN exploits a stochastic network to predict topics, while TopFilter relies on a syntactic-based function to recommend topics. In our previous work, we implemented MNBN and TopFilter to recommend GitHub topics. ![]() However, assigning inappropriate topics to a repository might hamper its popularity and reachability. To help developers find the right artifacts, GitHub uses topics, which are short texts assigned to the stored artifacts. ![]() GitHub is at the forefront of this kind of platforms, providing developer with a reservoir of code contained in more than 28M repositories. Software repositories are increasingly essential to support the management of typical artifacts building up projects, including source code, documentation, and bug reports. Moreover, our results show the value of recommendation and provide important insights for GitHub to recommend repositories. Our results show that forking is mainly used for making contributions of original repositories, and it is beneficial for OSS community. In comparison with unattractive repository owners, attractive repository owners have higher percentage of organizations, more followers and earlier registration in GitHub. ![]() (3) Developers mostly fork repositories from creators. (2) A repository written in a developer’s preferred programming language is more likely to be forked. Developers care about repository owners when they fork repositories. More than 42 % of developers that we have surveyed agree that an automated recommendation tool is useful to help them pick repositories to fork, while more than 44.4 % of developers do not value a recommendation tool. Developers find repositories to fork from various sources: search engines, external sites (e.g., Twitter, Reddit), social relationships, etc. Our main observations are: (1) Developers fork repositories to submit pull requests, fix bugs, add new features and keep copies etc. We make surveys, and analyze programming languages and owners of forked repositories. We collect a dataset containing 236,344 developers and 1,841,324 forks. In this paper, we explore why and how developers fork what from whom in GitHub. A deep understanding of repository forking can provide important insights for OSS community and GitHub. Developers freely fork repositories, use codes as their own and make changes. Though forking is controversial in traditional open source software (OSS) community, it is encouraged and is a built-in feature in GitHub. Forking is the creation of a new software repository by copying another repository. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |