Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,3 +1,5 @@
	1	+[[image:flow-banner.png]]
	2	+
1	1	= __The FLOW Syllabus__ //(Version 1.20)// =
2	2
3	3	**Under Construction**:\\
...	...	@@ -96,7 +96,7 @@
96	96
97	97	◐ "Perspectives Identification Discussion Template":/attachments/5995/PerspectivesIdentification_DiscussionTemplate.pdf ◑
98	98
99		-*
	101	+* \\
100	100	** Intellectual Provenance
101	101	— Electronic Discovery in Canada: Best Practices and Guidelines http://www.cch.ca/_resources/pdf/ebook/b109.pdf
102	102	— How might your current practices be improved to make it easier for you lawyers to help you in the event of litigation?
...	...	@@ -112,7 +112,7 @@
112	112
113	113	==== ☏ __Audio File (pending):__ Listen to a Discussion with an Invited Authority on the Composite International Legal Environment Governing Copyrights, Patents and Contracts (Part 1) ====
114	114
115		-> //Various domains of law affect computer program developers, and managers, and the organizations they work for. Their own legal incorporation, and that of each of their clients, may be state/provincial or national. And yet the developers, and managers may participate in free/libre/open works with globally-distributed co-authors and co-managers. Many multinational/multilateral organizations have employees located in multiple countries who participate in free/libre projects under rules of employment particular to their state/provincial or national jurisdictions and types of employers (commercial, charitable, educational, governmental, multilateral). In addition to the differences of semantic meaning of words across languages and contextually different concepts across cultures, formal laws and contracts are codified within different state/province, national, pluri-national, and multi-national legal jurisdictions. How should developers and development team managers take into account this deeply heterogeneous legal environment? What obvious pitfalls can be avoided? What risks must just be accepted?//
	117	+>//Various domains of law affect computer program developers, and managers, and the organizations they work for. Their own legal incorporation, and that of each of their clients, may be state/provincial or national. And yet the developers, and managers may participate in free/libre/open works with globally-distributed co-authors and co-managers. Many multinational/multilateral organizations have employees located in multiple countries who participate in free/libre projects under rules of employment particular to their state/provincial or national jurisdictions and types of employers (commercial, charitable, educational, governmental, multilateral). In addition to the differences of semantic meaning of words across languages and contextually different concepts across cultures, formal laws and contracts are codified within different state/province, national, pluri-national, and multi-national legal jurisdictions. How should developers and development team managers take into account this deeply heterogeneous legal environment? What obvious pitfalls can be avoided? What risks must just be accepted?//
116	116
117	117	◐ "5-10-40 Discussion Template":/attachments/5993/5-10-40_DiscussionTemplate.pdf ◑
118	118
...	...	@@ -445,9 +445,8 @@
445	445	* Concerns and Challenges
446	446	* Interests and Opportunities
447	447
	450	+==== The Free/Libre/Open Way Part 2: Multi-Entity Team and Organizational Performance ====
448	448
449		-==== The Free/Libre/Open Way Part 2: Multi-Entity Team and Organizational Performance ===
450		-
451	451	* Concepts, definitions, boundary of application, measurement, feedback
452	452	* Multi-Organizational Teams
453	453	** Risky Trust: How Multi-entity Teams Develop Trust in a High Risk Endeavor http://www.hbs.edu/research/pdf/11-089.pdf
...	...	@@ -472,21 +472,21 @@
472	472
473	473	* **Linux Foundation* http://www.linuxfoundation.org/about/bylaws
474	474	— A Guide to the Kernel Development Process https://www.kernel.org/doc/Documentation/development-process/1.Intro
475		-— Open Source Compliance Publications http://www.linuxfoundation.org/publications/compliance********
	476	+— Open Source Compliance Publications http://www.linuxfoundation.org/publications/compliance**********
476	476
477	477	* **OpenStack Foundation* https://wiki.openstack.org/wiki/Governance/Foundation/Bylaws
478	478	— Contribute to OpenStack / Community https://wiki.openstack.org/wiki/Main_Page
479		-— http://www.openstack.org/legal/********
	480	+— http://www.openstack.org/legal/**********
480	480
481	481	* **Eclipse Foundation* http://www.eclipse.org/org/documents/
482		-— Eclipse Development Process http://www.eclipse.org/projects/dev_process/development_process_2011.php********
	483	+— Eclipse Development Process http://www.eclipse.org/projects/dev_process/development_process_2011.php**********
483	483
484	484	* **Apache Foundation* http://www.apache.org/foundation/
485		-— Open Source Software Peer Review Practices: A Case Study of the Apache Server http://faculty.salisbury.edu/~xswang/research/papers/serelated/testing/p541-rigby.pdf********
	486	+— Open Source Software Peer Review Practices: A Case Study of the Apache Server http://faculty.salisbury.edu/~xswang/research/papers/serelated/testing/p541-rigby.pdf**********
486	486
487	487	* **LLVM* (not a foundation but still interesting for us)
488	488	— LLVM Developer Policy http://llvm.org/docs/DeveloperPolicy.html
489		-— Life of an Instruction in LLVM http://eli.thegreenplace.net/2012/11/24/life-of-an-instruction-in-llvm/********
	490	+— Life of an Instruction in LLVM http://eli.thegreenplace.net/2012/11/24/life-of-an-instruction-in-llvm/**********
490	490
491	491	* Other Interesting Foundations
492	492	** R Foundation http://www.r-project.org/foundation/Rfoundation-statutes.pdf