Daily Log of Tasks - Revision history

Marcin: /* Introduction */

2025-11-02T20:39:25Z

Introduction

← Older revision		Revision as of 20:39, 2 November 2025
Line 18:		Line 18:
	OSE promotes the use of a Log by all individuals and projects because the key to effective global collaboration is transparency and awareness of what any other individual or team is doing. A Log is a concise summary of tasks done with numerous hyperlinks to work product. It is intended to be used primarily for documentation, planning, review, and coordination.		OSE promotes the use of a Log by all individuals and projects because the key to effective global collaboration is transparency and awareness of what any other individual or team is doing. A Log is a concise summary of tasks done with numerous hyperlinks to work product. It is intended to be used primarily for documentation, planning, review, and coordination.

	'''To set up a work log, start a page on the wiki, with page name of Yourname_Log. If that page is already taken, please set up a page named Yourfirstname_Yourlastname_Log.'''		{{check}}'''To set up a work log, start a page on the wiki, with page name of Yourname_Log. If that page is already taken, please set up a page named Yourfirstname_Yourlastname_Log.'''

	It is different than a regular Blog in that it focuses on access to work product as opposed to a narrative. Logs are intended to be quick notes, which take a few seconds of time and are therefore not a chore. They should not be as refined as Blog or some other piece of formal writing - the goal is to simply keep a record of ongoing activity with intent of maximizing collaboration. The simple theory behind a Log, and behind documentation in general - is that if it is not documented, it effectively does not exist - from the standpoint of potential collaboration on the internet. One should keep in mind that a log is a permanent record, and as such, if nobody reads it today or tomorrow, it does not mean that someone won't see it next year - if the content is relevant from a long-term perspective.		It is different than a regular Blog in that it focuses on access to work product as opposed to a narrative. Logs are intended to be quick notes, which take a few seconds of time and are therefore not a chore. They should not be as refined as Blog or some other piece of formal writing - the goal is to simply keep a record of ongoing activity with intent of maximizing collaboration. The simple theory behind a Log, and behind documentation in general - is that if it is not documented, it effectively does not exist - from the standpoint of potential collaboration on the internet. One should keep in mind that a log is a permanent record, and as such, if nobody reads it today or tomorrow, it does not mean that someone won't see it next year - if the content is relevant from a long-term perspective.

Marcin: /* Introduction */

2025-11-02T20:39:14Z

Introduction

← Older revision		Revision as of 20:39, 2 November 2025
Line 18:		Line 18:
	OSE promotes the use of a Log by all individuals and projects because the key to effective global collaboration is transparency and awareness of what any other individual or team is doing. A Log is a concise summary of tasks done with numerous hyperlinks to work product. It is intended to be used primarily for documentation, planning, review, and coordination.		OSE promotes the use of a Log by all individuals and projects because the key to effective global collaboration is transparency and awareness of what any other individual or team is doing. A Log is a concise summary of tasks done with numerous hyperlinks to work product. It is intended to be used primarily for documentation, planning, review, and coordination.

	'''To set up a work log, start a page on the wiki, with page name of Yourname_Log. If that page is already taken, please set up a page named Yourfirstname_Yourlastname_Log.		'''To set up a work log, start a page on the wiki, with page name of Yourname_Log. If that page is already taken, please set up a page named Yourfirstname_Yourlastname_Log.'''
	'''
	It is different than a regular Blog in that it focuses on access to work product as opposed to a narrative. Logs are intended to be quick notes, which take a few seconds of time and are therefore not a chore. They should not be as refined as Blog or some other piece of formal writing - the goal is to simply keep a record of ongoing activity with intent of maximizing collaboration. The simple theory behind a Log, and behind documentation in general - is that if it is not documented, it effectively does not exist - from the standpoint of potential collaboration on the internet. One should keep in mind that a log is a permanent record, and as such, if nobody reads it today or tomorrow, it does not mean that someone won't see it next year - if the content is relevant from a long-term perspective.		It is different than a regular Blog in that it focuses on access to work product as opposed to a narrative. Logs are intended to be quick notes, which take a few seconds of time and are therefore not a chore. They should not be as refined as Blog or some other piece of formal writing - the goal is to simply keep a record of ongoing activity with intent of maximizing collaboration. The simple theory behind a Log, and behind documentation in general - is that if it is not documented, it effectively does not exist - from the standpoint of potential collaboration on the internet. One should keep in mind that a log is a permanent record, and as such, if nobody reads it today or tomorrow, it does not mean that someone won't see it next year - if the content is relevant from a long-term perspective.

Marcin: /* Introduction */

2025-11-02T20:39:05Z

Introduction

← Older revision		Revision as of 20:39, 2 November 2025
Line 18:		Line 18:
	OSE promotes the use of a Log by all individuals and projects because the key to effective global collaboration is transparency and awareness of what any other individual or team is doing. A Log is a concise summary of tasks done with numerous hyperlinks to work product. It is intended to be used primarily for documentation, planning, review, and coordination.		OSE promotes the use of a Log by all individuals and projects because the key to effective global collaboration is transparency and awareness of what any other individual or team is doing. A Log is a concise summary of tasks done with numerous hyperlinks to work product. It is intended to be used primarily for documentation, planning, review, and coordination.

	To set up a work log, start a page on the wiki, with page name of Yourname_Log. If that page is already taken, please set up a page named Yourfirstname_Yourlastname_Log.		'''To set up a work log, start a page on the wiki, with page name of Yourname_Log. If that page is already taken, please set up a page named Yourfirstname_Yourlastname_Log.
			'''
	It is different than a regular Blog in that it focuses on access to work product as opposed to a narrative. Logs are intended to be quick notes, which take a few seconds of time and are therefore not a chore. They should not be as refined as Blog or some other piece of formal writing - the goal is to simply keep a record of ongoing activity with intent of maximizing collaboration. The simple theory behind a Log, and behind documentation in general - is that if it is not documented, it effectively does not exist - from the standpoint of potential collaboration on the internet. One should keep in mind that a log is a permanent record, and as such, if nobody reads it today or tomorrow, it does not mean that someone won't see it next year - if the content is relevant from a long-term perspective.		It is different than a regular Blog in that it focuses on access to work product as opposed to a narrative. Logs are intended to be quick notes, which take a few seconds of time and are therefore not a chore. They should not be as refined as Blog or some other piece of formal writing - the goal is to simply keep a record of ongoing activity with intent of maximizing collaboration. The simple theory behind a Log, and behind documentation in general - is that if it is not documented, it effectively does not exist - from the standpoint of potential collaboration on the internet. One should keep in mind that a log is a permanent record, and as such, if nobody reads it today or tomorrow, it does not mean that someone won't see it next year - if the content is relevant from a long-term perspective.

Marcin: /* Introduction */

2025-11-02T20:38:36Z

Introduction

← Older revision		Revision as of 20:38, 2 November 2025
Line 17:		Line 17:
	=Introduction=		=Introduction=
	OSE promotes the use of a Log by all individuals and projects because the key to effective global collaboration is transparency and awareness of what any other individual or team is doing. A Log is a concise summary of tasks done with numerous hyperlinks to work product. It is intended to be used primarily for documentation, planning, review, and coordination.		OSE promotes the use of a Log by all individuals and projects because the key to effective global collaboration is transparency and awareness of what any other individual or team is doing. A Log is a concise summary of tasks done with numerous hyperlinks to work product. It is intended to be used primarily for documentation, planning, review, and coordination.

			To set up a work log, start a page on the wiki, with page name of Yourname_Log. If that page is already taken, please set up a page named Yourfirstname_Yourlastname_Log.

	It is different than a regular Blog in that it focuses on access to work product as opposed to a narrative. Logs are intended to be quick notes, which take a few seconds of time and are therefore not a chore. They should not be as refined as Blog or some other piece of formal writing - the goal is to simply keep a record of ongoing activity with intent of maximizing collaboration. The simple theory behind a Log, and behind documentation in general - is that if it is not documented, it effectively does not exist - from the standpoint of potential collaboration on the internet. One should keep in mind that a log is a permanent record, and as such, if nobody reads it today or tomorrow, it does not mean that someone won't see it next year - if the content is relevant from a long-term perspective.		It is different than a regular Blog in that it focuses on access to work product as opposed to a narrative. Logs are intended to be quick notes, which take a few seconds of time and are therefore not a chore. They should not be as refined as Blog or some other piece of formal writing - the goal is to simply keep a record of ongoing activity with intent of maximizing collaboration. The simple theory behind a Log, and behind documentation in general - is that if it is not documented, it effectively does not exist - from the standpoint of potential collaboration on the internet. One should keep in mind that a log is a permanent record, and as such, if nobody reads it today or tomorrow, it does not mean that someone won't see it next year - if the content is relevant from a long-term perspective.

Marcin at 20:15, 25 October 2025

2025-10-25T20:15:24Z

← Older revision		Revision as of 20:15, 25 October 2025
Line 4:		Line 4:

	<!-- This section commented out until we have a working video link		<!-- This section commented out until we have a working video link

			=TLDR=

			Start a work log with Yourname_Log as the page title, and log your work by date with newest on top. See example at [[Marcin Log]]. Embed a time graph on top.


	=Instructional Video on How to Write a Work Log=		=Instructional Video on How to Write a Work Log=

Marcin: /* Instructions Summary */

2025-10-23T05:31:38Z

Instructions Summary

← Older revision		Revision as of 05:31, 23 October 2025
Line 30:		Line 30:

	=Instructions Summary=		=Instructions Summary=
	To start a work log, set up an account and log in to the Wiki - see [[Instructions]]. Then create a page titled Your_Name_Log - such as [[Marcin Log]]. Keep daily entries for every day Monday-Friday, and record entries with a date. The format for the dates should be placing the date in between = signs (this is a heading in Wiki language). The proper heading format is, for example, "Tue Apr 8, 2014". Then, record newer entries on top, so that one does not have to scroll down a page to see your latest work. When recording entries, you should have a link or picture embed to all that you have done.		To start a work log, set up an account and log in to the Wiki - see [[Instructions]]. Then create a page titled Your_Name_Log - such as [[Marcin Log]]. If Your Name is already taken - use your first name and last name. If that is also taken already, use your first name and last name and another unique identifier such as 2.

			Keep daily entries for every day Monday-Friday, and record entries with a date. The format for the dates should be placing the date in between = signs (this is a heading in Wiki language). The proper heading format is, for example, "Tue Apr 8, 2014". Then, record newer entries on top, so that one does not have to scroll down a page to see your latest work. When recording entries, you should have a link or picture embed to all that you have done.

	=Format=		=Format=

Marcin: /* Sample Work Logs */

2020-02-05T02:04:19Z

Sample Work Logs

← Older revision		Revision as of 02:04, 5 February 2020
Line 26:		Line 26:
	#[[Michael Log]]		#[[Michael Log]]
	#[[Abe Log]]		#[[Abe Log]]

			When we do group design work, we post many log links on the same page so people can cross reference each others' work - see [[J]] for an example.

	=Instructions Summary=		=Instructions Summary=

Marcin at 02:03, 5 February 2020

2020-02-05T02:03:12Z

← Older revision		Revision as of 02:03, 5 February 2020
Line 1:		Line 1:
	~~{{Hint\|Governance meeting voted 4-3-5 by S-A-M on Nov 1, 2018}}~~

	<span style="color:red">Last updated Nov 1, 2018 </span>		<span style="color:red">Last updated Nov 1, 2018 </span>

Marcin: /* Sample Work Logs */

2020-02-03T22:03:17Z

Sample Work Logs

← Older revision		Revision as of 22:03, 3 February 2020
Line 22:		Line 22:
	#[[Marcin Log]]		#[[Marcin Log]]
	#[[Michel Log]]		#[[Michel Log]]
			#[[Jessica Log]]
	#[[William Log]]		#[[William Log]]
	#[[Michael Log]]		#[[Michael Log]]

Marcin: /* Introduction */

2019-09-21T20:18:25Z

Introduction

← Older revision		Revision as of 20:18, 21 September 2019
Line 14:		Line 14:
	It is different than a regular Blog in that it focuses on access to work product as opposed to a narrative. Logs are intended to be quick notes, which take a few seconds of time and are therefore not a chore. They should not be as refined as Blog or some other piece of formal writing - the goal is to simply keep a record of ongoing activity with intent of maximizing collaboration. The simple theory behind a Log, and behind documentation in general - is that if it is not documented, it effectively does not exist - from the standpoint of potential collaboration on the internet. One should keep in mind that a log is a permanent record, and as such, if nobody reads it today or tomorrow, it does not mean that someone won't see it next year - if the content is relevant from a long-term perspective.		It is different than a regular Blog in that it focuses on access to work product as opposed to a narrative. Logs are intended to be quick notes, which take a few seconds of time and are therefore not a chore. They should not be as refined as Blog or some other piece of formal writing - the goal is to simply keep a record of ongoing activity with intent of maximizing collaboration. The simple theory behind a Log, and behind documentation in general - is that if it is not documented, it effectively does not exist - from the standpoint of potential collaboration on the internet. One should keep in mind that a log is a permanent record, and as such, if nobody reads it today or tomorrow, it does not mean that someone won't see it next year - if the content is relevant from a long-term perspective.

	Once you set up a Work Log, you can request a ~~time log~~ graph by using the [[Time Log Request]].		Once you set up a Work Log, you can request a timesheet (graph of your work hours) by using the [[Time Log Request]].

	The work logs are a critical tool that enables large teams, up to 1000s of people, to inspect readily what any other contributor is currently doing. Combined with [[Special:RecentChanges]], one can get self-oriented on the progress of the project.		The work logs are a critical tool that enables large teams, up to 1000s of people, to inspect readily what any other contributor is currently doing. Combined with [[Special:RecentChanges]], one can get self-oriented on the progress of the project.