{"id":47310615,"url":"https://github.com/chicagopython/bylaws","last_synced_at":"2026-03-17T11:04:15.533Z","repository":{"id":45118109,"uuid":"232221292","full_name":"chicagopython/bylaws","owner":"chicagopython","description":"The bylaws that govern our organization and decision-making.","archived":false,"fork":false,"pushed_at":"2024-03-05T00:30:56.000Z","size":16,"stargazers_count":0,"open_issues_count":0,"forks_count":1,"subscribers_count":13,"default_branch":"master","last_synced_at":"2025-12-28T17:19:43.803Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/chicagopython.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null}},"created_at":"2020-01-07T01:56:51.000Z","updated_at":"2022-01-07T03:25:23.000Z","dependencies_parsed_at":"2024-02-20T05:44:36.132Z","dependency_job_id":null,"html_url":"https://github.com/chicagopython/bylaws","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/chicagopython/bylaws","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/chicagopython%2Fbylaws","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/chicagopython%2Fbylaws/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/chicagopython%2Fbylaws/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/chicagopython%2Fbylaws/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/chicagopython","download_url":"https://codeload.github.com/chicagopython/bylaws/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/chicagopython%2Fbylaws/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":30622427,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-03-17T08:10:05.930Z","status":"ssl_error","status_checked_at":"2026-03-17T08:10:04.972Z","response_time":56,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2026-03-17T11:04:14.869Z","updated_at":"2026-03-17T11:04:15.521Z","avatar_url":"https://github.com/chicagopython.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Name of Organization {#name-of-organization}\n\nThe Chicago Python User Group, AKA “ChiPy”.\n\n\n# Vision {#vision}\n\nChicago Python Users comprise the core of a healthy, world-wide Python\ndeveloper community.\n\n\n# Mission {#mission}\n\nTo promote, grow, and support engaged Python users of all levels through\ninclusive, community-driven events and resources in Chicago.\n\n\n# Values {#values}\n\n*   Openness\n*   Inclusiveness\n*   Shared Learning\n*   Technical Mastery\n*   Volunteerism\n*   Self-Motivation\n*   Open Source Development\n\n\n# Membership {#membership}\n\n## Eligibility to be a Member {#eligibility-to-be-a-member}\n\nA Member is defined as anyone who attends at least one ChiPy meeting a year,\nor who is an Organizer or Board member.\nMembership may be revoked for violations of ChiPy's Code of Conduct.\n\nNote that currently ChiPy membership confers no status or powers.\n\n\n## Eligibility to be an Organizer {#eligibility-to-be-an-organizer}\n\nAn Organizer is defined by the Board in the List of Organizers. Qualifications\nto be considered an Organizer are being a member and\nhaving been a volunteer in hosting/producing a ChiPy event or offering, outside of in a paid capacity, in the prior 12 months.\nAdditionally, “Outstanding/significant contributors” may be awarded Organizer\nstatus. Organizer nominations or removals must be put forward by an existing\nOrganizer or Board member and ratified by Board vote.\n\n\n### List of Organizers {#list-of-organizers}\n\nThe List of Organizers is maintained by the Secretary and available to the\npublic. It must contain at least the name, email (redacted from public view),\noffering, and last activity date for each Organizer. Especially important is\nthe email, which will be used for notifications related to voting.\n\nRatification of the List of Organizers is conducted via Board votes, which\nshall occur at the first regular meeting in March, June, September, and\nDecember. In the event that a ratification vote is missed, the previously\nratified list remains in effect, subject to volunteer date rolloffs, until the\nvote can be made up at the next meeting.\n\n\n# Board {#board}\n\n\n## General Powers  {#general-powers}\n\nThe scope of the Board’s powers are limited to those needed to keep ChiPy\nsolvent, set the vision/mission/values, and steer people/resources to achieve\nboth of those prior objectives.These are the people who will be “kept up at\nnight” about organization-level decisions. Board members have fiduciary\nresponsibility for ChiPy. Full powers are laid out across the by-laws, but two\ncritical powers include the power to update these by-laws as well as host\nelections for Board members.\n\n\n## Composition {#composition}\n\nThe Board is made up of seven people (including the chair).\n\n## Position Terms {#position-terms}\n\nBoard Members are appointed by election to terms of two years, with an effort\ntoward having half the board seats up for election at any point in time. There\nis no lifetime limit for the number of years a Board member may serve.\n\n## Removal {#removal}\n\nA Board member can be removed by a majority vote of the other Board members.\n\nBoard members will automatically be removed if they miss 65% of all regularly\nscheduled board meetings during a term (given an 8 month window),\nunless there is a majority vote to the contrary. Special meetings of the Board\nand scheduled meetings that do not meet Quorum do not count against absences.\nSuch a vote to override automatic explulsion would last for up to one-quarter\nbefore it would need to be renewed; overrides can be undone at any time by a\nsubsequent majority vote.\n\n## Vacancy Filling {#vacancy-filling}\n\nAny vacancy on the  Board shall be filled without undue delay by a majority\nvote of the remaining members of the Board at a regular meeting. The new Board\nmember will serve the remainder of the previous Board member’s term. Vacancies\nmay be filled by Board vote.\n\n## Board Officers {#board-officers}\n\nThere are three officer positions, with the role’s responsibilities as\ndescribed below.\n\n*   **Chair**: The Chair is responsible for presiding over all Board meetings,\nincluding setting the agenda for such meetings in advance and breaking any vote\nties, if necessary. The Chair also acts as ChiPy’s figurehead for the purposes\nof signatures and media/political representation.\n*   **Treasurer**: The treasurer is responsible for financial management and/or\noversight, including such basic tasks as selecting a bank, reconciling bank\nstatements, and managing cash flow. The Treasurer should be knowledgeable about\nwho has access to the organization’s funds and any outstanding bills or debts\nowed. The Treasurer should create and maintain systems for ensuring the\norganization’s ongoing solvency and oversee the development of the\norganization’s financial policies. Helpful policies to consider include check\nsigning authority, expense reimbursement, and credit card usage. The Treasurer\nis also responsible for preparing budgets, financial reports, and any required\ntax/financial forms required to be filed.\n*   **Secretary**: The Secretary shall attend all meetings of the Board and any\ndesignated committees, and act as a clerk thereof. In the event that the\nSecretary can’t attend a meeting, they are solely responsible for finding a\ntemporary replacement from within the Board. The Secretary’s duties shall\nconsist of:\n\t\t*   Recording meeting minutes of all proceedings as well as any votes in a\ndesignated place for such purpose, and which is available to all Board members.\n\t\t*   Making arrangements for all meetings, including advance dissemination\nof associated materials, along with the President.\n\t\t*   External correspondence of information as requested by the Board and/or\nChair within the normal scope of business.\n\nIn the event that the Chair becomes incapacitated, the Treasurer automatically\nassumes the role of interim President. If the Treasurer becomes incapacitated\nthe Secretary automatically assumes the role of interim Secretary or interim\nPresident(in the event of both being unavailable).\n\n## Officer Elections {#officer-elections}\n\nRegular officer elections will occur annually at the first regular meeting\nfollowing the results of elections to the Board. Should a vacancy of an officer\nposition occur outside of this schedule, vacant officer positions will be voted\non at the next regular meeting following the vacancy. In all cases, officers\nmay be nominated (including self-nomination) by any member of the Board.\nOfficers are determined by a majority vote.\n\nIn the event of a Vacancy or other interim position, the Board should re-elect\nany vacancies until the all officer positions are filled . Any board member may\nrun for any vacancy in any Officer Election. If an existing Officer on the\nboard wishes to run for a vacant position and wins, then their position will\nbecome available for a subsequent Officer Election decision.\n\n\n## Committees {#committees}\n\nThe board may create committees as needed, such as sponsorship, code of\nconduct, technology, public relations, data collection, etc. The board appoints\ncommittee chairs annually by majority. Current committees:\n\n*   **Code of Conduct.** This committee is responsible for recommended changes\nto the ChiPy code of conduct, as well as investigating any code of conduct\nviolation complaints from members.\n*   **Sponsorship.** This committee is responsible for fundraising for ChiPy,\nseeking both in-kind sponsorships (space, food, technology) and financial\nsponsorships.\n*   **Technology.** This committee is responsible for recommending,\nmaintaining, and developing technologies used by ChiPy for its operations. Any\nchanges to existing technologies still need to be proposed to the Board for\nmajority approval, and every Board member should have access to every system,\nat all times.\n\n\n## Confidentiality {#confidentiality}\n\nBoard Members shall not discuss or disclose information about the organization\nor its activities to any person or entity unless such information is required\nby law, the information is already a matter of public knowledge, such person or\nentity has a need to know, or the disclosure of such information is in\nfurtherance of the organization’s purposes, or can reasonably be expected to\nbenefit the organization. Board members shall use discretion and good business\njudgment in discussing the affairs of the organization with third parties.\n\nEach Board member shall execute a confidentiality agreement consistent herewith\nupon being voted onto and accepting appointment to the Board. Violation of this\nagreement is grounds for immediate removal from the Board as well as potential\nlegal action, should such be warranted.\n\n\n## Meetings {#meetings}\n\nRegular meetings are held no less than once a month in a manner that supports\nremote participation. Board meetings are called by the Chair or by a majority\nof the Board no less than 36 hours in advance of the meeting time.\n\n\n## Quorum {#quorum}\n\nThe presence of a majority of current members of the Board shall be necessary\nat any meeting to constitute a quorum to transact business, but a lesser number\nshall have power to adjourn to a specified later date without notice. The act\nof a majority of the members of the Board present at a meeting at which a\nquorum is present shall be the act of the Board, unless the act of a greater\nnumber is required by law or by these by-laws. For example, if four of seven\nboard members are present, quorum is met. If three of those four present Board\nmembers agree on a vote, the vote passes.\n\n## Parliamentary Procedure {#parliamentary-procedure}\n\nRobert’s Rules unless specified otherwise in the Bylaws.\n\n# Elections of the ChiPy Board {#elections-of-the-chipy-board}\n\n## Frequency/Scope {#frequency-scope}\n\nElections occur every calendar year, per the Schedule, to fill approximately\nhalf of the Board seats available. This frequency helps support healthy\nturnover, while not diminishing the Board’s knowledge base.\n\nElections are for Board membership, not Officer positions, which are internally\nvoted on by the Board.\n\n## Nomination {#nomination}\n\nAny Organizer or Board member may submit a name for nomination to the Board.\nNominations will be made via the Voting Platform.\n\n#### Requirements {#requirements}\n\nIn order to be on the ballot, a nominee must:\n\n1. live at least part of the year in the greater Chicagoland area,\n2. be able to attend events,\n3. have attended at least two events in the last 12 months, and\n4. be a member.\n\nNote: Board Members do NOT have to be day-to-day organizers. They are, however,\nresponsible for overseeing organizers (making sure they are enabled for success\nnot micromanaging).\n\n\n## Voting  {#voting}\n\nVoting is open to all Organizers and Board members. Aspirationally, we’d like\nto open up voting to all Members.\n\nVoting will occur via a third-party voting platform. The voting system used is\nmulti-winner run-off.\n\n## Schedule {#schedule}\n\nOne month prior to the start of elections, the names of the Board Members not\nsubject to election and the number of positions available on the Board in the\ncoming election will be made publicly available. This communication will also\ninclude the list of voters who can cast ballots or Nominate candidates to the\nBoard.\n\n**First regular Board meeting in January: **Last voter list ratification\nbefore elections.\n\n**January 15th: **Call for Board nominations made via email to Organizers and\nBoard members. The email will include a description of nomination requirements,\na Board member’s role, and instructions on how to cast a nomination.\n\n**February 7th:** Advance notice of the:\n\n1. names of the Board Members not subject to election,\n2. the number of positions available on the Board in the coming election,\n3. the names of the nominees,\n4. the date range to cast ballots, and\n5. how to cast ballots\n\nwill be made available to eligible voters via email.\n\n**February 14th:** Voting opens. Email reminders about voting will be sent to\neligible voters.\n\n**February 28th: **Voting closes.\n\n**March 2nd: **Results announced via email.\n\n**March __main__ meeting**: Election process and results announced.\n\n**First regular board meeting after results announced**: New board terms take\neffect.\n\n\n# Amending the Bylaws {#amending-the-bylaws}\n\nThe Board Members may amend these Bylaws by a majority vote at a meeting of the\nboard. Written notice setting forth the proposed amendment or summary of the\nchanges to be affected thereby shall be given to each Board Member within the\ntime and manner provided for the giving of notice of meetings of the Board.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fchicagopython%2Fbylaws","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fchicagopython%2Fbylaws","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fchicagopython%2Fbylaws/lists"}