Ma77Ball commented on issue #4071: URL: https://github.com/apache/texera/issues/4071#issuecomment-3565830276
Thanks for the clarification! That all makes sense. Given the Apache workflow and the limitations around GitHub's triage role, it's completely fine if we don't add the triage role for this purpose. This feature was more of a nice-to-have, as there are a few reasons I thought having triage access could be beneficial: 1. The website will likely have more frequent, minor edits (content tweaks, documentation fixes, layout changes). Allowing trusted contributors to help organize PRs can reduce the burden on committers. 2. The ability to self-assign or manage issues makes it easier for website maintainers to indicate what they're actively working on, reducing duplicate efforts. These would be conveniences rather than necessities, and access to the website repo can also be managed independently, so I'm totally fine with leaving things as they are, especially if this is the standard practice amongst Apache projects. -- 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]
