Repository navigation
Steering Committee - Meeting Minutes and Decisions #7
Replies: 8 comments 5 replies
2024-03-15Participants: Decisions and next actions
|
2025-02-17Participants
Agenda
Decisions and next actions
|
2025-05-27Participants @domoritz Agenda
Notes and Decisions
Participating in Studies
Funding Use
Open Collective
Funding Notes
Community Growth
Vega Conf
Lightning Talk Ideas
To Do
|
2025-08-27Participants: Agenda
Notes and DecisionsVega conference
Faster turnaround on PR and issues
Numfocus
Misc
|
2025-11-18Participants@joelostblom AgendaUpdates from Altair, Vega, etc
Funding
How to push PRs over the line
|
Steering Committee Meeting March 3, 2026Participants@jonmmease Updates from projects
Bountyhttps://github.com/vega/vega/discussions/categories/-experiment-feature-request-fastlane
Sponsoring DocsDraft for the website: https://github.com/vega/vega.github.io/tree/sponsor-page
Potential candidates we can send this to: Hex, Databricks, Datadog, Elastic. @mattijn @domoritz @jonmmease @kanitw @hydrosquall work on this over the next week to review.
AI PolicyNo explicit policy at the moment but we expect any contributor to be fully responsible for every line of code. For now, we have not seen issues but we may add an explicit policy when there is an issue. |
Steering Committee Meeting May 26, 2026Participants@jheer Updates from projects6.1.0 release of Altair 🎉! Lots of activity on the Vega/Vega-Lite repos. First bounty received a pull request. We need to consider what to do about agentic PRs. We now have an npm org for Vega. This simplifies adding people to get release permissions. Wins
Community building (@hydrosquall leading)
Notes
Next steps for sponsoring
Agentic PRs and how to deal with themDouble-edged sword. One one had allows people who are in the community to send PRs for changes. It empowers people and if the PRs are good, it makes sense to adopt the changes. However, AI PRs are often complex, and the author may not fully understand the implementation or whether it could have been simpler. This increases the maintenance burden (which is already challenging). Drive-by PRs (one off PRs) could be a burden when the author does not respond to feedback. No general policy. Proposed strategy: build of a ladder of engagement. Start with a small reaction (e.g. comment on a pull request asking for motivation), then engage more and more if we see that the author is engaging. TODO
|
Steering Committee Meeting August 25, 2026Participants@domoritz Updates from projects@domoritz Merged a bunch of PRs in Vega and made a release. Developed a process with git work trees + claude to triage a bunch of PRs and make a release. Typescript schema generator is in go. Vega-Lite now should run the full tests on forks (previously people had to add a PAT). Altair had a few fixes and work on automatic releases (with GitHub actions). Winshttps://github.com/datamazelab/vl2x as a cool demo. SponsorshipLet's get companies to become partners. Community health@hydrosquall wrote a proposal for lead maintainers per repo. Lead maintainers can self merge. Core maintainers are trusted and should judge whether they want another set of eyes on API changes. @hydrosquall has a few candidates for helping with a newsletter. We are having great contributions coming in especially from Omni, Databricks, and Microsoft. Security updateIn the recent releases, we get AI bots sending safety reports. It takes time to review and often turns out to not be credible security issues. AI contributionsShut down bug bounty because it led to too many drive by contributions. It's been great that community members can contribute to other packages (e.g. Altair contributors to Vega). Altair has had good experiences. VIS mini meetupLet's do it. Maybe in a break or an evening at the Datadog office? |
Uh oh!
There was an error while loading. Please reload this page.
We'll use this discussion to document decisions taken in meetings of the Vega Steering Committee. Everyone is welcome to provide inputs by replying to the individual discussion comments. Top-level comments are ideally to be used for the minutes only.
See vega/altair#3164 for a history of the meeting minutes and decisions of the former Vega-Altair Steering Committee which got merged into the Vega Steering Committee.
All reactions