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. Overall I think it is a good idea to introduce an explicit CoC > doc to QEMU, and indeed any community project, so thanks for > bringing this up again. > Agreed! > > > +If you are experiencing conflict, you should first address the perceived > > +conflict directly with other involved parties, preferably through a > > +real-time medium such as IRC. If this fails, I agree with Daniel that this part should only be advisory. For example: If you are experiencing conflict, please consider first addressing the perceived conflict directly with other involved parties, preferably through a real-time medium such as IRC. If this fails or if you do not feel comfortable proceeding this way,... Also this document doesn't mention anything about ensuring the > confidentiality/privacy for any complaints reported, which I > think is important to state explicitly. > Agreed, and also the part about keeping a record should be removed from the consequences part because it's a privacy regulation minefield. Thanks, Paolo > > 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 :| > >
