This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ripe-list] consensus defintions
- Previous message (by thread): [ripe-list] RIPE Working Group Chair Collective Meeting Summary
- Next message (by thread): [ripe-list] consensus defintions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Tue Feb 9 14:22:41 CET 2021
> On 9 Feb 2021, at 12:49, JORDI PALET MARTINEZ via ripe-list <ripe-list at ripe.net> wrote: > > Even if only me see those problems (which again is not the case, according to WGCC summary), still there is a chance that with the discussion of the proposal others support it and we can find a point where objections are invalid. This is what consensus mean. It does not mean that. You are wrong. Please read RFC7282. I quote: "Consensus is when everyone is sufficiently satisfied with the chosen solution, such that they no longer have specific objections to it.” Everyone is not sufficiently satisfied with your proposal(s) - QED - so by definition there cannot be a consensus for them.
- Previous message (by thread): [ripe-list] RIPE Working Group Chair Collective Meeting Summary
- Next message (by thread): [ripe-list] consensus defintions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]