|
| 1 | +--- |
| 2 | +sidebarTitle: GraphQL Local |
| 3 | +description: |
| 4 | + The GraphQL Local initiative helps the GraphQL Foundation foster a culture of |
| 5 | + community and innovation, contributing to the success, health, and |
| 6 | + sustainability of our ecosystem. |
| 7 | +--- |
| 8 | + |
| 9 | +import { Button } from "../../../app/conf/_components/button" |
| 10 | + |
| 11 | +# GraphQL Local Initiative |
| 12 | + |
| 13 | +The GraphQL Foundation's primary mission is to ensure the continued evolution of |
| 14 | +the GraphQL specification and reference implementations. As part of this |
| 15 | +mission, we strive to provide collaboration infrastructure that fosters a |
| 16 | +culture of community and innovation. Local get-togethers play a crucial role in |
| 17 | +this, bringing together developers, library maintainers, vendors, and |
| 18 | +enthusiasts to share knowledge and collaborate. |
| 19 | + |
| 20 | +To better support these meets and clarify the process, we are excited to |
| 21 | +announce the official **GraphQL Local** initiative. This initiative provides a |
| 22 | +framework for organizing local GraphQL user groups and offers support to each |
| 23 | +approved group (hereafter, a "Local"). |
| 24 | + |
| 25 | +We're happy to support both new and existing GraphQL meets; here’s what you |
| 26 | +need to know to get involved: |
| 27 | + |
| 28 | +## Requirements |
| 29 | + |
| 30 | +Organizers of a Local must agree: |
| 31 | + |
| 32 | +- All official events and related channels will be governed by the |
| 33 | + **[GraphQL Code of Conduct](https://graphql.org/codeofconduct/)**. |
| 34 | +- Official communications will comply with the |
| 35 | + **[GraphQL Brand Guidelines](https://graphql.org/brand/)**. |
| 36 | +- The Local accepts **GraphQL TSC oversight**: |
| 37 | + - At least one |
| 38 | + [GraphQL Technical Steering Committee (TSC) member](https://github.com/graphql/graphql-wg/blob/main/GraphQL-TSC.md#tsc-members) |
| 39 | + must be granted administrator access to the Local’s online platforms (we |
| 40 | + will assign a TSC member and supply the relevant details on approval of |
| 41 | + your Local). |
| 42 | + - In case of a serious Code of Conduct breach, an organizer may be replaced. |
| 43 | +- The Local has 1 or more organizer from the area. (We're pretty flexible on the |
| 44 | + definition of "from the area", just be reasonable.) |
| 45 | +- Each official event will have at least least one **organizer present**. |
| 46 | +- Official events will be held in an appropriate **professional setting**. |
| 47 | +- Official events will feature at least one GraphQL-related talk (the format can |
| 48 | + vary: lecture, lightning talk, panel, AMA, etc). |
| 49 | +- These **talks will be recorded** and made freely available online. |
| 50 | +- Official events will be be **announced at least two weeks in advance**. |
| 51 | + Popular ticketing platforms include Eventbrite, Guild.host, and Meetup.com. |
| 52 | +- Attending official events will be **affordable**. |
| 53 | + - If not free, attendance fees must not exceed USD $10 or local equivalent |
| 54 | + without explicit approval from the GraphQL Marketing and Content committee. |
| 55 | + Events charging fees waive their entitlement to GraphQL Foundation |
| 56 | + sponsorship. |
| 57 | +- Organizers will **report back on attendance**, general feedback, and any |
| 58 | + suggestions for future events in a timely manner. |
| 59 | + |
| 60 | +Groups may of course organize other events, e.g. a summer barbeque, but these |
| 61 | +are currently out-of-scope of GraphQL Foundation support. These other events |
| 62 | +shall not be referred to as "official", but are still encouraged to follow the |
| 63 | +guidelines that are applicable (in particular, the Code of Conduct and Brand |
| 64 | +Guidelines must still be honoured). |
| 65 | + |
| 66 | +## Support |
| 67 | + |
| 68 | +Each approved Local is entitled to request the following support for each |
| 69 | +event: |
| 70 | + |
| 71 | +- **Sponsorship** up to USD $200 per event (max 1 per quarter) for approved |
| 72 | + costs (see below). More sponsorship might be available directly from |
| 73 | + individual foundation members, see details below. |
| 74 | +- **Swag bundle**\* to distribute to speakers, attendees, or organizers (max 1 |
| 75 | + per quarter). |
| 76 | +- **Google Slides templates** for: |
| 77 | + - Code of Conduct |
| 78 | + - Call for Papers (CFP) |
| 79 | + - Sponsors |
| 80 | + - Schedule |
| 81 | + - Speaker/talk introduction |
| 82 | +- **Promotion** through GraphQL’s Twitter and LinkedIn channels. |
| 83 | +- **Local artwork** adhering to the GraphQL Brand Guidelines; including |
| 84 | + avatars, event banners, and slide templates. \*\* |
| 85 | + |
| 86 | +\* The content of swag bundles may change from time to time depending on |
| 87 | +available inventory. |
| 88 | + |
| 89 | +\*\* There may be a significant delay on the delivery of local artwork |
| 90 | +currently, we're still figuring out designs. |
| 91 | + |
| 92 | +## Approved Costs |
| 93 | + |
| 94 | +Sponsorship funds may be used towards: |
| 95 | + |
| 96 | +- Food (be sure to consider dietary restrictions and allergies) |
| 97 | +- Non-alcoholic drinks (alcoholic beverages, if provided, require sponsor |
| 98 | + approval or should be paid out of alternative funds) |
| 99 | +- Venue hire |
| 100 | +- Swag for speakers or attendees |
| 101 | +- Promotional materials |
| 102 | +- AV resources (e.g., camera stand, microphone) |
| 103 | + |
| 104 | +On approval of your GraphQL Local you will be provided with invoicing |
| 105 | +instructions. |
| 106 | + |
| 107 | +## Caveats |
| 108 | + |
| 109 | +All support is subject to the finite resources (both financial and temporal) of |
| 110 | +the GraphQL Local initiative. Sponsorship may be adjusted both up and down based |
| 111 | +on expected attendance and is discretionary. Bespoke work, e.g. local artwork, |
| 112 | +may have long and unpredictable lead times. Your application may be declined for |
| 113 | +any reason, but in particular if we think it is likely that the initiative will |
| 114 | +exhaust its budget we will decline all further applications until more budget |
| 115 | +becomes available. |
| 116 | + |
| 117 | +If you'd like to help support the GraphQL Foundation's various programs and |
| 118 | +initiatives, consider becoming a GraphQL Foundation member. |
| 119 | + |
| 120 | +## Additional Support |
| 121 | + |
| 122 | +If you need extra support for your event (e.g., transportation costs or higher |
| 123 | +venue fees/larger food and drinks budget for larger get-togethers), individual |
| 124 | +GraphQL Foundation member organizations may be able to offer additional support, |
| 125 | +often with a small ask such as saying a few words about them during the event. |
| 126 | +If your gathering is approved, you will be provided with contact information for |
| 127 | +member organizations who have expressed interest in supporting gatherings. |
| 128 | + |
| 129 | +## Get in Touch Now! |
| 130 | + |
| 131 | +We’re excited to see the GraphQL community grow and thrive through these |
| 132 | +gatherings. For more information or to get started, please contact us on |
| 133 | + |
| 134 | + |
| 135 | +<Button |
| 136 | + href="mailto:[email protected]?subject=I+want+to+start+a+GraphQL+Local+in+CITY_NAME_HERE" |
| 137 | + className="mx-auto my-6 !block" |
| 138 | +> |
| 139 | + Start a GraphQL Local! |
| 140 | +</Button> |
0 commit comments