OSE Chapters 2019

Introduction

For serious development along the lines of core OSE efforts, OSE encourages the creation of OSE Chapters. The intent for any chapter leader is to transition to full time open source product development towards creating the open source economy - consistent with OSE's goal of mass creation of right livelihoods via Distributive Enterprise.

Chapters coordinate work with OSE International - for adherence to the 20 year OSE Roadmap. All chapters are expected to work on the current priorities of OSE, such that clear development velocity is visible towards the creation of Distributive Enterprise, as opposed to multiple projects with limited effort in each project. OSE Chapters are required to undergo an application process, and good standing is verified as an administrative function of OSE international.

Currently (2016), OSE is developing its Distributive Enterprise program. The goal is to develop viable enterprises that help to scale the OSE movement by bootstrap funding further development

First, an official OSE chapter pursues work towards the completion of the GVCS. The basic thematic requirement for OSE chapter is having a clear answer to "How does the proposed work of a Chapter contribute to the OSE Roadmap?"

First, OSE is developing the GVCS according to OSE Specifications.

OSE Chapter Requirements

Requirements for chapters are:

1. Initial Application
2. Chapter Charter and 3 Year Vivid Vision - defining commitment to developing open source products in collaboration with OSE
3. Minimum of 40 hours per week commitment on average per Chapter, with a minimum of 2 Chapter Co-founders participating in this effort on a regular basis.
4. Developing and running Extreme Manufacturing Workshops in collaboration with OSE
5. Participating in OSE's annual Boot Camp
6. Minimum of 2 Founding members who serve as chapter contacts, and minimum of 2 active contributors at all times.
7. Duration of effort is 1 year, with option for renewal on a yearly basis as specified in the Charter. 2 Year and longer charters are possible for chapters in good standing
8. Internet presence with regular updates, commits, and logs
9. Participation in weekly Development Team meetings by at least one chapter represrntative
10. Setting up a development network on the OSE Minds platform.

Prerequisites

• Minimum of 2 Co-Founders
• Co-Founders are current members of OSE as OSE Developers
• At least one chapter member has received the OSE Process Manager skill badge, so that the chapter is adept in running an effective development process according to OSE best practices. An OSE Developer may consider applying for the Process Manager certification after serving one complete development cycle as an OSE Developer

Benefits

Benefits include:

1. Usage of the OSE Chapter Logo for brand identity throughout the duration of their Charter
2. Potential access to OSE's tax exempt status for charitable contributions
3. Potential access to publishing on OSE channels
4. Invitation to Team Leadership training and other skills training seminars
5. Being featured on the OSE site as part of the OSE Team
6. Invitation to an annual team retreat

Core Contract

• Representing OSE as Ambassadors
• Fully endorsing open culture, OSHWA compliant
• Working on expanding the scope of Open Source to Useful Source and Distributive Enterprise
• Working collaboratively on developing open economic models (distributive enterprise) that can help participants carry on continued development

OSE Ambassadors

Ambassadors are people who have been involved with OSE and who understand OSE's development procedures, goals, and culture. To become an official OSE Ambassador, candidates are required to serve at least one 90 day development cycle as an OSE Developer or OSE Documenter, and be in good standing.

Experience or involvement in OSE may include OSE Developers, Design Sprints, Book Sprints, Dedicated Project Visits, participation in webinars, participation on Work Teams, participation in True Fans Hangouts, participating in OSE Workshops, or others. For remote collaborators, the best way to get involved in our learning community is to sign up as an OSE Developer or OSE Documenter.

OSE has shifted its focus from ad-hoc development to all contributors working as part of an integrated team. This team is responsible for moving the current Critical Path forward, consistent with OSE Priorities, and along the long term OSE Development Roadmap. Ambassadors are the active members of OSE, and as such, are expected to be part of the core Development Team.

After gaining experience in OSE development process, Ambassadors are encouraged to undergo an assessment with OSE's Community Manager. The formal status of an OSE Ambassador means that the individual has had experience, training, and has met the qualifications of Ambassadorship. Ambassadors who pass the Ambassador Exam

Chapter Collaboration Standards

The guidelines for enhancing collaboration between chapters include:

• Using an official software selection such that templates and documents can be shared effectively, using FLOSS/H whenever possible. Some of the software is

• Mediawiki - templates can be shared
• Wordpress - templates
• FreeCAD - to share parts libraries. Sketchup should be phased out eventually, as an OSE cloud repository is created
• KiCAD
• phpList or other free email software
• LibreCAD
• SweetHome 3D
• OSGeo Live
• Kdenlive - for collaborative video editing where the edit file is shared and large files are downloaded from ready-access repositories such as YouTube
• Troublemaker as the official prototyping 3D printer
• YouTube
• Diaspora, Facebook, and Twitter as the official social media sites

• Chapters should organize around creating highly effective Working Teams.
• Monthly Global Chapters meeting
• Chapter leaders qualify to be posted on Team page
• Presence on OSE Forum
• Potentially sharing Web Admin duties
• Documenting tools used - such that
• Using and developing Icon Source
• Using and developing commong skills Badges, which are part of the Icon Source
• For social media, #OSEcology and other hashtags should be used commonly
• For social media, other chapters should be mentioned on a regular basis
• For the OSE Newsletter, a monthly update from chapters should be included

Working Teams

Working Teams should have members, team leaders, SME advisors, and leadership mentors.

Culture

Open Source distributive enterprise significance I the highest end state value of OSE. Chapters that focus on this will receive the most support from OSE International.

Open Source Consortium

An organization of practitioners in the subject matter area who agree to work openly to OSHWA standards.

Consortium role is to create a mechanism for crowd involvement via leadership, technical and organizational.

Internet Presence

For clear Chapter communications and identity, the OSE chapters should be identified on the Team Page.

Meta

See also OSE Chapters Strategy. Replication of OSE work is only beginning, and it is important to formalize this process as OSE grows. A good example to build on is the Open Knowledge Foundation Chapters. The OSE program will be expanded upon in the OSE Strategic Plan.

Links

• WikiHouse chapters -
• American Society of Civil Engineers - student chapters guidelines - [1]
• OKFN - chapters page -
• OSHWA - chapters page -
• OSE Team Charter

Candidates

OSE Europe, Austria (Leopold Zyka), Italy, France, Poland (Pawel Sroczynski), Greece, Germany, Spain, Sweden; Arizona (James Quaid); Texas; Canada; Chile; India; Caribbean; New Zealand; Australia (Paul Garner-Stephen); Slovenia (Luka Mustafa), Andrew Martz; Yousif (PC Workshop). Harold Westrich. Philip Jankoski. Priyanka.

Existing Efforts

• OSE France - twitter

Links

• Chapter Notes