How to Start a Working Doc - Revision history

Marcin: /* 12 Critical Elements of a Working Doc */

2022-04-05T01:09:17Z

12 Critical Elements of a Working Doc

← Older revision		Revision as of 01:09, 5 April 2022
Line 18:		Line 18:
	*This working doc has these elements of information architecture:		*This working doc has these elements of information architecture:

	<html> ~~________________________________~~ </html>		<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vTWEzJE4UgPIFDaAhiQhhZ6SoxNjy1igkGFQnOXjD4Ho-Ka9-CUGTFRmJ7ec2aHb9te4dPxxcr6piI7/embed?start=false&loop=false&delayms=3000" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

	[https://docs.google.com/presentation/d/1lcZLDXFY3twalbArBGQTniPog22mK2Nh7Wseqv1U5-I/edit#slide=id.g109eafdfe99_0_292 edit]		[https://docs.google.com/presentation/d/1lcZLDXFY3twalbArBGQTniPog22mK2Nh7Wseqv1U5-I/edit#slide=id.g109eafdfe99_0_292 edit]

Marcin: /* 12 Critical Elements of a Working Doc */

2022-04-05T01:09:01Z

12 Critical Elements of a Working Doc

← Older revision		Revision as of 01:09, 5 April 2022
Line 20:		Line 20:
	<html> ________________________________ </html>		<html> ________________________________ </html>

	[~~_______________________________________~~ edit]		[https://docs.google.com/presentation/d/1lcZLDXFY3twalbArBGQTniPog22mK2Nh7Wseqv1U5-I/edit#slide=id.g109eafdfe99_0_292 edit]

	=Future Work=		=Future Work=

Marcin: /* 12 Critical Elements of a Working Doc */

2022-04-05T01:08:55Z

12 Critical Elements of a Working Doc

← Older revision		Revision as of 01:08, 5 April 2022
Line 16:		Line 16:

	=12 Critical Elements of a Working Doc=		=12 Critical Elements of a Working Doc=
	*This working doc has ~~the~~ elements of information architecture ~~as listed on the Meta page in the working doc - [https~~:/~~/docs.google.com/presentation/d/1uU6DC73MAjaRa-acKw46kG0BiPR_F-LI58iESzyr-Fw/~~edit~~#slide=id.g109eafdfe99_0_292~~]		*This working doc has these elements of information architecture:

			<html> ________________________________ </html>

			[_______________________________________ edit]

	=Future Work=		=Future Work=

Marcin: /* Example */

2022-04-05T01:08:27Z

Example

← Older revision		Revision as of 01:08, 5 April 2022
Line 15:		Line 15:
	Note that the same principles apply to Google Spreasheets, which we use for [[BOMs]].		Note that the same principles apply to Google Spreasheets, which we use for [[BOMs]].

	=~~Example~~=		=12 Critical Elements of a Working Doc=
	*This working doc has the elements of information architecture as listed on the Meta page in the working doc - [https://docs.google.com/presentation/d/1uU6DC73MAjaRa-acKw46kG0BiPR_F-LI58iESzyr-Fw/edit#slide=id.g109eafdfe99_0_292]		*This working doc has the elements of information architecture as listed on the Meta page in the working doc - [https://docs.google.com/presentation/d/1uU6DC73MAjaRa-acKw46kG0BiPR_F-LI58iESzyr-Fw/edit#slide=id.g109eafdfe99_0_292]

	=Future Work=		=Future Work=
	*Once we have a full OSE Icon Set - such as started at [[Icon Source]] - Working Docs should use icons to clarify content types, to create diagrams, etc...		*Once we have a full OSE Icon Set - such as started at [[Icon Source]] - Working Docs should use icons to clarify content types, to create diagrams, etc...

Marcin at 22:22, 26 December 2021

2021-12-26T22:22:09Z

← Older revision		Revision as of 22:22, 26 December 2021
Line 15:		Line 15:
	Note that the same principles apply to Google Spreasheets, which we use for [[BOMs]].		Note that the same principles apply to Google Spreasheets, which we use for [[BOMs]].

			=Example=
			*This working doc has the elements of information architecture as listed on the Meta page in the working doc - [https://docs.google.com/presentation/d/1uU6DC73MAjaRa-acKw46kG0BiPR_F-LI58iESzyr-Fw/edit#slide=id.g109eafdfe99_0_292]
	=Future Work=		=Future Work=
	*Once we have a full OSE Icon Set - such as started at [[Icon Source]] - Working Docs should use icons to clarify content types, to create diagrams, etc...		*Once we have a full OSE Icon Set - such as started at [[Icon Source]] - Working Docs should use icons to clarify content types, to create diagrams, etc...

Marcin at 20:41, 10 February 2021

2021-02-10T20:41:36Z

← Older revision		Revision as of 20:41, 10 February 2021
Line 11:		Line 11:

	#Go into permissions and make sure the permissions are set to 'anyone can edit' the document. This is important. So that you don't have to grant individual permissions to users. Go ahead, that is how we work. Otherwise, if you had a large team (and our team is the whole world), the collaboration process would not scale simply because it would take too much admin time just to add everyone to the document. We'd rather be creating, not doing admin work.		#Go into permissions and make sure the permissions are set to 'anyone can edit' the document. This is important. So that you don't have to grant individual permissions to users. Go ahead, that is how we work. Otherwise, if you had a large team (and our team is the whole world), the collaboration process would not scale simply because it would take too much admin time just to add everyone to the document. We'd rather be creating, not doing admin work.
	#Make sure that this document is [[Findable]] to other team members.		#Make sure that this document is [[Findable]] to other team members

			Note that the same principles apply to Google Spreasheets, which we use for [[BOMs]].

	=Future Work=		=Future Work=
	*Once we have a full OSE Icon Set - such as started at [[Icon Source]] - Working Docs should use icons to clarify content types, to create diagrams, etc...		*Once we have a full OSE Icon Set - such as started at [[Icon Source]] - Working Docs should use icons to clarify content types, to create diagrams, etc...

Marcin at 20:13, 10 February 2021

2021-02-10T20:13:05Z

← Older revision		Revision as of 20:13, 10 February 2021
Line 3:		Line 3:
	Often in OSE development you will hear, 'let's start a working document'.		Often in OSE development you will hear, 'let's start a working document'.

	What does that mean? It means, specifically, a Google Slides, using the [[Presentation Template]], embedded in your [[Work Log]], on the current topic of exploration. Include an edit link below the document (such as at [[Presentation Template]]) - so that others can edit the document, because otherwise one cannot access edit mode and you'll be working on that document on your own.		What does that mean? It means, specifically, a Google Slides, using the [[Presentation Template]], embedded in your [[Work Log]], on the current topic of exploration. We start Working Docs as a place where we do technical diligence, past pictures, create diagrams, and otherwise develop any aspect of a development project. The relevance is not only keeping a paper trail so you can remember what you have explored - but also - for others to learn from. We treat a working doc as a place where we begin distilling vast amounts of potential information into that which results in a completed product and enterprise.


			Include an edit link below the document (such as at [[Presentation Template]]) - so that others can edit the document, because otherwise one cannot access edit mode and you'll be working on that document on your own.

	There are several keys to making sure that this document is completely open and collaborative, and therefore which could become part of a large-scale, open, collaborative development effort.		There are several keys to making sure that this document is completely open and collaborative, and therefore which could become part of a large-scale, open, collaborative development effort.

Marcin at 20:05, 10 February 2021

2021-02-10T20:05:12Z

← Older revision		Revision as of 20:05, 10 February 2021
Line 8:		Line 8:

	#Go into permissions and make sure the permissions are set to 'anyone can edit' the document. This is important. So that you don't have to grant individual permissions to users. Go ahead, that is how we work. Otherwise, if you had a large team (and our team is the whole world), the collaboration process would not scale simply because it would take too much admin time just to add everyone to the document. We'd rather be creating, not doing admin work.		#Go into permissions and make sure the permissions are set to 'anyone can edit' the document. This is important. So that you don't have to grant individual permissions to users. Go ahead, that is how we work. Otherwise, if you had a large team (and our team is the whole world), the collaboration process would not scale simply because it would take too much admin time just to add everyone to the document. We'd rather be creating, not doing admin work.
	#Make sure that this document is ~~findable~~ to other team members. This happens already if you put a link to the document on your work log. Anyone on the team will know where to find it if they know you created the document. But if somebody doesn't even know who is on the team - you can make this document findable by organizing it within the project that you are working on. This is where the [[Development Template]] comes in. Simply put the working doc at the specific deliverable of the specific project that you are working on. What if you don't even know the project name? You can find out from others, see the list of [[Genealogies]], or follow the principles of open hardware [[Taxonomy]]		#Make sure that this document is [[Findable]] to other team members.

	=Future Work=		=Future Work=
	*Once we have a full OSE Icon Set - such as started at [[Icon Source]] - Working Docs should use icons to clarify content types, to create diagrams, etc...		*Once we have a full OSE Icon Set - such as started at [[Icon Source]] - Working Docs should use icons to clarify content types, to create diagrams, etc...

Marcin: /* Introduction */

2021-02-09T22:54:38Z

Introduction

← Older revision		Revision as of 22:54, 9 February 2021
Line 8:		Line 8:

	#Go into permissions and make sure the permissions are set to 'anyone can edit' the document. This is important. So that you don't have to grant individual permissions to users. Go ahead, that is how we work. Otherwise, if you had a large team (and our team is the whole world), the collaboration process would not scale simply because it would take too much admin time just to add everyone to the document. We'd rather be creating, not doing admin work.		#Go into permissions and make sure the permissions are set to 'anyone can edit' the document. This is important. So that you don't have to grant individual permissions to users. Go ahead, that is how we work. Otherwise, if you had a large team (and our team is the whole world), the collaboration process would not scale simply because it would take too much admin time just to add everyone to the document. We'd rather be creating, not doing admin work.
	#Make sure that this document is findable to other team members. This happens already if you put a link to the document on your work log. Anyone on the team will know where to find it if they know you created the document. But if somebody doesn't even know who is on the team - you can make this document findable by organizing it within the project that you are working on. This is where the [[Development Template]] comes in. Simply put the working doc at the specific deliverable of the specific project that you are working on. What if you don't even know the project name? You can find out from others, see the list of [[Genealogies]],		#Make sure that this document is findable to other team members. This happens already if you put a link to the document on your work log. Anyone on the team will know where to find it if they know you created the document. But if somebody doesn't even know who is on the team - you can make this document findable by organizing it within the project that you are working on. This is where the [[Development Template]] comes in. Simply put the working doc at the specific deliverable of the specific project that you are working on. What if you don't even know the project name? You can find out from others, see the list of [[Genealogies]], or follow the principles of open hardware [[Taxonomy]]

	=Future Work=		=Future Work=

Marcin at 22:50, 9 February 2021

2021-02-09T22:50:33Z

← Older revision		Revision as of 22:50, 9 February 2021
Line 8:		Line 8:

	#Go into permissions and make sure the permissions are set to 'anyone can edit' the document. This is important. So that you don't have to grant individual permissions to users. Go ahead, that is how we work. Otherwise, if you had a large team (and our team is the whole world), the collaboration process would not scale simply because it would take too much admin time just to add everyone to the document. We'd rather be creating, not doing admin work.		#Go into permissions and make sure the permissions are set to 'anyone can edit' the document. This is important. So that you don't have to grant individual permissions to users. Go ahead, that is how we work. Otherwise, if you had a large team (and our team is the whole world), the collaboration process would not scale simply because it would take too much admin time just to add everyone to the document. We'd rather be creating, not doing admin work.
	#Make sure that this document is findable to other team members. This happens already if you put a link to the document on your work log. Anyone on the team will know where to find it if they know you created the document. But if somebody doesn't even know who is on the team - you can make this document findable by organizing it within the project that you are working on. This is where the [[Development Template]] comes in.		#Make sure that this document is findable to other team members. This happens already if you put a link to the document on your work log. Anyone on the team will know where to find it if they know you created the document. But if somebody doesn't even know who is on the team - you can make this document findable by organizing it within the project that you are working on. This is where the [[Development Template]] comes in. Simply put the working doc at the specific deliverable of the specific project that you are working on. What if you don't even know the project name? You can find out from others, see the list of [[Genealogies]],

	=Future Work=		=Future Work=