The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Introduction to open source paradigm
|
|
Examine the open source paradigm and demonstrate an understanding of the differences from the traditional software development models Completed |
Evidence:
|
Investigate and demonstrate understanding of the types of on-line resources Completed |
Evidence:
|
Investigate and demonstrate understanding of the types of project documentation Completed |
Evidence:
|
Recognise and demonstrate understanding of the role of an on-line community and international collaboration Completed |
Evidence:
|
Examine and demonstrate understanding of motivational factors for contributors to open source code Completed |
Evidence:
|
Analyse and demonstrate understanding of open source licensing models Completed |
Evidence:
|
Familiarise with target project
|
|
Examine on-line resources associated with the target project Completed |
Evidence:
|
Download pre-built executable binaries, to install and run project Completed |
Evidence:
|
Download, read and demonstrate understanding of supporting documentation Completed |
Evidence:
|
Prepare for maintenance activities
|
|
Select and register with a relevant on-line community open source group Completed |
Evidence:
|
Download nightly snapshots of latest source code and supporting documentation Completed |
Evidence:
|
Build and execute snapshot where appropriate Completed |
Evidence:
|
Maintain code
|
|
Access the project bug database and select bugs to be resolved or features to be added Completed |
Evidence:
|
Make changes to local copy of code to resolve selected bugs Completed |
Evidence:
|
Test resulting code to ensure it performs appropriately Completed |
Evidence:
|
Prepare code patch for submission Completed |
Evidence:
|
Submit code patch to project Completed |
Evidence:
|
Use appropriate software development tools and environment Completed |
Evidence:
|
Maintain documentation
|
|
Access project documentation Completed |
Evidence:
|
Prepare and contribute new information or updates to existing documentation Completed |
Evidence:
|
Prepare and submit documentation changes to project Completed |
Evidence:
|
Participate in community
|
|
Exchange messages with other project members and actively participate in community activities Completed |
Evidence:
|
Take action to ensure exchanges are sociallyacceptable Completed |
Evidence:
|
Submit code and documentation code patches for inclusion Completed |
Evidence:
|
Access on-line project resources frequently to keep up to date with project and community developments Completed |
Evidence:
|
Take action to ensure community participationstandards are observed and maintained Completed |
Evidence:
|