Difference between revisions of "SPO600 Code Review Lab"
Chris Tyler (talk | contribs) |
Chris Tyler (talk | contribs) |
||
| Line 1: | Line 1: | ||
[[Category:SPO600]] | [[Category:SPO600]] | ||
| − | # Select any two open source software packages that have different licenses. | + | # 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). | # 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). | ||
| − | # Identify one 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, how long the whole review took, how responsive the participants were to updates in the process, | + | # Identify one 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. | # 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. | ||
{{Admon/tip|Finding Software Packages|One way to find potential software packages for this lab on an RPM-based Linux system is to take advantage of the rpm database. For example, the command <code>rpm -q -i bash</code> will display information about the ''bash'' package, including the URL of the upstream project as well as the software license.}} | {{Admon/tip|Finding Software Packages|One way to find potential software packages for this lab on an RPM-based Linux system is to take advantage of the rpm database. For example, the command <code>rpm -q -i bash</code> will display information about the ''bash'' package, including the URL of the upstream project as well as the software license.}} | ||
Revision as of 16:36, 8 January 2014
- 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).
- Identify one 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.
Finding Software Packages
One way to find potential software packages for this lab on an RPM-based Linux system is to take advantage of the rpm database. For example, the command
One way to find potential software packages for this lab on an RPM-based Linux system is to take advantage of the rpm database. For example, the command
rpm -q -i bash will display information about the bash package, including the URL of the upstream project as well as the software license.