On Mon, Mar 29, 2021 at 10:59:23PM +0200, Paolo Bonzini wrote: > Il lun 29 mar 2021, 20:33 Daniel P. Berrangé <berra...@redhat.com> ha > scritto: > > > The obvious alternative is to import the contributor covenant > > > > https://www.contributor-covenant.org/ > > > The Contributor Covenant 1.x and 2.x are very different in that 2.x also > includes conflict resolution. Unlike the code of conduct, the consequences > of bad behavior are hard to generalize across multiple projects, so I would > prefer anyway the 1.x version. The differences with the Django CoC aren't > substantial. > > However this does mean being more careful about the language in the > "custom" documents such as the conflict resolution policy. > > > The second, it isn't a static document. It is being evolved over > > time with new versions issued as understanding of problematic > > situations evolves. We can choose to periodically update to stay > > current with the broadly accepted norms. > > > > This however has the same issues as the "or later" clause of the GPL (see > the above example of 1.x vs 2.x for the Contributor Covenant). I don't > think upgrade of the CoC should be automatic since there are no > "compatibility" issues.
Note, I didn't say we should automatically upgrade - I said we can choose to upgrade. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
