1
edit
Changes
m
1. *Identifying Bugs2. *Identifying and implementing features 3. *Creating documentation or revising documentation that is available for the code4. *Understanding how the code works5. *And the last and according to Mr.Smedberg the most hardest part of it all; keeping track of the patches or understanding what patches have been done on the software by other people in the community
no edit summary
'''Benjamin Smedberg's Open source code review'''
Focusing on the first talk that I attended; Benjamin Smedberg’s key main reasons behind code reading were as follows:
