Open Source Process Design - Revision history

Mac: /* Bootstrapping */

2007-04-12T12:18:08Z

‎Bootstrapping

Jonmc12: /* Community Committee */

2006-06-09T13:00:41Z

‎Community Committee

Jonmc12: /* Repository Committee */

2006-06-09T12:59:44Z

‎Repository Committee

Jonmc12: /* Repository Committee */

2006-06-09T03:37:05Z

‎Repository Committee

Jonmc12: /* Design and Change */

2006-06-09T03:28:25Z

‎Design and Change

Jonmc12: /* Community Goals */

2006-05-15T03:07:24Z

‎Community Goals

Jonmc12: /* Community */

2006-05-15T03:04:44Z

‎Community

Jonmc12: /* Repository Architecture */

2006-05-15T03:04:16Z

‎Repository Architecture

Jonmc12: /* Bootstrapping */

2006-05-15T03:03:14Z

‎Bootstrapping

Jonmc12: /* Goals */

2006-05-15T03:02:18Z

‎Goals

@@ Line 7: / Line 7: @@
 ===Bootstrapping===
-Sets forth the principles of Bootstrapping as interpretted by the organization
+Sets forth the principles of [[Bootstrap]]ping as interpretted by the organization
 ===Repository Architecture===

@@ Line 37: / Line 37: @@
 ===Community Committee===
-Role:  To implement initiatives within the Bootstrap community.  May include the forming of sub-committees to implement specific initiatives.  These initiatives do not have to be initiated by the Repository Committee, but they can be moderated by either the Repository Committee or the Bootstrap Committee.
+Role:  To implement initiatives within the Bootstrap community.  May include the forming of sub-committees to implement specific initiatives.  These initiatives do not have to be initiated by the Information Committee, but they can be moderated by either the Information Committee or the Bootstrap Committee.
-Members:  Volunteers heading up bootstrap initiatives, a representative or two from Repository committee, nomitated/elected members.
+Members:  Volunteers heading up bootstrap initiatives, a representative or two from Information committee, nomitated/elected members.
 Meeting Frequency/Purpose:  The group, and sub-groups will meet as often as required to implement initiatives.  The committee is responsible for acquiring resources, and executing process as it relates to implementing initiatives.

@@ Line 27: / Line 27: @@
 Meeting Frequency/Purpose:  The group will meet initially to outline a charter.  The committee may only need to meet 1-2 times per year to review the community goals and bootstrapping principles as relevant to the community.  The committee will also review the status of the community, their compliance to these goals and principles, and any changes required (this would be required in the case that the scope of the change is beyond community self-moderation).
-===Repository Committee===
+===Information Committee===
-Role:  The Repository Committee will define the types of knoweldge and tools that can be found within the Bootstrap Group.  They will actively work to architect these groups so that they meet the goals laid forth by the Bootstrap Committee.
+Role:  The Information Committee will define the types of knoweldge and tools that can be found within the Bootstrap Group - the 'Repository'.  They will actively work to architect these groups so that they meet the goals laid forth by the Bootstrap Committee, are relavent to member needs, and work together efficiently.
 Members:  Volunteers heading up bootstrap initiatives, a representive from Bootstrap Committee, and a couple nominated/elected members.

@@ Line 33: / Line 33: @@
 Members:  Volunteers heading up bootstrap initiatives, a representive from Bootstrap Committee, and a couple nominated/elected members.
-Meeting Frequency/Purpose:  The group will meet initially to map out current bootstrap activity (Boot Boards, Boot Rap, Book Club, Sub Groups, the wiki, Bootstrap Student, etc), and then suggest changes and actions in accordance with the community goals.  From there the committee should meet roughly every 1-2 months to review the status of the 'Repository'.
+Meeting Frequency/Purpose:  The group will meet initially to map out current bootstrap activity (Boot Boards, Boot Rap, Book Club, Sub Groups, the wiki, Bootstrap Student, etc), and then suggest changes and actions in accordance with the community goals.  This committee will also be responsible for the review of Business models used within the group as they relate to the community.  From there the committee should meet roughly every 1-2 months to review the status of the 'Repository'.
 ===Community Committee===

← Older revision		Revision as of 03:28, 9 June 2006
Line 18:		Line 18:

	==Design and Change==		==Design and Change==
		+
		+	===Bootstrap Committee===
		+
		+	Role: The Bootstrap committee will define both the goals of the community, as well as the interpretation of bootstrapping principles as they relate to the design of the community. The Bootstrap community will also monitor the implementation efforts of other committees for compliance to these goals and principles.
		+
		+	Members: Invited by committee, nominated/elected by committee/community. (actual rules to be defined by committee)
		+
		+	Meeting Frequency/Purpose: The group will meet initially to outline a charter. The committee may only need to meet 1-2 times per year to review the community goals and bootstrapping principles as relevant to the community. The committee will also review the status of the community, their compliance to these goals and principles, and any changes required (this would be required in the case that the scope of the change is beyond community self-moderation).
		+
		+	===Repository Committee===
		+
		+	Role: The Repository Committee will define the types of knoweldge and tools that can be found within the Bootstrap Group. They will actively work to architect these groups so that they meet the goals laid forth by the Bootstrap Committee.
		+
		+	Members: Volunteers heading up bootstrap initiatives, a representive from Bootstrap Committee, and a couple nominated/elected members.
		+
		+	Meeting Frequency/Purpose: The group will meet initially to map out current bootstrap activity (Boot Boards, Boot Rap, Book Club, Sub Groups, the wiki, Bootstrap Student, etc), and then suggest changes and actions in accordance with the community goals. From there the committee should meet roughly every 1-2 months to review the status of the 'Repository'.
		+
		+	===Community Committee===
		+
		+	Role: To implement initiatives within the Bootstrap community. May include the forming of sub-committees to implement specific initiatives. These initiatives do not have to be initiated by the Repository Committee, but they can be moderated by either the Repository Committee or the Bootstrap Committee.
		+
		+	Members: Volunteers heading up bootstrap initiatives, a representative or two from Repository committee, nomitated/elected members.
		+
		+	Meeting Frequency/Purpose: The group, and sub-groups will meet as often as required to implement initiatives. The committee is responsible for acquiring resources, and executing process as it relates to implementing initiatives.

@@ Line 3: / Line 3: @@
 ===Community Goals===
-Defines the role of the 'Bootstrap Repository', the desired role/experience of members, the desired role of the contributors, and the desired implementation of the moderation function.
+Defines the role of the 'Bootstrap Repository', the desired role/experience of members, the desired role of the contributors, and the desired implementation of the moderation function.  These goals define the required function of the organization and ultimately are responsible for the design of the Bootstrap Repository.
 ===Bootstrapping===

← Older revision		Revision as of 03:04, 15 May 2006
Line 14:		Line 14:

	===Community===		===Community===
		+
		+	All community interaction and rules should be directly related to the structure of the repository. These will be as dynamic as the repository itself.

	==Design and Change==		==Design and Change==

@@ Line 10: / Line 10: @@
 ===Repository Architecture===
 ===Community===
 ==Design and Change==

← Older revision		Revision as of 03:03, 15 May 2006
Line 6:		Line 6:

	===Bootstrapping===		===Bootstrapping===
		+
		+	Sets forth the principles of Bootstrapping as interpretted by the organization

	===Repository Architecture===		===Repository Architecture===

@@ Line 1: / Line 1: @@
 ==Structure==
-===Goals===
+===Community Goals===
 Defines the role of the 'Bootstrap Repository', the desired role/experience of members, the desired role of the contributors, and the desired implementation of the moderation function.