+1 Clearly committers should have read and write access to all non-private information in a project. I don’t even think this needs a vote. If this discussion quickly reaches consensus, as I assume it will, let’s just make it so.
The hypothetical risk that a committer would (accidentally or deliberately) cause damage is a non-issue. In source control systems such as SVN or Git, any change can be rolled back. Julian > On Aug 13, 2020, at 8:07 AM, Andrei Sereda <[email protected]> wrote: > > Hello, > > For the last two releases ([1] and [2]) committers were not able to > finalize the release due to SVN restrictions. One of the PMC members had to > step in order to distribute the artifacts. > > By default, only PMCs are allowed to make changes to dist > <https://dist.apache.org/repos/dist/release/calcite/> SVN repository. > > This can be changed > <https://issues.apache.org/jira/browse/INFRA-20681?focusedCommentId=17177075&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17177075>. > According to INFA: > >> A link on this Jira to an email discussion where it is approved will be > fine > > PMCs please vote on this proposal. > > Thanks, > Andrei. > > [1] > https://lists.apache.org/thread.html/rbd84cf78ef250685a05fdb9c70708daa6558619093f510d27aabc1af%40%3Cdev.calcite.apache.org%3E > [2] > https://lists.apache.org/thread.html/ra180b94d785d5575558ab10d919521a6395fcce8899ed1dcda78d004%40%3Cdev.calcite.apache.org%3E
