Skip to content

Commit 3a6a4fc

Browse files
beerosebeerose
committed
Update program note and bring back speak
1 parent 5738d36 commit 3a6a4fc

File tree

2 files changed

+352
-0
lines changed

2 files changed

+352
-0
lines changed

‎src/pages/conf/program.tsx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,10 @@ export default () => {
1515
<h1>GraphQLConf 2023 Program</h1>
1616
<section className="px-0 my-8">
1717
<h4>September 19-21, 2023 I San Francisco Bay Area, CA</h4>
18+
<p>
19+
We are excited to announce our speakers for GraphQLConf 2023.
20+
Please check back for more details about the program.
21+
</p>
1822
<div className="[&>div]:-ml-[15px]">
1923
<a
2024
id="sched-embed"

‎src/pages/conf/speak.tsx

Lines changed: 348 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,348 @@
1+
import React, { ReactNode, Fragment } from "react"
2+
import FooterConf from "../../components/Conf/Footer"
3+
import HeaderConf from "../../components/Conf/Header"
4+
import LayoutConf from "../../components/Conf/Layout"
5+
import ButtonConf from "../../components/Conf/Button"
6+
import SectionConf from "../../components/Conf/Section"
7+
import SeoConf from "../../components/Conf/Seo"
8+
9+
const cfp: Array<{ id: string; title: string; contents: ReactNode }> = [
10+
{
11+
id: "dates",
12+
title: "Dates to Remember",
13+
contents: (
14+
<DL
15+
items={[
16+
["CFP Closes", "Friday, June 9 at 11:59 PM PDT (UTC-7)"],
17+
["CFP Notifications", "Wednesday, June 21"],
18+
["Schedule Announcement", "Week of June 26"],
19+
["Slide upload deadline to Sched.com", "Friday, September 15"],
20+
["Event Date", "Tuesday, September 19 – Thursday, September 21"],
21+
]}
22+
/>
23+
),
24+
},
25+
{
26+
id: "topics",
27+
title: "Suggested Topics",
28+
contents: (
29+
<DL
30+
items={[
31+
[
32+
"GraphQL Core",
33+
"Latest and greatest developments in the GraphQL specification, graphql.js, GraphQL over HTTP, GraphiQL, and Composite Schemas.",
34+
],
35+
[
36+
"GraphQL in Production",
37+
"Best practices, real world use cases, spectacular success, spectacular failures, and lessons learned from production deployments of GraphQL.",
38+
],
39+
[
40+
"GraphQL Security",
41+
"Authentication/authorization, security testing, threat models, GraphQL and OWASP Top 10, exploit analysis and retrospective, full-lifecycle security considerations.",
42+
],
43+
[
44+
"GraphQL Clients",
45+
"Client development (web, mobile, and beyond) with GraphQL, frontend frameworks, GraphQL IDEs.",
46+
],
47+
[
48+
"Platform and Backend",
49+
"GraphQL server implementations, data sources for GraphQL resolvers, integration with platform providers/frameworks, serverless, mesh architectures, AI/ML.",
50+
],
51+
[
52+
"Spec Fusion",
53+
"Orchestrating a Symphony of API Standards. In today’s connected world, GraphQL coexists with various other specifications to enable seamless integrations and interoperability. Share your experiences and insights on integrating GraphQL with REST, gRPC, Websockets, RSocket, or other related technologies. Explore the harmonization of FAIR, FHIR, RDF/SPARQL, BIAN, or similar standards to create a beautiful symphony of API specifications.",
54+
],
55+
[
56+
"GraphQL and Data",
57+
"Discuss using GraphQL to interact with existing internal or external data sources, conventions and best practices for API design in different types of query and data workloads, federation across data sources, and authorization ownership and implementation best practices.",
58+
],
59+
[
60+
"Scaling",
61+
"Everything related to scaling GraphQL: testing, automation, performance, social/organizational considerations.",
62+
],
63+
[
64+
"Beyond Javascript",
65+
"Implementing and interacting with GraphQL APIs using languages and frameworks beyond JavaScript: Go, Ruby, Python, Rust, .NET, WebAssembly, et al.",
66+
],
67+
[
68+
"GraphQL Academia",
69+
"Research papers or studies in academia that involve GraphQL.",
70+
],
71+
[
72+
"Emerging Community Trends",
73+
"What’s happening at the vanguard of GraphQL adoption that will help define the future of GraphQL usage in the community.",
74+
],
75+
[
76+
"Defies Categorization",
77+
"Have a talk idea that doesn’t fit inside the topics above? Challenge accepted! Wow us with your awesome talk submission and we’ll work with you to fit it into our track structure. ",
78+
],
79+
]}
80+
/>
81+
),
82+
},
83+
{
84+
id: "types",
85+
title: "Submission Types",
86+
contents: (
87+
<DL
88+
items={[
89+
[
90+
"Session Presentation",
91+
"Typically 30-40 minutes in length, 1-2 speakers presenting on a topic",
92+
],
93+
[
94+
"Panel Discussion",
95+
"Typically 30-40 minutes in length, 3-5 speakers presenting on a topic",
96+
],
97+
["Birds of a Feather", "Typically 45 minutes to 1 hour in length"],
98+
["Lightning Talk", "Typically 5-10 minutes in length"],
99+
["Workshop", "Typically 1-2 hours in length"],
100+
]}
101+
/>
102+
),
103+
},
104+
{
105+
id: "important",
106+
title: "Important Notes",
107+
contents: (
108+
<>
109+
<p>
110+
All speakers are required to adhere to our{" "}
111+
<a href="/conf/faq/#codeofconduct">Code of Conduct</a>. We also highly
112+
recommend that speakers take our online{" "}
113+
<a
114+
href="https://training.linuxfoundation.org/linux-courses/open-source-compliance-courses/inclusive-speaker-orientation"
115+
target="_blank"
116+
>
117+
Inclusive Speaker Orientation Course
118+
</a>
119+
.
120+
</p>
121+
<p>
122+
Panel submissions must include the names of all participants in the
123+
initial submission to be considered. In an effort to promote speaker
124+
diversity, The Linux Foundation does not accept submissions with
125+
all-male panels, and speakers must not all be from the same company.
126+
</p>
127+
<p>
128+
Complimentary Passes For Speakers – One complimentary pass for the
129+
event will be provided for the accepted speaker(s) per submission.
130+
</p>
131+
<p>
132+
Avoid sales or marketing pitches and discussing unlicensed or
133+
potentially closed-source technologies when preparing your proposal;
134+
these talks are almost always rejected due to the fact that they take
135+
away from the integrity of our events, and are rarely well-received by
136+
conference attendees.
137+
</p>
138+
<p>
139+
The Linux Foundation will not select submissions that have already
140+
been presented at a previous Linux Foundation event within the past
141+
year. If your submission is similar to a previous talk, please explain
142+
how this version differs.
143+
</p>
144+
<p>
145+
You are allowed to be listed as a speaker on a maximum of two
146+
proposals submitted to the CFP, regardless of the format. If you are
147+
listed on more than two, we will contact you to remove yourself from
148+
any additional proposals.
149+
</p>
150+
<p>
151+
You may only be selected to speak on one panel and one non-panel
152+
session per event.
153+
</p>
154+
<p>
155+
All accepted speakers are required to submit their slides prior to the
156+
event.
157+
</p>
158+
</>
159+
),
160+
},
161+
{
162+
id: "prepare",
163+
title: "Prepare to Submit",
164+
contents: (
165+
<>
166+
<p>
167+
While it is not our intention to provide you with strict instructions
168+
on how to prepare your proposal, we hope you will take a moment to
169+
review the following guidelines that we have put together to help you
170+
prepare the best submission possible. To get started, here are three
171+
things that you should consider before submitting your proposal:
172+
</p>
173+
<ul className="list-disc">
174+
<li>What are you hoping to get from your presentation?</li>
175+
<li>
176+
What do you expect the audience to gain from your presentation?
177+
</li>
178+
<li>How will your presentation help better the ecosystem?</li>
179+
<li>
180+
There are plenty of ways to give a presentation about projects and
181+
technologies without focusing on company-specific efforts. Remember
182+
the things to consider that we mentioned above when writing your
183+
proposal and think of ways to make it interesting for attendees
184+
while still letting you share your experiences, educate the
185+
community about an issue, or generate interest in a project.
186+
</li>
187+
</ul>
188+
<h3>Writing Your Proposal</h3>
189+
<p>
190+
Your abstract title will be the main point of reference for attendees
191+
to decide if they want to attend your talk, so choose it carefully.
192+
The title should accurately reflect the content of your talk and
193+
comply with The Linux Foundation’s{" "}
194+
<a
195+
href="https://events.linuxfoundation.org/graphqlconf/program/cfp/#preparing-to-submit:~:text=The%20Linux%20Foundation%E2%80%99s-,Inclusive%20Language%20Initiative.,-It%20will%20appear"
196+
target="_blank"
197+
>
198+
Inclusive Language Initiative
199+
</a>
200+
. Please use title case when inputting your title.
201+
</p>
202+
<p>
203+
In the abstract, make the most of your opportunity to pitch your talk
204+
to the program committee by emphasizing its problem, contribution, and
205+
relevance. Don’t forget technical details, but keep the big picture in
206+
mind. Your proposal’s description should be focused, detailed, and
207+
comply with The Linux Foundation’s Inclusive Language Initiative. It
208+
will appear on the website schedule if accepted, so ensure it’s
209+
error-free, uses full sentences, and written in the third person. This
210+
description can make or break an attendee’s decision to attend your
211+
talk, so provide enough information to aid their choice, and be
212+
concise. The competition for presentation slots is high, so a
213+
well-crafted, engaging abstract will improve your chances of
214+
acceptance.
215+
</p>
216+
<h3>How to Give a Great Talk</h3>
217+
<p>
218+
We want to make sure submitters receive resources to help put together
219+
a great submission and if accepted, give the best presentation
220+
possible. To help with this, we recommend viewing seasoned speaker
221+
Dawn Foster’s in-depth talk:{" "}
222+
<a href="https://youtu.be/2I5fYBLCfUA" target="_blank">
223+
Getting Over Your Imposter Syndrome to Become a Conference Speaker –
224+
Dawn Foster, VMware
225+
</a>
226+
</p>
227+
<h3>
228+
Have More Questions? First Time Submitting? Don’t Feel Intimidated
229+
</h3>
230+
Linux Foundation events are an excellent way to get to know the
231+
community and share your ideas and the work that you are doing and we
232+
strongly encourage first-time speakers to submit talks for our events.
233+
In the instance that you aren’t sure about your abstract,{" "}
234+
<a href="mailto:cfp@linuxfoundation.org">reach out to us</a> and we will
235+
be more than happy to work with you on your proposal.
236+
</>
237+
),
238+
},
239+
{
240+
id: "sessionize",
241+
title: "Using Sessionize",
242+
contents: (
243+
<>
244+
<h3>First time using Sessionize?</h3>
245+
<p>
246+
Sessionize is a cloud-based event content management software designed
247+
to be intuitive and user-friendly. If you need guidance, please review
248+
how to submit your session for an event for step-by-step instructions
249+
and helpful screenshots.
250+
</p>
251+
252+
<h3>Submitting on behalf of somebody else?</h3>
253+
<p>
254+
While speakers ordinarily submit their sessions themselves, it’s also
255+
common for them to have someone else do it in their name. Submitters
256+
can choose to submit as someone else and must fill out the necessary
257+
speaker fields, but the session submission process is otherwise
258+
identical to when the session is submitted by the speaker themselves.
259+
</p>
260+
</>
261+
),
262+
},
263+
]
264+
265+
function DL({ items }: { items: [header: string, contents: ReactNode][] }) {
266+
return (
267+
<dl className="my-4">
268+
{items.map(([header, contents]) => (
269+
<Fragment key={header}>
270+
<dt className="mt-6 mb-2 text-xl">{header}</dt>
271+
<dd>{contents}</dd>
272+
</Fragment>
273+
))}
274+
</dl>
275+
)
276+
}
277+
278+
export default () => {
279+
const today = new Date()
280+
const expiredDate = new Date("2023-06-10")
281+
const isExpired = expiredDate > today
282+
283+
return (
284+
<LayoutConf>
285+
<HeaderConf />
286+
<div className="bg-white">
287+
<div className="prose lg:prose-lg mx-auto py-10 max-sm:px-4">
288+
<h1>Speak at GraphQLConf</h1>
289+
<section className="px-0 my-8">
290+
<p>
291+
Putting on an amazing conference depends on great content, which
292+
is where you come in! Join other GraphQL leaders and community
293+
members as a presenter by submitting to our Call for Proposals
294+
(CFP) and sharing your experience across a wide range of topics.
295+
</p>
296+
<p>
297+
The CFP is open through Friday, June 9. For any questions
298+
regarding the CFP process, please email{" "}
299+
<a href="mailto:cfp@linuxfoundation.org">
300+
cfp@linuxfoundation.org
301+
</a>
302+
.
303+
</p>
304+
{isExpired ? (
305+
<ButtonConf href="https://sessionize.com/graphqlconf2023/">
306+
Submit a Proposal
307+
</ButtonConf>
308+
) : (
309+
<div className="font-bold"> The CFP has closed.</div>
310+
)}
311+
<p className="italic">
312+
Please be aware that the Linux Foundation will now be utilizing
313+
Sessionize for CFP submissions. Sessionize is a cloud-based event
314+
content management software designed to be intuitive and
315+
user-friendly. If you need guidance, please review{" "}
316+
<a
317+
target="_blank"
318+
href="https://sessionize.com/playbook/submit-your-session-for-an-event"
319+
>
320+
how to submit your session for an event
321+
</a>{" "}
322+
to see step-by-step instructions and helpful screenshots.
323+
</p>
324+
</section>
325+
<ul className="md:columns-2 max-lg:p-0 max-lg:m-0 list-none">
326+
{cfp.map(q => (
327+
<li key={q.id} className="md:mt-0 md:mb-2">
328+
<a href={`#${q.id}`}>{q.title}</a>
329+
</li>
330+
))}
331+
</ul>
332+
{cfp.map(q => (
333+
<SectionConf key={q.id} id={q.id} title={q.title}>
334+
{q.contents}
335+
</SectionConf>
336+
))}
337+
</div>
338+
</div>
339+
<FooterConf />
340+
</LayoutConf>
341+
)
342+
}
343+
344+
export function Head() {
345+
return (
346+
<SeoConf title="Speak at GraphQLConf 2023 - (CFP) Call for proposals" />
347+
)
348+
}

0 commit comments

Comments
 (0)