User:Rphyrin/LCCWG

The Local Chapters and Communities Working Group (LCCWG) is tasked with :

• finding and implementing ways for the Foundation to support the growth of local communities
• facilitate a global exchange of ideas and support among Local Chapters and communities
• potentially encourage established communities to further organise themselves and eventually formally affiliate with the Foundation as one of its Local Chapters
• review and suggest improvements to the Local Chapters affiliation scheme

The following are the three focus items that the working group will concentrate on :

• Building local community cohesion : We will explore and develop ideas for the Foundation support the growth of Local Chapters and local communities, including helping mappers communicate or meet up with other local mappers, and working to reduce the challenges created by the fragmented nature of OSM.
• Facilitating a global exchange of ideas : We will aim to provide Local Chapters and local communities with venues and communication channels to exchange ideas and share best practices in growing their communities.
• Improving the Local Chapters affiliation scheme : We will review the role of Local Chapters within the Foundation and the interactions between them. Based on our findings we will make recommendations to the Board as to how the affiliation scheme can be improved to provide a stronger case for local communities to eventually become Local Chapters, or possibly suggest creating new affiliation models such as less-formal user groups.

The alternative affiliation scheme

Currently, the OSMF only recognizes geography-based Local Chapters as affiliates of the Foundation. As of writing, the Foundation has now recognized 18 Local Chapters.

It was observed that having Local Chapters as our only affiliation model is too limiting and sometimes provides a high or unreachable burden for various OSM communities worldwide.

Taking a leaf from other open-data and open-knowledge communities, it was recognized that other forms of affiliation model would be good to have to address barriers that OSM local communities face, such as (1) bureaucratic process in registering as a non-profit organization and (2) commercial activities of non-profit organizations viewed as bad when it is a way to fundraise for the organization.

One suggested model is to have a lightweight user group model that can be used in lieu of or as a stepping stone to Local Chapter status. Another model is to also recognize thematic groups or communities such as Youthmappers, GeoChicas, etc.

LCCWG welcome your ideas on how we can improve affiliation scheme in OSMF through this thread and wikipage!

LCCWG highly encourage you to join LCCWG to help us advance this agenda.

Draft A

Proposed Schemes	Requirements for affiliation	Way for affiliation	Obligations	Advantages	Way for the periodic evaluation of the affiliation	Way for people indicate irregular situations (like an Ombudsman)
OSMF Local Community	One president and a minimum of two members are required. The president must have contributed to OpenStreetMap on at least 42 calendar days within the past year (365 days). The remaining members must each have an OpenStreetMap account. The group's name should be "OpenStreetMap ((region name))," where "region name" can represent cities, villages, or other types of toponyms. All of the group's members should be domiciled in that region. An outline of the group's planned activities for the first year must be provided.	Registration via OSM OAuth-based web forms	Uniting mappers in the area to establish a region-specific consensus on how things should be mapped and to collaborate in addressing local vandalism. Providing formal representation to local government, organizations, or institutions. Ensuring that local data users adhere to OpenStreetMap’s licensing and attribution requirements. To document prominent OSM objects in their respective region on the OSM Wiki, providing each with additional details such as stories and histories related to those OSM objects (optional). Monthly activity report	Public recognition of the group’s affiliation with the OSMF	Each year, the groups would be evaluated by the LCCWG. The groups would either be recertified or would be dissolved for lack of interest, Members, etc.	A public whistleblowing system that can be accessed by anyone.

Reviews of Affiliation Models from Other Open Communities

Schemes	Requirements for affiliation	Way for affiliation	Obligations	Advantages	Way for the periodic evaluation of the affiliation
Wikimedia User Groups Link	A minimum of three mature, active accounts 300 or more contributions to a Wikimedia project on a registered account that has existed for more than 6 months) with a good track record in the movement. Two designated contacts for Wikimedia Foundation. A (suggested) minimum of ten members. A clear definition of scope and purpose Signing several agreements and a code of conduct. Letter of intent to all affected/overlapping Wikimedia projects and movement affiliates. As a group, it must be independent from other Wikimedia organizations. An outline of the group's planned activities for the first year. Group's logo	Online registration through the Wikimedia user group application page.	At least one a year offline and online activities to support Wikimedia	Public recognition of the group’s affiliation with the Wikimedia Foundation Merchandise support for outreach efforts Recognition from the Affiliations Committee allows a group to apply for using the Wikimedia trademarks and to get certain grants.	Annual report
Mozilla Community Groups	There must always be two contacts who rotate annually. Contacts should feel comfortable communicating in English and understanding their community’s needs. All groups must adhere to Mozilla's participation and naming guidelines. Group names must be descriptive to avoid implying exclusivity over a broader topic. Creators should verify that no similar groups exist; if they do, merging or revising names/descriptions may be necessary. Mozilla does not acknowledge a hierarchy between groups.	Online registration through Mozilla Community Web Portal	Responsible for maintaining the group’s page and liaising with Mozilla staff. Internal structures and governance are flexible, but leadership roles should align with Mozilla's Volunteer Leadership Principles.	Groups can request budgets or swag for events through local Resource Reps. Campaign-related requests up to $100 are fast-tracked.
Creative Commons Chapters Link	To form a Chapter at least one or more of you must be a member of the Creative Commons Global Network.	Organize the first Chapter Meeting. You must invite and include everyone interested, conduct outreach with sufficient notice to ensure everyone interested is aware of the meeting, and conduct the meeting as openly and visibly as you can. We will help you with that. It is not required that this meeting be in-person. Wwe strongly encourage you to provide ways for those who cannot be present in-person to participate remotely. Notify the Network Manager of your intention to coordinate the organization of the first meeting. Send us an email to network-support@creativecommons.org. At a minimum, two things need to happen during the first meeting : (1) Chapter will elect a member as a Representative at the Global Network Council. (2) Chapter will select a Chapter Lead to be the main point of contact of the Chapter. Send the minutes of the meeting to the Network Manager using the template. CC HQ will finalize chapter formation with the Chapter Lead via a signed agreement.	Run activities and provide support to local projects. Serve as a contact and information point for questions about CC. Represent the Creative Commons Global Network (CCGN) in interactions with governments and organisations. Maintain and update a country-specific website. Establish country consensus on positions related to the CCGN. Elect a representative for the Global Network Council and ensure that person actively fulfills those responsibilities. Chapters must comply with the Charter and the CC policies. Chapters may establish additional rules, guidelines and principles beyond those required here provided they do not conflict with the spirit of the Chapter or conflict with the CC policies.	We will include your new chapter in the list of Creative Commons chapters part of the Global Network.	Report on accomplishments and otherwise keep informed the Global Network Council (GNC) about the Chapter’s activities.
Library Publishing Coalition's Strategic Affiliates Program	To be eligible for affiliate status, an organization must be membership-based, must have a focal area in scholarly communications, and must have substantial engagement with libraries, publishers, or both. It must also provide an equivalent affiliate opportunity (formal or informal) within its organization for the Library Publishing Coalition (LPC). On a case-by-case basis, the Library Publishing Coalition (LPC) Board may admit to the program other mission-aligned non-profit organizations that do not currently have a membership structure in place.	Organizations interested in becoming strategic affiliates of the LPC should contact us (contact@librarypublishing.org). The LPC Board is responsible for determining eligibility for the program and approving new strategic affiliate relationships.	We work with our strategic affiliates to identify other benefits and engagement opportunities on a case-by-case basis. These may take the form of collaborative projects (e.g. joint task forces or collaboratively developed professional development opportunities), negotiated one-off benefits for members (e.g. scholarship opportunities or discounted event registrations), negotiated ongoing benefits for members (e.g. membership fee waivers or discounts). Negotiated benefits and planned collaborations will be included in the strategic affiliate memorandum of understanding (MOU).	One or more staff members (or elected leadership, in the case of organizations that do not have paid staff) of the affiliate organization may enroll in the LPC’s member email list and may attend webinars, roundtables, and other non-fee-based, member-only events.
Python User Groups	Find one or more people to become part of the organizers team. Define the group name - usually Python <city name> Have a website (preferably with your own domain name)	Self-add your group in the wiki.python.org	Define a meeting location. It's good to have a location you can rely upon, monthly, without fail. Define the style of meetings for the group. There are lots of different things to do at meetings : conferences, unconferences , lightning talks, code reviews, hack sessions, video screening, startup weekinds project walkthroughs, module of the months, social meetings, or just have people talk about what they've found interesting and what they're working on.	Contact the fiscal sponsorship team to become a fiscal sponsoree of the PSF to receive donations from sponsors in the U.S.
Python Software Foundation Working Group	One or more people would identify a need and propose a working group charter. The scope of each working group would be defined by a charter, which would include 1) the purpose of the group; 2) the length of time the group would be active; 3) the end goal or product of the group; 4) the methods of communication that the group would use; and 5) any sort of internal governance statement.	The working group charter would be proposed to the voting-eligible Members, who would approve the charter (or not) to create an official working group.	In order to be a Managing Member, a person would need to participate in one or more working groups. Initially, the working groups would correspond to existing functions and committees already identified by the PSF - the Board, the Infrastructure Committee, PyCon-Organizers, etc. Additional new working groups could be proposed by any Member.	If needed, a budget allowance would be provided to the new working group by the Board.	Each year, the working groups would be evaluated by the voting-eligible Members (with possible assistance from the Board). The working groups would either be recertified or would be dissolved for lack of interest, Members, etc.
Python Software Foundation	The PSF welcomes anyone who wants to be affiliated with Python. A Supporting Member is an individual who supports the PSF by helping fund its operations. A Managing Member is an individual who supports the PSF by spending time coordinating, teaching, and serving others. This could be time spent helping run conferences, running a user group, managing infrastructure, or performing some other work on behalf of the PSF. Contributing Members are those who support the Python community with contributions of code, tests, documentation, design, or other results of creative effort. A Fellow is the highest level of PSF membership and confers privileges for life. It should be granted on those who have consistently served the PSF and Python Community over a substantial period of time and have made notable contributions. For Fellows, the criteria would be as follows : For those who have served the Python community by creating and/or maintaining various creative contributions, the following statement should be true : "[Nominated Person] has served the Python community by making available code, tests, documentation, or design, either in a Python implementation or in a Python ecosystem project, that 1) shows technical excellence, 2) is an example of software engineering principles and best practices, and 3) has achieved widespread usage or acclaim." For those who have served the Python community by coordinating, organizing, teaching, writing, and evangelizing, the following statement should be true : "[Nominated Person] has served the Python community through extraordinary efforts in organizing Python events, publicly promoting Python, and teaching and coordinating others. [Nominated Person]'s efforts have shown leadership and resulted in long-lasting and substantial gains in the number and quality of Python users, and have been widely recognized as being above and beyond normal volunteering."	Anyone who wants to become a Member of the Python Software Foundation will have the opportunity to join, simply by signing up on the new pydotorg website and agreeing to the CoC. In order to become a Contributing Member, a person would need to announce what open source project(s) they were working on and commit to spend 5-10 hours a month working on them. To preserve the merit-based nature of becoming a Fellow, a person would need to be nominated by an existing Fellow, and then confirmed by a secret supermajority vote.	If someone wants to just be a Member, there are no other requirements and no other duties.	By signing up, anyone will have the opportunity to declare their part in the broader Python community and their support of the PSF. By making the regular membership a declaration of affiliation, we make the PSF the natural home of anyone that wants to declare their support for Python and be associated with the Python community. Those that became Supporting Members would receive an exclusive gift each year while they were supporting members, including at minimum 1) a custom Tee-shirt each year, 2) some other Python-themed toy, gadget, or item, 3) a number of designated Sponsor Delegate members in the PSF, 4) preferential placement of jobs on the Python jobs board, and 5) discounts to PSF-sponsored and PSF-run events. Other benefits could be proposed by special working groups and ratified by vote.