You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This event provides a great opportunity for collaboration. Participants can use the time to discuss important project topics, pair program, resolve bugs, build consensus, or tinker on new ideas. It's also a great time to collaborate with peers from other projects and learn more about their work and how the OpenJS Foundation can support these efforts.
Full Agenda TBD
Registration
This is an open event, but is geared towards contributors of the deck.gl framework and other frameworks in the vis.gl and kepler.gl OpenJS projects. We're also welcoming contributors from new projects joining OpenVis this year, including GeoDa!
Registration is required for attendance at the Summit. To attend the in-person Summit in Seattle, please register here
Attending in person
The Google South Lake Union office is located in Downtown Seattle.
While wearing masks is not mandatory, attendees are welcome to wear them if they choose.
As the summit takes place in an office building, attendees should remain within the designated summit area. If you need to leave this area, please seek assistance from a Google employee or security personnel on site.
The summit starts at 9:00 with a breakfast, sessions start at 9:30 and ends at 15:00 each day. After the summit we should leave the building by 16:00.
We invite vis.gl / deck.gl / kepler.gl / GeoDa contributors and collaborators to submit sessions proposals for this Collaborator Summit through this link.
We encourage submissions that foster collaboration, including panels, fire-side chats, discussions, interactive workshops, and presentations.
The goal of the Open Visualization Collaborator Summit is to enable discussions and collaborations on strategic long-term initiatives critical to the vis.gl, kepler.gl, and GeoDa projects.
Have an idea for a talk and want to run it by us? Discuss it here or contact us at openvizsummit@openjsf.org if you’re interested.
F.A.Q.
Is there any registration fee?
No, there is no fee for attending this year's summit.
Will there be remote attendance?
We will not be able to facilitate remote attendance; however, sessions will be recorded and made available on the OpenJS YouTube channel after the event.
Is financial support available for travel expenses?
OpenJS generously offers a community fund to support travel expenses for Collaborators, Standards body participants, and Speakers. Applicants should explore employer-sponsored funding options as their first source of financial support before applying.
Important for all participants ☝
We want everyone, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age, religion or lack thereof, to feel welcome and safe and collaborate with each other in a harassment free environment. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Summit participants violating these rules may be sanctioned or expelled.
Uh oh!
There was an error while loading. Please reload this page.
Date: October 8-9, 2025
Venue: Google South Lake Union, 1021 Valley St, Seattle, WA 98109
Cost: Free
Registration Page: Register Here!
Agenda: Check the event website for the latest agenda!
Schedule
This event provides a great opportunity for collaboration. Participants can use the time to discuss important project topics, pair program, resolve bugs, build consensus, or tinker on new ideas. It's also a great time to collaborate with peers from other projects and learn more about their work and how the OpenJS Foundation can support these efforts.
Full Agenda TBD
Registration
This is an open event, but is geared towards contributors of the deck.gl framework and other frameworks in the vis.gl and kepler.gl OpenJS projects. We're also welcoming contributors from new projects joining OpenVis this year, including GeoDa!
Registration is required for attendance at the Summit. To attend the in-person Summit in Seattle, please register here
Attending in person
Connect with us!
Submit a session proposal!
We invite vis.gl / deck.gl / kepler.gl / GeoDa contributors and collaborators to submit sessions proposals for this Collaborator Summit through this link.
We encourage submissions that foster collaboration, including panels, fire-side chats, discussions, interactive workshops, and presentations.
The goal of the Open Visualization Collaborator Summit is to enable discussions and collaborations on strategic long-term initiatives critical to the vis.gl, kepler.gl, and GeoDa projects.
Have an idea for a talk and want to run it by us? Discuss it here or contact us at openvizsummit@openjsf.org if you’re interested.
F.A.Q.
Is there any registration fee?
No, there is no fee for attending this year's summit.
Will there be remote attendance?
We will not be able to facilitate remote attendance; however, sessions will be recorded and made available on the OpenJS YouTube channel after the event.
Is financial support available for travel expenses?
OpenJS generously offers a community fund to support travel expenses for Collaborators, Standards body participants, and Speakers. Applicants should explore employer-sponsored funding options as their first source of financial support before applying.
Important for all participants ☝
We want everyone, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age, religion or lack thereof, to feel welcome and safe and collaborate with each other in a harassment free environment. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Summit participants violating these rules may be sanctioned or expelled.
Code of Conduct
The Linux Foundation Events Code of Conduct applies to all event spaces.
The text was updated successfully, but these errors were encountered: