|
| 1 | +# GraphQLConf FAQ |
| 2 | + |
| 3 | +<div className="mt-6 grid grid-cols-2">{toc.map(({value, id}) => <a key={id} href={`#${id}`}>{value}</a>)}</div> |
| 4 | + |
| 5 | +## Contact Us [#contact] |
| 6 | + |
| 7 | +Answers to many common questions are readily available on this event’s |
| 8 | +website. If you cannot find the answer to your question, you are welcome |
| 9 | +to contact us by emailing graphql_events@linuxfoundation.org. |
| 10 | + |
| 11 | +## Confidentiality |
| 12 | + |
| 13 | +We never sell attendee lists or contact information, nor do we authorize |
| 14 | +others to do so. If you receive an email claiming to sell an attendee |
| 15 | +list for a Linux Foundation event, please forward it to events@linuxfoundation.org. |
| 16 | + |
| 17 | +## Code of Conduct [#codeofconduct] |
| 18 | + |
| 19 | +The GraphQL Foundation and the Linux Foundation are dedicated to |
| 20 | +providing a harassment-free experience for participants at all of our |
| 21 | +events, whether they are held in person or virtually. GraphQLConf is a |
| 22 | +working conference intended for professional networking and |
| 23 | +collaboration within the open source community. It exists to encourage |
| 24 | +the open exchange of ideas and expression and requires an environment |
| 25 | +that recognizes the inherent worth of every person and group. While at |
| 26 | +GraphQLConf or related ancillary or social events, any participants, |
| 27 | +including members, speakers, attendees, volunteers, sponsors, |
| 28 | +exhibitors, booth staff and anyone else, should not engage in |
| 29 | +harassment in any form. |
| 30 | + |
| 31 | +This Code of Conduct may be revised at any time by The GraphQL |
| 32 | +Foundation or The Linux Foundation and the terms are non-negotiable. |
| 33 | +Your registration for or attendance at GraphQL, whether in person or |
| 34 | +virtually, indicates your agreement to abide by this policy and its |
| 35 | +terms. |
| 36 | + |
| 37 | +Please read the full [Code of Conduct](https://events.linuxfoundation.org/about/code-of-conduct) for the complete policy and terms. |
| 38 | + |
| 39 | +## Diversity & Inclusion [#dni] |
| 40 | + |
| 41 | +Education and collaboration are vital to the future of the open source |
| 42 | +ecosystem, and it is imperative to us that everyone in the community |
| 43 | +that wants to participate feels welcome to do so regardless of gender, |
| 44 | +gender identity, sexual orientation, disability, race, ethnicity, age, |
| 45 | +religion or economic status. Our [code of conduct](#codeofconduct) outlines our expectations |
| 46 | +for all those who participate in our community, as well as the |
| 47 | +consequences for unacceptable behavior. |
| 48 | + |
| 49 | + |
| 50 | +We offer diversity and need based |
| 51 | +[scholarships](#scholarships) and have considered a broad |
| 52 | +range of both [onsite resources](#onsite-resources) and |
| 53 | +[emergency resources](#emergency-resources) as well as a |
| 54 | +[health & safety](#health-and-safety) policy. |
| 55 | + |
| 56 | +If you have ideas on how we can create a more inclusive event, please |
| 57 | +do not hesitate to let us know. Contact Emily Ruf, Senior Event |
| 58 | +Manager, at eruf@linuxfoundation.org. |
| 59 | + |
| 60 | +## CHAOSS D&I Event Badge [#chaoss-event-badge] |
| 61 | + |
| 62 | + |
| 63 | + |
| 64 | +Awarded to events in the open source community that fosters healthy |
| 65 | +D&I practices. [Learn More](https://chaoss.community/diversity-and-inclusion-badging). |
| 66 | + |
| 67 | +## Invoices & Certificates of Attendance [#invoices] |
| 68 | + |
| 69 | +### Registration Invoices |
| 70 | + |
| 71 | +Invoice receipts are downloadable from the confirmation email you |
| 72 | +received after registering under the Payment Receipt Information |
| 73 | +section. If the downloadable invoice receipt does not meet your needs |
| 74 | +or you need to have your confirmation email resent, please submit your |
| 75 | +request [here](https://docs.google.com/forms/d/1uxCqF-ieG9QmpU8tl3HqgatHLY9FWhRs7KLpyhZA5KI/edit). |
| 76 | +Please include any additional customization you need for your |
| 77 | +invoice receipt in the request. |
| 78 | + |
| 79 | +### Certificates of Attendance |
| 80 | + |
| 81 | +To request a Certificate of Attendance, please submit a request [here](https://docs.google.com/forms/d/1RpI8h6AGK2rCl3aIlyEY0D6fU3tsZ5yr1Ba6c3h6p9Y/edit). |
| 82 | + |
| 83 | +> Please Note: We verify attendance through the registration system, and |
| 84 | +> Certificate of Attendance letters are sent out after the event is |
| 85 | +> completed. |
| 86 | +
|
| 87 | +## Refund Policy |
| 88 | + |
| 89 | +### Cancellations |
| 90 | + |
| 91 | +If you must cancel for any reason, please [sign back into your registration](https://cvent.me/4zbxz9), click the “Register/Modify” button and select “Unregister.” If you |
| 92 | +need further assistance, email registration@linuxfoundation.org. |
| 93 | + |
| 94 | +Refunds will only be issued for cancellations received two weeks prior |
| 95 | +to the event start date, including bulk ticket request refunds, and |
| 96 | +will appear as a credit on the card’s statement 7 – 10 business days |
| 97 | +after cancellation. Due to the ongoing pandemic, individual refund |
| 98 | +requests due to COVID-19 positive tests will be honored up until the |
| 99 | +start date of the event, and must be accompanied by a photo of a |
| 100 | +positive COVID-19 test. |
| 101 | + |
| 102 | +> Please note: Refunds can only be issued on the card the original |
| 103 | +> payment was made. |
| 104 | +
|
| 105 | +### Substitutions |
| 106 | + |
| 107 | +If you are unable to attend, you may substitute another attendee in |
| 108 | +lieu of cancellation. To substitute an attendee, [sign back into your registration](https://cvent.me/4zbxz9) |
| 109 | +, click the “Register/Modify”, and select “Transfer Registration” on |
| 110 | +your confirmation page. |
0 commit comments