<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">I notice that although the code is released under the Apache license, looking at a conceivable real at-scale deployment one would need to read docs still marked as belonging to AT&T, for example<div><br></div><div><a href="https://opendev.org/airship/treasuremap">https://opendev.org/airship/treasuremap</a> links to<br></div><div><a href="https://airship-treasuremap.readthedocs.io/en/latest/index.html">https://airship-treasuremap.readthedocs.io/en/latest/index.html</a><br></div><div><br></div><div>which is marked "© Copyright 2018 AT&T Intellectual Property. Revision 93aed048."<br><br>I do not know if this is a problem, per se, but does not seem entirely openstack-like to me.<br><br>Chris</div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Oct 16, 2019 at 3:17 PM Jeremy Stanley <<a href="mailto:fungi@yuggoth.org">fungi@yuggoth.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hi TC members,<br>
<br>
The Airship project will start its confirmation process with the OSF<br>
Board of Directors at the Board meeting[1] Tuesday next week. A<br>
draft of the slide deck[2] they plan to present is available for<br>
reference.<br>
<br>
Per the confirmation guidelines[3], the OSF Board of directors will<br>
take into account the feedback from representative bodies of<br>
existing confirmed Open Infrastructure Projects (OpenStack, Zuul and<br>
Kata) when evaluating Airship for confirmation.<br>
<br>
Particularly worth calling out, guideline #4 "Open collaboration"<br>
asserts the following:<br>
<br>
    Project behaves as a good neighbor to other confirmed and pilot<br>
    projects.<br>
<br>
If you (our community at large, not just TC members) have any<br>
observations/interactions with the Airship project which could serve<br>
as useful examples for how these projects do or do not meet this and<br>
other guidelines, please provide them on the etherpad[4] ASAP. If<br>
possible, include a citation with links to substantiate your<br>
feedback.<br>
<br>
If a TC representative can assemble this feedback and send it to the<br>
Board (for example, to the foundation mailing list) for<br>
consideration before the meeting next week, that would be<br>
appreciated. Apologies for the short notice.<br>
<br>
[1] <a href="http://lists.openstack.org/pipermail/foundation/2019-October/002800.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/foundation/2019-October/002800.html</a><br>
[2] <a href="https://www.airshipit.org/collateral/AirshipConfirmation-Review-for-the-OSF-Board.pdf" rel="noreferrer" target="_blank">https://www.airshipit.org/collateral/AirshipConfirmation-Review-for-the-OSF-Board.pdf</a><br>
[3] <a href="https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmationGuidelines" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmationGuidelines</a><br>
[4] <a href="https://etherpad.openstack.org/p/openstack-tc-airship-confirmation-feedback" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/openstack-tc-airship-confirmation-feedback</a><br>
<br>
-- <br>
Jeremy Stanley<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Chris Morgan <<a href="mailto:mihalis68@gmail.com" target="_blank">mihalis68@gmail.com</a>></div>