andygrove opened a new pull request, #2002: URL: https://github.com/apache/datafusion-ballista/pull/2002
# Which issue does this PR close? Closes #2001. # Rationale for this change As Ballista attracts more contributors and adopters, it becomes easy for a well-intentioned change to quietly take functionality away from an existing class of user. Ballista serves several distinct audiences that come to the project for different reasons and depend on different guarantees, but those audiences are not written down anywhere reviewers can check against. This page names them and turns them into a review contract, so we can keep changes **additive**: a PR may add or extend a persona, but should not remove or silently regress a capability an existing persona relies on. # What changes are included in this PR? A new `docs/source/contributors-guide/user-personas.md` page, wired into the Contributors Guide navigation. It explains the additive-change contract and defines three initial personas using a shared schema (who they are, what they are coming from, why Ballista, what they depend on, and the red flags that would regress them): 1. **The DataFusion user going multi-node** — wants transparent distribution with results identical to single-process DataFusion. 2. **The Spark user wanting the same execution model** — wants the stage/task model and AQE exposed and tunable. 3. **The library user building a specialized engine** — embeds Ballista and depends on stable, composable public APIs and extension points. The registry is append-only: new personas can be added over time, existing ones are not removed. # Are there any user-facing changes? Documentation only — a new Contributors Guide page. No code or API changes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
