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