On Thu, 15 Nov 2018, Theodore Y. Ts'o wrote: > On Thu, Nov 15, 2018 at 04:29:43PM +0000, Joseph Myers wrote: > > On Thu, 15 Nov 2018, Theodore Y. Ts'o wrote: > > > > > That's great. But is it or is it not true (either de jure or de > > > facto) that "a single active glibc developer" can block a system call > > > from being supported by glibc by objecting? And if not, under what is > > > the process by resolving a conflict? > > > > We use a consensus-building process as described at > > <https://sourceware.org/glibc/wiki/Consensus>. > > So can a single glibc developer can block Consensus? If it's a sustained objection - it still works an awful lot better than how things worked before 2011/12. (See my suggestion of having a process involving a supermajority vote of the GNU maintainers for glibc in the rare cases where a consensus cannot be reached - but those are rare enough that actually agreeing a process for such cases has never been a priority.) -- Joseph S. Myers joseph@xxxxxxxxxxxxxxxx
