Table of summary of pre-existent foundation schemes for affiliation

From OpenStreetMap Wiki
Jump to navigation Jump to search

Part of results of the Research Sub-committee on improvement of the affiliation scheme.

Link to the process: Improving the affiliation scheme of the OSMF

Link to the OSM Community message: OSM Community message

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)
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
  • 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.
  • 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)
  • 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.
QGIS Link Understanding Open Source Principles: * QGIS is licensed under the GNU General Public License (GPL) version 2 or greater. This means that any contributions made to the project must adhere to the principles of open source, including making source code available and allowing others to use, modify, and distribute the software freely.
  • Community Engagement: Active participation in community events such as conferences, workshops, and online discussions can help establish a stronger affiliation with QGIS. Engaging with other users and developers allows for knowledge sharing and networking opportunities that can benefit both individual contributors and organizations.
  • Adhering to Code of Conduct: Affiliates must adhere to a code of conduct that promotes respectful communication and collaboration within the community. This ensures a welcoming environment for all contributors regardless of their background or experience level.
1. Community Contributions

QGIS encourages contributions from anyone interested in enhancing its capabilities. This includes developers who can contribute code, documentation writers who can help improve user manuals, and users who provide feedback or report bugs. The community is organized around several key areas:

Code Contributions: Developers can contribute by writing plugins or improving the core software. This typically requires familiarity with programming languages such as Python or C++.

Documentation: Contributors can help by writing tutorials, guides, or translating existing documentation into different languages.

User Support: Experienced users often assist newcomers through forums or mailing lists. 2. Joining the QGIS Community To formally affiliate with QGIS, individuals can join various community platforms:

Mailing Lists: Users can subscribe to mailing lists where they can ask questions, share knowledge, and discuss features.

Forums: The QGIS community forum is a place for discussions about usage, troubleshooting, and sharing projects.

Events and Conferences: Participating in events like FOSS4G (Free and Open Source Software for Geospatial) conferences provides opportunities to network with other users and developers. 3. Institutional Affiliations Organizations using QGIS may also establish formal affiliations:

Educational Institutions: Universities often incorporate QGIS into their curricula and may collaborate on research projects using the software.

Government Agencies: Many governmental bodies utilize QGIS for spatial analysis and may contribute back to the project by developing plugins tailored to their needs.

1. Compliance with Licensing Terms

QGIS is released under the GNU General Public License (GPL), which imposes certain obligations on users and contributors:

Freedom to Use: Users can use QGIS for any purpose without restrictions. Source Code Availability: If modifications are made to the QGIS software, those changes must be documented and made available under the same GPL license. Attribution: When distributing modified versions or derivatives of QGIS, proper attribution must be given to the original authors. 2. Financial Contributions One of the primary obligations for affiliated organizations is to provide financial support. This can take various forms, including:

Annual Membership Fees: Organizations are often required to pay an annual fee that contributes directly to the maintenance and development of QGIS. Sponsorships: Companies may choose to sponsor specific features, events, or initiatives within the QGIS ecosystem, which helps fund targeted development efforts. 3. Community Engagement

Affiliates are expected to engage actively with the QGIS community:

Participation in Events: Affiliates should participate in conferences, workshops, and other events organized by or associated with QGIS. This helps foster collaboration and knowledge sharing. Feedback Mechanisms: Providing feedback on software usability, features, and bugs is essential for continuous improvement of QGIS. 4. Ethical Considerations Affiliates must adhere to ethical standards when using or contributing to QGIS:

Respectful Communication: All interactions within forums, mailing lists, or events should be conducted respectfully and professionally. Inclusivity Practices: Affiliates should promote inclusivity within the community by encouraging diverse participation from various backgrounds.

* Open Source and Free to Use

QGIS is an open-source software, meaning it is free to download, use, and modify. This accessibility allows users from various backgrounds, including students, researchers, and small businesses, to utilize advanced GIS capabilities without the financial burden associated with proprietary software.

  • Extensive Functionality QGIS provides a wide range of tools for spatial analysis, data visualization, and cartography. Users can perform complex geospatial analyses, create detailed maps, and manipulate spatial data in various formats (e.g., vector and raster). The functionality includes support for plugins that extend its capabilities even further.
* Defining Evaluation Criteria
  • Data collection
  • Analysis of findings
  • Reporting results
  • Continous improvement cycle
Apache FoundationApache Local Chapter (ALC) Only one ALC chapter per town/city; It is mandatory to have at least 1 ASF member plus 2 PMC members in the ALC Chapter team;  If a proposed ALC Chapter is not having any ASF member on a case-by-case basis ComDev PMC may assign a mentor (who will be an ASF member) to the proposed ALC Chapter and establish it. To follow the steps mentioned in Process to establish an ALC Chapter document (copied below). 

There will be a single ALC chapter per town/city, so please check the ALC Chapters to see if there’s an existing chapter in your location. The following process will be followed to establish an ALC Chapter:


1. A volunteer will request to establish an ALC Chapter by sending a message to dev@community.apache.org with "[ALC] Request to establish ALC in <name-of-your-town-or-city>" in the subject line.

Before sending the request, the volunteer needs to make sure the following points are addressed

  • There will be a single ALC chapter per town/city, so before sending the request please check the ALC Chapters to see if there’s an existing chapter in your location;
  • It is mandatory to have at least 1 ASF member plus 2 PMC members in the ALC Chapter team. The volunteer needs to make sure the proposed ALC chapter team meets this criterion. If a proposed ALC Chapter is not having any ASF member on a case-by-case basis ComDev PMC may assign a mentor (who will be an ASF member) to the proposed ALC Chapter and establish it.
  • Spread awareness on Apache in local communities;
  • Host various events for local open source enthusiasts that include students, developers, and the business community;
  • Share information about ASF, The Apache Way, and various Apache  projects. Bring together project users and developers.
  • To open the doors for having frequent and small events for the local Open Source community;
  • To provide a platform for different project committers from the same town/city to meet and exchange knowledge, thoughts, and ideas. will help build and expand communities, as the Apache maxim "Community Over Code".
  • f any ALC Chapter is inactive for three months, it will be dissolved after communication with members of that ALC chapter and PMC votes because we are having strictly one ALC chapter in a town/city. Here more details on Process to dissolve an ALC Chapter;
  • The ALC members should follow the Apache code of conduct, for details please refer https://www.apache.org/foundation/policies/conduct.html 
  • The ALC Chapter shares the status report to ComDev in every three months. The report includes details on the activities performed by ALC Chapter and it's impact.  The ALC Chapter is not allowed to execute any press releases.  
Open Source Initiatives
Encode JusticeLink Drive
Gnome FoundationGnome User Groups
KDE e.V.KDE Network
Free Software FoundationLibrePlanet("Start a Team")
DebianDebian Local Groups
Django
[example]
[example]
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)