Work Log Guidelines: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
(Created page with "=Introduction= See also Work Log The Work Log is intended to be the main log of progress for any OSE contributor. In order to facilitate coordination across a globally-dist...")
 
No edit summary
Line 5: Line 5:
The Work Log is intended to be the main log of progress for any OSE contributor. In order to facilitate coordination across a globally-distributed team, an essential log of progress is key. This log should include hyperlinks to all work product - such that contributions of team members are absolutely transparent to any other person. This is useful for volunteers to inform team members on progress, and it is useful for staff for planning, evaluation, and review purposes. We require that staff keep a daily log according to these guidelines:
The Work Log is intended to be the main log of progress for any OSE contributor. In order to facilitate coordination across a globally-distributed team, an essential log of progress is key. This log should include hyperlinks to all work product - such that contributions of team members are absolutely transparent to any other person. This is useful for volunteers to inform team members on progress, and it is useful for staff for planning, evaluation, and review purposes. We require that staff keep a daily log according to these guidelines:


#Use frequent hyperlinks to work product. Place or embed all work product, Google Docs, videos, images, spreadsheets, diagrams on the wiki itself. If you are choosing another web location as a repository, link to that repository. We like to have all material posted on the wiki to minimize broken links if content goes off-line at other web locations.
#Use frequent hyperlinks to work product. Place or embed all work product, Google Docs, videos, images, spreadsheets, diagrams on the wiki itself. If you are choosing another web location as a repository, link to that repository. We like to have all material posted on the wiki to minimize broken links if content goes off-line at other web locations. Document in paragraph format, don't sprawl your log as long lists - for ease of visual navigation. The Log is intended to be a hyperlinked index to work product more than an actual repository of work product. So in short: put all your work on the wiki. Our motto is, "If it's not documented on the wiki, it doesn't exist" (as far as the collaborative intent of this project).

Revision as of 13:34, 14 November 2012

Introduction

See also Work Log

The Work Log is intended to be the main log of progress for any OSE contributor. In order to facilitate coordination across a globally-distributed team, an essential log of progress is key. This log should include hyperlinks to all work product - such that contributions of team members are absolutely transparent to any other person. This is useful for volunteers to inform team members on progress, and it is useful for staff for planning, evaluation, and review purposes. We require that staff keep a daily log according to these guidelines:

  1. Use frequent hyperlinks to work product. Place or embed all work product, Google Docs, videos, images, spreadsheets, diagrams on the wiki itself. If you are choosing another web location as a repository, link to that repository. We like to have all material posted on the wiki to minimize broken links if content goes off-line at other web locations. Document in paragraph format, don't sprawl your log as long lists - for ease of visual navigation. The Log is intended to be a hyperlinked index to work product more than an actual repository of work product. So in short: put all your work on the wiki. Our motto is, "If it's not documented on the wiki, it doesn't exist" (as far as the collaborative intent of this project).