https://wiki.opensourceecology.org/index.php?action=history&feed=atom&title=Contract_Process 2026-05-14T02:46:54Z Revision history for this page on the wiki MediaWiki 1.39.13 https://wiki.opensourceecology.org/index.php?title=Contract_Process&diff=79116&oldid=prev 2012-11-06T06:48:41Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 06:48, 6 November 2012</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l3">Line 3:</td> <td colspan="2" class="diff-lineno">Line 3:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The following need to be specified with utmost clarity:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The following need to be specified with utmost clarity:</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*Open IP Guidelines</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*<ins style="font-weight: bold; text-decoration: none;">[[</ins>Open IP Guidelines<ins style="font-weight: bold; text-decoration: none;">]]</ins></div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Focused, non-negotiable core work plan - visible to world</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Focused, non-negotiable core work plan - visible to world</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Scope of work - what activities are and are not allowed</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Scope of work - what activities are and are not allowed</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Contract_Process&diff=79115&oldid=prev 2012-11-06T06:48:29Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 06:48, 6 November 2012</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l3">Line 3:</td> <td colspan="2" class="diff-lineno">Line 3:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The following need to be specified with utmost clarity:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The following need to be specified with utmost clarity:</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">*Open IP Guidelines</ins></div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Focused, non-negotiable core work plan - visible to world</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Focused, non-negotiable core work plan - visible to world</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Scope of work - what activities are and are not allowed</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Scope of work - what activities are and are not allowed</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Contract_Process&diff=79114&oldid=prev 2012-11-06T06:48:01Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 06:48, 6 November 2012</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l15">Line 15:</td> <td colspan="2" class="diff-lineno">Line 15:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, distibute tasks to others, and continue to define further collaborative process with the core team. The scope of such task distribution includes production of instructionals, conceptual designs, technical designs, documentation, review, and others.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, distibute tasks to others, and continue to define further collaborative process with the core team. The scope of such task distribution includes production of instructionals, conceptual designs, technical designs, documentation, review, and others.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Microinstructionals. Participants are required to document their work, and one effective way to document are vlogs and mincroinstructionals. Vlogs may be used to generate microinstructionals, which are scripted, short instructionals on mission-critical components of the project that are relevant for scaling the project via replication of [[OSE Incubators]]. In the immediate term, important microinstructionals on Factor e Farm-specific topics are also desirable. Topics specific to Factor e Farm include experimental methods which amy not necessarily be used by other OSE Incubators - but which may evolve over time towards replicability.  </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Microinstructionals. Participants are required to document their work, and one effective way to document are vlogs and mincroinstructionals. Vlogs may be used to generate microinstructionals, which are scripted, short instructionals on mission-critical components of the project that are relevant for scaling the project via replication of [[OSE Incubators]]. In the immediate term, important microinstructionals on Factor e Farm-specific topics are also desirable. Topics specific to Factor e Farm include experimental methods which amy not necessarily be used by other OSE Incubators - but which may evolve over time towards replicability.  </div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms and who <del style="font-weight: bold; text-decoration: none;">pays for </del>what. What resources are brought to the table by each party <del style="font-weight: bold; text-decoration: none;">- private</del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms <ins style="font-weight: bold; text-decoration: none;">(confidential) </ins>and who <ins style="font-weight: bold; text-decoration: none;">covers </ins>what <ins style="font-weight: bold; text-decoration: none;">costs</ins>. What resources are brought to the table by each party<ins style="font-weight: bold; text-decoration: none;">.</ins></div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes<ins style="font-weight: bold; text-decoration: none;">, and other contingencies</ins></div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Contract_Process&diff=79113&oldid=prev 2012-11-06T06:47:16Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 06:47, 6 November 2012</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l14">Line 14:</td> <td colspan="2" class="diff-lineno">Line 14:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Clear requirements on process documentation - how somebody else is to carry on a task in person&#039;s absence, or to distribute a particular task to remote collaborators.  </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Clear requirements on process documentation - how somebody else is to carry on a task in person&#039;s absence, or to distribute a particular task to remote collaborators.  </div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, distibute tasks to others, and continue to define further collaborative process with the core team. The scope of such task distribution includes production of instructionals, conceptual designs, technical designs, documentation, review, and others.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, distibute tasks to others, and continue to define further collaborative process with the core team. The scope of such task distribution includes production of instructionals, conceptual designs, technical designs, documentation, review, and others.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*Microinstructionals. Participants are required to document their work, and one effective way to document are vlogs and mincroinstructionals. Vlogs may be used to generate microinstructionals, which are scripted, short instructionals on mission-critical components of the project that are relevant for scaling the project via replication of [[OSE Incubators]]. In the immediate term, important microinstructionals on Factor e Farm-specific topics are also desirable <del style="font-weight: bold; text-decoration: none;">- for effective task allocation for temporary </del>methods - <del style="font-weight: bold; text-decoration: none;">given that methods </del>evolve over time <del style="font-weight: bold; text-decoration: none;">and multiple people are needed to carry out these tasks in order to evolve these tasks</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*Microinstructionals. Participants are required to document their work, and one effective way to document are vlogs and mincroinstructionals. Vlogs may be used to generate microinstructionals, which are scripted, short instructionals on mission-critical components of the project that are relevant for scaling the project via replication of [[OSE Incubators]]. In the immediate term, important microinstructionals on Factor e Farm-specific topics are also desirable<ins style="font-weight: bold; text-decoration: none;">. Topics specific to Factor e Farm include experimental </ins>methods <ins style="font-weight: bold; text-decoration: none;">which amy not necessarily be used by other OSE Incubators </ins>- <ins style="font-weight: bold; text-decoration: none;">but which may </ins>evolve over time <ins style="font-weight: bold; text-decoration: none;">towards replicability</ins>.  </div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms and who pays for what. What resources are brought to the table by each party - private</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms and who pays for what. What resources are brought to the table by each party - private</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Contract_Process&diff=79112&oldid=prev 2012-11-06T06:45:09Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 06:45, 6 November 2012</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l14">Line 14:</td> <td colspan="2" class="diff-lineno">Line 14:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Clear requirements on process documentation - how somebody else is to carry on a task in person&#039;s absence, or to distribute a particular task to remote collaborators.  </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Clear requirements on process documentation - how somebody else is to carry on a task in person&#039;s absence, or to distribute a particular task to remote collaborators.  </div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, distibute tasks to others, and continue to define further collaborative process with the core team. The scope of such task distribution includes production of instructionals, conceptual designs, technical designs, documentation, review, and others.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, distibute tasks to others, and continue to define further collaborative process with the core team. The scope of such task distribution includes production of instructionals, conceptual designs, technical designs, documentation, review, and others.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*Microinstructionals <del style="font-weight: bold; text-decoration: none;">- </del>scripted, <del style="font-weight: bold; text-decoration: none;">1 minute </del>instructionals on mission-critical components of <del style="font-weight: bold; text-decoration: none;">infrastructure </del>that are <del style="font-weight: bold; text-decoration: none;">intended to be scaled to </del>the [[<del style="font-weight: bold; text-decoration: none;">144 </del>Incubators]]. In the immediate term, important microinstructionals on Factor e Farm-specific topics are also desirable - for effective task allocation for temporary methods - given that methods evolve over time and multiple people are needed to carry out these tasks in order to evolve these tasks.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*Microinstructionals<ins style="font-weight: bold; text-decoration: none;">. Participants are required to document their work, and one effective way to document are vlogs and mincroinstructionals. Vlogs may be used to generate microinstructionals, which are </ins>scripted, <ins style="font-weight: bold; text-decoration: none;">short </ins>instructionals on mission-critical components of <ins style="font-weight: bold; text-decoration: none;">the project </ins>that are <ins style="font-weight: bold; text-decoration: none;">relevant for scaling </ins>the <ins style="font-weight: bold; text-decoration: none;">project via replication of </ins>[[<ins style="font-weight: bold; text-decoration: none;">OSE </ins>Incubators]]. In the immediate term, important microinstructionals on Factor e Farm-specific topics are also desirable - for effective task allocation for temporary methods - given that methods evolve over time and multiple people are needed to carry out these tasks in order to evolve these tasks.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms and who pays for what. What resources are brought to the table by each party - private</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms and who pays for what. What resources are brought to the table by each party - private</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Contract_Process&diff=79111&oldid=prev 2012-11-06T06:42:22Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 06:42, 6 November 2012</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l13">Line 13:</td> <td colspan="2" class="diff-lineno">Line 13:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Distraction management - given the integrated complexity of project, how do we assure navigation on well-defined path of responsibility</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Distraction management - given the integrated complexity of project, how do we assure navigation on well-defined path of responsibility</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Clear requirements on process documentation - how somebody else is to carry on a task in person&#039;s absence, or to distribute a particular task to remote collaborators.  </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Clear requirements on process documentation - how somebody else is to carry on a task in person&#039;s absence, or to distribute a particular task to remote collaborators.  </div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, distibute tasks to others, and continue to define further collaborative process with the core team. The scope of such task distribution includes production of instructionals, conceptual designs, technical designs, documentation, review, and <del style="font-weight: bold; text-decoration: none;">any other steps related to zero communication barriers afforded by the internet</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, distibute tasks to others, and continue to define further collaborative process with the core team. The scope of such task distribution includes production of instructionals, conceptual designs, technical designs, documentation, review, and <ins style="font-weight: bold; text-decoration: none;">others</ins>.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Microinstructionals - scripted, 1 minute instructionals on mission-critical components of infrastructure that are intended to be scaled to the [[144 Incubators]]. In the immediate term, important microinstructionals on Factor e Farm-specific topics are also desirable - for effective task allocation for temporary methods - given that methods evolve over time and multiple people are needed to carry out these tasks in order to evolve these tasks.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Microinstructionals - scripted, 1 minute instructionals on mission-critical components of infrastructure that are intended to be scaled to the [[144 Incubators]]. In the immediate term, important microinstructionals on Factor e Farm-specific topics are also desirable - for effective task allocation for temporary methods - given that methods evolve over time and multiple people are needed to carry out these tasks in order to evolve these tasks.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms and who pays for what. What resources are brought to the table by each party - private</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms and who pays for what. What resources are brought to the table by each party - private</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Contract_Process&diff=79110&oldid=prev 2012-11-06T06:40:34Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 06:40, 6 November 2012</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Contracts <del style="font-weight: bold; text-decoration: none;">for </del>OSE apply to paid staff and volunteers.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Contracts <ins style="font-weight: bold; text-decoration: none;">at </ins>OSE apply to paid staff and volunteers.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The following need to be specified with utmost clarity:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The following need to be specified with utmost clarity:</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Contract_Process&diff=78941&oldid=prev 2012-11-03T19:10:15Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 19:10, 3 November 2012</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l15">Line 15:</td> <td colspan="2" class="diff-lineno">Line 15:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, distibute tasks to others, and continue to define further collaborative process with the core team. The scope of such task distribution includes production of instructionals, conceptual designs, technical designs, documentation, review, and any other steps related to zero communication barriers afforded by the internet.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, distibute tasks to others, and continue to define further collaborative process with the core team. The scope of such task distribution includes production of instructionals, conceptual designs, technical designs, documentation, review, and any other steps related to zero communication barriers afforded by the internet.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Microinstructionals - scripted, 1 minute instructionals on mission-critical components of infrastructure that are intended to be scaled to the [[144 Incubators]]. In the immediate term, important microinstructionals on Factor e Farm-specific topics are also desirable - for effective task allocation for temporary methods - given that methods evolve over time and multiple people are needed to carry out these tasks in order to evolve these tasks.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Microinstructionals - scripted, 1 minute instructionals on mission-critical components of infrastructure that are intended to be scaled to the [[144 Incubators]]. In the immediate term, important microinstructionals on Factor e Farm-specific topics are also desirable - for effective task allocation for temporary methods - given that methods evolve over time and multiple people are needed to carry out these tasks in order to evolve these tasks.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms - private</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms <ins style="font-weight: bold; text-decoration: none;">and who pays for what. What resources are brought to the table by each party </ins>- private</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Contract_Process&diff=78901&oldid=prev 2012-11-03T16:28:10Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 16:28, 3 November 2012</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l14">Line 14:</td> <td colspan="2" class="diff-lineno">Line 14:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Clear requirements on process documentation - how somebody else is to carry on a task in person&#039;s absence, or to distribute a particular task to remote collaborators.  </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Clear requirements on process documentation - how somebody else is to carry on a task in person&#039;s absence, or to distribute a particular task to remote collaborators.  </div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, distibute tasks to others, and continue to define further collaborative process with the core team. The scope of such task distribution includes production of instructionals, conceptual designs, technical designs, documentation, review, and any other steps related to zero communication barriers afforded by the internet.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, distibute tasks to others, and continue to define further collaborative process with the core team. The scope of such task distribution includes production of instructionals, conceptual designs, technical designs, documentation, review, and any other steps related to zero communication barriers afforded by the internet.</div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">*Microinstructionals - scripted, 1 minute instructionals on mission-critical components of infrastructure that are intended to be scaled to the [[144 Incubators]]. In the immediate term, important microinstructionals on Factor e Farm-specific topics are also desirable - for effective task allocation for temporary methods - given that methods evolve over time and multiple people are needed to carry out these tasks in order to evolve these tasks.</ins></div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms - private</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms - private</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes</div></td></tr> </table>

Marcin https://wiki.opensourceecology.org/index.php?title=Contract_Process&diff=78900&oldid=prev 2012-11-03T16:24:44Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 16:24, 3 November 2012</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l13">Line 13:</td> <td colspan="2" class="diff-lineno">Line 13:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Distraction management - given the integrated complexity of project, how do we assure navigation on well-defined path of responsibility</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Distraction management - given the integrated complexity of project, how do we assure navigation on well-defined path of responsibility</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Clear requirements on process documentation - how somebody else is to carry on a task in person&#039;s absence, or to distribute a particular task to remote collaborators.  </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Clear requirements on process documentation - how somebody else is to carry on a task in person&#039;s absence, or to distribute a particular task to remote collaborators.  </div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, <del style="font-weight: bold; text-decoration: none;">involve </del>others <del style="font-weight: bold; text-decoration: none;">to take on tasks</del>, and continue to define further collaborative process with the core team.  </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>**The basic guideline for OSE work is that we intend to change culture by becoming the [[Most Collaborative Project in the World]]. In order to achieve scalability along the [[Critical Path]] and to change world culture towards open collaboration, we need to involve others. The critical way to involve remote collaborators effectively is to reduce barriers to on-boarding of those collaborators. This means educating them about our process to make an ask of them easy and transparent. For this, we use [[RACI Cubed]] (see last 2 points of this method). Therefore, we can leverage our core team to develop collaborative process, <ins style="font-weight: bold; text-decoration: none;">distibute tasks to </ins>others, and continue to define further collaborative process with the core team<ins style="font-weight: bold; text-decoration: none;">. The scope of such task distribution includes production of instructionals, conceptual designs, technical designs, documentation, review, and any other steps related to zero communication barriers afforded by the internet</ins>.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms - private</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Compensation terms - private</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Method to handle contract violations, conflict, exit, contract changes</div></td></tr> </table>

Marcin