How to Start a Working Doc: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| 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. | #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. | ||
=Future Work= | =Future Work= | ||
Revision as of 22:40, 9 February 2021
Introduction
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.
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.
- 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.
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...
- See how icons and work docs fit into massive parallel development - Extreme_Enterprise_Role_Architecture#CAD_Role_Architecture. Don't worry if this doesn't make sense to you initially, as you get familiar with the full set of open, collaborative development protocols, this will become obvious.
Exercise
- To show that you know how to start a working doc- start a working doc as described above.