Understanding "watchers" on GitHub

@inproceedings{Sheoran2014UnderstandingO,
  title={Understanding "watchers" on GitHub},
  author={Jyoti Sheoran and Kelly Blincoe and Eirini Kalliamvakou and Daniela E. Damian and Jordan Ell},
  booktitle={MSR 2014},
  year={2014}
}
Users on GitHub can watch repositories to receive notifications about project activity. This introduces a new type of passive project membership. In this paper, we investigate the behavior of watchers and their contribution to the projects they watch. We find that a subset of project watchers begin contributing to the project and those contributors account for a significant percentage of contributors on the project. As contributors, watchers are more confident and contribute over a longer… Expand

Tables from this paper

An in-depth study of the promises and perils of mining GitHub
TLDR
The results indicate that while GitHub is a rich source of data on software development, mining GitHub for research purposes should take various potential perils into consideration, and provides a set of recommendations for software engineering researchers on how to approach the data in GitHub. Expand
The Promises and Perils of Mining GitHub ( Extended Version )
With over 10 million git repositories, GitHub is becoming one of the most important sources of software artifacts on the Internet. Researchers mine the information stored in GitHub’s event logs toExpand
Which Contributions Predict Whether Developers are Accepted into GitHub Teams
TLDR
This work studies project communities on GitHub to discover which forms of software contribution characterize developers who begin as development team outsiders and eventually join the team, in contrast to developers who remain team outsiders. Expand
Adding Sparkle to Social Coding: An Empirical Study of Repository Badges in the npm Ecosystem
TLDR
A large-scale, mixed-methods empirical study of npm packages finds that non-trivial badges, which display the build status, test coverage, and up-to-dateness of dependencies, are mostly reliable signals, correlating with more tests, better pull requests, and fresher dependencies. Expand
GitHub and Stack Overflow: Analyzing Developer Interests Across Multiple Social Collaborative Platforms
TLDR
This study finds that developers share common interests in GitHub and Stack Overflow, and developers do share similar interests with other developers who co-participated activities in the two platforms. Expand
Adding Sparkle to Social Coding: An Empirical Study of Repository Badges in the npm Ecosystem
  • Asher Trockman
  • Computer Science
  • 2018 IEEE/ACM 40th International Conference on Software Engineering: Companion (ICSE-Companion)
  • 2018
TLDR
A large-scale, mixed-methods empirical study of npm packages finds that non-trivial badges, which display the build status, test coverage, and up-to-dateness of dependencies, are mostly reliable signals, correlating with more tests, better pull requests, and fresher dependencies. Expand
GitHub: factors influencing project activity levels
TLDR
This GitHub structural path modelling study captures the current top 100 JavaScript projects in operation for at least one year or more and shows a project's activity level increases with: greater responder-group collaborative efforts, increased numbers of major critical project version releases, and the generation of further commits. Expand
GitHub's milestone tool: A mixed‐methods analysis on its use
TLDR
A mixed‐methods analysis is conducted in a large‐scale dataset of GitHub projects, to help developers gain some insights into the milestone tool, including its usage, benefits, and limitations. Expand
Towards Community and Expert Detection in Open Source Global Development
TLDR
This work adopts a clustering algorithm in order to find experts not only with specific knowledge, but also expertise in collaboration on the topics required, and presents evidence that the detected clusters and core individuals reflect real life communities and influential developers. Expand
Data Analysis of Correlation Between Project Popularity and Code Change Frequency
TLDR
It is found that projects with at least 1500 watchers each month have a strong positive correlation between the project popularity and frequency of code changes, and the number of pull requests is 73.2 % more important to the popularity of a project than thenumber of watchers. Expand
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 10 REFERENCES
The promises and perils of mining GitHub
TLDR
It is shown, for example, that the majority of the projects are personal and inactive; that GitHub is also being used for free storage and as a Web hosting service; and that almost 40% of all pull requests do not appear as merged, even though they were. Expand
Social coding in GitHub: transparency and collaboration in an open software repository
TLDR
It is found that people make a surprisingly rich set of social inferences from the networked activity information in GitHub, such as inferring someone else's technical goals and vision when they edit code, or guessing which of several similar projects has the best chance of thriving in the long term. Expand
Creating a shared understanding of testing culture on a social coding site
TLDR
Several strategies that software developers and managers can use to positively influence the testing behavior in their projects are found, however, project owners on GitHub may not be aware of them. Expand
Social Networking Meets Software Development: Perspectives from GitHub, MSDN, Stack Exchange, and TopCoder
TLDR
The guest editors of the January/February 2013 issue conducted semistructured interviews with leaders from four successful companies to gain an understanding of the role social networking plays in today's software development world. Expand
Impression formation in online peer production: activity traces and personal profiles in github
TLDR
It is found that users in this setting seek out additional information about each other to explore the project space, inform future interactions, and understand the potential future value of a new person. Expand
The social structure of free and open source software development
TLDR
It is suggested that FLOSS projects might have to work hard to achieve the expected development advantages which have been assumed to flow from "going open", and the variation in communications structure across projects means that communications centralization is useful for comparisons between FLOSS teams. Expand
The GHTorent dataset and tool suite
  • Georgios Gousios
  • Computer Science
  • 2013 10th Working Conference on Mining Software Repositories (MSR)
  • 2013
TLDR
The GHTorent project has been collecting data for all public projects available on Github for more than a year, and the dataset details and construction process are presented. Expand
Community, joining, and specialization in open source software innovation: a case study
TLDR
An inductive theory of the open source software innovation process is developed by focussing on the creation of Freenet, a project aimed at developing a decentralized and anonymous peer-to-peer electronic file sharing network. Expand
Loop Recognition in C++/Java/Go/Scala
TLDR
The benchmark is encoded, a well specified, compact benchmark in four programming languages, namely C++, Java, Go, and Scala, which points to very large differences in all examined dimensions of the language implementations. Expand
4] https://github.com/blog/1204-notifications-stars
  • 4] https://github.com/blog/1204-notifications-stars