apache / apache/spark-connect-gateway
[COMMUNITY] Request to open dedicated discussion space (Slack /Discord/ GitHub Discussions)
- Dominant language
- Rust
- Stars
- 9
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Hi maintainers and community members,
I have been closely following the development of Spark Connect Gateway and am very excited about its potential for multi-tenant orchestration, gRPC routing, and enterprise-grade data access. I am keen to contribute actively to this project (code contributions, testing, and issue triage).
As more developers and users take an interest in this repository, having a centralized and dedicated discussion channel would greatly help us:
- Collaborate on technical designs, RFCs, and architecture decisions.
- Help newcomers and contributors ramp up, troubleshoot setup issues, and share feedback.
- Track common challenges, use cases, and community requirements without cluttering broad general channels.
Could we consider enabling GitHub Discussions for this repository or setting up a dedicated Slack channel (such as #spark-connect-gateway in the Apache Spark workspace)?
Looking forward to your thoughts and happy to help coordinate this!
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or code entry points are named. Start by reviewing the options in the request—GitHub Discussions, a dedicated Slack channel, or Discord—and the repository’s existing community setup. Done means maintainers choose and establish a centralized discussion space for designs, contributor support, troubleshooting, and feedback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100