andygrove opened a new issue, #2001: URL: https://github.com/apache/datafusion-ballista/issues/2001
## Is your feature request related to a problem or challenge? As Ballista attracts more contributors and adopters, it becomes easier 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, and today those audiences are not written down anywhere reviewers can check against. ## Describe the solution you'd like Add a **User Personas** page to the Contributors Guide that names each audience Ballista serves and, for each, records: - who they are and what they are coming from, - why they use Ballista, - the capabilities/guarantees they depend on, and - the "red flags" — concrete changes that would regress them. Frame it as a **review contract**: changes must be *additive*. A PR may add or extend a persona, but must not remove or silently regress a capability an existing persona relies on. Reviewers evaluate PRs against the list. Initial personas: 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. ## Describe alternatives you've considered Keeping this knowledge informal / in reviewers' heads — which is what allows silent regressions in the first place. -- 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]
