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

[Xen-devel] [RFC] Integrate CoC, Governance, Security Policy and other key documents into sphinx docs

  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Lars Kurth <lars.kurth@xxxxxxxxxx>
  • Date: Wed, 18 Dec 2019 14:01:26 +0000
  • Accept-language: en-GB, en-US
  • Authentication-results: esa6.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none; spf=None smtp.pra=lars.kurth@xxxxxxxxxx; spf=Pass smtp.mailfrom=lars.kurth@xxxxxxxxxx; spf=None smtp.helo=postmaster@xxxxxxxxxxxxxxx
  • Cc: Jürgen Groß <jgross@xxxxxxxx>, Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>, "Durrant, Paul" <pdurrant@xxxxxxxxxx>, "committers@xxxxxxxxxxxxxx" <committers@xxxxxxxxxxxxxx>
  • Delivery-date: Wed, 18 Dec 2019 14:01:42 +0000
  • Ironport-sdr: fz0Wo7p0+E7IC2PZJM57CiVsC2BFFnnWDtzQhb9rFVfSPEgmJwhTizZaTTntAtuACc6Pe/vXft G7DsDap3au8pWh9nei430kneDIa8WhoTAW3oXk/p6rEeh1iQec2lPvfvMjb8mgEN9/Xn120xxd 87DeokbHZAHp9BCHkqt8pG7Q01pvxH2r4dkOILxHYbBnNPJJH60wZExxzwGc04GtnJh22PK/FM 0KQJ95Wn5d5uafaVMNZdVi71DUIFJ+64NosbBngyiy6fvPd+HAHrfetz+HBkCek+tOsvizXJAd azQ=
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AQHVtaujTAEtf/n3rkCwi9Phdf0Yiw==
  • Thread-topic: [RFC] Integrate CoC, Governance, Security Policy and other key documents into sphinx docs

Hi all,

now that 4.13 is out of the way I wanted to get the CoC discussion closed - see 
 which means I need ACKs or final suggestions. The next step would be to 
publish it on the website.

However, I have also been thinking about keeping some documents in multiple 
places and defining a *master* copy somewhere in a tree. Right now, these are a 
few personal repos that I own, which seems unnecessary, given that we have the 
sphinx docs. In the interest of improving the docs, we also need more useful 
content in the docs to guide people to them.

My proposal would be to move the master sources for a number of key process 
docs to xen.git:/docs maybe under a "Working with the Xen Project community" in 
a process-guide directory. 
This would then include content from
• http://xenbits.xen.org/gitweb/?p=people/larsk/governance.git;a=summaryhttp://xenbits.xen.org/gitweb/?p=people/larsk/security-process.git;a=summaryhttp://xenbits.xen.org/gitweb/?p=people/larsk/code-of-conduct.git;a=summary

and we could also consider including some of the wiki pages related to 
contribution workflow and re-direct the pages.

We would need to answer some questions, such as
a) Are we OK with these staying in markdown - I don’t mind converting
b) Are we OK with some of the documents needing project wide agreement before 
they can be changed, specifically this would cover
- governance.git
- code-of-conduct.git:code-of-conduct.md
- code-of-conduct.git:communication-guide.md

Best Regards


Xen-devel mailing list



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