OSE Chapters 2019

Introduction

There are 2 forms of affiliations with OSE. One is OSEx, modeled after TEDx, which are independently organized entities. Are they part of OSE? Not legally or formally - they are independent. OSE encourages others to start up of OSEx operations - independent entities - which can be considered like the user groups of Linux, affinity groups, meetups, hackathons and other like-minded gatherings that follow OSE in principle. This is a casual entity, which still follow OSEx Guidelines. When it comes to following OSE techniques in practice - formal OSE Chapters are created.

For serious development along the lines of core OSE efforts, chapters may be created. The intent for any chapter leader is to transition to a full-time OSE developer on a 6 month time scale, consistent with the mass creation of livelihoods via Distributive Enterprise. These chapters coordinate work with OSE International - for adherence to the 20 year OSE Roadmap. Specific projects are agreed upon on an annual basis, and a collaboration plan is proposed. 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 - where OSE's scaling plan is to work with collaborators who spend 50% of their time to run established Distributive Enterprises, and 50% of their time to do OSE R&D work. We are currently recruiting Distributive Entrepreneurs - and one such position will be dedicated to community management of Chapters relationships. In our usual dogfooding style, we are interested in all OSE collaborators understanding OSE culture - such that even our administrators are required to run workshops themselves - so they have a deep understanding of translating knowledge into tangible products.

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 at least one open source product and distribute this enterprise per yeat in collaboration with OSE
3. Minimum of 10 hour per week commitment on average, developing an open source product with OSE based on creating viral enterprises that fund future OSE development
4. Developing and running Extreme Manufacturing Workshops in collaboration with OSE
5. Participating in OSE's annual Boot Camp
6. 2 Founding members who serve as contacts
7. Internet presence with regular updates, commits, and logs
8. Participation in regular Design Sprints, as in the OSE Roadmap

Benefits

Benefits include:

1. Recognition as entities approved under the OSE brand, with allowed use of the OSE brand to promote opportunities
2. After 2 years of proven track record, chapters may apply for fiscal sponsorship under OSE.
3. Access to publishing on the OSE blog and social media
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.
7. Access to publicity though OSE via postings on any content directly related to core development
8. Direct communication with core OSE developers
9. Priority access to collaboration on OSE Extreme Manufacturing workshops

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

Ambassadors

Ambassadors are people who have been involved with OSE and who understand OSE's development procedures, goals, and culture. Involvement in OSE may include Design Sprints, Dedicated Project Visits, participation in webinars, participation on Work Teams,participation in True Fans Hangouts, participating in OSE's workshops, or others. For remote collaborators, the best way to get involved in our learning community is to sign up for Design Sprints. To do this, please fill out our Tech Team Culturing Survey.

Ambassadors are the active members of OSE, and as such, are expected to participate in Design Sprints, Working Teams, and training Webinars.

After gaining experience in OSE development, 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. Such individuals will be featured on our website, including the experience they have with OSE, such as the skills or badges that they have gained.

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