Proceedings of the 40th International Conference on Software Engineering 2018
DOI: 10.1145/3180155.3180209
|View full text |Cite
|
Sign up to set email alerts
|

Adding sparkle to social coding

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
6
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 57 publications
(7 citation statements)
references
References 58 publications
1
6
0
Order By: Relevance
“…One potential explanation for this finding is that the Starstruck badge is awarded to a developer as a result of the interest of others (stars) in their repositories: creating a repository implies an effort broader in scope, if not harder, as compared to others badges, which require the developers to take one action (e.g., answer a question, merge a pull request). This result is somewhat consistent with those reported by Trockman et al [24] who found repository badges related to popularity to be more reliable as assessment signals. One major difference with their work is that repository badges are chosen-maintainers select what they intend to signal by adding them to README pages (e.g., the count of downloads badge to signal popularity, up-to-date dependency badge to signal the lack of known security risks).…”
Section: Discussionsupporting
confidence: 92%
See 1 more Smart Citation
“…One potential explanation for this finding is that the Starstruck badge is awarded to a developer as a result of the interest of others (stars) in their repositories: creating a repository implies an effort broader in scope, if not harder, as compared to others badges, which require the developers to take one action (e.g., answer a question, merge a pull request). This result is somewhat consistent with those reported by Trockman et al [24] who found repository badges related to popularity to be more reliable as assessment signals. One major difference with their work is that repository badges are chosen-maintainers select what they intend to signal by adding them to README pages (e.g., the count of downloads badge to signal popularity, up-to-date dependency badge to signal the lack of known security risks).…”
Section: Discussionsupporting
confidence: 92%
“…To gauge the perceptions of personal badges in GITHUB (RQ 4 ), we used Google Forms to design an online survey, consisting of 16 questions (both closed-and open-ended). The survey questions are partially based on a similar work by Trockman et al [24] who investigated repository badges in GITHUB. After collecting the basic demographics, the questions focused on why respondents choose (not) to display badges on their profile, whether they consider them as indicators of development skills, and what inferences they make about other developers who display badges on their profile pages.…”
Section: Empirical Study a Datamentioning
confidence: 99%
“…For prospective users, it is good to know whether you have tested your software and, if so, which tests you have included. This can be done by displaying a badge [ 7 ] (see https://github.com/microbinfie-hackathon2020/CSIS/blob/main/README.md#example-software-testing ), or linking to your defined testing strategy e.g. a GitHub Actions YAML, (see recommendation #2, Fig.…”
Section: Recommendationsmentioning
confidence: 99%
“…GitHub has added a number of social and awareness features that create a “social coding” transparent environment that provides fodder for a great many social and technical inferences about the state of a project and the activities of other developers 1–3 . Badges, which have become quite popular, can effectively encourage good development practices 4 . The pervasiveness of social coding also carries the benefits of de facto standardization, as when a developer we were interviewing said of pull requests, that they have created a uniform “language of contribution.”…”
Section: What Has Changed Since 2006?mentioning
confidence: 99%
“…encourage good development practices. 4 The pervasiveness of social coding also carries the benefits of de facto standardization, as when a developer we were interviewing said of pull requests, that they have created a uniform "language of contribution. "…”
mentioning
confidence: 99%