2013
DOI: 10.1007/978-3-319-03998-5_11
|View full text |Cite
|
Sign up to set email alerts
|

How Do Computer Science Students Use Distributed Version Control Systems?

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
7
0

Year Published

2014
2014
2024
2024

Publication Types

Select...
3
2
1

Relationship

1
5

Authors

Journals

citations
Cited by 6 publications
(7 citation statements)
references
References 5 publications
0
7
0
Order By: Relevance
“…The reason is that creating a repository always involves a small amount of overhead which is not significant if the benefits of the system are clear. We also noticed in our earlier research that students who are working in a project course produce better commit messages as when they use Git for weekly course work [4] (in the present paper we analyzed the students' own view of the messages). We recommend teachers to pay attention to how to communicate course management use cases and more realistic VCS use cases to learners, and even to use another kinds of tools for pure submission returns.…”
Section: Absence Of Authentic Use Casesmentioning
confidence: 65%
See 2 more Smart Citations
“…The reason is that creating a repository always involves a small amount of overhead which is not significant if the benefits of the system are clear. We also noticed in our earlier research that students who are working in a project course produce better commit messages as when they use Git for weekly course work [4] (in the present paper we analyzed the students' own view of the messages). We recommend teachers to pay attention to how to communicate course management use cases and more realistic VCS use cases to learners, and even to use another kinds of tools for pure submission returns.…”
Section: Absence Of Authentic Use Casesmentioning
confidence: 65%
“…-In our view, the most interesting aspect emerging from the data on commit message writing, constituting a future research question on the writing activity and informativeness, is that this writing may naturally become dependent on group size, communication distance, and the current complexity of the shared product development. The finding that students considered their presence in the work room removing a need for informative commit messages is likely to explain our previous observation of nonsensical commit messages [5], while this appears to be less prevailing in a project-based course as compared to exercise-based courses [4].…”
Section: Discussionmentioning
confidence: 96%
See 1 more Smart Citation
“…The adoption of git in education [10][11][12][13][14] offers the opportunity to gain insights into the amount of work contributed to the project by each team member (e.g., source code added to the repository), as well as behavior patterns (e.g., software engineering practices and the team dynamics), through metrics visualizations. We believe that an assessment based on quantitative git metrics could serve as a helpful feedback tool (and fairer grading scheme) for both instructors and students, providing objective real-time measures of contributions to a development project.…”
Section: Introductionmentioning
confidence: 99%
“…Version control software (VCS) has been used extensively in professional software engineering to manage changes to files (Cochez et al., 2013). In practice, these technologies enable multiple people to work together collaboratively whilst also permitting flexible change tracking, and the ability to revert to previous versions (Cochez et al., 2013; Sink, 2011). Centralised version control software retains the development repository on a central server, a popular example being Apache Subversion.…”
Section: Introductionmentioning
confidence: 99%