Difference between revisions of "SPO600 Code Review Lab"
Chris Tyler (talk | contribs) (Created page with 'Category:SPO600 # Select any two open source software packages that have different licenses.{{Admon/tip|Finding Software Packages|One way to find potential software packages…') |
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, and what kinds of issues were discussed. | # 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, and what kinds of issues were discussed. | ||
# 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 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 23:41, 7 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, how long the whole review took, how responsive the participants were to updates in the process, and what kinds of issues were discussed.
- 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 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 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.