Wiki source code of Local Chapters
Version 1.4 by Patrick Masson on 2018/07/02 18:15
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | : | ||
| 2 | |||
| 3 | ((( | ||
| 4 | = DIscussion = | ||
| 5 | ))) | ||
| 6 | |||
| 7 | ((( | ||
| 8 | Strengths: characteristics of the project that gives it an advantage over others | ||
| 9 | |||
| 10 | * local chapters can operate under guidelines set by HQ, and must adopt bylaws that are approved by a committee of volunteers (sort of like our working groups / incubator projects). | ||
| 11 | * Submit annual plan/review to ensure alignment | ||
| 12 | * As open source continues to gain adoption and awareness, there's a possibility that other groups will form independently to support open source, and may not even be aware of OSI. Chapters will provide a resource for those interested in forming groups. | ||
| 13 | |||
| 14 | Weaknesses: characteristics that puts the project at a disadvantage relative to others | ||
| 15 | |||
| 16 | * Dissolution of brand, "OSI" vs. "OSI UK" | ||
| 17 | * Alignment with other OSI efforts (FLOSSCC and Affiliates) | ||
| 18 | * Official role of and autonomy of members/activities | ||
| 19 | * Scope of authority: defining their own licensing. | ||
| 20 | |||
| 21 | Opportunities: elements that the project could exploit to its advantage | ||
| 22 | |||
| 23 | * Extends reach: | ||
| 24 | ** local groups can host local events | ||
| 25 | ** Local chapter members can attend local events on OSI's behalf | ||
| 26 | * Extends resources | ||
| 27 | ** Increase membership | ||
| 28 | |||
| 29 | Threats: elements in the environment that could cause trouble for the business or project | ||
| 30 | |||
| 31 | * Fracturing of the OSI community | ||
| 32 | * Fracturing of the OSI mission | ||
| 33 | ))) | ||
| 34 | |||
| 35 | == Other considerations == | ||
| 36 | |||
| 37 | It may be that we work with existing Affiliates, user groups, etc. to create OSI related activities, ensuring groups that exist for their own reasons become affiliated and are grouped with other regional affiliates in structures that mutually support and develop them. | ||
| 38 | |||
| 39 | = Charter = | ||
| 40 | |||
| 41 | The Open Source Initiative (OSI) is a non-profit corporation with global scope whose mission is,// **to educate about and advocate for the benefits of open source and to build bridges among different constituencies in the open source community**//. | ||
| 42 | |||
| 43 | |||
| 44 | The local chapter commits to upholding the mission, values and objectives of the Open Source Initiative and the Open Source Definition. | ||
| 45 | |||
| 46 | The local chapter recognizes that the OSI is the sole steward of the Open Source Definition (OSD), and the only recognized body for reviewing and approving licenses as OSD-conformant. | ||
| 47 | |||
| 48 | The local chapter acknowledges only licenses approves through the OSI License Review Process can be referred to as "open source software licenses." | ||
| 49 | |||
| 50 | The local chapter agrees only software distributed with an OSI approved open source license should be labeled "open source software" | ||
| 51 | |||
| 52 | |||
| 53 | Must meet once a month and provide notes of discussions / activities. | ||
| 54 | |||
| 55 | Must submit annual plan / review to OSI to ensure alignment. | ||
| 56 | |||
| 57 | |||
| 58 | Chapter leadership will be current individual members of the OSI. | ||
| 59 | |||
| 60 | Members, officials may not present themselves (e.g. activities, statements) as representatives of the OSI. | ||
| 61 | |||
| 62 | Agrees to abide by the OSI Trademark Guidelines. | ||
| 63 | |||
| 64 | Must gain OSI approval for any other partnerships, endorsements, sponsorships, affiliations. | ||
| 65 | |||
| 66 | Continued recognition as an OSI Chapter is ultimately at the sole discretion of the OSI Board of Directors. |