https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229859
--- Comment #6 from Mathieu Arnold <m...@freebsd.org> --- (In reply to Kurt Jaeger from comment #5) > Do I understand you correctly that you suspect that it would undermine > the role of the maintainer, so that in the long run being a maintainer > would not be seen as a useful role ? The change you proposes creates a very bad precedent. It would mean that committers are somehow above other people, and can decide to do whatever they want and the maintainer would have to check that the change they wanted to make to the port that they maintain (and thus, know better than the committer) was actually made the way they wanted. The policy in place says that submissions can be linted by committers, and this is because committers are supposed to know how to use the framework better than contributors. It is their main reason we have committers, a small group of people who know how the framework works and make sure submissions conform with its policies. But maintainers know their ports better than committers. If a committer want to change something that is not covered by the blanket approval, they can do like every other contributor, create a patch and open a PR. I do this regularly, I then use the snoozetab firefox extension to recall the tab with that PR in two weeks, and then I go do something else while it stews. Then I either get the tab back a couple of weeks later, or get an email from bugzilla if someone commented on the PR to say yes, no or whatever. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
