[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] [Xen-devel] [PATCH v2 0/6] Code of Conduct + Extra Guides and Best Practices



Hi Lars,

Sorry for the late response, the Unikraft team is certainly happy to support 
this code of conduct.

Thanks,

-- Felipe

On 27.09.19, 06:22, "Xen-devel on behalf of Lars Kurth" 
<xen-devel-bounces@xxxxxxxxxxxxxxxxxxxx on behalf of lars.kurth@xxxxxxxxxxxxxx> 
wrote:

    From: Lars Kurth <lars.kurth@xxxxxxxxxx>
    
    This series proposes a concrete version of the Xen Project
    CoC based on v1.4 of the Contributor Covenant. See [1]
    
    It contains *ALL* the portions I was still going to add.
    I spent a bit of time on word-smithing, but I am not a native English 
speaker
    So there is probably time for improvement
    
    The series also reflects the discussion in [2] and some private
    discussions on IRC to identify initial members of the Xen
    Project’s CoC team.
    
    For convenience of review and in line with other policy documents
    I created a git repository at [3]. This series can be found at [5].
    
    [1] https://www.contributor-covenant.org/version/1/4/code-of-conduct.md
    [2] https://xen.markmail.org/thread/56ao2gyhpltqmrew 
    [3] 
http://xenbits.xen.org/gitweb/?p=people/larsk/code-of-conduct.git;a=summary
    [4] 
https://www.slideshare.net/xen_com_mgr/xpdds19-keynote-patch-review-for-nonmaintainers-george-dunlap-citrix-systems-uk-ltd
    [5] 
http://xenbits.xen.org/gitweb/?p=people/larsk/code-of-conduct.git;a=shortlog;h=refs/heads/CoC-v2
    
    Changes since v1
    * Code of Conduct 
      Only whitespace changes
    
    * Added Communication Guide
      Contains values and a process based on advice and mediation in case of 
issues
      This is the primary portal for 
    
    * Added Code Review Guide
      Which is based on [4] with some additions for completeness
      It primarily sets expectations and anything communication related is 
removed
    
    * Added guide on Communication Best Practice
      Takes the communication section from [4] and expands on it with more 
examples
      and cases. This is probably where we may need some discussion
    
    * Added document on Resolving Disagreement
      A tiny bit of theory to set the scene
      It covers some common cases of disagreements and how we may approach them
      Again, this probably needs some discussion
    
    Cc: minios-devel@xxxxxxxxxxxxxxxxxxxx
    Cc: xen-api@xxxxxxxxxxxxxxxxxxxx
    Cc: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
    Cc: mirageos-devel@xxxxxxxxxxxxxxxxxxxx
    Cc: committers@xxxxxxxxxxxxxx
    
    Lars Kurth (6):
      Import v1.4 of Contributor Covenant CoC
      Xen Project Code of Conduct
      Add Communication Guide
      Add Code Review Guide
      Add guide on Communication Best Practice
      Added Resolving Disagreement
    
    -- 
    2.13.0
    
    
    _______________________________________________
    Xen-devel mailing list
    Xen-devel@xxxxxxxxxxxxxxxxxxxx
    https://lists.xenproject.org/mailman/listinfo/xen-devel

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/mirageos-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.