Work Log Guidelines - Revision history

Marcin: /* Requirements */

2014-01-28T15:44:26Z

Requirements

← Older revision		Revision as of 15:44, 28 January 2014
Line 13:		Line 13:
	#'''Log all relevant tasks as soon as they are done''' - If your contribution is relevant - log it. If it is not logged, it will be more difficult to provide you with attribution. Log right after you do something, otherwise it is easy to forget. This does not mean that you have Bookmark your log page and go to it after every task. Staff, volunteers, and remote collaborators are encouraged to keep a work log. Log everything that you do, on the same day that you do it. If you do not log it after task completion, you are less likely to remember what you did. Use our [[Date Format Convention]]. Roll up entries into a single link on a monthly basis - see links at bottom of [[Marcin Log]] for an example.		#'''Log all relevant tasks as soon as they are done''' - If your contribution is relevant - log it. If it is not logged, it will be more difficult to provide you with attribution. Log right after you do something, otherwise it is easy to forget. This does not mean that you have Bookmark your log page and go to it after every task. Staff, volunteers, and remote collaborators are encouraged to keep a work log. Log everything that you do, on the same day that you do it. If you do not log it after task completion, you are less likely to remember what you did. Use our [[Date Format Convention]]. Roll up entries into a single link on a monthly basis - see links at bottom of [[Marcin Log]] for an example.
	#'''Set weekly milestones and evaluate their completion''' - Every Monday, write down 3-5 milestones for the week. At the beginning of the next week, go back to this entry and document: (1) what you actually accomplished in the past week; and, if what you actually accomplished is different than what you promised, please explain the discrepancy. Then describe: (2) What worked for you? (3) What did not work for you, and how could that be improved? (4) Your plan for the coming week. This is for organizational learning and performance development purposes.		#'''Set weekly milestones and evaluate their completion''' - Every Monday, write down 3-5 milestones for the week. At the beginning of the next week, go back to this entry and document: (1) what you actually accomplished in the past week; and, if what you actually accomplished is different than what you promised, please explain the discrepancy. Then describe: (2) What worked for you? (3) What did not work for you, and how could that be improved? (4) Your plan for the coming week. This is for organizational learning and performance development purposes.
	#'''Set monthly milestones and evaluate''' - ~~At the beginning of the month, write down 3-5 main goals for that month~~. ~~At the beginning of the next month, write down~~		#'''Set monthly milestones and evaluate''' - See [[Review Process]].
	#'''Write a quarterly report''' - a quarterly report can be as simple as taking the Monthly Milestones and their Evaluation from the last 3 months - and compiled. Any extra comments on emergent patterns and point of improvement should be noted. Goals for the next quarter should also be listed, and these goals should be evaluated as part of the next quarter's report.		#'''Write a quarterly report''' - a quarterly report can be as simple as taking the Monthly Milestones and their Evaluation from the last 3 months - and compiled. Any extra comments on emergent patterns and point of improvement should be noted. Goals for the next quarter should also be listed, and these goals should be evaluated as part of the next quarter's report.
	#'''Formatting''' - For the logs to be easily understandable and effective in communicating work product succinctly, we are suggesting a particular format that emerges from our practical experience. Make every day indexable by entering it as a heading, such that any day can be accessed from an automatically-generated index on top of wiki page. Use Weekday, Month, Day, Year as standard headings - such as =Thu Oct 11, 2012=. This makes it easy to identify the Monday entry - which contain Weekly Milestones and their Review, which are written down by the person who is logging for self-evaluation, and others can assist in this evaluation as part of an open learning organization. Document in paragraph format, don't sprawl your log as long lists or subheadings - ''for compactness and ease of visual navigation''. Avoid lists whenever possible - and use a paragraph format instead. If you cannot resist using a list, use * instead of using a blank line - for compactness. ''Roll up entries into a single link on a monthly basis.'' See [[Marcin Log]] as an example, and see bottom of Marcin Log as an example of rolling entries up.		#'''Formatting''' - For the logs to be easily understandable and effective in communicating work product succinctly, we are suggesting a particular format that emerges from our practical experience. Make every day indexable by entering it as a heading, such that any day can be accessed from an automatically-generated index on top of wiki page. Use Weekday, Month, Day, Year as standard headings - such as =Thu Oct 11, 2012=. This makes it easy to identify the Monday entry - which contain Weekly Milestones and their Review, which are written down by the person who is logging for self-evaluation, and others can assist in this evaluation as part of an open learning organization. Document in paragraph format, don't sprawl your log as long lists or subheadings - ''for compactness and ease of visual navigation''. Avoid lists whenever possible - and use a paragraph format instead. If you cannot resist using a list, use * instead of using a blank line - for compactness. ''Roll up entries into a single link on a monthly basis.'' See [[Marcin Log]] as an example, and see bottom of Marcin Log as an example of rolling entries up.

Marcin: /* Requirements */

2014-01-28T15:44:01Z

Requirements

← Older revision		Revision as of 15:44, 28 January 2014
Line 12:		Line 12:
	#'''Use frequent hyperlinks to work product''' - Place or embed all work product, such as wiki pages, 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. 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).		#'''Use frequent hyperlinks to work product''' - Place or embed all work product, such as wiki pages, 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. 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).
	#'''Log all relevant tasks as soon as they are done''' - If your contribution is relevant - log it. If it is not logged, it will be more difficult to provide you with attribution. Log right after you do something, otherwise it is easy to forget. This does not mean that you have Bookmark your log page and go to it after every task. Staff, volunteers, and remote collaborators are encouraged to keep a work log. Log everything that you do, on the same day that you do it. If you do not log it after task completion, you are less likely to remember what you did. Use our [[Date Format Convention]]. Roll up entries into a single link on a monthly basis - see links at bottom of [[Marcin Log]] for an example.		#'''Log all relevant tasks as soon as they are done''' - If your contribution is relevant - log it. If it is not logged, it will be more difficult to provide you with attribution. Log right after you do something, otherwise it is easy to forget. This does not mean that you have Bookmark your log page and go to it after every task. Staff, volunteers, and remote collaborators are encouraged to keep a work log. Log everything that you do, on the same day that you do it. If you do not log it after task completion, you are less likely to remember what you did. Use our [[Date Format Convention]]. Roll up entries into a single link on a monthly basis - see links at bottom of [[Marcin Log]] for an example.
	#'''Set weekly milestones and evaluate their completion''' - Every Monday, write down 3-5 milestones for the week. At the beginning of the next week, go back to this entry and document: (1) what you actually accomplished; and ~~(2)~~, if what you actually accomplished is different than what you promised, please explain the discrepancy. This is for organizational learning and performance development purposes.		#'''Set weekly milestones and evaluate their completion''' - Every Monday, write down 3-5 milestones for the week. At the beginning of the next week, go back to this entry and document: (1) what you actually accomplished in the past week; and, if what you actually accomplished is different than what you promised, please explain the discrepancy. Then describe: (2) What worked for you? (3) What did not work for you, and how could that be improved? (4) Your plan for the coming week. This is for organizational learning and performance development purposes.
	#'''Set monthly milestones and evaluate''' - At the beginning of the month, write down 3-5 main goals for that month. At the beginning of the next month, write down ~~(1) what you actually accomplished in the past month; and (2), if what you actually accomplished is different than what you promised, please explain the discrepancy.~~		#'''Set monthly milestones and evaluate''' - At the beginning of the month, write down 3-5 main goals for that month. At the beginning of the next month, write down
	#'''Write a quarterly report''' - a quarterly report can be as simple as taking the Monthly Milestones and their Evaluation from the last 3 months - and compiled. Any extra comments on emergent patterns and point of improvement should be noted. Goals for the next quarter should also be listed, and these goals should be evaluated as part of the next quarter's report.		#'''Write a quarterly report''' - a quarterly report can be as simple as taking the Monthly Milestones and their Evaluation from the last 3 months - and compiled. Any extra comments on emergent patterns and point of improvement should be noted. Goals for the next quarter should also be listed, and these goals should be evaluated as part of the next quarter's report.
	#'''Formatting''' - For the logs to be easily understandable and effective in communicating work product succinctly, we are suggesting a particular format that emerges from our practical experience. Make every day indexable by entering it as a heading, such that any day can be accessed from an automatically-generated index on top of wiki page. Use Weekday, Month, Day, Year as standard headings - such as =Thu Oct 11, 2012=. This makes it easy to identify the Monday entry - which contain Weekly Milestones and their Review, which are written down by the person who is logging for self-evaluation, and others can assist in this evaluation as part of an open learning organization. Document in paragraph format, don't sprawl your log as long lists or subheadings - ''for compactness and ease of visual navigation''. Avoid lists whenever possible - and use a paragraph format instead. If you cannot resist using a list, use * instead of using a blank line - for compactness. ''Roll up entries into a single link on a monthly basis.'' See [[Marcin Log]] as an example, and see bottom of Marcin Log as an example of rolling entries up.		#'''Formatting''' - For the logs to be easily understandable and effective in communicating work product succinctly, we are suggesting a particular format that emerges from our practical experience. Make every day indexable by entering it as a heading, such that any day can be accessed from an automatically-generated index on top of wiki page. Use Weekday, Month, Day, Year as standard headings - such as =Thu Oct 11, 2012=. This makes it easy to identify the Monday entry - which contain Weekly Milestones and their Review, which are written down by the person who is logging for self-evaluation, and others can assist in this evaluation as part of an open learning organization. Document in paragraph format, don't sprawl your log as long lists or subheadings - ''for compactness and ease of visual navigation''. Avoid lists whenever possible - and use a paragraph format instead. If you cannot resist using a list, use * instead of using a blank line - for compactness. ''Roll up entries into a single link on a monthly basis.'' See [[Marcin Log]] as an example, and see bottom of Marcin Log as an example of rolling entries up.

Marcin: /* Requirements */

2014-01-28T15:08:30Z

Requirements

← Older revision		Revision as of 15:08, 28 January 2014
Line 15:		Line 15:
	#'''Set monthly milestones and evaluate''' - At the beginning of the month, write down 3-5 main goals for that month. At the beginning of the next month, write down (1) what you actually accomplished in the past month; and (2), if what you actually accomplished is different than what you promised, please explain the discrepancy.		#'''Set monthly milestones and evaluate''' - At the beginning of the month, write down 3-5 main goals for that month. At the beginning of the next month, write down (1) what you actually accomplished in the past month; and (2), if what you actually accomplished is different than what you promised, please explain the discrepancy.
	#'''Write a quarterly report''' - a quarterly report can be as simple as taking the Monthly Milestones and their Evaluation from the last 3 months - and compiled. Any extra comments on emergent patterns and point of improvement should be noted. Goals for the next quarter should also be listed, and these goals should be evaluated as part of the next quarter's report.		#'''Write a quarterly report''' - a quarterly report can be as simple as taking the Monthly Milestones and their Evaluation from the last 3 months - and compiled. Any extra comments on emergent patterns and point of improvement should be noted. Goals for the next quarter should also be listed, and these goals should be evaluated as part of the next quarter's report.
	#'''Formatting''' - For the logs to be easily understandable and effective in communicating work product succinctly, we are suggesting a particular format that emerges from our practical experience. Make every day indexable by entering it as a heading, such that any day can be accessed from an automatically-generated index on top of wiki page. Use Weekday, Month, Day, Year as standard headings - such as =Thu Oct 11, 2012=. This makes it easy to identify the Monday entry - which contain Weekly Milestones and their Review, which are written down by the person who is logging for self-evaluation, and others can assist in this evaluation as part of an open learning organization. Document in paragraph format, don't sprawl your log as long lists or subheadings - ''for compactness and ease of visual navigation''. Avoid lists whenever possible - and use a paragraph format instead. If you cannot resist using a list, use * instead of using a blank line - for compactness. Roll up entries into a single link on a monthly basis. See [[Marcin Log]] as an example, and see bottom of Marcin Log as an example of rolling entries up.		#'''Formatting''' - For the logs to be easily understandable and effective in communicating work product succinctly, we are suggesting a particular format that emerges from our practical experience. Make every day indexable by entering it as a heading, such that any day can be accessed from an automatically-generated index on top of wiki page. Use Weekday, Month, Day, Year as standard headings - such as =Thu Oct 11, 2012=. This makes it easy to identify the Monday entry - which contain Weekly Milestones and their Review, which are written down by the person who is logging for self-evaluation, and others can assist in this evaluation as part of an open learning organization. Document in paragraph format, don't sprawl your log as long lists or subheadings - ''for compactness and ease of visual navigation''. Avoid lists whenever possible - and use a paragraph format instead. If you cannot resist using a list, use * instead of using a blank line - for compactness. ''Roll up entries into a single link on a monthly basis.'' See [[Marcin Log]] as an example, and see bottom of Marcin Log as an example of rolling entries up.

	==Detailed==		==Detailed==

Marcin: /* Introduction */

2013-11-15T03:30:58Z

Introduction

← Older revision		Revision as of 03:30, 15 November 2013
Line 1:		Line 1:

			<html><iframe src="http://popcorn.webmadecontent.org/12ii_" width="640" height="403" frameborder="0" mozallowfullscreen webkitallowfullscreen allowfullscreen></iframe></html>

	=Introduction=		=Introduction=

Donovan: /* Links */

2012-11-30T22:39:24Z

Links

← Older revision		Revision as of 22:39, 30 November 2012
Line 35:		Line 35:
	=Links=		=Links=
	*See also [[OSE Rules of Engagement]]		*See also [[OSE Rules of Engagement]]

			[[Category:Logs]]

Donovan: /* Links= */

2012-11-30T22:34:54Z

Links=

← Older revision		Revision as of 22:34, 30 November 2012
Line 33:		Line 33:
	By doing this, we are pushing the limits to open collaboration and sound governance.		By doing this, we are pushing the limits to open collaboration and sound governance.

	=Links==		=Links=
	*See also [[OSE Rules of Engagement]]		*See also [[OSE Rules of Engagement]]

Donovan: /* Detailed */

2012-11-30T20:22:46Z

Detailed

← Older revision		Revision as of 20:22, 30 November 2012
Line 21:		Line 21:
	*Whenever possible, include source code. This applies to word documents, designs, CAD, calculations, spreadsheets. For example - if you post an image, upload the original file so someone else can work with it. If you upload a PDF of CAD drawings, upload the original CAD file. If a file format is unsupported, compress it first and upload as the supported .zip format.		*Whenever possible, include source code. This applies to word documents, designs, CAD, calculations, spreadsheets. For example - if you post an image, upload the original file so someone else can work with it. If you upload a PDF of CAD drawings, upload the original CAD file. If a file format is unsupported, compress it first and upload as the supported .zip format.
	*For Google doc embeds, embed the actual document and a link to that document. See [[Google Doc Embed]] example.		*For Google doc embeds, embed the actual document and a link to that document. See [[Google Doc Embed]] example.
	*For images such as Gimp - upload original file.		*For images such as [[Gimp]] - upload original file.
	*Start a video sharing channel (such as YouTube) so you can share vidoes and vlogs.		*Start a video sharing channel (such as YouTube) so you can share vidoes and vlogs.
	*For Bills of Materials, link to online sources		*For Bills of Materials, link to online sources

Marcin: /* Insights */

2012-11-30T18:27:23Z

Insights

← Older revision		Revision as of 18:27, 30 November 2012
Line 32:		Line 32:

	By doing this, we are pushing the limits to open collaboration and sound governance.		By doing this, we are pushing the limits to open collaboration and sound governance.

			=Links==
			*See also [[OSE Rules of Engagement]]

Marcin: /* Requirements */

2012-11-30T16:32:50Z

Requirements

← Older revision		Revision as of 16:32, 30 November 2012
Line 12:		Line 12:
	#'''Set monthly milestones and evaluate''' - At the beginning of the month, write down 3-5 main goals for that month. At the beginning of the next month, write down (1) what you actually accomplished in the past month; and (2), if what you actually accomplished is different than what you promised, please explain the discrepancy.		#'''Set monthly milestones and evaluate''' - At the beginning of the month, write down 3-5 main goals for that month. At the beginning of the next month, write down (1) what you actually accomplished in the past month; and (2), if what you actually accomplished is different than what you promised, please explain the discrepancy.
	#'''Write a quarterly report''' - a quarterly report can be as simple as taking the Monthly Milestones and their Evaluation from the last 3 months - and compiled. Any extra comments on emergent patterns and point of improvement should be noted. Goals for the next quarter should also be listed, and these goals should be evaluated as part of the next quarter's report.		#'''Write a quarterly report''' - a quarterly report can be as simple as taking the Monthly Milestones and their Evaluation from the last 3 months - and compiled. Any extra comments on emergent patterns and point of improvement should be noted. Goals for the next quarter should also be listed, and these goals should be evaluated as part of the next quarter's report.
	#'''Formatting''' - For the logs to be easily understandable and effective in communicating work product succinctly, we are suggesting a particular format that emerges from our practical experience. Make every day indexable by entering it as a heading, such that any day can be accessed from an automatically-generated index on top of wiki page. Use Weekday, Month, Day, Year as standard headings - such as =Thu Oct 11, 2012=. This makes it easy to identify the Monday entry - which contain Weekly Milestones and their Review, which are written down by the person who is logging for self-evaluation, and others can assist in this evaluation as part of an open learning organization. Document in paragraph format, don't sprawl your log as long lists or subheadings - ''for compactness and ease of visual navigation''. ~~Use~~ * ~~for lists~~ instead of using a blank line - for compactness. Roll up entries into a single link on a monthly basis, see bottom of [[Marcin Log~~]] for~~ example.		#'''Formatting''' - For the logs to be easily understandable and effective in communicating work product succinctly, we are suggesting a particular format that emerges from our practical experience. Make every day indexable by entering it as a heading, such that any day can be accessed from an automatically-generated index on top of wiki page. Use Weekday, Month, Day, Year as standard headings - such as =Thu Oct 11, 2012=. This makes it easy to identify the Monday entry - which contain Weekly Milestones and their Review, which are written down by the person who is logging for self-evaluation, and others can assist in this evaluation as part of an open learning organization. Document in paragraph format, don't sprawl your log as long lists or subheadings - ''for compactness and ease of visual navigation''. Avoid lists whenever possible - and use a paragraph format instead. If you cannot resist using a list, use * instead of using a blank line - for compactness. Roll up entries into a single link on a monthly basis. See [[Marcin Log]] as an example, and see bottom of Marcin Log as an example of rolling entries up.

	==Detailed==		==Detailed==

Marcin: /* Requirements */

2012-11-30T16:30:32Z

Requirements

← Older revision		Revision as of 16:30, 30 November 2012
Line 12:		Line 12:
	#'''Set monthly milestones and evaluate''' - At the beginning of the month, write down 3-5 main goals for that month. At the beginning of the next month, write down (1) what you actually accomplished in the past month; and (2), if what you actually accomplished is different than what you promised, please explain the discrepancy.		#'''Set monthly milestones and evaluate''' - At the beginning of the month, write down 3-5 main goals for that month. At the beginning of the next month, write down (1) what you actually accomplished in the past month; and (2), if what you actually accomplished is different than what you promised, please explain the discrepancy.
	#'''Write a quarterly report''' - a quarterly report can be as simple as taking the Monthly Milestones and their Evaluation from the last 3 months - and compiled. Any extra comments on emergent patterns and point of improvement should be noted. Goals for the next quarter should also be listed, and these goals should be evaluated as part of the next quarter's report.		#'''Write a quarterly report''' - a quarterly report can be as simple as taking the Monthly Milestones and their Evaluation from the last 3 months - and compiled. Any extra comments on emergent patterns and point of improvement should be noted. Goals for the next quarter should also be listed, and these goals should be evaluated as part of the next quarter's report.
	#'''Formatting''' - For the logs to be easily understandable and effective in communicating work product succinctly, we are suggesting a particular format that emerges from our practical experience ~~with logging~~. Make every day indexable by entering it as a heading, such that any day can be accessed from an automatically-generated index on top of wiki page. Use Weekday, Month, Day, Year as standard headings - such as =Thu Oct 11, 2012=. This makes it easy to identify the Monday entry - which contain Weekly Milestones and their Review, which are written down by the person who is logging for self-evaluation, and others can assist in this evaluation as part of an open learning organization. Document in paragraph format, don't sprawl your log as long lists or subheadings - ''for compactness and ease of visual navigation''. Use * for lists instead of using a blank line - for compactness. Roll up entries into a single link on a monthly basis, see bottom of [[Marcin Log]] for example.		#'''Formatting''' - For the logs to be easily understandable and effective in communicating work product succinctly, we are suggesting a particular format that emerges from our practical experience. Make every day indexable by entering it as a heading, such that any day can be accessed from an automatically-generated index on top of wiki page. Use Weekday, Month, Day, Year as standard headings - such as =Thu Oct 11, 2012=. This makes it easy to identify the Monday entry - which contain Weekly Milestones and their Review, which are written down by the person who is logging for self-evaluation, and others can assist in this evaluation as part of an open learning organization. Document in paragraph format, don't sprawl your log as long lists or subheadings - ''for compactness and ease of visual navigation''. Use * for lists instead of using a blank line - for compactness. Roll up entries into a single link on a monthly basis, see bottom of [[Marcin Log]] for example.

	==Detailed==		==Detailed==