Bug 206677 - please fix 17. The FreeBSD Committers' Big List of Rules # 5
Summary: please fix 17. The FreeBSD Committers' Big List of Rules # 5
Status: New
Alias: None
Product: Documentation
Classification: Unclassified
Component: Documentation (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: FreeBSD Core Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-27 14:56 UTC by John Marino
Modified: 2017-12-23 20:41 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Marino freebsd_committer 2016-01-27 14:56:29 UTC
"Any disputed change must be backed out pending resolution of the dispute if requested by a maintainer".

This is unacceptably ambiguous.  For ports alone, there are hundreds of maintainers (potentially 25,000+ maintainers).

It cannot be that *any* maintainer can force any commit to be backed out.  There has to be some ownership or connection or affect by the commit.  Please update the wording to reflect to the real intention (I am assuming what is literally written is not the desired rule)
Comment 1 John Marino freebsd_committer 2016-03-23 11:08:42 UTC
how about changing it to this?

"Any disputed change must be backed out pending resolution of the dispute if requested by someone who maintains code demonstrably affected by the change." ?
Comment 2 Matthew Seaman freebsd_committer 2017-12-23 20:06:07 UTC
Thank you for raising this issue.

Core generally prefers for people to send e-mail to core@FreeBSD.org rather than having a discussion through the comments on a bugzilla ticket.  Let's take it to e-mail.
Comment 3 Matthew Seaman freebsd_committer 2017-12-23 20:41:45 UTC
I have only just noticed this is nearly two years old...