<@U0A71G31CDV> who is the repo maintainer to @ whe...
# questions-and-troubleshooting
n
@Rocky who is the repo maintainer to @ when assigning an issue
r
The StarRocks community does not use a single "catch-all" handle (like
@maintainers
) for issue assignments. Instead, the process is decentralized and depends on the specific area of the project. According to the Contributing Guide, here is how you should handle issue assignments: 1. Comment on the Issue The most direct way is to comment on the issue itself stating that you would like to work on it. * Recommendation: Briefly share your plan for how you intend to solve the problem. * Whom to mention: If there is already a maintainer or committer engaging in the thread (e.g., they labeled the issue or added a comment), mention them directly by their GitHub handle. 2. Identify the Right Maintainer If no one has commented yet, you can find the relevant experts for that area: * Labels: Look at the labels assigned to the issue (e.g.,
area/query
,
area/storage
,
area/lakehouse
). * CODEOWNERS: Check the `.github/CODEOWNERS` file in the repository to see which individuals or teams are responsible for the specific directory related to the issue. * Frequent Contributors: Often, users will @ a specific committer who frequently works in that area (common names seen in recent issues include
kangkaisen
for query-related features or
murphyatwork
for general enhancements). 3. Use Slack for Coordination If you don't get a response on GitHub, the most effective way to reach a maintainer is through the StarRocks Slack. * Join the StarRocks Slack community. * Post your request in the
#contributing-to-starrocks
channel with a link to the issue. Summary of Process: 1. Sign the CLA. 2. Comment "I would like to work on this, please assign me" on the GitHub issue. 3. If no one assigns it within a day or two, ask in the
#contributing-to-starrocks
Slack channel. References • developers/How_to_Contribute.md