Hi all, I wanted to kick-off the email discussion around the wording and additional input for next week's vote on a potential exemption from the requirement to utilize a Pod Descriptor File for the Airship project.
Besides kicking off the wordsmithing process, I'd also like to direct a request to the Airship team to compile input for the TSC. As I mentioned on the TSC call, I'd like to prioritize value over former governance decisions, but want to be able to better understand the context of our decision. So, in line with other exemption requests and without attempting to add an overly huge burden on the Airship team, I'd like to ask the Airship project to describe... 1. the technical challenges of using the PDF for Airship. It has been stated that there are gaps / missing information in the PDF making it hardly suitable for Airship. I'd like to understand the challenges and the effort needed to make this work. 2. a firm plan on how to evolve Airship and the PDF (where needed) to make both go together in the Jerma release. Assuming those aspects will be addressed, I'd like to propose the following vote text: "Does the TSC exempt the Airship project from utilizing the Pod Descriptor File for the Iruya release based on a documented plan for supporting the PDF in the Jerma release?" Feedback and input is welcome. Best regards Georg
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#23739): https://lists.opnfv.org/g/opnfv-tech-discuss/message/23739 Mute This Topic: https://lists.opnfv.org/mt/61965023/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
