Summary

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

Details

Page properties

Content

...	...	@@ -23,8 +23,7 @@
23	23
24	24	* http://osi.xwiki.com/bin/Projects/draft-flow-syllabus
25	25	* The OSI Board wants to use osi.xwiki.com as its platform for collaborative content and discussion of issues;
26		-* Refined content is then pushed to opensource.org website
27		-* The "current version" can be occasionally updated. The dev environment remains the wiki.
	26	+Refined content is then pushed to opensource.org website the "current version" is occasionally updated while the wiki is the dev environment
28	28
29	29	== (b) What's the best structure and environment for us to maintain the master? ==
30	30
...	...	@@ -56,7 +56,7 @@
56	56	* The OSI-EDU-WG can be comprised of several "Theme-Based" Subject Matter Experts and Content Contributors
57	57	* Example 1: "License Compliance Theme" with a community of lawyers;
58	58	* Example 2: "Project Management Theme" with a community from the PM discipline;
59		-* **Follow-up thought by Joseph (after the meeting):** //I think it might be strategic to NOT segregate the WG into discipline ghettos (lawyers, economists, project management methodologists). The risk is that they end up taking past each other. The WG themes are currently topic-based and inter-disciplinary. Before we break the WG into separate working communities by professional field, let's assemble the initial interdiscplinary working group. Granted that interdisciplinary discussions are inherently harder to do, but they force us to address the very issues that make them difficult.//
	58	+* **Follow-up thought by Joseph (after the meeting):** //I think it might be strategic to NOT segregate the WG into discipline ghettos (lawyers, economists, project management methodologists). The risk is that they end up taking past each other. The WG themes are currently topic-based and inter-disciplinary. Before we break the WG into separate working communities by professional field, let's assemble the initial interdiscplinary working group. Granted that interdisciplinary discussions are inherently harded to do, but it forces us to address the issues that make them difficult.//
60	60	* We need an initial draft an email explaining the FLOW Syllabus resource << Joseph will provide an initial description for the introductory emails
61	61	* We should say where the initial funding is from (Joseph will check on permission)
62	62	* The intro email invite participation via the weekly teleconf call