OSE Chapters 2019

Introduction

There is significant interest in starting OSE-related efforts worldwide. Here we describe OSE's needs and requirements for these chapters to contribute significantly to OSE development.

Chapters can be local or regional - for example - cities, states or countries. Scope is determined by the Chapter's representation.

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 GVCS completion according to OSE Specifications."

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

Requirements for chapters are:

1. Becoming an Ambassador for OSE. An ambassador is a person familiar with OSE'sa: the mission and vision of OSE, OSE Specifications, the distinction between open source and noncommercial licenses, OSE's open source software policy, the GVCS product ecology, the current state of OSE, OSE's current projects, OSE's forum, GRAS Industry standard mashup approach, social media standards, the development methodology of OSE, wiki editing and logging, CAD standards, collaborative video editing standards. Ambassadors are also required to take 3 OSE webinars: (1) OSE overview, OSE development methods, and OSE culture.
2. 2 Founding members who serve as contacts
3. Internet presence with regular updates, commits, and logs
4. commitment to developing one or more of the GVCS tools
5. Adherenece to OSE Specifications for development
6. Monthly global Chapters Meeting for updates and collaboration
7. Open and ongoing collaboration
8. Participation in Monthly leadership training seminars
9. A design sprint held at least once per month.

Benefits include:

1. Allowed use of the OSE btlrand to further development 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.

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 -