<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hello!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you for giving Airship documentation a home. Having our documentation spread across several Read the Docs sites has long been a frustration for new Airship users. We are excited to fully embrace the site but cannot do so until all
of our content is represented there. Since we have many source code repositories, our documentation originates from several different locations. For example, Treasuremap is publishing to docs.airshipit.org; however, Armada documentation [0] is not reachable
from that page<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Airship Working Committee has considered how to accomplish hosting all of our documentation on the same site while allowing it to live in the same repositories as the corresponding source code. Looking at the publish job [1], it appears
that we could accomplish this by removing the final key, adding all of our projects to the “allowed-projects” list, and overriding the “publish_site” variable in repository-specific jobs. For example, we could create a job in the Armada repository that publishes
to “airshipit.org/docs/armada” and link to it from our main documentation at docs.airshipit.org.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is our approach feasible given our current setup? If so, the Working Committee will start submitting the necessary changes.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks in advance for your help!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Drew Walters<o:p></o:p></p>
<p class="MsoNormal">Airship Working Committee<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[0] <a href="https://airshipit.readthedocs.io/projects/armada/en/latest/">
https://airshipit.readthedocs.io/projects/armada/en/latest/</a><o:p></o:p></p>
<p class="MsoNormal">[1] <a href="https://opendev.org/openstack/project-config/src/branch/master/zuul.d/jobs.yaml#L452">
https://opendev.org/openstack/project-config/src/branch/master/zuul.d/jobs.yaml#L452</a><o:p></o:p></p>
</div>
</body>
</html>