Request for Review: Community & Program Responsibilities

Hi TSC team 👋

First, I want to say a genuine thank you for the opportunity to contribute to JSON Schema and for the trust the team has placed in me over this past year. The experience has been incredibly valuable to me, both professionally and personally. I have had the opportunity to work with contributors, maintainers, speakers, sponsors, community members, and partners across different parts of the ecosystem, and I am grateful for the space to learn, take ownership, and contribute to something I genuinely care about. As my involvement has grown, I’d like to open a conversation about reviewing my current stipend to better reflect the scope and continuity of the work I am now taking on

Over the past year, my responsibilities have expanded across several areas of the community, including contributor onboarding and pathways, GSoC, building trust, community engagement, events, content and communications, partnerships and sponsorships, program development, and representing JSON Schema at developer spaces. I have also been focused on creating more structured and sustainable ways for people to discover the project, participate, contribute, and remain engaged over time.

Partnerships and sponsorships have also become an important part of this work. Last year, the conference had 5 partners, and this year I have been actively reaching out to potential conference partners, managing conversations, and helping build relationships that can support the event and the wider ecosystem. Beyond the conference itself, I have also helped bring in new recurring sponsors this year, creating relationships that extend beyond a single event and provide ongoing value to the project. I see this as an important part of building a sustainable community program, developing relationships that can support not just individual events, but the longer-term growth of JSON Schema.

The upcoming conference is one example of the scale of this work. As we get closer, there are many moving parts requiring close and continuous coordination such as speaker coordination, partner and vendor management, programming, operations, logistics, scheduling, communications, planning, and on-the-ground execution. These pieces often happen concurrently and require a significant amount of focused attention to make sure the overall experience comes together smoothly.

At the same time, I see the conference as just one part of the broader community work rather than the endpoint of it. There is already a growing pipeline of initiatives and opportunities for next year, including:

• JSON Schema Local Co-working & Community Groups (in-person) — creating more opportunities for local community connection and participation.
• The possible 24-hour online conference bringing together the broader Open Standards community (currently being discussed with other open standards groups).
• Further contributor onboarding, mentorship, and community pathway initiatives.
• More opportunities for community-led programs, collaboration, partnerships, and ecosystem engagement.

I am excited about these opportunities and would love to continue contributing beyond the conference and helping build a community program that is sustainable, welcoming, well-organised, and able to grow with the project.

With the scope of the work, the time and attention it requires, the partnerships and sponsorship relationships I am helping develop with continued responsibilities, I would appreciate the TSC considering a stipend of $1,000/month.

I completely understand that this also needs to be considered within the project’s budget and overall structure, and I am very open to discussing what is feasible. My intention with opening this issue is simply to have a transparent conversation about how we can align the stipend with the role and contribution as the community continues to grow.

Thank you again for the opportunity, the trust, and the experience so far. I am genuinely excited about what we’re building together and look forward to continuing the work. 🙏

No files, tests, or code entry points are mentioned. Start by reviewing the requested stipend, the described responsibilities, and the project's budget and overall structure; done means the TSC reaches a documented decision about the stipend and role.