Development Platform Clause Samples
Development Platform. Customer may utilize the Development Platform to create an Application to run on the Platform Services. Customer’s use of the Development Platform is governed by the terms of the Agreement subject to the restrictions set forth in Sections 4.2.1 to 4.2.2 below. Customer’s development of an Application must meet the best practices development guidelines set forth in the User Guide. Each Customer Application shall at all times materially conform to policies and best practices set forth in the User Guide. Prior to the deployment of any Customer Applications in a production or non-production environment of the Platform Services, Customer must conduct security and functional tests of each Customer Application and submit the results of such tests to BMC for review. BMC reserves the right to reject Customer’s deployment request of a Customer Application based on the results of Customer’s security and functional tests. Additionally, BMC reserves the right, during the term of the Agreement, to request Customer conduct additional security and functional tests and provide the results of said tests to BMC for review. Notwithstanding the foregoing, Customer must ensure that at all times Customer Applications are secure.
Development Platform. The GitLab development platform hosted at the French National Institute of Nuclear and Particle Physics - in2p3 (1) - was chosen and made available for the whole ESCAPE community. The idea of establishing this service and making it available was not to substitute the development platforms already used by each institution/group. It provides however a common place to gather the common developments, ideas, guidelines and templates for the community, as well as a development platform for new developments if needed by an institution/group and shows the potential integration of this development platform in the software lifecycle. Two main reasons led us to choose the self-hosted GitLab platform rather than GitHub (despite its popularity). First, GitHub's services are based on a closed source and are privately owned (the platform was bought by Microsoft in 2018), and second, the GitLab platform is hosted by one of the ESCAPE consortium members. Table 1: comparison of GitHub or GitLab as web services and a self-hosted GitLab solution Advantages Drawbacks GitHub or GitLab as a service - Free for open source - No setup - Integration with lot of services - Huge community - Data stored outside the E.U. - No control over the data & conditions of use - No control of accounts Self-hosted GitLab - Private projects - Control - Open source - Private projects - Control - Open source A GitLab group was created (2) where the developments under the ESCAPE2020 project WP3 are currently being collected. Within this group a 'template project' was created (3). The objectives of this template project are:
1. Provide the main guidelines for developing a new Open Source project (within the ESCAPE context),
2. Have a web platform where the new implementations discussed within the ESCAPE work packages can be tested, and
3. Show a 'real' use case development example. The project will be reused and customized as per the individual needs of ESCAPE partners. The idea behind a template is that any user can make a copy of it (clone or fork the repository) and start making changes / continue developing from the state of this work. The main components a repository must contain are: An open source license file (the license and provenance model will be covered in D3.7); Various README files with instructions/explanations of the different packages within the project and their usage. Within these files the contribution guidelines (instructions) are also explained in detail; A setup.py file to...