Open main menu

CDOT Wiki β

Changes

SPO600 Code Review Lab

41 bytes added, 13:58, 6 September 2017
Lab 1
# Select '''any two open source software packages''' that have '''different licenses'''.
# Research the procedure used by those projects to accept code ("patches") from contributors. This may be through a mailing list, bug tracker, or source code management system (SCMS)/version control system (VCS)such as Mercurial, Bazaar, or Git/GitHub.
# Identify one software change ("patch") successfully submitted in each community, and observe the entire review process from start to finish. Note how many people were involved in the review, the role of those people in the community and project, how long the whole review took, how responsive the participants were to updates in the process, what kinds of issues were discussed, and how issues were resolved.
# '''Write a blog post discussing your findings'''. Explain how each community's review process works, the reasons for what you've observed, and note the advantages and disadvantages of each approach. Consider what you personally would have to do and learn in order to successfully submit a patch to each community.