<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Chris, thank you for the feedback.</div><div class=""><br class=""></div><div class="">I think it comes from the way how Apache 2.0 license needs to get applied, with a line like described here – [0].</div><div class="">> Copyright [yyyy] [name of copyright owner]</div><div class=""><br class=""></div><div class="">But the concern is valid, and I have submitted a change to get it changed to "Airship Team” – [1].</div><div class=""><br class=""></div>[0] <a href="https://www.apache.org/licenses/LICENSE-2.0#apply" class="">https://www.apache.org/licenses/LICENSE-2.0#apply</a><div class="">[1] <a href="https://review.opendev.org/#/c/689212/" class="">https://review.opendev.org/#/c/689212/</a></div><div class=""><br class=""><div>Best regards,</div><div>— Roman Gorshunov</div><div><br class=""><blockquote type="cite" class=""><div class="">On 17 Oct 2019, at 18:10, Chris Morgan <<a href="mailto:mihalis68@gmail.com" class="">mihalis68@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class="">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 class=""><br class=""></div><div class=""><a href="https://opendev.org/airship/treasuremap" class="">https://opendev.org/airship/treasuremap</a> links to<br class=""></div><div class=""><a href="https://airship-treasuremap.readthedocs.io/en/latest/index.html" class="">https://airship-treasuremap.readthedocs.io/en/latest/index.html</a><br class=""></div><div class=""><br class=""></div><div class="">which is marked "© Copyright 2018 AT&T Intellectual Property. Revision 93aed048."<br class=""><br class="">I do not know if this is a problem, per se, but does not seem entirely openstack-like to me.<br class=""><br class="">Chris</div></div></div></div></div><br class=""><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" class="">fungi@yuggoth.org</a>> wrote:<br class=""></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 class="">
<br class="">
The Airship project will start its confirmation process with the OSF<br class="">
Board of Directors at the Board meeting[1] Tuesday next week. A<br class="">
draft of the slide deck[2] they plan to present is available for<br class="">
reference.<br class="">
<br class="">
Per the confirmation guidelines[3], the OSF Board of directors will<br class="">
take into account the feedback from representative bodies of<br class="">
existing confirmed Open Infrastructure Projects (OpenStack, Zuul and<br class="">
Kata) when evaluating Airship for confirmation.<br class="">
<br class="">
Particularly worth calling out, guideline #4 "Open collaboration"<br class="">
asserts the following:<br class="">
<br class="">
Project behaves as a good neighbor to other confirmed and pilot<br class="">
projects.<br class="">
<br class="">
If you (our community at large, not just TC members) have any<br class="">
observations/interactions with the Airship project which could serve<br class="">
as useful examples for how these projects do or do not meet this and<br class="">
other guidelines, please provide them on the etherpad[4] ASAP. If<br class="">
possible, include a citation with links to substantiate your<br class="">
feedback.<br class="">
<br class="">
If a TC representative can assemble this feedback and send it to the<br class="">
Board (for example, to the foundation mailing list) for<br class="">
consideration before the meeting next week, that would be<br class="">
appreciated. Apologies for the short notice.<br class="">
<br class="">
[1] <a href="http://lists.openstack.org/pipermail/foundation/2019-October/002800.html" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/pipermail/foundation/2019-October/002800.html</a><br class="">
[2] <a href="https://www.airshipit.org/collateral/AirshipConfirmation-Review-for-the-OSF-Board.pdf" rel="noreferrer" target="_blank" class="">https://www.airshipit.org/collateral/AirshipConfirmation-Review-for-the-OSF-Board.pdf</a><br class="">
[3] <a href="https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmationGuidelines" rel="noreferrer" target="_blank" class="">https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmationGuidelines</a><br class="">
[4] <a href="https://etherpad.openstack.org/p/openstack-tc-airship-confirmation-feedback" rel="noreferrer" target="_blank" class="">https://etherpad.openstack.org/p/openstack-tc-airship-confirmation-feedback</a><br class="">
<br class="">
-- <br class="">
Jeremy Stanley<br class="">
</blockquote></div><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div dir="ltr" class="gmail_signature">Chris Morgan <<a href="mailto:mihalis68@gmail.com" target="_blank" class="">mihalis68@gmail.com</a>></div>
</div></blockquote></div><br class=""></div></body></html>