TEMPLATE LAYOUT FOR THE OPEN SOURCE PORTAL Sample Clauses

TEMPLATE LAYOUT FOR THE OPEN SOURCE PORTAL. This section presents requirements for the Open Source Portal for each open source project. The PREFORMA website contains a dedicated section for the Open Source Portal, which presents a web page in order to provide an overview of all open source projects. From this overview page it is possible to reach a dedicated page for each open source project. On this overview page each open source project shall be selectable (and linked to) and there shall be a title and a short description (2-3 sentences) of each open source project. From each dedicated open source project page on the PREFORMA website there will be a number of specific links to specific resources provided by each open source project which is hosted on an open platform (GitHub or equivalent). The rest of this section details requirements for the content on each dedicated open source project page on the PREFORMA Open Source Portal. At time of writing, specific links to resources provided by each open source project are not yet available. Therefore, this section will use indicative conceptual links to precisely what will be provided from each open source project. Each dedicated open source project page on the PREFORMA website will contain the following sections: • Overview • Documentation and coding practices • Collaboration and development toolsSource code • Build environment • Executables • Test files For the remainder of this section we detail each of these sections.
AutoNDA by SimpleDocs

Related to TEMPLATE LAYOUT FOR THE OPEN SOURCE PORTAL

  • Third Party Software/Open Source Nothing in this Agreement shall restrict, limit or otherwise affect any rights or obligations You may have, or conditions to which You may be subject, under any applicable open source licenses to any open source code contained in the Software. The Software may include or be bundled with other software programs licensed under different terms and/or licensed by a licensor other than Licensor. Use of any software programs accompanied by a separate license agreement is governed by that separate license agreement. Any third party software that may be provided with the Software is included for use at Your option.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • Open Source Software The Software product may include certain open source components that are subject to open source licenses (“Open Source Software”), in which case, the embedded Open Source Software is owned by a third party. The Open Source Software is not subject to the terms and conditions of this XXXX. Instead, each item of Open Source Software is licensed under its applicable license terms which accompanies such Open Source Software. Nothing in this XXXX limits your rights under, nor grants you rights that supersede, the terms and conditions of any applicable license terms for the Open Source Software. Any fees charged by GC in connection with the SOFTWARE, do not apply to the Open Source Software for which fees may not be charged under the applicable license terms. The terms and conditions of the applicable license for the Open Source Software are available on the LICENSE.txt file, which is provided with the SOFTWARE.

  • Third Party Software 1. The Software may contain third party software that requires and/or additional terms and conditions. Such required third party software notices and/or additional terms and conditions are located at xxxx://xxx.xxxxxxxxx.xxx/thirdparty/index.html and are made a part of and incorporated by reference into this XXXX. By accepting this XXXX, You are also accepting the additional terms and conditions, if any, set forth therein.

  • Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient.

  • CONTRACTOR TO PACKAGE DELIVERABLES The Contractor will package deliverables in accordance with good commercial practice and shall include a packing list showing the description of each item, the quantity and unit price unless otherwise provided in the Specifications or Supplemental Terms and Conditions, each shipping container shall be clearly and permanently marked as follows: (a) The Contractor's name and address, (b) the City’s name, address and purchase order or purchase release number and the price agreement number if applicable, (c) Container number and total number of containers, e.g. box 1 of 4 boxes, and (d) the number of the container bearing the packing list. The Contractor shall bear cost of packaging. Deliverables shall be suitably packed to secure lowest transportation costs and to conform to all the requirements of common carriers and any applicable specification. The City's count or weight shall be final and conclusive on shipments not accompanied by packing lists.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Templates The Applicant shall use Templates provided by Alberta Innovates to comply with its Required Reporting Metrics, Reports obligations, and with the Survey requirements. Because the Reports may contain technical or proprietary information about the Project or the Applicant, the Templates will specify when a section will be considered non-confidential. The content of sections that are marked as non-confidential can be disclosed in the public domain. All other sections will be considered confidential, and thus can only be disclosed to the Government of Alberta and to Funding Partners, if any, in confidence, but to no other party.

  • Software compliance Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license (like MIT, BSD, Apache 2.0,...). ● The license should provide unlimited access rights to the EGI community. ● Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the EGI organisation in GitHub13.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. ○ Using Semantic Versioning. ○ Using a Configuration Management frameworks such as Ansible. ○ Taking security aspects into consideration through at every point in time. ○ Having automated testing in place. ○ Using code reviewing. 9 xxxxx://xxx.xxx.xx/about/policy/policies_procedures.html 10 xxxxx://xxxx.xxx.xx/wiki/OMB 11 xxxx://xxx.xxx.xx/ 12 xxxxx://xxx.xxx.xx/portal/index.php?Page_Type=NGI&id=4 13 xxxxx://xxxxxx.xxx/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.

  • Open Source 15.1 All software created for the Buyer must be suitable for publication as open source, unless otherwise agreed by the Buyer.

Time is Money Join Law Insider Premium to draft better contracts faster.