REQUIREMENTS. A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:
a) it complies with the terms and conditions of this Agreement; and
b) its license agreement:
i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose;
ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits;
iii) states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and
iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange. When the Program is made available in source code form:
a) it must be made available under this Agreement; and b) a copy of this Agreement must be included with each copy of the Program. Contributors may not remove or alter any copyright notices contained within the Program. Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution.
REQUIREMENTS. Each performer shall prepare a dedicated Quality Plan. For contracts placed directly by the IO, this is sent to the IO for review and acceptance. For Procurement Arrangements and Task Agreements, the DA submits a Quality Plan for IO review and acceptance however DA supplier/subcontractor Quality Plans are accepted by the DA, and then submitted to the IO for acceptance. Quality Plans shall be submitted to the IO after suppliers/subcontractors are identified. Quality Plans shall be brief and to the point, while giving sufficient visibility on the control of the activities to be carried out. Quality Plans shall be revised, when appropriate, to reflect changes that have been made e.g.: • to the requirements of the contract • to the manner in which the contract is implemented A revised Quality Plan shall be subject to the same acceptance procedure as the original Quality Plan. Work shall continue in accordance with the current approved Quality Plan until the revised Quality Plan is accepted. DAs and IO direct contractors shall prepare a dedicated Quality Plan and submit it to the IO for acceptance. The DA Suppliers/Subcontractors dedicated Quality Plans are accepted by the DA, and then submitted to the IO for acceptance. Work shall not start until the relevant Quality Plan has been accepted by the IO. Work shall be performed as directed in the Quality Plan. The performers shall monitor the implementation and effectiveness of the Quality Plan. Documents referred to in the Quality Plan shall be made available to the IO. IO acceptance of the Quality Plan shall not relieve the performer of any contractual obligations and responsibilities. Quality Plans are living documents and shall be updated to identify any changes from the original e.g. change in design activities; the supply chain or surveillance management. Revised Quality Plans must follow the same acceptance procedure as the original.